Identifying The Record That Caused The “No inserts are allowed in Integration Component” Error.
(Doc ID 519564.1)
Last updated on FEBRUARY 04, 2020
Applies to:Siebel System Software - Version 7.7.2  and later
Siebel CRM - Version 7.7.2 SIA  and later
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.2 
Database: Oracle 126.96.36.199
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Sun Solaris 5.8
This document was previously published as Siebel SR 38-1861267541.
***Checked for relevance on 11-JAN-20111***
A customer added the following integration component user property to a child integration component:
The customer created a workflow that called the Upsert method on the EAI Siebel Adapter business service. If a child record included in the SiebelMessage did not exist in the application an error occurred as expected. In the event of an error the customer wanted to identify the record that caused it.
If a child record included in the SiebelMessage did not exist in the application the following error occurred:
"(stepexec.cpp (768)) SBL-BPR-00162: Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Business Service:xxx'.
SBL-BPR-00162PrcExec PropSet 4 0 2005-03-30 18:15:27 No inserts are allowed in Integration Component 'Contact'.
Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Business Service:xxx'.(SBL-BPR-00162)"
But it was not possible to identify which record caused the error message.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document