Discovering SAP’s Grouping, Pegging, and Distribution(GPD) – Distribution

[Varsha2]

Welcome to the third blog of the series on understanding GPD – Distribution.

Part 1 - Grouping

Part 2 - Pegging

The purpose is to help gain a high level understanding of how distribution component functions within SAP GPD.

Distribution - distributes the individual / actual costs from the Group WBS elements (grouped replenishments) back to the individual WBS elements (original requirement). It picks up the quantities assigned during pegging for which the costs are to be distributed.

It is a common approach to use Production Orders, Purchase Orders as the objects where the actual cost distribution could be made from, while the list could also include:

• Commitments and Payments


• Stock Values


• Valuated Stock


• WIP

Pre-requisite:

1. WBS elements are assigned to Group WBS element.


2. Distribution profile for the Group WBS element to define the values to be distributed.


3. Requirements planning is executed.


4. Pegging against the appropriate

Application:

Customising: SPRO→ Project System → Financials → Period End Closing → Single Functions → Distribution

While distribution could be implemented for both valuated and non valuated stock, SAP recommends not going for valuated stock due to business process and technical complexities.

For non-valuated stock, goods movement do not have values and the overall costs are still associated with the Group WBS elements. Distributed values can then be used further for processes such as resource-related billing, surcharge or discount settlement. Only GPD distributed costs should be billed to the customer.

Below image highlights the difference mainly between Internal Procurement (Production Orders),  External Procurement (Purchase Orders) and the value distribution that it can have. We will leave Valuated stock out of scope for this blog.

Source: help.sap.com. (n.d.). SAP Help Portal. [online] Available at: https://help.sap.com/docs/SAP_ERP_SPV/cfff13ea14f3430488af41bbc02dbb69/18f5c353b677b44ce10000000a174....‌

Reports:

Two standard reports: RDISALL (transaction DIS01) and RDISALL2 (transaction DIS01N, an advanced version of RDISALL)  are available for triggering cost distribution. When you run DIS01N, depending on the combination of entries in Group WBS and Replenishment object below combinations are possible:

Grouping WBS Element		Replenishment Object	Behaviour	Exclude
Include	Exclude	Include
Blank	Blank	Blank	Blank	All the costs on all the grouping WBS elements and their associated replenishment objects are distributed
Entered	Blank	Blank	Blank	All the costs on the selected grouping WBS elements and their associated replenishment objects are distributed
Blank	Entered	Blank	Blank	All the costs on the grouping WBS elements except those selected are distributed
Entered	Entered	Blank	Blank	All the costs on the selected grouping WBS elements and their associated replenishment objects are distributed
Blank	Blank	Entered	Blank	All costs on the selected replenishment objects are distributed
Entered	Blank	Entered	Blank	All costs on the selected replenishment objects are distributed
Blank	Entered	Entered	Blank	All costs on the selected replenishment objects are distributed
Entered	Entered	Entered	Blank	All costs on the selected replenishment objects are distributed
Blank	Blank	Blank	Entered	All costs on the grouping WBS elements except those for the selected replenishment objects are distributed
Entered	Blank	Blank	Entered	All the costs on the selected grouping WBS elements except those for the selected replenishment objects are distributed
Blank	Entered	Blank	Entered	All the costs on the grouping WBS elements except those for the selected grouping WBS elements and the selected replenishment objects are distributed
Entered	Entered	Blank	Entered	All the costs on the selected grouping WBS elements except those for the selected replenishment objects are distributed
Blank	Blank	Entered	Entered	All costs on the selected replenishment objects are distributed. Replenishment object include/exclude must be mutually exclusive
Entered	Blank	Entered	Entered	All costs on the selected replenishment objects are distributed
Blank	Entered	Entered	Entered	All costs on the selected replenishment objects are distributed
Entered	Entered	Entered	Entered	All costs on the selected replenishment objects are distributed

Source: help.sap.com. (n.d.). SAP Help Portal. [online] Available at: https://help.sap.com/docs/SAP_ERP_SPV/cfff13ea14f3430488af41bbc02dbb69/d9f4c353b677b44ce10000000a174...

 

Limitations:

Two major limitations of distribution are:

1. Once you distribute the costs for a specific period, distribution cannot be re-run for the preceding period.


2. Distribution run cannot be cancelled.

Summary:

Distribution, based on pegged proportions distributes the costs. The process supports both valuated and non-valuated project stock. Overall, GPD could be quite complex and may not support all the desired processes. Project Manufacturing Management and Optimisation (PMMO) offers several benefits over GPD component in S/4 HANA. Please refer to some of these SAP notes as a starting point for PMMP offerings.

3030517 - SAP S/4HANA 2021, Project Manufacturing Management and Optimization: Restriction Note

2928343 - Data Migration from GPD on S/4 HANA to PMMO

Thank you for checking this blog.

References:

help.sap.com. (n.d.). SAP Help Portal. [online] Available at: https://help.sap.com/doc/78f5c353b677b44ce10000000a174cb4/700_SFIN20%20006/en-US/frameset.htm.

help.sap.com. (n.d.). SAP Help Portal. [online] Available at: https://help.sap.com/docs/SAP_ERP_SPV/cfff13ea14f3430488af41bbc02dbb69/d9f4c353b677b44ce10000000a174....

‌

‌