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

MSI_CUST008 - Overview

• 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