Defining Your Operational Structure

When you set up the Enterprise Performance Management (EPM) system, you define your operational structure using business units and SetIDs. This section reviews the logic that is specific to Workforce Analytics regarding the determination of business units, SetIDs, and currency codes when you are bringing workforce data into EPM.

Here are some common principles of the Operational Warehouse data structures and data migration logic:

• All fact tables (F00s) are keyed by business unit.

• Generally, dimension tables (D00s) are keyed by SetID, but depending on the source table or the business need of the EPM application, they may contain business units instead.

• Generally, reference tables (R00s) are keyed by SetID, but depending on the source table or the business need of the EPM application, they may contain business units instead.

• Each EPM business unit has one base currency code to support integrated data analysis on a common point.

• Each fact, dimension, or reference table that contains monetary values has an amount in the base currency of the related business unit (*_BCE_AMT or *_BCE), and an amount in another currency with a code identifying that currency (*_AMT and CURRENCY_CD).

• Each dimension or reference table that contains monetary values must have a SetID that relates only to business units with common base currency codes. (For example, if you have a salary structure defined in Canadian dollars that is keyed by a SetID, that SetID must relate only to business units with a base currency of Canadian dollars.)

The data migration logic that is specific to Workforce Analytics arises when the source table from Human Resources Management System (HRMS) has neither a business unit nor a SetID as a key. When this is the situation, you define the business unit or SetID to use, with the exception being tables that are keyed by employee ID. In this case, the business unit and corresponding base currency code are retrieved from the employee's job record.