Do you have any question about this error?
Message type: E = Error
Message class: PMMO_PEGGING - Messages for Pegging in PMMO
Message number: 035
Message text: Assignment not possible: missing master data &1, group &2, MRP area &3
Pegging assignment is not possible because of missing master data: &V1&,
grouping WBS element &V2&, MRP area &V3&
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Add the missing master data using the transaction
<DS:TRAN.PMMO_PEGEXC>Assign Exceptions.</>
INCLUDE PMMO_MMI_CUSTOMIZABLE_MSG OBJECT DOKU ID TX LANGUAGE EN
Error message extract from SAP system. Copyright SAP SE.
PMMO_PEGGING035
- Assignment not possible: missing master data &1, group &2, MRP area &3 ?The SAP error message PMMO_PEGGING035 indicates that there is an issue with the assignment of a material to a production order or a planned order due to missing master data. This error typically arises in the context of Production Planning (PP) and Material Requirements Planning (MRP) when the system cannot find the necessary master data for the specified material, group, or MRP area.
Cause:
The error can be caused by several factors, including:
Missing Material Master Data: The material specified in the error message may not have been created or may be incomplete in the Material Master (transaction code MM01/MM02).
Missing MRP Area: The MRP area specified in the error message may not be defined for the material. MRP areas are used to manage stock and planning at a more granular level.
Missing or Incorrect Group Data: The group (e.g., production version, planning group) may not be defined or may not be correctly assigned to the material.
Configuration Issues: There may be configuration issues in the system that prevent the assignment of the material to the production order or planned order.
Solution:
To resolve the PMMO_PEGGING035 error, you can take the following steps:
Check Material Master Data:
- Use transaction code MM03 to display the material master data for the material in question.
- Ensure that all necessary views (e.g., Basic Data, MRP, Work Scheduling) are maintained correctly.
Verify MRP Area:
- Check if the MRP area specified in the error message is defined for the material. You can do this by navigating to the MRP area settings in the material master.
- If the MRP area is missing, you may need to create it or assign the material to an existing MRP area.
Check Group Data:
- Verify that the group (e.g., production version, planning group) is correctly defined and assigned to the material.
- If necessary, create or update the group data using the appropriate transaction codes (e.g., C223 for production versions).
Review Configuration:
- Check the configuration settings related to MRP and production planning to ensure that they are set up correctly.
- Consult with your SAP configuration team if you suspect any configuration issues.
Consult Documentation:
- Review SAP documentation or notes related to the specific error message for additional insights or updates.
Testing:
- After making the necessary changes, test the process again to see if the error persists.
Related Information:
By following these steps, you should be able to identify and resolve the underlying issue causing the PMMO_PEGGING035 error in SAP.
Get instant SAP help. Start your 7-day free trial now.
PMMO_PEGGING034
Mandatory field "Exception Handling Category" (EXC_CAT) is not filled
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PMMO_PEGGING033
Mandatory field "Grouping WBS Element" (GRPNR) is not filled
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
PMMO_PEGGING036
Pegging assignment already exists for WBS element &1
What causes this issue? The WBS element &V1& is used in PMMO assignment records (table PMMO_ASSIGNMENT, field PSPNR_ASSGND). Do not delete th...
PMMO_PEGGING037
Rework order &1 pegged to NHA replen &2 ahead of earlier replenishments
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.