Skip to main content

Posts

Showing posts with the label Data Map Editor

No user key can be used for the Integration Component instance 'IO Name' error in Siebel

Error: Error invoking service 'EAI Siebel Adapter', method 'Update' at step 'Workflow Step Name'.(SBL-BPR-00162)--No user key can be used for the Integration Component instance 'Integration Component Name'.(SBL-EAI-04397) Steps to Reproduce: Created new Integration Component in Siebel Tools and set Id field (system default) as the Integration Component User Key. Created Data map in Siebel Client. Added a query step in workflow and get the response in Siebel Message process property. (EAI Siebel Adapter, Query) Added Data Map step and used above response. (EAI Data Transformation Engine,Execute) Added Update step and used the response of Data Map step. (EAI Siebel Adapter, Update) Deployed the workflow and run. On Run received the above error. Reason & Solution: From the Workflow instance logs got the Siebel Message value (from Step 3 and 4) and on inspection found out that Id tag was missing. When checked and compare the Id field in Integration compo...

InvokeServiceMethod in EAI Data Mapper Returns Error " SBL-DAT-00610: Access denied to invoke business service 'Custom Service' " (Doc ID 538237.1)

APPLIES TO: Siebel System Software - Version 7.7.1 SIA [18306] and later Siebel CRM - Version 7.7.1 [18306] and later z*OBSOLETE: Microsoft Windows 2000 Product Release: V7 (Enterprise) Version: 7.7.1 [18306] Pub Sect Database: Oracle 9.2.0.4 Application Server OS: Microsoft Windows 2000 Advanced Server SP 4 Database Server OS: IBM AIX 5100-03 This document was previously published as Siebel SR 38-1409242127. **Checked for relevance on 28-JUN-2016*** SYMPTOMS In Siebel version 7.7, a data map has been created (based on a working Siebel 7.5.3 version mapping). One of the mappings invokes a custom business service using expression InvokeServiceMethod.  The following is inclued in a Source Expression in the EAI Data Mapper :- InvokeServiceMethod("Custom Service", "GetUserAccountId", "loginName=" + [submitter], "Account Id") When the mapper service ('EAI Data Transformation Engine') is executed, the following error is r...

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 ...

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 instantiat...