z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2 
Database: Oracle 126.96.36.199
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server
This document was previously published as Siebel SR 38-1501532257.
***Checked for relevance on 07-JAN-2011***
Step 1: Start
Step 2. File Transport Method: Receive
Input Argument: d:\export\pu.xml
Output: SiebelXMLFromFile of type binary and stores XMl Doc
Step 3. EAI XML Converter Method: XMLDocToIntObjHier
Output: SiebelPropSet of type Hierarchy
Step 4: End
causes error: SBL-EAI-04398: No input integration object hierarchy found.
CauseAt step 3, the problem was with Output Argument Name. While looking into the workflow process, it was found that the output argument for the EAI XML Converter from File business service was specified â€œSiebel Messageâ€ (with one space) in the XML file exported from the workflow process. The output argument should be â€œSiebelMessageâ€ (without space) instead of â€œSiebel Messageâ€.
Please modify the output variable name :
Step 3: EAI Siebel Adapter Method: Upsert
Input Argument: SiebelPropSet
Applies to: Siebel Product Configurator - Version: 188.8.131.52 SIA and later [Release: V8 and later ]
Information in this document applies to any platform.
with 184.108.40.206 remote product configurator does not work any more
1) enable remote product configurator for financial services and for eCommunications.
2) enable component Siebel Product Configuration Object Manager (ENU) of component group Siebel ISS
3) enable remote product configurator for all products or a small set you want to test with.
4) Import Products
5) Test behavior in Financial Services
select a contact,
in contact screen create an order, select Purchase Order
drill down order
change an attribute
hit Done Button
--> Error message:
SBL-GEN-00000: Unable to load message 0xffff
6)Other scenario with eCommunications:
In Sales Order Screen create a new order, add order line item with product ZP Test Product.
--> SBL-GEN-00000: Unable to load message 0xffff seen in log, not in UI.
Hit Customize and Done and you get following error in UI:
Error invoking service 'SIS OM PMT Service', method 'Synchronize' at step 'Sync Order Line Item'.(SBL-BPR-00162)
No input integration object hierarchy found.(SBL-EAI-04398)
Create a new Line item add poduct, hit Customize
Add a child product and hit Done Button.
You get the error message again.
Click on List link to see the order line items again.
Verify that there are no child items for the root product.
8) Run the same scenario without remote product configurator ans see that now all works without problems.
To turn off remote product configurator set for financial services and eCommunications
Parameter: Product Configurator - Use Rem = TRUE
new CR 10593351, bug
determined as duplicated of CR 12-1VM6MQX
following fixes are available:
220.127.116.11 QF6511 BugID: SBA: 9174030
18.104.22.168 QF0822 BugID: SBA: 9204251
22.214.171.124QF0917 BugID: SBA:9708959
126.96.36.199 Fix Pack Build2 [20435
Applies to: Siebel System Software - Version: 188.8.131.52  and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 184.108.40.206  SVE
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Microsoft Windows 2000 Advanced Server SP 4
This document was previously published as Siebel SR 38-2502831811.
***Checked for relevance on 11-NOV-2010***
SymptomsWhile calling an inbound web service from an VB.Net application, the inbound web service calls a workflow that performs a synchronize using the EAI Siebel Adapter the following error was observed :
SBL-EAI-04398 No input integration object hierarchy found.
CauseSiebelMessage input argument was defined as hierarchy instead of integration object
InboundDispatcher_input_args_187(004).dmp showed that SiebelMessage was of type â€œxsd:string" and that all of the â€œ&â€, â€œ<â€ and â€œ>â€ characters had been escaped in the incoming SOAP message.
The following information was included in the EAI Object Manager log file:
â€œAnger kÃ¶rtidsvÃ¤rde fÃ¶r egenskap 'SiebelMessage' till:
<SiebelMessage MessageId="" IntObjectName="LF Person" MessageType="Integration Object" IntObjectFormat="Siebel Hierarchical"><ListOfLfPerson><Contact><LKFCode>056202</LKFCode><BirthDate>10/24/1945</BirthDate><EmailAddress/><EmailAddress2/><FirstName>Bernst-arne</FirstName><LFCompanyNumber>42</LFCompanyNumber><LFDeceasedDate/><LFSPARProtected>N</LFSPARProtected><LastName>Persson</LastName><MF>K</MF><LFPersonalNumber>19451024-0825</LFPersonalNumber><PartyUId>1163</PartyUId><ListOfCutAddress><CutAddress><AddressType>Alternativ adress</AddressType><City>Stockholm</City><Country>Sverige</Country><LFContactPrimaryAddressFlg>Y</LFContactPrimaryAddressFlg><LFStreetAddress1>Ostgota Brandstodsbolag</LFStreetAddress1><LFStreetAddress2>Platensgatan 11</LFStreetAddress2><LFStreetAddress3>Box 400</LFStreetAddress3><PostalCode>58104</PostalCode></CutAddress></ListOfCutAddress></Contact></ListOfLfPerson></SiebelMessage>â€
This confirmed that the escaped characters included in the incoming SOAP message were correctly â€œunescapedâ€. The log file also showed that the following input argument string was passed to the EAI Siebel Adapter:
As you can see it did not include the value assigned to the SiebelMessage process property. The customer had defined the SiebelMessage process property as follows:
Name, Type, In/Out
SiebelMessage, Hierarchy, In
The reported behavior was resolved after the customer changed the Type of SiebelMessage from Hierarchy to Integration Object and set the Integration Object field to the name of the integration object. The customer then regenerated the WSDL and amended the.NET code accordingly to pass in an instance of the integration object.
Product Release: V7 (Enterprise)
Version: 220.127.116.11  Com/Med
Database: Oracle 18.104.22.168
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 8
This document was previously published as Siebel SR 38-3347905181.
SymptomsWe have created inbound webservice based on Workflow. Workflow has 2 process properties of type Integration Object (Account Integration Object and Order Integration Object)
Workflow upserts Account and Order Integration Objects using EAI Siebel Adapter step.
We were able to create WSDL and import in SOAP UI successfully. However while trying to call workflow using inbound webservice we experienced error on upsert step.
Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Upsert'.(SBL-BPR-00162)-No input integration object hierarchy found.(SBL-EAI-04398)
Further investigation of SRs on supportweb suggested that name of property should be SiebelMessage. One of the process property (For Account IO) was renamed to SiebelMessage and then we were able to upsert account data.
However as per requirements we need 2 process properties as integration objects (Account and Order) and we can have only 1 process property with name SiebelMessage.
In other words Siebel Workflow based webservice seem to have technical limitation of having only 1 process property of datatype Integration Object and type "In" or "In/Out"
Is there any workaround to accept more than ONE Integration Object in workflow through webservice??
SolutionMessage 1For the benefit of other users:
A workflow process can be built to meet the requirement with the following characteristics.
It has 2 process properties of type Integration Object, one for Account and the other one for Order with respective name AccountIO and OrderIO, not SiebelMessage, otherwise it will raise errors.
It contains at least 2 business services steps to upsert with the AccountIO and to upsert with the OrderIO.
After deploying this workflow process and defining an inbound web service to use it, SOAP UI can be used with the generated WSDL and request can be sent to populate both the Account and Order records.
The workflow process demonstrates that passing 2 Integration Objects to a web service is possible.
Moreover, the workflow process mode should be set to Service Flow to avoid running into errors.