SBL-EAI-04057: Cannot map internal integration object ('%1') to output object ('%2').

Applies to:

Siebel System Software - Version: 8.1.1 [21112] - Release: V8
Information in this document applies to any platform.

Symptoms

Comments
--------
The customer created a custom ASI called X Kontakt to insert a contact. When the Insert method was called, the contact was created but the following error was returned to the external application:

dispatcherrortext: [0] Could not find 'Integration Object' named ''. This object is inactive or nonexistent.(SBL-DAT-00144) (0x750090) [1] Cannot map internal integration object ('X Kontakt Internal') to output object ('').(SBL-EAI-04057) (0x230fd9)
Content-Type: text/xml;charset=UTF-8
siebel-error-message-2: Cannot map internal integration object ('X Kontakt Internal') to output object ('').(SBL-EAI-04057)

Cause

Comments
--------
It appears that the application could not map an instance of the internal IO X Kontakt Internal into an instance of the external IO X Kontakt.

I compared the custom ASI with the standard ASI Siebel Contact and noted that, for the latter, Type = Input / Output for the argument Siebel Message, whereas, for the former, it is set to Input. Therefore, the custom ASI was not returning an IO instance.

Solution

Comments
--------
The web service call completed correctly after Type was set to Input / Output for the argument Siebel Message on the Insert method on the custom ASI.

Applies to:

Siebel Life Sciences CRM - Version: 8.1.1 SIA [21111] and later   [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms

We are building a Siebel Inbound interface for Oracle EBS integration. All the WSDLs are generated with string datatype and EBS team recommended to have datatype to be same the datatype of the field. Supportweb suggested that changing the datatype for Business Server Method Arg to 'Strongly Typed Integration Obj' should solve the problem.

Changing the Data Type property on the business service for all the methods arguments generated the following error message.

SBL-DAT-00144: Could not find '<?>' named '<?>'. This object is inactive or nonexistent.
SBL-DAT-00144: Could not find 'Integration Object' named ''. This object is inactive or nonexistent.
SBL-EAI-04057: Cannot map internal integration object ('') to output object ('').

Cause

Customer was exposing a ASI Business Service as Inbound Web Service.

ASI Business Services don't support Strongly Typed Integration Obj Data Type.

  The request CR#10600296 was created to address this issue.

Solution

As Workaround please consider the following suggestions:

1) Create Wrapper Business Service and set the input argument Siebel Message

Data Type = Strongly Typed Integration Obj
Integration Object = your IO.

2) Call the EAI Siebel Adapter from a WF process.

Define the Process Property as Strongly Typed Integration Obj

Publish the WF process as Inbound Web Service.

Regards
Oracle Technical Support

References

BUG:10600296 - ASI BUSINESS SERVICE DOES NOT SEEM TO SUPPORT DATA TYPE STRONGLY TYPED INTEGRATION OBJ