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 file
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]
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
><></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.
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.
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:
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 file
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].[Column Instance]
[Workload Condition].[Column Instance Object Id]
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
><></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
| |
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.
No comments:
Post a Comment