SBL-EAI-04399: All field values corresponding to the user key '%1' in the integration component '%2' have NULL 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-04399: All field values corresponding to the user key '%1' in the integration component '%2' have NULL values

ScopeThis document is informational and intended for any user.

SBL-EAI-04399: All field values corresponding to the user key '%1' in the integration component '%2' have NULL valuesExplanationAll the input fields specified in the integration component user key have empty values.

Corrective ActionWhen using a particular integration component user key, make sure that all of the input data field values are not empty























Applies to: Siebel CRM - Version: 8.0 [20405] - Release: V8

Information in this document applies to any platform.

Symptoms
Customer was getting error code “SBL-EAI-04399” while importing product from .xml file. Customer used the following steps to import product:

1. Navigate to Administration - Product screen > Workspace Projects view
2. In the Workspace Projects list, click the New button to create a new project
3. In the Workspace Projects menu, select Import Contents
4. In the VOD Import dialog box, click Browse to select the .xml file to import
5. Click the Import button
6. When the Import process is complete, check the Import Report and find the following error message:

Importar: Partial; Objeto: Tipo - Definición de producto, Nombre - POLITICA TERMINAL GAMA ALTA, Identificador - 1-DPJQ; [1] Todo los valores correspondientes a la clave de usuario 'User Key:1' del componente de integración 'Object Product Bu ImpExp BC' tienen valores NULL(SBL-EAI-04399); Se omitirán los datos

Cause
Import issue was due to corrupted organization data.

SolutionCustomer had done the following to resolve the issue:

1. From the source environment, navigate to Administration - Product screen, query for the product and lock it
2. Change the value in the Organization field to a different Organization
3. Release the product and export product in Workspace Projects view
4. In the target environment, navigate to Administration - Product screen > Workspace Projects view
5. In the Workspace Projects list, add a new record and complete the necessary fields
6. In the Workspace Projects menu, select Import Contents
7. In the VOD Import dialog box, click Browse and select the file to import, and then click Import. The imported file appears in the Workspace Projects list.
8. Check the Import report, the Import process is successful, no error is found.

Thank you,
Oracle|Siebel Technical Support




















Applies to: Product Release: V7 (Enterprise)
Version: 7.5.2.216 [16084] SVE Com/Med
Database: Oracle 8.1.7
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Sun Solaris 2.8

This document was previously published as Siebel SR 38-1047975761.

SymptomsSBL-EAI-04399

In the Accounts Summary Screen, Installed Assets applet, Selected as Asset and pressed MACD button, a pop up window comes up and in place of Existing Order and Existing Quote nothing was selected and MODIFY button was pressed, then work flow related error pops up (Please find the attchement for the Screen shot of the Error Message.

SolutionMessage 1For the benefit of other users:

The Modify button is on Account>>>Installed Assets screen is working fine for most of the accounts and Assets and it's only not working for some accounts/assets which they move from version 99.6 to 7.5.2. They are testing to make sure all accounts/assets moved from 99.6 works fine. The following error was reported for some assets for modify button was clicked:

All field values corresponding to the user key 'User Key:2' in the integration component 'Line Item' have NULL values
Error invoking service 'SIS OM PMT Service', method 'Synchronize' at step 'PMT Synch Quote Line Item'

Customer was suggested to enable persistence for SIS OM Edit Complex Asset Workflow where the error is encountered so that we can compare the input/output arguments for the records where the workflow runs fine vs. errors.

Later it was updated by customer that it was due to some of the line items having parent Asset Id as NULL. Once this was corrected all worked fine.

Change Request # 12-HGRYZX has been logged to enhance the above error message for efficient error message reporting/resolution.

Thank you,
-Siebel Technical Support.

Related Products Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Workflow

SBL-EAI-04398: No input integration object hierarchy found.

Applies to: Siebel System Software - Version: 7.7.2 [18325] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

This document was previously published as Siebel SR 38-1501532257.
***Checked for relevance on 07-JAN-2011***

SymptomsWorkfow steps:

Step 1: Start
Step 2. File Transport Method: Receive
Input Argument: d:\export\pu.xml
Output: SiebelXMLFromFile of type binary and stores XMl Doc
Step 3. EAI XML Converter Method: XMLDocToIntObjHier
Output: SiebelPropSet of type Hierarchy
Step 4: End

causes error: SBL-EAI-04398: No input integration object hierarchy found.

CauseAt step 3, the problem was with Output Argument Name. While looking into the workflow process, it was found that the output argument for the EAI XML Converter from File business service was specified “Siebel Message” (with one space) in the XML file exported from the workflow process. The output argument should be “SiebelMessage” (without space) instead of “Siebel Message”.

Solution

Please modify the output variable name :

Step 3: EAI Siebel Adapter Method: Upsert
Input Argument: SiebelPropSet












Applies to: Siebel Product Configurator - Version: 8.0.0.9 SIA[20433] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms
Comments
--------
with 8.0.0.9 remote product configurator does not work any more

Repro Steps:

1) enable remote product configurator for financial services and for eCommunications.

2) enable component Siebel Product Configuration Object Manager (ENU) of component group Siebel ISS

3) enable remote product configurator for all products or a small set you want to test with.

4) Import Products

5) Test behavior in Financial Services

select a contact,

in contact screen create an order, select Purchase Order

drill down order

add product

hit customize

change an attribute

hit Done Button

--> Error message:

SBL-GEN-00000: Unable to load message 0xffff

6)Other scenario with eCommunications:

In Sales Order Screen create a new order, add order line item with product ZP Test Product.

--> SBL-GEN-00000: Unable to load message 0xffff seen in log, not in UI.

Hit Customize and Done and you get following error in UI:

Error invoking service 'SIS OM PMT Service', method 'Synchronize' at step 'Sync Order Line Item'.(SBL-BPR-00162)

No input integration object hierarchy found.(SBL-EAI-04398)

Create a new Line item add poduct, hit Customize

Add a child product and hit Done Button.

You get the error message again.

Click on List link to see the order line items again.

Verify that there are no child items for the root product.

8) Run the same scenario without remote product configurator ans see that now all works without problems.

To turn off remote product configurator set for financial services and eCommunications

Parameter: Product Configurator - Use Rem = TRUE

Cause

new CR 10593351, bug

determined as duplicated of CR 12-1VM6MQX




Solution
following fixes are available:

8.0.0.5 [20420]QF6511 BugID: SBA: 9174030

8.0.0.8 [20430]QF0822 BugID: SBA: 9204251

8.0.0.9[20433]QF0917 BugID: SBA:9708959

8.0.0.10 Fix Pack Build2 [20435





















Applies to: Siebel System Software - Version: 7.5.3.5 [16183] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3.5 [16183] SVE
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2000 Advanced Server SP 3
Database Server OS: Microsoft Windows 2000 Advanced Server SP 4

This document was previously published as Siebel SR 38-2502831811.
***Checked for relevance on 11-NOV-2010***

SymptomsWhile calling an inbound web service from an VB.Net application, the inbound web service calls a workflow that performs a synchronize using the EAI Siebel Adapter the following error was observed :


SBL-EAI-04398 No input integration object hierarchy found.

CauseSiebelMessage input argument was defined as hierarchy instead of integration object

InboundDispatcher_input_args_187(004).dmp showed that SiebelMessage was of type “xsd:string" and that all of the “&”, “<” and “>” characters had been escaped in the incoming SOAP message.

The following information was included in the EAI Object Manager log file:


“Anger körtidsvärde för egenskap 'SiebelMessage' till:

<SiebelMessage MessageId="" IntObjectName="LF Person" MessageType="Integration Object" IntObjectFormat="Siebel Hierarchical"><ListOfLfPerson><Contact><LKFCode>056202</LKFCode><BirthDate>10/24/1945</BirthDate><EmailAddress/><EmailAddress2/><FirstName>Bernst-arne</FirstName><LFCompanyNumber>42</LFCompanyNumber><LFDeceasedDate/><LFSPARProtected>N</LFSPARProtected><LastName>Persson</LastName><MF>K</MF><LFPersonalNumber>19451024-0825</LFPersonalNumber><PartyUId>1163</PartyUId><ListOfCutAddress><CutAddress><AddressType>Alternativ adress</AddressType><City>Stockholm</City><Country>Sverige</Country><LFContactPrimaryAddressFlg>Y</LFContactPrimaryAddressFlg><LFStreetAddress1>Ostgota Brandstodsbolag</LFStreetAddress1><LFStreetAddress2>Platensgatan 11</LFStreetAddress2><LFStreetAddress3>Box 400</LFStreetAddress3><PostalCode>58104</PostalCode></CutAddress></ListOfCutAddress></Contact></ListOfLfPerson></SiebelMessage>”

This confirmed that the escaped characters included in the incoming SOAP message were correctly “unescaped”. The log file also showed that the following input argument string was passed to the EAI Siebel Adapter:


Input: @0*0*0*0*0*0*

As you can see it did not include the value assigned to the SiebelMessage process property. The customer had defined the SiebelMessage process property as follows:


Name, Type, In/Out
SiebelMessage, Hierarchy, In

Solution

The reported behavior was resolved after the customer changed the Type of SiebelMessage from Hierarchy to Integration Object and set the Integration Object field to the name of the integration object. The customer then regenerated the WSDL and amended the.NET code accordingly to pass in an instance of the integration object.


Product Release: V7 (Enterprise)
Version: 7.8.2.5 [19227] Com/Med
Database: Oracle 9.2.0.7
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-3347905181.

SymptomsWe have created inbound webservice based on Workflow. Workflow has 2 process properties of type Integration Object (Account Integration Object and Order Integration Object)
Workflow upserts Account and Order Integration Objects using EAI Siebel Adapter step.

We were able to create WSDL and import in SOAP UI successfully. However while trying to call workflow using inbound webservice we experienced error on upsert step.
Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Upsert'.(SBL-BPR-00162)-No input integration object hierarchy found.(SBL-EAI-04398)

Further investigation of SRs on supportweb suggested that name of property should be SiebelMessage. One of the process property (For Account IO) was renamed to SiebelMessage and then we were able to upsert account data.
However as per requirements we need 2 process properties as integration objects (Account and Order) and we can have only 1 process property with name SiebelMessage.

In other words Siebel Workflow based webservice seem to have technical limitation of having only 1 process property of datatype Integration Object and type "In" or "In/Out"

Is there any workaround to accept more than ONE Integration Object in workflow through webservice??

SolutionMessage 1For the benefit of other users:

A workflow process can be built to meet the requirement with the following characteristics.
It has 2 process properties of type Integration Object, one for Account and the other one for Order with respective name AccountIO and OrderIO, not SiebelMessage, otherwise it will raise errors.
It contains at least 2 business services steps to upsert with the AccountIO and to upsert with the OrderIO.
After deploying this workflow process and defining an inbound web service to use it, SOAP UI can be used with the generated WSDL and request can be sent to populate both the Account and Order records.

The workflow process demonstrates that passing 2 Integration Objects to a web service is possible.

Moreover, the workflow process mode should be set to Service Flow to avoid running into errors.

Applies to:

SBL-EAI-04397: No user key can be used for the Integration Component instance '%1'.

Applies to: Siebel Universal Customer Master - Version: 7.8.1.1 [19044] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
""""Checked for relevance on 26-OCT-2010""""
Product Release: V7 (Enterprise)
Version: 7.8.1.1 [19044]
Database: Oracle 9i
Application Server OS: Microsoft Windows 2000 Server
Database Server OS: Microsoft Windows 2000 Server

This document was previously published as Siebel SR 38-2139753541.

Symptomsexecuting ‘UCM Contact Batch Data Management Workflow’ in UCM application 7.8.1 and getting the following error at the step ‘Process NoMatch’:

ObjMgrLog Error 1 0 2005-06-17 15:37:03 (adptutils.cpp (1066)) SBL-EAI-04397: No user key can be used for the Integration Component instance 'Contact'.

EAISiebAdpt EAISiebAdptErr 1 0 2005-06-17 15:37:03 [0] No user key can be used for the Integration Component instance 'Contact'.(SBL-EAI-04397) (IDS_ERR_EAI_SA_NO_USERKEY)



Cause
The EAI Siebel Adapter uses the user key to match records. If there is no user key that can be used, Siebel Adapter has to error out. Siebel Adapter will enumerate through every user key based on sequence number and check if all the fields in the user key are present in the instance and one of the fields in non-empty. If such a user key is found, Siebel Adapter will use it for all the other integration component instances of the same type.

In this case, the error occurs at the step ‘'Process NoMatch' in which the ‘UCM Batch Manager’ business service is invoked at the step to process the Contact record. The business service in turn, invokes EAI Siebel Adapter internally to update or insert the input integration object instance to Contact table. Here the integration object instance is based on integration object ‘CIFContactInsert’.

The Contact integration component in the integration object has four user keys but EAI Siebel Adapter can’t find any user key meets the condition that all the fields in the user key are present in the instance and one of the fields in non-empty. That is why the reported original error is caused.

Solution

The Party UID is user key field in the first user key in the Contact integration component. If the Party UID is populated to Null when creating the Contact record to UCM SDH table, EAI Siebel Adapter can’t use the field value when moving the Contact record from UCM SDH table to Contact base table.

In order to make sure the Party UID is populated in UCM SDH table, one way is to set the <Id> field value to a valid value such as external record id in the CRMML message and execute the workflow ‘UCM Server Party Package Workflow’. The other way is to set UCM_PARTY_UID column to a unique value in EIM_UCM_CON table and run the EIM job.

Please set ‘UCM_PARTY_UID’ column value to a unique value when running the EIM job so that the Party UID is populated





















Applies to: Siebel System Software - Version: 7.5.3 [16157] - Release: V7

Information in this document applies to any platform.
Version:Siebel 7.5.3

PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04397: No user key can be used for the Integration Component instance '%1'.

ScopeThis document is informational and intended for any user.

SBL-EAI-04397: No user key can be used for the Integration Component instance '%1'.ExplanationSiebel Adapter uses the user key to match records. If there is no user key that can be used, Siebel Adapter has to error out. During processing of integration component instance, the EAI Siebel Adapter chooses to use the first user key in the sequence that satisfies the condition that all the fields of that user key are present in an integration component instance. The first instance of each integration component type determines the user key used by all instances of that type.

Corrective ActionCheck the integration component instance and make sure that all fields for at least one user key exist in the integration component instance.





















Applies to: Siebel System Software - Version: 7.5.3 [16157] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.5.3 [16157]
Database: Oracle 8.1.7.2
Application Server OS: Microsoft Windows 2000 Server SP 2
Database Server OS: Microsoft Windows 2000 Server SP 2

This document was previously published as Siebel SR 38-1057386131.
***Checked for relevance on 12-JAN-2011***

SymptomsThe following error was being reported by the EAI Siebel Adapter when the incoming message did not contain a value for the <SerialNumber> in a custom Integration Object

SBL-EAI-04397 No user key can be used for the Integration Component instance "SMX Tyres Parts - Tyres Parts"

There was a Pre Default Value on the associated Business Component Field, but this did not effect the result.

CauseUsing the Upsert method of the EAI Siebel Adapter (which could result in either an Insert or an Update) there must be a valid User Key present for each Integration Component in the SiebelMessage. This is so the EAI Siebel Adapter can determine whether it should perform an update or an insert (i.e. before the Pre Default Value is even considered).

Solution

In this case, the requirement was to update (or insert if it did not exist) a row in the Business Component matching the incoming <SerialNumber>. If no <SerialNumber> was provided, then a row was to be created (and the “Serial Number” Field in the Business Component set to the newly created row_id. This was achieved as follows :-

The Pre Default Value for the “Serial Number” field was set to - Field: 'Id'. A second User Key (Key Sequence Number = 2) was added to the Integration Component, based on Id. Before the EAI Siebel Adapter step, the Id was set with a hard-coded value using eScript (the customer did not want to amend the structure of the XML file) :-

Inputs.GetChild(0).GetChild(0).GetChild(0).SetProperty("Id", "XXX");
The SerialNumber property was also checked in eScript, and if this was empty, it was removed from the SiebelMessage using RemoveProperty.

At the Upsert step, because there is no SerialNumber present (User Key 1), the EAI Siebel Adapter will use the second User Key.
And because 'XXX' cannot exist as a valid row_id, it will create a new row in the Business Component.
If the SerialNumber is present in the message, then the first User Key will be used, as before (and update or insert a row as required). This worked as expected.

Lastly, it was a requirement to obtain the value of the newly created row_id. This was available through the Output Argument "Object Id" of the EAI Siebel Adapter Upsert method.
















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

PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-04397: No user key can be used for the Integration Component instance '%1'.

ScopeThis document is informational and intended for any user.

SBL-EAI-04397: No user key can be used for the Integration Component instance '%1'.ExplanationSiebel Adapter uses the user key to match records. If there is no user key that can be used, Siebel Adapter has to error out. Siebel Adapter will enumerate through every user key based on sequence number and check if all the fields in the user key are present in the instance and one of the fields in non-empty. If such a user key is found, Siebel Adapter will use it for all the other integration component instances of the same type.

Corrective ActionCheck the integration component instance and make sure that all fields for at least one user key exists in the integration component instance and one of those fields is not empty.























Applies to: Siebel System Software - Version: 7.8.2 SIA [19213] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Professional)
Version: 7.8.2 [19213]
Database: Microsoft SQL Server 2000 SP3
Application Server OS: Microsoft Windows 2003 Server SP1
Database Server OS: Microsoft Windows 2003 Server SP1

This document was previously published as Siebel SR 38-3178804201.
***Checked for relevance on 01-DEC-2010***

SymptomsThe “Personal Address” integration component instance contains “User Key 1”
composed of
'Personal Street Address' ;
'Personal State'
'Personal City'
“CM Addr Num”

“CM Addr Num” is not present int the integration component though.

Even after creating and activating the field, when “User Key 1” is active, the following error is observed.


ObjMgrLog Error 1 0 2006-10-23 06:41:54 (adptutils.cpp (1090)) SBL-EAI-04397: No user key can be used for the Integration Component instance 'Personal Address'.



CauseThe root cause of this behavior is related with the Business Component User Property definition "Promotion Map:Personal Address.CM Address Num" defined in the “List Mgmt Prospective Contact” Business Component. Customer did not define the correct Field Integration Component Name.


Reference:Integration Platform Technologies: Siebel Enterprise Application Integration > Integration Objects > About Integration Component Keys >
User Keys

Solution



Incorrect User Propertie definition: "Promotion Map:Personal Address.CM Address Num

Correct User Propery Definition: "Promotion Map:Personal Address.CM Addr Num"

After change the User Property definition the user key issue was not experienced.

Reference: Bookshelf: Siebel Marketing User Guide > List Management > Promotion of Prospects to Contacts > Modifying Map Entries






















Applies to: Siebel CRM Call Center - Version: 8.1 [21039] and later [Release: V8 and later ]
Information in this document applies to any platform.

SymptomsEnvironment :- Siebel CRM version 8.1.x

On trying to invoke the InsertOrUpdate method of a Custom ASI web service , an error was reported as below :-
---------------
SBL-EAI-04397: No user key can be used for the Integration Component instance 'XXX'.
---------------

The Internal Integration Object (IO) consisted of multiple user keys (e.g user key 1, user key 2 and user key 3), out of which ALL fields specified under one user key (i.e User key 1) was provided in the incoming soap message. Nevertheless, the above error occurred while invoking the web service.

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

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 inconsistent IO definition, it is recommended to keep the "Deploy the Integration Object" checkbox unchecked (the default value).

SolutionThe error could be avoided either by :-

1. Re-deploying the latest IO definition in the runtime database.

Steps :-
-------------
1. In the Object Explorer in Siebel Tools, select the latest IO definition.
2. Right-click the integration object name and choose Deploy to Runtime Database.

Or

2. Undeploying the IO so that the latest IO definition is read from .SRF.

Steps :-
-------------
1. In the Object Explorer in Siebel Tools, select the IO definition.
2. Right-click the integration object name and choose Undeploy to remove it from runtime database

























Applies to: Siebel Email Marketing - Version: 8.0.0.2 [20412] and later [Release: V8 and later ]
Information in this document applies to any platform.

Symptoms
Customer has identified the following error on BHD.log:

No user key can be used for the Integration Component instance 'Marketing Camp Con'.(SBL-EAI-04397)Unknown

and could not see any other activity on the bhd.log.

Cause
Inspecting the auditMbox file that show part of the bounce email messages received by BHD from outside we could see that the bounces really do not have the corresponding SEMA-CR-@ as expected.

The Return-Path email heards shows:

Return-Path: <SEMA=2DCR=2D@<BHD Server domain>>

<SEMA=2DCR=2D@As the Row Id is not present in the Return-Path the BHD could not parse it and it parse a blank row id.

Then the BHD send the request to the Object Manager we get the error message: No user key can be used for the Integration Component instance 'Marketing Camp Con'.(SBL-EAI-04397).

We have request the customer to identify the Campaigns for the bounce messages with blank row id based on the Subject of the bounce emails.

Customer identified that the emails are not from Siebel Marketing Campaigns, but regular Siebel Application like F9 and Outbound Request.

Solution
Customer was requested to check on Site Map>Administration - Communications>Communications Drive and Profiles>select Internet SMTP/POP3 Server driver> Driver Parameters tab and verify if "Delivery Status Mailbox" or "Delivery Status Domain" has been set.

This can be set at Profile level so you must check all Profiles too at Site Map>Administration - Communications>Communications Drive and Profiles>select Internet SMTP/POP3 Server driver>Profile tab> and in the grand child applet Profile Parameters Overrides check for the same parameters.

If this is set and pointing to BHD Domain/Server it should be cleared, since BHD should only serves Siebel Marketing Campaigns sent by ESD daemon and not Siebel Communications Server.
















Applies to: Product Release: V7 (Enterprise)
Version: 7.7.2 [18325]
Database: Microsoft SQL Server 2000 SP 2
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

This document was previously published as Siebel SR 38-1547599769.

SymptomsSBL-EAI-13011, SBL-EAI-04397

Hi,

The ADM tool was working well for migrating Views and Responsibilities untill we applied Siebel 7.7.2 patch. Here we are observing that View names with less than 50 characters have no issues but more than 50 characters are throwing out the attached error. Have included the XML files and screen shots of the error messages.

Thanks.

SolutionMessage 1For the benefit of other users, ADM uses vanilla "UDA View Access" Integration Object to deploy views. In 7.7.1 if you create a new view named "Siebel Account Invoice Adjustment Request Items View (eService)" in Tools, by using "Copy Record" on vanilla view named "Account Invoice Adjustment Request Items View (eService)". This view name is 62 characters (with spaces); you are able to deploy it successfully. After applying 7.7.2 patch, you are unable to deploy it.

In customer’s case, they got 2 different errors:

1. Single file import:

No use key can be used for the Integration Component instance 'Feature Access'.(SBL-EAI-04397)

2. Multiple files import through workflow process, a different error:

Field '<?>' in the integration component '<?>' contains value '<?>', which is longer than allowed length of '<?>' characters.(SBL-EAI-13011)

The problem is identified to be as follows:
=====
The problem is with the external length of the Name field of "Feature Access" Integration component. Should be set to column length of 75 instead of BC Text Length of 50.
=====

The Change Request CR# 10482048 has been logged to address this issue, and it has been fixed in Siebel 7.8.


...continued in next activity...

Message 2The workaround is the following:

In Siebel Tools:
1. Lock the project "EMT Objects".
2. Navigate to Integration Object > choose "UDA View Access" > Integration Component > choose "Feature Access" > Integration Component Field > choose "Name" field. Change "External Length" property from 50 to 75.
3. Recompile client srf, and copy the recompiled srf to Siebel Server side.

And after that, the import works fine on 7.7.2 for the view with name = 62 characters. This should be the only change required.

Another property for this Integration Component Field is "Length"; it can be left as 50. We don't need to change "Text Length" property on Name field of "Feature Access" Business Component either.


keyword search:

SBL-EAI-04397; 04397 ERROR





 

SBL-EAI-04394: No integration component field corresponding to '%1'

Applies to: Siebel Tools - Version: 7.7.2 SIA [18325] to 8.1.1.3[21219] - Release: V7 to V8
z*OBSOLETE: Microsoft Windows 2000
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] CHS Com/Med
Database: Oracle 9.2.0.4
Application Server OS: Microsoft Windows 2000 Server SP 3
Database Server OS: HP-UX 11i

This document was previously published as Siebel SR 38-1809575601.

"" Checked for Relevance on 09/11/2010 ""

SymptomsSBL-EAI-04394

I encounter a problem after adding a user property inside the SIS OM PMT Service "Delta Old Field 10" = my custom field name. The error is [No integration component field corresponding '' (SBL-EAI-04394)]. Normally it would give a field name but this one doesn't.

I think I have completed adding all the custom field in there. But not sure why it still not work.

I attach the log and the SIS OM PMT Service + IO to you.
Please advise!

CauseThe customer has added a user property to the SIS OM PMT Service business service. The user property used is the ‘Delta Old Field’ which is used to capture the old value of a line item field when the line item is change by a modify order. The customer had

For example, Delta Old Field user property is defined as
Name = Delta Old Field 6
Value = [Custom Field 1]:[Custom Field 2]

The custom fields has been added to the Quote Item, MACD Quote Item, Order Entry – Line Items and MACD Order Entry – Line Items. It has been added to the SIS OM Quote and SIS OM Order integration objects.

When the Customize button is used on an Order Line Item, and the Done button is the clicked, the following error is displayed –
[No integration component field corresponding '' (SBL-EAI-04394)].


Bug 10493629 - "Receive error after adding new 'Delta Old Field' user property to SIS OM PMT Service bus. service" to report the fact that no field name is included in the error message.

Solution

If you encounter this error, please verify that you have taken the configuration steps outlined as follows:

1. Ensure both fields (Custom Field 1 & Custom Field 2) are defined in the Quote Item & MACD Quote Item business components and SIS OM Quote > Line Item Integration Component

2. Ensure both fields are defined in the Order Enter - Line Items & MACD Order Entry - Line Items business components and the SIS OM Order > Line Item Integration Component

3. The first field as defined for the 'Delta Old Field' user property, so only 'Custom Field 1' from [Custom Field 1]:[ Custom Field 2]) also needs to be added to Asset Mgmt – Asset business component and the SIS OM Asset Integration object.

4. Add following user props to SIS OM PMT Service:
SIS OM Quote.Line Item:SIS OM Order.Line Item Map n [Custom Field 1]:[ Custom Field 1]
SIS OM Quote.Line Item:SIS OM Order.Line Item Map n+1 [Custom Field 2]:[ Custom Field 2]

Further information regarding this user property please refer Bookshelf: Siebel Order Management Infrastructure Guide > PSP Engine > Configuring PSP Procedures > Configuring Eligibility, Compatibility, and Pricing > Configuring an Additional Field For Use in Eligibility, Compatibility, and Pricing






















Applies to: Siebel CRM - Version: 8.0 SIA [20405] and later [Release: V8 and later ]
Information in this document applies to any platform.
***Checked for relevance on 06-JAN-2011***

SymptomsAn error was reported as below while trying to create a new Integration Object by importing the attached xsd using EAI XSD Wizard.

---------------
ObjMgrLog Error 1 0000000249bf16f8:0 2009-03-17 13:26:45 (adptutils.cpp (4937)) SBL-EAI-04394: No integration component field corresponding to 'XML Literal Value'
EAISiebAdpt EAISiebAdptErr 1 0000000249bf16f8:0 2009-03-17 13:26:45 [0] No integration component field corresponding to 'XML Literal Value'(SBL-EAI-04394) (0x23112a)
---------------

CauseThrough further testing, the reported behaviour was narrowed down to schema element "default" being specified for xml elements (xs:element) in the xsd that was being imported.

It seems to be a limitation of the Integration Object Builder that it is not able to process the "default" attribute for xml elements whereas it can process it well for xml attributes (xs:attributes).


Per Bookshelf: XML Reference: Siebel Enterprise Application Integration > XML
Integration Objects and the XSD Wizard > Supported XSD Elements and Attributes, the level of support for the schema elements “default: element” and “default: attribute” is mentioned as "Mapped".

where Bookshelf defines Mapped as below:

--------------
Mapped. This level of support means that the information specified in a given element
or attribute is used in the integration object representation.”
----------------
So no difference in the behaviour should be observed while importing the schema element “default” for xml elements and xml attributes.

Change Request# 12-1SJNU69 has been logged to address this behaviour in a future version of the Siebel product.

SolutionThe XSD could be imported successfully in Siebel Tools after ammending it to remove the "default” attribute for the xsd elements while keeping it for xsd attributes .





















Applies to: Product Release: V7 (Enterprise)
Version: 7.5.3 [16157] Com/Med
Database: Oracle 8.1.6.3
Application Server OS: Sun Solaris 5.8
Database Server OS: Sun Solaris 5.8

This document was previously published as Siebel SR 38-1157161477.

SymptomsSBL-ISS-00119, SBL-ISS-00120, SBL-CFG-00175, SBL-ORD-00141, SBL-DBC-00105, SBL-EAI-04394, SBL-BPR-00162, SBL-EAI-04421

eConfigurator Issues with siebel patch 753.

We have recently Installed siebel patch 753 and we are facing some of the issues with that.

Issues:

1)All the Product attribute LOV's are appearing in red. Which were appearing fine before this installation.
2)Some of the eConfigurator rules are giving conflicts which were working fine before 753.
3)UI for the some of the product is not appearing as expected eg(on handsets tab Stocklevel field is not getting

expacted values and handsets are appearing in red and giving conflicts)

We have seen the similar SR (38-1059098781) on support web but this does not resolve the problem for us .

Please clarify the follwoing :

1)Is this an expected behaviour after applying the patch.
2)If so , Is there any workaround avalilable for them.
3)If not , Please suggest how to resolve them

We are already in contact with siebel DMO - Lisa Gill on this issue.




SolutionMessage 1For the benefit of other readers:

The customer recently Installed siebel patch 753 and found the following issue within their eConfigurator environment and found that all the Product attribute LOV's for a Customizable Product were appearing in red.This was not the case prior to the patch installation.

Technical Support tested the cusomter's Customizable Product against the standard Siebel configuration (vanilla srf) and sample database. Also used were the customer's customised web templates.

In V7.5.2.217, the attributes displayed after validating are in black.

In V7.5.3, the attributes displayed after validating are in red.

We also observed the same behaviour using the customer's local database against the vanilla srf files of both versions.

As a result Change Request # 12-J99C6K was raised to address this issue. For any customers encountering this issue please contact your Technical Account Manager and/or Technical Support for further guidance

Keywords: Customizable Product, Customisable, Product Administration, UI Designer, Web Template, Class Administration, Product Designer.

Siebel Technical Support.


Products

---

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

---

IMPORT; INTEGRATION COMPONENT; XSD

Errors

---

SBL-EAI-04394; ERROR 1

SBL-EAI-04392: Could not find a business component that corresponds to the integration component '%1'

Applies to: Siebel Sales Enterprise - Version: 8.1.1 [21112] - Release: V8
Information in this document applies to any platform.

Symptoms
After creating an IO using EAI Siebel Wizard for Opportunity BO, the error SBL-EAI-04392 was raised when trying to use it with EAI Siebel Adapter.

Could not find a business component that corresponds to the integration component 'Opportunity_Approved Registration'(SBL-EAI-04392).

Cause
Siebel inactivate some fields during the IO creation ex. calculated fields.
If a IC is created from a MVG (ex. Opportunity_Approved Registration) and if no corresponding MVF is active in the IC created, this error will be raised.
For this case the unique MVF for this BC was a calculated field that was inactive in the IC "Opportunity_Approved Registration".

SolutionActivate the inactivated IC field (at least one) from the IC that corresponds to the MVG assuring that at least one multi value field used in the underline BC is present and active.
Ex. in the IC Opportunity_Approved Registration, activate the IC field "Calc Approved Items".
Steps:

1. Search for the BC ex. Opportunity


2. In "Multi Value Field" locate the fields related to the MVL used "Approved Registration". In this case you will find just one "Calc Approved Items".


3. Go to the IO created and verify if this field is Inactive. If so, active it


4. Recompile and retest the application.

Applies to: Siebel Reports - Version: 8.1.1.3[21219] and later [Release: V8 and later ]
Information in this document applies to any platform.

SymptomsCustomized Integration Object is built for use with BIP. In Administration - BIP Reports -> Sample Data file Generation -> When we click on "Generate Sample XML" button, Siebel Client crashes.

When we refer to the client_1\log\siebel.log, the following CALL STACK appears:

Exception 0xc0000005 at 0xd04bb4b8
Thread: 0x00002734, Process 0x0000240c

- CONTEXT -
EIP: 0x00313992, EFL: 0x00010246, FS: 0x0000003b, GS: 0x00000000
CS: 0x0000001b, DS: 0x00000023, SS: 0x00000023, ES: 0x00000023
EAX: 0x00cf01c9, EBX: 0x08144a08, ECX: 0x0ccf4b78, EDX: 0x0012e748
ESI: 0x0ccf4b78, EDI: 0x00000000, EBP: 0x00000000, ESP: 0x0012feb8

- CALL STACK -
<invalid> 0xd04bb4b8
sscfcmn +0x18b75 = CSSObjectBase::DoGetErrorMsg() +0x15
sscfcmn +0x19080 = CSSObjectBase::CopyErrorMsg() +0xf0
sscfcmn +0x1953d = CSSObjectBase::DoSetErrorMsg() +0x13d
sscfcmn +0x19be5 = CSSObjectBase::SetErrorMsg() +0xa5
SSCAXMLPWFR +0xef8d = CSSSWEFrameXMLPOutputType::DoInvokeMethod() +0xbcd
SSCAXMLPWFR +0xf84f = CSSSWEFrameXMLPOutputType::DoInvokeMethod() +0x148f
sscaswbc +0x292a9 = CSSSWEFrame::InvokeMethod() +0xe9
sscaswbc +0xc6825 = CSSSWEFrameMgrInternal::InvokeAppletMethod() +0x9f5
sscaswbc +0xa2327 = CSSSWECmdProcessor::InvokeMethod() +0x557
sscaswbc +0xa6f7f = CSSSWECmdProcessor::_ProcessCommand() +0x64f
sscaswbc +0xa7f3d = CSSSWECmdProcessor::ProcessCommand() +0x76d
sscaswbc +0xa8442 = CSSSWECmdProcessor::ProcessCommand() +0xc2
sscaswbc +0x1d1422 = CSSServiceSWEIface::Request() +0x2e2
sscaswbc +0x1d2c5e = CSSServiceSWEIface::DoInvokeMethod() +0x8fe
sscfom +0x188ea = CSSService::InvokeMethod() +0x1ba
siebel +0x25d60 = siebel_xmlns::ElemContainer::GetLocation() +0x25f0
siebel +0x27069 = siebel_xmlns::ElemContainer::GetLocation() +0x38f9
siebel +0x9d37
MFC71U +0x33992 = Ordinal3942() +0x6a
Further analysis of log shows:

ObjMgrBusCompLog Warning 2 000000024d510ca0:0 2011-02-08 07:29:40 (buscomp.cpp (10735)) SBL-DAT-00247: An error has occurred retrieving the multi valued group object for field 'Quote Relation Type Code' .
Please have your systems administrator check your application configuration.

ObjMgrLog Error 1 000000024d510ca0:0 2011-02-08 07:29:40 (adptutils.cpp (5633)) SBL-EAI-04376: Method 'GetMvgBusComp' of business component 'Quote Item' (integration component 'Quote Item') returned the following error:
"An error has occurred retrieving the multi valued group object for field 'Quote Relation Type Code' .

Please have your systems administrator check your application configuration.(SBL-DAT-00247)"

EAISiebAdpt EAISiebAdptWrn 2 000000024d510ca0:0 2011-02-08 07:29:40 Please verify that configurations of integration object and corresponding business object are both valid and in sync.

ObjMgrBusCompLog Warning 2 000000024d510ca0:0 2011-02-08 07:29:40 (buscomp.cpp (10735)) SBL-DAT-00247: An error has occurred retrieving the multi valued group object for field 'Asset Product Part Number' .

Please have your systems administrator check your application configuration.

ObjMgrLog Error 1 000000024d510ca0:0 2011-02-08 07:29:40 (adptutils.cpp (5633)) SBL-EAI-04376: Method 'GetMvgBusComp' of business component 'Quote Item' (integration component 'Quote Item') returned the following error:
"An error has occurred retrieving the multi valued group object for field 'Asset Product Part Number' .

Please have your systems administrator check your application configuration.(SBL-DAT-00247)"

EAISiebAdpt EAISiebAdptWrn 2 000000024d510ca0:0 2011-02-08 07:29:40 Please verify that configurations of integration object and corresponding business object are both valid and in sync.

ObjMgrBusCompLog Warning 2 000000024d510ca0:0 2011-02-08 07:29:40 (buscomp.cpp (10735)) SBL-DAT-00247: An error has occurred retrieving the multi valued group object for field 'Asset Product' .

Please have your systems administrator check your application configuration.

ObjMgrLog Error 1 000000024d510ca0:0 2011-02-08 07:29:40 (adptutils.cpp (5633)) SBL-EAI-04376: Method 'GetMvgBusComp' of business component 'Quote Item' (integration component 'Quote Item') returned the following error:
"An error has occurred retrieving the multi valued group object for field 'Asset Product' .

Please have your systems administrator check your application configuration.(SBL-DAT-00247)"

EAISiebAdpt EAISiebAdptWrn 2 000000024d510ca0:0 2011-02-08 07:29:40 Please verify that configurations of integration object and corresponding business object are both valid and in sync.

ObjMgrLog Error 1 000000024d510ca0:0 2011-02-08 07:29:40 (adptutils.cpp (3510)) SBL-EAI-04392: Could not find a business component that corresponds to the integration component 'Quote Item_Asset'

CauseThe above 3 errors indicate that there is a problem with the configuration of an MVG field.

SolutionIn order to resolve this behavior the decision was taken to inactivate the 3 MVG fields specified in the log file.

Related Products Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel Reports Keywords
CRASH; BI PUBLISHER; DATA; INTEGRATION COMPONENT; GENERATE; DATA FILE
Errors
SBL-EAI-04392; SBL-EAI-04376; SBL-DAT-00247; ERROR 1

SBL-EAI-04390: Multiple matches found for instance of integration component '%1' using search specification '%2' in the business component '%3', based on user key '%4'.

Applies to: Siebel System Software - Version: 7.7.2 SIA [18325] and later [Release: V7 and later ]
Oracle Solaris on SPARC (64-bit)
Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Com/Med
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-3008964956.

SymptomsThe EAI Siebel Adapter (Upsert method) is called with Contact data, but the following error is reported :-

"Multiple matches found for instance of integration component 'Contact' using search specification '[First Name] = "MAHENDRA" AND [Last Name] = "HEMNANI" AND [Work Phone #] = "+54989907987"' in the business component 'Contact', based on user key 'V77 Wizard-Generated User Key:1'.(SBL-EAI-04390)
--
Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Insert Contact'.(SBL-BPR-00162)"

CauseBecause method 'Upsert' was used, customer expectation was that if the record is already there in the database then it should update, otherwise insert.

However, in this case there was more than one record which satisfied the user key fields, hence the error.

SolutionTo avoid the error, ensure the user key for the Integration Component can uniquely identify the record, and that for any given set of user key fields, there are no duplicates. Also see :-

Integration Platform Technologies: Siebel Enterprise Application Integration > About Integration Component Keys > User Keys
"A user key is a group of fields whose values must uniquely identify a Siebel business component record."













Applies to: Siebel Financial Services CRM - Version: 8.0.0.6 SIA [20423] - Release: V8
Information in this document applies to any platform.

Goal
What could be causing the following error message when trying to import a Workflow Process:
Multiple matches found for instance of integration component 'Repository WF Process Prop' using search specification '[Name] = "Error Code"' in the business component 'Repository WF Process Prop', based on user key 'User Key:1'.(SBL-EAI-04390)

Solution
In all known occurrences of error message "SBL-EAI-04390" for integration component "Repository WF Process Prop" the error was caused by duplicate values in a workflow-related LOV Type.
=> Verify the values for these LOV Types: "WF_DATA_TYPE_CD" and "WF_INOUT_TYPE_CD".
If there are any duplicate LOVs please remove them, and activate any LOVs not activated.
=> If this does not help, check all LOV Types called WF_*.
If there are any duplicate LOVs please remove them, and activate any LOVs not activated.

















Applies to: Siebel System Software - Version: 7.8.2.3 SIA [19221] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2.3 [19221] PTG Com/Med
Database: Oracle 9.2.0.6
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Sun Solaris 9

This document was previously published as Siebel SR 38-3248342821.
***Checked for relevance on 11-NOV-2010***

SymptomsSBL-EAI-04390

Requirement is to automatically generate activities using Activity Templates functionality when creating Service Request through the EAI application Tibco, via an Integration Object.

To implement this, following was configured :-

1. Create an Integration Object to create Service Request and an Activity of Type 'Recepção Documento' under Service Request;
2. In Business Component Service Request we have a pickmap in field ‘PTF_GD Subject L0’ to fill the field ‘PTF_GD Activity Template’ (this field save the name of activity template in Service Request) with value defined in list of value of this field;
3. In BusComp_PreSetFieldValue event of Service Request we have code to fill the field ‘PTF_GD Activity Template’, if exist a value of activity template name defined in list of value of field ‘PTF_GD Subject L1’ or ‘PTF_GD Subject L2’ ( the fields PTF_GD Subject L0, PTF_GD Subject L1 e PTF_GD Subject L2 are related hierarchically).
4. In BusComp_WriteRecord event we have code to invoke a workflow that create an Activity Plan if field ‘PTF_GD Activity Template’ is filled with name of activity template;
5. In BusComp_WriteRecord event of Business Component Activity Plan we invoke a workflow named ‘PTF_GD Update Activity Plan Action Workflow’ to fill some custom fields of Business Component Activity Plan Action with values of Business Component Activity Plan;
6. In BusComp_WriteRecord event of Activity Pan Action we invoke a workflow named ‘PTF_GD Position/Activity Plan Action Association’ to create record in intersection table of Activity and Position, for visibility reasons.

When the Insert method of EAI Siebel Adapter was called to create a Service Request and Action, it failed with the following error:

"Siebel InvokeMethod error, for Insert (Localizadas várias corresps para a instância do comp. de integração 'PTF_GD Action' utilizando a especificação de procura '[PTF_GD Integration Id] IS NULL' no Business Component 'PTF_GD Action', com base na chave de utlzr 'V77 Wizard-Generated User Key:1'.(SBL-EAI-04390)).".

In English:

Multiple matches found for instance of integration component 'PTF_GD Action' using search specification '[PTF_GD Integration Id] IS NULL' in the business component 'PTF_GD Action', based on user key 'V77 Wizard-Generated User Key:1'.

CauseThe customer had added code the WriteRecord event on the Service Request bus comp to invoke a workflow that inserted an activity plan against the SR. The log file for the EAI Object Manager task showed that the EAI Siebel Adapter inserted the SR and then started to process the activity. It executed a select statement against S_EVT_ACT to retrieve the any records associated to the SR and then tried to delete one of the activities inserted as part of the activity plan, at which point the error occurred.

The following information is included in the Integration Platform Technologies: Siebel Enterprise Application Integration, EAI Siebel Adapter, EAI Siebel Adapter Methods:

“Insert Method

This method is also similar to the Synchronize method with the exception that the EAI Siebel Adapter generates an error if a matching root component is found; otherwise, it inserts the root component and synchronizes all the children. It is important to note that when you insert a record, there is a possibility that the business component would create default children for the record, which need to be removed by the Insert method. The Insert method synchronizes the children, which deletes all the default children. For example, if you insert an account associated with a specific organization, it will also be automatically associated with a default organization. As part of the Insert method, the EAI Siebel Adapter deletes the default association, and associates the new account with only the organization that was originally defined in the input integration object instance. The EAI Siebel Adapter achieves this by synchronizing the children.”

The important point here is that the Insert method “inserts the root component and synchronizes all the children.” This is why the Siebel Adapter was trying to delete the activities inserted as part of the activity plan and associated to the SR.

SolutionAfter script was removed from the WriteRecord event, the Workflow Process was not invoked and, as a result, the EAI Siebel Adapter completed correctly.

The Workflow Process was instead invoked using a Workflow Policy, after the SR and the activity was inserted. An alternative solution was to invoke the Upsert method on the EAI Siebel Adapter.


Keywords: EAI Siebel Adapter Insert WriteRecord Workflow Process Service Request Activity Plan Action Multiple Matches Found Instance Integration Component

















Applies to: Siebel CRM - Version: 8.0 [20405] and later [Release: V8 and later ]
Information in this document applies to any platform.
***Checked for relevance on 11-NOV-2010***

Symptoms
When using the "Synchronize" operation of the EAI Siebel Adapter, Siebel is giving the following error message :-


SBL-EAI-04390: Multiple matches found for instance of integration component 'Order Entry - Line Items' using search specification '[JUN Oracle Order Line Id] IS NULL' in the business component 'JUN Order Entry - Line Items Copy', based on user key 'User Key:4'.

Cause
The user key field for 'Order Entry - Line Items' was 'JUN Oracle Order Line Id'. When the line items were initially created, this field contained null. It is a requirement for the EAI Siebel Adapter that the user key for an Integration Component is unique :-

Integration Platform Technologies: Siebel Enterprise Application Integration > Integration Objects > About Integration Component Keys >User Keys


"User key is a group of fields whose values must uniquely identify a Siebel business component record."

Solution
At BusComp layer, the "JUN Oracle Order Line Id" was pre-defaulted with the Id field (Predefault Value=Field: 'Id'), and the reported error did not re-occur.



















Applies to: Product Release: V7 (Enterprise)
Version: 7.5.2.216 [16084] Com/Med
Database: Oracle 9.2.0.2
Application Server OS: Sun Solaris 8
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-1040672641.

SymptomsSBL-EAI-04390

create new order and submit order; then auto-asset. Next modify this asset and go to product configurator and change, then click done. Then go to the Order and change status to complete for the line items and then auto-asset and you get the error message "Multiple matches found for Instance of Integration component header using searchspecification Product Id ..."

Will attach log and the error message screenshot.

SolutionMessage 1For the benefit of other users:

Customer observed that clicking 'Auto-Asset' the 2nd time after making changes to the Order line items resulted in the error "Multiple matches found for instance of integration component 'Header' using search specification '[Product Id]="1-232" AND [Integration Id]="1-6RAF0"' in the business component 'Asset Mgmt - Asset - Header', based on user key 'User Key:1'."

Technical Support on analysing the logs generated after enabling SIEBEL_LOG_EVENTS found that the first time the Asset was created it inserted 2 rows in S_ASSET for the same Product Id. This resulted in the 'Multiple Matches' error the 2nd time 'Auto-Asset' was clicked. The reason why there were 2 inserts in S_ASSET table was because the step that queried for the newly created Asset after inserting the 1st row did not return any rows, thus causing the 2nd insert. The query on 'Asset Mgmt - Asset' resulted no rows as customer had created a custom Search specification that caused the newly asseted row not to return.

To resolve the behavior customer removed the custom Search Specification on the 'Asset Mgmt - Asset' Business component.


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

---

INTEGRATION OBJECT; INTERSECTION; EAI SIEBEL ADAPTER; NEW ACCOUNT; ASSOCIATION; BUSINESS COMPONENTS

Errors

---

SBL-EAI-04390

 

SBL-EAI-04389: Required field is missing in instance of Integration Component '%1' with the user key '%2': %3

Applies to: Siebel Marketing - Version: 8.1.1.1 [21211] to 8.1.1.2 - Release: V8 to V8
Information in this document applies to any platform.
SymptomsWhen attempting to import a response using List Import in Siebel 8.1.1.1, the import fails with the following error:
ObjMgrBusCompLog Error 1 000000114b8c2d38:0 2010-03-02 14:17:40 (buscomp.inl (70)) SBL-DAT-00498: '' ist ein obligatorisches Feld. Geben Sie einen Wert fur das Feld ein.

ObjMgrBusCompLog Error 1 000000114b8c2d38:0 2010-03-02 14:17:40 (buscomp.cpp (33454)) SBL-DAT-00498: 'First Name' ist ein obligatorisches Feld. Geben Sie einen Wert fur das Feld ein.

ObjMgrLog Error 1 000000114b8c2d38:0 2010-03-02 14:17:40 (adptutils.cpp (5634)) SBL-EAI-04389: Erforderliches Feld fehlt in Instanz von Integrationskomponente 'List Mgmt Prospective Contact' mit dem Benutzerschlussel '[Id] = "1-85H6AA"': 'First Name' ist ein obligatorisches Feld. Geben Sie einen Wert fur das Feld ein.
(SBL-DAT-00498)

The translation of this would be:
ObjMgrBusCompLog Error 1 000000114b8c2d38:0 2010-03-02 14:17:40 (buscomp.inl (70)) SBL-DAT-00498: '' is a required field. Please enter a value for the field.

ObjMgrBusCompLog Error 1 000000114b8c2d38:0 2010-03-02 14:17:40 (buscomp.cpp (33454)) SBL-DAT-00498: 'First Name' is a required field. Please enter a value for the field.

ObjMgrLog Error 1 000000114b8c2d38:0 2010-03-02 14:17:40 (adptutils.cpp (5634)) SBL-EAI-04389: Required field is missing in instance of Integration Component 'List Mgmt Prospective Contact' with the user key '[Id] = "1-85H6AA"': 'First Name' is a required field. Please enter a value for the field.
(SBL-DAT-00498)


What is strange about this error is that there is a reference to "List Mgmt Prospective Contact", however in the file to be imported and in the mappings, a Contact has been specified, not a prospect.

CauseThe cause of the reported issue was determined to be a new regression introduced in 8.1.1.1 where the data mapping is no longer associated automatically to the import file at the point where the file to be imported is linked to the import job. The following change request documents this issue:

BUG: 10588649 "List Import 8.1: Automatic association of import mappings no longer works with 8.1.1.1 and 8.1.1.2"
SolutionThe following work-around was provided which forces the mappings to be associated to the import file:

go to the "Data Mapping" tab of your import job
click on the button "Create New Mapping"
the "Example Value" should be populated with the first line of data from your import file
now, from the "Input Field", associated the Field from the object that you want to map to your data fileReferencesBUG:10588649 - LIST IMPORT 8.1: AUTOMATIC ASSOCIATION OF IMPORT MAPPINGS NO LONGER WORKS WITH 8.1.1.1 AND 8.1.1.2









Applies to: Siebel CRM - Version: 8.0.0.2 SIA [20412] and later [Release: V8 and later ]
Information in this document applies to any platform.
GoalThe goal is to migrate custom field(s) from a source area to a target area.
A custom Content Object is created with a configured Integration Object.

Steps to reproduce:
1. Application Deployment Manager (ADM) is executed to export the desired field, creating a corresponding XML file.
2. ADM is launched to import the XML file into the target location.
3. The deployment fails with the following error message:
Required field is missing in instance of Integration Component 'AAA' with the user key '[Name] IS NULL': 'Name' is a required field.
Please enter a value for the field.(SBL-DAT-00498)(SBL-EAI-04389)
The deployment does not occur since the user key [Name] is NULL (i.e., missing a value) in the target.
Solution
Please check the following:
1. Confirm that you synchronized the Siebel Integration Object and the Siebel Business Object.
2. Confirm the customized Integration Component/Object has been validated.
3. Confirm the customized Integration Component/Object has been compiled into a new SRF for both the source and target environments.
4. Confirm the source and target SRFs are the same.
5. Confirm a value exists in the source.
6. Compare the respective Business Components/Integration Components in the source with the Business Components/Integration Components in the target.

Result:
The problem was identified as the [Name] field (a key field) was set to ReadOnly.

After the required field was corrected to allow inserts, the deployment succeeded.










Applies to: Siebel CRM - Version: 8.1 [21039] and later [Release: V8 and later ]
Information in this document applies to any platform.
SymptomsWhen migrating Assignment Rules with Workload Distribution rule, the ADM Deploy steps fails with the following error message: "Required field is missing in instance of Integration Component 'Workload Condition' ... Please enter a value for the field.(SBL-DAT-00498)(SBL-EAI-04389)".
CauseADM cannot migrate Assignment Rules with workload conditions, as discussed in Doc ID 1076291.1
SolutionAs a workaround, modify the UDA Workload Rule.

Steps:
1. In "UDA Workload Rule" Integration Object, inactivate the following three Integration Component fields:.
[Workload Condition].[Workload Object Id]
[Workload Condition].[Column Instance]
[Workload Condition].[Column Instance Object Id](Note: [Workload Condition].[Column Instance Object Id] is inactive for 8.1)
ReferencesBUG:10583945 - REQUIRED FIELD IS MISSING IN INSTANCE OF INTEGRATION COMPONENT 'WORKLOAD CONDITION'
NOTE:1076291.1 - ASSIGNMENT RULE IMPORTING ERROR
NOTE:782895.1 - xml file of Assignment Rules gets imported, but data (AM Rules) not seen









Product Release: V7 (Enterprise)
Version: 7.7.2 [18325] Com/Med
Database: Oracle 9.2.0.4
Application Server OS: Sun Solaris 9
Database Server OS: Sun Solaris 8

This document was previously published as Siebel SR 38-1554547402.
SymptomsSBL-DAT-00498, SBL-EAI-04389, SBL-EAI-04400
Hi,

When trying to migrate state models we are getting a number of errors which we cannot resolve. The issue seems to be more with NEW state models which are non-existent in the target system. We get the same error whether we migrate using files or via http. The error messages we are getting as follows:

Required field is missing in instance of Integration Component 'State Model - Transition' with the user key '[From State Name] = "Raised" AND [To State Name] = "Cancelled"': 'Rule Operator' is a required field. Please enter a value for the field.
(SBL-DAT-00498)(SBL-EAI-04389)

EAI Logs:
Cannot find entry 'Automation Failed' in the bounded picklist for the field 'State Name' in integration component 'State Model_State Model - State'(SBL-EAI-04401)

I know the first error message can be resolved by implementing 38-1427981691. For the second error message however it seems that when you import a state model it doesn't want to create the new States?

Can you confirm if you experience the same behaviour and provide a workaround to allow brand new state models to be imported completely.

Thanks,
SolutionMessage 1For the benefit of other readers:
Customer is migrating state models using ADM (Application Deployment Manager) and getting errors. The issue seems to be more with NEW State Models which are non-existent in the target system.
We get the same error whether we migrate using files or via http. The error messages we are getting as follows:

Required field is missing in instance of Integration Component 'State Model - Transition' with the user key '[From State Name] = "Raised" AND [To State Name] = "Cancelled"': 'Rule Operator' is a required field. Please enter a value for the field.
(SBL-DAT-00498)(SBL-EAI-04389)

EAI Logs:
Cannot find entry 'Automation Failed' in the bounded picklist for the field 'State Name' in integration component 'State Model_State Model - State'(SBL-EAI-04401)

I know the first error message can be resolved by implementing 38-1427981691. For the second error message however it seems that when you import a state model it doesn't want to create the new States?


Resolution.
1) Customer had created a new State Model in the source environment.
Customer had created a new State Model and had also populated the values for the States and Transitions.
After populating the values for State Name customer had modified the values for the Description field in the State Model - State List Applet.
After further research it was found that the error was due to the modification done to the Description field in the source system.

... contd 1/2
Message 2... contd 2/2

The Description field value in the target system was different and due to this reason customer was getting error “
Cannot find entry 'Automation Failed' in the bounded picklist for the field 'State Name' in integration component 'State Model_State Model - State'(SBL-EAI-04401)”
2) Once the customer modified the Description value similar to the target system they were able to load the State Models successfully.
3) Please do not modify the value of the Description field after populating the State Name.

Thank you,

Siebel Technical Support
Keywords: ADM, ADM and State Model, State Model, Application Deployment Manager







Applies to: Siebel System Software - Version: 8.0.0.5 [20420] - Release: V8
Information in this document applies to any platform.
SymptomsService Request records were being updated in Siebel. The pick map defined on the business component field 'Account Location' was configured to clear out values for 'Contact Last Name', 'Asset ID' and 'Product' when the 'Account Location' changes.

However, when the same value for 'Account Location' (that exists in BC) arrived in the xml, the value of 'Product' field was cleared out and an error was thrown as below :-

-----
SBL-EAI-04389: Required field is missing in instance of Integration Component 'Service Request' with the user key [XXX] = "Value1" AND [YYY]= "Value2"': 'Product' is a required field. Please enter a value for the field.(SBL-DAT-00498).
------
CauseInspecting the 'Service Request' BC configuration, it was found that 'Product' field that was defined inside the pickmap for 'Account Location was mapped to the field 'Dummy '(so that on changing 'Account Location', the value of 'product' is cleared out).

On the Integration Object, the Integration Object field user property 'PICKLIST' for 'Account Location' was set to Y. Due to this the validation of the picklist field was being done by EAI Siebel Adapter, and Pick was triggered on the BC every incoming request (having same or different value of 'Account Location').

According to Bookshelf (http://download.oracle.com/docs/cd/E14004_01/books/EAI2/EAI2_IntObjs_Understanding11.html#wp216692) :-
---
When an integration component field is created for a Siebel business component field, and the business component field is based on a picklist, the EAI Siebel Adapter or the Object Manager validates the
field. To have the validation done using the EAI Siebel Adapter, the integration component field has a user property with the name PICKLIST and a value of Y; otherwise, validation is done by the Object Manager.
---

Since for same 'Account Location', the value of 'Product' was not supplied in the incoming soap message and validation was done by 'EAI Siebel Adapter', the reported error - 'Product' is a required field. Please enter a value for the field.(SBL-DAT-00498) - was thrown.
SolutionThe error was avoided by deleting/inactivating the Integration Object field user property 'PICKLIST = Y' for the picklist field 'Account Location'. With this setting the picklist field validation was done by the object manager and no longer was Pick triggered for same value of 'Account Location'.
ReferencesSBL-EAI-04389
SBL-DAT-00498











Applies to: Oracle Customer Master Data Management Integration - Version: 2.5 and later [Release: 2.5 and later ]
Information in this document applies to any platform.
SymptomsCustomer records synchronization from UCM (Siebel) to CRM (Siebel) applications (the "SynchCustomerPartyListResponseProvABCS" bpel) was failing at the error from CRM side, complaining the empty "State" field in the account address.

Sample CRM error, observed in the SOAP Fault response (the "SWICustomerPartyInsertOrUpdate" method of the "SWI Customer Party Service" Siebel Inbound Web Service):
Required field is missing in instance of Integration Component 'CUT Address' with the user key '[Row Id] = "1-ABC"': 'State' is a required field. Please enter a value for the field.(SBL-DAT-00498)(SBL-EAI-04389)
The similar inconsistency was also observed in CRM to UCM accounts synchronization: the "State" address field of account, created in CRM (and populated with correct value such as "NY") was not synchronized in the UCM (was left blank). So, on the way back the UCM had to send CRM the empty "State" field.
ChangesThe Siebel CRM instance was enabled to support both kind of AIA PIPs: MDM Customer and Order-to-Bill for Communications. So the "Enable AIA Comm" Siebel CRM application system preference was set to "True".
This setting made (via the "Required" user property) the "State" field required on the "CUT Address" Siebel Business Component (involved in the integration flows).
CauseIncomplete configuration was found. It has been seen in bpel audit trail review of the CRM to UCM synchronization process (the "SyncAccountSiebelReqABCSImp" bpel) that:

1. the Siebel CRM value of "State" field (e.g. "NY") from CRM Application Business Message (ABM) could be successfully mapped to the Common value (e.g. "New York") in the "StateName" field of Enterprise Business Message (EBM), using the "STATE" Domain Value Map (DVM) of SOA Middleware (source column: "SEBL_01", target column: "COMMON")

2. however, the Common Value of "StateName" (e.g. "New York") could NOT be well passed into "State" field of UCM ABM, using the same DVM (source column: "COMMON", target column; "UCM_01").
Because all values of the target column (the "UCM_01") of the "STATE" DVM were EMPTY.
SolutionThe "State" synchronization issue has been resolved, once the "STATE" DVM (e.g. using the SOA ESB Console) was updated, so that the "UCM_01" column was populated. Values from the "SEBL_01" column have been taken as input, since both: UCM and CRM are Applications of he same Siebel CRM software release.
ReferencesNOTE:819603.1 - Siebel 8.1.1 QF1002 for ACR 463: AIA COM 2.4 Order to Active and Order to Bill PIP Enhancements










Applies to: Siebel CRM - Version: 7.8.2.3 [19221] - Release: V7

Information in this document applies to any platform.
SymptomsImport an Inbox Type gives error:
Additionally the following has been observed:
It is also possible that the import goes through without errors. However, after import the newly created Inbox Type has NO values for fields like:
Business Object Name
Integration Object Name
Action Type
This happened although there is a value given in the XML for these fields.
CauseCause for the import error:
The XML file for the Inbox Type refers to a view that is not in the DB you want to import the Inbox Type.
Cuase of the behavior that data is not imported:
The XML file for the Inbox Type refers to a object names that are not in the DB you want to import the Inbox Type
Reason why there is an error for View Name but not for the other objects:
The value that can be entered in these fields must match the according references. E.g. the "Business Object Name" that you can enter for the Inbox Type must match with an existing Business Object defined in the repository. During the import Siebel checks if the values of the XML file match accordingly. When they do not match these values are ignored during import.
The difference why there is an error for "View Name" but not for fields like "Business Object Name", "Integration Object Name" and "Action Type" is that for View Name a User Key is defined in the Integration Component "UInbox Inbox Type View" for Integration Object "UInbox Type Definition".
SolutionIn order to make sure that the import for Inbox Types is successful, please make sure that the values in the XML file for the fields like "View Name","Business Object Name", "Integration Object Name" or"Action Type" do already exist in the DB you import. Additionally, please double-check the Inbox type you have imported in really completely imported and all fields have according values.
NOTE
WORKAROUND:

Additionally, Enhancement Request BUG 10546379 has been logged in order to address the fact that there is no warring during import when referred data does not exist in DB..
ReferencesBUG:10546374 - ERROR DURING IMPORT OF INBOX TYPE (SBL-DAT-00498)(SBL-EAI-04389)
BUG:10546379 - NO WARNINGS DURING IMPORT OF INBOX TYPE WHEN DATA NOT AVAILABLE IN DB









Applies to: Siebel CRM - Version: 8.0.0.3 SIA [20416] - Release: V8
Information in this document applies to any platform.
Symptoms
Deploying assignment rules from dev to test environment via ADM using 'Export to File' and 'Deploy from File' via client application, got the following error during import in target environment:

Required field is missing in instance of Integration Component 'Workload Condition' with the user key '[Condition Column Name] = "Activity Status" AND [WF Link Name] = "Activity"': 'Value' is a required field. Please enter a value for the field.(SBL-DAT-00498)(SBL-EAI-04389)
Cause
Create the new product defect CR 10583945 for this issue:
Required field is missing in instance of Integration Component 'Workload Condition'

The ADM generated xml data file:

- <Workload_spcCondition>
- <__und_undPROPERTIES_und_und>
<Source_spcField>Value</Source_spcField>
<Repository_spcId>1-C9A-1</Repository_spcId>
<Condition_spcColumn_spcId>1-C9A-YG6P</Condition_spcColumn_spcId>
<Pick_spcApplet>Activity Status Pick Applet</Pick_spcApplet>
<Column_spcId>1-C9A-J9C0</Column_spcId>
<WF_spcLink_spcName>Activity</WF_spcLink_spcName>
<Pick_spcList>PickList Action Status</Pick_spcList>
<Workload_spcObject_spcId>1-2SR92</Workload_spcObject_spcId>
<Column_spcInstance>Activity Status</Column_spcInstance>
<Real_spcValue>Closed</Real_spcValue>
<Comparison><></Comparison>
<Inactive>N</Inactive>
<Condition_spcColumn_spcName>Activity Status</Condition_spcColumn_spcName>
</__und_undPROPERTIES_und_und>
</Workload_spcCondition>

Comparison is there:
<Comparison><></Comparison>

Open xml data file with notepad, it shows escape characters for "<>":


<Comparison
>&lt;&gt;</Comparison
>

The escape characters look correct, however ADM import doesn't recognize the operator <>, and it thinks it is blank.


Solution
The CR 10583945 is Open, it hasn't been fixed yet, so no patches available containing the fix for this defect.

Customer does not wish to import the workload rules. The workaround that works was set up ADM deployment project to export only assignment rules without workload rules, and use ADM to export and import. To know how to set up ADM to do that, please refer to the following Doc ID 782895.1:

xml file of Assignment Rules gets imported, but data (AM Rules) not seen (Doc ID 782895.1)

Doc ID 782895.1 is linked to this SR for your review.

Another vanilla data type AssignGroup also has Workload Rule as child data type. If you don't want to import workload rule the same solution is applicable to AssignGroup.
ReferencesNOTE:782895.1 - xml file of Assignment Rules gets imported, but data (AM Rules) not seen










Applies to: Siebel System Software - Version: 7.8.2 SIA [19213] and later [Release: V7 and later ]
z*OBSOLETE: Microsoft Windows Server 2003
Product Release: V7 (Enterprise)
Version: 7.8.2 [19213] Cons Goods
Database: Oracle 10.1.0.4
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: Microsoft Windows 2003 Server

This document was previously published as Siebel SR 38-2629588551.
***Checked for relevance on 11-NOV-2010***
Symptomsthe following error occurred when the customer invoked the Upsert method on the EAI Siebel Adapter using an integration object based on the Retail Objective bus comp:

“(stepexec.cpp (803)) SBL-BPR-00162: Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Upsert'.
(SBL-BPR-00162)--(SBL-DAT-00498)
Error invoking service 'EAI Siebel Adapter', method 'Upsert' at step 'Upsert'.(SBL-BPR-00162)
--
Required field is missing in instance of Integration Component 'Retail Objective' with the user key '[Organization] = "FRANCE CIGARES" AND [Name] = "A107"': 'End Date' is a required field. Please enter a value for the field.
(SBL-DAT-00498)(SBL-EAI-04389)”

The SiebelMessage included a valid value for End Date.
Causebusiness component is based on specialized class and requires that Period Name be instantiated prior to End Date.
SolutionRetail Objective is based on the specialized class CSSBCRetailObjective which is used to implement additional functionality and validation.
The error was resolved after the Retail Objective integration component was modified so that the External Sequence for Period Name was less than the External Sequence for End Date.

Related Products Siebel > Customer Relationship Management > CRM - Enterprise Edition > Siebel System Software Keywords
EAI SIEBEL ADAPTER; REQUIRED FIELD
Errors
SBL-BPR-00162; SBL-EAI-04389; SBL-DAT-00498

For the Inbox Type import, please use an administrator user who has access to all views.: You might still get the error although the View Name does exist in the target DB. This can happen when the user who imports the file has no access to the view. BUG 10546374 has been logged in order to address the fact that the view need to be indeed available to the user who imports the Inbox Type. However, it should be sufficient if the view is registered in the DB (Administration - Application > Views) and compiled into the .srf file.

Steps:
- Go to Inbox Administration > Inbox Types
- Launch Menu > Import Inbox Type
- Select XMLfile
- Press "Import" button

Error
"We detected an Error which may have occurred for one or more of the following reasons:

Required field is missing in instance of Integration Component 'UInbox Inbox Type View' with the user key '[View Name] IS NULL': 'View Name' is a required field. Please enter a value for the field. (SBL-DAT-00498)(SBL-EAI-04389) "
2. In "Workload Condition" Business Component, change "Column Instance" field to be not required.

3. Compile the changes.

4. Deploy the newly compiled SRF.

5. Execute ADM process again.