Defining the Data Load Details

  To define the data load details:

1. Enter the data load rule name.

2. Select a Category.

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

3. Optional: Enter a description.

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

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

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

7. 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 ERP Integrator (or FDM) to determine the Source General Ledger Periods mapped to each ERP Integrator period (or FDM period) included in a Data Rule execution.

   • Explicit—The Data Rule uses the Explicit period mappings defined in ERP Integrator to determine the Source GL Periods mapped to eachERP Integrator Period (or FDM 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 ERP Integrator period (or FDM period) selected in a Data Rule execution.

8. For Planning applications, select a Plan Type.

9. For Performance Management Architect applications, in the Data Synchronization select the data synchronization for the target application.

   If you select “Auto-Create” ERP Integrator creates the data synchronization when the data rule runs.

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

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

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 ERP Integrator (or FDM) to determine the Source General Ledger Periods mapped to each ERP Integrator period (or FDM period) included in a Data Rule execution.

    • Explicit—The Data Rule uses the Explicit period mappings defined inERP Integrator to determine the Source GL Periods mapped to each ERP Integrator Period (or FDM 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 ERP Integrator period (or FDM period) selected in a Data Rule execution.

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 the user 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. Click Save.