Clearing the local budget copy

During budget editing, the system retrieves budget data for each budget group from the cube. Once a change request is released, the system saves a local copy of the total budget data for the budget groups used in the change request. On subsequent budget edits, the system uses this local copy instead of querying the cube again, which improves performance.

Before importing additional budgets using the Incremental Load process, you must run the Clear Local Budget Copy action. The incremental load cannot proceed if any active template in the scenario still contains a local budget copy. This step ensures that budget editing reflects the most current data from the cube after incremental load process.

When the Clear Local Budget Copy action is triggered, the system deletes all local copies for the budget groups in the selected template. A new local copy will be created the next time any of those budget groups are used in a change request. To verify if a local budget copy exists, open a budget template. The status is displayed if there is an existing local budget copy.

To verify the last cube refresh for general ledger totals, select the Cube Update Details tab on the budget scenario.

See Budget edits processing.