Show TOC

Background documentationMaintain Summarization Hierarchies Locate this document in the navigation structure

 

In this step in Customizing for the Product Cost Controlling Information System, you define the structure of your summarization hierarchies by specifying which criteria are used to summarize costs and quantities.

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)

  • Manufacturing orders, QM orders, and product cost collectors

    This includes the following order categories:

    • CO production orders (order category 04)

    • Product cost collectors (order category 05)

    • QM orders (order category 06)

    • PP production orders (order category 10)

    • Process orders (order category 40)

  • Projects

    When projects are summarized, the dependent objects (such as orders or WBS elements) are summarized as well.

  • Sales orders with or without dependent orders

    When you summarize sales orders, you can control whether the data of the manufacturing orders assigned to the sales order is summarized by selecting the corresponding object type.

You can later summarize the values of individual objects upwards in accordance with the hierarchy structure.

You use the master data fields of the account assignment objects as the summarization criteria. Each level of the summarization hierarchy corresponds to one master data field. The account assignment objects are selected for summarization based on the master data fields, and the costs and quantities for each characteristic value of a master data field are summarized.

Note Note

If you are using customer-specific fields to summarize internal orders, the case (upper/lowercase) must be the same as used in these fields.

End of the note.

The calculated sums are saved to summarization objects that correspond to the nodes of the hierarchy generated during the summarization run. You can analyze the summarization objects in the information system.

You can use summarization hierarchies to summarize data such as the following:

  • Planned costs

  • Actual costs

  • Target costs

  • Variances

  • Work in process

  • Results analysis data

  • Input quantities

  • Output quantities

  • Scrap

Note Note

  • The highest node in the hierarchy is always the controlling area.

  • If you specify a status selection profile when you create summarization hierarchies, the only objects selected for summarization are those whose status matches the selection criteria specified in the status selection profile at the time of summarization. If you want to summarize on the object type Sales Orders, the status selection profile specified in the hierarchy definition refers to the production orders assigned to the sales order.

  • Once a summarization run for a hierarchy has been executed, you can no longer change the summarization hierarchy. If you want to change the summarization hierarchy, you must first execute a deletion run to delete all summarized data.

End of the note.

You can specify selection variants to preselect internal orders.

Note Note

To enable status-dependent selection of orders in joint production, you can enter separate status selection profiles for the order header and the order item, since in joint production the status of the order header can differ from the status of the order item.

In joint production, only the values of the order items are summarized. Values on the order header are not summarized. Therefore, you should execute the Distribution for Co-Products function before starting a summarization run.

End of the note.

Prerequisites

If you want to use status selection profiles, you must first carry out the step Define Status Selection Profiles in Customizing.

If you want to use selection variants, you must first carry out the step Define Selection Variants in Customizing.

Activities

To define a summarization hierarchy, proceed as follows:

  1. Choose New Entries.

  2. Give the hierarchy a name and a description.

    To summarize input quantities, select Summarize input qty.

  3. If you want to limit the data scope using form routines, enter the user exit pool that contains those form routines (see also step 6).

  4. Save your entries and go back.

    You return to the overview of all summarization hierarchies.

  5. To specify which types of account assignment objects are included in the summarization run, choose Data scope (object types) and select the object types to be summarized.

    • If you only summarize projects, the data of assigned objects (such as dependent orders) is summarized as well.

    • If you want to summarize sales orders, you can control whether the data of manufacturing orders assigned to the sales order is summarized by selecting the corresponding object type.

    • If you select more than one object type, you need to specify a priority for each of the object types.

      Priorities are necessary to prevent duplicate summarization on master data fields, which would result in incorrect summarization values.

      Example Example

      The sales order for a master data field can have a value that differs from the value of the production order below it for the same field. If you summarized on this master data field, the production order would be included both in summarization on the value of the master data field in the sales order and in summarization on the value of the master data field in the production order. To prevent this, specify Priority 1 for the object type Sales Orders and Priority 2 for the object type Production Orders.

      End of the example.

  6. To specify which costs and quantities should be summarized, choose Data Scope (Totals Records Tables).

    • To exclude individual totals records tables from summarization, select Not summarized.

    • To improve performance, you can summarize the records of the totals records file without the origin. To do this, select No origin. This is recommended when you are interested in pure cost element reports. However, it is then no longer possible to drill down from the cost element values to the origins.

    • If you want to limit the data scope using a user exit, enter the name of the user exit form routine. This is only possible if you entered the name of the user exit pool when you created the summarization hierarchy.

  7. To assign master data fields to the levels of your summarization hierarchy, choose Hierarchy levels.

    You can define up to nine hierarchy levels.

    In the Hierarchy Field column, specify the desired master data field for each hierarchy level. If you want to create a hierarchy level using part of a master data field, enter the offset and the length.

  8. If you want to group account assignment objects for which a characteristic is not filled under the node other, select Blank.

More Information

For more information on creating summarization hierarchies in Product Cost Controlling, see Summarization Hierarchies.