Defining Data Load Rule Details

You create and modify data load rules on the Data Load screen. The Data Load Rule screen has three sections:

Note:

Before you create data load rules, ensure that your source system data does not include special characters, which are not supported in Financial Management target applications.

  To define the data load details for a source system:

  1. From Workflow, and then under Data Load, select Data Load Rule.

  2. In Data Load Rule, and then from the Data Load summary task bar, click Add.

  3. In Name, enter the data load rule name.

  4. Select a Category.

    The categories listed are those that you created in the FDMEE setup. See Defining Category Mappings.

    By default only rules that belong to the category selected in POV are displayed. To see all rules, select Show and then All Categories.

  5. Optional: Enter a description.

  6. In Accounting Entity: If the Location has no accounting value, enter the accounting entity.

    If the Location was created with an accounting entity, this field is already populated.

  7. In the *Include Adjustment Periods drop-down select either yes or no from the drop-down.

    Adjustment periods ensure that the FDMEE adjustment periods map correctly to the source system adjustment periods.

    This option is only available for EBS, Peoplesoft, and Fusion.

  8. In the *Period Mapping Type drop-down, select the period mapping type for each data rule.

    Valid options are:

    • Default—The Data Rule uses the Period Key and Prior Period Key defined in FDMEE to determine the Source General Ledger Periods mapped to each FDMEE period included in a Data Rule execution.

    • Explicit—The Data Rule uses the Explicit period mappings defined in FDMEE to determine the Source GL Periods mapped to each FDMEE Period included in a Data Rule execution. Explicit period mappings allow support of additional GL data sources where periods are not defined by start and end dates.

    • None—With source Adaptors use this option to ignore source period mappings. Thus, all imported data rows are mapped to the FDMEE period selected in a Data Rule execution.

    These options are not available for a file-based definition.

  9. Select a Plan Type.

  10. In the *Include Adjustment Periods drop-down select either yes or no from the drop-down.

    Adjustment periods ensure that the FDMEE adjustment periods map correctly to the source system adjustment periods.

    When you explicitly map period 13 to December/Period 12, and select the Include Adjustment Period option, then the following occurs:

    • For YTD balances, then period 13 becomes the ending balance.

    • For PTD balances, then period 13 and December/Period12, are added.

  11. In *Period Mapping Type drop-down, select the period mapping type for each data rule.

    Valid options are:

    • Default—The Data Rule uses the Period Key and Prior Period Key defined in FDMEE to determine the Source General Ledger Periods mapped to each FDMEE period included in a Data Rule execution.

    • Explicit—The Data Rule uses the Explicit period mappings defined inFDMEE to determine the Source GL Periods mapped to each FDMEE Period included in a Data Rule execution. Explicit period mappings allow support of additional GL data sources where periods are not defined by start and end dates.

    • None—Source period mappings are ignored, thus all imported data rows are mapped to the FDMEE period selected in a Data Rule execution.

    The following table outlines the available Period Mapping Types depending on the Location Type and the Import Format Type.

    Table 27. Period Mapping Types

    Location TypeImport Format TypePeriod Mapping

    Default

    Explicit Period Mapping

    Explicit

    Period Mapping Include Adjustment Periods
    With Accounting Entity Standard Yes Yes N/A Yes
    Without Accounting Entity Standard Yes Yes N/A Yes
    With Accounting Entity Source Adapter N/A N/A Yes Explicit: Yes None: N/A
    Without Accounting Entity Source Adapter N/A N/A Yes Explicit: Yes None: N/A
  12. In Accounting Entity, select the accounting entity from the list of values of the source system.

    You can specify the accounting entity on this screen, or when entering location detail. Data Rules in Locations without an Accounting Entity require you to select an Accounting Entity. This functionality is only applicable to Data Rules in a Location using a Standard Import Format.

    The Accounting Entity cannot be modified once the Data Rule has been executed.

  13. To use the PeopleSoft's Commitment Control feature, complete the following:

    • *Period Mapping Type Select Budget—If commitment Ledger Group is the source, then the period mapping type must be Budget.

      Note:

      From PeopleSoft Commitment Control, only Budget Period Data can be extracted. The source calendar / period are determined based on control budget definition in PeopleSoft.

    • As of Date—Select the effective date of records from the source system.

    • Target for Blank Period—Select the target period to use when the source period is blank.

  14. Click Save.

Source filter options by source systems: