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

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPAPO/PDEM -

• Message number: 890

• Message text: Selection does not return any records to save in EXT 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.

Smart SAP Assistant

• What is the cause and solution for SAP error message /SAPAPO/PDEM890 - Selection does not return any records to save in EXT Demand table ?

  The SAP error message /SAPAPO/PDEM890 Selection does not return any records to save in EXT Demand table typically occurs in the context of SAP Advanced Planning and Optimization (APO) when there is an attempt to save external demand data, but the selection criteria do not yield any records. Here’s a breakdown of the potential causes, solutions, and related information for this error:
  Causes:
  
  Incorrect Selection Criteria: The selection criteria used to fetch external demand data may be too restrictive or incorrect, leading to no records being found.
  Data Not Available: There may simply be no external demand data available in the system for the specified time period or other selection parameters.
  Data Deletion: The external demand data might have been deleted or not yet created in the system.
  Authorization Issues: The user may not have the necessary authorizations to view or access the external demand data.
  Configuration Issues: There may be configuration issues in the APO system that prevent the correct fetching of external demand data.
  
  Solutions:
  
  Review Selection Criteria: Check the selection criteria used in the transaction or program that triggered the error. Ensure that the criteria are set correctly and are not overly restrictive.
  Check Data Availability: Verify if there is any external demand data available in the system for the specified parameters. You can do this by running a report or transaction that lists external demand.
  Data Creation: If no data exists, ensure that the external demand data is created and available in the system before attempting to save it.
  Authorization Check: Ensure that the user has the necessary authorizations to access and manipulate external demand data. This can be checked with the security team or by reviewing user roles.
  Configuration Review: Consult with your SAP Basis or APO configuration team to ensure that the system is correctly set up to handle external demand data.
  Debugging: If the issue persists, consider debugging the program or transaction to identify where the selection is failing.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as /SAPAPO/EXTDEMAND for managing external demand.
  SAP Notes: Check for any relevant SAP Notes that might address known issues or bugs related to external demand processing.
  Documentation: Review SAP documentation related to APO and external demand management for best practices and troubleshooting steps.
  Community Forums: Engage with SAP community forums or support channels for additional insights and shared experiences from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.