Mandatory Fields - Define Data Mappings

Users must select specific mandatory fields to complete the Data Load Rule (DLR) creation process during the Define Data Mappings step. Mandatory fields vary depending on the options selected in the following areas:

• Load Type

• Load Sub-Item

• Build Type (as selected in the Define Overall Settings step)

• Time Mapping

• Parameters set to "Yes" or "No" in the Define Overall Settings step

• Direct data input basis

Load Item - Segment Hierarchies

To complete the Segment Hierarchy or Alternative Hierarchy - DLR creation process, users must map specific fields in the Maps To column in the Define Data Mappings step. The required fields may vary depending on the Build Type selected in the Define Overall Rule Settings step. Also, if the Include In Data File field is set to Yes for any parameter in the Define Overall Rule Settings step, that parameter will become required in the Define Data Mappings step.

Hierarchy Type - Main Hierarchy

The required fields for each combination are detailed in the table below:

Note:

• The number of segments depends on your configuration as defined in the Configuration Task > Define Financial Segments.

• The system displays segment names defined in the Configuration Task > Define Financial Segments.

Hierarchy Type - Alternate Hierarchies

The required fields for Alternate Hierarchies for each combination are detailed in the table below:

Load Item - Data

To complete the Data - DLR creation process, users must map specific fields in the Maps To column in the Define Data Mappings step. The required fields for the Define Data Mappings primarily differ based on the Load Sub Item selected in the New Data Load Rule step. The Load Sub Item can be GL Data, Transaction Data, Transaction Data V2, or Translations Data.

For each Load Sub Item, the required fields differ based on the options chosen for the below parameters on the Define Overall Rule Settings step:

1. Time Mapping - Down Rows or Across Columns.

2. Include in Data File - set to Yes or No.

3. Other than the above two, users might have a mandatory field(s) based on the Data Load Sub Item chosen on the New Data Load Rule step.

The detailed required fields are explained below for each Load Sub Item:

Load Sub Item - GL Data

Note:

The number of segments might vary based on your configuration. The Segment names will be displayed as defined in the Define Financial Segments - Configuration Task.

Load Sub Item - Translations Data

If users have selected more than one translation on the Define Data Mappings page, then the Mandatory column will be based on the maximum number of source columns.

For example, if users have selected 5 source columns on the Translation page, then in the Maps to Column users have to select Source Column 1 to Source Column 5.

Load Sub Item - Transaction Data or Transaction Data V2

The mandatory fields differ based on the Amount Columns and Source Data selected on the Transaction Details Setup page.

• The number of segments might vary based on your configuration and names will be displayed as defined in the Define Financial Segments - Configuration Task.

• Source Column(s) might differ based on the number of Source Columns assigned to the Translations Data Load in the Transaction Details Setup page.

• If users added Attribute Type(s) on the Transaction Details Setup page, those fields will also become mandatory, along with the fields mentioned in the table below.

Load Item - Attributes

Users can load values associated with attributes using the Attributes load item type. In the Define Data Mappings step, users must map the Name in the Maps To column, which is mandatory. Optionally, users can also map the Description.

Load Item - Attributes Hierarchies

Users can load values for an attribute in an attribute hierarchy using the Attributes Hierarchies Load Item Type. The Mandatory Fields in the Define Data Mappings step depend on the levels defined in the Finance Hierarchies Setup. Users must map the level's name in the Map To column.

For example, if two levels are defined, such as Cash_Flow and Variable_Flow, the mandatory fields will be Cash_Flow Name and Variable_Flow Name.

Load Item - Entity Hierarchy

To complete the Budget Entity Hierarchy - DLR creation process, users must map specific fields in the Maps To column in the Define Data Mappings step. The required fields in the Define Data Mappings step differ based on the Build Type selected in the Define Overall Rule Settings step. Additionally, if the Include in Data File is set to Yes for a parameter, those parameters will become mandatory in the Define Data Mappings step.

Load Item - User Information

The required fields for the User Information - DLR creation process in the Define Data Mappings step are:

1. First Name

2. Login

Additionally, if the user sets the Include In Data File to Yes for the following parameters, these parameters will become mandatory in the Define Data Mappings step:

1. Navigation Role

2. Reporting Role

3. Support Role

Load Item -  Workforce Planning

The required fields for each Workforce Planning - DLR creation process in the Define Data Mappings step are explained below:

Load Sub Item - Workforce - Employee Data

The following Data Load Column fields on the Define Overall Rule Settings page are required fields:

1. Employee Number

2. Hire Date

3. Pay Plan Code

4. Employee Name

5. Employee Type Code

6. Position Name

7. Budget Entity Code

8. Salary or Wage Type

9. Rate per Hour

10. Work Hours

Note:

• Rate per Hour and Work Hours are mandatory only if the Salary type is defined as Hourly. Otherwise, these fields are not required.

• For segment allocations, if no default segments are provided, the user must load the segments from the Load Column options.

All the above fields must be mapped in the Maps To column on the Define Data Mappings step to complete the Workforce - Employee Data DLR creation process.

Load Sub Item - Workforce - Employee Actuals

Note:

If you choose to enable Pfw - Workforce Actuals, the Workforce - Employee Actuals option will no longer be available

The following fields are required on the Define Data Mappings step to complete the Workforce - Employee Actuals DLR creation process.

1. Employee Number

2. Employee Name

3. Position Description

4. Employee Type

5. Position Budget Entity

6. Home Budget Entity

7. Segment 1 to Segment 8

   • The number of segments depends on your configuration as defined in the Configuration Task > Define Financial Segments.

   • The system displays segment names defined in the Configuration Task > Define Financial Segments.

8. FiscalYear

9. Month’s Amount (Select any 1 of the months)

Notes:

• Other than Employee Number, Employee Name, and Position Description, the user can select the Default value on the Default Overall Rule Settings step. When you select a default value, that parameter will not be mandatory in the Define Data Mappings step.

• If users set the Include in Data File to No for the Fiscal Month, the selected month’s amount must be mapped.

Load Sub Item - Workforce - Employee Compensation Item

The below table explains the required fields based on the selection of Direct data input basis and Time Mapping on the Define Data Mappings step:

The mentioned required fields must be mapped in the Maps To column to complete the Workforce - Employee Compensation Item DLR creation process.

Load Sub Item - Workforce - Employee Allocations

The required fields on the Define Data Mappings step differ based on the Time Mapping selected on the Define Overall Rule Settings step. To complete the Workforce - Employee Allocations DLR creation process, the required fields below must be mapped in the Maps To column on the Define Data Mappings step.

Notes:

In addition to the fields mentioned in the table, users might find a few required fields based on the below configurations

• Mapped segment(s) in the Define Financial Budget Entity page becomes a required field

• If constant financial segments at the WFP budgeting level on the Define Workforce Planning Budgeting Criteria page are excluded, the user needs to load them from the Load Column option.

Load Sub Item - Pfw - Employee Actuals

The Pfw - Employee Actuals DLR creation process requires specific fields to be defined during the Define Data Mappings step. The required fields depend on the selected Time Mapping option in the Define Overall Rule Settings step: Across Columns or Down Rows. The table below outlines the required fields:

Other than Employee Number, Employee Name, and Position Description, the user can select the Default value on the Default Overall Rule Settings step. When you select a default value, that parameter will not be mandatory in the Define Data Mappings step.

Load Item - Currency Exchange Rates

Load Sub Item - Load Exchange Rates

To complete the Load Exchange Rates - DLR creation process, users must map specific fields in the Maps To column in the Define Data Mappings step. The required fields in the Define Data Mappings step differ based on the Time Mapping selected in the Define Overall Rule Settings step. Additionally, suppose the Include in Data File is set to Yes for a parameter in the Define Overall Rule Settings step. In that case, those parameters will be mandatory in the Define Data Mappings step.

The Mandatory fields are listed in the below table:

Load Item - External Source Model

Users can select a Model from the Load Sub Item for the External Source Model Load type. The selected model’s corresponding fields will appear in the Define Overall Rule Setting step. These fields must be mapped in the Maps to a column in the Define Data Mappings step to complete the External Source Model - DLR creation process.