Error while mapping file attachment: SBL-EAI-04058: Source expression generated attachment ID '...' but the corresponding attachment cannot be found. (Doc ID 972381.1)
APPLIES TO:
Siebel CRM - Version 7.8.2 [19213] and later
Information in this document applies to any platform.
SYMPTOMS
Following error will be reported by EAI Data Transformation Engine (Intgeraiton Object Declarative Data Mapper) when mapping file attachment (copying file content) from improperly configured / provided source Integration Component Field;
SBL-EAI-04058: Source expression generated attachment ID '...' but the corresponding attachment cannot be found.
CAUSE
The field type of the source (and also traget) Integration Component that (the field) provide the file attachment content has to be "DTYPE_ATTACHMENT".
The error occurs if it is set to "DTYPE_TEXT" (that may be default setting provided while creating the Integration Object from XSD schema using Siebel Tools Wizard.
Also there are alo following requirements for the text (VALUE) of the XML element in the input XML document where the source integration object is instantiated from:
- it has to be valid base64 encoded text
- it must not contain leading line breaks (<CR> and/or <LF>) and any other characters which are not part of base64 encoded text.
- the entire text can be well included as the CDATA block: <![CDATA[...]]>
Finally the instance of Integration Object, instantiated from the XML document with file attachment,
should be created using the "XMLDocToIntObjHier" method of the "EAI XML Converter" Business Service.
This method, invoked explicitly or implicitly (e.g. via the "ReadEAIMsg" method of the "EAI XML Read from File" Business Service or via EAI Data Handling named subsystem)
uses definition of the Integration Object to properly recognize file attachment item, decoded it into a binary file content and make it be ready
for followed EAI operations (Data Mapping and EAI Siebel Adapter methods etc).
SOLUTION
The error did not occur after the Data Type property of source IC field was changed to DTYPE_ATTACHMENT.
Source:
https://support.oracle.com/ > Doc ID 972381.1
Siebel CRM - Version 7.8.2 [19213] and later
Information in this document applies to any platform.
SYMPTOMS
Following error will be reported by EAI Data Transformation Engine (Intgeraiton Object Declarative Data Mapper) when mapping file attachment (copying file content) from improperly configured / provided source Integration Component Field;
SBL-EAI-04058: Source expression generated attachment ID '...' but the corresponding attachment cannot be found.
CAUSE
The field type of the source (and also traget) Integration Component that (the field) provide the file attachment content has to be "DTYPE_ATTACHMENT".
The error occurs if it is set to "DTYPE_TEXT" (that may be default setting provided while creating the Integration Object from XSD schema using Siebel Tools Wizard.
Also there are alo following requirements for the text (VALUE) of the XML element in the input XML document where the source integration object is instantiated from:
- it has to be valid base64 encoded text
- it must not contain leading line breaks (<CR> and/or <LF>) and any other characters which are not part of base64 encoded text.
- the entire text can be well included as the CDATA block: <![CDATA[...]]>
Finally the instance of Integration Object, instantiated from the XML document with file attachment,
should be created using the "XMLDocToIntObjHier" method of the "EAI XML Converter" Business Service.
This method, invoked explicitly or implicitly (e.g. via the "ReadEAIMsg" method of the "EAI XML Read from File" Business Service or via EAI Data Handling named subsystem)
uses definition of the Integration Object to properly recognize file attachment item, decoded it into a binary file content and make it be ready
for followed EAI operations (Data Mapping and EAI Siebel Adapter methods etc).
SOLUTION
The error did not occur after the Data Type property of source IC field was changed to DTYPE_ATTACHMENT.
Source:
https://support.oracle.com/ > Doc ID 972381.1
Comments
Post a Comment