How To Fix SD_CDS_READ_API036 - Condition generation: Invalid stack asc_pos &1: &2 = &3

SD_CDS_READ_API036 - Overview

• Message type: E = Error

• Message class: SD_CDS_READ_API -

• Message number: 036

• Message text: Condition generation: Invalid stack asc_pos &1: &2 = &3

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_API036 - Condition generation: Invalid stack asc_pos &1: &2 = &3 ?

  The SAP error message SD_CDS_READ_API036 typically indicates an issue related to condition generation in the Sales and Distribution (SD) module. The message specifically states that there is an "Invalid stack" for a condition record, which can occur due to various reasons. Here’s a breakdown of the potential causes, solutions, and related information:
  Causes:
  
  Invalid Condition Records: The condition records may be corrupted or not properly maintained in the system.
  
  Configuration Issues: There may be issues with the configuration of condition types, access sequences, or pricing procedures.
  Data Inconsistencies: Inconsistencies in master data (like customer or material master) can lead to issues in condition determination.
  Custom Code: If there are custom enhancements or modifications in the pricing logic, they might be causing the error.
  Transport Issues: If the configuration or condition records were transported from one system to another, there might be inconsistencies.
  
  Solutions:
  
  
  Check Condition Records: Verify the condition records for the relevant condition types. Ensure they are