ITCanopy

Error: Error invoking service 'EAI Data Transformation Engine', method 'Execute' at step 'Map'.(SBL-BPR-00162)--Data Transform Error. No entry for lookup key in EAI Value Map.   Key:   'Administration Fees'   Type: 'External-Siebel'   Direction: 'Siebel Outbound'(SBL-DAT-00102) SBL-DAT-00102: Data Transform Error. No entry for lookup key in EAI Value Map. Key: '%1' Type: '%2' Direction: '%3' Reason: Value is not defined in EAI Value Map for Outbound direction. External system have different value for "Administration Fees". If this was working before that means external entity have changed the value in their system. Below details will help and guide you to resolve this error and understand the EAI Value Map. EAI Value Map: This is similar to List of Values but defined and use is different. Use case is when integrating with external system most likely external system will have different list of values. S...

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

1: Error Join in business component definition '%1' has source fields that come from tables '%2' and '%3' (SBL-DAT-00452). 2: Steps on which error occurred 2.1. In Business Component created new Join by providing table, alias and outer join flag checked. 2.2. In Join Specification created new record provided the destination column and source field (field is based on base table of the business component). 2.3. In Join Specification created new record provided the destination column and source field (field is based on other table, added using join). 2.4. Created new field based on the new join and exposed in applet. 2.5. Compiled the objects and open Siebel application. 2.6. When navigate to view Siebel returned the above error. 3: Findings and Conclusion: When inspecting the Object Manager (Public Sector) logs could not able to find the exact reason but just the above error. When checked on Oracle Docs found out that documentation is saying that in Join Specific...

Error: No user key can be used for Integration Component instance 'IC NAME'.(SBL-EAI-04397) Cause: In this case the behavior was encountered on Siebel CRM 8.1 release, where customer had another definition of the same IO deployed in the run time database. The IO deployed in the run time database was later amended to incorporate some changes in the user key fields. Next 'EAI Siebel Adapter' was invoked with a SiebelMessage corresponding to the amended/latest IO definition, which was compiled in the srf but not re-deployed in the runtime database. Since in version 8.1, IOs are first read from the cache and then from the SRF, this made 'EAI Siebel Adapter' to ignore the amended IO definition and throw the user key error. From experience gathered, it is seen that similar incidents can often arise when the "Deploy the Integration Object" checkbox is selected while creating an IO (using the EAI Siebel Wizard). In order to avoid such incidents due to inconsis...

Error: The ability to delete records is not available in this screen or applet.(SBL-DAT-00278)    Reasons: The error is thrown in the following case: 1. The No Delete property may be set to TRUE for one of the following repository objects; business component, applet, MVL, Link. 2. The record may be set to read-only by the business component user properties. 3. For business components that have the state model activated, the No Delete parameter may be set to TRUE for the corresponding State Model under Administration - Application > State Models > States.  Source: Oracle Community

Error: We're sorry, but one or more limits for the requested action have been exceeded. Reason: You can only create a maximum of 100 posts per day. If u have multiple blogs same limit apply for all. Can not create more than 100 posts from all blogs collectively.

Error: The workflow/task engine cannot determine a next step while executing process definition 'Workflow Name'. The last step that it executed was 'Workflow Step Name'.(SBL-BPR-00176) Reason: This is a problem with the connectors attached to your step 'Workflow Step Name'. Solution: Delete the incoming and outgoing connectors of this step. Save the workflow. Add the connectors again.

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

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

Siebel is returning below error, when invoking Outbound Web Service through Workflow. Error Code (SBL-BPR-00162)--IDS_EAI_WS_OD_RESPONSE_EXPECTED Error Message Error invoking service 'Business Service', method 'Method Name' at step 'Workflow Step Name'.(SBL-BPR-00162)--Operation 'Method Name' is expecting a response but no response was received.(SBL-EAI-04311) You should be getting above error while invoking Outbound Web Service through Workflow. Reason: Web Service might be unavailable at the host location. The machine on which Siebel Web Server is installed is not able to access the end point URL. Solution: Check with Vendor. Add entry of End Point URL in Windows Host file or exclude from Firewall and Antivirus.