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

Related Business Component Selection in Database Updates

When a row is inserted or updated in the Siebel database, it is often necessary to create relationships with other business components through a foreign key. For example, an account has a many-to-one relationship with Price List—an account is associated with one price list; the same price list can be used with different accounts. The correct price list is identified by the foreign key Price List Id, which exists in the Account component. This relationship is implemented through the picklist.

For this type of integration, a pointer to the appropriate price list row is stored in the account row, where it is identified by a foreign key.