Changes and Enhancements: Allocation Processor


Cycle Maintenance

Cycle end date, date of last change, last person to change, iteration

Segment name, sender rule, receiver rule, field group for variable portions, lock indicator, sender percentage, actual/plan indicator for determining sender values, assessment cost element, sort field

1 - No scaling
2 - Standard scaling
3 - Absolute value (negatives treated as positives)
4 - Negative tracing factors set to zero
5 - Smallest negative tracing factor set to zero
6 - Smallest negative tracing factor set to zero, but zero remains zero
The scaling indicator is no longer in the cycle header data screen because it appeared as a default value for new segments only.
1. Check sender balancing to 100% in the cycle
2. Fixed values for sender do not equal those for receiver

Cycle Execution

All possible allocations and postings of parallel valuations occur independently of each other. Version 000 serves as the sole basis for tracing factors in actual.
Example: You use cross-company-code cost accounting. You define one cycle per company code. In this case, the cycles are integrated fully and can be executed in parallel.
NOTE: Include all cycles that reference each other in the same run group. Otherwise, if you execute these cycles in another parallel run, this will result in inconsistent data and incorrect allocations.
Check very carefully if you assign cycles to parallel run groups. The R/3 System does not make any consistency checks. If in doubt, accept the default setting that uses the same lock protocols as earlier releases (only one cycle executed with posting).

Selection by cycle (default; as in previous releases) -- Per cycle field (cost center, cost element, etc.), the largest and smallest value determined for the entire cycle and used for database selection.
Advantage: A single select command. Disadvantage: Too many objects can be selected, which must then be eliminated (number of segments should be no greater than 50).

Optimized by cycle (CO-OM only) -- (nur CO-OM): Selection only for defined CO objects in cycle
Advantage: Small number of selections. Disadvantage: Multiple database access (number of segments should be no greater than 50).

Selection by segment: Per segment field, the largest and smallest value determined for the entire segment and used for database selection.
Advantage: Database selection correlated almost linearly with segments, not expotentially. Disadvantage: In some cases too many objects can be selected, and multiple database access in any case.


You can use orders and WBS elements in plan assessment, distribution, periodic reposting, and indirect activity allocation as valid receivers (or senders in reposting) if you fulfill the following requirements:

In contrast to Release 3.0/3.1, Release 4.0 checks in version 000 during plan assessment and distribution whether these three conditions are met. This was not possible in Release 3.0/3.1 due to compatability problems with earlier releases.

Effect on batch input

The R/3 System has new screens in cycle maintenance and new functions for cycle execution; check your batch input settings.

Changes to the interface

The cycle maintenance screens have been completely changed.


Further notes

Due to unavoidable program restructuring, you can no longer access variants created in Releases 3.0 and 3.1. You must recreate them in Release 4.0.