Show TOC
Define Cycles
for Process Cost Assessment
In this IMG activity, you define rules for
assessing business process costs to Profitability Analysis. These rules are
stored in so-called "cycles".
Activities
Define your assessment cycles. In doing so,
observe the following:
1. The header
of the cycle contains the parameters that are valid for the entire cycle. This
includes the "sender selection type", where you specify for actual values
whether you want to assess all costs together or fixed and variable costs
separately.
2. The segments
contain the combinations of sender processes and receiver profitability
segments that are processed using a single distribution rule.
a) Specify
either an assessment cost element or an allocation structure, which determines
more than one assessment cost element for each cost element group. The sender
processes are credited using these secondary cost elements (cost element
category 42). In account-based CO-PA, the receiver profitability segments are
also credited using these cost elements.
b) Specify
either single value fields for the fixed and variable costs respectively, or a
PA transfer structure, which determines more than one value field for each
cost element group.
c) Specify the
rule which you want to use to credit the sender.
Note that, for technical reasons, you can use an allocation structure or a PA
transfer structure only when using sender rule "1" (posted
amounts).
d) Define the
tracing factor, the rule which determines how the values are distributed to
the receivers. For example, you can distribute certain percentages to the
different receivers or distribute using certain values (such as the quantity
sold or the revenue) as an allocation base. If you choose to use an allocation
base, choose the receiver rule "Variable portions".
e) Specify the
senders and receivers in the "allocation characteristics".
Prerequisites
1.
Activity-Based Costing must be active as an operational CO
component.
2. The desired
form of Profitability Analysis must be active ( Check activation flag for
CO-PA).
3. You must
define an internal number range for CO transaction KSPA (actual) or KSPB
(plan).
Check number ranges for CO documents.
4. In
Profitability Analysis, you must define a number range for record type "D"
before you can assess process costs to CO-PA.
Check number ranges for actual data
Check number ranges for planning
5. To improve
runtimes in process assessment, it is recommended that you use summarization
levels if possible. These provide presummarized tracing factors for the
receiver profitability segments.
Notes on Planning
- The receiver version that you specify in cycle
maintenance should correspond to the one assigned for the sender version in
the transaction Assign Receiver Plan Version. If this is not the case, a
warning appears. This is due to the fact that, in future releases, it will no
longer be possible to enter the receiver version in cycle maintenance;
instead, the system will take the receiver version from the assignment made
for the sender version. However, to enable you to change the assignments for
your old cycles if need be, it is still possible to perform this type of entry
in cycle maintenance in this release. Nevertheless, you should still convert
your cycles.
Note that the field "Receiver Version" is only relevant for costing-based
Profitability Analysis. In account-based Profitability Analysis, data is
posted to the sender version.
- Ensure that the controlling area for the
receiver is the same as that for the sender. Consequently, you have to check
in the receiver rule "Variable Portions" that the characteristic "Controlling
Area" must have already been planned in manual planning if assessment is to
occur on the basis of planning data.
- The cycles that you have defined for plan
process assessment cannot be used for actual assessment. Instead, you have to
create them separately. However, it is possible to copy plan cycles to actual
cycles and vice versa.