PurposeThis document is intended to provide cause and corrective action information about Siebel Error Message SBL-EAI-11000: Integration component field '%1' has a dependency on the field '%2' that does not exist in the integration component '%3'.
ScopeThis document is informational and intended for any user.
SBL-EAI-11000: Integration component field '%1' has a dependency on the field '%2' that does not exist in the integration component '%3'.ExplanationThe integration component field has a dependency on another field that cannot be found in the integration component definition.
Corrective ActionMake sure that the integration component field exists and is active.
Applies to: Product Release: V7 (Enterprise)
Version: 7.7.1  Auto
Database: Oracle 126.96.36.199
Application Server OS: Microsoft Windows 2003 Server
Database Server OS: HP-UX 10.0
This document was previously published as Siebel SR 38-1427635831.
Could you please double check the following issues we encountered with ADM? I
found workarounds for most, but it would be great to know if those are known
issues and whether patches will be available soon.
So, here are the objects and the errors I found:
We cannot export to file all the views. Siebel prompts an error related to the
query size (too many records in the query) even though there's more LOV records than Views
and it doesn't fail with that object. I tried changing the FetchSize and
MaxCursors of the buscomp to -1 but didn't work either.
The workaround I found was to add a filter on one field (e.g. "local
access" field) and then the query works. Problem is, we need several files to
handle the views.
By definition, in the Integration Object "UDA List Of Values" , the Siebel
vanilla component "List Of Values Parent (UDA)" has as user key the combination
of fields: Value, Name, Parent.
However, the Siebel vanilla LOV has at least two records that will be treated
as duplicates following that definition (see LOV type where Display Value =
The problem is that the same type exists for different language options.
Therefore, if we export the standard LOV to file and try to import back into
Siebel it fails.
The workaround was to add two more fields to the User Key, "Translate" and
"Order By". Additionally, we will only e...
SolutionMessage 1For the benefit of other readers
Customer is using Application Deployment Manager (ADM) to export all LOV records using export to file option. Customer is trying to import all the exported record into another environment using Deploy from file option (using ADM). In doing so they are getting error "Multiple matches found for instance of integration component '%1' using search specification '%2' in the business component '%3', based on user key '%4'."
The error in customers scenario was because of the duplicate records for Type = LOV_TYPEâ€™ and Display Value = â€˜APPROVAL_DECISION_TYPEâ€™.
I have logged Change Request # 12-MPWXD3 to address this behavior.
Customer was suggested the workaround to modify the value of the Display Value field to make the record unique and they were able to successfully import the data.
Siebel Technical Support