Hi friends i have doubt on collect statement.

i have some problem with matnr which is repeating no.of times. so i tried using collect and selected some of the fields to collect. Now i need to collect those collected elements in to internal table and need to display those fields in an ouput. for example.
loop at sumtab.
matnr type s886-matnr,
avg1 type p decimals 3,
total type p decimals 3,
endloop.
and now using loop i am collecting. these fields using my itab.
loop at itab.
move-corresponding itab to sumtab.
collect sumtab.
clear sumtab.
endloop.
***here itab contains no.of other fields like qty,stock etc.
so after here i am using ALV to display the itab.
my problem is how to make SUMTAB fields tobe moved in itab.

Hi Kalyan,
   The collect statement works like this . (ex)
data: begin of itab occurs 0,
      name(10) type c,
      value(4) type n,
      end of itab.
itab-name = 'JACK'.
itab-value = 100.
append itab.
itab-name = 'PAT'.
itab-value = 200.
append itab.
itab-name = 'JACK'.
itab-value = 200.
append itab.
sort itab.
loop itab.
collect itab.
write: / itab-name, itab-value.
endloop.
<b>o/p:</b>
JACK 300
PAT 200

Similar Messages

Hi friends i have doubt on select statement

hi friends, i am using one ztable which contains around 60 fields. i would like to consider in to itab around 52 fields. for this i am using "select * from ztable into itab....". can u please suggest me how can i improve by selecting all the fields and without reducing performance.

Declare as below:
Select-options: s_matnr FOR mara-matnr.
Data: Begin of itab.
INCLUDE STRUCTURE mara.
Data: End of itab.
Clear itab.
Refresh itab.
Select * from mara
into table itab
where matnr = s_matnr.
if sy-subrc = 0.
SORT itab.
endif.
OR if you are selecting based on some internal table then use
FO ALL ENTRIES IN itab1.
Hope this helps you, it will also improve your performance.
Reward points and close the thread else revert back.

I have doubt in Read statement

Hi All.
I have doubt in Read statement .i need to convert following select statement as read statement .how can i change help me.
IF p_field1 IS INITIAL
     AND p_field2 IS INITIAL
     AND p_field3 IS INITIAL
     AND p_field4 IS INITIAL
     AND p_field5 IS INITIAL.
    SELECT *
          FROM zdbt
           INTO TABLE itab
           WHERE field5 = p_field5
           ORDER BY PRIMARY KEY.
    IF sy-subrc <> 0.
      MESSAGE s035.
    ENDIF.
ENDIF.
regards,
Jay.

hi
The READ statement is as below:
When u have a table already with values and to improve the performance u need to use this.
Reading Lines of Tables
To read a single line of any table, use the statement:
READ TABLE <itab> <key> <result>.
For the statement to be valid for any kind of table, you must specify the entry using the key and
not the index. You specify the key in the <key> part of the statement. The <result> part can
specify a further processing option for the line that is retrieved.
If the system finds an entry, it sets SY-SUBRC to zero, if not, it takes the value 4, as long as it is
not influenced by one of the possible additions. If the internal table is an index table, SY-TABIX
is set to the index of the line retrieved. If the table has a non-unique key and there are duplicate
entries, the first entry is read.
Thanks
Shiva

Hi friends i have doubt in dialog programming.

i am desiging the screen using table control. which is suppose to accept unit of measure as 'car' means carton, kg, and so on. so if i enter numerics it should not accept. can anybody tell me how can i restrict the user to enter only alphanumerics. thanks in advance.

Hello,
U can use the system table field ABCDE for checking if it has only alphabets.
system field == SY-ABCDE
Regards
Anurag

Hi friends i have doubt on set cursor.

i am using dialog programming. here in the first text field i am auto generating the number, so user should only suppose to enter the values for other repective fields only.but in execution the cursor is positioning at the first field. it should start from the second and so on.
i tried using SET CURSOR FIELD F2. but tbe result is same. please provide me guidence on this.

Hi,
In the PBO of the dialog module,write the following code :
SET CURSOR FIELD `FIELD2`.
Remember the FIELD2 is the name assigned to the textbox of the screen.
Best regards,
Prashant
PS : Please reward all helpful answers

Reg: Collect statement in internal table

Hi,
   Can any one tell me wether we can use the collect statement in an internal table which has no header line
if it can be used can anyone please send me a sample snippet
Thanks In ADVANCE
Guhapriyan Subrahmanyam

Hi Guhapriyan,
I have used the collect statement in the way as shown..
DATA : BEGIN of I_ALLOCATIONS OCCURS 0,
        PSPNR LIKE PRPS-PSPNR,
        PSPID LIKE PROJ-PSPID,
        PSPHI LIKE PRPS-PSPHI,
        POST1 LIKE PROJ-POST1,
        ZZLOB LIKE PROJ-ZZLOB,
        WERKS LIKE PROJ-WERKS,
        SOBID LIKE HRP1001-SOBID,
        OBJID LIKE HRP1001-OBJID,
        BEGDA LIKE HRP1001-BEGDA,
        ENDDA LIKE HRP1001-ENDDA,
        PROZT LIKE HRP1001-PROZT,
        LOB   LIKE HRP1000-STEXT,
        TEMP TYPE P decimals 2,
        TYPE(3),
        ZROLE LIKE PA0001-ZROLE,
        HOLID TYPE P decimals 2,
        LEAVE TYPE P decimals 2,
        DAYS TYPE P decimals 2,
       END of I_ALLOCATIONS.
DATA: I_ALLOCATION LIKE I_ALLOCATIONS OCCURS 0 WITH HEADER LINE.
************Populate I_ALLOCATIONS **************
LOOP AT I_ALLOCATIONS.
    COLLECT I_ALLOCATIONS INTO I_ALLOCATION.
ENDLOOP.
Actually i had requirement like u, but this one is rather simple...
Get the required data in an I_Table which dont require Header line..
Later on collect this particular I_Table in other I_Table1 with the Header Line...
Regards,
Abhishek

Hi i have some problem with collect statement.

hi when i am using collect statement and whn ever any field is modified it is getting doubled and showing doubled value. may i knoe what would be problem.

Hai Kumar
Go through the following Collect Syntax
COLLECT
Basic form
COLLECT [wa INTO] itab.
Addition
... SORTED BY f
Effect
COLLECT is used to create unique or compressed datsets. The key fields are the default key fields of the internal table itab .
If you use only COLLECT to fill an internal table, COLLECT makes sure that the internal table does not contain two entries with the same default key fields.
If, besides its default key fields, the internal table contains number fields (see also ABAP/4 number types ), the contents of these number fields are added together if the internal table already contains an entry with the same key fields.
If the default key of an internal table processed with COLLECT is blank, all the values are added up in the first table line.
If you specify wa INTO , the entry to be processed is taken from the explicitly specified work area wa . If not, it comes from the header line of the internal table itab .
After COLLECT , the system field SY-TABIX contains the index of the - existing or new - table entry with default key fields which match those of the entry to be processed.
Notes
COLLECT can create unique or compressed datasets and should be used precisely for this purpose. If uniqueness or compression are unimportant, or two values with identical default key field values could not possibly occur in your particular task, you should use APPEND instead. However, for a unique or compressed dataset which is also efficient, COLLECT is the statement to use.
If you process a table with COLLECT , you should also use COLLECT to fill it. Only by doing this can you guarantee that
the internal table will actually be unique or compressed, as described above and
COLLECT will run very efficiently.
If you use COLLECT with an explicitly specified work area, it must be compatible with the line type of the internal table.
Example
Compressed sales figures for each company
DATA: BEGIN OF COMPANIES OCCURS 10,
        NAME(20),
        SALES TYPE I,
      END   OF COMPANIES.
COMPANIES-NAME = 'Duck'. COMPANIES-SALES = 10.
COLLECT COMPANIES.
COMPANIES-NAME = 'Tiger'. COMPANIES-SALES = 20.
COLLECT COMPANIES.
COMPANIES-NAME = 'Duck'. COMPANIES-SALES = 30.
COLLECT COMPANIES.
The table COMPANIES now has the following appearance:
NAME SALES
Duck 40
Tiger 20
Addition
... SORTED BY f
Effect
COLLECT ... SORTED BY f is obsolete and should no longer be used. Use APPEND ... SORTED BY f which has the same meaning.
Note
Performance
The cost of a COLLECT in terms of performance increases with the width of the default key needed in the search for table entries and the number of numeric fields with values which have to be added up, if an entry is found in the internal table to match the default key fields.
If no such entry is found, the cost is reduced to that required to append a new entry to the end of the table.
A COLLECT statement used on a table which is 100 bytes wide and has a key which is 60 bytes wide and seven numeric fields is about approx. 50 msn (standardized microseconds).
Note
Runtime errors
COLLECT_OVERFLOW : Overflow in integer field when calculating totals.
COLLECT_OVERFLOW_TYPE_P : Overflow in type P field when calculating totals.
Thanks & regards
Sreenivasulu P

Issue while using Collect statement in program

Hi friend's,
i have some issue regarding Collect statement..
Issue is somthing like this,i have created a structure and internal table and work area with same type,
u can look in below code..i wann to collect 'enmng' f'ield value whose matnr,charg,mvt type ,aufnr,rsnum are same but rspos and lgort are differnt for this i need to collect 'ENMNG' field value can any one tel me what to do...it not collectng value instead of this it append entire row...
types: begin of ty_resb,
        rsnum   type resb-rsnum,                "Resrvation Number
        rspos   type resb-rspos,                "item position
        xloek   type resb-xloek,                "Item Deleted if = 'X'
        matnr   type resb-matnr,                "Material Number
        lgort   type resb-lgort,                "Storage location 'REJT'
        charg   type resb-charg,                "Batch No
        enmng   type resb-enmng,                "Quantity withdrawn should be greater then '0'
        enwrt   type resb-enwrt,                "Value Withdrawn
        aufnr   type resb-aufnr,                "Order
        bwart   type resb-bwart,                "Movement type
   end of ty_resb.
data:tt_resb type table of ty_resb ,
      tt_resb1 type table of ty_resb ,
      tt_resb2 type standard table of ty_resb ,
**workarea.
      ts_resb type ty_resb,
      ts_resb2 type ty_resb,
      ts_resb1 type ty_resb.
**move data to another internal table
tt_resb1[] = tt_resb[].
sort tt_resb by rsnum rspos matnr charg bwart lgort aufnr .
sort tt_resb1 by rsnum rspos matnr charg bwart lgort aufnr.
DELETE adjacent duplicates from tt_resb comparing rsnum rspos matnr charg bwart lgort aufnr .
DELETE adjacent duplicates from tt_resb1 comparing rsnum rspos matnr charg bwart lgort aufnr.
loop at tt_resb into ts_resb .
clear:ts_resb1,ts_resb2.
read table tt_resb1 into ts_resb1 with key rsnum = ts_resb-rsnum rspos = ts_resb-rspos matnr = ts_resb-matnr
                                            charg = ts_resb-charg aufnr = ts_resb-aufnr binary search.
if ts_resb1-bwart = '261' .
    move ts_resb1-aufnr to ts_resb2-aufnr.
    move ts_resb1-matnr to ts_resb2-matnr.
    move ts_resb1-charg to ts_resb2-charg.
    move ts_resb1-bwart to ts_resb2-bwart.
    move ts_resb1-enwrt to ts_resb2-enwrt.
    move ts_resb1-lgort to ts_resb2-lgort.
    move ts_resb1-enmng to ts_resb2-enmng.
    collect ts_resb2 into tt_resb2.
endif.
clear ts_resb.
endloop.
Regard's,
shaikh khalid.

Hi Shaikh,
I have added new declarations as highlighted below and new lines within your loop:
Execute your program in debug mode and see what happens to the internal tt_collect I added. The collect will sum the fields enmng for all entries that have same value on the fields matnr,charg,mvt type ,aufnr,rsnum.
Question from me: what do you want to do with the collected/Summed up entries?
types: begin of ty_resb,
        rsnum   type resb-rsnum,                "Resrvation Number
        rspos   type resb-rspos,                "item position
        xloek   type resb-xloek,                "Item Deleted if = 'X'
        matnr   type resb-matnr,                "Material Number
        lgort   type resb-lgort,                "Storage location 'REJT'
        charg   type resb-charg,                "Batch No
        enmng   type resb-enmng,                "Quantity withdrawn should be greater then '0'
        enwrt   type resb-enwrt,                "Value Withdrawn
        aufnr   type resb-aufnr,                "Order
        bwart   type resb-bwart,                "Movement type
   end of ty_resb.
data:tt_resb type table of ty_resb ,
      tt_resb1 type table of ty_resb ,
      tt_resb2 type standard table of ty_resb ,
types: begin of ty_collect,
rsnum   type resb-rsnum,
matnr   type resb-matnr,
charg   type resb-charg,
bwart   type resb-bwart,
aufnr   type resb-aufnr,
enmng   type resb-enmng,
       end of ty_collect.
data: tt_collect type table of ty_collect,
      ts_collect type ty_collect.
**workarea.
      ts_resb type ty_resb,
      ts_resb2 type ty_resb,
      ts_resb1 type ty_resb.
**move data to another internal table
tt_resb1[] = tt_resb[].
sort tt_resb by rsnum rspos matnr charg bwart lgort aufnr .
sort tt_resb1 by rsnum rspos matnr charg bwart lgort aufnr.
DELETE adjacent duplicates from tt_resb comparing rsnum rspos matnr charg bwart lgort aufnr .
DELETE adjacent duplicates from tt_resb1 comparing rsnum rspos matnr charg bwart lgort aufnr.
loop at tt_resb into ts_resb .
clear:ts_resb1,ts_resb2.
read table tt_resb1 into ts_resb1 with key rsnum = ts_resb-rsnum rspos = ts_resb-rspos matnr = ts_resb-matnr
                                            charg = ts_resb-charg aufnr = ts_resb-aufnr binary search.
if ts_resb1-bwart = '261' .
    move ts_resb1-aufnr to ts_resb2-aufnr.
    move ts_resb1-matnr to ts_resb2-matnr.
    move ts_resb1-charg to ts_resb2-charg.
    move ts_resb1-bwart to ts_resb2-bwart.
    move ts_resb1-enwrt to ts_resb2-enwrt.
    move ts_resb1-lgort to ts_resb2-lgort.
    move ts_resb1-enmng to ts_resb2-enmng.
    collect ts_resb2 into tt_resb2.
     move-corresponding ts_resb1 to ts_collect.
     collect ts_collect into tt_collect
endif.
clear ts_resb.
clear ts_collect.
endloop.

How to use collect statement properly

In PBID table , i will get 4 rows for a material . I will get the corresponding values of bdzei from the same table . Now i will pass this bdzei into pbhi table. then i will get some 200 rows of data. I have to sum up the field plnmg , by grouping the laeda field of pbhi. In short, i need to know the sum of pbhi-plnmg for a particular pbhi-laeda . I know a way to do it. But i want to know how to use the COLLECT statement for this purpose. My output should contain oly 1 line for 1 material ..
PBID table
Matnr   BDZEI
p4471   457
        1002
        2309
        2493
PBHI table
BDZEI     LAEDA         PLNMG
1002     06.08.2004     0.000
1002     06.08.2004     83.000
457      07.08.2004     12.000
457     07.08.2004     24.000
Reqd O/p
MATNR   LAEDA        PLNMG
p4471 06.08.2004    83
p4471 07.08.2004    36
Hope u understood my situation .please help me out ...
Thanking you in advance ..
Shankar

REPORT zppr_zpipr NO STANDARD PAGE HEADING LINE-SIZE 150 LINE-COUNT 63.
TABLES: pbid,
        pbhi,
        makt,
        mseg,
        mkpf.
DATA: BEGIN OF it_pbid OCCURS 0,
      matnr LIKE pbid-matnr,        " Material
      status TYPE c LENGTH 4,       " For distinguishing materials from pbid and pbim .. will contain space for PBID and 'PBIM' for PBIM
      bdzei LIKE pbid-bdzei,
      laeda LIKE pbhi-laeda,
end of it_pbid.
DATA: BEGIN OF it_pbim OCCURS 0,
      matnr LIKE pbid-matnr,        " Material
      status TYPE c LENGTH 4,       " For distinguishing materials from pbid and pbim .. will contain space for PBID and 'PBIM' for PBIM
      bdzei LIKE pbim-bdzei,
      laeda LIKE pbhi-laeda,
end of it_pbim.
DATA: BEGIN OF it_pbid_pbim OCCURS 0,
      matnr LIKE pbid-matnr,        " Material
      laeda LIKE pbhi-laeda,        " Reduction Date
      dbmng LIKE pbhi-dbmng,        " Planned quantity in the data base
      plnmg LIKE pbhi-plnmg,        " Planned quantity
      status TYPE c LENGTH 4,       " For distinguishing materials from pbid and pbim .. will contain space for PBID and 'PBIM' for PBIM
      mblnr LIKE mseg-mblnr,        " Material Doc Number
      pbfnr LIKE pbid-pbdnr,        " Plan Number
      maktx LIKE makt-maktx,         " Matl Desc
      aenam LIKE pbhi-aenam,        " User Changed
      erfmg LIKE mseg-erfmg,        " Qty Invoiced
      budat LIKE mkpf-budat,        " Invoice date
      bdzei LIKE pbid-bdzei,        " Independent requirements pointer
      werks LIKE pbid-werks,        " plant
      pirrednqty TYPE i,            " PIR Reduction Quantity        = pbih-plnmg - pbih-dbmng
      diff TYPE i,                  " Difference
      slno TYPE i,                  " Sl No
END OF it_pbid_pbim.
DATA: BEGIN OF it_allrows OCCURS 0.
        INCLUDE STRUCTURE it_pbid_pbim.
DATA: END OF it_allrows.
*DATA: BEGIN OF it_final OCCURS 0.
       INCLUDE STRUCTURE it_pbid_pbim.
*DATA: END OF it_final.
DATA: BEGIN OF line,
      matnr LIKE pbid-matnr,        " Material
      laeda LIKE pbhi-laeda,        " Reduction Date
      plnmg LIKE pbhi-plnmg,        " Planned quantity
      maktx LIKE makt-maktx,        " Matl Desc
      dbmng LIKE pbhi-dbmng,        " Planned quantity in the data base
      mblnr LIKE mseg-mblnr,        " Material Doc Number
      pbfnr LIKE pbid-pbdnr,        " Plan Number
      aenam LIKE pbhi-aenam,        " User Changed
      erfmg LIKE mseg-erfmg,        " Qty Invoiced
      budat LIKE mkpf-budat,        " Invoice date
      bdzei LIKE pbid-bdzei,        " Independent requirements pointer
      werks LIKE pbid-werks,        " plant
      pirrednqty TYPE i,            " PIR Reduction Quantity        = pbih-plnmg - pbih-dbmng
      diff TYPE i,                  " Difference
      slno TYPE i,                  " Sl No
      status TYPE c LENGTH 4,       " For distinguishing materials from pbid and pbim .. will contain space for PBID and 'PBIM' for PBIM
END OF line.
DATA Itfinal1 LIKE STANDARD TABLE
            OF LINE
          WITH DEFAULT KEY.
DATA ITfinal LIKE ITfinal1.
DATA: BEGIN OF it_dates OCCURS 0,
      date TYPE sy-datum,
END OF it_dates.
DATA: l_slno TYPE i.
DATA: l_zebra TYPE c.
SELECT-OPTIONS:
      s_werks FOR pbid-werks obligatory.
SELECT-OPTIONS:
      s_matnr FOR pbid-matnr.
SELECT-OPTIONS:
      s_pbdnr FOR pbid-pbdnr.
SELECT-OPTIONS:
      s_laeda FOR pbhi-laeda obligatory.
parameter:
      c_print type checkbox.
SELECT matnr bdzei FROM pbid INTO (it_pbid-matnr, it_pbid-bdzei) WHERE werks IN s_werks AND matnr IN s_matnr AND pbdnr IN s_pbdnr.
it_pbid-status = 'PBID'.
APPEND it_pbid.
move-corresponding it_pbid to it_pbid_pbim.
Append it_pbid_pbim.
ENDSELECT.
SELECT matnr bdzei FROM pbim INTO (it_pbim-matnr,it_pbim-bdzei) WHERE werks IN s_werks AND matnr IN s_matnr AND pbdnr IN s_pbdnr.
APPEND it_pbim.
Append it_pbid_pbim.
ENDSELECT.
*break-point.
START-OF-SELECTION.
LOOP AT s_laeda.
    it_dates-date = s_laeda-low.
    APPEND it_dates.
ENDLOOP.
DATA: l_startdate LIKE sy-datum.
IF s_laeda-high EQ space.
ELSE.
    l_startdate = s_laeda-low + 1.
    DO.
      IF l_startdate <= s_laeda-high.
        it_dates-date = l_startdate.
        APPEND it_dates.
      ELSE.
        it_dates-date = sy-datum.
        EXIT.
      ENDIF.
      l_startdate = l_startdate + 1.
    ENDDO.
ENDIF.
*break-point.
LOOP AT it_pbim.
    LOOP AT it_dates.
      it_pbim-laeda = it_dates-date.
      it_pbim-status = 'PBIM'.
      MODIFY it_pbim TRANSPORTING laeda status.
      MOVE-CORRESPONDING it_pbim TO it_pbid_pbim.
      APPEND it_pbid_pbim.
    ENDLOOP.
ENDLOOP.
break-point.
l_zebra = 'X'.
DATA: l_toterfmg LIKE mseg-erfmg.
DATA: l_erfmg LIKE mseg-erfmg.
data: l_totpir type i.
**************************************PBID*************************************
LOOP AT it_pbid.
    move-corresponding it_pbid to it_pbid_pbim.
       append it_pbid_pbim.
    SELECT SINGLE maktx FROM makt INTO (it_pbid_pbim-maktx) WHERE matnr = it_pbid-matnr.
    MODIFY table it_pbid_pbim TRANSPORTING maktx.
    SELECT aenam laeda FROM pbhi INTO (it_pbid_pbim-aenam,it_pbid_pbim-laeda) WHERE bdzei = it_pbid-bdzei AND aenam = 'Abbau-'.
       MODIFY TABLE it_pbid_pbim TRANSPORTING aenam laeda. " debug here
    select single sum( dbmng ) sum( plnmg ) FROM pbhi INTO (it_pbid_pbim-dbmng,it_pbid_pbim-plnmg) WHERE bdzei = it_pbid-bdzei AND aenam = 'Abbau-' and laeda = it_pbid_pbim-laeda..
       MODIFY TABLE it_pbid_pbim TRANSPORTING dbmng plnmg. " debug here
   endselect.
    it_pbid_pbim-pirrednqty = it_pbid_pbim-dbmng - it_pbid_pbim-plnmg.
       MODIFY table it_pbid_pbim TRANSPORTING pirrednqty.
    IF ( it_pbid_pbim-laeda IN s_laeda AND it_pbid_pbim-aenam EQ 'Abbau-' ).
      MOVE-CORRESPONDING it_pbid_pbim TO it_allrows.
      append it_allrows.
    ELSEIF NOT it_pbid_pbim-laeda IN s_laeda.
          delete it_pbid_pbim index sy-tabix.           " debug here
    ENDIF.
    ENDSELECT.
ENDLOOP.
**************************************PBIM*************************************
LOOP AT it_pbim.
    move-corresponding it_pbim to it_pbid_pbim.
       append it_pbid_pbim.
    SELECT SINGLE maktx FROM makt INTO (it_pbid_pbim-maktx) WHERE matnr = it_pbim-matnr.
       MODIFY table it_pbid_pbim TRANSPORTING maktx.
    SELECT aenam laeda FROM pbhi INTO (it_pbid_pbim-aenam,it_pbid_pbim-laeda) WHERE bdzei = it_pbim-bdzei AND aenam = 'Abbau-'.
       MODIFY TABLE it_pbid_pbim TRANSPORTING aenam laeda. " debug here
    select single sum( dbmng ) sum( plnmg ) FROM pbhi INTO (it_pbid_pbim-dbmng,it_pbid_pbim-plnmg) WHERE bdzei = it_pbim-bdzei AND aenam = 'Abbau-' and laeda = it_pbid_pbim-laeda..
       MODIFY TABLE it_pbid_pbim TRANSPORTING dbmng plnmg. " debug here
    it_pbid_pbim-pirrednqty = it_pbid_pbim-dbmng - it_pbid_pbim-plnmg.
       MODIFY table it_pbid_pbim TRANSPORTING pirrednqty.
    IF ( it_pbid_pbim-laeda IN s_laeda AND it_pbid_pbim-aenam EQ 'Abbau-' ).
      MOVE-CORRESPONDING it_pbid_pbim TO it_allrows.
      append it_allrows.
    ELSEIF NOT it_pbid_pbim-laeda IN s_laeda.
          delete it_pbid_pbim index sy-tabix.           " debug here
    ENDIF.
    ENDSELECT.
ENDLOOP.
sort it_allrows by matnr laeda status.
**********************************ALL ROWS************************
loop at it_allrows.
line-matnr = it_allrows-matnr.
line-laeda = it_allrows-laeda.
line-plnmg = it_allrows-plnmg.
line-dbmng = it_allrows-dbmng.
line-mblnr = it_allrows-mblnr.
line-pbfnr = it_allrows-pbfnr.
line-maktx = it_allrows-maktx.
line-aenam = it_allrows-aenam.
line-erfmg = it_allrows-erfmg.
line-budat = it_allrows-budat.
line-bdzei = it_allrows-bdzei.
line-werks = it_allrows-werks.
line-pirrednqty = it_allrows-pirrednqty.
line-diff = it_allrows-diff.
line-slno = it_allrows-slno.
line-status = it_allrows-status.
collect line into itfinal1.
endloop.
loop at itfinal1 into line.
collect line into itfinal.
    write: / line-matnr, line-plnmg, line-dbmng,line-laeda,line-status..
endloop.
skip 4.
loop at itfinal into line.
write: / line-matnr, line-plnmg, line-dbmng,line-laeda,line-status..
endloop.
break-point.

Problem in collect statement

Hi,
i have requirement to get all unique entries from table .if i am getting duplicate record then i need to add qunatity field which i have define like rlbes-anfme.
my internal table is :
11 name1 23.00
22 name2 1,324.00
11 name1 10.00
I want output in this way
11 name1 33.00
22 name2 1,324.00
i tried to use collect statement but the problem is its not working on character type field.
if i use packed field then i am not able to upload my file because i am getting quantity filed 1,2344.00 this way.( instead of 1325.00)
please give me any solution.
thanks,
jack

Hi,
Try this..
Create another internal table which has the same structure of your internal table.
DATA: LT_COLLECT LIKE ITAB OCCURS 0 WITH HEADER LINE.
DATA: V_QUANTITY TYPE MENGE_D.
Sort the internal table.
SORT ITAB BY field1 field2.    " Give the appropriate field names.
<b>* process the internal table which has the records.</b>
LOOP AT ITAB.
Sum up the quantity.
   V_MENGE = V_MENGE + ITAB-ANFME. " Quantity field.
Move the first two fields.
   LT_COLLECT-FIELD1 = ITAB-FIELD1.
   LT_COLLECT-FIELD2 = ITAB-FIELD2.
At the end of the record..append the record.
   AT END OF FIELD2.     " Give the corresponding field name.
      LT_COLLECT-ANFME = V_MENGE.
      APPEND LT_COLLECT.
     CLEAR: V_MENGE.
   ENDAT.
ENDLOOP.
Thanks,
Naren

Report in which collect statement .

report in which collect statement is used and also its purpose.

COLLECT
Basic form
COLLECT [wa INTO] itab.
Addition
... SORTED BY f
Effect
COLLECT is used to create unique or compressed datsets. The key fields are the default key fields of the internal table itab .
If you use only COLLECT to fill an internal table, COLLECT makes sure that the internal table does not contain two entries with the same default key fields.
If, besides its default key fields, the internal table contains number fields (see also ABAP/4 number types ), the contents of these number fields are added together if the internal table already contains an entry with the same key fields.
If the default key of an internal table processed with COLLECT is blank, all the values are added up in the first table line.
If you specify wa INTO , the entry to be processed is taken from the explicitly specified work area wa . If not, it comes from the header line of the internal table itab .
After COLLECT , the system field SY-TABIX contains the index of the - existing or new - table entry with default key fields which match those of the entry to be processed.
Notes
COLLECT can create unique or compressed datasets and should be used precisely for this purpose. If uniqueness or compression are unimportant, or two values with identical default key field values could not possibly occur in your particular task, you should use APPEND instead. However, for a unique or compressed dataset which is also efficient, COLLECT is the statement to use.
If you process a table with COLLECT , you should also use COLLECT to fill it. Only by doing this can you guarantee that
the internal table will actually be unique or compressed, as described above and
COLLECT will run very efficiently.
If you use COLLECT with an explicitly specified work area, it must be compatible with the line type of the internal table.
Example
Compressed sales figures for each company
DATA: BEGIN OF COMPANIES OCCURS 10,
NAME(20),
SALES TYPE I,
END OF COMPANIES.
COMPANIES-NAME = 'Duck'. COMPANIES-SALES = 10.
COLLECT COMPANIES.
COMPANIES-NAME = 'Tiger'. COMPANIES-SALES = 20.
COLLECT COMPANIES.
COMPANIES-NAME = 'Duck'. COMPANIES-SALES = 30.
COLLECT COMPANIES.
The table COMPANIES now has the following appearance:
NAME SALES
Duck 40
Tiger 20
Addition
... SORTED BY f
Effect
COLLECT ... SORTED BY f is obsolete and should no longer be used. Use APPEND ... SORTED BY f which has the same meaning.
Note
Performance
The cost of a COLLECT in terms of performance increases with the width of the default key needed in the search for table entries and the number of numeric fields with values which have to be added up, if an entry is found in the internal table to match the default key fields.
If no such entry is found, the cost is reduced to that required to append a new entry to the end of the table.
A COLLECT statement used on a table which is 100 bytes wide and has a key which is 60 bytes wide and seven numeric fields is about approx. 50 msn (standardized microseconds).
Note
Runtime errors
COLLECT_OVERFLOW : Overflow in integer field when calculating totals.
COLLECT_OVERFLOW_TYPE_P : Overflow in type P field when calculating totals.

Advice regarding how best to collect stats on 10G RAC Production system

Friends,
I have read quite a lot of blogs and docs and need some help with the best way forward. I am a DBA new to RAC who has limited experience with busy 24@7 10g systems on the scale of my current employer.
Historically stats are gathered here as follows :-
exec dbms_stats.unlock_schema_stats('BP');
exec dbms_stats.gather_schema_stats(ownname => 'BP', cascade => true, estimate_percent => dbms_stats.auto_sample_size);
exec dbms_stats.lock_schema_stats('BP');
Then Flush shared pool ok ????
Because of previous issues with this - alll tables are currently locked and this process is recommended for every 1-2 months rather than daily.
EM Grid Control is used when performance is poor and the sql tuning advisor is run to generate recommendations from which a sql profile could be selected and enabled for the selected code.
My plan is to bring back gathering of stats every 1 to 2 months, my goal is make sure I can fix things quickly if it all goes to custard !!!!
From research it looks like sql_profile is like a hint and independent of gathering stats - it tells optimiser what hints to use when executing sql.
This thread is for advice from professional dba's in my shoes - how do you approach this so that any issues are quickly rectified ???
My thinking is to query dba_profiles and get list of profiles and statuses ... for all tables with sql profiles ..
This is so profiles can be disabled and then quickly enabled if there is a problem aftewr the tables are analyzed.
To revert all the schema stats :-
exec dbms_stats.unlock_schema_stats('BP');
exec dbms_stats.restore_schema_stats(ownname=>'BP',as_of_timestamp=>sysdate-1);
exec dbms_stats.lock_schema_stats('BP');
To revert a table's stats (this looks more finicky so not sure the way to go ...):-
Pre gather stats :-
select stats_update_time from user_tab_stats_history where table_name = ‘<EnterTabName>’;
exec dbms_stats.create_stat_table ( -‘SCOTT’, -‘stattab_new’);
exec dbms_stats.export_table_stats ( -‘SCOTT’, -‘DEPT’, -null, -‘stattab_new’, -null, -true, -‘SCOTT’);
Then later after gather stats :-
exec dbms_stats.restore_table_stats ( -‘SCOTT’, -‘DEPT’, -’21-JAN-09 11.00.00.000000 AM -05:00′);
Enable/Disable Profile
exec dbms_sqltune.alter_sql_profile('<Profile name>', 'STATUS', 'DISABLED');
exec dbms_sqltune.alter_sql_profile('<Profile name>', 'STATUS', 'ENABLED');
I will do the plan below on a test system first however load may not really identify problems until for real on the Prod system.
My plan is to :-
1 analyze all tables as per outline at start above (existing practice)
2 Disable the sql profiles that are in use on the analyzed tables
3 See what code is affected and what tables
If Profile exists for these sql statements then either apply existing profile (as disabled) or use tuning adviser to create another profile
(Advice welcome here - what do you do on big systems ????)
4 If its a catastrophe - I can restore the schema stats using (exec dbms_stats.restore_schema_stats(ownname=>'BP',as_of_timestamp=>sysdate-1);)
and then possibly re-enabling the sql_profiles that were in place before ....
I welcome any advice based on similar experiences that can help me get this right.
Many thanks,
cheers, Rob
Edited by: Diesel on Jun 27, 2012 10:51 PM

Useful Link:
http://www.oradev.com/create_statistics.jsp
## Gather schema stats
begin
dbms_stats.gather_schema_stats(ownname=>'SYSLOG');
end;
## Gather a particular table stats of a schema
begin
DBMS_STATS.gather_table_stats(ownname=>'syslog',tabname=>'logs');
end;
Regards
Asif Kabir
--mark the answer as correct/helpful

Doubt on Select Statement

HI Friends,
i have a requirement to select matnr,werks and mmsta from marc table.where i have input of matnr and mmsta.
The matnr in the marc table having 2 werks with different mmsta.
i was asked to select matnr not having mmsta 40.
but in marc table there is same matnr with two mmsta 37 and 40.
i want a select statement which should not pick matnr having 40.
my select statement was
select matnr werks mmsta into itab from marc
where matnr in fpso_matnr and mmsta in fpso_mmsta.
this does not work for the above condition.
please suggest me a correct statement..
Thanks,
Gokul

select matnr werks mmsta into itab from marc
where matnr in fpso_matnr and mmsta in fpso_mmsta
and mmsta NE 40.
ill this not work ?
MARC is plant data.. so I guess u need to give werks also...
Edited by: jackandjay on Dec 19, 2007 12:02 PM

Collect statement not working

Hi,
My collect statement is not working. Kindly let me know what is the other way to add one filed in the loop.
thanks
Moderator message - Please ask a specific question - post locked
Edited by: Rob Burbank on Nov 19, 2009 9:24 AM

Same thing i faced few days ago --. i have resolved this using following logic ... try this it will workout
CLEAR: wa_mkpf_mseg, w_werks, w_matnr, w_lgort, w_bwart.
LOOP AT t_mkpf_mseg INTO wa_mkpf_mseg.
IF wa_mkpf_mseg-werks EQ w_werks AND wa_mkpf_mseg-matnr EQ w_matnr AND wa_mkpf_mseg-lgort EQ w_lgort AND wa_mkpf_mseg-bwart EQ w_bwart.
CLEAR: wa_p_coi.
READ TABLE t_p_coi INTO wa_p_coi WITH KEY werks = wa_mkpf_mseg-werks matnr = wa_mkpf_mseg-matnr lgort = wa_mkpf_mseg-lgort bwart = wa_mkpf_mseg-bwart.
IF sy-subrc = 0.
wa_p_coi-Avg Days = wa_p_coi-Avg Days + wa_mkpf_mseg-Avg Days.
MODIFY t_p_coi FROM wa_p_coi TRANSPORTING Avg Days .
CLEAR: wa_p_coi, wa_p_coi.
endif.
ELSE.
wa_p_coi-werks = wa_mkpf_mseg-werks.
wa_p_coi-matnr = wa_mkpf_mseg-matnr.
wa_p_coi-bwart = wa_mkpf_mseg-bwart.
wa_p_coi-lgort = wa_mkpf_mseg-lgort.
wa_p_coi-Avg Days = wa_mkpf_mseg-Avg Days .
APPEND wa_p_coi TO t_p_coi.
CLEAR: wa_p_coi.
ENDIF.
w_werks = wa_mkpf_mseg-werks.
w_matnr = wa_mkpf_mseg-matnr.
w_lgort = wa_mkpf_mseg-lgort.
w_bwart = wa_mkpf_mseg-bwart.
CLEAR: wa_mkpf_mseg.
ENDLOOP.

Collect statement in a class.

Hello,
This is related to BW infospoke enhancement,
in this class i have structure which is filled and i have to aggregate the data in this structure by one of the field level,
i want to declare a internal table with header and take the data from structure into internal table and then do a collect statement on to this internal table..
but i am getting a message that no one more header line is supported in OOPS concept..meaning i am not able to declare a internal table with header line..
any solution to this will be awarded with points.

Hello Shashi
You should not use itab with header lines since they mess up any coding and are a nightmare when it comes to maintaining code.
Fortunately, SAP has abandoned header lines from ABAP-OO. If you are not using table types then you have to define your own types, e.g.:
TYPES: BEGIN OF ty_s_line.
TYPES:   field_a TYPE ... .
TYPES:   field_b TYPE ... .
TYPES: END OF ty_s_line.
TYPES: ty_t_itab TYPE STANDARD TABLE OF ty_s_line
                  WITH DEFAULT KEY.
DATA:
ls_line   TYPE ty_s_line,
lt_itab   TYPE ty_t_itab.
* Now fill your itab, e.g.
SELECT * FROM ... INTO CORRESPONDING FIELDS
                    OF TABLE lt_itab.
* Now working with the itab data.
LOOP AT lt_itab INTO ls_line.
ENDLOOP.
Regards
   Uwe

Hi friends i have doubt on collect statement.

Similar Messages

Maybe you are looking for