Regarding the transfering the internal table to memory

hi,
this is my requirement
in the alv_grid_display_output,iam selecting the records by using the checkbox that is present for the each record.
after selecting the records,when i press 'update' button it has to call a module pool screen and what ever may be the selected records to be trasnfered to the screen.
please provide the code for this requirement.
thanks in advance

HI,
Please check the below code....
Function module to display the ALV report
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
I_CALLBACK_PROGRAM = W_REPID
I_CALLBACK_PF_STATUS_SET = 'PF_STATUS'
I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
FORM USER_COMMAND USING P_UCOMM TYPE SY-UCOMM
P_SELFLD TYPE SLIS_SELFIELD.
DATA : L_REP_MODE. "report mode
CASE P_UCOMM.
Data ref1 type ref to cl_gui_alv_grid.
CALL FUNCTION 'GET_GLOBALS_FROM_SLVC_FULLSCR'
IMPORTING
E_GRID = ref1.
call method ref1->check_changed_data
WHEN 'SAVE'.
loop at itab where check eq 'X'.
Call Module pool....
endloop.
ENDCASE.
Cheers,
Bujji

Similar Messages

Gui_download for transferring the data from internal table to excel sheet.

hi all,
i am using gui_download for transferring the data from internal table to excel sheet.
I have a internal table with 3 columns col1,col2,col3 and I am getting the file at the specified path,but my problem is that,in the excel sheet(path specified) all the 3 columns values are printed in one column.Please help me.
Thanks in advance.

Hi Venkata,
plz use FM 'SAP_CONVERT_TO_XLS_FORMAT' :
call function 'SAP_CONVERT_TO_XLS_FORMAT'
 exporting
* I_FIELD_SEPERATOR =
* I_LINE_HEADER =
 i_filename = p_file
* I_APPL_KEEP = ' '
 tables
 i_tab_sap_data = t_mbew
* CHANGING
* I_TAB_CONVERTED_DATA =
* EXCEPTIONS
* CONVERSION_FAILED = 1
* OTHERS = 2
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
Hope this helps,
Erwan

It cannot reference the dynamic internal table in memory as an object.

Hi,
I am getting the syntax error in the second select. I guest it cannot reference the dynamic internal table in memory as an object.
The internal table contains different fields from multiple tables and it gets created OK. Then the first select within the loop executes OK allowing me to read the multiple tables in ITABLES.
* Create dynamic internal table and assign to FS
call method cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = ifc
 IMPORTING
 ep_table = dy_table.
***OK, the dynamic tables is created here
assign dy_table->* to <dyn_table>.
* Create dynamic work area and assign to FS
create data dy_line like line of <dyn_table>.
assign dy_line->* to <dyn_wa>.
loop at ITABLES.
***OK, no syntax errors in this select here
select * appending corresponding fields of table <dyn_table>
 from (ITABLES-TABNAME).
endloop.
data: ikonp like konp occurs 0 with header line.
***NOT OK, there is syntax errors
select * into table ikonp
from KONP for all entries in <dyn_table>
where knumh = <dyn_table>-knumh.
Some of the tables in ITABLES are pooled tables which does not allow me to use INNER JOINS. Therefore I need a second select in order to read the pricing table KONP.
Thanks in advance for any hint.

Hi Abel,
You must be getting the syntax error that <dyn_table> does not contain the field knumh.
try putiing the entire where clause in a char type variable say wa_char and then use in ur query as
where (wa_char) .. it may work..
concatenate 'knumh' '=' '<dyn_table>-knumh' INTO wa_char SEPARATED BY SPACES.
SELECT ... from konp...
where (wa_char).
Revert if it doesnt work.

Fetch the values from internal table inside an internal table (urgent!!)

data : BEGIN OF PITB2_ZLINFO occurs 0,
         BEGDA LIKE SY-DATUM,
         ENDDA LIKE SY-DATUM,
         PABRJ(4) TYPE N,                       "Payroll Year
         PABRP(2) TYPE N,                       "Pay. Period
         ZL LIKE PC2BF OCCURS 0,
       END OF PITB2_ZLINFO.
I have a internal table like this,
How to Fetch the values from internal table inside an internal table.
Kindly Help me on this..
Regards,
Ram.

Hi,
Try this....
Loop at PITB2_ZLINF0.
Loop at PITB2_ZLINF0-ZL.
endloop.
Endloop.
Thanks...
Preetham S

Problem in uploading the file of internal table into appliaction server

i want to send the data of internal table to application server through selection screen and in selection screen and in selection screen parameter it should show the path of application server and through that path internal table data should go to application server , if possible give the code

Hi,
form download_file_appl_server.
open dataset p_dlf2 for output
          in text mode encoding default .
if sy-subrc ne 0.
    message:i005 with text-415 text-407.
endif.
loop at i_final into wa_final.
    transfer wa_final to p_dlf2.
endloop.
close dataset p_dlf2.
endform.                    " OPENDATA_CLOSE
where p_dlf2 is the seelction screen parameter which give the application server file path
You can use this code for ur purpose.
Reward if useful.
Regards
Shibin

How to increase the length of internal table dynamically

How to increase the length of internal table dynamically depending on the number of fields fetched into the internal table ?
The requirement code :
types: begin of t_data,
 form like zscr_data_hdr-form,
 werks like zscr_data_hdr-werks,
 matnr like zscr_data_hdr-matnr,
 verid like zscr_data_hdr-verid,
 lot like zscr_data_hdr-lot,
 lot_qty like zscr_data_hdr-lot_qty,
 udate like zscr_data_hdr-udate,
 utime like zscr_data_hdr-utime,
 zuser like zscr_data_hdr-zuser,
 processed like zscr_data_hdr-processed,
 defect like zscr_defect_data-defect,
 vornr like zscr_route_data-vornr,
 fld1 like zscr_defect_data-defect_val,
 fld2 like zscr_defect_data-defect_val,
 fld3 like zscr_defect_data-defect_val,
 fld4 like zscr_defect_data-defect_val,
 fld5 like zscr_defect_data-defect_val,
 fld6 like zscr_defect_data-defect_val,
 fld7 like zscr_defect_data-defect_val,
 fld8 like zscr_defect_data-defect_val,
 fld9 like zscr_defect_data-defect_val,
 fld10 like zscr_defect_data-defect_val,
 fld11 like zscr_defect_data-defect_val,
 fld12 like zscr_defect_data-defect_val,
 fld13 like zscr_defect_data-defect_val,
 fld14 like zscr_defect_data-defect_val,
 fld15 like zscr_defect_data-defect_val,
 fld16 like zscr_defect_data-defect_val,
 fld17 like zscr_defect_data-defect_val,
 fld18 like zscr_defect_data-defect_val,
 fld19 like zscr_defect_data-defect_val,
 fld20 like zscr_defect_data-defect_val,
 fld21 like zscr_defect_data-defect_val,
 fld22 like zscr_defect_data-defect_val,
 fld23 like zscr_defect_data-defect_val,
 fld24 like zscr_defect_data-defect_val,
 fld25 like zscr_defect_data-defect_val,
 fld26 like zscr_defect_data-defect_val,
 fld27 like zscr_defect_data-defect_val,
 fld28 like zscr_defect_data-defect_val,
 fld29 like zscr_defect_data-defect_val,
 fld30 like zscr_defect_data-defect_val,
 fld31 like zscr_defect_data-defect_val,
 fld32 like zscr_defect_data-defect_val,
 fld33 like zscr_defect_data-defect_val,
 fld34 like zscr_defect_data-defect_val,
 fld35 like zscr_defect_data-defect_val,
 fld36 like zscr_defect_data-defect_val,
 fld37 like zscr_defect_data-defect_val,
 fld38 like zscr_defect_data-defect_val,
 fld39 like zscr_defect_data-defect_val,
 fld40 like zscr_defect_data-defect_val,
 fld41 like zscr_defect_data-defect_val,
 fld42 like zscr_defect_data-defect_val,
 fld43 like zscr_defect_data-defect_val,
 fld44 like zscr_defect_data-defect_val,
 fld45 like zscr_defect_data-defect_val,
 fld46 like zscr_defect_data-defect_val,
 fld47 like zscr_defect_data-defect_val,
 fld48 like zscr_defect_data-defect_val,
 fld49 like zscr_defect_data-defect_val,
 fld50 like zscr_defect_data-defect_val,
 fld51 like zscr_defect_data-defect_val,
 fld52 like zscr_defect_data-defect_val,
 fld53 like zscr_defect_data-defect_val,
 fld54 like zscr_defect_data-defect_val,
 fld55 like zscr_defect_data-defect_val,
 fld56 like zscr_defect_data-defect_val,
 fld57 like zscr_defect_data-defect_val,
 fld58 like zscr_defect_data-defect_val,
 fld59 like zscr_defect_data-defect_val,
 fld60 like zscr_defect_data-defect_val,
 fld61 like zscr_defect_data-defect_val,
 fld62 like zscr_defect_data-defect_val,
 fld63 like zscr_defect_data-defect_val,
 fld64 like zscr_defect_data-defect_val,
 fld65 like zscr_defect_data-defect_val,
 fld66 like zscr_defect_data-defect_val,
 fld67 like zscr_defect_data-defect_val,
 fld68 like zscr_defect_data-defect_val,
 fld69 like zscr_defect_data-defect_val,
 fld70 like zscr_defect_data-defect_val,
 fld71 like zscr_defect_data-defect_val,
 fld72 like zscr_defect_data-defect_val,
 fld73 like zscr_defect_data-defect_val,
 fld74 like zscr_defect_data-defect_val,
 fld75 like zscr_defect_data-defect_val,
 fld76 like zscr_defect_data-defect_val,
 fld77 like zscr_defect_data-defect_val,
 fld78 like zscr_defect_data-defect_val,
 fld79 like zscr_defect_data-defect_val,
 fld80 like zscr_defect_data-defect_val,
 fld81 like zscr_defect_data-defect_val,
 fld82 like zscr_defect_data-defect_val,
 fld83 like zscr_defect_data-defect_val,
 fld84 like zscr_defect_data-defect_val,
 fld85 like zscr_defect_data-defect_val,
 fld86 like zscr_defect_data-defect_val,
 fld87 like zscr_defect_data-defect_val,
 fld88 like zscr_defect_data-defect_val,
 fld89 like zscr_defect_data-defect_val,
 fld90 like zscr_defect_data-defect_val,
 fld91 like zscr_defect_data-defect_val,
 fld92 like zscr_defect_data-defect_val,
 fld93 like zscr_defect_data-defect_val,
 fld94 like zscr_defect_data-defect_val,
 fld95 like zscr_defect_data-defect_val,
 fld96 like zscr_defect_data-defect_val,
 fld97 like zscr_defect_data-defect_val,
 fld98 like zscr_defect_data-defect_val,
 fld99 like zscr_defect_data-defect_val,
 fld100 like zscr_defect_data-defect_val,
 fld101 like zscr_defect_data-defect_val,
 fld102 like zscr_defect_data-defect_val,
 fld103 like zscr_defect_data-defect_val,
 fld104 like zscr_defect_data-defect_val,
 fld105 like zscr_defect_data-defect_val,
 fld106 like zscr_defect_data-defect_val,
 fld107 like zscr_defect_data-defect_val,
 fld108 like zscr_defect_data-defect_val,
 fld109 like zscr_defect_data-defect_val,
 fld110 like zscr_defect_data-defect_val,
 fld111 like zscr_defect_data-defect_val,
 fld112 like zscr_defect_data-defect_val,
 fld113 like zscr_defect_data-defect_val,
 fld114 like zscr_defect_data-defect_val,
 fld115 like zscr_defect_data-defect_val,
 fld116 like zscr_defect_data-defect_val,
 fld117 like zscr_defect_data-defect_val,
 fld118 like zscr_defect_data-defect_val,
 fld119 like zscr_defect_data-defect_val,
 fld120 like zscr_defect_data-defect_val,
 fld121 like zscr_defect_data-defect_val,
 fld122 like zscr_defect_data-defect_val,
 fld123 like zscr_defect_data-defect_val,
 fld124 like zscr_defect_data-defect_val,
 fld125 like zscr_defect_data-defect_val,
 fld126 like zscr_defect_data-defect_val,
 fld127 like zscr_defect_data-defect_val,
 fld128 like zscr_defect_data-defect_val,
 fld129 like zscr_defect_data-defect_val,
 fld130 like zscr_defect_data-defect_val,
 fld131 like zscr_defect_data-defect_val,
 fld132 like zscr_defect_data-defect_val,
 fld133 like zscr_defect_data-defect_val,
 fld134 like zscr_defect_data-defect_val,
 fld135 like zscr_defect_data-defect_val,
 dayst like zscr_data_hdr-dayst,
 end of t_data.
In this fld1 to fld135 are defined in internal table.
But if the number of fields are more than 135 then the program is going to short dump.
Some times fld1 to fid170 or more fields will be there in my internal table.
Please suggest me how to make my requirement dynamic and display this data fetched into this internal table onto a .XLS file in the presentation server ?

Hi
You can try to use the type string:
form like zscr_data_hdr-form,
werks like zscr_data_hdr-werks,
matnr like zscr_data_hdr-matnr,
verid like zscr_data_hdr-verid,
lot like zscr_data_hdr-lot,
lot_qty like zscr_data_hdr-lot_qty,
udate like zscr_data_hdr-udate,
utime like zscr_data_hdr-utime,
zuser like zscr_data_hdr-zuser,
processed like zscr_data_hdr-processed,
defect like zscr_defect_data-defect,
vornr like zscr_route_data-vornr,
fieldxx type string,
dayst like zscr_data_hdr-dayst,
end of t_data.
So you can save you informations of every fld<n> concatenating their values into fieldxx.
Max

Hi I want to know the difference between the type of internal tables.

I know the types of internal table but i dont know the difference between them can any one explain me in simple sentence.

Hi,
Standard Internal Tables
Standard tables have a linear index. You can access them using either the index or the key. If you use the key, the response time is in linear relationship to the number of table entries. The key of a standard table is always non-unique, and you may not include any specification for the uniqueness in the table definition.
This table type is particularly appropriate if you want to address individual table entries using the index. This is the quickest way to access table entries. To fill a standard table, append lines using the (APPEND) statement. You should read, modify and delete lines by referring to the index (INDEX option with the relevant ABAP command). The response time for accessing a standard table is in linear relation to the number of table entries. If you need to use key access, standard tables are appropriate if you can fill and process the table in separate steps. For example, you can fill a standard table by appending records and then sort it. If you then use key access with the binary search option (BINARY), the response time is in logarithmic relation to
the number of table entries.
Sorted Internal Tables
Sorted tables are always saved correctly sorted by key. They also have a linear key, and, like standard tables, you can access them using either the table index or the key. When you use the key, the response time is in logarithmic relationship to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique, or non-unique, and you must specify either UNIQUE or NON-UNIQUE in the table definition. Standard tables and sorted tables both belong to the generic group index tables.
This table type is particularly suitable if you want the table to be sorted while you are still adding entries to it. You fill the table using the (INSERT) statement, according to the sort sequence defined in the table key. Table entries that do not fit are recognised before they are inserted. The response time for access using the key is in logarithmic relation to the number of
table entries, since the system automatically uses a binary search. Sorted tables are appropriate for partially sequential processing in a LOOP, as long as the WHERE condition contains the beginning of the table key.
Hashed Internal Tables
Hashes tables have no internal linear index. You can only access hashed tables by specifying the key. The response time is constant, regardless of the number of table entries, since the search uses a hash algorithm. The key of a hashed table must be unique, and you must specify UNIQUE in the table definition.
This table type is particularly suitable if you want mainly to use key access for table entries. You cannot access hashed tables using the index. When you use key access, the response time remains constant, regardless of the number of table entries. As with database tables, the key of a hashed table is always unique. Hashed tables are therefore a useful way of constructing and
using internal tables that are similar to database tables.

Export internal table to memory in User Exit FM

Hi all,
My scenario here is to export an internal table in one user exit FM and import it back in another user exit FM.
I was trying to use
Export lt_table to memory id 'LABEL'.
then
Import lt_table from memory id 'LABEL'.
But then i hit error in the import statement. How can I rectify this?
Thanks. Answer will be rewarded.

Refer to the below related threads
Export an internal table to memory and import from memory into an internal
http://help.sap.com/saphelp_erp2005/helpdata/en/fc/eb3bf8358411d1829f0000e829fbfe/frameset.htm
Regards,
Santosh

Exporting an internal table to memory

Hi
I want to call an program from another program and want the values stored in an internal table used in the called program.
how can i export an internal table to memory id an then import it.
Regards
Arun

So to be clear, for your requirement it would be:
* Towards the end of the called program
EXPORT it_itab TO MEMORY ID 'ZZ_MEM_ID'.
* And then from calling program after the submit zzzz and return statement
IMPORT it_itab FROM MEMORY ID 'ZZ_MEM_ID'.
Hope that helps.
Brad
Message was edited by: Brad Williams (put back intro text)
Message was edited by: Brad Williams

Save Internal table to memory - problem

Hi everybody ,
I need to extract one Internal table to memory , every 1st in the Month .
Then every day I will be reading this table for my report ( in order to avoid running every day same and same database selections) .
My originall idea wos with EXPORT TO MEMORY ID , AND IMPORT
but it does'nt work next day ... With Export data is cept only untill tthe end of the transaction ...
Is there any way except of storing data in one Z_ database table ???
Thanks in advance

Hi,
You can use the following code to export to memory
*data variable required for background processing
data: wa_indx type indx.
*EXPORT Internal Table TO MEMORY ID 'XYZ'.
*part for background processing
export tab = <your table> to database indx(xy) from wa_indx client
sy-mandt id 'XYZ'.
the following code will import from Memory and clear memory
*data variable required for background processing
data: wa_indx type indx.
imports from database the list sent by the calling program
IMPORT tab = <your table> FROM DATABASE indx(xy) TO wa_indx CLIENT sy-mandt
ID 'XYZ'.
deletes the data to save wastage of memory
DELETE FROM DATABASE indx(xy)
CLIENT sy-mandt
ID 'XYZ'.
Regards,
Samson Rodrigues.

Pass Internal Table to Memory

Dear Experts.
I have the following problem.
I am using a User-Exit for Travel that is called from a program standard with use the T.Code TRIP. The program standard use a structure that when entry in the user exit not is. I need use this structure in the user exit. (p_t_req_head).
I had read abour SAP and ABAP Memory but from the program standar How can Pass Internal Table to Memory SAP or ABAP from the program standard to user-exit?
When I am doing debugging in the program Standard and this call to the user exit, I use ()namestructure for example ()p_t_req_head and I get the datas of the structure, But In the Source Code ABAP, How can do this with instructions?
Regards

Hi,
You try with Import & Export Statements as follows ---
DATA : t_itab LIKE TABLE OF spfli.
EXPORT t_itab TO MEMORY ID 'ABCD'.
After sending the internal table to ABAP memory you need to get that by IMPORT in the called session.
IMPORT t_itab FROM MEMORY ID 'ABCD'.

Export internal table to memory.

How can I export and import an internal table to memory?
This:
export messtab to memory id 'TAB'. (in program 1)
import messtab=messtab from memory id 'TAB'. (in program 2)
does not work.

Even without the brackets it doesn't work.
In program 1 I have:
    WRITE text-e21 TO messtab-message.
    messtab-type = c_tipo_error.
    APPEND messtab. CLEAR messtab.
    DELETE messtab WHERE message = space.
    EXPORT messtab[] TO MEMORY ID para.
    EXIT.
The EXIT leads to program 2, from where I made a submit to program 1, and where I have:
import messtab[] from memory id para.
Where:
        DATA: para TYPE tpara-paramid VALUE 'MES',
        messtab TYPE TABLE OF bapireturn WITH HEADER LINE.
What's wrong?
Thanks in advance.
Oh, and I've checked the table in program 1 does have an entry.

Passing Dynamic Internal Tables to Memory

I have a bit of a conundrum right now that I can't seem to correct. I am working on adding an ALV report to an existing report program. I was able to write a simple helper program that builds a custom object that I defined that translates my raw data into two seperate dynamic tables, and then builds an ALV grid and outputs it. The reason I wrote this in a simple helper program was so that I could use SUBMIT ... EXPORTING LIST TO MEMORY from my primary report program and capture the input so I can later write it out under our company's standard ABAP list format as if I were using WRITE statements.
The output of the report itself is working beautifully. We have included functionality to automatically take the output, produce an HTML file from it, and then FTP it directly to a webserver so our clients can get easy access to it. What I want to be able to do though is give the clients two tab-delimited files that contain the raw data that was used to build the report. We have an interface in place to do that, but I somehow need to be able to pass these two dynamic internal tables which I have field-symbols to reference back to my calling program.
Here is what I am trying to do:
CALL METHOD OBJ_ALV_MR_EST_REASONS->PRODUCE_ESTIMATION_REPORT
 IMPORTING
 RPT_DATA_BY_REASON = ref_it_estreason
 RPT_DATA_BY_DISTRICT = ref_it_district.
* Assign the field symbols
ASSIGN ref_it_estreason->* TO <it_estreason>.
ASSIGN ref_it_district->* TO <it_district>.
* Export the two internal tables to memory so they can be
* retrieved by the calling program
EXPORT reason = <it_estreason>[]
 district = <it_district>[]
TO MEMORY ID 'ZCR_ESTIMATION_REASON_RPT'.
As you can see, my method returns two references to dynamic internal tables. I have used the memory debugger to see that these tables are being correctly written to the ABAP memory.
However, back in my parent program when I try to do the following,
CREATE DATA ref_it_estreason TYPE REF TO DATA.
 CREATE DATA ref_it_district TYPE REF TO DATA.
 ASSIGN ref_it_estreason->* TO <it_estreason>.
 ASSIGN ref_it_district->* TO <it_district>.
 IMPORT reason = <it_estreason>
 district = <it_district>
 FROM MEMORY ID 'ZCR_ESTIMATION_REASON_RPT'.
I get the REFS_NOT_SUPPORTED_YET exception which says that "For the statement Export/Import ..." object references, interface references, and data references are currently not supported".
I have tried multiple other ways of defining my field-symbols or my reference pointers but they all result in exceptions of some sort. Is there any way for me to get this data passed back? It seems like there must be a way to get the data from memory since I know it's being correctly stored there.
Thanks in advance.

Shortly after posting this, I had an idea which I was able to implement to actually get this to work.
I decided that I would simply pass the FIELDCAT tables for each of my dynamic tables into the same memory ID as the tables themselves.
EXPORT reason_fcat = it_estreason_fcat
 district_fcat = it_district_fcat
 reason = <it_estreason>[]
 district = <it_district>[]
TO MEMORY ID 'ZCR_ESTIMATION_REASON_RPT'.
Then, back in my calling program I execute the following code. This retrieves the FIELDCAT tables, builds two empty dynamic table type reference variables and then lets me create field-symbols to reference those components.
* Retrieve the fieldcat internal tables first
 IMPORT reason_fcat = it_estreason_fcat
 district_fcat = it_district_fcat
 FROM MEMORY ID 'ZCR_ESTIMATION_REASON_RPT'.
* Generate an internal table type assigned to each
* reference variable based on the fieldcat listings we
* retrieve
 CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = it_estreason_fcat
 IMPORTING
 ep_table = ref_it_estreason.
 CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = it_district_fcat
 IMPORTING
 ep_table = ref_it_district.
* Assign the field symbols
 ASSIGN ref_it_estreason->* TO <it_estreason>.
 ASSIGN ref_it_district->* TO <it_district>.
 CREATE DATA ref_wa_estreason LIKE LINE OF <it_estreason>.
 CREATE DATA ref_wa_district LIKE LINE OF <it_district>.
 ASSIGN ref_wa_estreason->* TO <wa_estreason>.
 ASSIGN ref_wa_district->* TO <wa_district>.
* Finally, we can retrieve the data from memory and assign
* to the internal tables referenced by our field-symbols
 IMPORT reason = <it_estreason>[]
 district = <it_district>[]
 FROM MEMORY ID 'ZCR_ESTIMATION_REASON_RPT'.
This worked beautifully and saved me from having to do a major redesign. I don't know how helpful it would be for ABAP Objects to be passed to memory (I believe some type of serialization would need to be in order there), but for dynamically typed internal tables it worked like a dream with little overhead.

Regarding the modify of internal table

do 40 times varying lga from p0008-lga01 next p0008-lga02
varying bet from p0008-bet01 next p0008-bet02.
*data: bet01 type p decimals 2.
if lga is initial.
exit.
endif.
INDEX = SY-INDEX.
amt1 = bet .
*bet01 = 20 / 100.
bet = ( bet * 50 ) / 100 .
CONCATENATE ch INDEX INTO BETXX.
assign betxx to <F2>.
assign (betxx) to <F1>.
<F2> = bet.
modify p0008 index INDEX transporting F1
write:/ <F2>.
enddo.
*endif.
ENDCASE.
endform.
can sombody tell me how to modify the p0008 table at the place vr im having the bet01 bet02 and so on fields.
vn im using this modify statement im getting an error as
Unable to interpret "INDEX". Possible causes of error: Incorrect

Hi Madhvi,
When you are posting a thread, please make sure others do not find it difficult to understand. Please don't use abbreviations like "vr" and "vn".
If you need prompt responses, please ensure you describe your requirements in
a proper manner.
You are getting error because of using wrong syntax. the correct syntax is -
MODIFY <itab> FROM <wa> [INDEX <idx>] [TRANSPORTING <f1> <f 2> ... ].
The work area <wa> specified in the FROM addition replaces the existing line in <itab>. The work area must be convertible into the line type of the internal table.
If you use the INDEX option, the contents of the work area overwrites the contents of the line with index <idx>. If the operation is successful, SY-SUBRC is set to 0. If the internal table contains fewer lines than <idx>, no line is changed and SY-SUBRC is set to 4.
Without the INDEX addition, you can only use the above statement within a LOOP. In this case, you change the current loop line <idx> is implicitly set to SY-TABIX.
When you change lines in sorted tables, remember that you must not change the contents of key fields, and that a runtime error occurs if you try to replace the contents of a key field with another value. However, you can assign the same value.
The TRANSPORTING addition allows you to specify the fields that you want to change explicitly in a list.
Regards
Indrajit.

Regarding the modifying an internal table

hi,
   i am having an internal table,i have to modify one field and the remaining fields should remain same in the internal table while displaying the internal table.
   can any body send the solution for this issue.
thanks in advance

hi,
you can see the following logic regarding modify statement with in loop or without loop.
DATA : BEGIN OF itab OCCURS 0,
       no(10) TYPE n,
       name(10) TYPE c,
       city(20) TYPE c,
       END OF itab.
itab-no = 001.
itab-name = 'vijay'.
itab-city = 'dharmavaram'.
APPEND itab.
itab-no = 002.
itab-name = 'krishna'.
itab-city = 'dharmavaram'.
APPEND itab.
itab-no = 003.
itab-name = 'vijay'.
itab-city = 'dharmavaram'.
APPEND itab.
itab-name = 'ram1'.
MODIFY itab INDEX 3 TRANSPORTING name.
LOOP AT itab.
IF sy-tabix = 2.
    itab-no = '0012'.
    itab-name = 'krishna.v'.
    MODIFY itab INDEX 2 TRANSPORTING no name.
    CLEAR itab.
ENDIF.
ENDLOOP.
LOOP AT itab.
WRITE :/ itab-no,itab-name,itab-city.
ENDLOOP.
Hope this example will be usage for you.
Reward with points if it is useful.
Regards,
Vijay

Regarding how to delete the record in internal table

Hi experts ,
how to delete the record in intarnal table after validating the data,
if record contains invalid fields?
i am giving my code see this and give me the answer?
loop at it_data into wa_data .
Validate Cost Center
    READ TABLE it_kostl INTO wa_kostl WITH KEY kostl = wa_data-kostl BINARY SEARCH.
    IF sy-subrc NE 0.
      PERFORM update_error_log USING wa_data
                                     text-004.
    ENDIF.
Validate source file material ( material number )
loop at it_mara into wa_mara .
read table it_ausp into wa_ausp with key atwrt = wa_data-i_matnr .
           if sy-subrc NE 0 .
   PERFORM update_error_log USING wa_data
                                       text-002.
delete it_data-objek .
     else.
read table it_mara into wa_mara with key matnr = wa_ausp-objek .
       if sy-subrc EQ 0 .
       wa_data-objek = wa_mara-matnr.
       wa_data-matkl = wa_mara-matkl.
     ENDIF.
     Modify it_data from wa_data .
endif.
*endloop.
Validate unit of measure (unit)
    READ TABLE it_t006 INTO wa_t006 WITH KEY msehi = wa_data-unit .
    IF sy-subrc NE 0.
      PERFORM update_error_log USING wa_data
                                     text-003.
    endif.
Validate delivery location ( storage location )
    READ TABLE it_lgort INTO wa_lgort WITH KEY del_loc = wa_data-del_loc.
    IF sy-subrc NE 0.
      PERFORM update_error_log USING wa_data
                                     text-001.
         if wa_data-flag ='x' .
      delete it_data from wa_data .
    endif.
    ENDIF.
endloop.

Hi Naren,
First get the index number of the IT_data table and store it in one variable whose declaration like this.
data: tabix type sy-tabix.
while reading the internal table it_data set the tabix variable.
tabix = sy-tabix.
Instead of the above use below one.
Delete it_data-objek
Use the Below statement it will delete the row from the internal table.
Delete it_data-objek index tabix
Thanks,
Chidanand

Regarding the transfering the internal table to memory

Similar Messages

Maybe you are looking for