Search This Blog

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

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)