Search This Blog

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.

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)