Changes and enhancements to assessment to CO-PA in Release 4.0A

Description

Oveview of new functions

The following is a detailed description of the new functions for maintaining and executing assessment cycles:

Maintaining cycles

Cycle end date, Date of last change to the cycle, user who last changed the cycle, iteration indicator, aggregation indicator

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

Executing cycles

Be sure to assign cycles that are dependent on one another to the same cycle run group, since you otherwise might accidentally run them at the same time, which could lead to incorrect allocations!
Cycles are dependent on one another when they credit the same sender or when they read the same tracing factor for "variable shares" and use the reference base "costing-based Profitability Analysis" with record type D. Do not run these cycles at the same time!
You therefore need to check carefully when assigning cycles to different run groups. The system does not check to ensure that this is possible for those cycles. If you are not sure, leave the default setting as it is, which uses the same locking techniques as in earlier releases (only one cycle at a time).
Example:
You have two sets of cycles: one for transferring costs from the sales cost centers and one for transferring costs from administrative cost centers. Each of these sets contains two cycles that are not dependent on a cycle in the other set, while the cycles within each set are dependent on each other. You therefore need to assign the cycles in one set to the same run group. You can then execute cycles from different sets at the same time.

Changed screens in cycle maintenance and new functions for executing cycles make it necessary to rework the creation of batch-input sessions.

Changes to the interface

The screens for cycle maintenance have been fully redesigned.

Planning