יום רביעי, 27 באפריל 2011

SESSION SQL

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 be very handy if anybody wants to update or delete from the Base table or Interface table after EIM processing is done as defined in the configuration file. A sample requirement could be setting Primary Organization in Contact. If EIM champs are still reading then definitely thought of using "EIM Explicit Primary Mapping" will be lurking in mind. But unfortunately the Primary Organization Id (BU_ID) is not mapped in the explicit primary settings in EIM_CONTACT table.

But still we can achieve the desired task by using "SESSION SQL". The idea is we can update BU_ID in the S_CONTACT with the ROW_ID of Organization which we want to be primary after we are done with the loading of "S_CONTACT_BU" base table. The key here is to have an identifier defined in the interface table that will specify which BU is the primary in the Interface table. We can either extend interface table or reuse any of the existing column(ensure that is not used in the EIM operation).

[Siebel Interface Manager]
.
.
.
.

[Update Primary Org]
SESSION SQL ="UPDATE SIEBEL.S_CONTACT SCON SET SCON.BU_ID = (SELECT SBU.ROW_ID FROM SIEBEL.S_BU SBU,SIEBEL.EIM_CONTACT ECON WHERE SBU.NAME = ECON.NAME AND ECON.X_PR_FLG = 'Y' AND ECON.T_CONTACT__RID = SCON.ROW_ID) WHERE SCON.ROW_ID IN (SELECT T_CONTACT__RID FROM SIEBEL.EIM_CONTACT WHERE T_CONTACT__RID IS NOT NULL AND X_PR_FLG = 'Y')"
TYPE = IMPORT
BATCH = 9999
TABLE = EIM_CONTACT
ONLY BASE TABLES = S_PARTY, S_CONTACT, S_CONTACT_BU


Interestingly we can have only one SESSION SQL statement per block and did i tell you we can also call procedures from this awesome parameter for complex processing.

Happy Data Load!!

יום חמישי, 21 באפריל 2011

Hierarchy Extraction ++

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 workflow in order to get the values from siebel message we need to pass input/Output variables as shown below:

Input Arguments


Output Arguments




The other advantage of using Aliases is that it doesn't error out reading a non-existing attribute from a Property Set.

Happy Extracting!!

יום רביעי, 20 באפריל 2011

Prompt:Browser Script::LoadPopupApplet:Server Script

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 server side code. "LoadPopupApplet" mehtod is key here. It takes input as the name of applet to popup and the mode in which the applet should be displayed. I followed below steps to achieve desired requirement.

1 - Create a LOV of type "SR_POPUP". Keep the description blank and fill any random value in Name and Value. We will use the description field to be displayed in the Popup applet. Description will be used as temporary storage to user input.

2 - Create a pop up applet "SR Type Popup Applet" based on the "List Of Values" business component with search spec "([Type] = 'SR_POPUP' AND [Active] = 'Y')" . Only expose the Description field in this applet. Ensure that applet should have Edit web layout defined.

3 - Now comes the part where we write the script to popup the above applet and consume the input provided by user. The below code is written to invoke the applet and clear the description field once the processing is done.

For the "Summary" method in the "Service Request List Applet", below mentioned code is written.

if(MethodName == "Summary")
{
//Initial Processing to check the status of SR
if(this.Buscomp().GetFieldValue("Status") == "Open")
{
//Processing to clear the keyed in description by user
var sLOVBC = TheApplication().GetBusObject("List Of Values").GetBusComp("List Of Values");
with(sLOVBC)
{
ClearToQuery();
SetViewMode(3);
ActivateField("Description");
SetSearchSpec("Type","SR_POPUP");
ExecuteQuery();
if(FirstRecord())
{
SetFieldValue("Description","");
WriteRecord();
}

}
// code to popup the applet
var sBS = TheApplication().GetService("SLM Save List Service");
var sInput = TheApplication().NewPropertySet();
var sOutput = TheApplication().NewPropertySet();
sInput.SetProperty("Applet Name","SR Type Popup Applet");
sInput.SetProperty("Applet Mode","6");
sBS.InvokeMethod("LoadPopupApplet",sInput,sOutput);
}
return (CancelOperation);

}

For the "PickRecord" method in "SR Type Popup Applet" following code needs to be written for setting the "Abstract" field in SR.

if(MethodName == "PickRecord")
{
TheApplication().ActiveBusObject().GetBusComp("Service Request").SetFieldValue("Abstract",this.BusComp().GetFieldValue("Description"));
this.BusComp().SetFieldValue("Description","");
this.InvokeMethod("CloseApplet");
return (CancelOperation);
}

This is approach by which one can popup an applet and allow user to enter something and then do further executions. Please do share alternates to prompt in server script.

Happy Prompting!!



יום שלישי, 19 באפריל 2011

Siebel Power User - Part 1

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 Activities to 'Call'

Select all records and click the Edit option in the application menu and select change records. Change records allows you to update a maximum of 4 fields of the same record simultaneously.





















Select Type in Field 1 and change the value to 'Call Back'
 













And there you go, you now have 15 more minutes to facebook ;)

Please feel free to use the comments section for any feeback on this post, or if you would like to contribute to this series.

Cheers!


יום חמישי, 14 באפריל 2011

Fetching IP Address in Siebel

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 "GetServerVariables". The input argument to this BS should be "REMOTE_HOST" and "AUTH_USER_ID". This returns the host ip address and logged in user id respectively.
  • Second step makes use of "Inbound E-mail Database Operations" business service with method "InsertRecord". It inserts the fetched IP address and User Id values in the desired audit table.
2 - Invoke the above created action set by using Application Login run time event.

This business service is extensively used for session management and cookies handling. Digging deep will reveal the true power of this BS.

Happy Securing!!

יום שני, 11 באפריל 2011

SBL-EAI-50187: The file '%1' does not exist.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50187: The file reference '%1' does not exist.
ScopeThis document is informational and intended for any user.
SBL-EAI-50187: The file reference '%1' does not exist.ExplanationThe specified file cannot be found on the file system.
Corrective ActionCheck 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 published as Siebel SR 38-3474521161.
***Checked for relevance on 22-NOV-2010***
SymptomsHave a Siebel Web Service that has a file (buffer) as an input parameter.
Push a file bigger thant 10 Kilobyte and get the following error :
Erreur lors du traitement de l'argument http://www.siebel.com/xml/RBQ%20Form%20Instance%20Attachment:ListOfRBQFormInstanceNumerisation de l'op�ration IncrireDocument(SBL-EAI-04316)

in english
SBL-EAI-50187 The file 'D:\sba80\siebsrvr\temp\1-IG49_0.tmp'does not exist.
CauseWS-Security is used to pass security credentials in the SOAP header. When a SOAP / inline XML message reaches Siebel the SOAP header is parsed and temporary attachment files are created.

After the authenticate event the EAI OM runs the ReLogin event to disconnect the anon user and connect the SOAP header user. During this event the EAI OM deletes the temporary files.

When the XML Converter is invoked to convert the XML message and attachment temp file into property set the message error SBL-EAI-50187 is experienced, crashing the EAI OM component.

The Change Request# 10531649 was created to address this issue on future releases.
Solution

Since customer was not allowed to pass security credentials in the URL it was suggested to use the Session Management instead of WS-Security.

Reference Bookshelf 8.0 > Integration Platform Technologies: Siebel Enterprise Application Integration > Web Services > About Siebel Authentication and Session Management SOAP Headers

This issue has been fixed in 8.0.0.6 Fix Pack and 8.1.1.1 Fix Pack
ReferencesNOTE:745864.1 - EAI File Streaming is NOT supported before 8.0.0.6 Fix Pack or 8.1.1.1 Fix Pack

SBL-EAI-50177: Error getting the size of file reference file '%1'


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis 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'

ScopeThis document is informational and intended for any user.

SBL-EAI-50177: Error getting the size of file reference '%1'ExplanationCannot get the size of a temporary file.

Corrective ActionCheck whether the specified file exists and is readable.

SBL-EAI-50176: Error writing to file reference file '%1'


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

SymptomsThe "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 size. So the big XML documents can be efficiently passed between an XML Converter and an EAI Transport without its intermediate loading it into memory buffer.

Normally, all temporary files are automatically removed once the BS is unregistered (unloaded) or Siebel Session is completed . However some orphan files could remain there in case of unexpected Siebel CRM Application crash and termination.

Solution
Monitor the space usage in the "temp" folder of each Siebel Server installation
and periodically clean-up .tmp files from the "temp" sub-folder when the accordant Siebel Server is shutdown.

Product Enhancement Request CR # BUG 10566911 "Enable parameterization of XML file reference creation" has been logged to address the need in parametrisation of the XML file referencing feature (e.g. either increase the XML document file size threshold or turn it off or change the path to the temporary folder). This will be reviewed and evaluated for a possible implementation in future releases.

ReferencesBUG:10566911 - ENABLE PARAMETERIZATION OF XML FILE REFERENCE CREATION.
NOTE:745864.1 - EAI File Streaming is NOT supported before 8.0.0.6 Fix Pack or 8.1.1.1 Fix Pack















Applies to: Siebel CRM - Version: 8.1.1 SIA [21111] and later [Release: V8 and later ]
Information in this document applies to any platform.

SymptomsDuring processing for some interfaces, XML is written to a file in a network folder, for further processing by the middleware. The 'EAI XML Write to File' Business Service is used to write the file to the intended network location.

When processing some large files (e.g. 1 MB), it was observed that Siebel would write to a temporary location. And when this occurred, a failure was reported :-

ObjMgrBusServiceLog Error 1 000002ef4be2083c:0 2010-05-06 01:53:54 (eaixmlprtsvc.cpp (234)) SBL-EAI-04266: 'EAI XML Write to File' service with method 'WriteXMLHier' failed while generating XML to be written to file '\\10.10.10.10\SiebFS\CreditCard\FileWJ05.000006.xml'.

New large file reference is created - 'D:\sba811\siebsrvr\temp\1-6TU2_0.tmp'.

EAIFileAttachments EAIFileAttachmentDebug 5 000030134bde1fbc:0 2010-05-04 04:36:40 New large file reference is registered - 'D:\sba811\siebsrvr\temp\1-6TU2_0.tmp'.

ObjMgrLog Error 1 000030134bde1fbc:0 2010-05-04 04:36:40 (filerefutil.cpp (272)) SBL-GEN-10103: Error opening specified file

ObjMgrLog Error 1 000030134bde1fbc:0 2010-05-04 04:36:40 (filerefutil.cpp (272)) SBL-EAI-50176: Error writing to file reference 'D:\sba811\siebsrvr\temp\1-6TU2_0.tmp'.


CauseIn this case, it was determined that the error arose because the middleware application was picking up the file before Siebel had completed writing the file.

SolutionThe middleware process picking up the file was delayed, to allow Siebel to complete it's operation.

Other points to check :-

1. Ensure the \temp directory being written to is accessible from the operating system user running the Siebel Server service.

2. Ensure there is sufficient space, as discussed in :-

The "Error writing to file reference '...\siebsrvr\....tmp (SBL-EAI-50176)'" is raised from "IntObjHierToXMLDoc" method of the "EAI XML Converter" BS when producing large XML document (Doc ID 824888.1)

3. Check that no other processes (e.g. anti-virus software) are trying to access the files being written to by Siebel.


ReferencesNOTE:824888.1 - The "Error writing to file reference '...\siebsrvr\....tmp (SBL-EAI-50176)'" is raised from "IntObjHierToXMLDoc" method of the "EAI XML Converter" BS when producing large XML document
















Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50176: Error writing to file reference '%1'.

ScopeThis document is informational and intended for any user.

SBL-EAI-50176: Error writing to file reference '%1'.ExplanationUnable to write to temporary file.

Corrective ActionCheck whether the specified file exists and is writable.





















Applies to: Siebel CRM - Version: 8.0.0.2 [20412] to 8.0.0.5 [20420] - Release: V8 to V8
Information in this document applies to any platform.
***Checked for relevance on 22-NOV-2010***

DescriptionEAI File Streaming is NOT supported on Siebel before 8.0.0.6 Fix Pack or 8.1.1.1 Fix Pack

There are known issues in using the new "EAI File Streaming" that causes failure in specific cases.

One example is BUG :12-1LTG2F6 described in "Problem with file attachment size with EAI object manager (Doc ID 496506.1)"

Please do not use it prior to 8.0.0.6 Fix Pack or 8.1.1.1 Fix Pack

Likelihood of OccurrenceMay happen if "LargeFileChunkingEnabled" is explicitly set to TRUE in the [Application] section of eapps.cfg and a large dataset is returned from an inbound web service call.

Possible SymptomsEAIFileAttachments EAIFileAttachmentDebug 5 00000af848f814f2:0 2008-10-18 11:35:28 Getting file reference manager Session Global by key 'FileReferenceManager'
EAIFileAttachments EAIFileAttachmentDetail 4 00000af848f814f2:0 2008-10-18 11:35:28 New large file reference is created - '/sbsiebcrmtest/siebsrvr/temp/1-DN5R_0.tmp'
EAIFileAttachments EAIFileAttachmentDebug 5 00000af848f814f2:0 2008-10-18 11:35:28 New large file reference is registered - '/sbsiebcrmtest/siebsrvr/temp/1-DN5R_0.tmp'
ObjMgrLog Error 1 00000af848f814f2:0 2008-10-18 11:35:28 (filerefutil.cpp (249)) SBL-GEN-10103: Error opening specified file
ObjMgrLog Error 1 00000af848f814f2:0 2008-10-18 11:35:28 (filerefutil.cpp (249)) SBL-EAI-50176: Error writing to file reference

and

Erreur lors du traitement de l'argument http://www.siebel.com/xml/RBQ%20Form%20Instance%20Attachment:ListOfRBQFormInstanceNumerisation de l'op�ration IncrireDocument(SBL-EAI-04316)

SBL-EAI-50187 The file 'D:\sba80\siebsrvr\temp\1-IG49_0.tmp'does not exist

Workaround or Resolution
Please ensure "LargeFileChunkingEnabled" is explicitly set to FALSE in the [Application] section of eapps.cfg. and restart the web server.

Or please apply 8.0.0.6 Fix Pack or higher or 8.1.1.1 Fix Pack or higher.









Related







Products








Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel CRM


Keywords






 

WEB SERVICES; INBOUND; SERVICES

 

Errors





 

SBL-EAI-50176; SBL-EAI-04316; SBL-EAI-50187; SBL-GEN-10103; ERROR 1



SBL-EAI-50175: Error reading from file reference file '%1'


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

SBL-EAI-50174: Error deleting file reference file '%1'


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50174: Error deleting file reference '%1'.

ScopeThis document is informational and intended for any user.

SBL-EAI-50174: Error deleting file reference '%1'.ExplanationError deleting temporary file.

Corrective ActionCheck to see if a user temporary file exists.

SBL-EAI-50173: Error creating file reference file '%1'


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

SBL-EAI-50172: The Workflow Process '%1' is either not active or its status is not "Completed" and cannot be exposed as a Web Service.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis 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. ExplanationThe workflow may not be activated or completed.

Corrective ActionMake sure the workflow is completed and activated.

SBL-EAI-50171: The Business Service '%1' is not active. Please activate it first.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis document is informational and intended for any user.

SBL-EAI-50171: The business service '%1' is not active. You must activate it.ExplanationThe business service is not active.

Corrective ActionActivate the business service first.

SBL-EAI-50170: The Business Service %s does not contain any method that can be exposed.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis document is informational and intended for any user.

SBL-EAI-50170: The business service % does not contain any method that can be exposed.ExplanationThe business service does not contain any method that can be exposed.

Corrective ActionVerify that the business service to be exposed as a Web service contains methods.

SBL-EAI-50169: No method was selected to get exposed. Please selecte the methods to be exposed.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50169: Select the methods you want to expose.

ScopeThis document is informational and intended for any user.

SBL-EAI-50169: Select the methods you want to expose.ExplanationNo method is selected.

Corrective ActionSelect at least one method.

SBL-EAI-50168: The following selected methods either have arguemnt(s) of unsupported type hierarchy without an Integration Object specified or do not have any argument at all.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis 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.ExplanationSome methods either have argument(s) of unsupported type hierarchy without an Integration Object specified or do not have any argument configured.

Corrective ActionMake sure that all methods have arguments and that for any argument of data type Hierarcy, an Integration Object Name is also specified.

SBL-EAI-50167: The selected Workflow Process contains process properties of hierarchy type without Integration Object name specified. This is not supported in Siebel Inbound Web Service.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis 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.ExplanationThe selected workflow process contains hierarchy type process properties without having the integration object name specified.

Corrective ActionSpecify an integration object name for process properties of hierarchy type.

SBL-EAI-50166: The web service URL is not valid. Please replace and with the appropriate values.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis document is informational and intended for any user.

SBL-EAI-50166: The Web Service URL is not valid. Replace and with the appropriate values.ExplanationThe Web Service URL is not valid.

Corrective ActionEnter a valid URL for the Web Service.

SBL-EAI-50165: The operation name '%1' is not unique. Please enter a new one or use the one generated for you.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis 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.ExplanationThe operation name is not unique.

Corrective ActionEnter a new name or use the name generated for you by the wizard.

SBL-EAI-50164: Please enter a operation name for the web service.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
PurposeThis 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.
ScopeThis document is informational and intended for any user.
SBL-EAI-50164: Enter an operation name for the Web Service.ExplanationThe operation name is missing.
Corrective ActionEnter an operation name.

SBL-EAI-50163: Please enter a valid path for the wsdl file.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis document is informational and intended for any user.

SBL-EAI-50163: Enter a valid path for the WSDL file.ExplanationA valid path for the WSDL file is missing.

Corrective ActionEnter a valid path for 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

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

ScopeThis 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.ExplanationThe Workflow is not activated.

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

SBL-EAI-50161: The Business Service or Workflow Process '%1' has already been deployed as a web service of namespace '%2'.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis 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'.ExplanationThe business service or workflow has already been deployed in the same namespace.

Corrective ActionDelete the existing Web Service before trying to deploy it again.

SBL-EAI-50160: Cannot find integration component field definition (Integration Component '%1', Integration Object '%2') corresponding to the property '%3' (Property Set Type '%4')


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis 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')

ScopeThis 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')ExplanationA property set property was found that does not correspond to a known integration component field.

Corrective ActionCheck that the specified property in the property set corresponds to an integration component field in the integration component definition.

SBL-EAI-50157: Error converting property set hierarchy to integration object hierarchy. Cannot find integration component definition correspoding to property set with type '%1'


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis 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'.ExplanationThe property set type does not match any known integration component.

Corrective ActionCheck the input property set type and make sure it corresponds to an integration component.

SBL-EAI-50156: Cannot find definition for integration component field '%1' in Integration Component '%2' (Integration Object '%3')


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis 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'

ScopeThis 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'ExplanationMore than one active integration component was found in the integration object instance.

Corrective ActionCheck the integration object instance and make sure that only one active ID is specified.

SBL-EAI-50152: Cannot have more than one active Id specified on Integration Object Instance, current active Id is '%1'


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
PurposeThis 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'
ScopeThis 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'ExplanationMore than one active integration component was found in the integration object instance.
Corrective ActionCheck the integration object instance and make sure that only one active ID is specified.

SBL-EAI-50145: No record retrieved corresponding to the business component '%1' and Id '%2'


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
PurposeThis 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'
ScopeThis document is informational and intended for any user.
SBL-EAI-50145: No record retrieved corresponding to the business component '%1' and Id '%2'ExplanationThis event is logged when a record referenced by the integration component instance does not exist in the business component.
Corrective ActionCheck the integration component and make sure that a correct Id is specified. The referenced record does not exist in the database.

SBL-EAI-50143: During Business Component Query, error returned '%1'


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50143: During Business Component Query, error returned '%1'

ScopeThis document is informational and intended for any user.

SBL-EAI-50143: During Business Component Query, error returned '%1'ExplanationAn error has occured while querying the business component.

Corrective ActionSee the error that is returned and take the appropriate action.

SBL-EAI-50134: Integration object instance '%1' did not have a valid root component.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
PurposeThis 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.
ScopeThis document is informational and intended for any user.
SBL-EAI-50134: Integration object instance '%1' did not have a valid root component.ExplanationUnable to obtain the root component of an integration object instance.
Corrective ActionCheck the root component of the integration object instance to verify it conforms to its definition in Tools.

SBL-EAI-50120: Please examine the server log file '%1'.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
PurposeThis 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'.
ScopeThis 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'.ExplanationAn error has occured while processing a request.
Corrective ActionExamine the server log file for more details.

SBL-EAI-50129: Could not create state, No Active ID was found on the leaf level in Integration Object Instance '%1'


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis 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'.ExplanationIn 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 ActionCheck the integration object instance and make sure that an active leaf level integration component is specified.

SBL-EAI-50128: No rows retrieved corresponding to the business component '%1' and Id '%2'


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis 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'

ScopeThis document is informational and intended for any user.

SBL-EAI-50128: No rows retrieved corresponding to the business component '%1' and ID '%2'ExplanationA record referenced by the integration component instance does not exist in the business component.

Corrective ActionCheck the integration component instance and make sure that the correct ID is specified and that the referenced record exists in the database.

SBL-EAI-50127: No rows retrieved corresponding to the business component '%1'


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis 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'

ScopeThis document is informational and intended for any user.

SBL-EAI-50127: No rows retrieved corresponding to the business component '%1'ExplanationAn attempt to recreate the business component state failed because there are no records.

Corrective ActionCheck the itegration component instance and make sure that all referenced records exist.

SBL-EAI-50126: Multiple matches found for record using search specification '%2' in the business component '%3'.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
PurposeThis 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'.
ScopeThis 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'.ExplanationThe business component query returned more than one record when attempting to recreate the business component state.
Corrective ActionCheck the integration component instance and make sure that the correct ID is specified.





Related


SBL-EAI-50125: Could not create state, No Active ID was specified in Integration Component '%1'


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis 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'

ScopeThis document is informational and intended for any user.

SBL-EAI-50125: Could not create state, no ID is specified in integration component '%1'ExplanationTo 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 ActionSpecify an ID for the integration component instance.

SBL-EAI-50124: Could not obtain Business Object; No external name set on Integration Object


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis 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'

ScopeThis 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'ExplanationNo external name has been set for the specified integration object.

Corrective ActionCheck the integration object definition and make sure that an external name is specified.

SBL-EAI-50123: The integration object '%1' is inactive. Please activate it first.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-50123: The integration object '%1' is inactive.

ScopeThis document is informational and intended for any user.

SBL-EAI-50123: The integration object '%1' is inactive.ExplanationThe integration object is inactive.

Corrective ActionActivate the integration object.

SBL-EAI-50122: Required data is missing in the integration object '%1' definition: the '%2' for integration component '%3' has to be set.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis 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'.ExplanationVerify that the required data is provided. For example, external name.

Corrective ActionCheck the error message and set the missing data in the integration component definition.

SBL-EAI-50121: The %1 is missing in the input parameters for method %2.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis document is informational and intended for any user.

SBL-EAI-50121: The %1 is missing in the input parameters for method %2.ExplanationA required parameter is missing from the input for this method.

Corrective ActionVerify that the input parameter is specified.

SBL-EAI-50119: Integration Object '%1' contains an Integration Component with invalid XML tags.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis document is informational and intended for any user.

SBL-EAI-50119: Integration Object '%1' contains an Integration Component with invalid XML tags.ExplanationThe XML tag for Integration Component contains invalid characters

Corrective ActionMake sure that the XML Tags do not contain invalid characters.

SBL-EAI-50118: Integration Component '%1' in Integration Object '%2' contains Integration Fields with invalid XML tags.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
PurposeThis 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.
ScopeThis 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.ExplanationThe XML tag for an Integration Component Field contains invalid characters
Corrective ActionMake sure that the XML Tags do not contain invalid characters.

SBL-EAI-50117: The XML tag '%1' for Integration Object '%2' contains invalid character.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis document is informational and intended for any user.

SBL-EAI-50117: The XML tag '%1' for Integration Object '%2' contains invalid character.ExplanationThe XML tag for Integration Object contains invalid characters

Corrective ActionMake sure that the XML Tags do not contain invalid characters.

SBL-EAI-50116: The XML tag '%1' for Integration Component Field '%2' contains invalid character.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis document is informational and intended for any user.

SBL-EAI-50116: The XML tag '%1' for Integration Component Field '%2' contains invalid character.ExplanationThe XML tag for Integration Component Field contains invalid characters

Corrective ActionMake sure that the XML Tags do not contain invalid characters.

SBL-EAI-50115: The XML tag '%1' for Integration Component %2 contains invalid character '%3'.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1
PurposeThis 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'.
ScopeThis document is informational and intended for any user.
SBL-EAI-50115: The XML tag '%1' for integration component %2 contains invalid character '%3'.ExplanationThe XML tag for integration component contains invalid characters.
Corrective ActionVerify the XML tags do not contain invalid characters.





Related








Products










Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel System Software








SBL-EAI-50114: Ingegration Components have to form a tree. The following components form a loop: %1. %1.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis document is informational and intended for any user.

SBL-EAI-50114: Integration components must form a tree. The components may form a loop: %1.ExplanationThe integration components form a loop, which is not valid.

Corrective ActionCheck your integration object definition to verify that the setting of the Parent Component field does not form a loop.

SBL-EAI-50113: Ingegration Components have to form a tree. There should be only one root component. Instead the following components do not have a Parent Component: %1.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis 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.ExplanationMore than one root component exists.

Corrective ActionCheck the integration object definition and make sure there is only one root component.

SBL-EAI-50112: Required data is missing in the integration object '%1' definition: '%2' has to be set.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis 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.ExplanationVerify required data (such as Base Object Type) is provided.

Corrective ActionCheck the error message and set the missing data in the integration object definition

SBL-EAI-50111: An invalid EAI Message was received. Please check your configuration


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

PurposeThis 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

ScopeThis document is informational and intended for any user.

SBL-EAI-50111: An invalid EAI Message was received. Please check your configurationExplanationAn invalid EAI message is received

Corrective ActionCheck your configuration

SBL-EAI-50110: The input parameter %1 is missing or invalid for the Integration Ojbect Definition Wizard Service.


Applies to: Error Message Area:Application Integration Infrastructure, Enterprise Application Interfaces - EAI
Version:Siebel 8.1

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

ScopeThis 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.ExplanationAn input parameter is missing from the message.

Corrective ActionVerify that the input message contains valid input parameters, such as Project Name and Repository Name.