How To Fix /SAPAPO/PDEM826 - Selection does not return any records to save in STO Demand table

/SAPAPO/PDEM826 - Overview

• Message type: E = Error

• Message class: /SAPAPO/PDEM -

• Message number: 826

• Message text: Selection does not return any records to save in STO Demand table

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.

/SAPAPO/PDEM826 - Details

• The SAP error message /SAPAPO/PDEM826 Selection does not return any records to save in STO Demand table typically occurs in the context of SAP Advanced Planning and Optimization (APO) when there is an attempt to save or process data related to Stock Transport Orders (STO) demand, but the selection criteria do not yield any records.
  Causes:
  
  Incorrect Selection Criteria: The selection criteria used to fetch the records may be too restrictive or incorrect, leading to no records being found.
  Data Availability: There may be no relevant data in the system that meets the selection criteria. This could be due to data not being created or not being transferred correctly.
  
  Configuration Issues: There may be configuration issues in the APO system that prevent the correct data from being fetched.
  Master Data Issues: Missing or incorrect master data (like material master, vendor, or customer data) can lead to this error.
  Time Frame: The time frame specified for the