How To Fix /SAPAPO/PDRP_APPR086 - Document &1: Annonymous PR - no source of supply defined

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/PDRP_APPR -

• Message number: 086

• Message text: Document &1: Annonymous PR - no source of supply defined

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 /SAPAPO/PDRP_APPR086 - Document &1: Annonymous PR - no source of supply defined ?

  The SAP error message /SAPAPO/PDRP_APPR086 indicates that there is an anonymous Purchase Requisition (PR) in the system that does not have a source of supply defined. This typically occurs in the context of Advanced Planning and Optimization (APO) when the system is trying to process a demand or supply planning scenario, and it cannot find a valid source for the specified purchase requisition.
  Cause:
  
  Anonymous Purchase Requisition: The PR is created without a specific source of supply assigned to it. This can happen if the PR was created manually or if there was an issue during the planning run that did not assign a source.
  Missing Source of Supply: The system may not have any valid source of supply defined for the material in question. This could be due to missing vendor information, incorrect planning settings, or issues with the material master data.
  Planning Parameters: The planning parameters may not be set up correctly, leading to the system not being able to determine a source of supply.
  
  Solution:
  
  Check Purchase Requisition: Review the details of the anonymous PR in the system. You can do this by navigating to the relevant transaction (e.g., ME53N for display) and checking if a source of supply is assigned.
  Assign Source of Supply: If the PR is indeed anonymous, you may need to manually assign a source of supply. This can be done by creating a purchase order or by updating the PR with a valid vendor.
  Review Material Master Data: Ensure that the material master data is correctly maintained. Check the purchasing view to confirm that valid vendors are assigned and that the necessary purchasing info records exist.
  Check Planning Settings: Review the planning settings in APO to ensure that the system is configured to determine sources of supply correctly. This includes checking the sourcing strategy and any relevant planning parameters.
  Run Planning Again: After making the necessary adjustments, you may need to run the planning process again to see if the issue is resolved.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME53N (Display Purchase Requisition), ME21N (Create Purchase Order), and /SAPAPO/SDP94 (Display Planning Book).
  Documentation: Refer to SAP documentation for detailed information on managing purchase requisitions and sources of supply in APO.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to this error message or provide additional troubleshooting steps.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.