Changes and enhancements to assessment to
CO-PA in Release 4.0A
Oveview of new functions
Transferring process costs
Explicit assessment to company codes and business areas
Aggregated processing of tracing factors
Execution of multiple cycles at the same time
The following is a detailed description of the new functions for
maintaining and executing assessment cycles:
The sender object "Business process" is now available so that
you can assess process costs. The prerequisite for this is that you
are using Activity-Based Costing operationally in your system.
The characteristics "company code" and "Business area" are now
available as receivers. If the company code or business area you
specify differs from that of the sender object, this results in
cross-company or cross-business-area postings.
The "Aggregate tracing factor" field in the header of the cycle
lets you aggregate the tracing factor before it is processed. The
system adds together all the periods. If your tracing factor shows
large fluctuations, this can smooth these out.
You can assign cycles to so-called "cycle groups" and execute
these at the same time. You assign a cycle to a group in the header
data under "Goto -> Cycle run group".
The cycle maintenance functions use the new set/group concept.
You can use groups created in Cost Center Accounting or
Activity-Based Costing for the fields "Cost center", "Business
process", and "Cost element".
The segment overview was expanded to include a few important
settings (such as sender and receiver rules) and functions. You can
enter central settings in the segment overview and thus change them
quickly. You can search for certain objects (such as cost centers)
in the whole cycle and then jump directly to the relevant
It is now possible to sort the segments of a cycle into any
order and insert them anywhere in the sequence. You therefore do
not need to add new segments at the end.
Change documents in cycle maintenance: Logs are kept on any
changes to the following settings:
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
In cycle maintenance, you can specify up to ten characteristics
for the fixed sender values and receiver tracing factors
(previously only five).
The number of receivers for fixed receiver tracing factor
values can now be as high as 9999 instead of just 999.
For the receiver tracing factor "fixed shares", the number of
characters before the period has been increased from three to
The following new methods were implemented to scale negative
1. No scaling
2. Standard scaling
3. Absolute value (negative become positive)
4. Negative become zero
5. Smallest negative becomes zero
6. Smallest negative becomes zero, zero remains zero
The scaling flag on the cycle header screen was removed, since it
was only used as a default when you created a new segment.
You can place cycles into cycle run groups and execute the
cycles in different run groups at the same time. The only exception
to this is cycle run group 0000 does not allow multiple runs in
parallel. So you cannot start another cycle with the same
allocation type while cycle run group 0000 is running unless one of
these is in the test mode. Similarly, you cannot start a cycle in
run group 0000 while a cycle in another group is being executed.
Existing and new cycles are initially contained in cycle run group
0000 by default.
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
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.
Following assessment, the system displays the results using the
new ABAP/4 List Viewer. You can use all of the available list
viewer functions (sorting, filters, and so on). However, you cannot
yet create your own display variants. This wil be supported in a
later release. "Journal lists" provide you with a combined,
detailed view of the senders and receivers. However, you need to
activate these on the screen where you execute the cycle, which
increases the amount of main memory required.
To find errors, you can call up the most important information
about the cycle run in the "Technical statistics". Note that these
statistics must also be activated on the screen where you execute
the cycle (under "Settings").
You can use a customer exit to check authorization to execute
and maintain specific cycles.
Due to internal restructuring that could not be avoided,
variants created in Release 3.0 or 3.1 can no longer be accessed
and therefore need to be defined again.
Changed screens in cycle maintenance and new functions for
executing cycles make it necessary to rework the creation of
Changes to the interface
The screens for cycle maintenance have been fully
In a future release, utilities will be designed to help you
assign your cycles to cycle run groups optimally.
the change documents will be extended to record the sender and
receiver objects and their characteristic values.