Search This Blog

SBL-EAI-04127: Element with XML tag '%1' is not found in the definition of EAI Integration Component '%2'

Applies to: Siebel System Software - Version: SIA [16192] - Release: V7
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: [16192] FIN Fin Svcs
Database: IBM DB2/UDB 8.1 FixPack 1S
Application Server OS: Microsoft Windows 2000 Advanced Server SP 4
Database Server OS: IBM AIX 5L 5.1

This document was previously published as Siebel SR 38-3179740701.
SymptomsAn outbound web service has been amended to include a new field (an array), and the new wsdl was imported to Siebel to generate the new Integration Objects and proxy Business Service. However, when the web service was invoked, an error was generated as follows :-

ObjMgrLog Error 4 2006-10-19 15:35:58 (SBL-EAI-04127) Element with XML tag 'cdhpList' is not found in the definition of EAI Integration Component 'cdhpList'

ObjMgrBusServiceLog InvokeMethod 4 2006-10-19 15:35:58 Business Service 'EAI Integration Object to XML Hierarchy Converter' invoke method 'XMLHierToIntObjHier' Execute Time: 0.033 seconds.

ObjMgrLog Error 4 2006-10-19 15:35:58 (SBL-EAI-04316) Error while processing argument findMemberDetailResponse for operation findMemberDetail
CauseFrom the wsdl, the element cdhpList is implemented an array :-

<element name="cdhpList" nillable="true" type="impl:ArrayOf_tns1_CDHPSummary"/>

And this array was defined as follows :-

<complexType name="ArrayOf_tns1_CDHPSummary">
<element maxOccurs="unbounded" minOccurs="0" name="item" type="tns1:CDHPSummary"/>

From this, the parent element name was “cdhpList”, and the child element name was “item”. But in the returned SOAP document, both the parent and child element were using tag “cdhpList” :-


Siebel was unable to accept this – it was expecting the child data to be returned within element <item>, per the wsdl definition.
SolutionThe customer discovered that the web service had an "internal Axis serialization problem that only shows up with non-Java clients".
After ensuring the returned SOAP response contained the expected structure (as expected from the given wsdl) the error was resolved.

Applies to: Siebel System Software - Version: SIA [19224] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Professional)
Version: [19224]
Database: Oracle
Application Server OS: Sun Solaris 10
Database Server OS: HP-UX 11i

This document was previously published as Siebel SR 38-3507237323.
SymptomsA custom Integration Object (based on Account) is used in a UCM implementation. An inbound web service is invoked, which uses this Integration Object. The requirement is to inactive one Integration Component Field ('Sector') in the Integration Object, even though the external system continues to send this field.

The following error is returned :-

<?xml version="1.0" encoding="UTF-8"?>
<?Siebel-Property-Set EscapeNames="false"?>
<CRMML ErrorMessage="Error invoking service 'UCM Converter', method 'XMLPropSetToPropSet' at step 'Convert Request In'.(SBL-BPR-00162)
Element with XML tag 'Sector' is not found in the definition of EAI Integration Component 'Account'(SBL-EAI-04127)" ErrorCode="(SBL-BPR-00162)--IDS_EAI_ERR_INTOBJHIER_ELEM_UNKN"/>
CauseThe following is documented in the Siebel Master Data Applications Reference for Industry Applications > Configuring Siebel Master Data Applications > Configuring Siebel Master Data Application Features > About Siebel Master Data Applications Integration Services :-
"The UCM Converter uses the hierarchy represented in the UCM integration object to guide the message through the converting process. If the integration object instance receives elements that do not have a definition defined in the integration object definition, the converter errors out. If you expect such a situation, you can set the Ignore Undefined XML Tag parameter on the user property of the corresponding integration object.

NOTE: This user property is created by the wizard and is set to Y. You can turn it off if you want the converter to error out. "
However, even with the Ignore Undefined XML Tag user property added to the Integration Object, the error persisted.
SolutionIn Siebel Bookshelf, this Integration Object user property is wrongly mentioned as "Ignore Undefined XML Tag". It should be "Ignore Undefined XML Tags" instead of "Ignore Undefined XML Tag".

Bug 12-1M4CTHH has been raised to address the documentation issue.

Applies to: JD Edwards EnterpriseOne Tools - Version: 8.97 - Release: 8.97
Information in this document applies to any platform.
SymptomsCan I synch a CRMOD Account to JDE AFTER the CRMOD Account is created?
1) Created CRMOD Account - did not turn synch flag on
2) Update CRMOD Account, turned synch flag to 'Synch On'.
3) Record did not synch
4) Is this intended functionality?
CauseThis is standard functionality provided according to the documentation found in Implementation guide.


The UpdateCustomerCRMODReqABCSImpl receives an Account Update integration event from CRM On Demand. The service converts the event message from CRM On Demand format to UpdateCustomerPartyEBM format and invokes the UpdateCustomerPartyEBS.

In cases where the account has not been synchronized to JD Edwards EnterpriseOne before, the service queries the CRM On Demand system to fetch full information of the account, including account addresses. The service then converts the message to UpdateCustomerpartyEBM format and invokes the CreateCustomerPartyEBS to enable the JD Edwards EnterpriseOne system to create a new account, including addresses if necessary.

There is one asynchronous one-way operation provided by this interface service:

What was found was that within the failed BPEL process UpdateCustomerCRMODReqABCSImpl the following message

Error in evaluate <from> expression at line "219". The result is empty for the XPath expression : "/ns3:ListOfAccount/ns3:Account/ns3:plSync_Status".

This indicates that the BPEL process could not resolve the sync status.

Once this was corrected, another error was found in the related process - AccountWSEndPointCRMOnDemand. The error shown in this process was

Element with XML tag 'stRelated_Account_Id' is not found in the definition of EAI Integration Component 'Account'(SBL-EAI-04127)

If the bpel process can't resolve the sync status then it will not know what to do next.
SolutionFirst customer needed to check and verify the Picklist for Sync Status was set up correctly and the Workflow for Update-Account was defined correctly.

The second issue was regarding the invalid tag name 'rtRelatedAccountId'.

This is a custom field setup during implementation. Documentation states to create 'Related Account ID'. It should read 'Related Account Id'. To correct this field do the following steps.

1. Go into CRMOD > Admin > Customization > Account > Account field setup
2. Click on the Rename Fields button.
3. Click on the Advanced button.
4. Locate the customer field for Related Account ID.
5. Change the value for the Integation Tag to
6. Save and exit.
7. Logout of CRMOD
8. Go to the middleware database and locate the table SIEBELODSESSIONPOOL under the BPEL schema.
9. Do a SQL change on the table to update the SESSION_ID field with 'NULL' value.
10. Commit changes.

Login to CRMOD and test again.

No comments:

Post a Comment