Bookshelf Home | Contents | Index | PDF     

Siebel Content Publishing Guide > Content Center > Configuring Content Objects for Content Center >

Modifying Business Components for Content Center

NOTE:  This step is potentially recursive. Complete this step before using the Integration Object Builder wizard in Siebel Tools to create integration objects.

After you have identified or defined the business object on which your content object is based, check its business components for underlying tables that contain foreign keys to other tables. If there are business components with foreign keys, you must modify them to assure the integrity of foreign keys when these objects are published.

Typically, you need to follow one of the following two processes to modify the business components.

To modify the business components containing foreign keys

  1. Create a join in the business component from each foreign key column to the row_id of the foreign key's table.
  2. Create fields in the business component for all user key columns in the foreign key's table. If any of these columns are foreign keys, repeat Step 1.
  3. Assign a PickList and fill the PickMap with the foreign key and all related user key fields, including any intermediate foreign key fields.
  4. Add Pick Map UpdOnlyIfNull columns for each Id type column in the Pick Map.

    The UpdOnlyIfNull column should be the same one as its parent on the Pick Map.

Or, if the business component table contains a foreign key to a child (or other descendent) object in the business object, complete the following process.

To modify the business components where the business component table contains a foreign key to a child object

  1. Create a Multi Value Link to the business component on the foreign key table.
  2. Include the entire foreign user key as multi-value fields. Expand foreign keys in the user key by joining and adding fields to the Multi Value Link business component.
  3. Set the Primary Id field of the Multi Value Link to the foreign Key column.

NOTE:  To resolve foreign keys to child (descendent) objects in the correct order, you must specify a sequence number and XML sequence number for the resulting integration object.

If two business components joined by a foreign key contain user key columns of the same name, create different field names for each user key column. Table 3 shows an example.

Table 3. Example: How to Handle Identical User Key Column Names
Business Component
User Key Columns
Comments

Internal Product Sales Tool

BU_ID

This is a foreign key from the Internal Product Sales Tool business component to the Organization business component.

NAME

This is a _U1 user key column in the Internal Product Sales Tool business component.

This user key column name is identical to the one in the Organization business component described below.

In the Internal Product Sales Tool, create a field called Name to map to this column.

Organization

NAME

This is a user key column in the Organization business component.

This user key column name is identical to the one in the Internal Product Sales Tool business component described above.

In the Internal Product Sales Tool, create a field called Organization Name to join to this column.

NOTE:  Later, you disable all other user keys, so you only need to check for duplicate names in your business component's _U1 table user key.

  
Siebel Content Publishing Guide Copyright © 2006, Oracle. All rights reserved.