Dynamic Work Area and field symbol

Hi All,
I'm have a big internal table like this
data: begin of data occurs 0,
Field01,
Field02,
Field03,
*bucket 1
Field04,
Field05,
Field06,
*bucket 2
Field04,
Field05,
Field06,
*bucket 3
Field04,
Field05,
Field06,
Field 1, 2 3 will be the same for pernr, first last name.
Field 4, 5, 6 are the same format but different numbers (or values ) in different buckets.
Each bucket can be shown (or not) based on the condition of a person, for example if that person live in 2 states, it will show 2 bucket with 2 address info inside each.
I will run this under get pernr to sort out each person who have many address or not.
Can I use dynamic work area and field symbol here? if I can, how?
Really appreciate your help with points...

You can use the ASSIGN COMPONENT ... and than APPEND the work area to the table.
Check out this sample program:
REPORT ZTEST_NP.
DATA: BEGIN OF ITAB OCCURS 0,
 F1 TYPE I,
 F2 TYPE I,
 F3 TYPE I,
 END OF ITAB.
DATA: WA_ITAB LIKE ITAB.
DATA: L_CNT TYPE I.
FIELD-SYMBOLS: <F_FLD> TYPE ANY.
DO 10 TIMES. " I want 10 reocrds
CLEAR L_CNT.
DO 3 TIMES. " I have 3 fields
 L_CNT = L_CNT + 1.
 ASSIGN COMPONENT L_CNT OF STRUCTURE WA_ITAB TO <F_FLD>.
 <F_FLD> = L_CNT.
ENDDO.
APPEND WA_ITAB TO ITAB.
CLEAR ITAB.
ENDDO.
LOOP AT ITAB INTO WA_ITAB.
WRITE: / WA_ITAB-F1,
 WA_ITAB-F2,
 WA_ITAB-F3.
ENDLOOP.
Regards,
Naimesh Patel

Similar Messages

How to fill Dynamic work area or field symbol?

HI All,
I have created dynamic work area(field symbol) by using following code. Now I want to fill the work area with values which are there in other internal table.
* Create dynamic internal table/structure
call method cl_alv_table_create=>create_dynamic_table
 exporting
 it_fieldcatalog = it_fieldcat
 importing
 ep_table = dyn_table.
assign dyn_table->* to <fs_table>.
* Create dynamic work area and assign to Field Symbol
create data dyn_line like line of <fs_table>.
assign dyn_line->* to <fs_wa>.
My <FS_WA> contains:
ROW1
ROW2
ROW3
ROW4 as fields in it without having any data.
I have other internal table.. where I have FIELDS and Data like following:
FIELD1 FIELD2 FIELD3
ID1 ROW1 A1
ID1 ROW2 A2
ID1 ROW3 A3
ID1 ROW4 A4
ID2 ROW1 B1
ID2 ROW2 B2
ID2 ROW3 B3
ID3 ROW1 C4
Important thing that I have to share with you is... Source table of my Internal table and Source structure to create my dynamic table are same.
This dynamic table has fields... with "FIELD2" values.
Thanks,
Naveen.I

Create a dynamic internal table
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = lt_fcat
 IMPORTING
 ep_table = lt_dy_table.
Create dynamic work area and assign to FS
ASSIGN lt_dy_table->* TO <fs_dyn_table>.
CREATE DATA lt_dy_line LIKE LINE OF <fs_dyn_table>.
ASSIGN lt_dy_line->* TO <fs_dyn_wa>.
Define WA
CREATE DATA dref TYPE (iv_struc_name).
ASSIGN dref->* TO <fs_final>.
Populate dynamic table from the file
OPEN DATASET iv_path FOR INPUT IN TEXT MODE ENCODING DEFAULT.
IF sy-subrc = 0.
 DO.
 READ DATASET iv_path INTO ls_str.
 IF sy-subrc <> 0.
 ev_failed = abap_true.
 EXIT.
 ENDIF.
 SPLIT ls_str AT ';' INTO TABLE lt_dyn_tab. " columns
 LOOP AT lt_dyn_tab INTO ls_dyn_tab.
 READ TABLE lt_struc_fld INTO ls_struc_fld INDEX sy-tabix.
 IF sy-subrc EQ 0.
 MOVE ls_struc_fld-fieldname TO ls_fieldname.
 ASSIGN COMPONENT ls_fieldname OF STRUCTURE <fs_dyn_wa> TO <fs_val>.
 IF sy-subrc = 0.
 <fs_val> = ls_dyn_tab.
 ENDIF.
 ASSIGN COMPONENT ls_fieldname OF STRUCTURE <fs_final> TO <fs_val>.
 IF sy-subrc = 0.
 <fs_val> = ls_dyn_tab.
 ENDIF.
 ENDIF.
 ENDLOOP.
 APPEND <fs_dyn_wa> TO <fs_dyn_table>.
 APPEND <fs_final> TO et_table.
 UNASSIGN: <fs_val>.
 ENDDO.
ENDIF.
CLOSE DATASET iv_path.

Some help needed on dynamic internal tables and field symbols

Hi,
I have a dyn internal table <dyn_table_r>.
One of its fields is kna1-kunnr.
I have another wa <fs>, with only one field alt_kunnr.
now i want to modify the data of <dyn_table_r>-kna1-kunnr from <fs>-alt_kunnr
How should i do it?
Regards ,
Harshit Rungta

Harshit Rungta:
You have opened a number of related questions today. I'd like to see the other ones closed before you continue with this one.
I'll lock this but will re-open it once the others are marked as solved.
Rob

How to move a dynamic variable to a FIELD-SYMBOL

Hello:
i would like to ask a favor i have been trying to move a dynamic variable to a FIELD-SYMBOL but, when i compile the programm it send a error message that say 'error with assign'.
The FS is declared like this
FIELD-SYMBOLS: <dyn_table> TYPE STANDARD TABLE, <dyn_wa>.
and then there is a PERFORM that send a dynamic varible and then this variable is asigned to the <dyn_table> and after of this one variable is created like this CREATE DATA wa_dynamic LIKE LINE OF <dyn_table>.
and finalilly there is a sentences where i trying to send the wa_dynamic to the <dyn_wa>.
here is where the error appear.
if you have any tips for this problem i will appreciate.
thanks a lot
Definition of FS
FIELD-SYMBOLS: <dyn_table> TYPE STANDARD TABLE, <dyn_wa>.
PERFORM
Create dynamic internal table and Assign it to Field Symbol
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = it_fldcat
 IMPORTING
 ep_table = it_dynamic.
ASSIGN it_dynamic->* TO <dyn_table>.
Create dynamic work area and assign to FS
CREATE DATA wa_dynamic LIKE LINE OF <dyn_table>.
ASSIGN wa_dynamic->* TO <dyn_wa>. "HERE IS THE PROBLEM

How is wa_dynamic defined?
data: wa_dynamic type ref to data.
Regards,
Rich Heilman

Populate data into the dynamic table ie using field symbols

Dear All,
I need to convert the XML data into internal table. I did this using the guidelines in the forum. Using all those i can get my data
in the format of
Cname Cvalue
id 1
name XX
id 2
name YY
But i need the values in the format of int_tab like,
ID Name
1 XX
2 YY
I used the below code to create the dynamic table strucure.
call method cl_alv_table_create=>create_dynamic_table
 exporting
 it_fieldcatalog = ifc
 importing
 ep_table = dy_table.
assign dy_table->* to <itab>.
* Create dynamic work area and assign to FS
create data dy_line like line of <itab>.
assign dy_line->* to <wa>.
So now my strucure will be like ID Name.
I strucked in the place of populating the data into this like 1,XX,2,YY into the dynamic table.
If you come across with this scenario, can anyone suggest me on this.
Regards,
Anita Vizhi Arasi B

Hi Anita,
Try to understand below given code. It works same as you want. But I used Function module not any method.
TYPES: BEGIN OF ty_xml,
 raw(255) TYPE x,
 END OF ty_xml.
DATA: lv_file_name TYPE rlgrap-filename,
 lit_hdr TYPE TABLE OF ty_hdr,
 ls_hdr TYPE ty_hdr,
 lv_file TYPE string,
 wa_xml TYPE ty_xml,
 lit_xml TYPE STANDARD TABLE OF ty_xml,
 lv_filename TYPE string ,
 ls_xmldata TYPE xstring ,
 lit_result TYPE STANDARD TABLE OF smum_xmltb,
 ls_result TYPE smum_xmltb,
 lit_return TYPE STANDARD TABLE OF bapiret2,
 lv_size TYPE i,
 lv_count TYPE i.
CONSTANTS: line_size TYPE i VALUE 255.
REFRESH lit_hdr.
*~ File selected from Local System
CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
 EXPORTING
 program_name = syst-repid
 dynpro_number = syst-dynnr
 CHANGING
 file_name = lv_file_name
 EXCEPTIONS
 mask_too_long = 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.
lv_file = lv_file_name.
*~ Upload for Data Provider
CALL FUNCTION 'GUI_UPLOAD'
 EXPORTING
 filename = lv_file
 filetype = 'BIN'
 has_field_separator = ' '
 header_length = 0
 IMPORTING
 filelength = lv_size
 TABLES
 data_tab = lit_xml
 EXCEPTIONS
 OTHERS = 1.
*~ Convert from Binary to String
CALL FUNCTION 'SCMS_BINARY_TO_XSTRING'
 EXPORTING
 input_length = lv_size
 IMPORTING
 buffer = ls_xmldata
 TABLES
 binary_tab = lit_xml
 EXCEPTIONS
 failed = 1
 OTHERS = 2.
*~ Parse XML docment into a table structure
CALL FUNCTION 'SMUM_XML_PARSE'
 EXPORTING
 xml_input = ls_xmldata " Buffered data
 TABLES
 xml_table = lit_result " final internal table which contain records
 return = lit_return.
LOOP AT lit_result INTO ls_result.
 IF ls_result-hier = '3'.
 IF ls_result-type = 'V'.
 CASE ls_result-cname.
 WHEN 'intno'. "Internal Number
 ls_hdr-intno = ls_result-cvalue.
 WHEN 'acode'. "Article Code
 ls_hdr-matnr = ls_result-cvalue.
 WHEN 'adesc'. "Article Description
 ls_hdr-maktx = ls_result-cvalue.
 WHEN 'idesc'. "Item Description
 ls_hdr-itmds = ls_result-cvalue.
 WHEN 'sdesc'. "Standard Description
 ls_hdr-stdds = ls_result-cvalue.
 WHEN 'at'. "Article Type
 ls_hdr-mtart = ls_result-cvalue.
 WHEN 'mc'. "Merchandise Category
 ls_hdr-matkl = ls_result-cvalue.
 WHEN 'cp'. "Characteristic Profile
 ls_hdr-charp = ls_result-cvalue.
 CONDENSE ls_hdr-charp.
 WHEN 'c1'.
 ls_hdr-col01 = ls_result-cvalue.
 WHEN 'c2'.
 ls_hdr-col02 = ls_result-cvalue.
 WHEN 'c3'.
 ls_hdr-col03 = ls_result-cvalue.
 WHEN 'c4'.
 ls_hdr-col04 = ls_result-cvalue.
 WHEN 'c5'.
 ls_hdr-col05 = ls_result-cvalue.
 WHEN 'c6'.
 ls_hdr-col06 = ls_result-cvalue.
 WHEN 'tc'. "Tax Classification
 ls_hdr-taklv = ls_result-cvalue.
 WHEN 's'. "Season
 ls_hdr-saiso = ls_result-cvalue.
 WHEN 'sy'. "Season Year
 ls_hdr-saisj = ls_result-cvalue.
 WHEN 'fg'. "Fashion Grade
 ls_hdr-fashg = ls_result-cvalue.
 WHEN 'rm'. "Reference Material
 ls_hdr-rfmat = ls_result-cvalue.
 WHEN 'fcv'. "Free Character Value
 ls_hdr-frecv = ls_result-cvalue.
 WHEN 'uom'. "Unit of Measure
 ls_hdr-uom = ls_result-cvalue.
 WHEN 'pou'. "PO Unit
 ls_hdr-pount = ls_result-cvalue.
 WHEN 'v'. "Vendor
 ls_hdr-lifnr = ls_result-cvalue.
 WHEN 'b'. "Vendor
 ls_hdr-brand = ls_result-cvalue.
 WHEN 'pg'. "Purchasing Group
 ls_hdr-wekgr = ls_result-cvalue.
 WHEN 'rv'. "Regular Vendor
 ls_hdr-rlifn = ls_result-cvalue.
 WHEN 'pp'. "Pricing Profile
 ls_hdr-sprof = ls_result-cvalue.
 WHEN 'sp'. "Sales Price
 ls_hdr-spric = ls_result-cvalue.
 WHEN 'm'. "Margin
 ls_hdr-margn = ls_result-cvalue.
 WHEN 'c'. "Calculate
 ls_hdr-pcalc = ls_result-cvalue.
 WHEN 'purp'. "Purchase Price
 ls_hdr-ppric = ls_result-cvalue.
 WHEN 'a'. "Assortment
 ls_hdr-asort = ls_result-cvalue.
 WHEN 'bm'. "Batch Management
 ls_hdr-batch = ls_result-cvalue.
 WHEN 'mrl'. "Min. Remaining Life
 ls_hdr-minrl = ls_result-cvalue.
 WHEN 'aag'. "Account Assignment Group
 ls_hdr-acass = ls_result-cvalue.
 WHEN 'vc'. "Valuation Class
 ls_hdr-valcl = ls_result-cvalue.
 WHEN 'eancat'. "EAN Category
 ls_hdr-eanct = ls_result-cvalue.
 WHEN 'ean11'.
 ls_hdr-ean11 = ls_result-cvalue.
 ENDCASE.
 AT END OF hier.
 APPEND ls_hdr TO lit_hdr.
 ENDAT.
 ENDIF.
 ENDIF.
ENDLOOP.
APPEND LINES OF lit_hdr TO git_hdr.
DELETE git_hdr WHERE maktx IS INITIAL "Article Description
 AND mtart IS INITIAL "Article Type
 AND matkl IS INITIAL "Merchandise Category
 AND charp IS INITIAL "Characteristic Profile
 AND taklv IS INITIAL "Tax Classification
 AND uom IS INITIAL "Unit of Measure
 AND pount IS INITIAL "PO Unit
 AND lifnr IS INITIAL "Vendor
 AND brand IS INITIAL "Brand
 AND wekgr IS INITIAL "Purchasing Group
 AND ppric IS INITIAL "Purchasing Price
 AND spric IS INITIAL "Sales Price
 AND acass IS INITIAL "A/c Assign. Grp.
 AND valcl IS INITIAL "Valuation Class
 AND saiso IS INITIAL "Season
 AND saisj IS INITIAL. "Season Year
IF git_hdr[] IS NOT INITIAL.
 CLEAR: lv_count.
 LOOP AT git_hdr INTO ls_hdr.
 lv_count = lv_count + 1.
 ls_hdr-intno = lv_count.
 MODIFY git_hdr FROM ls_hdr TRANSPORTING intno.
 CLEAR: ls_hdr.
 ENDLOOP.
ENDIF.
Code written is part of my program. Try to understand it. I hope it will help you out.
Regards,
Narendra

How to read data from dynamic work area.

Hi guys,
 I have created dynamic table and work area for report.
i have populated few values in dynamic work area.
Now i want to read that data from work area again for calculation.
i can not use local varialbes to store those values as i dont know how many such variables i need to read.
that will be known only at run time.
So as per my knowledge i have only 1 option...to read those all values from work area.
Kindly help me .... how can i read data which is stored in dynamic work area.

Hi Kiran,
Following is not exact code, but exact solution to your problem:
LOOP AT <dyn_table> ASSIGNING <dyn_wa>.
 l_tabix = sy-tabix.
 ASSIGN COMPONENT 'KOTAB' OF STRUCTURE <dyn_wa> TO <l_kotab>.
 IF <l_kotab> IS ASSIGNED AND <l_kotab> IS INITIAL.
 <l_kotab> = gt_tabs-kotab.
 MODIFY <dyn_table> FROM <dyn_wa> INDEX l_tabix.
 ENDIF.
 ENDLOOP.
I am hardcoding KOTAB as I was sure about that being in the dynamic structure.
You can loop on the field catalogue, which you used to create dyamic table, to use the FIELDNAME to read all the fields of the work area (structure) of your dynamic table.
thanks,
Aabhas
Edited by: Aabhas K Vishnoi on Sep 24, 2009 8:12 PM

Difference between work area and internal tables.

Hi I wanna know the difference between work area and internal tables.
what happend if i give with out header line in internal table.
also how to assosiate work area to internal table in that scenario.

Hi Balaji..
The internal table is an ABAP runtime object which has two parts the Body and the header.
Whereas a work area cannot have a body.. It is mere a field or group of fields which can hold values at runtime..
In the SAP higher versions mySAP ERP, the use of tables with header line is made obsolete.. But there is absolutely no problem with the same..
Just think that when you define an internal table with occurs or with header line statement, the system automatically creates a workarea with this table, using which you can access the contents in the bosy of tyhe table.. You can read a record from the table body to this header or add a record in the header to the internal table body..
When you work with a table ITAB without a header line, you can not use statements like READ TABLE, APPEND, INSERT etc without giving an explicit work area..
Suppose i have an internal table like:
DATA : itab TYPE STANDARD TABLE OF t001.
This table will not have a header with it.
If you will use APPEND itab. The compilor will give error.
Here i will create a work area with same structure of the table.
DATA : e_wa TYPE t001.
Now i will write:
APPEND e_wa TO itab.
READ TABLE itab INTO e_wa WITH KEY xxxxxx
LOOP AT itab INTO e_wa... etc..
In a better approach we use Field symbols with such tables, instead of structures
FIELD-SYMBOLS: <fs_itab> TYPE t001.
So,
LOOP AT itab ASSIGNING <fs_itab>
READ TABLE itab ASSIGNING <fs_itab> etc.. However we can not use field symbols in few cases..
I hope this will help you..
Thanks and Best Regards,
Vikas Bittera.
**Points for usefull answers**

Internal table declaration - work area and body

Hi all
I have declared my internal table in my program as
data : itab_wa type ZRESULT_LINE,
       itab    type ZRESULT_ROW.
Where ZRESULT_LINE and ZRESULT_ROW are the structure and table types.
Now I want to add
data: TCOLOR TYPE SLIS_T_SPECIALCOL_ALV.
in my internal table declaration. How can I do this. Please remember I need to have work area and body in my internal table as I have used work area and body in my code.
Waiting..............
Message was edited by: Raju Boda

HI,
See the Declarion types of workarea and Internal tables
* Table declaration (old method)
DATA: BEGIN OF tab_ekpo OCCURS 0,             "itab with header line
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
END OF tab_ekpo.
*Table declaration (new method)     "USE THIS WAY!!!
TYPES: BEGIN OF t_ekpo,
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
END OF t_ekpo.
DATA: it_ekpo TYPE STANDARD TABLE OF t_ekpo INITIAL SIZE 0,      "itab
      wa_ekpo TYPE t_ekpo.                    "work area (header line)
* Build internal table and work area from existing internal table
DATA: it_datatab LIKE tab_ekpo OCCURS 0,      "old method
      wa_datatab LIKE LINE OF tab_ekpo.
* Build internal table and work area from existing internal table,
* adding additional fields
TYPES: BEGIN OF t_repdata.
        INCLUDE STRUCTURE tab_ekpo. "could include EKKO table itself!!
TYPES: bukrs TYPE ekpo-werks,
       bstyp TYPE ekpo-bukrs.
TYPES: END OF t_repdata.
DATA: it_repdata TYPE STANDARD TABLE OF t_repdata INITIAL SIZE 0,   "itab
      wa_repdata TYPE t_repdata.                 "work area (header line
you need to maintain same structure for both workarea as well Internal table
Regards
Sudheer

Create Dynamic Structure based on Field-Symbol

Hi Experts!!
I need to create a structure with dynamic structure included within.
I have a parameter on sel. screen in which we provide table name.
PARAMETERS: p_table TYPE tabname.
FIELD-SYMBOLS: <gt_data> TYPE ANY TABLE.
CREATE DATA gr_data TYPE TABLE OF (p_table).
ASSIGN gr_data-* TO <gt_data>.
Now I need a structure like below:
TYPES: BEGIN OF type_test,
struct TYPE <gt_data>, " dynamic structure based on table name entered on sel. screen
fld1 TYPE c,
fld2 TYPE n,
END OF type_test.
Can somebody suggest how to achieve this?
Your help is highly appreciated. Thanks a lot

You can view this thread where our friend Marcin rocks .. Dynamically create a type
FIELD-SYMBOLS: <gt_data> TYPE ANY TABLE.
FIELD-SYMBOLS: <gs_wa> TYPE ANY.
data:wf_ref type ref to data.
DATA:i_comp TYPE cl_abap_structdescr=>component_table,
i_tot_comp TYPE cl_abap_structdescr=>component_table.
CREATE DATA gr_data TYPE TABLE OF (p_table).
ASSIGN gr_data-* TO <gt_data>.
create data wf_ref like line of <gt_data>.
assign wf_ref->* to <gs_wa>.
*--Getting Compoents from existing type
lf_struct ?= cl_abap_typedescr=>describe_by_name( '<GS_WA>' ).
i_comp = lf_struct->get_components( ).
APPEND LINES OF i_comp TO i_tot_comp.
The idea is Get all the field details available it to i_tot_comp, then append individual fields manually to
i_tot_comp as explained in the link and create a dynamic structure and table.

Work area and internal table

hi friends,
Please let me know when do we use work area and when do we use internal table.
Thanks in advance
Tina Wilson

Work areas are used with internal tables. For example if you have an internal table defined like this.
data: itab type table of mara.
This internal table can hold many rows of data, right? SO say you need to read this data. Well you will need to LOOP or READ the internal table, since this internal table has no header line(please to put the read data), you need to have a work area to put the data into.
data: wa like line of itab.
Loop at itab into wa.
endloop.
Now if you defined the internal table with a header line, there is no reason to have the work area and you can just do the same like this.
data: itab type table of mara with header line.
Loop at itab.
endloop.
It is now best practice to use work areas instead of header lines because in ABAP OO, header lines are not allowed.
Regards,
Rich Heilman

Creating dynamic internal table(Not field symbol table)

Hi Experts,
I am facing problem creating Intarnal table
I have fieldcatalog, I want create dynamic internal table(Not field symbol table).
I have written----
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 i_style_table =
 it_fieldcatalog = it_fldcat
 it_fieldcatalog = me->gt_fieldcat
 i_length_in_byte =
 IMPORTING
 ep_table = lt_new_table
 e_style_fname =
 EXCEPTIONS
 generate_subpool_dir_full = 1
 OTHERS = 2.
 ASSIGN lt_new_table->* TO <gt_dyn_repdata>.
 CREATE DATA ls_new_line LIKE LINE OF <gt_dyn_repdata>.
 ASSIGN ls_new_line->* TO <gs_dyn_repdata>.
above logic creating dynamic field symbol table.... But I want create normal internal table.
Thanks,
Rajasekhar

Hi
What do you mean?
It needs to use the field-symbol, this is the price to pay if it wants a dynamic object
Max

Dynamic Work Area - fields

HI SDN COMMUNITY..!!
I HAVE TO USE THE WA_SEKPO-FIELDNAME DYNAMICALLY..
DATA: BEGIN OF WA_SEKPO,
 EBELN TYPE EBELN,
 BRTWR TYPE BRTWR,
 EFFWR TYPE EFFWR,
 MENGE TYPE MENGE,
 END OF WA_SEKPO.
DATA: SEKPO LIKE TABLE OF WA_SEKPO.
DATA: VAR_FNAME TYPE STRING.
FIELD-SYMBOLS: <FS> TYPE ANY.
STRUCTURE OF EDITPOS(INTERNAL TABLE)
|OBJECTID |TABNAME|FNAME | F_NEW | F_OLD
|4500016340 |EKPO |BRTWR | 26 | 11
|4500016340 |EKPO |EFFWR | 25 | 12
|4500016340 |EKPO |MENGE | 22 | 13
INTERNAL TABLE :
EDITPOS CONTAINS VALUES FOR : BRTWR
 EFFWR
 MENGE
IT MAY CONTAIN VALUES FOR MORE FIELDS.
NOW PROBLEM IS
I HAVE TO UPDATE MY INTERNAL TABLE : SEKPO
FOR FIELDNAMES : BRTWR
 EFFWR
 MENGE
BUT I DONT HAVE TO HARD CODE IT FOR EACH FIELD.
PLEASE CHECK, HOW THIS CAN BE ACHIVED?
WA_SEKPO-BRTWR = WA_EDITPOS-F_NEW.
PLEASE UPDATE THE CODE:
LOOP AT EDITPOS INTO WA_EDITPOS.
 ASSIGN WA_EDITPOS-FNAME TO <FS>.
 CONCATENATE 'WA_SEKPO-' <FS> INTO VAR_FNAME.
 WA_SEKPO-(<FS>) = WA_EDITPOS-F_NEW.
* MODIFY TABLE SEKPO FROM WA_SEKPO
* TRANSPORTING <FS>.
ENDLOOP.
HELP WILL BE APPRICIATED
THANKS IN ADVANCE
VIJAY RAHEJA

HI
STRUCTURE OF EDITPOS(INTERNAL TABLE)
|OBJECTID |TABNAME|FNAME | F_NEW | F_OLD
|4500016340 |EKPO |BRTWR | 26 | 11
|4500016340 |EKPO |EFFWR | 25 | 12
|4500016340 |EKPO |MENGE | 22 | 13
LOOP AT EDITPOS INTO WA_EDITPOS.
IF WA_EDITPOS = 'BRTWR'.
WA_SEKPO-BRTWR = WA_EDITPOS-F_NEW.
MODIFY TABLE SEKPO FROM WA_SEKPO
TRANSPORTING BRTWR.
ELSEIF WA_EDITPOS = 'EFFWR'.
WA_SEKPO-EFFWR = WA_EDITPOS-F_NEW.
MODIFY TABLE SEKPO FROM WA_SEKPO
TRANSPORTING EFFWR.
ELSEIF WA_EDITPOS = 'MENGE'.
WA_SEKPO-EFFWR = WA_EDITPOS-F_NEW.
MODIFY TABLE SEKPO FROM WA_SEKPO
TRANSPORTING MENGE.
ENDIF.
ENDLOOP.
I AM TRYING TO ACHIEVE THE ABOVE FUNCTIONALITY DYNAMICALLY,
AS I AM UNAWARE OF ENTRIES IN Internal Table: EDITPOS.
It contains values: BRTWR/EFFWR/MENGE
But it may contain more,SO i cannot straight away HARD code it for modifying entries in SEKPO.
for which i have written the code:
LOOP AT EDITPOS INTO WA_EDITPOS.
ASSIGN WA_EDITPOS-FNAME TO <FS>.
CONCATENATE 'WA_SEKPO-' <FS> INTO VAR_FNAME.
WA_SEKPO-<FS> = WA_EDITPOS-F_NEW.
MODIFY TABLE SEKPO FROM WA_SEKPO
TRANSPORTING <FS>.
ENDLOOP.
But there it shown Error before Activating the code: that <fs> is not a component of work area wa_sekpo
WA_SEKPO-<FS>
that is the problem,How to assign fieldname to a work area Dynamically.
Regards,
Vijay Raheja

Dynamic Work Area Field name Assignment.

hi Guru,
data: it_SFLIGHT type TABLE OF SFLIGHT,
 wa_SFLIGHT TYPE SFLIGHT,
 lv_field TYPE string.
lv_field = 'CARRID'. " Field name
 wa_SFLIGHT-<lv_field> = 'vivek'. " Assigning Value to workarea.
When i try this i am getting the error.
Regards.
Vivekananthan.S

Hi,
assign (p_tc_name) to <tc>.
TYPES:
BEGIN OF st_mytable,
 name1 TYPE string,
 name2 TYPE string,
 age TYPE i,
END OF st_mytable.
DATA:
gi_mytable TYPE STANDARD TABLE OF st_mytable,
g_mytable TYPE st_mytable.
* Define field symbols
FIELD-SYMBOLS:
<myfield1> TYPE ANY,
<myfield2> TYPE ANY,
<myfield3> TYPE ANY,
<myline> TYPE ANY.
* Fill table with data
g_mytable-name1 = 'John'.
g_mytable-name2 = 'Johnson'.
g_mytable-age = 25.
APPEND g_mytable TO gi_mytable.
g_mytable-name1 = 'Claudio'.
g_mytable-name2 = 'Jensen'.
g_mytable-age = 45.
APPEND g_mytable TO gi_mytable.
* The normal way to do it
LOOP AT gi_mytable INTO g_mytable.
WRITE: / g_mytable-name1, g_mytable-name2 ,g_mytable-age.
ENDLOOP.
SKIP 2.
* Do it with field symbols
LOOP AT gi_mytable ASSIGNING <myline>.
ASSIGN COMPONENT 1 OF STRUCTURE <myline> TO <myfield1>.
ASSIGN COMPONENT 2 OF STRUCTURE <myline> TO <myfield2>.
ASSIGN component 3 OF STRUCTURE <myline> TO <myfield3>.
WRITE: / <myfield1>,<myfield2>,<myfield3>.
ENDLOOP.
* Unassign field symbols
UNASSIGN <myfield1>.
UNASSIGN <myfield2>.
UNASSIGN <myfield3>.
UNASSIGN <myline>.
Regards,
Prabhudas

Dynamic internal tables using field symbols

Hello,
Is it possible to create a dynamic table where the no of fields in the internal table can be created dynamically(using field symbols).
Say sometimes internal tables with 10 fields and depending upon the requirement the fields can be dynamically increased or decreased in runtime.
Thanks.

Hi,
Go through the following code....
*Data definitions
*** Tables
data: lt_data type ref to data.
data: lt_fieldcatalog type lvc_t_fcat.
*** Structure
data: ls_fieldcatalog type lvc_s_fcat.
*** Data References
data: new_line type ref to data,
 fs_data type ref to data.
*** Field Symbols
field-symbols: <fs_data> type ref to data,
 <fs_1> type any table,
 <fs_2>,
 <fs_3>.
*Populating the internal table with fieldnames required for our dynamic
*internal table
ls_fieldcatalog-fieldname = 'MANDT'.
append ls_fieldcatalog to lt_fieldcatalog.
ls_fieldcatalog-fieldname = 'CARRID'. "Fieldname
ls_fieldcatalog-inttype = 'C'. "Internal Type C-> Character
append ls_fieldcatalog to lt_fieldcatalog.
ls_fieldcatalog-fieldname = 'CONNID'.
ls_fieldcatalog-inttype = 'N'.
append ls_fieldcatalog to lt_fieldcatalog.
ls_fieldcatalog-fieldname = 'FLDATE'.
ls_fieldcatalog-inttype = 'D'.
append ls_fieldcatalog to lt_fieldcatalog.
ls_fieldcatalog-fieldname = 'PRICE'.
ls_fieldcatalog-inttype = 'P'.
append ls_fieldcatalog to lt_fieldcatalog.
ls_fieldcatalog-fieldname = 'CURRENCY'.
ls_fieldcatalog-inttype = 'C'.
append ls_fieldcatalog to lt_fieldcatalog.
*Calling the method CREATE_DYNAMIC_TABLE
call method cl_alv_table_create=>create_dynamic_table
 exporting
 it_fieldcatalog = lt_fieldcatalog
 importing
 ep_table = fs_data
 exceptions
 generate_subpool_dir_full = 1
 others = 2
if sy-subrc <> 0.
endif.
*Assigning Field-Symbol to our dynamic internal table
assign lt_data to <fs_data>.
*Internal Table is ready, now to put data in that table
*** So <FS_1> now points to our dynamic internal table.
assign fs_data->* to <fs_1>.
*** Next step is to create a work area for our dynamic internal table.
create data new_line like line of <fs_1>.
*** A field-symbol to access that work area
assign new_line->* to <fs_2>.
*** And to put the data in the internal table
select
 mandt
 carrid
 connid
 fldate
 price
 currency
 from sflight
 into corresponding fields of table <fs_1>.
*** Access contents of internal table
loop at <fs_1> assigning <fs_2>.
do 5 times.
assign component sy-index of structure <fs_2> to <fs_3>.
write: <fs_3>.
enddo.
skip 1.
endloop.
top-of-page.
write:/5 'FUJITSU CONSULTING COMPANY' inverse color 6,
 50 sy-datum inverse color 6,
 70 sy-pagno inverse color 6.
uline.
<REMOVED BY MODERATOR>
Vijay C
Code Formatted by: Alvaro Tejada Galindo on Apr 14, 2008 1:47 PM

Basic query regarding work-area and select query

hi
dear sdn members,
thanks too all for solving all my query's up till now
i am stuck in a problem need help
1) why basically work-area has been used ? the sole purpose
2) different types of select query ? only coding examples
note: no links pls
regards,
virus

hi,
Work Area
Description for a data object that is particularly useful when working with internal tables or database tables as a source for changing operations or a target for reading operations.
WORKAREA is a structure that can hold only one record at a time. It is a collection of fields. We use workarea as we cannot directly read from a table. In order to interact with a table we need workarea. When a Select Statement is executed on a table then the first record is read and put into the header of the table and from there put into the header or the workarea(of the same structure as that of the table)of the internal table and then transferred top the body of the internal table or directly displayed from the workarea.
Each row in a table is a record and each column is a field.
While adding or retrieving records to / from internal table we have to keep the record temporarily.
The area where this record is kept is called as work area for the internal table. The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
.g.
data: begin of itab occurs 10,
ab type c,
cd type i,
end of itab. " this table will have the header line.
data: wa_itab like itab. " explicit work area for itab
data: itab1 like itab occurs 10. " table is without header line.
The header line is a field string with the same structure as a row of the body, but it can only hold a single row.
It is a buffer used to hold each record before it is added or each record as it is retrieved from the internal table. It is the default work area for the internal table.
With header line
SELECT.
Put the curson on that word and press F1 . You can see the whole documentation for select statements.
select statements :
SELECT result
FROM source
INTO|APPENDING target
[[FOR ALL ENTRIES IN itab] WHERE sql_cond]
Effect
SELECT is an Open-SQL-statement for reading data from one or several database tables into data objects.
The select statement reads a result set (whose structure is determined in result ) from the database tables specified in source, and assigns the data from the result set to the data objects specified in target. You can restrict the result set using the WHERE addition. The addition GROUP BY compresses several database rows into a single row of the result set. The addition HAVING restricts the compressed rows. The addition ORDER BY sorts the result set.
The data objects specified in target must match the result set result. This means that the result set is either assigned to the data objects in one step, or by row, or by packets of rows. In the second and third case, the SELECT statement opens a loop, which which must be closed using ENDSELECT. For every loop pass, the SELECT-statement assigns a row or a packet of rows to the data objects specified in target. If the last row was assigned or if the result set is empty, then SELECT branches to ENDSELECT . A database cursor is opened implicitly to process a SELECT-loop, and is closed again when the loop is ended. You can end the loop using the statements from section leave loops.
Up to the INTO resp. APPENDING addition, the entries in the SELECTstatement define which data should be read by the database in which form. This requirement is translated in the database interface for the database system´s programming interface and is then passed to the database system. The data are read in packets by the database and are transported to the application server by the database server. On the application server, the data are transferred to the ABAP program´s data objects in accordance with the data specified in the INTO and APPENDING additions.
System Fields
The SELECT statement sets the values of the system fields sy-subrc and sy-dbcnt.
sy-subrc Relevance
0 The SELECT statement sets sy-subrc to 0 for every pass by value to an ABAP data object. The ENDSELECT statement sets sy-subrc to 0 if at least one row was transferred in the SELECT loop.
4 The SELECT statement sets sy-subrc to 4 if the result set is empty, that is, if no data was found in the database.
8 The SELECT statement sets sy-subrc to 8 if the FOR UPDATE addition is used in result, without the primary key being specified fully after WHERE.
After every value that is transferred to an ABAP data object, the SELECT statement sets sy-dbcnt to the number of rows that were transferred. If the result set is empty, sy-dbcnt is set to 0.
Notes
Outside classes, you do not need to specify the target area with INTO or APPENDING if a single database table or a single view is specified statically after FROM, and a table work area dbtab was declared with the TABLES statement for the corresponding database table or view. In this case, the system supplements the SELECT-statement implicitly with the addition INTO dbtab.
Although the WHERE-condition is optional, you should always specify it for performance reasons, and the result set should not be restricted on the application server.
SELECT-loops can be nested. For performance reasons, you should check whether a join or a sub-query would be more effective.
Within a SELECT-loop you cannot execute any statements that lead to a database commit and consequently cause the corresponding database cursor to close.
SELECT - result
Syntax
... lines columns ... .
Effect
The data in result defines whether the resulting set consists of multiple rows (table-like structure) or a single row ( flat structure). It specifies the columns to be read and defines their names in the resulting set. Note that column names from the database table can be changed. For single columns, aggregate expressions can be used to specify aggregates. Identical rows in the resulting set can be excluded, and individual rows can be protected from parallel changes by another program.
The data in result consists of data for the rows lines and for the columns columns.
SELECT - lines
Syntax
... { SINGLE }
| { { } } ... .
Alternatives:
1. ... SINGLE
2. ... { }
Effect
The data in lines specifies that the resulting set has either multiple lines or a single line.
Alternative 1
... SINGLE
Effect
If SINGLE is specified, the resulting set has a single line. If the remaining additions to the SELECT command select more than one line from the database, the first line that is found is entered into the resulting set. The data objects specified after INTO may not be internal tables, and the APPENDING addition may not be used.
An exclusive lock can be set for this line using the FOR UPDATE addition when a single line is being read with SINGLE. The SELECT command is used in this case only if all primary key fields in logical expressions linked by AND are checked to make sure they are the same in the WHERE condition. Otherwise, the resulting set is empty and sy-subrc is set to 8. If the lock causes a deadlock, an exception occurs. If the FOR UPDATE addition is used, the SELECT command circumvents SAP buffering.
Note
When SINGLE is being specified, the lines to be read should be clearly specified in the WHERE condition, for the sake of efficiency. When the data is read from a database table, the system does this by specifying comparison values for the primary key.
Alternative 2
Effect
If SINGLE is not specified and if columns does not contain only aggregate expressions, the resulting set has multiple lines. All database lines that are selected by the remaining additions of the SELECT command are included in the resulting list. If the ORDER BY addition is not used, the order of the lines in the resulting list is not defined and, if the same SELECT command is executed multiple times, the order may be different each time. A data object specified after INTO can be an internal table and the APPENDING addition can be used. If no internal table is specified after INTO or APPENDING, the SELECT command triggers a loop that has to be closed using ENDSELECT.
If multiple lines are read without SINGLE, the DISTINCT addition can be used to exclude duplicate lines from the resulting list. If DISTINCT is used, the SELECT command circumvents SAP buffering. DISTINCT cannot be used in the following situations:
If a column specified in columns has the type STRING, RAWSTRING, LCHAR or LRAW
If the system tries to access pool or cluster tables and single columns are specified in columns.
Note
When specifying DISTINCT, note that you have to carry out sort operations in the database system for this.
SELECT - columns
Syntax
| { {col1|aggregate( col1 )}
{col2|aggregate( col2 )} ... }
| (column_syntax) ... .
Alternatives:
1. ... *
2. ... {col1|aggregate( col1 )}
{col2|aggregate( col2 )} ...
3. ... (column_syntax)
Effect
The input in columns determines which columns are used to build the resulting set.
Alternative 1
Effect
If * is specified, the resulting set is built based on all columns in the database tables or views specified after FROM, in the order given there. The columns in the resulting set take on the name and data type from the database tables or views. Only one data object can be specified after INTO.
Note
If multiple database tables are specified after FROM, you cannot prevent multiple columns from getting the same name when you specify *.
Alternative 2
... {col1|aggregate( col1 )}
{col2|aggregate( col2 )} ...
Effect
A list of column labels col1 col2 ... is specified in order to build the resulting list from individual columns. An individual column can be specified directly or as an argument of an aggregate function aggregate. The order in which the column labels are specified is up to you and defines the order of the columns in the resulting list. Only if a column of the type LCHAR or LRAW is listed does the corresponding length field also have to be specified directly before it. An individual column can be specified multiple times.
The addition AS can be used to define an alternative column name a1 a2 ... with a maximum of fourteen digits in the resulting set for every column label col1 col2 .... The system uses the alternative column name in the additions INTO|APPENDING CORRESPONDING FIELDS and ORDER BY. .
Column labels
The following column labels are possible:
If only a single database table or a single view is specified after FROM, the column labels in the database table - that is, the names of the components comp1 comp2... - can be specified directly for col1 col2 ... in the structure of the ABAP Dictionary.
If the name of the component occurs in multiple database tables of the FROM addition, but the desired database table or the view dbtab is only specified once after FROM, the names dbtab~comp1 dbtab~comp2 ... have to be specified for col1 col2 .... comp1 comp2 ... are the names of the components in the structure of the ABAP Dictionary.
If the desired database table or view occurs multiple times after FROM, the names tabalias~comp1 tabalias~comp2 ... have to be specified for col1 col2 .... tabalias is the alternative table name of the database table or view defined after FROM, and comp1 comp2 ... are the names of the components in the structure of the ABAP Dictionary.
The data type of a single column in the resulting list is the datatype of the corresponding component in the ABAP Dictionary. The corresponding data object after INTO or APPENDING has to be selected accordingly.
Note
If multiple database tables are specified after FROM, you can use alternative names when specifying single columns to avoid having multiple columns with the same name.
Example
Read specific columns of a single row.
DATA wa TYPE spfli.
SELECT SINGLE carrid connid cityfrom cityto
INTO CORRESPONDING FIELDS OF wa
FROM spfli
WHERE carrid EQ 'LH' AND connid EQ '0400'.
IF sy-subrc EQ 0.
WRITE: / wa-carrid, wa-connid, wa-cityfrom, wa-cityto.
ENDIF.
Alternative 3
... (column_syntax)
Effect
Instead of static data, a data object column_syntax in brackets can be specified, which, when the command is executed, either contains the syntax shown with the static data, or is initial. The data object column_syntax can be a character-type data object or an internal table with a character-type data type. The syntax in column_syntax, like in the ABAP editor, is not case-sensitive. When specifying an internal table, you can distribute the syntax over multiple rows.
If column_syntax is initial when the command is executed, columns is implicitly set to * and all columns are read.
If columns are specificied dynamically without the SINGLE addition, the resulting set is always regarded as having multiple rows.
Notes
Before Release 6.10, you could only specify an internal table with a flat character-type row type for column_syntax with a maximum of 72 characters. Also, before Release 6.10, if you used the DISTINCT addition for dynamic access to pool tables or cluster tables, this was ignored, but since release 6.10, this causes a known exception.
If column_syntax is an internal table with header line, the table body and not the header line is evaluated.
Example
Read out how many flights go to and from a city. The SELECT command is implemented only once in a sub-program. The column data, including aggregate function and the data after GROUP BY, is dynamic. Instead of adding the column data to an internal l_columns table, you could just as easily concatenate it in a character-type l_columns field.
PERFORM my_select USING `CITYFROM`.
ULINE.
PERFORM my_select USING `CITYTO`.
FORM my_select USING l_group TYPE string.
DATA: l_columns TYPE TABLE OF string,
l_container TYPE string,
l_count TYPE i.
APPEND l_group TO l_columns.
APPEND `count( * )` TO l_columns.
SELECT (l_columns)
FROM spfli
INTO (l_container, l_count)
GROUP BY (l_group).
WRITE: / l_count, l_container.
ENDSELECT.
ENDFORM.
SELECT - aggregate
Syntax
... { MAX( col )
| MIN( col )
| AVG( col )
| SUM( col )
| COUNT( DISTINCT col )
| COUNT( * )
| count(*) } ... .
Effect
As many of the specified column labels as you like can be listed in the SELECT command as arguments of the above aggregate expression. In aggregate expressions, a single value is calculated from the values of multiple rows in a column as follows (note that the addition DISTINCT excludes double values from the calculation):
MAX( col ) Determines the maximum value of the value in the column col in the resulting set or in the current group.
MIN( col ) Determines the minimum value of the content of the column col in the resulting set or in the current group.
AVG( col ) Determines the average value of the content of the column col in the resulting set or in the current group. The data type of the column has to be numerical.
SUM( col ) Determines the sum of the content of the column col in the resulting set or in the current group. The data type of the column has to be numerical.
COUNT( DISTINCT col ) Determines the number of different values in the column col in the resulting set or in the current group.
COUNT( * ) (or count(*)) Determines the number of rows in the resulting set or in the current group. No column label is specified in this case.
If you are using aggregate expressions, all column labels that are not listed as an argument of an aggregate function are listed after the addition GROUP BY. The aggregate functions evaluate the content of the groups defined by GROUP BY in the database system and transfer the result to the combined rows of the resulting set.
The data type of aggregate expressions with the function MAX, MIN or SUM is the data type of the corresponding column in the ABAP Dictionary. Aggregate expressions with the function AVG have the data type FLTP, and those with COUNT have the data type INT4. The corresponding data object after INTO or APPENDING has to be selected accordingly.
Note the following points when using aggregate expressions:
If the addition FOR ALL ENTRIES is used in front of WHERE, or if cluster or pool tables are listed after FROM, no other aggregate expressions apart from COUNT( * ) can be used.
Columns of the type STRING or RAWSTRING cannot be used with aggregate functions.
When aggregate expressions are used, the SELECT command makes it unnecessary to use SAP buffering.
Null values are not included in the calculation for the aggregate functions. The result is a null value only if all the rows in the column in question contain the null value.
If only aggregate expressions are used after SELECT, the results set has one row and the addition GROUP BY is not necessary. If a non-table type target area is specified after INTO, the command ENDSELECT cannot be used together with the addition SINGLE. If the aggregate expression count( * ) is not being used, an internal table can be specified after INTO, and the first row of this table is filled.
If aggregate functions are used without GROUP BY being specified at the same time, the resulting set also contains a row if no data is found in the database. If count( * ) is used, the column in question contains the value 0. The columns in the other aggregate functions contain initial values. This row is assigned to the data object specified after INTO, and unless count( * ) is being used exclusively, sy-subrc is set to 0 and sy-dbcnt is set to 1. If count( *) is used exclusively, the addition INTO can be omitted and if no data can be found in the database, sy-subrc is set to 4 and sy-dbcnt is set to 0.
if helpful reward points

Dynamic Work Area and field symbol

Similar Messages

Maybe you are looking for