Internal Table Moving

Dear Friends
i am developing small BSP application
when i enter material code and click on the preview button material descriptions came to page and end of the list another button came with description download
when i click on that the list must download to as excel file.
so my requirement is in my preview button data load to itab so in my event handler i want to use these loaded iteb in download event also
but when i click onthe download button that itab was initialized
please help me to solve this

Hi,
I don´t understand it all due to a bad description but check first whether your web page is statefull or stateless (and read the documentation about what this is). Additionally, where exactly did you define your internal table ?? if it was in an event (OnInitialization, for example) it is logical that records are knwon only in this event. Definition of table is in the attributes of page (pages with logic) or in the attributes of the class (MVC).

Similar Messages

Value not moved to work are of the internal table

HI
I have one internal table declared with occurs 2500.
i am selecting the values from a z table into this internal table.
now i want to move the values in the table to another internal table for download.here except one field all the other fields are moving to the new internal table.When i debugged i could see the value in the internal table but its not getting moved to work area of that internal table (or the header line).
I could not see the value when i use itab[]-field in debugger mode instead when i use itab[1]-field i could see that field value.
please do suggest.

There is no need to move your data from one internal table to another with fixed structure. All you need to do is take each row's components skipping the column you don't want to download and concatenate this to some string. Then append to string table and download it. Sample:
"let's say your column is on 3rd place in the table
data l_row_string type string.
data lt_string_tab type table of string.
Loop at itab assigning <wa>.
do.
    check sy-index ne 3. "skip this column
    assign component sy-index of structure <wa> to <comp>.
    if sy-subrc = 0.
      CONCATENATE l_row_string <comp> INTO l_row_string SEPARATED BY cl_abap_char_utilities=>horizontal_tab.
    else.
      "no more component in row
      append l_row_string to lt_string_tab.
      clear l_row_string.
      exit.
    endif.
enddo.
endloop.
Now all you need is to downlaod your lt_string_tab as your text file (extension TXT).
Regards
Marcin

Problem in moving the data into final internal table

Hello all,
I am stuck in apeculair situation.
I have a internal table having header record and a internal table having its line items.
Header record ::    90006103 A   20080110   ALBERTA    3456
Detail   record ::    90006103 D2 2219CR1710441
                           90006103 D2 2219M11710443
                           90006103 D2 2219M21710442
                           90006103 A    20080115   ALBERTA    3456
                           90006103 D2 2219CR1710441
                           90006103 D2 2219M11710443
                           90006103 D2 2219M21710442
I collected the header record in one internal table and another internal table having all the line items.But the problem is when i am moving the values to the final inernal table i am getting the same payment date
20080110 (Date field in first record of header internal table) for all the line items .
But my requirement is that date should be 20080110 for the first 3 line items of first header record and similarly date should be 20080115 for all the line items of the next header record.
Kindly suggest.
Regards,
Arun

assumption: some mistake in ur posting that, How belnr and date r same for both header records, so i guess, either one is different.
try with AT NEW - ENDAT.
AT NEW belnr.
here use looping, READing of ur itabs.---> so, u need to build couple of itabs to move forth and back.
ENDAT.
pls. note that, when u use this AT NEW all the CHAR fileds of itab wuld show as STARS **.....so, this is the necessity behind building new itabs.
thanq
Edited by: SAP ABAPer on Dec 30, 2008 6:24 PM

Moving the record to another internal table.

dear all,
i am having two internal tables . itab & itab1.
itab contains matnr   plant   quantity     date
                    100      500      1000       yyyy/mm/10
                    100      500      2000       yyyy/mm/20.
          i have to move the records to itab1 if dd less than 15 quantity should be moved to q1 if gt 15 then the quantity should be moved to same q2 in a same line.
i want itab1 to be
           matnr   plant     q1        q2
          100       500      1000       2000.
regards ,
balaji

hi Balaji,
Please use the following logic:
data:
     v_dd(2).
loop at itab.
      itab1-matnr = itab-matnr.
      itab1-plant = itab-plant.
      v_dd = itab-date+8(2).
      read table itab1 with key matnr = itab1-matnr
                                         plant   = itab1-plant.
      if v_dd < 15.
            itab1-q1 = itab1-q1 + itab-quantity.
      else.
            itab1-q2 = itab1-q2 + itab-quantity.
      endif.
      if sy-subrc = 0.
             modify itab1 index sy-tabix.
      else.
            append itab1.
      endif.
      clear itab1.
endloop.
Hope this helps,
Sajan Joseph.

Moving data from internal table to Dynamic internal table

Hello All,
I am facing a problem i moving the data from a internal table data to Dyn. internal table.
My code is as follows
*******Declartion**************************************
DATA: IT_FIELDCAT TYPE LVC_T_FCAT,
      IS_FIELDCAT LIKE LINE OF IT_FIELDCAT.
DATA: IT_OUTTAB TYPE STANDARD TABLE OF ZVTEST.
DATA: WA_OUTTAB TYPE ZVTEST.
DATA: LV_LINE LIKE SY-TABIX,
       COUNT TYPE I.
FIELD-SYMBOLS: <NEW_TABLE> TYPE REF TO DATA.
FIELD-SYMBOLS: <L_TABLE> TYPE ANY TABLE,
               <L_LINE> TYPE ANY.
FIELD-SYMBOLS: <L_FIELD> TYPE ANY.
FIELD-SYMBOLS: <FS_DATA> TYPE REF TO DATA,
               <FS_1> TYPE ANY TABLE,
               <FS_2>,
               <FS_3>.
DATA: NEW_LINE TYPE REF TO DATA.
DATA: LT_DATA TYPE REF TO DATA.
ASSIGN LT_DATA TO <FS_DATA>.
Create a new Table
CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
EXPORTING
        IT_FIELDCATALOG = IT_FIELDCAT
IMPORTING
        EP_TABLE = <FS_DATA>
EXCEPTIONS
      GENERATE_SUBPOOL_DIR_FULL = 1
      OTHERS                    = 2.
IF SY-SUBRC = 0.
    ASSIGN <FS_DATA>->* TO <FS_1>.
    CREATE DATA NEW_LINE LIKE LINE OF <FS_1>.
A field-symbol to access that work area
    ASSIGN NEW_LINE->* TO <FS_2>.
LOOP AT IT_OUTTAB INTO WA_OUTTAB.
    MOVE-CORRESPONDING WA_OUTTAB TO <FS_1>.
ENDLoop.
But when I am using MOVE-CORRESPONDING WA_OUTTAB TO <FS_1>.
I am getting the error like
"<FS_1>" is not a structure or internal table with header line.
Please check the code and tell where I am making the mistake.
Regards,
Vasanth

Hello Rich ,
My is code is as below..
Declaration:
DATA: IT_FIELDCAT TYPE LVC_T_FCAT,
      IS_FIELDCAT LIKE LINE OF IT_FIELDCAT.
DATA: BEGIN OF IT_OUTTAB OCCURS 0,
        PSPID     LIKE PROJ-PSPID, "Projektdefinition
        POSID     LIKE PRPS-POSID, "PSP-Element
        POST1     LIKE PRPS-POST1, "Kurzbeschreibung
        STTXT_INT LIKE CNJ_STAT-STTXT_INT, "Systemstatus
        STTXT_EXT LIKE CNJ_STAT-STTXT_EXT, "Anwenderstatus
      END OF IT_OUTTAB.
DATA: WA_OUTTAB LIKE IT_OUTTAB.
DATA: LV_LINES LIKE SY-TABIX,
       COUNT TYPE I.
FIELD-SYMBOLS: type any.
DATA: NEW_LINE TYPE REF TO DATA.
DATA: LT_DATA TYPE REF TO DATA.
G_R_DISP_VARIANT-REPORT = SY-REPID.
G_R_DISP_VARIANT-VARIANT = PA_VAR.
CALL FUNCTION 'REUSE_ALV_VARIANT_SELECT'
       EXPORTING
            I_DIALOG            = 'N'
            I_USER_SPECIFIC     = 'A'
            I_DEFAULT           = 'X'
            IT_DEFAULT_FIELDCAT = G_T_FIELDCAT
            I_LAYOUT            = G_R_LAYOUT
       IMPORTING
            ET_FIELDCAT         = G_T_FIELDCAT
           et_sort             = l_tab_sort
           et_filter           = l_tab_filter
           ES_LAYOUT           = G_R_LAYOUT
       CHANGING
            CS_VARIANT          = G_R_DISP_VARIANT
       EXCEPTIONS
            ERROR_MESSAGE       = 4
            OTHERS              = 4.
LOOP AT G_T_FIELDCAT INTO G_R_FIELDCAT WHERE NO_OUT IS INITIAL
                                           AND TECH IS INITIAL.
    MOVE-CORRESPONDING G_R_FIELDCAT TO IS_FIELDCAT.
    IS_FIELDCAT-FIELDNAME = G_R_FIELDCAT-FIELDNAME.
    IS_FIELDCAT-INTTYPE   = G_R_FIELDCAT-INTTYPE.
    IS_FIELDCAT-OUTPUTLEN = G_R_FIELDCAT-OUTPUTLEN.
    IS_FIELDCAT-REF_FIELD = G_R_FIELDCAT-FIELDNAME.
    IS_FIELDCAT-REF_TABLE = G_R_FIELDCAT-REF_TABNAME.
    APPEND IS_FIELDCAT TO IT_FIELDCAT.
ENDLOOP.
DATA: WA_LISTE LIKE P_T_LISTE.
CLEAR:IT_OUTTAB.
REFRESH: IT_OUTTAB.
LOOP AT P_T_LISTE INTO WA_LISTE.
    WA_OUTTAB-PSPID = WA_LISTE-PSPID .
    WA_OUTTAB-POSID = WA_LISTE-POSID.
    WA_OUTTAB-POST1 = WA_LISTE-POST1.
    WA_OUTTAB-STTXT_INT = WA_LISTE-STTXT_INT.
    WA_OUTTAB-STTXT_EXT = WA_LISTE-STTXT_EXT.
    APPEND WA_OUTTAB TO IT_OUTTAB.
ENDLOOP.
**dynamic table creation for data
ASSIGN LT_DATA TO .
Create a new Table
CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
EXPORTING
        IT_FIELDCATALOG = IT_FIELDCAT
IMPORTING
        EP_TABLE = .
A field-symbol to access that work area
    ASSIGN NEW_LINE->* TO = WA_OUTTAB-PSPID.
     ASSIGN COMPONENT 'POSID' OF STRUCTURE WA_OUTTAB TO <FS_3>.
      ASSIGN COMPONENT 'POSID' OF STRUCTURE = WA_OUTTAB-POSID.
     ASSIGN COMPONENT 'POST1' OF STRUCTURE WA_OUTTAB TO <FS_3>.
      ASSIGN COMPONENT 'POST1' OF STRUCTURE .
     <FS_5> = <FS_3>.
       = WA_OUTTAB-POST1.
     ASSIGN COMPONENT 'STTXT_INT' OF STRUCTURE WA_OUTTAB TO <FS_3>.
      ASSIGN COMPONENT 'STTXT_INT' OF STRUCTURE TO P_FILE.
    ENDLOOP.
ELSE.
    MESSAGE E041(S9) WITH P_FILE.
ENDIF.
CLOSE DATASET P_FILE.
Here my problem is ´´, I am not able to use move corresponding statement.
So I am not getting the exact values to the fields of the dynamic table...
Please check it and give me a solution,
Regards,
Vasanth

Moving the data from multiple internal tables into a single one

Hello everyone,
I am creating a classical report which uses the following tables.
tables : ekko, ekpo, mara, makt,lfa1.
my input parameter is
Select-options Purchase Order number
Following fields are getting used.
Doc no                  EKKO-EBELN
Material              EKPO-MATNR
Item number          EKPO-EBELP
Quantity             EKPO-MENGE
Material Group          MARA-MATKL
Vendor                  EKKO-LIFNR
Old Material code   MARA-BISMT
Material Desc.           MAKT-MAKTX
Vendor name         LFA1-NAME1
Now i need to do the following task.
1 Select record from EKKO Using document number.
2 Select record from EKPO using EKKO record using Document no as key.
3 Find out Old Material code of each and every material from Material master.
4 Find out Material description for each and every material from MAKT.
5 Sort record on Vendor, Purchase Order number and Material.
I have defined seperate internal tables for these operation.
Once i have fetched records into these individual internal tables from the corresponding DB tables i need to move these values into a new internal tables which has all the above fields mentioned
I need to move these values into a new internal table because to display the values on the report.
Any idea for the above ? Plz help with a sample example or some relevant.
Regards,
Ranjith Nambiar

Hi
1 Select record from EKKO Using document number.
2 Select record from EKPO using EKKO record using Document no as key.
Use inner join and retrive data into one internal table.for Ex ITAB1
3 Find out Old Material code of each and every material from Material master.
Use ITAB1 with for allentries in MARA table to get the onl materil number populate in to one table.
4 Find out Material description for each and every material from MAKT.
Get the Material desc with the same manner as above,
5 Sort record on Vendor, Purchase Order number and Material.
now sort the ITAB1 as you req.
now Loop on the ITAB1.
and read above 2 tables for old matnr and matner deac and append into another table as you want.
Hope this will help.
Regards,
Hiren Patel

Moving data from one internal table to another

Hi,
I have one internal table populated with a list of material codes and another with all the material numbers.
ITAB1: MCODE KSCHL KNUMH MATNR
ITAB2: MCODE MATNR
The matnr field in itab1 is blank initially. It needs to be populated with all the material numbers from itab2. How can I achieve this?
Thanks,
ap

Hi
Lets say that there is only one record in itab1 and for that there is correspondingly 10 records in itab2.
that means that the one record in itab1 should be changed to the first material number in itab2 and there should be nine more records created in itab1 according to the values in itab2.
Hope this is what you mean.
If this is the logic then the following code should work
then lets have a third internal table the same type as itab1
Loop at itab1 into wa_itab1
*readt table itab2 into wa_itab2 with key mcode = wa_itab1-mcode.
*IF sy-subrc eq 0.
loop at itab2 into wa_itab2 where mcode = wa_itab1-mcode.
wa_itab1-matnr = wa_itab2-matnr
append wa_itab1 to itab3.
endloop.
*ENDIF.
*modify itab1 from wa_itab1.
endloop.
itab3 will contain all the values that you require

Problem in moving data of an internal table to other internal tables

My internal table ITAB contains two columns NODE and VALUE.
The contents are as follows
NODE                VALUE
A                              1
B          2
C          3
D          4
E          5
F          6
D          7
E          8
F          9
G          10
H          11
I          12
G          13
H          14
I          15
G          16
H          17
I          18
J          19
K          20
L          21
J          22
K          23
L          24
My requirement is I need to move the values to JTAB such that JTAB should have columns as D E F and should be having the following values filled in the columns.
JTAB
D     E     F
4     5     6
7     8     9
Similarly I need to move the values to KTAB such that KTAB should have columns as G H I and should be having the following values filled in the columns.
KTAB
G     H     I
10     11     12
13     14     15
16     17     18
Similarly I need to move the values to NTAB such that NTAB should have columns as G H I and should be having the following values filled in the columns.
NTAB
J     K     L
19     20     21
22     23     24
Please help. Any help is higly appreciated. if dont want to put several if conditions as it will effect performance. is there a simple way to do this

Hello,
How itab is sorted ?
- For example table jtab has 3 fields D E F. D is the first one and F the last one.
-- Are itab entries sorted like that :
D 5                  <--- 1st field of structure jtab
E 4
F 7                  <--- last field of structure jtab
or like that
E 4
D 5
F 77
or something else
re-using the code of a®s. You can do something like that :
    loop at itab.
        CASE itab-node.
         WHEN 'D' OR 'E' OR 'F'. "jtab fields
                CASE itab-node.
                   WHEN 'D'. "1st field
                          CLEAR              wa_jtab.
                          MOVE itab-value TO wa_jtab-d.
                   WHEN 'F'. "last field
                          MOVE itab-value TO wa_jtab-f.
                          APPEND wa_jtab TO jtab.
                   WHEN OTHERS.
                          ASSIGN COMPONENT itab-node OF STRUCTURE wa_jtab TO <fs>.
                          IF sy-subrc IS INITIAL.
                               MOVE itab-value TO <fs>.
                          ENDIF.
                 ENDCASE.
         WHEN 'G' OR 'H' OR 'I'. "ktab fields
                CASE itab-node.
                   WHEN 'G'. "1st field
                          CLEAR              wa_ktab.
                          MOVE itab-value TO wa_ktab-g.
                   WHEN 'I'. "last field
                          MOVE itab-value TO wa_ktab-i.
                          APPEND wa_ktab TO ktab.
                   WHEN OTHERS.
                          ASSIGN COMPONENT itab-node OF STRUCTURE wa_ktab TO <fs>.
                          IF sy-subrc IS INITIAL.
                               MOVE itab-value TO <fs>.
                          ENDIF.
                 ENDCASE.
           ENDCASE.
ENDLOOP.
Pre requisite: itab must be sorted by field position in structure of each target tables (jtab ktab ...)
Remark : if target tables have lot of fields you can use range instead of WHEN 'D' OR 'E' OR 'F'.
Cordialement,
Chaouki.
Edited by: Chaouki AKIR on Feb 19, 2009 9:59 PM

Moving columns in an internal table

Hi Gurus,
I have this ALV program which displays the cost element and its corresponding groups (up to 10th level only).
My problem is on how to display the report where the first column is the cost element and the succeeding columns the cost element groups starting from the top level.
Below is example of a hierarchy of a given cost element ( 50030000 ).
    EMPSTOTAL                            <---Top level
         ESSPENDING
              ES5003
                   ES5003P
                       50030000              <---Cost Element
Now, since the selection of data is from the cost element up to to the top level group.
The internal table would look like this:
Cost Element       Group 1      Group 2        Group 3           Group 4          Group 5             Group 6   .......
50030000           ES5003P      ES5003       ESSPENDING    EMPSTOTAL     (blank)           (blank)......
But this output is wrong, what I really want is like this:
Cost Element       Group 1            Group 2              Group 3           Group 4          Group 5             Group 6   .......
50030000           EMPSTOTAL      ESSPENDING      ES5003            ES5003P        (blank)               (blank)......
As you can see, what is placed next to the cost element is the Top level Group and the last is the group directly linked to the cost element.
Can you please teach me on how to do just that?
Thank you so much for your help.
Regards,
Onyx

Hi,
As my analysis you are passing the values to the wrong fields of the internal table. Please check the structure of your internal table . Is this in the order which you want?
Other wise please look into how this internal table is getting filled?
This is the sturucture mismatch probelm.
Also look in to the fieldcatalog.
With Regards,
Sumodh.P

Error occured in moving internal tables

Hi i have a doubt in internal tables
Actually i have created a internal table(rtab_alv ) for the output in the format of alv grid and after that i had created another internal table as iznew1 in which i had transfered all the values of a database view(znew1) into that internal table iznew1 after that while i was trying to move the values of iznew1 to rtab_alv its not accepting it was showing an error as
<b>rtab_alv and iznew1 are not mutually convertible in a unicode program</b>
so can u explain me what is the possible error in this and how to resolve it
solution will be rewarded points

Hi Mr. Sadiqui
By following your procedure an error has occured as
below field are coming from database view and i m passing view data into iznew1
fields of iznew1
             LIFNR LIKE EKKO-LIFNR,
             EBELN LIKE EKKO-EBELN,
             VGABE LIKE EKBE-VGABE,
             EBELP LIKE EKBE-EBELP,
             BELNR LIKE EKBE-BELNR,
             MATNR LIKE EKPO-MATNR,
             TXZ01 LIKE EKPO-TXZ01,
        PS_PSP_PNR LIKE EKKN-PS_PSP_PNR,
             KOSTL LIKE EKKN-KOSTL,
             NAME1 LIKE LFA1-NAME1,
             NAME2 LIKE LFA1-NAME2,
             WERKS LIKE EKPO-WERKS,
             NETWR LIKE EKPO-NETWR,
             KNUMV LIKE EKKO-KNUMV,
             GJAHR LIKE EKBE-GJAHR,
and now i want to pass
one field ED1 which i hase calculated separatly and i want to pass this value into iznew1
but error is coming that iznew1 is a table with out header line has no component like ED1.
so how can i pass calculated value to internal table iznew1,

Moving internal table to another internal table using ASSIGN statement.

Hi,
We have a requirement to move an internal table form one program(SAPMV60A) to the internal table of the include(RV61B9xx) using the following statement.
[ xvbrp is a internal table in SAPMV60A. ]
ASSIGN ('(SAPMV60A)xvbrp') TO <ls_xvbrp>.
We tried all the combinations for declaring <ls_xvbrp> as table.
It is going to dump in our system,
" Type conflict with ASSIGN in program "SAPLV61B ".".
Your efforts will be rewarded with points.
Thanks in Advance,
Warm Regards,
Baburaj

Hi
If you declare your field-symbols as table you should use []
FIELD-SYMBOLS: <ls_xvbrp> TYPE TABLE.
ASSIGN ('(SAPMV60A)xvbrp[]') TO <ls_xvbrp>.
else
FIELD-SYMBOLS: <ls_xvbrp> TYPE ANY.
ASSIGN ('(SAPMV60A)xvbrp') TO <ls_xvbrp>.
But I believe in this case you'll assign the header line of xvbrp.
Max

Moving columns of an internal table to rows of an another internal table.

Hi
i have an internal table with 20 fields for single record .Now i need to move the 20 fields
(of similar length) of single record into internal table with those 20 fields as 20 records i.e i need to make rows of first internal table into columns of second internal table.
hope iam clear.

HI Deepthi,
Try with this Logic...
IF NOT ITAB[] IS INITIAL.
      LOOP AT ITAB FROM 7.
        ITAB2-FIELD1 = ITAB-FIELD1.
        ITAB2-FIELD2 = ITAB-FIELD2.
        APPEND : ITAB2.
        CLEAR : ITAB2.
      ENDLOOP.
      DO 27 TIMES.
        CASE CNT.
          WHEN '1'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD6.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD6.
          WHEN '2'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD7.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD7.
          WHEN '3'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD8.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD8.
          WHEN '4'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD9.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD9.
          WHEN '5'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD10.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD10.
          WHEN '6'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD11.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD11.
          WHEN '7'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD12.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD12.
          WHEN '8'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD13.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD13.
          WHEN '9'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD14.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD14.
          WHEN '10'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD15.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD15.
          WHEN '11'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD16.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD16.
          WHEN '12'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD17.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD17.
          WHEN '13'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD18.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD18.
          WHEN '14'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD19.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD19.
          WHEN '15'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD20.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD20.
          WHEN '16'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD21.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD21.
          WHEN '17'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD22.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD22.
          WHEN '18'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD23.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD23.
          WHEN '19'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD24.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD24.
          WHEN '20'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD25.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD25.
          WHEN '21'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD26.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD26.
          WHEN '22'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD27.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD27.
          WHEN '23'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD28.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD28.
          WHEN '24'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD29.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD29.
          WHEN '25'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD30.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD30.
          WHEN '26'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD31.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD31.
          WHEN '27'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD32.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD32.
          WHEN '28'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD33.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD33.
          WHEN '29'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD34.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD34.
          WHEN '30'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD35.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD35.
          WHEN '31'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD36.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD36.
          WHEN '32'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD37.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD37.
          WHEN '33'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD38.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD38.
          WHEN '34'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD39.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD39.
          WHEN '35'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD40.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD40.
          WHEN '36'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD41.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD41.
          WHEN '37'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD42.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD42.
          WHEN '38'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD43.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD43.
          WHEN '39'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD44.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD44.
          WHEN '40'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD45.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD45.
          WHEN '41'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD46.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD46.
          WHEN '42'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD47.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD47.
          WHEN '43'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD48.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD48.
          WHEN '44'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD49.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD49.
          WHEN '45'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD50.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD50.
          WHEN '46'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD51.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD51.
          WHEN '47'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD52.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD52.
          WHEN '48'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD53.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD53.
          WHEN '49'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD54.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD54.
          WHEN '50'.
            READ TABLE ITAB INDEX 4.
            ITAB3-FIELD1 = ITAB-FIELD55.
            READ TABLE ITAB INDEX 5.
            ITAB3-FIELD2 = ITAB-FIELD55.
        ENDCASE.
        APPEND ITAB3.
        CLEAR ITAB3.
        CNT = CNT + 1.
      ENDDO.
    ENDIF.
ENDIF.
Regards,
Santosh

Moving data in internal tables

hi
I have defined an internal table(say itab_master) and one of its field is table name which will store name of some other internal table(say itab2, itab3..etc).
now i want to move data into the tables(itab2, itab3..etc) selected as per row of itab1_master.
kindly suggest me way of doing it.
thnks

hi there,
FIrst you declare :
FIELD-SYMBOLS <fs> TYPE ANY TABLE.
ASSIGN itab_temp <fs>.
Note : If itab2 ,itab3..... are having the same structure there is now problem
Else you have to use FIELD-GROUPS.
Doc...
Defining an Extract
To define an extract, you must first declare the individual records and then define their structure.
Declaring Extract Records as Field Groups
An extract dataset consists of a sequence of records. These records may have different structures. All records with the same structure form a record type. You must define each record type of an extract dataset as a field group, using the FIELD-GROUPS statement.
FIELD-GROUPS <fg>.
This statement defines a field group <fg>. A field group combines several fields under one name. For clarity, you should declare your field groups at the end of the declaration part of your program.
A field group does not reserve storage space for the fields, but contains pointers to existing fields. When filling the extract dataset with records, these pointers determine the contents of the stored records.
You can also define a special field group called HEADER:
FIELD-GROUPS HEADER.
This group is automatically placed before any other field groups when you fill the extract. This means that a record of a field group <fg> always contains the fields of the field group HEADER. When sorting the extract dataset, the system uses these fields as the default sort key.
Defining the Structure of a Field Group
To define the structure of a record, use the following statement to add the required fields to a field group:
INSERT <f1>... <f n> INTO <fg>.
This statement defines the fields of field group <fg>. Before you can assign fields to a field group, you must define the field group <fg> using the FIELD-GROUPS statement. The fields in the field group must be global data objects in the ABAP program. You cannot assign a local data object defined in a procedure to a field group.
The INSERT statement, just as the FIELD-GROUPS statement, neither reserves storage space nor transfers values. You use the INSERT statement to create pointers to the fields <f i > in the field group <fg>, thus defining the structures of the extract records.
When you run the program, you can assign fields to a field group up to the point when you use this field group for the first time to fill an extract record. From this point on, the structure of the record is fixed and may no longer be changed. In short, as long as you have not used a field group yet, you can still extend it dynamically.
The special field group HEADER is part of every extract record. Consequently, you may not change HEADER once you have filled the first extract record.
A field may occur in several field groups; however, this means unnecessary data redundancy within the extract dataset. You do not need to define the structure of a field group explicitly with INSERT. If the field group HEADER is defined, an undefined field group consists implicitly of the fields in HEADER, otherwise, it is empty.
NODES: SPFLI, SFLIGHT.
FIELD-GROUPS: HEADER, FLIGHT_INFO, FLIGHT_DATE.
INSERT: SPFLI-CARRID SPFLI-CONNID SFLIGHT-FLDATE
INTO HEADER,
SPFLI-CITYFROM SPFLI-CITYTO
INTO FLIGHT_INFO.
The program is linked to the logical database F1S. The NODES statement declares the corresponding interface work areas.
There are three field groups. The INSERT statement assigns fields to two of the field groups.
Filling an Extract with Data
Once you have declared the possible record types as field groups and defined their structure, you can fill the extract dataset using the following statements:
EXTRACT <fg>.
When the first EXTRACT statement occurs in a program, the system creates the extract dataset and adds the first extract record to it. In each subsequent EXTRACT statement, the new extract record is added to the dataset.
Each extract record contains exactly those fields that are contained in the field group <fg>, plus the fields of the field group HEADER (if one exists). The fields from HEADER occur as a sort key at the beginning of the record. If you do not explicitly specify a field group <fg>, the
EXTRACT
statement is a shortened form of the statement
EXTRACT HEADER.
When you extract the data, the record is filled with the current values of the corresponding fields.
As soon as the system has processed the first EXTRACT statement for a field group <fg>, the structure of the corresponding extract record in the extract dataset is fixed. You can no longer insert new fields into the field groups <fg> and HEADER. If you try to modify one of the field groups afterwards and use it in another EXTRACT statement, a runtime error occurs.
By processing EXTRACT statements several times using different field groups, you fill the extract dataset with records of different length and structure. Since you can modify field groups dynamically up to their first usage in an EXTRACT statement, extract datasets provide the advantage that you need not determine the structure at the beginning of the program.
Assume the following program is linked to the logical database F1S.
REPORT demo_extract_extract.
NODES: spfli, sflight.
FIELD-GROUPS: header, flight_info, flight_date.
INSERT: spfli-carrid spfli-connid sflight-fldate
INTO header,
spfli-cityfrom spfli-cityto
INTO flight_info.
START-OF-SELECTION.
GET spfli.
EXTRACT flight_info.
GET sflight.
EXTRACT flight_date.
There are three field groups. The INSERT statement assigns fields to two of the field groups. During the GET events, the system fills the extract dataset with two different record types. The records of the field group FLIGHT_INFO consist of five fields: SPFLI-CARRID, SPFLI-CONNID, SFLIGHT-FLDATE, SPFLI-CITYFROM, and SPFLI-CITYTO. The first three fields belong to the prefixed field group HEADER. The records of the field group FLIGHT_DATE consist only of the three fields of field group HEADER. The following figure shows the structure of the extract dataset:
Reading an Extract
Like internal tables, you can read the data in an extract dataset using a loop.
LOOP.
[AT FIRST | AT <fgi> WITH <fg j> | AT LAST.
ENDAT.]
ENDLOOP.
When the LOOP statement occurs, the system stops creating the extract dataset, and starts a loop through the entries in the dataset. One record from the extract dataset is read in each loop pass. The values of the extracted fields are placed in the corresponding output fields within the loop. You can use several loops one after the other, but they cannot be nested. It is also no longer possible to use further EXTRACT statements within or after the loop. In both cases, a runtime error occurs.
In contrast to internal tables, extract datasets do not require a special work area or field symbol as an interface. Instead, you can process each record of the dataset within the loop using its original field names.
Loop control
If you want to execute some statements for certain records of the dataset only, use the control statements AT and ENDAT.
The system processes the statement blocks between the control statements for the different options of AT as follows:
AT FIRST
The system executes the statement block once for the first record of the dataset.
AT <fgi> WITH <fgj>
The system processes the statement block, if the record type of the currently read extract record was defined using the field group <fg i >. When using the WITH <fg j > option, in the extract dataset, the currently read record of field group <fg i > must be immediately followed by a record of field group <fg j >.
AT LAST
The system executes the statement block once for the last record of the dataset.
You can also use the AT and ENDAT statements for control level processing.
Assume the following program is linked to the logical database F1S.
REPORT DEMO.
NODES: SPFLI, SFLIGHT.
FIELD-GROUPS: HEADER, FLIGHT_INFO, FLIGHT_DATE.
INSERT: SPFLI-CARRID SPFLI-CONNID SFLIGHT-FLDATE
INTO HEADER,
SPFLI-CITYFROM SPFLI-CITYTO
INTO FLIGHT_INFO.
START-OF-SELECTION.
GET SPFLI.
EXTRACT FLIGHT_INFO.
GET SFLIGHT.
EXTRACT FLIGHT_DATE.
END-OF-SELECTION.
LOOP.
AT FIRST.
WRITE / 'Start of LOOP'.
ULINE.
ENDAT.
AT FLIGHT_INFO WITH FLIGHT_DATE.
WRITE: / 'Info:',
SPFLI-CARRID, SPFLI-CONNID, SFLIGHT-FLDATE,
SPFLI-CITYFROM, SPFLI-CITYTO.
ENDAT.
AT FLIGHT_DATE.
WRITE: / 'Date:',
SPFLI-CARRID, SPFLI-CONNID, SFLIGHT-FLDATE.
ENDAT.
AT LAST.
ULINE.
WRITE / 'End of LOOP'.
ENDAT.
ENDLOOP.
The extract dataset is created and filled in the same way as shown in the example for Filling an Extract with Data. The data retrieval ends before the END-OF-SELECTION event, in which the dataset is read once using a loop.
The control statements AT FIRST and AT LAST instruct the system to write one line and one underscore line in the list, once at the beginning of the loop and once at the end.
The control statement AT <fg i > tells the system to output the fields corresponding to each of the two record types. The WITH FLIGHT_DATE option means that the system only displays the records of field group FLIGHT_INFO if at least one record of field group FLIGHT_DATE follows; that is, if the logical database passed at least one date for a flight.
The beginning of the output list looks like this:
The contents of the field SFLIGHT-FLDATE in the HEADER part of record type FLIGHT_INFO are displayed as pound signs (#). This is because the logical database fills all of the fields at that hierarchy level with the value HEX 00 when it finishes processing that level. This feature is important for sorting and for processing control levels in extract datasets.
rewards would be appreciated.

Moving the data of five internal tables to one internal tables.

iam having the five internal table. like below
g_t_vbfa
g_t_vbrk
g_t_vbpa
g_t_kna1
g_t_vbak
this are the five internal tables. each tables having the datas . but each table having the number of records is different. one table having 100 records means another table having 50 records.
previously i used index sys-tabix concept it was not working properly...
my output table is g_t_output_header_data ..
i want to move that output table....
please coding wise give some solution...
thanks
santhosh

hi,
chk a sample.
data : begin of itab1 occurs 0. "itab with work area.
key_field1 like ztable1-key_field1,
field1 like ztable1-field1,
field2 like ztable1-field2,
endof itab1.
data : begin of itab2 occurs 0. "itab with work area.
key_field2 like ztable2-key_field2,
field3 like ztable2-field3,
field4 like ztable2-field4,
endof itab2.
data : begin of itab_final occurs 0.
key_field1 like ztable1-key_field1,
field1 like ztable1-field1,
field2 like ztable1-field2,
field3 like ztable2-field3,
field4 like ztable2-field4,
endof itab_final.
put the date final(merged) internal table
1. loop at itab1.
read table itab2 with key keyfield2 = itab1-keyfield1.
if sy-surc = 0.
itab_final-key_field1 = itab1-keyfield1
itab_final-field1 = itab1-field1.
itab_final-field2 = itab1-keyfield2.
itab_final-field3 = itab2-field2.
itab_final-field4 = itab2-keyfield2.
append itab_final.
clear itab_final.
endif.
endloop.
or
LOOP AT ITAB1.
MOVE-CORRESPONDING TO ITAB1 to ITAB_FINAL.
READ TABLE ITAB2 WITH KEY FILED1 = ITAB1-FIELD1.
if sy-subrc = 0.
MOVE-CORRESPONDING TO ITAB2 to ITAB_FINAL.
endif,
READ TABLE ITAB3 WITH KEY FILED1 = ITAB1-FIELD1.
if sy-subrc = 0.
MOVE-CORRESPONDING TO ITAB2 to ITAB_FINAL.
endif,
append itab_final.
clear itab_final.
endloop
rgds
Anver

Moving DATA from Internal Table to Ranges

Hi All,
I have an Internal table and a range variable both contain one field. Internal table is having only one table. I am populating the table data from a select query. Now I want to transfer the data to a range field. The internal table is having thousands of records so I want to do this <b>without LOOP</b>. Can anybody suggest the efficient way to achieve this?
Any help would be appreciated.
Thanks so much.
Jignesh.

... the sump with too big range tables is a pure oracle sickness. AFAIK the size limit for the select statement has been extended from 16k to 32k, so this danger is smaller than it used to be.
Anyway you can use the FOR ALL ENTRIES IN clause and the ABAP-SQL-interface will handle the package size very efficienly. There was a time I believed that FOR ALL ENTRIES IN should not be used because it would slow down the data selection. I have learned that this is not true at all because of the package technique.
And now for everyone who wants to built ranges of any size (no limit for internal tables):
Call this like (just as an example for initializing select-options:
PERFORM append_range USING:
'IEQ' sy-datum(4) '' CHANGING s_gjahr[],
'IBT' 1 'ZZZZZZZZZZ' CHANGING s_prctr[],
'IBT' 1 16           CHANGING s_monat[].
Note that SIGN and OPTION are combined into one parameter saving time and gaining overview (?).
I created the FORM once and used it so many times...
Actually you don't need so many "CHECK sy-subrc = 0" if you know how to use the form.
*&      Form append_range
      append selection range
FORM append_range USING    p_signopt     TYPE c
                            p_low         TYPE any
                            p_high        TYPE any
                   CHANGING pt_range      TYPE table.
FIELD-SYMBOLS:
    <range>                               TYPE ANY,
    <sign>                                TYPE ANY,
    <option>                              TYPE ANY,
    <low>                                 TYPE ANY,
    <high>                                TYPE ANY.
DATA:
    l_ref                                 TYPE REF TO data.
CREATE DATA l_ref                       LIKE LINE OF pt_range.
ASSIGN l_ref->* TO <range>.
CHECK sy-subrc                          = 0.
ASSIGN COMPONENT 'SIGN' OF STRUCTURE <range> TO <sign>.
CHECK sy-subrc                          = 0.
ASSIGN COMPONENT 'OPTION' OF STRUCTURE <range> TO <option>.
CHECK sy-subrc                          = 0.
ASSIGN COMPONENT 'LOW' OF STRUCTURE <range> TO <low>.
CHECK sy-subrc                          = 0.
ASSIGN COMPONENT 'HIGH' OF STRUCTURE <range> TO <high>.
CHECK sy-subrc                          = 0.
<sign>                                  = p_signopt(1).
<option>                                = p_signopt+1(2).
<low>                                   = p_low.
<high>                                  = p_high.
APPEND <range> TO pt_range.
ENDFORM.                    " append_range
Enjoy your ranges,
Clemens

Internal Table Moving

Similar Messages

Maybe you are looking for