Processing Multiple Currencies for Workforce Analytic Applications

In Workforce Analytics applications, each fact, dimension, or reference table that contains monetary values stores the amount in the original currency, along with a code identifying that currency. Generally, these values are stored in fields named *_AMT or *_RT, and CURRENCY_CD. Tables containing monetary values also have a corresponding amount in the base currency of the related business unit. These values are known as base currency equivalent amounts (BCEs). Generally, BCEs are stored in fields named *_BCE_AMT or *_BCE.

When you import source data, the data migration process loads the source amounts and currency codes. The process also by default changes BCE amounts to zero (or to the same value as the related amount field if your jobs have been configured). Then you run a subsequent currency conversion process that populates the BCE amount fields.

In HCM Warehouse and Workforce Rewards, certain Application Engine processes use the BCE amount rather than the amount field. As a result, the data migration process and the subsequent currency conversion process that populates the BCE amount fields are critical. You must remember to run the currency conversion process (PF_MULT_CURR) after loading monetary data. This process correctly supplies all of the BCE amounts for the Workforce Analytics tables in the warehouse. You must run this process before you can use any HCM Warehouse or workforce simulation data. When you run the currency conversion process, the base currency equivalent (*_BCE_AMT or *_BCE) is calculated using the base currency code of the related EPM business unit, the source amount (*_AMT), and the source amount currency code (CURRENCY_CD).

If your system is set up to run in a multiple-currency environment, set up and run the currency conversion process for the following tables and fields in the Operational Warehouse - Enriched (OWE):

Table	Name of Base Currency Equivalent Amount Field	Name of Amount Field
JOB_F00	ANNL_BBASE_BCE_AMT	ANNL_BENEF_BASE_RT
JOB_F00	ANNUAL_BCE_AMT	ANNUAL_RT
JOB_F00	CHANGE_BCE_AMT	CHANGE_AMT
JOB_F00	COMPRATE_BCE_AMT	COMPRATE
JOB_F00	HOURLY_BCE_AMT	HOURLY_RT
JOB_F00	MONTHLY_BCE_AMT	MONTHLY_RT
JOBCODE_D00	SURVEY_SAL_BCE_AMT	SURVEY_SALARY
JOB_INTRADY_F00	ANNL_BBASE_BCE_AMT	ANNL_BENEF_BASE_RT
JOB_INTRADY_F00	ANNUAL_BCE_AMT	ANNUAL_RT
JOB_INTRADY_F00	CHANGE_BCE_AMT	CHANGE_AMT
JOB_INTRADY_F00	COMPRATE_BCE_AMT	COMPRATE
JOB_INTRADY_F00	DAILY_BCE_AMT	DAILY_RT
JOB_INTRADY_F00	CTG_RATE_BCE	CTG_RATE
JOB_INTRADY_F00	GVT_ANLRTNOLOC_BCE	GVT_ANLRTNOLOC
JOB_INTRADY_F00	GVT_ANUITYOFST_BCE	GVT_ANUITYOFST
JOB_INTRADY_F00	GVT_BIWEEKLYRT_BCE	GVT_BIWEEKLYRT
JOB_INTRADY_F00	GVT_BWRTNOLOC_BCE	GVT_BWRTNOLOC
JOB_INTRADY_F00	GVT_COMPRATE_BCE	GVT_COMPRATE
JOB_INTRADY_F00	GVT_DAILY_RT_BCE	GVT_DAILY_RT
JOB_INTRADY_F00	GVT_DLYRTNOLOC_BCE	GVT_DLYRTNOLOC
JOB_INTRADY_F00	GVT_FEHB_PCT_BCE	GVT_FEHB_PCT
JOB_INTRADY_F00	GVT_FGLIBSCPCT_BCE	GVT_FGLIBSCPCT
JOB_INTRADY_F00	GVT_FGLIOPTPCT_BCE	GVT_FGLIOPTPCT
JOB_INTRADY_F00	GVT_HRLYRTNOLC_BCE	GVT_HRLYRTNOLC
JOB_INTRADY_F00	GVT_LIVING_AMT_BCE	GVT_LIVING_AMT
JOB_INTRADY_F00	GVT_LOCALITYADJ_BCE	GVT_LOCALITYADJ
JOB_INTRADY_F00	GVT_MNLYRTNOLC_BCE	GVT_MNLYRTNOLC
JOB_INTRADY_F00	HOURLY_BCE_AMT	HOURLY_RT
JOB_INTRADY_F00	MONTHLY_BCE_AMT	MONTHLY_RT
JOB_INTRADY_F00	UNION_FEE_AMT_BCE	UNION_FEE_AMOUNT
SAL_GRADE_D00	MAX_RT_ANN_BCE_AMT	MAX_RT_ANNUAL
SAL_GRADE_D00	MAX_RT_HR_BCE_AMT	MAX_RT_HOURLY
SAL_GRADE_D00	MAX_RT_MON_BCE_AMT	MAX_RT_MONTHLY
SAL_GRADE_D00	MID_RT_ANN_BCE_AMT	MID_RT_ANNUAL
SAL_GRADE_D00	MID_RT_HR_BCE_AMT	MID_RT_HOURLY
SAL_GRADE_D00	MID_RT_MON_BCE_AMT	MID_RT_MONTHLY
SAL_GRADE_D00	MIN_RT_ANN_BCE_AMT	MIN_RT_ANNUAL
SAL_GRADE_D00	MIN_RT_HR_BCE_AMT	MIN_RT_HOURLY
SAL_GRADE_D00	MIN_RT_MON_BCE_AMT	MIN_RT_MONTHLY
SAL_STEP_D00	ANNUAL_BCE_AMT	ANNUAL_RT
SAL_STEP_D00	HOURLY_BCE_AMT	HOURLY_RT
SAL_STEP_D00	MONTHLY_BCE_AMT	MONTHLY_RT
WA_BEN_HST_F00	WA_ANNUAL_BCE_AMT	WA_ANNUAL_AMT
WA_COMP_HST_F00	WA_AMOUNT_BCE	WA_AMOUNT
WA_RECR_EXP_F00	PER_EE_CST_BCE_AMT	PER_EE_COST
WA_TRNCST_F00	PER_EE_CST_BCE_AMT	PER_EE_COST
WA_TRNCST_F00	TUIT_REIMB_BCE_AMT	TUIT_REIMB_AMT

Note: For any configured fields other than those delivered, modify the delivered Application Engine process, job, and rule sets to include your custom fields. If your implementation does not have a multiple currency environment, you do not need to run the currency conversion process by remapping the Extract, Transform, and Load (ETL) jobs to supply all BCE amounts with the corresponding source amounts.

Prerequisites

Before you run the Multicurrency engine, you must properly set up your currency conversion rules using the Currency Conversion Rule page. Follow these steps:

Access the Currency Conversion Rule page.
Click the Add button to add a new currency conversion rule.
Enter an effective date, status, and rate type.
In the From Currency Code Column field, enterCURRENCY_CD.
In the To Currency Code Column field, enterCURRENCY_CD.

The field name here does not matter because the multicurrency processing uses the base currency value for the business unit. However, this field name is mandatory on the currency mapping page.