Transfer Pegging Processor (Group-to-Group Transfers)
Note
If you are using pegging report PEG01 , the following information is relevant for you.
When you do a group-to-group transfer of a part with sub-components, you create a pegging dependency between the two groups.
This dependency requires that you do one of the following:
Run pegging for the two groups in one pegging run
If you do not run pegging for the two groups together, run the transfer pegging program after you run pegging for the two groups
The transfer pegging program (transaction PEG15 ) allows you to decouple this dependency between the two groups; it also re-establishes the missing links from when you ran pegging for the two groups in different pegging runs.
You can alternate between pegging-dependent groups in one pegging run, pegging them independently, and running transfer pegging after that. But this flexibility may cause some changes in the pegging results.
We recommend you adopt one of the following policies for the transfer pegging program:
Always use it
Never use it
Use the transfer pegging program if you meet all of the following criteria:
More than one grouping work breakdown structure (WBS) element is used in your system landscape.
There is at least one stock transfer from one grouping WBS element to another, and the transferred stock has sub-components.
Pegging for the two groups is not run in one pegging run.
Before you run the transfer pegging program, you must run pegging at least once for each of the dependent groups.
Note
If your business process uses the transfer pegging program, then the program must be run before distribution is run.
You do not need to run the transfer pegging program for the following scenarios:
No group-to-group transfers
Group-to-group transfers of parts without sub-components (for example, purchased parts)
Running pegging for the dependent groups together
Group-to-group goods issues
If you use the transfer pegging process after you run pegging for one group, red traffic lights are displayed for the materials that were involved in group-to-group transfers. This lights are resolved during the transfer pegging process.
Errors can result from the time difference between pegging and transfer pegging, and the fact that some group-to-group transfers could take place during this time. These errors are corrected over time, but new ones may appear during the next pegging process run.
Since you can run pegging independently for multiple grouping WBS elements, the overall pegging time is reduced, even if the elements have transfers between them. If you do not have many groups, and you do not generally have pegging performance issues, we recommend you run pegging together for all groups and do not use the transfer pegging processor. This is because the transfer pegging process adds another process to an already complex GPD procedure, which creates the chances for errors .
Restriction on Exception Handling with Transfer Pegging Functionality
Note
The following applies to both pegging reports PEG01 and PEG01N .
If you have group-to-group transfers, each grouping WBS element must have a unique exception WBS element assigned to each exception.
Note
You have two groups, G1 and G2. They have some stock transfers between them. Transaction PEG04 must have a unique (different) WBS element defined for the scrap, surplus, and lost/found for each group.
Pegging stops running under the following conditions:
Exception WBS elements are the same for the two different grouping WBS elements.
You have group-to-group transfers between the groups.
You are running pegging only for one of the groups.
If you have group-to-group transfers, and you only want to run pegging for the groups independently, you cannot define exceptions on the plant. (Because this step results in non-unique exception WBS elements for the groups.)
See also: