Best practice recommendations
This table shows recommendations for processing allocations:
Recommendation | Description |
---|---|
Create alternate structures | Create alternate structures for allocations for these reasons:
Alternate structures must only contain posting elements that affect allocations. |
Processing source address | When the source is processed at the posting details level, the calculation performance may be affected if the top summary is selected or the dimension is blank. Create alternate structures so that the direct parent is selected. You can also break the line into multiple lines so that the direct parent can be selected. |
Multiline allocations | Put lines in separate steps only if there are dependencies between them. |
Selecting report options | When you select report options, performance is affected. Select report options only when it is required. |
Deleting allocation transactions | To conserve database space, use the | action on allocation transactions that are no longer required.
Allocation queue | Set up the allocation queue to track and save the history of allocations tasks. |
Quick-post and batch post | Do not quick-post or schedule journal entry posting during allocation posting if locations that match allocations are written to by the posting process. Incorrect calculations may occur if the locations are read by allocations during the refresh of the Global Ledger Total (GLOT) cube that is triggered by posting. |
Scheduling allocations | Do not schedule an allocation job during a scheduled refresh of the analytic cube because your allocation job may terminate. |