Siebel eConfigurator - Version: 22.214.171.124 SIA  and later [Release: V8 and later ]
Information in this document applies to any platform.
Checked for Relevance on 02-05-2010
A product was exported to an xml file. When this product was tried to be imported, the error SBL-EAI-04264 occurred.
Internet Explorer settings caused the generated xml file to contain the string "f4240" at the beginning. This made the file incorrectly structured for the parser.
Unchecking the following properties in Internet Explorer resolved the issue for the customer.
Use HTTP1.1 through proxy connections
Siebel System Software - Version: 126.96.36.199  and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
***Checked for relevance on 10-Nov-2010***
Product Release: V7 (Enterprise)
Version: 188.8.131.52 
Database: Oracle 184.108.40.206
Database Server OS: IBM AIX 5L 5.2
This document was previously published as Siebel SR 38-3216568551.
Requirement is to be able to Export Accounts from the UI as a CSV file, manipulate the details with Excel, save the excel file as XML then import the accounts using EAI workflow (calling EAI XML Read From File then EAI Siebel Adaptor).
In order to save the excel file as XML, an XSD was generated on a relevant Integration Object in tools (with a Siebel Envelope).
However, the import fails saying I dont have a Siebel Envelope :-
"ObjMgrBusServiceLog Error 1 0 2006-12-07 11:50:04 (eaixmlprtsvc.cpp (285)) SBL-EAI-04264: 'EAI XML Read from File' service with method 'ReadEAIMsg' failed while processing XML from file 'c:\AccountOutput.xml'.
PrcExec PropSet 4 0 2006-12-07 11:50:04 Error invoking service 'EAI XML Read from File', method 'ReadEAIMsg' at step 'Import XML file'.(SBL-BPR-00162)
'EAI XML Read from File' service with method 'ReadEAIMsg' failed while processing XML from file 'c:\AccountOutput.xml'. (SBL-EAI-04264)
If the SiebelMessage header is not present, either an Integration Object Name or an Integration Object Name Lookup RuleSet should be specified in order to convert the XML Document to a Siebel Message.(SBL-EAI-04109)"
In the XML produced by Excel, SiebelMessage has been prefixed 'ns1:'.
This was resolved by setting the "StripNamespace" parameter to "True" in the business service 'EAI XML Read from File' called by workflow process.
For reference, another possible approach is using the standard Business Service 'Read CSV File' which can be used to achieve the above requirement.
- Export the accounts in the CSV file
- Use Read CSV File BS, which reads from CSV file and converts to property set
- Write this property set to XML using EAI XML Write to File BS
Use the above steps in workflow so you have the XML which you would like to modify further
- Once the XML is updated, use the EAI Siebel Adapter to import the accounts using the custom Integration Object.
@ reviewed 08JUN09, similar to 730021.1, but keeping
Product Release: V7 (Enterprise)
Version: 220.127.116.11 
Database: Oracle 18.104.22.168
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: Sun Solaris 8
This document was previously published as Siebel SR 38-1114352474.
I'm trying to import my workflow processes into a new environment and am running into errors on import of some of the workflows. I've pretty much figured out that it's due to the workflows containing subprocesses with names that are too long. I'd like to know exactly how many characters can a subprocess name be? All the SR's that I've found on supportweb only say they should be "small length", such as SR # 38-947296651. Can you provide the specific length please?
For the benefit of other customers:
In version 7.5.x, the Subprocess name used within a Workflow Process should be up to 60 characters in length; otherwise importing an exported XML file for the process will fail with an error similar to the following:
'EAI XML Read from File' service with method 'ReadEAIMsg' failed while processing XML from file 'c:\sea752\client\temp\2300_2296_NOVL - 0 Days to Renew Premium Email Notification Process.xml'.
Change Request#12-E9Z0DW exists to address this product defect and the new releases should be modified to hold up to 100 characters. CR# 10469170 has been logged to address this documentation enhancement.
Post a Comment