Creating and Updating the Tables for Many-to-Many Effective Dating Records

First, you create a history table for the intersection table, and you update the intersection table. The intersection table relates to the parent and child business component.

To create and update the tables for effective dating records

  1. Log in to Siebel Tools or Web Tools as an administrator and create a new workspace.

  2. Determine the intersection table that contains the records for which you want to set up effective dating.

    In this example, the name of the intersection table for the records in the Account business component and the Contact business component is S_PARTY_PER.

    Note: To determine this table name, navigate to Link in Object Explorer, and find the link that contains the parent and child business component. This table name appears in the Inter Table column for the link.
  3. Lock the PUB Effective Dating project, and create a history table in this project with a name that is consistent with the name of the intersection table.

    In this example, the name of the history table is S_PARTY_PER_ED.

    The following table includes the values in the columns for the column names in the history table.

    Name User Name User Key Seq Null-able Re-quired Physical Type Length Default

    PAR_ROW_ID

    Parent Id

    1

    N

    Y

    Varchar

    15

    None

    FIELD_NAME

    Field Name

    2

    N

    Y

    Varchar

    75

    None

    FIELD_VALUE

    Field Value

    None

    Y

    N

    Varchar

    250

    None

    EFF_START_DATE

    Effective StartDate

    3

    N

    Y

    Date

    7

    None

    EFF_END_DATE

    Effective EndDate

    None

    Y

    N

    Date

    7

    None

    LINK_ED_FLG

    Link ED Flag

    None

    N

    Y

    Character

    1

    Y

    Note: For the PAR_ROW_ID column name, the Foreign Key Table column value is S_PARTY_PER.
  4. Add column names to the intersection table.

    The following table includes the values in the columns for the additional column names in the intersection table.

    Name User Name Nullable Required Physical Type Length Default

    ED_DELETED_FLG

    ED Deleted

    N

    Y

    Character

    1

    N

  5. Apply the changes to the tables to the Siebel database.

  6. Deliver the changes to the Integration Branch.