Show TOC
New Features in
Periodic Overhead Allocation
Use
- Batch reports for executing a cycle are now
more clearly laid out and more comprehensible. They use a uniform naming
convention: RKGAL + transaction code (for example,
RKGALKEU5 for the assessment of actual data).
You can use the same
functions with these reports as those that are available in the screen for
executing cycles. In this way, you can plan the cancellation of a cycle as a
batch report.
- Consistency checks on cycle run
groups
You can run a
consistency check on the cycle run groups for cycles in CO-PA. In cycle
maintenance, you start the check when creating or changing the cycle run group
(Goto -> Cycle run group) by choosing
Check cycle run group . When running a cycle, start the
check from the overview of the cycle run groups (Extras ->
Cycle run groups ).
The consistency
check looks for the following inconsistencies in all cycle run groups except
group 0000 (no parallel processing):
- Whether the cycles containing a sender assign
these senders to more than one cycle run group, and
- Whether the receiver tracing factor is read
from record type D or from an allocation cost element for the corresponding
allocation run type.
When complete, the
check lists all objects that it has found to be inconsistent. If you save the
result of the consistency check (which you do by choosing Activate
check result ), then it is taken into account when the cycle is
executed. A cycle can only be started in parallel if you have not started
another cycle in the update run that is dependent according to the
check.
When you want to
execute a cycle, you can decide under Settings
whether a consistency check should be run on the cycle run groups before the
cycle is executed. A cycle can only be started in parallel if the following
conditions are fulfilled:
- The consistency check for the cycle run groups
is up to date
- None of the cycles started in the update run
are dependent according to the check
The results of the
consistency check run on the cycle run groups are no longer valid once changes
have been made to the cycle. If changes have been made and the consistency of
the cycle run groups is to be taken into account upon executing the cycle, you
therefore need to run the consistency check on the cycle run groups
again.