How To Fix MSI_CUST008 - Message control for Purchasing: entry &1 &2 not found

SAP Error Message - Details

• Message type: E = Error

• Message class: MSI_CUST - Message Class for Customizing Load

• Message number: 008

• Message text: Message control for Purchasing: entry &1 &2 not found

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 MSI_CUST008 - Message control for Purchasing: entry &1 &2 not found ?

  The SAP error message MSI_CUST008 indicates that there is an issue with the message control for purchasing, specifically that an entry for the specified parameters (usually a combination of message type and message number) could not be found in the system. This error typically arises in the context of message determination in purchasing documents, such as purchase orders or purchase requisitions.
  Cause:
  
  Missing Configuration: The most common cause of this error is that the necessary configuration for message control in purchasing has not been set up correctly. This could mean that the message type or the specific message number does not exist in the system.
  Incorrect Message Type: The message type being referenced may not be valid for the purchasing document type you are working with.
  Data Entry Issues: There may be a typo or incorrect entry in the fields that are being used to determine the message.
  Custom Development: If there are custom developments or enhancements in the message determination process, they may not be functioning as expected.
  
  Solution:
  
  
  Check Message Control Configuration:
  
  Go to the transaction code NACE (Message Control).
  Select the application area for purchasing (e.g., Purchasing).
  Check if the message type and the corresponding message number are defined correctly.
  Ensure that the necessary conditions for triggering the message are met.
  
  
  
  Verify Message Type:
  
  Ensure that the message type you are trying to use is valid for the document type you are working with.
  Check if the message type is active and properly configured.
  
  
  
  Review Customizations:
  
  If there are any custom developments related to message determination, review the code to ensure it is functioning correctly.
  Check for any enhancements or user exits that might be affecting the message determination process.
  
  
  
  Test with Different Data:
  
  Try to replicate the issue with different data to see if the problem persists. This can help identify if the issue is data-specific.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to message control in purchasing for any additional insights or known issues.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: NACE (Message Control), ME21N (Create Purchase Order), ME22N (Change Purchase Order), ME23N (Display Purchase Order).
  SAP Notes: Check for any relevant SAP Notes that might address known issues with message control in purchasing.
  Custom Development: If your organization has custom developments, ensure that they are documented and that the developers are aware of the issue.
  
  By following these steps, you should be able to identify and resolve the cause of the MSI_CUST008 error in your SAP system.