What to Do After Environment Clone or Copy to Test

You may find after an environment clone or a production copy to test that you can't access GL balances cubes or run allocations, Financial Reporting reports, or Smart View queries.

Here's what you need to do in a cloned environment or in a test environment that was copied from production.

1. From the Scheduled Processes work area, run the Create General Ledger Balances Cube process and rebuild the balances cubes.
   Caution: If you're using the same chart of accounts with different calendars, then you must rebuild the balances cubes in the same order as your production environment. Otherwise, the dimensions and dimension members in the cloned environment won't be the same as in the production environment, particularly the ledger dimension members and potentially also the accounting calendar dimensions and members.
   Note: You can identify the order that such cubes were created based on the cube name. When a new cube with the same chart of accounts as an existing cube is created, a number is automatically appended to the name of the new cube, for example, VisionCorporation_2. You can find the associated chart of accounts and accounting calendar for numbered cubes by running the Enterprise Structures Setup report.
2. After the cubes are rebuilt, migrate your Financial Reporting reports to the cloned or test environment.
3. If you're using allocations, migrate your allocation rules to the cloned or test environment.