Depending on your requirement, you can use one of the following modes to load data: Full Refresh, Merge, Recalculate, or Snapshot.
Full Refresh Mode
A Full Refresh clears out all balances for the period and reloads the location. 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) since these type 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.
The following are restrictions with using the Full Refresh mode:
If any data load is in a pending or running status, do not use full refresh.
If a full refresh data load has a pending or running status, then no data load can be run.
When using this mode, 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.
Use the Merge mode to replace some of the existing balances at the same location but leave the other balances as is. This is very useful when you load large data files on an ongoing basis and only have a need to change (update) some of the balances at the same location. This not only saves you time, but is less error prone.
In order to use Merge mode, you must set this up by creating a Merge ID (a unique identifier) using Data Integration. Access this by using the Data Exchange card under Applications. Then create a Merge ID in Map Dimensions.
See Adding an Account Reconciliation Merge Balance Dimension in Administering Data Integration for Oracle Enterprise Performance Management Cloud.
Best Practice for Using Merge Mode
When loading balances (except for the first data load), it is recommended that you first run the data load using Recalculate mode and then run the data load using Merge mode.
Typically, mapping definitions may be updated in the course of business operations. If the definition was updated between two data loads, some balances that were originally loaded into a particular profile may now need to be removed from this profile and loaded into a different profile. If you use the Merge mode to reload balances, you must ensure that balances that were erroneously loaded into a profile are wiped out from the profile before being loaded into the correct profile (as per the updated mapping definition). To achieve this, you first load balances using the Recalculate mode, to reapply the mappings, and then load the same balances using Merge mode.
Use this mode to reapply mapping rules without having to reload balances into Data Management staging tables. Recalculate uses the balances that are already there, remaps them, and then reimports them into Account Reconciliation. An Administrator can use this option to fix a mapping error.
Use the Snapshot mode to replace (or update) previously loaded balances at only the locations you specify. For example this mode is useful if you loaded balances one day and want to add more the next day.