Maintain Summarization Hierarchies
In this step in Customizing for the Product Cost Controlling Information System, you specify the structure of your summarization hierarchies. In the definition of a summarization hierarchy, you specify what criteria are used to summarize the costs and quantities of objects.
You can use a summarization hierarchy to summarize the values of the following objects:
When projects are summarized, the system also summarizes the dependent objects (such as assigned orders or WBS elements) automatically.
When you summarize sales orders, you can control whether the system summarizes the data of the manufacturing orders assigned to the sales order by selecting the corresponding object type.
You can later summarize the values of individual objects upwards in accordance with the defined 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. Using the master data fields, the system selects the account assignment objects for summarization and sums the costs and quantities for each characteristic value of a master data field (such as plant 1000, plant 2000).
If you are using customer-specific fields to summarize internal orders, the case (upper/lowercase) must be the same as used in these fields.
The system saves the calculated sums 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:
You can use a summarization hierarchy to summarize the costs incurred in each period by the orders to produce a particular material in a particular plant.
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 the system has executed a summarization run for a hierarchy, 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.
You can specify selection variants to preselect internal orders.
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, the system summarizes only the values of the order items. Values on the order header are not summarized. Therefore, you should execute the function Distribution for Co-Products before starting a summarization run.
If you want to use status selection profiles, you must first carry out the stepDefine Status Selection Profiles.
If you want to use selection variants, you must first carry out the stepDefine Selection Variants.
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 quantities.
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 type of account assignment objects are included in the summarization run, choose Data scope (object types).
If you only summarize projects, the system also summarizes the data of assigned objects such as dependent orders. If you want to summarize sales orders, you can control whether the system summarizes the data of the manufacturing orders assigned to the sales order by selecting the corresponding object type.
If you select more than one object type (such as sales orders and production orders), you must specify a priority. This is necessary because the sales order for a master data field, for example, can have a value that differs from the value of the production order below it for the same field. If the system were to summarize 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 from happening, in the hierarchy definition specify priority 1 for the object type sales order and priority 2 for the object type production order.
6. To specify which costs and quantities should be summarized, choose Data Scope (Totals Records Tables).
If you want to limit the data scope using a user exit, enter the name of the user exit form routine. To do this, you must have 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 9 hierarchy levels.
In the column Hierarchy field, 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.
For more information on creating summarization hierarchies and on their use in Product Cost Controlling, refer to the SAP Library underSummarization Hierarchy.