Activating Inactive Dimension Keys in the PS_F_LEDGER Table
The PS_F_LEDGER fact table is delivered with the following active dimension keys:
|
Active Dimension Keys |
Active Dimension Keys |
|---|---|
|
BU_SID |
OPER_UNIT_SID |
|
PPERIOD_SID |
FUND_CODE_SID |
|
LEDGER_SID |
PRODUCT_SID |
|
ACCOUNT_SID |
PROJECT_SID |
|
ALT_ACCT_SID |
BUDGET_REF_SID |
|
DEPT_SID |
STAT_CODE_SID |
|
SUBLEDGER_SID |
SCENARIO_SID |
|
AFFILIATE_BU_SID |
CURRENCY_CD |
The following inactive columns can be activated as additional dimension keys:
|
Inactive Dimension Key Columns |
Inactive Dimension Key Columns |
|---|---|
|
CBU_SID |
ADJUST_TYPE_SID |
|
PROGRAM_FDM_SID |
CLASS_FIELD_SID |
|
AFF_OU_SID |
CHARTFIELD1_SID |
|
AFF_FUND_SID |
CHARTFIELD2_SID |
|
BOOK_CODE_SID |
CHARTFIELD3_SID |
To activate inactive dimension keys, you will use the PeopleSoft Application Designer and IBM WebSphere DataStage tools.
Configuring PS_F_LEDGER in Application Designer
To activate additional dimension keys in the PS_F_LEDGER table:
Open PeopleSoft Application Designer.
Select File, Open from the menu.
In the Open Definition dialog box, select Record for the Definition field, then enter F_LEDGER.
The Record Fields tab for the PS_F_LEDGER table appears. Note the inactive dimension keys.
In the Record Fields tab, right-click an inactive dimension key and select Record Field Properties.
The Record Field Properties window appears for the column.
In the Use tab of the Record Field Properties window select the Key and Search Key check boxes.
Click OK to continue.
Save your changes.
Select Build, Project from the menu.
The Build window appears.
In the Build window select the Create Indexes and Execute and Build Script check boxes.
Select Settings.
The Build Settings window appears.
In the Create tab of the Build Settings window, select the Recreate Index only if Modified check box.
Click OK to continue.
Click Build to complete your configuration of the PS_F_LEDGER table.
Repeat steps 4 through 13 to activate other inactive dimension keys in the PS_F_LEDGER table.
Configuring the J_Fact_PS_F_LEDGER ETL Job in DataStage
To configure the new keys in the J_Fact_PS_F_LEDGER job:
In DataStage Designer client, navigate to the J_Fact_PS_F_LEDGER job in the project tree and open it for editing.
Image: J_Fact_PS_F_LEDGER job in the project tree
This example illustrates the fields and controls on the J_Fact_PS_F_LEDGER job in the project tree. You can find definitions for the fields and controls later on this page.
Open the DRS target stage (DRS_PS_F_LEDGER) and select the Inputs tab.
Select the Columns sub-tab and locate each column you have activated as a key in Application Designer.
For each column you have activated as a key in Application Designer, select Yes for the Key field.
Image: Specifying keys in the DRS_PS_F_LEDGER target stage
This example illustrates the fields and controls on the Specifying keys in the DRS_PS_F_LEDGER target stage. You can find definitions for the fields and controls later on this page.
Note: Ensure that you add all the same keys that you added in Application Designer.
Click OK to continue, then save your changes.
Repeat steps 2 through 5 for the DRS_PS_F_LEDGER_UPD target stage.
Open the HASH_PS_F_LEDGER hashed file to configure the new keys in the lookup.
In the HASH_PS_F_LEDGER hashed file, select the Inputs tab, then the Columns sub-tab.
Select the Key field check box for each column you have activated as a key in the target DRS stage.
Image: Specifying keys in the HASH_PS_F_LEDGER hashed file
This example illustrates the fields and controls on the Specifying keys in the HASH_PS_F_LEDGER hashed file. You can find definitions for the fields and controls later on this page.
Click OK to continue, then save your changes.
Repeat steps 7 through 10 for the HASH_F_LEDGER_INC_UPDATE and HASH_PS_F_LEDGER_AVERAGE hashed files.
Open the Trans_Assign_Values stage to map the newly activated keys in the hashed files to the source columns.
Image: Mapping keys in the Trans_Assign_Values stage
This example illustrates the fields and controls on the Mapping keys in the Trans_Assign_Values stage. You can find definitions for the fields and controls later on this page.
Click OK to continue, then save your changes.
Configuring the Related ETL Job J_Fact_PS_F_LEDGER_LEDGER_BUDG in DataStage
The job J_Fact_PS_F_LEDGER_LEDGER_BUDG also loads the PS_F_LEDGER table and must be configured to include new keys.
To configure the new keys in the J_Fact_PS_F_LEDGER_LEDGER_BUDG job:
In DataStage Designer client, navigate to the J_Fact_PS_F_LEDGER_LEDGER_BUDG job in the project tree and open it for editing.
Image: J_Fact_PS_F_LEDGER_LEDGER_BUDG job in the project tree
This example illustrates the fields and controls on the J_Fact_PS_F_LEDGER_LEDGER_BUDG job in the project tree. You can find definitions for the fields and controls later on this page.
Open the DRS target stage (DRS_PS_F_LEDGER) and select the Inputs tab.
Select the Columns sub-tab and locate each column you have activated as a key in Application Designer.
For each column you have activated as a key in Application Designer, select Yes for the Key field.
Image: Specifying keys in the DRS_PS_F_LEDGER target stage
This example illustrates the fields and controls on the Specifying keys in the DRS_PS_F_LEDGER target stage. You can find definitions for the fields and controls later on this page.
Note: Ensure that you add all the same keys that you added in Application Designer.
Click OK to continue, then save your changes.
Open the HASH_PS_F_LEDGER hashed file to configure the new keys in the lookup.
In the HASH_PS_F_LEDGER hashed file, select the Inputs tab, then the Columns sub-tab.
Select the Key field check box for each column you have activated as a key in the target DRS stage.
Image: Specifying keys in the HASH_PS_F_LEDGER hashed file stage
This example illustrates the fields and controls on the Specifying keys in the HASH_PS_F_LEDGER hashed file stage. You can find definitions for the fields and controls later on this page.
Click OK to continue, then save your changes.
Repeat steps 8 through 10 for the HASH_PS_F_LEDGER1 hashed file.
Open the Trans_Assign_Values stage to map the newly activated keys in the hashed files to the source columns.
Image: Mapping keys in the Trans_Assign_Values stage
This example illustrates the fields and controls on the Mapping keys in the Trans_Assign_Values stage. You can find definitions for the fields and controls later on this page.
Click OK to continue, then save your changes.