How To Fix PRF_CNTRL_MSG087 - Procurement Data is not required for Doc typ &1 and Co-code &2

SAP Error Message - Details

• Message type: E = Error

• Message class: PRF_CNTRL_MSG - Message Class for control messages of PRF

• Message number: 087

• Message text: Procurement Data is not required for Doc typ &1 and Co-code &2

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 PRF_CNTRL_MSG087 - Procurement Data is not required for Doc typ &1 and Co-code &2 ?

  The SAP error message PRF_CNTRL_MSG087 indicates that procurement data is not required for a specific document type and company code. This message typically arises in the context of purchasing documents, such as purchase orders or requisitions, when the system expects certain procurement-related information but finds that it is not necessary for the specified document type and company code.
  Cause:
  
  Document Type Configuration: The document type you are using may be configured in such a way that it does not require procurement data. This can happen if the document type is set up for a specific purpose that does not involve procurement.
  Company Code Settings: The company code settings may dictate that procurement data is not needed for certain document types. This can be due to specific business processes or configurations.
  Missing Configuration: There may be a missing or incorrect configuration in the purchasing or procurement settings that leads to this error.
  
  Solution:
  
  
  Check Document Type Configuration:
  
  Go to the configuration settings for the document type in question (Transaction Code: OME9 for purchasing document types).
  Verify if the document type is set to require procurement data. If it is not, you may need to adjust the settings based on your business requirements.
  
  
  
  Review Company Code Settings:
  
  Check the settings for the company code (Transaction Code: OX02 for company code settings).
  Ensure that the company code is configured to allow procurement data for the relevant document types.
  
  
  
  Consult with Functional Team:
  
  If you are unsure about the configuration or the implications of changing it, consult with your SAP functional team or a consultant who specializes in SAP MM (Materials Management) or procurement processes.
  
  
  
  Testing:
  
  After making any changes, perform tests to ensure that the error no longer occurs and that the procurement process works as expected.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or additional guidance related to this error message. SAP Notes can provide insights into specific configurations or patches that may resolve the issue.
  Documentation: Review SAP documentation related to purchasing document types and procurement data requirements to better understand the configurations and settings.
  User Training: Ensure that users are trained on the correct document types and processes to avoid confusion and errors in the future.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.