How To Fix /ACCGO/SCP_MSG090 - Nomination item &1 is not pegged

SAP Error Message - Details

• Message type: E = Error

• Message class: /ACCGO/SCP_MSG -

• Message number: 090

• Message text: Nomination item &1 is not pegged

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message /ACCGO/SCP_MSG090 - Nomination item &1 is not pegged ?

  The SAP error message /ACCGO/SCP_MSG090 indicates that a nomination item is not pegged, which typically means that there is a mismatch or a missing link between the nomination and the corresponding supply or demand elements in the system. This error is often encountered in the context of supply chain planning and logistics, particularly when dealing with nominations in the context of materials management or production planning.
  Cause:
  
  Missing Pegging Information: The nomination item may not have been properly linked to the corresponding supply or demand elements, such as production orders, purchase orders, or stock.
  Incorrect Configuration: There may be configuration issues in the system that prevent proper pegging from occurring.
  Data Inconsistencies: There could be inconsistencies in the master data or transaction data that lead to the nomination item not being pegged.
  Timing Issues: The nomination may have been created or modified after the pegging process was executed, leading to a lack of linkage.
  
  Solution:
  
  Check Nomination Configuration: Ensure that the nomination configuration is set up correctly in the system. This includes checking the settings for pegging and ensuring that all necessary parameters are defined.
  Review Master Data: Verify that the master data for materials, production orders, and other relevant entities is complete and accurate. Look for any missing or incorrect entries that could affect pegging.
  Reprocess Pegging: If the nomination was created or modified recently, try reprocessing the pegging logic to establish the necessary links. This may involve running specific background jobs or transactions that handle pegging.
  Manual Linking: If automatic pegging is not working, consider manually linking the nomination item to the appropriate supply or demand elements, if feasible.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance on handling this error in your version of SAP.
  Contact Support: If the issue persists, consider reaching out to SAP support or your internal IT team for further assistance. They may be able to provide insights based on system logs or specific configurations.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in diagnosing or resolving the issue, such as MD04 (Stock/Requirements List) or MD05 (Individual Display of MRP List).
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide patches or additional guidance.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.