Show TOC

Function documentationData Collection for Summarization Hierarchy Locate this document in the navigation structure


The data summarized with a summarization hierarchy is collected in a data collection run. The data collection run is usually carried out for each summarization hierarchy after period-end closing in Cost Object Controlling.

The following occurs during a data collection run:

The system 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 according to the structure of the hierarchy and it is updated by period and cost element in the summarization objects. A summarization object is built for each field characteristic for all fields in a summarization hierarchy.

Example Example

If your summarization hierarchy consists of the fields plant and order type, for example, the system creates the following summarization objects:

Plant A

Plant B

Plant A, order type 1

Plant B, order type 1

End of the example.

If a data collection run was already executed, the data selected for a new data collection run is updated as follows:

  • Data on the summarization object for periods within the summarization time frame of the new data collection run is reset and recalculated.

  • Data on the summarization object for periods outside the specified time frame of the new data collection run is retained. This prevents the data calculated in an earlier summarization run from being deleted by a new data collection run.

You can make the selection of objects for the summarization dependent 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 (released, or confirmed, for example). If you work with status selection, you should keep this in mind when you choose the summarization time frame.

Caution Caution

If, for example you want to summarize only settled orders and limit the summarization time frame to the last two periods, even though one order runs over four periods, the values (such as actual costs) of the first two periods of the order will not be summarized and will therefore not be in the summarization hierarchy. Because the total target costs are only calculated and updated in the period in which the order was delivered or technically completed, the cumulated target costs are presented against partial actual costs in the summarization hierarchy.

If you are using status selection, specify a summarization time frame that is large enough to include 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.

End of the caution.

You can find more information under Background Information on Summarized Analysis.


If you are using joint production, you must execute the function Preliminary Settlement for Co-Products, Rework before executing the data collection run. This is due to the fact that summarizations for joint production only summarize the values of the order items upwards, and not the values in the order header. You can find more information under Special Processing with Joint Production.


You can carry out a data collection run for:

  • the entire summarization hierarchy

    If you carry out a data collection run for the entire hierarchy, you can display a report for each summarization object of the hierarchy.

  • for a partial hierarchy

    For example, if you want to calculate the costs for all orders for a particular material, you can carry out the data collection run for the appropriate subhierarchy. In addition, you can display reports for all summarization objects in this subhierarchy.

You can also perform a deletion run. This will delete the data for all summarization objects in the specified hierarchy. It is meaningless to enter a time frame when performing a deletion run. A deletion run is necessary, for example, if you want to make subsequent changes to the definition of a summarization hierarchy.

In addition, you can execute a data collection run in which the summarization hierarchy is built but no data is selected. If a summarization was already executed for this time frame, the summarization objects were updated in the data collection run without writing over existing data.

Notes on Performance

To reduce runtimes, you can run the summarization 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 stipulate 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 choose the field Order number as a hierarchy level when defining the summarization hierarchy.

If you work with an order hierarchy with classification, you should execute the function Characteristic Statistics on a regular basis. You can change the sequence of the selected characteristics, which will speed up the selection of the classification characteristics. You can find this function in the application menu of the particular component in Cost Object Controlling under   Information System   Data Collection   Order Hierarchy (Classification)   Environment   Characteristic Statistics   Generate  .

Before executing the data collection run, set the indicator Classification in Customizing of Cost Object Controlling in Product Cost by Period or in Product Cost by Order under Check Order Types in the Change Order Type view and classify the orders with the report RKO CLASS. Then, deactivate the indicator.