Mapping Personnel Actions for JOB_F00

To map personnel actions for JOB_F00, use the WA_ACTN_RSN_DFN.GBL component.

This section discusses how to:

Review source table action and reason codes.
Define action types.
Map action and reason combinations.
Review your personnel action mappings.
Load your personnel action data.

Pages Used to Map Personnel Actions for JOB_F00

Page Name	Definition Name	Navigation	Usage
Action Type	WA_ACTION_TYPE	select EPM Foundation, then select Business Metadata, then select OW-E Dimension Maintenance, then select HRMS, then select Common, then select Action Type.	Define personnel action types, and map them to personnel action types from benchmark metrics surveys. The primary purpose of the action type definition is to facilitate roll-up and drilldown for this attribute in the HCM Warehouse Insight analysis templates.
Action Reason Map	WA_ACTN_RSN_DFN	select EPM Foundation, then select Business Metadata, then select OW-E Dimension Maintenance, then select HRMS, then select Common, then select Action Reason Map.	Map action and reason combinations from your HRMS system to the Voluntary Term (voluntary termination) field in EPM. You can also map the action and reason combinations to benchmark survey action type codes on using this page. The two primary purposes of these attributes are to facilitate high-level action counts and turnover metrics in the HCM Warehouse Insight analysis templates.

Reviewing Source Table Action and Reason Codes

Review your HRMS source table (PS_ACTN_REASON_TBL) and identify all the valid combinations of action code and reason code that you want to use in EPM. Then determine whether they should map to one of the workforce termination values: Voluntary,Involuntary, orNot a Termination.

Also review your HRMS source table action codes and determine which action types to group them into. For example, your human resources organization may already have standard action types, or you may want to use the same action types used by your company's third-party provider of benchmark metric data.

Action Type Page

Use the Action Type page (WA_ACTION_TYPE) to define personnel action types, and map them to personnel action types from benchmark metrics surveys.

The primary purpose of the action type definition is to facilitate roll-up and drilldown for this attribute in the HCM Warehouse Insight analysis templates.

Navigation

select EPM Foundation, then select Business Metadata, then select OW-E Dimension Maintenance, then select HRMS, then select Common, then select Action Type.

Image: Action Type setup page

This example illustrates the fields and controls on the Action Type setup page. You can find definitions for the fields and controls later on this page.

Note: No ETL job is delivered for the WA_ACTION_TYPE table. You define action types online prior to running ETL.

Warning! The action type values of HIR (Hire), OTH (Other), PRO (Promotion), SEP (Separation), and XFR (Transfer) are hard-coded in the data mart processing logic.

Action Type

The personnel action type code that you entered to access this page is displayed at the top of the page. After you've created these codes, you can use them on the Action Reason Map page.

Benchmark Action Type

Select a benchmark action type from the list of valid values. You map your action type to a standardized personnel action type that is used in many benchmark metrics surveys. Valid values are Hire,Other,Promotion,Separation, andTransfer.Other includes all other action types that are not hires, separations, transfers, or promotions.

Action Reason Map Setup Page

Use the Action Reason Map page (WA_ACTN_RSN_DFN) to map action and reason combinations from your HRMS system to the Voluntary Term (voluntary termination) field in EPM.

You can also map the action and reason combinations to benchmark survey action type codes on using this page. The two primary purposes of these attributes are to facilitate high-level action counts and turnover metrics in the HCM Warehouse Insight analysis templates.

Navigation

select EPM Foundation, then select Business Metadata, then select OW-E Dimension Maintenance, then select HRMS, then select Common, then select Action Reason Map.

Image: Action Reason Map setup page

This example illustrates the fields and controls on the Action Reason Map setup page. You can find definitions for the fields and controls later on this page.

Note: No ETL job is delivered for the WA_ACTN_RSN_DFN table. You map action and reason combinations online prior to loading the OWE table.

Action Code

To open the page, you select an action code, which is a translate table value. The valid values are based on the translate table values for the action code field in HRMS.

Reason Code

Enter a reason code, if one exists. Enter only what you consider valid combinations of action and reason from HRMS. For example, your organization may not want to use a combination in which the action is Separation, and the reason isNull.

Voluntary Term (voluntary termination)

In workforce analytic applications, some of the turnover metrics in the data marts require the ability to define whether an action and reason combination results in a termination, and whether the termination is voluntary or involuntary. Enter the voluntary termination code to which you want to map this action and reason combination. Valid values are from the translate table, and include Involuntary,Voluntary andNot a Termination.

Action Type

Enter the action type to which you want to map this action and reason code combination. Prompt values are from the WA_ACTION_TYPE table, which you created using the Action Types setup page.

Loading Your Personnel Action Data

After you've completed the two mapping pages, use ETL to import your personnel action data into the data warehouse tables. For each incoming row of employee data, the process validates the reason code against the WA_ACTN_RSN_DFN table. If a mapping exists, then the system places the appropriate value (voluntary, involuntary, or not a termination), along with the row of data, into the Job Data (JOB_F00) table. If no reason code mapping is on the WA_ACTN_RSN_DFN table, then the data goes to the error table.