topic Re: SELECT statement in Application Development and Automation Discussions

SELECT statement

Former Member — Mon, 23 Oct 2006 13:23:40 GMT

Hi All!

I just start to learn ABAP ...so this question maybe is not difficult but I didn't find an answer on my own. I have the ABAP code:

.....

SELECT A_{VBELN A}FKART A_{VKORG A}VTWEG A_{KKBER A}SPART

A_{KUNAG A}FKDAT A_{ERNAM A}ERZET B~WERKS

INTO table IT_VBRK

FROM VBRK AS A INNER JOIN

VBRP AS B ON

A_{VBELN = B}VBELN

WHERE FKDAT = DATAF.

SORT IT_VBRK BY VBELN.

LOOP AT IT_VBRK.

AT NEW VBELN.

WRITE : /5 IT_VBRK-VBELN , IT_VBRK-FKDAT , IT_VBRK-FKART .

ENDAT.

AT END OF VBELN.

ENDAT.

ENDLOOP.

......

And the result is:

.........

90080973 *..*** ****

90080974 *..*** ****

90080975 *..*** ****

.........

Why the system don't write the date and the type of the invoices? It's something wrong with the SELECT statement?

Thank you very much.

Florina

Re: SELECT statement

Former Member — Mon, 23 Oct 2006 13:25:11 GMT

Why the system don't write the date and the type of the invoices? It's something wrong with the SELECT statement?

There is nothing wrong with the select statement..it is due to the control statement AT NEW.

Basically, the way AT NEW event works is that it asteriks all the fields to the right of the defined field. So in your case AT NEW VBELN all the fields to the right of VBELN in the internal table are replaced be asterix. To get the value you can initialise another field string similar to itab and move that before AT event and you can use the values from field strings.

Message was edited by: Anurag Bankley

Re: SELECT statement

Former Member — Mon, 23 Oct 2006 13:26:21 GMT

Hi Florina,

Your select is Good.

The Culprit is the at new statement.

you should read the internal table immediatley after a at new statement.

SORT IT_VBRK BY VBELN.

LOOP AT IT_VBRK.

AT NEW VBELN.

read table it_vbrk index sy-tabix.

WRITE : /5 IT_VBRK-VBELN , IT_VBRK-FKDAT , IT_VBRK-FKART .

ENDAT.

AT END OF VBELN.

ENDAT.

ENDLOOP.

Make the highlighted change.

Regards,

Ravi

Re: SELECT statement

RichHeilman — Mon, 23 Oct 2006 13:26:56 GMT

The effect is coming from the AT NEW statement, you can get around it by doing this. Define a wa, and move the line into it before the AT NEW, and use the WA to write out the data.

data: wa_vbrk like line of it_vbrk.

LOOP AT IT_VBRK.

wa_vbrk = it_vbrk.

AT NEW VBELN.

WRITE : /5 wa_VBRK-VBELN , wa_VBRK-FKDAT , wa_VBRK-FKART .

ENDAT.

AT END OF VBELN.

ENDAT.

ENDLOOP.

Regards,

Rich Heilman

Message was edited by: Rich Heilman

Re: SELECT statement

Former Member — Mon, 23 Oct 2006 13:43:36 GMT

Thank you all!

Maybe was a stupid question but asking stupid question I'm learning .

I hope I didn't offend you ;).

Thanks again.

Florina

Re: SELECT statement

Former Member — Mon, 23 Oct 2006 13:45:36 GMT

"There are no stupid questions. There are only questions"-- Anonymous

Re: SELECT statement

RichHeilman — Mon, 23 Oct 2006 13:45:46 GMT

Floirna, Ravi's answer may work, but you are then reading the same internal table line twice. This is not a good thing, in my example, you are only reading the line once. This will be important when performance is an issue.

Regards,

Rich Heilman

Re: SELECT statement

Former Member — Mon, 23 Oct 2006 13:55:22 GMT

Thank you.

There is an transaction to measure the report performance?

Florina

Re: SELECT statement

Former Member — Mon, 23 Oct 2006 13:57:02 GMT

Yes .

se30 is the tcode for performance analysis of programs.

regards,

ravi

Re: SELECT statement

RichHeilman — Mon, 23 Oct 2006 13:57:29 GMT

Transaction SE30.

Regards,

Rich Heilman

Re: SELECT statement

Former Member — Mon, 23 Oct 2006 14:02:19 GMT

Thank you again all of you!

Best regards,

Florina