Data Collection for Summarization Hierarchy
The data to be summarized in a summarization hierarchy can be collected in a data collection run.
Note
You can also summarize data in a summarization hierarchy dynamically when you run the report. In this case it is not necessary to use a data collection run. For more information, see Summarization Hierarchies.
A data collection run is usually executed for each summarization hierarchy after period-end closing in Cost Object Controlling.
The data collection run reads the quantities and values of the selected objects as defined by the summarization hierarchy for the period being closed. This data is summarized upwards in the hierarchy and updated by period and cost element on the summarization objects. A summarization object is generated for each field characteristic for all fields in the summarization hierarchy.
Example
If the summarization hierarchy consists of the fields Plant
and Order Type
, the data collection run creates the following summarization objects:
Plant A
Plant B
Plant A, order type 1
Plant B, order type 1
Summarization Time Frame
If summarization objects exist from a previous data collection run, the data selected for a new data collection run is updated as follows:
Data on the summarization objects for periods within the summarization time frame of the new data collection run is reset and recalculated.
Data on the summarization objects for periods outside the summarization time frame of the new data collection run is retained.
You can have the selection of objects for the summarization depend on the status of the object. To do this, create a status selection profile when defining the summarization hierarchy. In the status selection profile, you can specify which status the selected objects should have. If you use status selection, keep this in mind when you define the summarization time frame.
Note
If you summarize only settled orders, for example, and you limit the summarization time frame to the last two periods although one of the orders runs across four periods, the actual costs of the first two periods will not be summarized. Since the cumulative target costs are only calculated and updated in the period in which the order was delivered or technically completed, the summarization hierarchy will not contain complete actual costs that can be compared against the cumulative target costs.
Therefore, if you are using status selection you should specify a summarization time frame that includes the entire life of an order.
If you are not using status selection, it is sufficient to specify a summarization time frame that includes all open periods in Financial Accounting
.
For more information, see Background Information on Summarized Analysis.
Prerequisites
If you are using joint production, you need to execute the Preliminary Settlement for Co-Products, Rework function before the data collection run. This is because summarizations for joint production only summarize the values of the order items upwards, and not the values in the order header. For more information, see Special Processing with Joint Production.
Features
You can execute a data collection run for:
The entire summarization hierarchy
If you execute a data collection run for the entire summarization hierarchy, you can call up a report for each summarization object.
A subhierarchy
If you want to calculate the costs for all orders for a particular material, for example, you can execute the data collection run for the corresponding subhierarchy. In addition, you can call up reports for all summarization objects in that subhierarchy.
You can also execute a deletion run. This will delete the data for all summarization objects in the hierarchy. A deletion run is necessary for example if you want to make changes to the definition of a summarization hierarchy. You do not need to enter a time frame for a deletion run.
In addition, you can execute a data collection run in which the summarization hierarchy is created but no data is selected. If a summarization was already executed for the same time frame, the summarization objects were updated in the data collection run without overwriting existing data.
Notes on Performance
To reduce runtimes, you can execute the data collection run for summarization hierarchies on multiple servers simultaneously. You can improve the performance of simultaneous processing by defining the number of summarization nodes.
In addition, in the summarization hierarchy you can specify that individual totals records files should not be summarized, or that the records of totals records files without origin should be summarized. It is recommended that you set this indicator if you are interested in simple cost element reports without much detail.
For performance reasons it is also recommended that you do not select the Order number
field as a hierarchy level when defining the summarization hierarchy.