SBL-EAI-04108: Cannot convert Integration Object Hierarchy to XML Hierarchy.

Applies to:


Siebel System Software - Version: 7.8.2.6 SIA [19230] and later   [Release: V7 and later ]
Information in this document applies to any platform.

Product Release: V7 (Enterprise)

Version: 7.8.2.6 [19230] Com/Med

Database: Other (Please specify in Comments field)

Application Server OS: None - Not Implementing Web Server OS

Database Server OS: Sun Solaris 8



This document was previously published as Siebel SR 38-3495138641.

***Checked for relevance on 14-JAN-2010***


Symptoms


SBL-EAI-04019, SBL-EAI-04108, SBL-BPR-00162

A Workflow Process has been migrated from Siebel 6.0, with the following steps :-

1) Start

2) Query Database



Type:BS
BS Name:EAI Siebel Adapter
BS Method:Query
Input Arguments:
SearchSpec:"[Claimant.Id] = '" + [&Object Id] + "' AND [Claim.Id] = '" + [&ClaimId] + "'AND [WR.Id] = '" + [&WrId] + "'"
OutputIntObjectName:KEWESRD EKOS


3) Convert PropSet to XML (erroring step)
Input Arguments:



SiebelMessage=Interface Message (Process Property)
SiebelMessage.Custom1=Custom1 (Process Property)
SiebelMessage.Custom2=Custom2 (Process Property)
SiebelMessage.Custom3=Custom3 (Process Property)
SiebelMessage.Custom4=Custom4 (Process Property)
SiebelMessage.Custom5=Custom5 (Process Property)
 

The EAI XML Converter step errors with the the following message :-

"Error invoking service 'EAI XML Converter', method 'PropSetToXML' at step 'Convert PropSet to XML'.(SBL-BPR-00162)
--
Cannot convert Integration Object Hierarchy to XML Hierarchy.(SBL-EAI-04108)
--
Required message header property 'IntObjectName' is missing or invalid.(SBL-EAI-04019)


Cause


The error was re-produced, and change request Bug 10498747 was logged.



When trying to insert 4 or less dot notation elements to the SiebelMessage, it works fine by creating the elements on the same SiebelMessage that came as input.  But the error was found to arise when adding 5 or more elements to the original SiebelMessage using dot notation.  The error could be avoided using the Workflow Utilities Business Service (method Echo), but then the output contained two SiebelMessage elements, one with the input elements and another one with all the dot notation elements.


Solution


To workaround the issue with the limitation of dot notation elements, you need to separate them into groups of 4 or less elements on each workflow utilities step.  For example, if you have 7 elements to add, you should create at least 2 Workflow Utilities step, one with 4 and another one with 3.

Another possibility is to use a custom Business Service to add the elements on the SiebelMessage, and call this Business Service prior to calling the EAI XML Converter.



Keywords: Dot Notation, Workflow Utilities, IntObjectName




References


BUG:10498747 - [CR#12-104YEW0][FR#12-104YEX6] INPUT ARGUMENT NUMBER LIMIT WITH DOT NOTATION









Applies to:


Siebel System Software - Version: 7.8.2.6 SIA [19230] and later   [Release: V7 and later ]
Information in this document applies to any platform.

Product Release: V7 (Enterprise)

Version: 7.8.2.6 [19230] Com/Med

Database: Other (Please specify in Comments field)

Application Server OS: None - Not Implementing Web Server OS

Database Server OS: Sun Solaris 8



This document was previously published as Siebel SR 38-3495138641.

***Checked for relevance on 14-JAN-2010***


Symptoms


SBL-EAI-04019, SBL-EAI-04108, SBL-BPR-00162

A Workflow Process has been migrated from Siebel 6.0, with the following steps :-

1) Start

2) Query Database



Type:BS
BS Name:EAI Siebel Adapter
BS Method:Query
Input Arguments:
SearchSpec:"[Claimant.Id] = '" + [&Object Id] + "' AND [Claim.Id] = '" + [&ClaimId] + "'AND [WR.Id] = '" + [&WrId] + "'"
OutputIntObjectName:KEWESRD EKOS


3) Convert PropSet to XML (erroring step)
Input Arguments:



SiebelMessage=Interface Message (Process Property)
SiebelMessage.Custom1=Custom1 (Process Property)
SiebelMessage.Custom2=Custom2 (Process Property)
SiebelMessage.Custom3=Custom3 (Process Property)
SiebelMessage.Custom4=Custom4 (Process Property)
SiebelMessage.Custom5=Custom5 (Process Property)
 

The EAI XML Converter step errors with the the following message :-

"Error invoking service 'EAI XML Converter', method 'PropSetToXML' at step 'Convert PropSet to XML'.(SBL-BPR-00162)
--
Cannot convert Integration Object Hierarchy to XML Hierarchy.(SBL-EAI-04108)
--
Required message header property 'IntObjectName' is missing or invalid.(SBL-EAI-04019)


Cause


The error was re-produced, and change request Bug 10498747 was logged.



When trying to insert 4 or less dot notation elements to the SiebelMessage, it works fine by creating the elements on the same SiebelMessage that came as input.  But the error was found to arise when adding 5 or more elements to the original SiebelMessage using dot notation.  The error could be avoided using the Workflow Utilities Business Service (method Echo), but then the output contained two SiebelMessage elements, one with the input elements and another one with all the dot notation elements.


Solution


To workaround the issue with the limitation of dot notation elements, you need to separate them into groups of 4 or less elements on each workflow utilities step.  For example, if you have 7 elements to add, you should create at least 2 Workflow Utilities step, one with 4 and another one with 3.

Another possibility is to use a custom Business Service to add the elements on the SiebelMessage, and call this Business Service prior to calling the EAI XML Converter.



Keywords: Dot Notation, Workflow Utilities, IntObjectName




References


BUG:10498747 - [CR#12-104YEW0][FR#12-104YEX6] INPUT ARGUMENT NUMBER LIMIT WITH DOT NOTATION









Applies to:


Siebel System Software - Version: 7.8.2.6 SIA [19230] and later   [Release: V7 and later ]
Information in this document applies to any platform.

Product Release: V7 (Enterprise)

Version: 7.8.2.6 [19230] Com/Med

Database: Other (Please specify in Comments field)

Application Server OS: None - Not Implementing Web Server OS

Database Server OS: Sun Solaris 8



This document was previously published as Siebel SR 38-3495138641.

***Checked for relevance on 14-JAN-2010***


Symptoms


SBL-EAI-04019, SBL-EAI-04108, SBL-BPR-00162

A Workflow Process has been migrated from Siebel 6.0, with the following steps :-

1) Start

2) Query Database



Type:BS
BS Name:EAI Siebel Adapter
BS Method:Query
Input Arguments:
SearchSpec:"[Claimant.Id] = '" + [&Object Id] + "' AND [Claim.Id] = '" + [&ClaimId] + "'AND [WR.Id] = '" + [&WrId] + "'"
OutputIntObjectName:KEWESRD EKOS


3) Convert PropSet to XML (erroring step)
Input Arguments:



SiebelMessage=Interface Message (Process Property)
SiebelMessage.Custom1=Custom1 (Process Property)
SiebelMessage.Custom2=Custom2 (Process Property)
SiebelMessage.Custom3=Custom3 (Process Property)
SiebelMessage.Custom4=Custom4 (Process Property)
SiebelMessage.Custom5=Custom5 (Process Property)
 

The EAI XML Converter step errors with the the following message :-

"Error invoking service 'EAI XML Converter', method 'PropSetToXML' at step 'Convert PropSet to XML'.(SBL-BPR-00162)
--
Cannot convert Integration Object Hierarchy to XML Hierarchy.(SBL-EAI-04108)
--
Required message header property 'IntObjectName' is missing or invalid.(SBL-EAI-04019)


Cause


The error was re-produced, and change request Bug 10498747 was logged.



When trying to insert 4 or less dot notation elements to the SiebelMessage, it works fine by creating the elements on the same SiebelMessage that came as input.  But the error was found to arise when adding 5 or more elements to the original SiebelMessage using dot notation.  The error could be avoided using the Workflow Utilities Business Service (method Echo), but then the output contained two SiebelMessage elements, one with the input elements and another one with all the dot notation elements.


Solution


To workaround the issue with the limitation of dot notation elements, you need to separate them into groups of 4 or less elements on each workflow utilities step.  For example, if you have 7 elements to add, you should create at least 2 Workflow Utilities step, one with 4 and another one with 3.

Another possibility is to use a custom Business Service to add the elements on the SiebelMessage, and call this Business Service prior to calling the EAI XML Converter.



Keywords: Dot Notation, Workflow Utilities, IntObjectName




References


BUG:10498747 - [CR#12-104YEW0][FR#12-104YEX6] INPUT ARGUMENT NUMBER LIMIT WITH DOT NOTATION


תגובות

הוסף רשומת תגובה

פוסטים פופולריים מהבלוג הזה

FINS Data Transfer Utilities

תמונה
The best thing while working on siebel is you are never short of options. Recently we had requirement of updating a Service request from contact. Finally we did that using "EAI Siebel Adapter" business service. However during that time i came across another business service "FINS Data Transfer Utilities" popularly known as DTU business service. As i was not having prior knowledge of it going by the rule of not learning swimming lessons while drowning i decided not to go for it. Lately i have tried to explore this service and trust me it can do wonders. Here is a sample example update of Service Request from contact. We need to follow below steps in order to understand strength of this business service. 1 - Navigate to Site Map. Go to Administration - Application -> Data Map Administration tab. Create a new Record with following options: Name: Service Request Test Source Business Object: Contact Destination Business Object: Service Request Here the source business
המשך לקרוא

SBL-BPR-00191: The rowId of the active row of the primary buscomp '%1', '%2', does not match the Primary Id

Applies to: Product Release: V7 (Enterprise) Version: 7.5.3 [16157] ESN Database: Oracle 9.2.0.2 Application Server OS: Microsoft Windows 2000 Server SP 3 Database Server OS: Microsoft Windows 2000 Server SP 3 This document was previously published as Siebel SR 38-1386997031. Symptoms SBL-BPR-00191 We have a error with a workflow. This WF is excuted by policy when a particular activity is closed. The WF Business Object is 'Action'. Inside this WF, there is a subprocess that invokes a Business Service that creates a new activity. In a second subprocess, the region Id of this new activity is updated using the standar update method funcionality of Siebel workflow process. Error processing Siebel Operation for: Business Object 'Action' Business Component 'Action' Primary Id ''1-5NEI6' Operation 'Insert'(SBL-BPR-00100) -- The rowId of the active row of the primary buscomp 'Action', '1-4SNCV', does not match the Prima
המשך לקרוא

Profile Attributes and Open UI

תמונה
Yes, Profile Attributes! As the ever attentive, up-to-date Siebel CRM expert that you are when you read this, you know that in Siebel Open UI (since version 15), it is no longer allowed/supported to  set  Profile Attributes from browser-side script. But  getting  them is not a problem, since the  GetProfileAttr  function works perfectly fine. Recently I found a few vanilla Profile Attributes that came quite handy in my work in Open UI JavaScript: Navigation Type : stores the navigation type such as "NAVIGATION_TAB" ActiveViewName : does what it says on the tin IsOpenUI : returns "1" when the application runs in Open UI Is SUI Theme : when "TRUE", the application theme is Synergy (aka SUI) Position:  returns the currently active position Primary Responsibility Name : guess what this one is… Profile Image : returns the URL of the user's profile image Org.Name : returns the name of the user's organization Here's a sample line of
המשך לקרוא