How To Fix ORF1008 - Selection criterion is presently not supported

ORF1008 - Overview

• Message type: E = Error

• Message class: ORF1 - Spare Parts Stock Calculation

• Message number: 008

• Message text: Selection criterion is presently not supported

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 ORF1008 - Selection criterion is presently not supported ?

  The SAP error message ORF1008, which states "Selection criterion is presently not supported," typically occurs when you are trying to execute a report or transaction that includes selection criteria that are not supported by the underlying data model or the specific transaction you are using. This can happen for various reasons, including:
  Causes:
  
  Unsupported Fields: The selection criteria may include fields that are not available or not supported in the context of the report or transaction.
  Data Model Limitations: The data model for the report may not support certain types of selections, such as complex joins or aggregations.
  Transaction Restrictions: Some transactions have specific restrictions on the selection criteria that can be used, and using unsupported criteria can trigger this error.
  Custom Development Issues: If the report or transaction has been customized, there may be issues with the custom code that lead to unsupported selection criteria.
  
  Solutions:
  
  Review Selection Criteria: Check the selection criteria you are using