siebel

Disclaimer: This post may not appeal EIM war horses but might be of some interest to newbies in EIM. There are two types of Data, the one you look up and the one you make up. EIM is the technique which is used for the later type. As per siebel Bookshelf "Siebel EIM manages the exchange of data between Siebel database tables and other corporate databases". The EIM process constitue of two major steps: 1 - The data is first copied from external source(external table, csv , excel) into the interface tables. 2 - This data from the interface tables is then loaded into predefined destination columns in the base tables using the configuration file. This configuration file, popularly known as ifb file, hosts the magical words which can be used to import, update, delete, extract, merge data. A more detailed list of paramters is available in bookshelf. One of the interesting parameters in the list is "SESSION SQL" which can perform operations after the EIM execution. This can

This is an extension to my previous post regarding Hierarchy Extraction which compares different ways to extract property sets. I have quoted in the earlier post regarding the length limitation(75 characters) of Workflow Utilities echo method using dot notation. But Siebel never run out of altervatives and each one gives me something different. In order to overcome the length limitation of the dot notation one can make use of "Aliases" which lasts upto 255 characters. Workflow Processes can have Process Properties of type "Alias" (ignorant me). Basically this data type acts as a pointer to a specific attribute inside a Property Set. So in order to fetch Sr Number or Account Id, mentioned in previous post, we have to define two process properties of data type "Alias" with Default value as below SR Number: SiebelMessage/ListOfService/Service Request/@SR Number Activity Id: SiebelMessage/ListOfService/Service Request/ListOfAction/Action/@Activity Id In the w

Whether we can repeat browser side capabilities via server side, like Alert/Prompt, always charms any developer. Server side "Alert" is beautifully explained on the siebel Impossible scriptless challenge using "LS SubjectVisits Service" business service with "ShowConfirmationDlg" method. Recently i was asked to implement Prompt sort of functionality using server side code. After some hits and lots of misses i came up with not so beautiful solution but it worked. Lets consider a scenario where on click of "Summary" button, code should check the status of Service Request if it is "open" then it should prompt user to enter notes and capture these notes and put it in the Summay of service request. The solution is blend of List of Value BC and pop up applet. I found a business service "SLM Save List Service"(thanks to Google again...wonder what life would have been w/o Google...) which could be used to invoke a popup applet from s

Hey Folks, Here is the first of the many Siebel power user series to come. Just recently discovered a few cool features in Siebel from an end user perspective. Many a times the user is required to update multiple records of data based on a condition, that the user would normally not know how to execute simultaneously. For instance, I recently had to update a few(not really) activities in Siebel under a condition where the activity had just one contact associated to it. How would an end user go about making this change? Lets discuss two such "Good to knows" in the following scenario The Requirement - Lets say you have to update the status of 100 or so activities which do not have more than one contact. The Trick - Go to the Activities applet, and use the below query on the Contacts field Count("Contact") > 1 Note: Contact is the MVL used in the Contact MVG This will give you all activities with more than one contact association. Now, lets update the Type of the A

Security is like superstition. Hits are always counted while misses doesn't. Recently i was asked to enhance security measure of our siebel ebusiness applications by tracking the IP address along with the login of the client. The first thought that came to mind was @#$@#$@# but then again why-to-fear-when-google-is-here happened. I found a lesser heard OOB business service which returns the session variables, cookies information and many more useful stuff. "Web Engine HTTP TXN” business service can do the trick for you. Details of this BS is avialable on the support web in "TECHNICAL NOTE 317". "GetAllServerVariables" and "GetServerVariables" are key methods here for fetching the Login and IP address respectively. I followed below steps in order to capture the IP address of the logged in user. 1 - Create a action set which calls a workflow. In this workflow we will have two steps: First step calls " Web Engine HTTP TXN " with method &qu

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50187: The file reference '%1' does not exist. Scope This document is informational and intended for any user. SBL-EAI-50187: The file reference '%1' does not exist. Explanation The specified file cannot be found on the file system. Corrective Action Check whether the specified file exists and whether the user temporary directory is defined and accessible. Applies to: Siebel System Software - Version: 8.0 [20405] and later [Release: V8 and later ] z*OBSOLETE: Microsoft Windows Server 2003 Product Release: V8 (Enterprise) Version: 8.0 [20405] FRA Pub Sect Database: Microsoft SQL Server 2005 Application Server OS: Microsoft Windows 2003 Server Database Server OS: Microsoft Windows 2003 Server This document was previously publi

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50177: Error getting the size of file reference '%1' Scope This document is informational and intended for any user. SBL-EAI-50177: Error getting the size of file reference '%1' Explanation Cannot get the size of a temporary file. Corrective Action Check whether the specified file exists and is readable.

Applies to: Siebel CRM - Version: 8.0 [20405] to 8.1.1 [21112] - Release: V8 to V8 Information in this document applies to any platform. ***Checked for relevance on 23-NOV-2010*** Symptoms The "Error writing to file reference 'C:\sba80\siebsrvr\temp\1-18RZ0U_0.tmp' (SBL-EAI-50176)" error reported by the "IntObjHierToXMLDo" method of the "EAI XML Converter", broke the integration process, worked well before. Cause The "temp" folder's file system on the affected Siebel Server was likely lack of free space. Since Siebel CRM Release 8.0, the internal memory management mechanism has been significantly improved for optimized RAM usage. The EAI XML Converter BS and other EAI business services which are manipulating with property set hierarchies and XML Documents are using now the "temp" sub-folder of the Siebel Product installation root to store temporary XML file references if the parsed or produced document size exceeds the 50Kb

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50175: Error reading from file reference '%1'. Scope This document is informational and intended for any user. SBL-EAI-50175: Error reading from file reference '%1'. Explanation Unable to read from temporary file. Corrective Action Check whether the specified file exists and is readable.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50174: Error deleting file reference '%1'. Scope This document is informational and intended for any user. SBL-EAI-50174: Error deleting file reference '%1'. Explanation Error deleting temporary file. Corrective Action Check to see if a user temporary file exists.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50173: Error creating file reference '%1'. Scope This document is informational and intended for any user. SBL-EAI-50173: Error creating file reference '%1'. Explanation Error creating temporary file. Corrective Action Check to see if the user temporary directory is defined and accessible.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50172: The workflow process '%1' is either not activated or its status is not ""Completed"", and therefore cannot be exposed as a Web Service. Scope This document is informational and intended for any user. SBL-EAI-50172: The workflow process '%1' is either not activated or its status is not ""Completed"", and therefore cannot be exposed as a Web Service. Explanation The workflow may not be activated or completed. Corrective Action Make sure the workflow is completed and activated.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50171: The business service '%1' is not active. You must activate it. Scope This document is informational and intended for any user. SBL-EAI-50171: The business service '%1' is not active. You must activate it. Explanation The business service is not active. Corrective Action Activate the business service first.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50170: The business service % does not contain any method that can be exposed. Scope This document is informational and intended for any user. SBL-EAI-50170: The business service % does not contain any method that can be exposed. Explanation The business service does not contain any method that can be exposed. Corrective Action Verify that the business service to be exposed as a Web service contains methods.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50169: Select the methods you want to expose. Scope This document is informational and intended for any user. SBL-EAI-50169: Select the methods you want to expose. Explanation No method is selected. Corrective Action Select at least one method.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50168: The following selected methods either have argument(s) of unsupported type hierarchy without an Integration Object specified or do not have any argument configured. They are not supported in Siebel inbound web service: %s. Please unselect them to proceed. Scope This document is informational and intended for any user. SBL-EAI-50168: The following selected methods either have argument(s) of unsupported type hierarchy without an Integration Object specified or do not have any argument configured. They are not supported in Siebel inbound web service: %s. Please unselect them to proceed. Explanation Some methods either have argument(s) of unsupported type hierarchy without an Integration Object specified or do not have any argument conf

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50167: The selected workflow process contains hierarchy type process properties without having the integration object name specified. Scope This document is informational and intended for any user. SBL-EAI-50167: The selected workflow process contains hierarchy type process properties without having the integration object name specified. Explanation The selected workflow process contains hierarchy type process properties without having the integration object name specified. Corrective Action Specify an integration object name for process properties of hierarchy type.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50166: The Web Service URL is not valid. Replace and with the appropriate values. Scope This document is informational and intended for any user. SBL-EAI-50166: The Web Service URL is not valid. Replace and with the appropriate values. Explanation The Web Service URL is not valid. Corrective Action Enter a valid URL for the Web Service.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50165: The operation name '%1' is not unique. Please enter a new one or use the one generated for you. Scope This document is informational and intended for any user. SBL-EAI-50165: The operation name '%1' is not unique. Please enter a new one or use the one generated for you. Explanation The operation name is not unique. Corrective Action Enter a new name or use the name generated for you by the wizard.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50164: Enter an operation name for the Web Service. Scope This document is informational and intended for any user. SBL-EAI-50164: Enter an operation name for the Web Service. Explanation The operation name is missing. Corrective Action Enter an operation name.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50163: Enter a valid path for the WSDL file. Scope This document is informational and intended for any user. SBL-EAI-50163: Enter a valid path for the WSDL file. Explanation A valid path for the WSDL file is missing. Corrective Action Enter a valid path for the WSDL file.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50162: WSDL cannot be generated for web service '%1'. The Workflow Process '%1' may not have been activated and caused the WSDL generation to fail. Scope This document is informational and intended for any user. SBL-EAI-50162: WSDL cannot be generated for web service '%1'. The Workflow Process '%1' may not have been activated and caused the WSDL generation to fail. Explanation The Workflow is not activated. Corrective Action Activate the Workflow Process before generating the WSDL file. SBL-EAI-50162: WSDL cannot be generated for web service '%1'. The Workflow Process '%1' may not be activated and caused the WSDL generation to fail.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50161: The business service or workflow process '%1' has already been deployed as a Web Service of namespace '%2'. Scope This document is informational and intended for any user. SBL-EAI-50161: The business service or workflow process '%1' has already been deployed as a Web Service of namespace '%2'. Explanation The business service or workflow has already been deployed in the same namespace. Corrective Action Delete the existing Web Service before trying to deploy it again.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50160: Cannot find integration component field definition (Integration Component '%1', Integration Object '%2') corresponding to the property '%3' (Property Set Type '%4') Scope This document is informational and intended for any user. SBL-EAI-50160: Cannot find integration component field definition (Integration Component '%1', Integration Object '%2') corresponding to the property '%3' (Property Set Type '%4') Explanation A property set property was found that does not correspond to a known integration component field. Corrective Action Check that the specified property in the property set corresponds to an integration component field in the integration component definition.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50157: Error converting property set hierarchy to integration object hierarchy. Cannot find integration component corresponding to property set with type '%1'. Scope This document is informational and intended for any user. SBL-EAI-50157: Error converting property set hierarchy to integration object hierarchy. Cannot find integration component corresponding to property set with type '%1'. Explanation The property set type does not match any known integration component. Corrective Action Check the input property set type and make sure it corresponds to an integration component.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50152: Cannot have more than one active integration component specified on integration object instance. The ID of the current active integration component is '%1' Scope This document is informational and intended for any user. SBL-EAI-50152: Cannot have more than one active integration component specified on integration object instance. The ID of the current active integration component is '%1' Explanation More than one active integration component was found in the integration object instance. Corrective Action Check the integration object instance and make sure that only one active ID is specified.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50152: Cannot have more than one active integration component specified on integration object instance. The ID of the current active integration component is '%1' Scope This document is informational and intended for any user. SBL-EAI-50152: Cannot have more than one active integration component specified on integration object instance. The ID of the current active integration component is '%1' Explanation More than one active integration component was found in the integration object instance. Corrective Action Check the integration object instance and make sure that only one active ID is specified.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50145: No record retrieved corresponding to the business component '%1' and Id '%2' Scope This document is informational and intended for any user. SBL-EAI-50145: No record retrieved corresponding to the business component '%1' and Id '%2' Explanation This event is logged when a record referenced by the integration component instance does not exist in the business component. Corrective Action Check the integration component and make sure that a correct Id is specified. The referenced record does not exist in the database.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50143: During Business Component Query, error returned '%1' Scope This document is informational and intended for any user. SBL-EAI-50143: During Business Component Query, error returned '%1' Explanation An error has occured while querying the business component. Corrective Action See the error that is returned and take the appropriate action.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50134: Integration object instance '%1' did not have a valid root component. Scope This document is informational and intended for any user. SBL-EAI-50134: Integration object instance '%1' did not have a valid root component. Explanation Unable to obtain the root component of an integration object instance. Corrective Action Check the root component of the integration object instance to verify it conforms to its definition in Tools.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50120: An error has occured while handling a request. Please examine the server log file '%1'. Scope This document is informational and intended for any user. SBL-EAI-50120: An error has occured while handling a request. Please examine the server log file '%1'. Explanation An error has occured while processing a request. Corrective Action Examine the server log file for more details.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50129: Could not create state. No active integration component was found on the leaf level in integration object instance '%1'. Scope This document is informational and intended for any user. SBL-EAI-50129: Could not create state. No active integration component was found on the leaf level in integration object instance '%1'. Explanation In order to raise a signal on a C/OM-enabled business component, the business component must be positioned on a leaf level record for the integration object instance. Corrective Action Check the integration object instance and make sure that an active leaf level integration component is specified.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50128: No rows retrieved corresponding to the business component '%1' and ID '%2' Scope This document is informational and intended for any user. SBL-EAI-50128: No rows retrieved corresponding to the business component '%1' and ID '%2' Explanation A record referenced by the integration component instance does not exist in the business component. Corrective Action Check the integration component instance and make sure that the correct ID is specified and that the referenced record exists in the database.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50127: No rows retrieved corresponding to the business component '%1' Scope This document is informational and intended for any user. SBL-EAI-50127: No rows retrieved corresponding to the business component '%1' Explanation An attempt to recreate the business component state failed because there are no records. Corrective Action Check the itegration component instance and make sure that all referenced records exist.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50126: Multiple matches found for record using search specification '%2' for the business component '%3'. Scope This document is informational and intended for any user. SBL-EAI-50126: Multiple matches found for record using search specification '%2' for the business component '%3'. Explanation The business component query returned more than one record when attempting to recreate the business component state. Corrective Action Check the integration component instance and make sure that the correct ID is specified. Related

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50125: Could not create state, no ID is specified in integration component '%1' Scope This document is informational and intended for any user. SBL-EAI-50125: Could not create state, no ID is specified in integration component '%1' Explanation To recreate the state of a business component, you need to know the IDs of all the requested records. These IDs must be included in the integration component instance. Corrective Action Specify an ID for the integration component instance.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50124: Could not obtain business object; external name is not set on Integration Object '%1' Scope This document is informational and intended for any user. SBL-EAI-50124: Could not obtain business object; external name is not set on Integration Object '%1' Explanation No external name has been set for the specified integration object. Corrective Action Check the integration object definition and make sure that an external name is specified.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50123: The integration object '%1' is inactive. Scope This document is informational and intended for any user. SBL-EAI-50123: The integration object '%1' is inactive. Explanation The integration object is inactive. Corrective Action Activate the integration object.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50122: Required data is missing in the integration object '%1' definition: you must set the '%2' for integration component '%3'. Scope This document is informational and intended for any user. SBL-EAI-50122: Required data is missing in the integration object '%1' definition: you must set the '%2' for integration component '%3'. Explanation Verify that the required data is provided. For example, external name. Corrective Action Check the error message and set the missing data in the integration component definition.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50121: The %1 is missing in the input parameters for method %2. Scope This document is informational and intended for any user. SBL-EAI-50121: The %1 is missing in the input parameters for method %2. Explanation A required parameter is missing from the input for this method. Corrective Action Verify that the input parameter is specified.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50119: Integration Object '%1' contains an Integration Component with invalid XML tags. Scope This document is informational and intended for any user. SBL-EAI-50119: Integration Object '%1' contains an Integration Component with invalid XML tags. Explanation The XML tag for Integration Component contains invalid characters Corrective Action Make sure that the XML Tags do not contain invalid characters.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50118: Integration Component '%1' in Integration Object '%2' contains Integration Fields with invalid XML tags. Scope This document is informational and intended for any user. SBL-EAI-50118: Integration Component '%1' in Integration Object '%2' contains Integration Fields with invalid XML tags. Explanation The XML tag for an Integration Component Field contains invalid characters Corrective Action Make sure that the XML Tags do not contain invalid characters.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50117: The XML tag '%1' for Integration Object '%2' contains invalid character. Scope This document is informational and intended for any user. SBL-EAI-50117: The XML tag '%1' for Integration Object '%2' contains invalid character. Explanation The XML tag for Integration Object contains invalid characters Corrective Action Make sure that the XML Tags do not contain invalid characters.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50116: The XML tag '%1' for Integration Component Field '%2' contains invalid character. Scope This document is informational and intended for any user. SBL-EAI-50116: The XML tag '%1' for Integration Component Field '%2' contains invalid character. Explanation The XML tag for Integration Component Field contains invalid characters Corrective Action Make sure that the XML Tags do not contain invalid characters.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50115: The XML tag '%1' for integration component %2 contains invalid character '%3'. Scope This document is informational and intended for any user. SBL-EAI-50115: The XML tag '%1' for integration component %2 contains invalid character '%3'. Explanation The XML tag for integration component contains invalid characters. Corrective Action Verify the XML tags do not contain invalid characters. Related Products Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel System Software

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50114: Integration components must form a tree. The components may form a loop: %1. Scope This document is informational and intended for any user. SBL-EAI-50114: Integration components must form a tree. The components may form a loop: %1. Explanation The integration components form a loop, which is not valid. Corrective Action Check your integration object definition to verify that the setting of the Parent Component field does not form a loop.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50113: Integration components must form a tree with only one root component. The following components did not specify a parent component: %1. Scope This document is informational and intended for any user. SBL-EAI-50113: Integration components must form a tree with only one root component. The following components did not specify a parent component: %1. Explanation More than one root component exists. Corrective Action Check the integration object definition and make sure there is only one root component.

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50112: Required data is missing in the integration object '%1' definition: '%2' has to be set. Scope This document is informational and intended for any user. SBL-EAI-50112: Required data is missing in the integration object '%1' definition: '%2' has to be set. Explanation Verify required data (such as Base Object Type) is provided. Corrective Action Check the error message and set the missing data in the integration object definition

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50111: An invalid EAI Message was received. Please check your configuration Scope This document is informational and intended for any user. SBL-EAI-50111: An invalid EAI Message was received. Please check your configuration Explanation An invalid EAI message is received Corrective Action Check your configuration

Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI Version:Siebel 8.1 Purpose This document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50110: The input parameter %1 is missing or invalid for the Integration Object Definition Wizard Service. Scope This document is informational and intended for any user. SBL-EAI-50110: The input parameter %1 is missing or invalid for the Integration Object Definition Wizard Service. Explanation An input parameter is missing from the message. Corrective Action Verify that the input message contains valid input parameters, such as Project Name and Repository Name.