Do you have any question about this error?
Message type: E = Error
Message class: GPDPEG - A&D GPD message classed used by Pegging only
Message number: 026
Message text: Fixing rule set to '2'; plnd orders and PReqs. not pegged in profile &1
According to the settings of the selected pegging run profile &V1&,
purchase orders and production orders will not be pegged.
Fixing rule automatically set to '<LS>2 - Purchase Orders and Production
Orders Fixed Otherwise MRP</>'.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
GPDPEG026
- Fixing rule set to '2'; plnd orders and PReqs. not pegged in profile &1 ?The SAP error message GPDPEG026 indicates that there is an issue with the pegging of planned orders and purchase requisitions (PReqs) in the context of a specific profile. This error typically arises in the context of production planning and control, particularly when using the SAP Advanced Planning and Optimization (APO) module or similar functionalities.
Cause:
The error message "Fixing rule set to '2'; plnd orders and PReqs. not pegged in profile &1" suggests that:
- Fixing Rule: The fixing rule is set to '2', which means that the system is configured to not allow pegging of planned orders and purchase requisitions to the specific profile indicated by &1.
- Pegging Configuration: The configuration for pegging in the system may not be set up correctly, or the planned orders and purchase requisitions do not meet the criteria for pegging as defined in the profile.
- Profile Settings: The profile settings may not allow for the pegging of certain types of orders or requisitions, leading to this error.
Solution:
To resolve this error, you can take the following steps:
Check Profile Settings:
- Go to the configuration settings for the profile indicated in the error message. Ensure that the profile allows for pegging of planned orders and purchase requisitions.
- Review the settings related to the fixing rule and adjust them if necessary.
Adjust Fixing Rule:
- If the fixing rule is set to '2', consider changing it to a value that allows pegging (e.g., '1' or '0') if it aligns with your business requirements.
Review Order Types:
- Ensure that the planned orders and purchase requisitions you are trying to peg are of the correct type and meet the criteria defined in the profile.
Consult Documentation:
- Review SAP documentation or help resources related to pegging and the specific profile you are using to understand the implications of the settings.
Testing:
- After making changes, test the configuration by attempting to create or process planned orders and purchase requisitions again to see if the error persists.
Seek Help from SAP Support:
- If the issue continues after checking the above points, consider reaching out to SAP support or consulting with an SAP expert who can provide more tailored assistance based on your specific system configuration.
Related Information:
By following these steps, you should be able to identify the root cause of the GPDPEG026 error and implement a suitable solution.
Get instant SAP help. Start your 7-day free trial now.
GPDPEG025
Exception category not maintained for pegging run profile &1
What causes this issue? Exception category not maintained for pegging run profile &V1&.System Response The system issues an error message an...
GPDPEG024
Fixing rule is not maintained for pegging run profile &1
What causes this issue? Fixing rule is not maintained for pegging run profile &V1&.System Response The system issues an error message and wi...
GPDPEG027
Material &1 in Plant &2 is not grouped
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
GPDPEG028
MRP Group &1 in Plant &2 is not relevant for grouping
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.