Allocations

In this IMG activity you make settings for allocation of plan data.

Recommendation

When using assessment, distribution, and periodic reposting, keep the following information in mind:

Note that the data volume generated for past periods will grow with increased numbers of periods. Especially in reporting and for data backups, it is important to keep the data volume generated by allocation to a minimum. For this reason, SAP recommends assessment or periodic reposting.

For performance reasons, you should not use more than 50 segments in one cycle. If necessary, define multiple cycles. A larger number of segments per cycle is only necessary for extensive iterations.

Also: For performance reasons, never use more than 10,000 relationships in an allocation cycle. If you require more than that, you must plan a mass test of the allocations beforehand.

Example

From a sender cost center with 100 sender cost elements, allocations are made with one segment to 500 receiver cost centers.

The following numbers of sender and receiver totals records result from the different allocations that must be written in the processed period:

Allocation Sender totals recds Receiver totals recds

------------------------------------------------------------------------

Assessment 500 500
Periodic reposting 100 500 x 100
Distribution 500 x 100 500 x 100

------------------------------------------------------------------------

This simple example already demonstrates that

In practice, because of the far higher number of senders and receivers, the advantages of assessment and periodic posting will be much more apparent.

Further Notes