topic Re: extracting only one record in Application Development and Automation Discussions

extracting only one record

Former Member — Thu, 07 Jul 2005 16:20:56 GMT

Hi,

I am using the Field Catalog to display the contents of my internal table. One of the entries being displayed is the payment date. I just want to display only entries corresponding to the last payment date. Should I make another internal table and move the entries which I require to the new table or is there a way by which I can display only entires I require in my first internal table with the given constraint?

I know its a bit confusing but I can post my source code if you want.

Thanks in advance,

Gaurav

Re: extracting only one record

RichHeilman — Thu, 07 Jul 2005 16:31:17 GMT

I would probably move the records to a new internal table. You may want to use a the AT END OF statement.

Say that you have an internal table with the vendor and the payment date. Sort the internal table by vendor and payment date. Now loop at the internal table and when the last record for a specific vendor is read, move that record to another internal table. Use the second internal table to show in ALV.

Here is a short sample.



report zrich_0004 .


data: begin of itab occurs 0,
      lifnr type lfa1-lifnr,
      pydat type sy-datum,
      end of itab.

data: begin of itab2 occurs 0,
      lifnr type lfa1-lifnr,
      pydat type sy-datum,
      end of itab2.

data: wa like line of itab.

itab-lifnr = '1'.
itab-pydat = '20050709'.
append itab.

itab-lifnr = '1'.
itab-pydat = '20050708'.
append itab.

itab-lifnr = '1'.
itab-pydat = '20050707'.
append itab.

itab-lifnr = '2'.
itab-pydat = '20050712'.
append itab.

itab-lifnr = '2'.
itab-pydat = '20050711'.
append itab.

itab-lifnr = '2'.
itab-pydat = '20050710'.
append itab.


sort itab ascending by lifnr pydat.

loop at itab.
  wa = itab.
  at end of lifnr.
    move-corresponding wa to itab2.
    append itab2.
  endat.
endloop.


loop at itab2.
  write:/ itab2-lifnr, itab2-pydat.
endloop.

Regards,

Rich Heilman

Re: extracting only one record

Former Member — Thu, 07 Jul 2005 16:38:52 GMT

Hi Gaurav,

it's pretty difficult for me to understand your question when you say "I am using the Field Catalog to display the contents of my internal table". I assume you are using ABAP List Viewer (ALV).

If so, and if you're using ALV based on function modules, there is an import parameter named IT_FILTER, which contains data to be filtered. Although the documentation on this parameter explicitly says "This table should never be built-up 'manually'", you may write your own test programs with this issue, at your own risk

I hope it helps. BR,

Alvaro

Re: extracting only one record

Former Member — Thu, 07 Jul 2005 17:12:04 GMT

Hi Alvaro,

I have heard about the IT_FILTER but I am not familiar with the syntax and how it works. I will stick with the new internal table suggestion.

Thanks for your reply,

Gaurav

Re: extracting only one record

RichHeilman — Thu, 07 Jul 2005 17:21:51 GMT

If your question has been answered please close the post and award points accordingly. Thanks.

Regards,

Rich Heilman

Re: extracting only one record

Former Member — Thu, 07 Jul 2005 17:31:18 GMT

Hi Rich,

I have sorted the table in desecding order. So I have all the records arranged in descending order of payment date. So the structure of my table look like this

10 03/04 ...

11 03/04 ...

12 03/04 ...

13 02/04 ...

So I have to move the above records having different identification number to new table for the last date that is 03/04 in this case.

I am bit confused about how to use AT END OF statement. Can you please explain?

Thanks,

Gaurav

Re: extracting only one record

RichHeilman — Thu, 07 Jul 2005 17:44:34 GMT

Since you have sorting your table in descending order, then you will want to get the FIRST record of the sequence instead of the LAST. The AT END OF statement would work for you if you table had been sorted in ASCENDING order. You can use the AT NEW statement to get the first record of the sequence.

Regards,

Rich Heilman

Re: extracting only one record

RichHeilman — Thu, 07 Jul 2005 17:46:23 GMT

Check the changes to the sample program.




report zrich_0004 .


data: begin of itab occurs 0,
      lifnr type lfa1-lifnr,
      pydat type sy-datum,
      end of itab.

data: begin of itab2 occurs 0,
      lifnr type lfa1-lifnr,
      pydat type sy-datum,
      end of itab2.

data: wa like line of itab.

itab-lifnr = '1'.
itab-pydat = '20050709'.
append itab.

itab-lifnr = '1'.
itab-pydat = '20050708'.
append itab.

itab-lifnr = '1'.
itab-pydat = '20050707'.
append itab.

itab-lifnr = '2'.
itab-pydat = '20050712'.
append itab.

itab-lifnr = '2'.
itab-pydat = '20050711'.
append itab.

itab-lifnr = '2'.
itab-pydat = '20050710'.
append itab.


<b>sort itab by lifnr ascending
             pydat descending.</b>

loop at itab.
  wa = itab.
<b>at new lifnr.</b>
    move-corresponding wa to itab2.
    append itab2.
  endat.
endloop.


loop at itab2.
  write:/ itab2-lifnr, itab2-pydat.
endloop.

Regards,

Rich Heilman

Re: extracting only one record

RichHeilman — Thu, 07 Jul 2005 17:47:54 GMT

Taken from F1 help.

<i>

<b>AT - Control breaks with extracts</b>

Variants:

1. AT NEW f.

2. AT END OF f.

3. AT FIRST.

4. AT LAST.

5. AT fg.

Effect

In a LOOP which processes a dataset created with EXTRACT, you can use special control structures for control break processing. All these structures begin with AT and end with ENDAT. The sequence of statements which lies between is executed whenever a control break occurs.

You can use these key words for control break processing with extract datasets only if the active LOOP statement is processing an extract dataset.

The control level structure with extract datasets is dynamic. It corresponds exactly to the sort key of the extract dataset, i.e. to the order of fields in the field group HEADER by which the extract dataset was sorted.

At the end of a control group ( AT END OF, AT LAST), there are two types of control level information between AT and ENDAT:

If the sort key of the extract dataset contains a non-numeric field h (particularly in the field group HEADER), the field CNT(h) contains the number of control breaks in the (subordinate) control level h.

For extracted number fields g (see also ABAP Number Types), the fields SUM(g) contain the relevant control totals.

Notes

The fields CNT(h) and SUM(g) can only be addressed after they have been sorted. Otherwise, a runtime error may occur.

The fields CNT(h) and SUM(g) are filled with the relevant values for a control level at the end of each control group ( AT END OF, AT LAST), not at the beginning (AT FIRST, AT NEW).

When calculating totals with SUM(g), the system automatically chooses the maximum field sizes so that an overflow occurs only if the absolute value area limits are exceeded.

You can also use special control break control structures with LOOPs on internal tables.

Variant 1

AT NEW f.

Variant 2

AT END OF f.

Effect

f is a field from the field group HEADER. The enclosed sequence of statements is executed if

the field f occurs in the sort key of the extract dataset (and thus also in the field group HEADER) and

the field f or a superior sort criterion has a different value in the current LOOP line than in the preceding (AT NEW) or subsequent (AT END OF) record of the extract dataset.

If f is not an assigned field symbol, the control break criterion is ignored, and the subsequent sequence of statements is not executed. If a field symbol is assigned, but does not point to the HEADER field group, the system triggers a runtime error.

Example

DATA: NAME(30),

SALES TYPE I.

FIELD-GROUPS: HEADER, INFOS.

INSERT: NAME INTO HEADER,

SALES INTO INFOS.

...

LOOP.

AT NEW NAME.

NEW-PAGE.

ENDAT.

...

AT END OF NAME.

WRITE: / NAME, SUM(SALES).

ENDAT.

ENDLOOP.

Notes

If the extract dataset is not sorted before processing with LOOP, no control level structure is defined and the statements following AT NEW or AT END OF are not executed.

Fields which stand at hex zero are ignored by the control break check with AT NEW or AT END OF. This corresponds to the behavior of the SORT statement, which always places unoccupied fields (i.e. fields which stand at hex zero) before all occupied fields when sorting extract datasets, regardless of whether the sort sequence is in ascending or descending order.

Variant 3

AT FIRST.

Variant 4

AT LAST.

Effect

Executes the relevant series of statements just once - either on the first loop pass (with AT FIRST) or on the last loop pass (with AT LAST).

Variant 5

AT fg.

Addition:

... WITH fg1

Effect

This statement makes single record processing dependent on the type of extracted record.

The sequence of statements following AT fg are executed whenever the current LOOP record is created with EXTRACT fg (in other words: when the current record is a fg record).

Addition

... WITH fg1

Effect

Executes the sequence of statements belonging to AT fg WITH fg1 only if the record of the field group fg in the dataset is immediately followed by a record of the field group fg1.

Additional help

Control Level Processing

</i>

Regards,

Rich Heilman

Re: extracting only one record

Former Member — Thu, 07 Jul 2005 19:04:02 GMT

Hi Rich,

Thanks a lot. Its working fine now.

Thanks again.

Gaurav