SBL-EAI-04109: If the SiebelMessage header is not present, either an Integration Object Name or an Integration Object Name Lookup..................................

Applies to:


Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI

Version:Siebel 8.1

Purpose


This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.

Scope


This document is informational and intended for any user.

SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.


Explanation


In order to convert an XML hierarchy to an integration object instance, Integration Object Hierarchy Converter service must know the name of the integration object. The integration object name can come from either the SiebelMessage header property IntObje

Corrective Action


Provide an integration object name in one of the specified ways.









Applies to:


Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI

Version:Siebel 8.1

Purpose


This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.

Scope


This document is informational and intended for any user.

SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.


Explanation


In order to convert an XML hierarchy to an integration object instance, Integration Object Hierarchy Converter service must know the name of the integration object. The integration object name can come from either the SiebelMessage header property IntObje

Corrective Action


Provide an integration object name in one of the specified ways.









Applies to:


Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI

Version:Siebel 8.1

Purpose


This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.

Scope


This document is informational and intended for any user.

SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.


Explanation


In order to convert an XML hierarchy to an integration object instance, Integration Object Hierarchy Converter service must know the name of the integration object. The integration object name can come from either the SiebelMessage header property IntObje

Corrective Action


Provide an integration object name in one of the specified ways.









Applies to:


Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI

Version:Siebel 8.1

Purpose


This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.

Scope


This document is informational and intended for any user.

SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.


Explanation


In order to convert an XML hierarchy to an integration object instance, Integration Object Hierarchy Converter service must know the name of the integration object. The integration object name can come from either the SiebelMessage header property IntObje

Corrective Action


Provide an integration object name in one of the specified ways.









Applies to:


Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI

Version:Siebel 8.1

Purpose


This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.

Scope


This document is informational and intended for any user.

SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.


Explanation


In order to convert an XML hierarchy to an integration object instance, Integration Object Hierarchy Converter service must know the name of the integration object. The integration object name can come from either the SiebelMessage header property IntObje

Corrective Action


Provide an integration object name in one of the specified ways.









Applies to:


Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI

Version:Siebel 8.1

Purpose


This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.

Scope


This document is informational and intended for any user.

SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.


Explanation


In order to convert an XML hierarchy to an integration object instance, Integration Object Hierarchy Converter service must know the name of the integration object. The integration object name can come from either the SiebelMessage header property IntObje

Corrective Action


Provide an integration object name in one of the specified ways.








Applies to:


Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI

Version:Siebel 8.1

Purpose


This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.

Scope


This document is informational and intended for any user.

SBL-EAI-04109: If the SiebelMessage header is not present, either an integration object name or an integration object name lookup rule set should be specified in order to convert the XML document to a Siebel message.


Explanation


In order to convert an XML hierarchy to an integration object instance, Integration Object Hierarchy Converter service must know the name of the integration object. The integration object name can come from either the SiebelMessage header property IntObje

Corrective Action


Provide an integration object name in one of the specified ways.

תגובות

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

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

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 ...
המשך לקרוא

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...
המשך לקרוא

SBL-SVC-00150

Applies to: Siebel CRM - Version: 7.5.3 [16157] and later   [Release: V7 and later ] z*OBSOLETE: Microsoft Windows 2000 Product Release: V7 (Enterprise) Version: 7.5.3 [16157] Database: IBM DB2/UDB 7.2 Application Server OS: Microsoft Windows 2000 Advanced Server SP 2 Database Server OS: IBM AIX 4.3.3 This document was previously published as Siebel SR 38-1153677971. Symptoms SBL-SVC-00150In callcenter (development environment) Group News administration > All News, when the ‘Status’ field of a news story is changed from ‘Submitted’ to ‘Completed’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Completed’. Rule validation failed: ‘[Total Approvers] = 0’ (SBL-SVC-00150) When the status field of a news story is changed from ‘Submitted’ to ‘Pending Approval’, the following error pops up. You cannot change the current field’s value from ‘Submitted’ to ‘Pending Approval’. R...
המשך לקרוא