String functions in MACRO SQL()

Answered

Scott McClure

• January 30, 2017 22:16

It seems that not all string (or other) functions are supported in the SQL() function available in a MACRO.  At the moment I would like to user either CHAR() or ASCII() to detect a single quote mark in a field on the screen but any attempt is met with an error.

Is there a list of supported SQL functions that are not supported in the MACRO SQL()?

Maybe the better question is whether my premise is correct?

Vote

2

• Official comment

  

  Yaremi Miranda Lopez

  • February 01, 2017 14:28

  Hello Scott,

   

  The supported SQL command supported should be the same as what SAP can run in the SAP query-manager.
• 

  Scott McClure

  • February 01, 2017 19:06

  Yes, I see that this is the case.  However, I need to re-work my question.  I am trying to detect the presence of an apostrophe embedded in a field and take action based on that.  While I can "escape" the character in Query manager (and SQL query analyzer) all my attempts in a macro have failed.  Functions work with other characters but when the apostrophe is encountered it is treated as an unbalanced quote.  I can see it well enough to display it in a message as a single character but cannot compare it directly and cannot get it to compare to CHAR(39).

  Can you provide any tip to help with this?  There must be a way!
• 

  Scott McClure

  • February 01, 2017 20:02

  For what it's worth, found that s @STORE var worked differently than a field referred to by dynamic syntax.  When I replaced '@STORE3' which had been set to $[$7.0.0] (CardName on Business Partner) with simply $[$7.0.0] all worked.

  There are just a lot of syntax engines in play - hard to get them all aligned.

Please sign in to leave a comment.