Help with a COLLECT statement.

Question

I had to make changes to some code and these changes required me to add some fields to an internal table.  Below is what the table looked like before I made any changes:
DATA : BEGIN OF t_frgroup OCCURS 0,
    BEGIN CHANGE 02/11/03
        hazmat       TYPE c,
    END CHANGE 02/11/03
        mfrgr        LIKE lips-mfrgr,
        brgew        LIKE lips-brgew,
        lfimg        LIKE lips-lfimg,
        qtypal       LIKE w_nbr_palletsx,
        qtypce       LIKE w_nbr_palletsx,
        vstel        LIKE likp-vstel,
        no_cnvrt     TYPE c,
END OF t_frgroup.
This is what it looked like after I made the changes:
DATA : BEGIN OF t_frgroup OCCURS 0,
    BEGIN CHANGE 02/11/03
        hazmat       TYPE c,
    END CHANGE 02/11/03
        mfrgr        LIKE lips-mfrgr,
        brgew        LIKE lips-brgew,
        lfimg        LIKE lips-lfimg,
        qtypal       LIKE w_nbr_palletsx,
        qtypce       LIKE w_nbr_palletsx,
        vstel        LIKE likp-vstel,
        no_cnvrt     TYPE c,
        matnr        TYPE lips-matnr,
        vbeln        TYPE lips-vbeln,
        posnr        TYPE lips-posnr,
        qty          LIKE vblkp-lfimg,
        vrkme        LIKE lips-vrkme,
        converted(1) TYPE c VALUE 'N',
END OF t_frgroup.
My issue is, after adding those fields, my collect statement no longer works:
      LOOP AT t_lips.
        MOVE-CORRESPONDING t_lips TO t_frgroup.
        COLLECT t_frgroup.
      ENDLOOP.
I need it to collect with the key being mfrgr.  How can I do this?  After adding the fields the collect statement now acts as an insert (I assume that matnr is now acting as the key) instead of collect. 
Regards,
Aaron

Answer 1

Hi Aaron,
1. Define the table keys while defining your internal table.
2. The order of the fields in the structure should be that the key fields come first , then the quantity fields and amount fields next.
3. Sort the table by the key fields before the loop.
The collect statment is creating news entries because If the system finds an entry with the key fields , the numeric fields that are not part of the table key are added to the sum total of the existing entries. If it does not find an entry, the system creates a new entry instead. Clearly the system is unable to find the existing entry because the key fields are not defined in your internal table or the fields are are out of order.
Hope this helps.
A simple example depicting this is as follows :
TYPES: BEGIN OF COMPANY,
        NAME(20) TYPE C,
        SALES    TYPE I,
      END OF COMPANY.
DATA: COMP    TYPE COMPANY,
      COMPTAB TYPE HASHED TABLE OF COMPANY
                                WITH UNIQUE KEY NAME.
COMP-NAME = 'Duck'.  COMP-SALES = 10. COLLECT COMP INTO COMPTAB.
COMP-NAME = 'Tiger'. COMP-SALES = 20. COLLECT COMP INTO COMPTAB.
COMP-NAME = 'Duck'.  COMP-SALES = 30. COLLECT COMP INTO COMPTAB.
regards,
Advait Gode.
Edited by: Advait Gode on Mar 28, 2008 3:50 PM