SetIDs, Business Units, and Currency Conversion
SetIDs or business units are mapped separately in PeopleSoft EPM and do not use the structure that is established in other PeopleSoft application tables. If the data that you import has a different base currency than the base currency for the data warehouse table to which you import the source data, you must define a currency conversion rule. Keep these basic principles in mind when you move data into PeopleSoft EPM and when you work with the PeopleSoft Scorecard system:
Every data warehouse table that is a fact table (*_F00) is keyed by business unit.
Fact tables contain monetary amounts in a given currency (CURRENCY_CD) and in a base currency equivalent amount (BCE_AMT) if the original data was in a different base currency prior to import into the system.
Every data warehouse table that is a dimension (*_D00) or reference (*_R00) table is keyed by SetID.
Only one base currency code exists per SetID.
Any SetID that is mapped to another SetID must have a common base currency code. Any business unit must map to a SetID with a common currency code.
Only one business unit is allowed per scenario, and every business unit has one base currency.
So every scenario can have only one base currency.
The basic extract, transform, and load rule (ETL rule) for importing a PeopleSoft application's source table data is to first find the base currency for a given SetID from the corresponding business unit.
If the imported data currency code does not equal the base currency code for the EPM SetID and business unit, the ETL system calculates and supplies the amount for the base currency equivalent field.
For employee-level tables, the rule is to find the employee ID on the Job table and use the corresponding business unit and base currency.
For employee-level tables such as JOB_F00, base currency is derived from the business unit.
KPIs are keyed by SetID; scorecards are keyed by business unit.
During KPI processing, to properly convert any monetary amounts that are not in a business unit's base currency, the system uses a currency conversion rule named KP_CONVERT (for each SetID). This rule is provided as part of the sample data within the SHARE SetID. To review currency rules, access the Currency Conversion Rule page by selecting Unless you have specific reasons for configuring it differently, you should set up this rule with the selections shown in this example; Rate Type is the one field that you might modify.
Image: Currency Conversion Rule page (PF_MC_RULE_DFN1), displaying the KPI currency conversion rule
This example illustrates the fields and controls on the Currency Conversion Rule page (PF_MC_RULE_DFN1), displaying the KPI currency conversion rule. You can find definitions for the fields and controls later on this page.
When the rate type is blank, the system uses the rate type that is defined for each business unit. This enables each business unit that shares this conversion rule to use different rate types for the conversion. Therefore, you could set up one SetID, and all business units within it could use this conversion rule.
If you enter a rate type, then all business units within that SetID will use the rate type that is specified for KPI currency conversion. If you need to use a different rate type for a given business unit, it must be defined under a different SetID. Therefore, when you enter the rate type, if you need to have any business units that use different rate types (and accordingly, different conversion rules), you'll need to use multiple SetIDs.
On the KPI Definition - Definition page, the Measure Type field should be set to Currency for any KPIs that involve currency amounts. Selecting this option instructs the system to convert foreign currency amounts to the business unit's base currency automatically during KPI processing.