Siebel Connector for PeopleSoft > Prebuilt Integration Objects > Overview >

Picking Related Components

When you insert or update rows into the Siebel database it is often necessary to create relationships with other business components through a foreign key. For example, an account has a M:1 relationship with Price Lists. This means that an account will have one price list associated with it. The same price list could be used for several accounts.

For this type of integration, you store a pointer to the appropriate price list row in the account row. In most cases, there are three ways to identify the foreign row by name, ID, or integration ID. In the Account—Price List example, you can use any one of the following three fields to link these two components: PriceList (name of the price list), Price List Id, or Price List Integration Id.

The related row should already exist in Siebel. In the example above, if you put a Price List name in the Account record, that particular Price List must already exist in Siebel. A new Price List row will not be created if it does not exist.


 Siebel Connector for PeopleSoft 
 Published: 18 April 2003