Siebel Application Services Interface Reference > Application Services Interfaces > About Integration Object Structure >

Unique Keys in Integration Objects


Internal integration objects implement user keys that the Siebel application creates for each component, based on the user primary key defined for the underlying table. User keys are a group of fields whose values uniquely identify only one Siebel record. When an ASI executes, it searches the list of user keys to find the first key present in the component instance and uses it to determine whether the record has a match in the Siebel database.

You can deactivate, modify, or create additional keys for an ASI depending on your business and application needs. However, it is recommended that each component contain a set of three unique keys:

  • Row ID. The Siebel Row ID.
  • Integration ID. A cross-reference that links the Siebel application to the corresponding record in the external application.
  • User Key. Corresponds to the U1 index of the underlying table.
Siebel Application Services Interface Reference Copyright © 2017, Oracle and/or its affiliates. All rights reserved. Legal Notices.