Resolving Reopening of Reconciliations After Partial Source (General Ledger) or Subsystem (Subledger) Balance Reload

By default, Oracle Hyperion Financial Data Quality Management, Enterprise Edition requires that reloads be full loads of the previously loaded balances through a particular Location, Category, and Period. If you reload partial balances, Account Reconciliation may reopen reconciliations.

For example, assume that 1,000 general ledger balances for the January 2021 period were loaded on February 1 using Location 1 in the Entered Currency bucket. If some January 2021 balances change and must be reloaded on February 2, then all 1,000 balances must be reloaded on February 2; you should not reload only the balances that have changed. If any of the 1,000 balances loaded on February 1 load are not included in the February 2 reload, then reconciliations may be reopened because they now have missing balances.

To avoid this issue, use the Merge feature, which allows partial balance re-loads. This feature ensures that balances included in subsequent loads only update the previously loaded balances with the same Merge ID. Any balances not included in the subsequent load would be left as is and will not reopen associated reconciliations. For more information, see these information sources:

• Define and Save a Data Load Definition in Account Reconciliation Administering Account Reconciliation
• Adding an Account Reconciliation Merge Balance Dimension