Bookshelf Home | Contents | Index | PDF     

Siebel Public Sector Guide > Administering Benefits Cases > Process of Setting Up Effective Dating for Additional Business Components >

Setting Up Effective Dating for Records with Many-To-Many Links

To set up effective dating for records with many-to-many links, complete the tasks in this topic. In this topic, you set up effective dating for the records in the Contacts view of the Accounts screen as an example. The records in the Contacts view have a many-to-many link with the records in the Accounts screen. In this example, the parent business component is Account, and the child business component is Contact.

NOTE:  Before you complete the tasks in this topic, you must create and update the tables for the parent and child business components, if necessary. For more information, see Creating and Updating the Tables for One-To-Many Effective Dating Records.
You must also create and update the parent and child business components for effective dating, if necessary. For more information, see Creating and Updating the Business Components for One-To-Many Effective Dating Records.

To set up effective dating for records with many-to-many links, complete the following tasks:

  1. Creating and Updating the Tables for Many-To-Many Effective Dating Records
  2. Creating and Updating the Business Components for Many-To-Many Effective Dating Records
  3. Configuring the Dialog Box for the Link History Button for Many-To-Many Records
  4. Configuring the Link History Button and Inactive Field in the User Interface for Many-To-Many Records
  5. Configuring the Menu Items in the User Interface for Many-To-Many Records

NOTE:  After you complete the tasks in this topic, you must implement effective dating tracking for the records. For more information, see Implementing Effective Date Tracking.

This task is a step in Process of Setting Up Effective Dating for Additional Business Components.

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 as an administrator.
  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. Compile the tables into the Siebel Repository File.

Creating and Updating the Business Components for Many-To-Many Effective Dating Records

After you create and update the tables for effective dating records, you create a history business component for the history table, and you update the parent and child business components.

To create and update the business components for effective dating records

  1. Use the wizard to create the history business component in the PUB Effective Dating project using the history table.

    In this example, the name of the history business component is Account Contact ED.

    The following table includes the field and column names for the history business component.

    Field Name
    Column Name
    Join
    Type

    Field Name

    FIELD_NAME

    None

    DTYPE_TEXT

    Field Value

    FIELD_VALUE

    None

    DTYPE_TEXT

    Effective Start Date

    EFF_START_DATE

    None

    DTYPE_UTCDATE

    Effective End Date

    EFF_END_DATE

    None

    DTYPE_UTCDATE

    Created By UserName

    LOGIN

    S_USER

    DTYPE_TEXT
  2. Compile the history business component into the Siebel Repository File.
  3. In the PUB Effective Dating project, create the links between the parent or child business components and the history business components.

    The following table includes the parent business components, child business components, history business components, source fields, and destination fields for each link in this example.

    Link Name
    Parent Business Component
    Child Business Component
    History Business Component
    Source Field
    Destination Field

    Account/Account History

    Account

    None

    Account History

    Id

    Parent Id

    Contact/Contact History

    None

    Contact

    Contact History

    Id

    Parent Id

    Account/Account Contact ED

    Account

    None

    Account Contact ED

    Contact/Account.Id

    Parent Id

    Contact/Account Contact ED

    None

    Contact

    Account Contact ED

    Account/Contact.Id

    Parent Id
  4. Compile these links into the Siebel Repository File.
  5. Use these links to add the history business components to the two business objects for the parent and child business components.

    The following table includes the links to use to add the history business components to the business objects for the parent and child business components in this example.

    Link Name
    History Business Component
    Business Object

    Account/Account History

    Account History

    Account

    Contact/Contact History

    Contact History

    Account

    Contact/Account Contact ED

    Account Contact ED

    Account

    Account/Account History

    Account History

    Contact

    Contact/Contact History

    Contact History

    Contact

    Account/Account Contact ED

    Account Contact ED

    Contact
  6. Compile the two business objects into the Siebel Repository File.
  7. Add a field to the parent and child business component.

    The following table includes the values in the columns for the field name in the parent and child business component.

    Business Component
    Name
    Join
    Column
    Type

    Account

    Contact/Acount.ED_DELETED_FLG

    S_PARTY_PER

    ED_DELETED_FLG

    DTYPE_FLG

    Contact

    Account/Contact.ED_DELETED_FLG

    S_PARTY_PER

    ED_DELETED_FLG

    DTYPE_FLG
  8. Add user properties to the parent and child business component.

    The following table includes the values in the columns for the user property names in the parent and child business component.

    Business Component
    Name
    Value

    Account

    ED Link BusComp:Contact/Account

    Account Contact ED

    Contact

    ED Link BusComp:Account/Contact

    Account Contact ED
  9. Compile the parent and child business component into the Siebel Repository File.

Configuring the Dialog Box for the Link History Button for Many-To-Many Records

After you create and update the business components for the effective dating records, you configure the dialog box that appears when users click the Link History button for the child business component.

In this example, you do not configure the dialog box for the Link History button because this dialog box is already configured. If this dialog box is not configured for your child business component, then complete the steps in this procedure.

To configure the dialog box for the Link History button

  1. Copy the Contact Link ED Popup Applet, rename the copied applet with the name of the child business component for which you want to set up effective dating records, and change the business component for the applet to the history business component for the history table.

    NOTE:  In the List Columns for the applet, make sure that the Effective Start Date field and Effective End Date field appear in the user interface. Also, in the Edit List mode for the applet layout, make sure that the following controls are mapped in the web layout: NewRecord, DeletedRecord, NewQuery, EDRefreshBusComp, and CloseApplet.

  2. If you want users to have access to the functionality in the standard-interactivity client, then add the Edit mode to the applet.
  3. Compile the applet into the Siebel Repository File.

Configuring the Link History Button and Inactive Field in the User Interface for Many-To-Many Records

After you configure the dialog box for the Link History button, you configure the Link History button and the Inactive field in the appropriate applet in the user interface. The Inactive field indicates whether the record is active or inactive.

In this procedure, you configure the Link History button and the Inactive field in the Contacts view of the Accounts screen, but, if necessary, you can also configure the Link History button and the Inactive field in the Accounts view of the Contacts screen.

To configure the Link History button and the Inactive field in the user interface

  1. Determine the applet that will display the Link History button and the Inactive field.

    In this example, the Account Contact List Applet will display the Link History button and the Inactive field.

  2. For the applet, add the LinkHistory control.

    The following table includes the values in the columns for the LinkHistory control.

    Caption - String Reference
    HTML Only
    HTML Type
    Method Invoked
    Runtime

    Select the string reference for the Link History current string value.

    True

    MiniButtonEdit

    ShowPopup

    True

    NOTE:  To select a different button name, you must first create a string reference for the button name in the Symbolic Strings project, and then compile the project into the Siebel Repository File.

  3. Right-click the applet, select Edit Web Layout, move the Link History button to the Edit List mode of the applet.

    NOTE:  If the Edit List mode is not available for the applet, then move the Link History button to the mode of the applet in the view that contains the applet. To determine this mode, navigate to View Web Template Item for the view that contains the applet in Object Explorer. This mode appears in the Applet Mode column for the applet.

  4. For the applet, add user properties to the LinkHistory control.

    The following table includes the values in the columns for the user property names in the LinkHistory control.

    Name
    Value

    Mode

    Edit List

    Popup

    The name of the copied applet for the dialog box. For more information, see Configuring the Dialog Box for the Link History Button for Many-To-Many Records.
  5. Display the Account/Contact.ED_DELETED_FLG field in the applet, and select the string reference for the Inactive current string value in the Caption - String Reference column.
  6. Compile the applet into the Siebel Repository File.

Configuring the Menu Items in the User Interface for Many-To-Many Records

After you configure the Link History button and the Inactive field in the user interface, you configure the menu items in the appropriate applet in the user interface.

In this procedure, you configure the menu items in the Contacts view of the Accounts screen, but, if necessary, you can also configure the menu items in the Accounts view of the Contacts screen.

To configure the menu items in the user interface

  1. Determine the applet that will include the menu items.

    In this example, the Account Contact List Applet will include the menu items.

  2. For the applet, add the menu items.

    The following table includes the values in the columns for the menu items.

    Command
    Menu Text
    Menu Text - String Reference

    PUB Show All ED

    Show All

    Select the string reference for the Show All current string value.

    PUB Show Active ED

    Active Items

    Select the string reference for the Active Items current string value.

    PUB Undelete ED

    Undelete Record

    Select the string reference for the Undelete Record current string value.
  3. For the applet, add user properties.

    The following table includes the values in the columns for the user property names in the applet.

    Name
    Value

    CanInvokeMethod: EDQueryShowActive

    True

    CanInvokeMethod: EDQueryShowAll

    True

    CanInvokeMethod: SetEDQueryMode

    True
  4. Compile the applet into the Siebel Repository File.
    
Siebel Public Sector Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.