How To Fix SD_EXPRESSION070 - Datatypes CURR and QUAN currently not supported at this position

SAP Error Message - Details

• Message type: E = Error

• Message class: SD_EXPRESSION - Messages processing AST expressions

• Message number: 070

• Message text: Datatypes CURR and QUAN currently not supported at this position

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_EXPRESSION070 - Datatypes CURR and QUAN currently not supported at this position ?

  The SAP error message SD_EXPRESSION070 indicates that there is an issue with the use of data types CURR (currency) and QUAN (quantity) in a specific context where they are not supported. This error typically arises in the context of pricing procedures, condition records, or when defining calculations in sales and distribution (SD) processes.
  
  Cause:
  
  Inappropriate Data Type Usage: The error occurs when you attempt to use CURR or QUAN data types in a context that does not support them, such as in certain formula calculations or conditions where only specific data types (like CHAR or NUMC) are allowed.
  Incorrect Configuration: It may also arise from incorrect configuration in pricing procedures or condition types where the system expects a different data type.
  Custom Logic: If there is custom logic or user-exits that manipulate pricing or conditions, they may inadvertently introduce CURR or QUAN in unsupported contexts.
  
  
  Solution:
  
  Review Pricing Procedure: Check the pricing procedure and ensure that