Hierarchy

⤷

⤷

IMG Activity
ID | 0PEG01 | Pegging: General Settings |
Transaction Code | S_KA5_12000969 | IMG Activity: 0PEG01 |
Created on | 20010112 | |
Customizing Attributes | 0PEG01 | Pegging: General Settings |
Customizing Activity | 0PEG01 | Pegging: General Settings |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | 0PEG01 |
In this activity you make the basic settings for pegging on client level: or:
- The logic to apply on assigning replenishment elements to pegs. You have the following options:
- MRP-Logic: Assignment occurs according to the current requirements planning situation.
- Fixing rule: During the assignment process the system attempts to assign a replenishment element from the previous run to the peg if the required quantity for the corresponding part has not changed.
- Fixing rule for purchase orders / production orders: During the assignment process the system attempts to assign a replenishment element (only purchase orders or production orders) from the previous run to the peg if the required quantity of the corresponding part has not changed. For other replenisments (planned order or purchase requisitions), the assignment occurs according to the current requirements planning situation.
- Permitting or excluding split quantities by setting or not setting the relevant indicators.
- Permitting or excluding update of assignments for planned orders and purchase requisitions by setting or not setting the relevant indicators. In cost distribution this is not necessary because actual costs cannot be account assigned to planned orders and purchase requisitions.
In test systems it makes more sense to set the indicator for the purposes of analysis. In productive systems we do not recommend you set the indicator for performance reasons.
- Pegging exception handling category: You have the following options to assign exception pegs:
- Plant: Exception handling (Surplus, scrap and lost & found) assignment will be based on plant. If you select this option, you must define the master data WBS elements for exception handling (based on plant) in transaction PEG04.
- Group: Exception handling (Surplus, scrap and lost & found) assignment will be based on group. If you select this option, you must define the master data WBS elements for exception handling (based on group) in transaction PEG04.
- Plant+Group: Exception handling (Surplus, scrap and lost & found) assignment will be based on the combination of plant and group. If you select this option, you must define the master data WBS elements for exception handling (based on combination of plant and group) in transaction PEG04.
- The rules for assigning exceptions. You have the following options:
- Proportional assignment corresponding to existing material assignment relationships between individual WBS elements
- Separate WBS element to assign excess, scrap, and stock differences
- Retention duration in calendar months to archive and delete data.
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
ASAP Roadmap ID | 204 | Establish Functions and Processes |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | 0PEG01 | 0 | KAD0000007 | Pegging, Grouping, and Distribution |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
PEG_CLIENT | S - Table (with text table) | 0PEG01 |
History
Last changed by/on | SAP | 20021217 |
SAP Release Created in | 46C2 |