Goods Movements that Affect Pegging and Distribution Several types of goods movements are relevant for pegging. The grouping, pegging, and distribution (GPD) process tracks goods movements through the GPD goods movements tables.
You can execute Customizing transaction 0PEG02 to set up the relevance for pegging. If a movement type is not classified in transaction 0PEG02, or if it is classified as
Not relevant for Pegging
, it does not create changes in any of the GPD goods movement tables.
There are seven different categories of goods movements. To allow new movement types for pegging you have to call transaction
0PEG02
and add the entry to the Customizing table (
PEG_TCHKMT).
You can implement your own logic for the validation of goods movements using BAdI BADI_GPD_MM_PRECHECKING.For more information, see Customizing for
Project System
under
The following is a list of the different categories of GPD relevant goods movements:
Relevant to assignments: goods issues, goods receipts, reversals
Scrap backflush: scrapping from stock
Stock differences: lost or found inventory
No influence
Material-to-material: transfer between materials (only works for externally procured materials)
Transfer posting between groups
Transfer posting between stocks: to transfer materials from one stock category to another (unrestricted, quality inspection, blocked)
For technical reasons, the following movement types are not supported by pegging:
Movement Type |
Description |
231 |
Consumption for sales order from unrestricted project stock |
232 |
Consumption for sales order from unrestricted project - reversal |
291 |
Consumption for all account assignments from unrestricted project |
292 |
Consumption for all account assignments from unrestricted project – reversal |
411 |
Transfer posting project to own |
412 |
Transfer posting project to own - reversal |
413 |
Transfer posting project to sales order |
414 |
Transfer posting project to sales order – reversal |
531 |
Receipt by-product |
532 |
RE by-product |
581 |
Receipt by-product network |
582 |
RE by-product network |
These not supported movement types must be entered in table
PEG_TMTNS
. To enter them call transaction
SM30
.
Make sure that movement types created as a copy of one of these movement types are contained in table
PEG_TMTNS
.
See also: