Show TOC
Maintain
Summarization Hierarchies
In this IMG activity, you specify the structure
of your summarization hierarchy. You specify which criteria are used for the
summarization of costs and quantities of objects in the definition of the
summarization hierarchy.
You can use a summarization hierarchy to
summarize the values of the following objects:
- Internal orders (order category 01 and
02)
- Maintenance/service orders (order category
30)
- Production orders, QM orders and product cost
collectors
- The following order types fall into this
category:
CO production orders (order category 04), product cost collector (order
category 05), QM orders (order category 06), PPC production orders (order
category 10), process orders (order category 40).
When summarizing
projects, the system also automatically summarizes dependent objects such as
assigned orders or WBS elements.
- Sales orders without dependent
orders
- Sales orders with dependent orders
When summarizing
sales orders, you can decide whether the system should also summarize the data
from the assigned production orders in the sales order. You do this by
choosing the corresponding object type.
You can then summarize the values (level by
level) of individual objects in ascending order, according to the defined
hierarchy structure.
You need to use the master data fields of the
account assignment objects as criteria for summarization. Each level of the
summarization hierarchy corresponds to a master data field. The system uses
the master data fields to select account assignment objects for summarization.
It then totals the costs and quantities for each value of a master data field
(for example, plant 1000, plant 2000).
Note:
When you use the
user-defined fields for internal order summarization, use the same upper/lower
case.
The system saves the calculated amounts in so
called summarization objects. These objects correspond to the nodes in the
hierarchy that was constructed during the summarization run. You can analyze
individual summarization objects in the information system.
You can use summarization hierarchies to
summarize various types of data, such as the following:
- Results analysis data from calculation of
profits
Example
Using a summarization hierarchy, you summarize
(by period) the costs incurred for the orders of a particular material
produced in a particular plant.
Notes
The first level in the hierarchy is always the
controlling area.
If you enter a status selection profile when
creating summarization hierarchies, only the objects for summarization are
selected, whose status at the time of summarization correspond to the
selection criteria in the status selection profile. If you wish to summarize
using the sales orders object type, then the status selection profile stored
in the hierarchy definition refers to the production order that you assigned
to the sales order.
Once the system has executed a summarization
run for a hierarchy, you can no longer change this hierarchy. If you would
like to change this hierarchy, you need to delete all the summarized data in a
deletion run.
You can enter selection variants for internal
order preselection
Notes
on joint production
For a status dependent selection of orders in
joint production, you can store separate status selection profiles for the
order header and the order item. This is because the status of the order
header and item can vary from each other in co-production.
When using co-production, the system only
summarizes the order item values. It disregards values that are on the order
header during summarization, therefore you need to use the "Co-product
distribution" function before starting a summarization run.
Requirement
You need to
Define Status Selection Profiles before using them.
If you wish to use selection variants, you need
to
Define Selection Variants first.
Actions
To define a summarization hierarchy, proceed as
follows:
1. Choose "New
entries".
2. Issue a
hierarchy name and a corresponding long text.
Select "Summarize
input quantities" if you wish to summarize input quantities. If you wish to
reduce the data using form routines, enter the user exit pool name that
contains this form routine (also see point 6).
3. Save your
entries and choose "Back".
You now return to
the overview of all the summarization hierarchies.
4. Choose "Data
scope (object types)" to determine which types of account assignment objects
should be included in each summarization run.
- Select the object types that you wish to
summarize.
If you only
summarize projects, the system also summarizes the data of assigned objects,
such as dependent orders. If you wish to summarize sales orders, you can
decide whether the system should include the production orders assigned to the
sales order during summarization, by choosing the corresponding object
type.
If you select more
than one object type (such as sales orders and production orders), you need to
specify a priority. This is because for example, the sales order can have a
certain value for a master data field, whereas the production order below
might have a different value for the same field. So, if the system used this
master data field for summarization, it would refer to the production order,
taking the value of the master data field in the sales order for
summarization, and the value in the master data field in the production order.
To avoid this, store priority 1 for the "sales order" object type, and
priority 2 for the "production order" object type in the hierarchy
definition.
5. Choose "Data
scope (totals record table)" to specify which costs and quantities should be
summarized.
- Select "Do not summarize" if you wish to
exclude individual totals record tables from the summarization.
- For better performance, you can summarize the
records in the totals record file without an origin. To do this, highlight the
"Without origin" indicator. Setting this indicator is recommended if you are
only require cost element reports, but means it is not possible to expand the
values on a cost element level to show their origins.
If you would like to
reduce the data scope using a user exit, enter the name for the user exit form
routine. Before doing this, enter the name of the user exit pool when you
create the summarization table.
6. Choose
"Hierarchy levels" if you wish to assign master data fields to the levels in
your summarization hierarchy.
You can define up to
nine hierarchy levels.
In the "Hierarchy
field" column, enter the required master data field for each hierarchy level.
If you wish to create a hierarchy level above a section of a master data
field, maintain "Offset" and "Length".
7. Select
"Blank" if you wish to group account assignment objects (that have a
characteristic that is not filled) to the "Miscellaneous" node.
Further
Notes
For more information on structuring
summarization hierarchies and their purpose within Product Cost Controlling,
see the R/3 library: "AC - Financials -> CO - Controlling ->
Product Cost Controlling -> CO-PC Information System -> Summarized
Analysis in Cost Object Controlling -> General Information on Summarized
Analysis -> Summarization Hierarchies".