topic Re: WHERE clause items dropped when Open SQL is translated in Application Development and Automation Discussions

WHERE clause items dropped when Open SQL is translated

Former Member — Tue, 14 Aug 2012 15:13:04 GMT

Does anyone know why the following open SQL statement:

* Fetching data from faglflexa table
   SELECT docnr
          buzei
          HSL
          ryear
          rldnr
          rbukrs
          docln
          prctr
           FROM faglflexa
           INTO TABLE it_belnr_prctr
           FOR ALL ENTRIES IN it_pos
           WHERE rldnr = '0L'               AND
                 rbukrs = it_pos-bukrs      AND
                 ryear  = it_pos-gjahr      AND
                 poper  = it_pos-poper      AND
                 docnr  = it_pos-belnr      AND
                 buzei  = it_pos-buzei      AND
                 prctr IN s_prctr.

Would be translated to the following when looking at the statement from DBACOCKPIT?

SELECT "DOCNR" AS c,"BUZEI" AS c,"HSL" AS c,"RYEAR" AS c,"RLDNR" AS c,"RBUKRS"

AS c,"DOCLN" AS c,"PRCTR" AS c

FROM "FAGLFLEXA"

WHERE "RCLNT" = @P1

Where are the rest of the WHERE clause items? The reason I ask is because it seems to be really slow. Thanks!

Re: WHERE clause items dropped when Open SQL is translated

ThomasZloch — Tue, 14 Aug 2012 16:41:28 GMT

Looks like it is just truncated, as it is the case e.g. in the ST05 overview. Can you doubleclick on the statement to see it in full glory? If not, try an SQL trace.

Thomas

Re: WHERE clause items dropped when Open SQL is translated

Former Member — Tue, 14 Aug 2012 18:08:27 GMT

Yeah, you're right... just truncated. DOH!