How To Fix /SAPAPO/PDEM_GEN_SRV087 - No demand history was read for product &1 using TDL

/SAPAPO/PDEM_GEN_SRV087 - Overview

• Message type: E = Error

• Message class: /SAPAPO/PDEM_GEN_SRV -

• Message number: 087

• Message text: No demand history was read for product &1 using TDL

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/PDEM_GEN_SRV087 - No demand history was read for product &1 using TDL ?

  The SAP error message /SAPAPO/PDEM_GEN_SRV087 indicates that no demand history was found for a specific product when using the Time-Dependent Location (TDL) in the Advanced Planning and Optimization (APO) module. This can occur in various scenarios, such as during demand planning or when trying to analyze historical data for a product.
  
  Cause:
  
  
  No Historical Data: The most common cause is that there is no demand history recorded for the specified product in the system. This could be due to:
  
  The product has not been sold or used in the specified time frame.
  The demand history has not been maintained or has been deleted.
  The product is newly created and has not yet had any transactions.
  
  
  
  Incorrect Configuration: There may be issues with the configuration of the planning area or the data model that prevent the demand history from being accessed.
  
  
  Data Transfer Issues: If the demand data is supposed to be transferred from another system (like SAP