| No balances to process |
- Check balances in the cube
- Run refresh if balances exist in the General Ledger Total but
not in the cube
- Verify that source transactions do not cancel each other
out
|
| Allocation run failed, or Allocation task in Async terminated
abnormally |
- Check Async or the error message for the cause of the
error
- Select . On the Queue
View tab, search to find the allocation queue or default queue
- Search for the task name that begins with Allocation
- Search for the task name AnalyticCube.Refresh
- Fix the error and re-queue the failed Allocation async
task
- If the error is not resolved, obtain the grid logs from the
time of the error, open a ticket and attach the logs
|
| Allocation run remaining in Started status |
- Check async to verify that allocation tasks or analytic cube
refresh is still running or has terminated abnormally
- If the process terminated abnormally, then see the Allocation
task in Async terminated abnormally issue
|
| Timeout |
- Obtain the grid logs with the time-out error
- Open a ticket with the logs. Include information on the sizes
of source dimensions used and multiple overrides
|
| Incorrect Rollup |
- Run refresh of the Finance Enterprise Group and General Ledger
Total cubes
- Rebuild the shadow files of the allocation calendar and each
dimension
Note: Each dimension has a shadow file. For each summary, including top
nodes, all of the summary and posting children are displayed. Shadow files are
used internally for allocations, budgets, account analysis, and code block
relations.
|