Adding Data Load Rules

After you define member mappings for the location, define data load rules for ledgers or business units in your source system to extract the data from the Oracle General Ledger and move it to the EPM application.

Data load rules are defined for locations that you have already set up. Data load rules are specific to locations. You can create multiple data load rules for a target application so that you can import data from multiple sources into a target application.

The data load rule is created once, but used each time there is a transfer.

To create a data load rule for synchronization:

  1. On the Workflow tab, under Data Load, select Data Load Rule.
  2. From the POV Bar, select the location to use for the data load rule.

    Data load rules are processed within the context of a point of view. The default point of view is selected automatically. The information for the point of view is shown in the POV bar at the bottom of the screen.

  3. Click Add
  4. In Name, enter the name of the data load rule.
  5. In Category, leave the default category value.

    The categories listed are those that you created in the Oracle Hyperion Financial Data Quality Management, Enterprise Edition setup. See Defining Category Mappings.

  6. In Period Mapping Type, select the period mapping type for each data rule.

    Valid options:

    • 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 General Ledger periods mapped to each FDMEE period included in a data load rule execution. Explicit period mappings enable support of additional Oracle General Ledger data sources where periods are not defined by start and end dates.

    • Click Save.