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

Setting Up Effective Dating for Fields

To set up effective dating for the fields in an additional business component that is not preconfigured for effective dating, complete the tasks in this topic. In this topic, you set up effective dating for the fields in the Account business component as an example, but you can set up effective dating for the fields in another business component.

To set up effective dating for fields, complete the following tasks:

1. Creating and Updating the Tables for Effective Dating Fields
2. Creating and Updating the Business Components for Effective Dating Fields
3. Configuring the Dialog Box for the Effective Date Button

NOTE:  After you complete the tasks in this topic, you must set up the view of field history. For more information, see Setting Up the View of Field History.

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

Creating and Updating the Tables for Effective Dating Fields

First, you create a history table for the table for the base business component, and you update the table for the base business component.

To create and update the tables for effective dating fields

1. Log in to Siebel Tools as an administrator.
2. Determine the table for the base business component that contains the fields for which you want to set up effective dating.

   In this example, the name of the table for the appropriate fields in the Account business component is S_PARTY. (For party-based business components, such as Account, Contact, and Household, the name for the table is S_PARTY.)

   NOTE:  To determine this table name, navigate to Business Component in Object Explorer, and find the base business component. This table name appears in the Table column for the base business component.

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 table for the base business component.

   In this example, the name of the history table is S_ORG_EXT_ED. For party-based business components, use a history table name that is consistent with the extension table name for the party-based business component.

   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	NULL
   LINK_ED_FLG	Link ED Flag	None	N	Y	Character	1	N
   LAST_RECONCILED_NUM	Eligibility Processed	None	N	Y	Integer	None	-1
   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_PARTY.

4. Add column names to the table for the base business component.

   The following table includes the values in the columns for the additional column names in the table for the base business component.

   Name	User Name	Nullable	Required	Physical Type	Length	Default
   ED_DELETED_FLG	ED Deleted	N	Y	Character	1	N
   ED_ENABLED_FLG	ED Enabled	N	Y	Character	1	Y

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 Effective Dating Fields

After you create and update the tables for effective dating fields, you create a history business component for the history table, and you update the base business component.

To create and update the business components for effective dating fields

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 History.

   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 base business component, add fields.

   The following table includes the values in the columns for the field names in the base business component.

   Name	Column	Force Active	Predefault Value
   ED Deleted Flag	ED_DELETED_FLG	True	N
   ED Enabled Flag	ED_ENABLED_FLG	True	N

   In this example, the base business component is Account.

4. In the base business component, add the ED BusComp user property with a value of the name of the history business component.

   In this example, the base business component is Account, and the name of the history business component is Account History.

5. For each field in the base business component for which the Required column is selected, add the ED Control Expr user property and include the following value for this user property:

   Required Field Name IS NOT NULL.

   In this value, Required Field Name is the name of field in the base business component for which the Required column is selected.

   This step ensures that field effective dating is implemented after a user creates a record, and not when the user creates the record.

6. Compile the base business component into the Siebel Repository File.
7. In the PUB Effective Dating project, create a new link between the base business component and the history business component.
8. Compile this link into the Siebel Repository File.
9. Use this link to add the history business component to the business object for the base business component.

   In this example, the business object for the base business component is Account.

10. Compile the business object into the Siebel Repository File.

Configuring the Dialog Box for the Effective Date Button

After you create and update the business components for the effective dating fields, you configure the dialog box that appears when users click the effective date button for the base business component.

To configure the dialog box for the effective date button

1. Copy the Contact Field ED Popup Applet, rename the copied applet with the name of the base business component for which you want to set up effective dating fields, 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 Account Field ED Popup Applet.

   NOTE:  In the List Columns for the applet, make sure that the Field Value field, 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, PopupQueryComboBox, SetFieldContext, 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.