Creating Data Load Definitions

To load balance data:

1. Select a period, then Actions, and then Load Data.

   Data Load contains a history of data loads, reporting the start date, end date, the user who executed it, the status, and the result. The status report shows subprocesses and the status of each:

   • Staging—The staging process extracts balances from the source system, assigns the profile ID and balance type, and stores the balances in a temporary staging table. In the staging table, there is a one-to-one relationship to balances in the source system (no summarization has occurred). The staging table is refreshed with every data load; balances of prior loads are not maintained.

   • Data Load—The load process summarizes the balances by profile, balance type, currency bucket, and currency code and loads the balances into ARM. These balances are permanently stored in ARM but are updated if changed balances are imported in the future.

   • Post-Processing—Performs these actions:

     • Changes the status of reconciliations "Open with Reviewer" or "Closed" to "Open with Preparer" if balances changed

     • Runs the auto-reconciliation routines

     • Flags reconciliations containing normal balance violations (cases in which an expected debit balance is a credit balance, or when an expected credit balance is a debit balance.

     • Post-processing may run certain rules. See Order of Precedence Rules for Account Reconciliation.

   Statuses of each of the three subprocesses are reported using icons. On Data Load, place your cursor over an icon in the Staging, Data Load, and Post Process columns to display information:

   • Pending

   • Running

   • Complete

2. Click New
3. In New Data Load Execution, enter:

   • Use saved data load

     If selected, a list of data load definitions is enabled. See Scheduling Data Loads.

   • Name

   • Description

   • Mode—Select one:

     Note:

     Except when doing a full refresh, loads can run in parallel if their Load phases do not overlap.

     • Full Refresh

       Use the Full Refresh option when data load definitions in Data Management have been changed (due to removing Data Load Rules or Locations, or changing Category Mappings). These types of changes can break the connection between balances imported through Data Management and stored in Account Reconciliation, which can result in double counting of the balances.

       • If any data load is in a pending or running status, then no full refresh data load can be run.

       • If a full refresh data load has a pending or running status, then no data load can be run.

       Note:

       When you choose the Full Refresh option, all balances for this period are purged. They are replaced with balances only from the selected Locations.

       Caution:

       When using this feature, you must import balances from all locations containing balances. Failure to do so could result in reconciliations previously closed to reopen, because only a partial set of balances were imported, causing Account Reconciliation to calculate a change in the balance.

     • Recalculate

       Use to reapply mapping rules without having to reload data into Data Management staging tables. Recalculate uses the data that is already there, re-maps it, and reimports it into Account Reconciliation.

       An Administrator can use this option to fix a mapping error.

     • Snapshot

       Use the Snapshot option for a Read-only view of the data from a specific time.

   • Location

     The Data Management location to import.