How To Fix /SAPAPO/PDEM806 - Period for date &1 cannot be determined

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/PDEM -

• Message number: 806

• Message text: Period for date &1 cannot be determined

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/PDEM806 - Period for date &1 cannot be determined ?

  The SAP error message /SAPAPO/PDEM806 Period for date &1 cannot be determined typically occurs in the context of SAP Advanced Planning and Optimization (APO) when the system is unable to determine a planning period for a specific date. This can happen for various reasons, and understanding the cause is essential for resolving the issue.
  Causes:
  
  
  Missing Period Definition: The planning period for the specified date may not be defined in the system. This can occur if the planning calendar or periods have not been set up correctly.
  
  
  Incorrect Date Format: The date provided may not be in the expected format or may not correspond to a valid date in the system.
  
  
  Period Validity: The date might fall outside the defined validity period of the planning version or the planning book.
  
  
  Master Data Issues: There may be issues with the master data, such as missing or incorrect entries for the product, location, or other relevant entities.
  
  
  Configuration Issues: There could be configuration issues in the APO system that prevent the correct determination of periods.
  
  
  Solutions:
  
  
  Check Period Definitions: Verify that the planning periods are correctly defined in the system. You can do this by checking the configuration settings in the SAP APO system.
  
  
  Validate Dates: Ensure that the date you are using is valid and correctly formatted. Check if the date falls within the defined planning horizon.
  
  
  Review Planning Version: Make sure that the planning version you are using is active and that the date falls within its validity period.
  
  
  Check Master Data: Review the relevant master data (e.g., product master, location master) to ensure that all necessary entries are present and correct.
  
  
  Consult Configuration: If you suspect configuration issues, consult with your SAP Basis or APO configuration team to review the settings related to planning periods and calendars.
  
  
  Use Transaction Codes: Utilize transaction codes like /SAPAPO/SDP94 (for planning book) or /SAPAPO/MC62 (for checking periods) to analyze the planning book and periods.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Refer to the SAP Help Portal for detailed documentation on planning periods and configuration in SAP APO.
  Community Forums: Engage with SAP community forums or user groups for insights from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it. If the issue persists, consider reaching out to SAP support for further assistance.