Do you have any question about this error?
Message type: E = Error
Message class: /ACCGO/MBS_MSG -
Message number: 000
Message text: Only two items can be pegged
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
/ACCGO/MBS_MSG000
- Only two items can be pegged ?The SAP error message
/ACCGO/MBS_MSG000 Only two items can be pegged
typically occurs in the context of the SAP Advanced Planning and Optimization (APO) module, particularly when dealing with pegging in the context of production planning or inventory management. This error indicates that the system is trying to peg more than two items to a single demand or supply, which is not allowed.Cause:
- Pegging Limitations: The system has a limitation that allows only two items to be pegged to a single demand or supply. This is often a design choice to simplify the planning process and avoid complexity in the supply chain.
- Data Configuration: There may be a configuration issue or data inconsistency that is causing the system to attempt to peg more than two items.
- Planning Parameters: The planning parameters or settings in the system may not be correctly defined, leading to this error.
Solution:
- Review Pegging Relationships: Check the pegging relationships in the system. Ensure that only two items are pegged to the demand or supply in question. You may need to adjust the planning or production orders to comply with this limitation.
- Adjust Planning Parameters: Review and adjust the planning parameters in the system. This may involve changing the settings related to how items are pegged or how demand is fulfilled.
- Data Cleanup: If there are inconsistencies in the data, perform a cleanup to ensure that the pegging relationships are valid and do not exceed the limit.
- Consult Documentation: Refer to SAP documentation or help resources for specific guidance on how to manage pegging in your version of SAP.
- Contact SAP Support: If the issue persists and you cannot find a resolution, consider reaching out to SAP support for assistance. They may provide insights specific to your configuration or version.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
/ACCGO/LOAD_OUT058
Match reversal not allowed as storage settlement exists
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/ACCGO/LOAD_OUT057
Application document & is locked
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/ACCGO/MBS_MSG001
Completion indicator is checked, further pegging not allowed
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
/ACCGO/MBS_MSG002
Same types of contract not allowed
What causes this issue? The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Syst...
Click on this link to search all SAP messages.