How To Fix /SAPAPO/PDEM868 - No BOD Found for Product &1 and Facing location &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/PDEM -

• Message number: 868

• Message text: No BOD Found for Product &1 and Facing location &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 /SAPAPO/PDEM868 - No BOD Found for Product &1 and Facing location &2 ?

  The SAP error message /SAPAPO/PDEM868 No BOD Found for Product &1 and Facing location &2 typically occurs in the context of SAP Advanced Planning and Optimization (APO), particularly when dealing with Demand Planning or Supply Network Planning. This error indicates that there is no Bill of Distribution (BOD) found for the specified product and location combination.
  Cause:
  
  Missing BOD Configuration: The most common cause is that the Bill of Distribution (BOD) has not been defined for the specified product and location in the system.
  Data Inconsistency: There may be inconsistencies in the master data, such as missing or incorrect entries in the product master or location master.
  Planning Area Issues: The planning area may not be correctly set up to include the product or location in question.
  Incorrect Key Figures: The key figures used in the planning process may not be correctly defined or populated.
  
  Solution:
  
  
  Check BOD Configuration:
  
  Go to the transaction code /SAPAPO/BOD to check if the BOD is defined for the product and location.
  If it is missing, you will need to create or update the BOD for the relevant product and location.
  
  
  
  Verify Master Data:
  
  Ensure that the product master data is correctly maintained. Check the product's details in transaction code /SAPAPO/MAT1.
  Verify that the location master data is also correctly maintained in transaction code /SAPAPO/LOC1.
  
  
  
  Review Planning Area:
  
  Check if the planning area includes the product and location. You can do this by reviewing the planning area settings in transaction code /SAPAPO/PA (Planning Area).
  
  
  
  Check Key Figures:
  
  Ensure that the key figures relevant to the BOD are correctly defined and populated. You can check this in the planning book or by using transaction code /SAPAPO/MC62.
  
  
  
  Run Consistency Checks:
  
  Use the consistency check tools available in SAP APO to identify any inconsistencies in the data that may be causing the issue.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help notes for additional guidance on BOD configuration and troubleshooting.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  /SAPAPO/BOD: To manage and view BODs.
  /SAPAPO/MAT1: To view and maintain product master data.
  /SAPAPO/LOC1: To view and maintain location master data.
  /SAPAPO/PA: To manage planning areas.
  /SAPAPO/MC62: To check key figures.
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to BODs or the error message in question.
  
  
  Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP APO expert for further assistance.