MENU
      Contents x
      Data Load Rules - Required Fields
      • 12 Minutes to read
      • Print
      • Dark
      • PDF
      Contents

      Data Load Rules - Required Fields

      • 12 Minutes to read
      • Print
      • Dark
      • PDF
      Article summary

      Users must select specific mandatory fields to complete the Data Load Rule (DLR) creation process during the Define Data Mappings step. A few additional 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

      The following is the list of Load Items available in the DLRs:

      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:

      Notes:
      • 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.
      Load Sub Item (New Data Rule Load Rule)Define Overall Rule SettingsDefine Data Mappings (Mandatory Fields)
      Segment 1
      1. Credit/Debit
      2. Account Group
      3. Account Type
      4. Currency Type
      5. Normal Data Input Type
      6. Variance Type
      7. Trial Balance
      8. Rollup Operator
      9. Report Category
      1. For the Parent ChildBuild Type, the mandatory fields are:
          1. Child Code
          2. Parent Code or Parent Name
          3. Leaf Node

      2. For the Level Build Type, the mandatory fields depend on the level selected in the Define Overall Rule Settings step.
        • If the Max Number of Levels is set to 1, only the Leaf Code is mandatory.
        • If the Max Number of Levels is set to more than Level 1, users must define both the Leaf Code and the corresponding Level Code or Level Name for each level.

          For example, if the Level is set to 3, the mandatory fields are:
          1. Leaf Code
          2. Level 1 Code or Level 1 Name
          3. Level 2 Code or Level 2 Name
      Segment 2
      1. Currency Code
      2. Rollup Operator
      3. Elim Attribute
      4. Report Category
      Segment 3 to Segment 8
      1. Rollup Operator
      2. Report Category

      Hierarchy Type - Alternate Hierarchies

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

      Load Sub Item (New Data Rule Load Rule)Define Overall Rule SettingsDefine Data Mappings (Mandatory Fields)
      Segment 1Build Type - Parent Child
      1. Hierarchy Name
      2. Parent Code or Parent Name
      3. Child Code
      4. Leaf Node
      5. Rollup Operator

      Note: If the Include in Data File is set to No, then the parameter will not be a mandatory field.

      Build Type - Level
      1. Hierarchy Name
      2. Leaf Code
        • If the Max Number of Levels is set to 1, only the Leaf Code is mandatory.
        • If the Max Number of Levels is set to more than Level 1, users must define both the Leaf Code and the corresponding Level Code or Level Name for each level.

          For example, if the Level is set to 3, the mandatory fields are:
          1. Leaf Code
          2. Level 1 Code or Level 1 Name    
          3. Level 2 Code or Level 2 Name
      3. Rollup Operator
      Segment 2Build Type - Parent Child
      1. Hierarchy Name
      2. Parent Code or Parent Name
      3. Child Code
      4. Leaf Node
      5. Rollup Operator
      6. Elimination

      Note: If the Include in Data File is set to No for Rollup Operator and Elimination, then those two parameters will not be a mandatory field.

      Build Type - Level
      1. Hierarchy Name
      2. Leaf Code
        • If the Max Number of Levels is set to 1, only the Leaf Code is mandatory.
        • If the Max Number of Levels is set to more than Level 1, users must define both the Leaf Code and the corresponding Level Code or Level Name for each level.

          For example, if the Level is set to 3, the mandatory fields are:
          1. Leaf Code
          2. Level 1 Code or Level 1 Name    
          3. Level 2 Code or Level 2 Name
      3. Rollup Operator
      4. Elimination

      Note: If the Include in Data File is set to No for Rollup Operator and Elimination, then those two parameters will not be a mandatory field.

      Segment 3 to Segment 8Build Type - Parent Child
      1. Hierarchy Name
      2. Parent Code or Parent Name
      3. Child Code
      4. Leaf Node
      5. Rollup Operator

      Note: If the Include in Data File is set to No, then the parameter will not be a mandatory field.

      Build Type - Level
      1. Hierarchy Name
      2. Leaf Code
        • If the Max Number of Levels is set to 1, only the Leaf Code is mandatory.
        • If the Max Number of Levels is set to more than Level 1, users must define both the Leaf Code and the corresponding Level Code or Level Name for each level.

          For example, if the Level is set to 3, the mandatory fields are:
          1. Leaf Code
          2. Level 1 Code or Level 1 Name    
          3. Level 2 Code or Level 2 Name
      3. Rollup Operator

      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:

      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.
      Define Overall Rule SettingsDefine Data Mappings

      Time Mapping  -  Down Rows

      Include In Data File  - Yes 

      1. Segment 1 to Segment 8
      2. Fiscal Year
      3. Fiscal Month 
      4. Amount

      Note: If Include in Data File is set to No for any of the Parameters listed in the Define Overall Rule Settings step, the corresponding field (from 1 to 3) will not be mandatory.

      Time Mapping  -  Across Columns

      Include In Data File  - Yes 

      1. Segment 1 to Segment 8
      2. Fiscal Year
        Note: If the Include in Data File is set to No for any of the Parameters listed in the Define Overall Rule Settings step, the corresponding field (from 1 to 2) will not be mandatory.
      3. Month Amount (At least one must be selected). Users can also select multiple Month(n) Amounts.
        Note: If users set the Include in Data File to No for the Fiscal Month, the selected month’s amount must be mapped.

      Time Mapping  -  Across Column by Scenario (applicable only for non-actual Scenario)

      Include In Data File  - Yes 

      1. Segment 1 to Segment 8
        Note: If the Include in Data File is set to No for any of the Parameters listed in the Define Overall Rule Settings step, the corresponding field will not be mandatory.
      2. Month (At least one month must be selected)

      Translations Data

      Note: 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.

      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.

      Define Overall Rule SettingsDefine Data Mappings

      Time Mapping  -  Down Rows

      Include In Data File  - Yes 

      1. Source Column(s)
      2. Amount
      3. Fiscal Year
      4. Fiscal Month

      Note: If Fiscal Year and Fiscal Month are set to No in the Include in the Data File in the Define Overall Rule Settings step, then those two parameters will not be mandatory.

      Time Mapping  -  Across Columns

      Include In Data File  - Yes 

      1. Source Column 
      2. Fiscal Year
        Note: If users set the Include in Data File to No, then the Fiscal Year will not be a mandatory field.
      3. Month’s Amount (At least one must be selected). Users can also select multiple Month(n) Amounts.
        Note: If users set the Include in Data File to No for the Fiscal Month, then the selected month’s amount must be mapped.

      Time Mapping  -  Across Column by Scenario (applicable only for non-actual Scenario)

      Include In Data File  - Yes 

      1. Source Column 
      2. Month (At least one month must be selected)

      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 add Attribute Type(s) on the Transaction Details Setup page, those fields will also become mandatory, along with the fields mentioned in the table below.
      Source Data & Amount ColumnsDefine Data Mappings (Mandatory Fields)
      CCOA & Single Value
      1. Segment 1 to Segment 8
      2. DATETIME
      3. Amount
      CCOA & Debit amount and credit amount
      1. Segment 1 to Segment 8
      2. DATETIME
      3. DEBIT_AMOUNT
      4. CREDIT_AMOUNT
      On Source Segments (with translations)  & Single Value
      1. DATETIME
      2. Source Column(s)
      3. AMOUNT
      On Source Segments (with translations)  & Debit amount and credit amount
      1. DATETIME
      2. Source Column(s)
      3. DEBIT_AMOUNT
      4. CREDIT_AMOUNT

      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.

      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.

      Entity Hierarchy

      Budget 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.

      Define Overall Rule SettingsDefine Data Mappings (Mandatory Fields)

      If Entity type - Based on Segments - Default Budget Entity is selected then the following will be the mandatory fields:

      1. Rollup Operator
      2. Entity
      3. Department
      4. Currency Code


      If Entity type - any of Based on Attributesis selected then the following will be mandatory fields:
      1. Rollup Operator
        Note: If you select any of the attributes, the mapped attributes will be mandatory in Define Data Mappings unless Include In Data File is set to No.

      For the Parent Build Type

      1. Parent Code
      2. Child Code
      3. Leaf Node

      For the Level Build Type

      1. Level Code1 
      2. Leaf Code

      Note: If you have selected level 1, you must select Leaf Code. If you have selected more than 1 level then select n-1 level code. For example, for Level 3, you need to select Level Code1 and Level Code 2.

      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

      Workforce Planning

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

      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. Rate per Hour
      9. Work Hours
      10. Wage Type or Salary

        Additionally, if constant financial segments at the WFP budgeting level on the Define Workforce Planning Budgeting Criteria page are excluded, the users need to load 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.

      Workforce - Employee Actuals

      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.

      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:

      Direct data input basisDefine Data Mappings
      1. Monthly Value 
      2. Annual Value
      1. Employee Number
      2. Compensation Code
      3. Rate
      4. Hour
      5. Default Value    

      Change by Period 

      Time Mapping: Down Rows

      1. Employee Number
      2. Compensation Code
      3. Rate
      4. Hour
      5. Default Value
      6. Fiscal Year
      7. Fiscal Month    

      Change by Period 

      Time Mapping: Across Columns

      1. Employee Number
      2. Compensation Code
      3. Rate
      4. Hour
      5. Fiscal Year
      6. Fiscal Month (at least one month must be selected)

      Change by Period 

      Time Mapping: Across Columns by Scenario

      1. Employee Number
      2. Compensation Code
      3. Rate
      4. Hour
      5. Month (at least one month must be selected)

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

      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.

      Time MappingDefine Data Mappings
      Down Rows
      1. Employee Number
      2. Allocation %
      Across Columns
      1. Employee Number
      2. Fiscal Year
      3. Month’s Allocation (need to select all months)
      Across Columns by Scenario
      1. Employee Number
      2. Month’s Allocation (At least one-month allocation must be selected)


      Note:

      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.

      Currency Exchange Rates

      To complete the Currency Exchange Rates (Load Item) > Load Exchange Rates (Load Sub Item) - 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:

      Define Overall Rule SettingsDefine Data Mappings

      Time Mapping  -  Down Rows

      Include In Data File  - Yes 

      1. Currency
      2. Currency Type
      3. Fiscal Year
      4. Fiscal Month
      5. Amount

      Time Mapping  -  Across Columns

      Include In Data File  - Yes 

      1. Currency
      2. Currency Type
      3. Fiscal Year
      4. Month1 Amount (At least one must be selected). Users can also select multiple Month(n) Amounts.

      Note: If users set the Include in Data File to No in the Define Overall Rule Settings step, those fields will not be mandatory except for the Fiscal Month. The defined Fiscal Month will become a mandatory field.

      Time Mapping  -  Across Columns by Scenario

      Include In Data File  - Yes 

      1. Currency
      2. Currency Type
      3. Month’s Amount (At least one must be selected). Users can also select multiple Month(n) Amounts.

      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.

      Was this article helpful?
      What's Next

        Planful. 150 Spear Street, Suite 1850, San Francisco, CA 94105

      • Copyright © 2025 Planful. All Rights Reserved.

      Terms of Use - Privacy Policy