How To Fix SD_CDS_READ_API035 - Condition generation: Invalid stack expr type: &1

SD_CDS_READ_API035 - Overview

• Message type: E = Error

• Message class: SD_CDS_READ_API -

• Message number: 035

• Message text: Condition generation: Invalid stack expr type: &1

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 SD_CDS_READ_API035 - Condition generation: Invalid stack expr type: &1 ?

  The SAP error message SD_CDS_READ_API035 Condition generation: Invalid stack expr type: &1 typically occurs in the context of condition processing in the Sales and Distribution (SD) module. This error indicates that there is an issue with the condition records or the way conditions are being evaluated in the system.
  
  Cause:
  
  
  Invalid Condition Records: The error may arise due to invalid or corrupted condition records in the pricing procedure. This can happen if the condition types are not properly defined or if there are inconsistencies in the condition records.
  
  
  Custom Code Issues: If there are custom enhancements or modifications in the pricing logic, they may lead to unexpected behavior, resulting in this error.
  
  
  Data Inconsistencies: Inconsistent or missing data in master data (like customer master, material master, etc.) can also lead to this error.
  
  
  
  Configuration Issues: Incorrect configuration in the pricing procedure or condition types can lead to this error.
  
  
  
  Solution:
  
  
  Check Condition Records: 
  
  Go to transaction VK13