|
Siebel Public Sector Guide > Administering Benefits Cases > Process of Setting Up Effective Dating for Additional Business Components >
Setting Up Effective Dating for Records with One-To-Many Links
To set up effective dating for records with one-to-many links, complete the tasks in this topic. In this topic, you set up effective dating for the records in the Opportunities view of the Accounts screen as an example. The records in the Accounts screen have a one-to-many link with the records in the Opportunities view. In this example, the parent business component is Account, and the child business component is Opportunity. To set up effective dating for records with one-to-many links, complete the following tasks:
- Creating and Updating the Tables for One-To-Many Effective Dating Records
- Creating and Updating the Business Components for One-To-Many Effective Dating Records
- Configuring the Dialog Box for the Link History Button for One-To-Many Records
- Configuring the Link History Button and Inactive Field in the User Interface for One-To-Many Records
- Configuring the Menu Items in the User Interface for One-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 One-To-Many Effective Dating Records
First, you create a history table for the table for the child business component, and you update the table for the child business component. To create and update the tables for effective dating records
- Log in to Siebel Tools as an administrator.
- Determine the table for the child business component that contains the records for which you want to set up effective dating.
In this example, the name of the table for the records in the Opportunity business component is S_OPTY.
NOTE: To determine this table name, navigate to Business Component in Object Explorer, and find the child business component. This table name appears in the Table column for the child business component.
- 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 table for the child business component.
In this example, the name of the history table is S_OPTY_ED.
The following table includes the values in the columns for the column names in the history table.
|
|
|
|
|
|
|
|
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 |
NULL |
LINK_ED_FLG |
Link ED Flag |
None |
N |
Y |
Character |
1 |
N |
INTER_ROW_ID |
Intersection Table Row Id |
4 |
Y |
N |
Varchar |
15 |
None |
NOTE: For the PAR_ROW_ID column name, the Foreign Key Table column value is S_OPTY.
- Add column names to the table for the child business component.
The following table includes the values in the columns for the additional column names in the table for the child business component.
|
|
|
|
|
|
|
ED_DELETED_FLG |
ED Deleted |
N |
Y |
Character |
1 |
N |
ED_ENABLED_FLG |
ED Enabled |
N |
Y |
Character |
1 |
Y |
- Apply the changes to the tables to the Siebel database.
- Compile the tables into the Siebel Repository File.
Creating and Updating the Business Components for One-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 child business component. To create and update the business components for effective dating records
- 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 Opportunity History.
The following table includes the field and column names for the history business component.
|
|
|
|
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 |
- Compile the history business component into the Siebel Repository File.
- In the child business component, add fields.
The following table includes the values in the columns for the field names in the child business component.
|
|
|
|
ED Deleted Flag |
ED_DELETED_FLG |
True |
N |
ED Enabled Flag |
ED_ENABLED_FLG |
True |
N |
In this example, the child business component is Opportunity.
- In the child business component, add the ED BusComp user property with a value of the name of the history business component.
In this example, the child business component is Opportunity, and the name of the history business component is Opportunity History.
- Compile the child business component into the Siebel Repository File.
- In the PUB Effective Dating project, create a new link between the child business component and the history business component.
- Compile this link into the Siebel Repository File.
- Use this link to add the history business component to the business object for the parent business component.
In this example, the business object for the parent business component is Account.
- Compile the business object into the Siebel Repository File.
Configuring the Dialog Box for the Link History Button for One-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. To configure the dialog box for the Link History button
- Copy the Income 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.
In this example, the name of the copied applet is Opportunity Link ED Popup Applet.
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.
- If you want users to have access to the functionality in the standard-interactivity client, then add the Edit mode to the applet.
- Compile the applet into the Siebel Repository File.
Configuring the Link History Button and Inactive Field in the User Interface for One-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. To configure the Link History button and the Inactive field in the user interface
- Determine the applet that will display the Link History button and the Inactive field.
In this example, the Opportunity List Applet will display the Link History button and the Inactive field.
- For the applet, add the LinkHistory control.
The following table includes the values in the columns for the LinkHistory control.
Caption - String Reference |
|
|
|
|
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.
- 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.
- 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.
- Display the ED Deleted Flag field in the applet, and select the string reference for the Inactive current string value in the Caption - String Reference column.
- Compile the applet into the Siebel Repository File.
Configuring the Menu Items in the User Interface for One-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. To configure the menu items in the user interface
- Determine the applet that will include the menu items.
In this example, the Opportunity List Applet will include the menu items.
- For the applet, add the menu items.
The following table includes the values in the columns for the menu items.
|
|
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. |
- For the applet, add user properties.
The following table includes the values in the columns for the user property names in the applet.
|
|
CanInvokeMethod: EDQueryShowActive |
True |
CanInvokeMethod: EDQueryShowAll |
True |
CanInvokeMethod: SetEDQueryMode |
True |
- Compile the applet into the Siebel Repository File.
|
