Field Symbol that call input field

I learnt that I will need to use field symbol to call the values that is in my input field call (IO_INPUT). How am I suppose to call the valuein my input field? Codes example is appreciated

FIELD-SYMBOLS
Declares field symbols.
Syntax
FIELD-SYMBOLS <FS> [<type>|STRUCTURE <s> DEFAULT <wa>].
Field symbols are placeholders or symbolic names for other fields. Pointed brackets are part of the syntax for field symbol names. The <type> addition allows you to specify the type of a field symbol. The STRUCTURE addition forces a structured view of the data objects that you assign to the field symbol.
PLZ REWARD IF USEFUL.
PEGARDS,
PRIYA.

Similar Messages

ADF: Mandatory symbol for ReadOnly input fields

Hi All,
I am using JDeveloper 11.1.2 version. I am creating sample login window. In that there is Input Text filed called "old Password" which should be readOnly always [It will display oldPassword value]. When I ran my page in OldPassword field, mandatory symbol is not displaying. Eventhough I gave required="true" and showRequired="true" in jsff file, I am getting same output. The input Text is not ViewObject based. I am just binding ManagedBean variable value to that Input field to display oldPassword value.
Can u please help me out?
Regards,
Praveen.

This is the normal behavior, as a workaround you can surround the input text with af:panelLabelAndMessage and set its showRequired property to true.
<af:panelLabelAndMessage id="plam1" showRequired="true">
<af:inputText label="old Password" id="it1" readOnly="true" value="value"/>
</af:panelLabelAndMessage>

Field symbol to dynamic variable field naming

Hello all,
I am not used to field-symbols and I don't know if it's possible to do.
I need to create a node for a ALV Tree and the hierarchy changes 9 times. So, instead of create 9 loops I want to create a Perform and use the field as parameter.
case 'X'.
     when s1.
       perform tree_nodes_s1 using 'BEZEI' 'NAME1' 'VTEXT'.
     when s2.
       perform tree_nodes_s2 using 'BEZEI' 'VTEXT' ''.
In the Form
loop at it_data into wa_data.
     if l_field1 is not initial.
       on change of field.
         perform add_carrid_line using wa_data   ''
                                 changing l_carrid_key.
       endon.
     endif.
So, the field need to be wa_data-bezei or wa_data-name1 or wa_data-vtext etc.
I guess that I saw it on SAP code but I really don't know how to reproduce it.
Thanks,
Andréa

Hi Roland Spindler
I did that before and I thought that it was wrong because I got this same error message:
The field "<L_FIELD1>" specified under LIKE either has no type or a generic type. type.
Code
   field-symbols: <l_field1> type any.
   assign component param1 of structure wa_data to <l_field1>.
   check sy-subrc = 0.
     loop at it_data into wa_data.
     if <l_field1> is not initial.
       on change of <l_field1>.
         perform add_carrid_line using wa_data   ''
                                 changing l_carrid_key.
       endon.
     endif.
Not sure if I can use it on 'on change of'.
do you know the right type to declare?
Thanks,
Andrea

Field name retrieval from field symbols after assigning to field in a struc

We have an internal table of about 100 columns. First 7 of them have key values and other fields are data fields. Out of remaining 93 fields, any 2 to 3 fields have data stored in it in each record. Using field symbols in a loop (93 fixed iterations), we are identifying which fields has a data in it. Once we identify the field, how do we retrieve the name of the field / column of the table. We are performing further processing based on name of the field.
Any ideas how to get the name of the column assigned to field symbols?
sample raw code piece is as below:
clear n.
Do 93 times.
n = n + 1.
assign component n of structure itab to <fs>.
if not <fs> is initial.
Get name of the field in cfname.
perform process_record using cfname.
endif.
enddo.
Thanks.
Regards.

Hi,
Try this..use the function module GET_COMPONENT_LIST to get the fields of the internal table and store it in an internal table ITAB_COMP..
Then use READ TABLE ITAB_COMP INDEX sy-index..
You can get the field name from the work area..
Thanks,
Naren

Bringing two input fields under one long input field

HI
I have a input field (which is for description 40 chars long).
in my next row.. i have data and time.. i want this data and time input fields to be exactly under the description input field.
I am using Matrix layout... can u tell me how to acheive this. pls..
right now.. i see there is a gap between the data lable and data input field... so its not coming under the input field of description.
thanks
Niraja

make changes in properties as matrix header data.( it come as new line)
matrix data it will come as flow layout, one after one.
Hope this helps you.
Regards,
sarath

Auto population of data to fields based on other input field.

In overview screen, I have one input field "Business Partner" which contain search help. As soon as business partner selected from dropdown, the other input fields like Name, Address, City, state should automatically populated without hit of 'ENTER' key.
I verified with method DO_PREPARE_OUTPUT, but it is triggering only by hitting ENTER key. Is there any event or method which will trigger after business partner selected from dropdown? or any other option to achieve to auto populate the fields.
Please find attached screen.
Thanks in advance.

Hi Narayana,
You can use the get p method for setting up the values without pressing the enter.
CASE iv_property.
    WHEN if_bsp_wd_model_setter_getter=>fp_fieldtype.
      rv_value = cl_bsp_dlc_view_descriptor=>field_type_picklist.
    WHEN if_bsp_wd_model_setter_getter=>fp_server_event.
      rv_value = 'AI_SELECT'.( you can give here the event name)
    WHEN OTHERS.
ENDCASE.
Define event with the same name above( AI_SELECT),
You can set the value of fields based on the first field value within this event.
Thanks,
Dharmakasi.

RUn time error while saving po    Field symbol has not yet been assigned.

Hi Experts,
I am getting abap dump while saving PO in ME21N plz seee the below dump plzzzzzzzzzzzzzzzzzzzzz help me
Runtime Errors         GETWA_NOT_ASSIGNED
Date and Time          19.06.2009 11:24:46
Short dump has not been completely stored (too big)
Short text
     Field symbol has not yet been assigned.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLKKBL" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
     You attempted to access an unassigned field symbol
     (data segment 106).
     This error may occur if
     - You address a typed field symbol before it has been set with
       ASSIGN
     - You address a field symbol that pointed to the line of an
       internal table that was deleted
    - You address a field symbol that was previously reset using
      UNASSIGN or that pointed to a local field that no
      longer exists
    - You address a global function interface, although the
      respective function module is not active - that is, is
      not in the list of active calls. The list of active calls
      can be taken from this short dump.
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "GETWA_NOT_ASSIGNED" " "
    "SAPLKKBL" or "LKKBLF99"
    "GEN_FIELD_OUT2"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
   In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
em environment
SAP-Release 700
Application server... "gplqty"
Network address...... "128.12.0.19"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "8x AMD64 Level"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "GPLQTY"
Database type..... "MSSQL"
Database name..... "GPQ"
Database user ID.. "gpq"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Aug 4 2008 02:33:25"
create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"
Database version. "SQL_Server_8.00 "
Patch level. 172
Patch text.. " "
Database............. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
   NT 6.0"
Memory consumption
Roll.... 16192
EM...... 16759360
Heap.... 0
Page.... 237568
MM Used. 12036016
MM Free. 530432
er and Transaction
Client.............. 410
User................ "SAP_SUPPORT"
Language key........ "E"
Transaction......... "ME21N "
Transactions ID..... "9E955CDE97CBF1648B4C001A64C7B85A"
Program............. "SAPLKKBL"
Screen.............. "SAPLKKBL 0500"
Screen line......... 3
Information on where terminated
    Termination occurred in the ABAP program "SAPLKKBL" - in "GEN_FIELD_OUT2".
    The main program was "RM_MEPO_GUI ".
    In the source code you have the termination point in line 2908
    of the (Include) program "LKKBLF99".
Source Code Extract
Line SourceCde
2878       else.
2879         assign <fs11> to <field>.
2880         gs_fc = gs_sfc11.
2881       endif.
2882     when 012.
2883       if gs_out_flags-slave ne 'X'.
2884         assign <fm12> to <field>.
2885         gs_fc = gs_mfc12.
2886       else.
2887         assign <fs12> to <field>.
2888         gs_fc = gs_sfc12.
2889       endif.
2890     when 013.
2891       if gs_out_flags-slave ne 'X'.
2892         assign <fm13> to <field>.
2893         gs_fc = gs_mfc13.
2894       else.
2895         assign <fs13> to <field>.
2896         gs_fc = gs_sfc13.
2897       endif.
2898     when 014.
2899       if gs_out_flags-slave ne 'X'.

Hi,
this error occurs when you try to address a field-symbol before it has been assigned to a field or
the assignment has failed.
Use following code to remove this dump
Assign <mara-matnr> to <fs>.
if sy-subrc <> 0.
Error Message.
Endif.
Hope it helps,
Raj

Regarding error "Field symbol is not assigned." during print preview

Hi experts,
    I am getting dump while trying print preview for particular POs in ME23n transaction(ECC 6.0). Please refer the below dump error:
Runtime Errors         GETWA_NOT_ASSIGNED_RANGE
Date and Time          29.09.2009 19:30:39
Short dump has not been completely stored (too big)
Short text
     Field symbol is not assigned.
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLSTXC" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
     A field symbol that was not assigned was accessed
     (data segment no. 32769).
    The field symbol is no longer assigned because there was an attempt
    makde previously in a Unicode program to set the field symbol using
    ASSIGN with offset and/or length specification. Here, the memory
    addressed by the offset/length specification was not within the
    allowed area.
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "GETWA_NOT_ASSIGNED_RANGE" " "
    "SAPLSTXC" or "LSTXCFFT"
    "FT_COMPOSE"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
   2. Corresponding system log
      Display the system log by calling transaction SM21.
      Restrict the time interval to 10 minutes before and five minutes
   after the short dump. Then choose "System->List->Save->Local File
   (Unconverted)".
   3. If the problem occurs in a problem of your own or a modified SAP
   program: The source code of the program
      In the editor, choose "Utilities->More
   Utilities->Upload/Download->Download".
   4. Details about the conditions under which the error occurred or which
   actions and input led to the error.
I am getting this dump only for few POs.. Rest of the POs are able to print. I am not able to find notes for this issue. Is there any SAP notes available for that or Is there any configuration issue related to this?
Please provide solution for thsi as soon as possible.
Thanks and Regards
Subbu

A field symbol is not assigned, but thats what the dump is telling you. Mostly this happens, when fields or function modules are stored by name, like the fieldnames in the fieldcatalog in an ALV report. It a field referenced in such a way does not exist you will get this error. Always store fieldnames and function names in capital letters and check mistyping of 1L 8B and so on.

Dynamic select with field symbols

Hi guys,
I have 2 tables.
First table is the popup fields using fm popup_get_values:
tab1-tabname
tab1-fieldname
tab1-value
Second table is the input fields to be displayed in the popup box:
tab2-transactno
tab2-docno
tab2-customer
tab2-postdate
etc... (it has many fields)
Let's say currently i loop at tab2 and assign each value of the individual fields to a variable each:
loop at tab2
v_transactno = tab2-transactno
v_docno = tab2-docno
etc...
endloop.
My question is how do i assign each variable to the popup fields according to the fieldname so that it can get its corresponding value correctly?
How can this be done dynamically?
Can the loop above be done dynamically as well coz it has alot of fields to cater for?
Please help me solve this problem. Futher similar examples would be much appreciated as well.
Thank you very much!

Hi
see the concept of field sysmbols and do accordingly
Field Symbols
Field symbols are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field symbols are similar to dereferenced pointers in C (that is, pointers to which the content operator * is applied). However, the only real equivalent of pointers in ABAP, that is, variables that contain a memory address (reference) and that can be used without the contents operator, are reference variables in ABAP Objects.
All operations programmed with field symbols are applied to the field assigned to it. For example, a MOVE statement between two field symbols moves the contents of the field assigned to the first field symbol to the field assigned to the second field symbol. The field symbols themselves point to the same fields after the MOVE statement as they did before.
You can create field symbols either without or with type specifications. If you do not specify a type, the field symbol inherits all of the technical attributes of the field assigned to it. If you do specify a type, the system checks the compatibility of the field symbol and the field you are assigning to it during the ASSIGN statement.
Field symbols provide greater flexibility when you address data objects:
If you want to process sections of fields, you can specify the offset and length of the field dynamically.
You can assign one field symbol to another, which allows you to address parts of fields.
Assignments to field symbols may extend beyond field boundaries. This allows you to address regular sequences of fields in memory efficiently.
You can also force a field symbol to take different technical attributes from those of the field assigned to it.
The flexibility of field symbols provides elegant solutions to certain problems. On the other hand, it does mean that errors can easily occur. Since fields are not assigned to field symbols until runtime, the effectiveness of syntax and security checks is very limited for operations involving field symbols. This can lead to runtime errors or incorrect data assignments.
While runtime errors indicate an obvious problem, incorrect data assignments are dangerous because they can be very difficult to detect. For this reason, you should only use field symbols if you cannot achieve the same result using other ABAP statements.
For example, you may want to process part of a string where the offset and length depend on the contents of the field. You could use field symbols in this case. However, since the MOVE statement also supports variable offset and length specifications, you should use it instead. The MOVE statement (with your own auxiliary variables if required) is much safer than using field symbols, since it cannot address memory beyond the boundary of a field. However, field symbols may improve performance in some cases.
check the below links u will get the answers for your questions
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/content.htm
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/field_sy.htm
http://searchsap.techtarget.com/tip/1,289483,sid21_gci920484,00.html
Syntax Diagram
FIELD-SYMBOLS
Basic form
FIELD-SYMBOLS <fs>.
Extras:
1. ... TYPE type
2. ... TYPE REF TO cif
3. ... TYPE REF TO DATA
4. ... TYPE LINE OF type
5. ... LIKE s
6. ... LIKE LINE OF s
7. ... TYPE tabkind
8. ... STRUCTURE s DEFAULT wa
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Untyped Field Symbols ad Cannot Use Field Symbols as Components of Classes.
Effect
This statement declares a symbolic field called <fs>. At runtime, you can assign a concrete field to the field symbol using ASSIGN. All operations performed with the field symbol then directly affect the field assigned to it.
You can only use one of the additions.
Example
Output aircraft type from the table SFLIGHT using a field symbol:
FIELD-SYMBOLS <PT> TYPE ANY.
DATA SFLIGHT_WA TYPE SFLIGHT.
ASSIGN SFLIGHT_WA-PLANETYPE TO <PT>.
WRITE <PT>.
Addition 1
... TYPE type
Addition 2
... TYPE REF TO cif
Addition 3
... TYPE REF TO DATA
Addition 4
... TYPE LINE OF type
Addition 5
... LIKE s
Addition 6
... LIKE LINE OF s
Addition 7
... TYPE tabkind
Effect
You can define the type of the field symbol using additions 2 to 7 (just as you can for FORM parameters (compare Defining the Type of Subroutine Parameters). When you use the ASSIGN statement, the system carries out the same type checks as for USING parameters of FORMs.
This addition is not allowed in an ABAP Objects context. See Cannot Use Obsolete Casting for FIELD SYMBOLS.
In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. See Defining Types Using STRUCTURE.
Effect
Assigns any (internal) field string or structure to the field symbol from the ABAP Dictionary (s). All fields of the structure can be addressed by name: <fs>-fieldname. The structured field symbol points initially to the work area wa specified after DEFAULT.
The work area wa must be at least as long as the structure s. If s contains fields of the type I or F, wa should have the structure s or at least begin in that way, since otherwise alignment problems may occur.
Example
Address components of the flight bookings table SBOOK using a field symbol:
DATA SBOOK_WA LIKE SBOOK.
FIELD-SYMBOLS <SB> STRUCTURE SBOOK
DEFAULT SBOOK_WA.
WRITE: <SB>-BOOKID, <SB>-FLDATE.
Regards
Anji

Field symbol has not yet been assigned. ???

Dear Experts ,
W hen i tried to execute my program this error appears :
Short text
    Field symbol has not yet been assigned.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSLVC" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    You attempted to access an unassigned field symbol
    (data segment 32821).
    This error may occur if
    - You address a typed field symbol before it has been set with
      ASSIGN
    - You address a field symbol that pointed to the line of an
      internal table that was deleted
    - You address a field symbol that was previously reset using
      UNASSIGN or that pointed to a local field that no
      longer exists
    - You address a global function interface, although the
      respective function module is not active - that is, is
      not in the list of active calls. The list of active calls
      can be taken from this short dump.
and Here is my CODE :
*& Report ZPO
Report ZPO1.
type-pools slis.
PARAMETERS : PO_Doc like EKBE-EBELN DEFAULT '4800000007'.
PARAMETERS : Plant TYPE WERKS DEFAULT '1000'.
PARAMETERS : PO_ORG TYPE EKORG DEFAULT ''.
data TtlS type mara-wesch .
data TtlH type mara-wesch .
data Ttl type mara-wesch .
data ZEKBE type TABLE OF EKBE.
data ZEKBER type EKBE.
data ZEKPO type TABLE OF EKPO.
data ZEKPOR type EKPO.
data ZEKKOR TYPE EKKO.
data ZNAME1F type LFA1-LIFNR.
data ZWGBEZF TYPE T023T-WGBEZ.
data i type n.
data counter type n.
types : begin of SBAGDS,
Serial Type n, "Purchase Order
EBELN like EKKO-EBELN, "Purchase Order
MATNR like EKPO-MATNR, "Material
TXZ01 like EKPO-TXZ01, "Short Text
MATKL like EKPO-MATKL, "Material Group
WGBEZ like T023T-WGBEZ, "Material Group Desc"
SUBMI like EKKO-SUBMI, "GPM
CHARG like EKBE-CHARG, "Batch
LIFNR like EKKO-LIFNR, "Vendor
NAME1 like LFA1-NAME1, "Vendor Name
RECV like mara-wesch, "Received Quantity
REVR like mara-wesch, "Reversed Quantity
DELV like mara-wesch, "Delivered Quantity
end of SBAGDS .
DATA : BAGDS TYPE SBAGDS OCCURS 0 WITH HEADER LINE.
data Struc like BAGDS.
data: gr_table like BAGDS OCCURS 0 WITH HEADER LINE.
data: gt_fieldcat type slis_t_fieldcat_alv, gt_outtab type SBAGDS occurs 0 with header line.
INITIALIZATION.
i = 0.
counter = 0 .
perform field_cat_init using gt_fieldcat[].
FORM field_cat_init using rt_fieldcat type slis_t_fieldcat_alv.
data: ls_fieldcat type slis_fieldcat_alv,
         pos type i value 1.
clear LS_FIELDCAT.
*Column 1
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'Serial'.
ls_fieldcat-SELTEXT_L      = 'Serial'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 2
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'EBELN'.
ls_fieldcat-SELTEXT_L      = 'Purchase Order'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 3
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'MATNR'.
ls_fieldcat-SELTEXT_L      = 'Material'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 4
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'TXZ01'.
ls_fieldcat-SELTEXT_L      = 'Short Text'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 5
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'MATKL'.
ls_fieldcat-SELTEXT_L      = 'Material Group'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 6
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'WGBEZ'.
ls_fieldcat-SELTEXT_L      = 'Material Group Desc'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 7
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'SUBMI'.
ls_fieldcat-SELTEXT_L      = 'GPM'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 8
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'CHARG'.
ls_fieldcat-SELTEXT_L      = 'Batch'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 9
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'LIFNR'.
ls_fieldcat-SELTEXT_L      = 'Vendor'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 10
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'NAME1'.
ls_fieldcat-SELTEXT_L      = 'Vendor Name'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 11
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'RECV'.
ls_fieldcat-SELTEXT_L      = 'Received Quantity'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 12
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'REVR'.
ls_fieldcat-SELTEXT_L      = 'Reversed Quantity'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
*Column 13
ls_fieldcat-col_pos           = pos.
ls_fieldcat-fieldname        = 'DELV'.
ls_fieldcat-SELTEXT_L      = 'Delivered Quantity'.
ls_fieldcat-DDICTXT          = 'L'.
append ls_fieldcat to rt_fieldcat.
clear ls_fieldcat.
pos = pos + 1.
endform.
START-OF-SELECTION.
       select SINGLE * from EKKO into ZEKKOR where EBELN = PO_DOC.
       select SINGLE * from EKPO into ZEKPOR where EBELN = PO_DOC.
       select SINGLE NAME1 from LFA1 into ZNAME1F where LIFNR = ZEKKOR-LIFNR.
*         ' Buliding Structure
          Struc-EBELN = ZEKPOR-EBELN.
          Struc-SUBMI = ZEKKOR-SUBMI.
          Struc-LIFNR = ZEKKOR-LIFNR.
          Struc-Name1 = ZNAME1F.
       select * from EKPO into TABLE ZEKPO where EBELN = PO_Doc and WERKS = plant.
       LOOP at ZEKPO into ZEKPOR.
           select SINGLE WGBEZ from T023T into ZWGBEZF WHERE MATKL = ZEKPOR-MATKL .
           counter = counter + 1.
*         ' Buliding Structure
          Struc-Serial = counter.
          Struc-MATNR = ZEKPOR-MATNR.
          Struc-TXZ01 = ZEKPOR-TXZ01.
          Struc-MATKL = ZEKPOR-MATKL.
          Struc-WGBEZ = ZWGBEZF.
*          Calcualting Debit transactions from PO History
           select * from EKBE into table ZEKBE where EBELN = PO_Doc and MATNR = ZEKPOR-MATNR and EBELP = ZEKPOR-EBELP and BWART NOT LIKE '' and SHKZG = 'S'.
           LOOP AT ZEKBE INTO ZEKBER.
               TtlS = TtlS + ZEKBER-MENGE.
           ENDLOOP.
*          ' Buliding Structure
           Struc-CHARG = ZEKBER-CHARG.
           Struc-RECV = TtlS.
           Ttl = TtlS.
           clear TtlS.
*         Calcualting Credit transactions from PO History
         select * from EKBE into table ZEKBE where EBELN = PO_Doc and MATNR = ZEKPOR-MATNR and EBELP = ZEKPOR-EBELP and BWART NOT LIKE '' and SHKZG = 'H'.
           LOOP AT ZEKBE INTO ZEKBER.
               TtlH = TtlH + ZEKBER-MENGE.
           ENDLOOP.
*          ' Buliding Structure
           Struc-REVR = TtlH.
*          Calculating Total Delivered
           Ttl = Ttl - TtlH.
           clear TtlH.
*          ' Buliding Structure
           Struc-DELV = Ttl.
           clear Ttl.
*      Writtng ITAB
       APPEND Struc to BAGDS.
       ENDLOOP.
*      Reading ITAB
*       WRITE : / , 'ITAB Begin : '    .
*       loop at BAGDS into Struc.
*         counter = counter + 1.
*         write : /,'Serial : ',counter.
*         write : / ,'PO : ',Struc-EBELN.
*         write : / ,'Vendor : ',Struc-LIFNR.
*         write : / ,'Vendor Name : ',Struc-NAME1.
*         write : / ,'Material : ',Struc-MATNR.
*         write : /,'Short Text: ',Struc-TXZ01.
*         write : / ,'Model : ',Struc-MATKL.
*         write : / ,'Model Desc : ',Struc-WGBEZ.
*         write : /,'GPM : ',Struc-SUBMI.
*         write : /,'Lot : ',Struc-CHARG.
*         write : /,'Received : ',Struc-RECV.
*         write : /,'Reversed : ',Struc-REVR.
*         write : /,'Delivered : ',Struc-DELV,/,/,/.
*       ENDLOOP.
* Call ALV Grid Viewer
*BREAK-POINT.
gr_Table[] = BAGDS[].
   CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
        EXPORTING
             I_STRUCTURE_NAME   = 'SBAGDS'
             IT_FIELDCAT          = gt_fieldcat[]
        TABLES
             T_OUTTAB                  = gr_Table.
Please Advise
Edited by: Sap Sap on Jul 27, 2009 12:18 PM
Edited by: Sap Sap on Jul 27, 2009 12:22 PM
Edited by: Sap Sap on Jul 27, 2009 12:22 PM

Hi,
The problem seems to be in your ALV grid display.
The reason must be your field catalog.
Just check your fieldcatalog.
The value in the fieldname field of the fieldcatalog should be same as the fieldname in your internal table and should be in capital letters.
Probably you must have mistyped some field.
Kinldy check.
Regards,
Ankur Parab

The difference between FIELD-SYMBOL and normal DATA TYPE

Dear experts,
Please see the example below, both are output the same result.
DATA: EXTERNAL_RECORD(4000),
      POSITION TYPE I,
      LENGTH TYPE N,
      ENTRY TYPE STRING.
EXTERNAL_RECORD = '0005Smith0007Edwards0005Young'.
DO.
LENGTH = EXTERNAL_RECORD+POSITION(4).
IF LENGTH = 0.
    EXIT.
ENDIF.
ADD 4 TO POSITION.
MOVE EXTERNAL_RECORD+POSITION(LENGTH) TO ENTRY.
WRITE ENTRY.
ADD LENGTH TO POSITION.
IF POSITION >= 4000.
    EXIT.
ENDIF.
ENDDO.
--OR It can be written as--
DATA: EXTERNAL_RECORD(4000),
      POSITION TYPE I,
      LENGTH TYPE N.
FIELD-SYMBOLS <ENTRY>.
EXTERNAL_RECORD = '0005Smith0007Edwards0005Young'.
DO.
LENGTH = EXTERNAL_RECORD+POSITION(4).
IF LENGTH = 0.
    EXIT.
ENDIF.
ADD 4 TO POSITION.
ASSIGN EXTERNAL_RECORD+POSITION(LENGTH) TO <ENTRY>.
WRITE <ENTRY>.
ADD LENGTH TO POSITION.
IF POSITION >= 4000.
    EXIT.
ENDIF.
ENDDO.
Is there any special circumstances we need to use FIELD-SYMBOL?
Why is FIELD-SYMBOL is introduce in the first place?
Kindly advice with example.
Thanks in advance for those who can help me on this.

HI,
You can use field symbols to make the program more dynamic. In this example the name of a table control is substituted by a field symbol. Thus you cal call the form with any internal table, using the name of the table control as a parameter.
Example
form insert_row
using p_tc_name.
field-symbols <tc> type cxtab_control. "Table control
assign (p_tc_name) to <tc>.
insert 100 lines in table control
<tc>-lines = 100.
Field symbols allow you to:
**     Assign an alias to a data object(for example, a shortened
        name for data objects structured through several hierarchies
        - <fs>-f instead of rec1-rec2-rec3-f)
**     Set the offset and length for a string variably at runtime
**     Set a pointer to a data object that you determine at runtime (dynamic ASSIGN)
**     Adopt or change the type of a field dynamically at runtime
**     Access components of a structure
**     (from Release 4.5A) Point to lines of an internal table
        (process internal tables without a separate work area)
Field symbols in ABAP are similar to pointers in other programming
languages. However, pointers (as used in PASCAL or C) differ from ABAP
field symbols in their reference syntax.
The statement ASSIGN f to <fs> assigns the field f to field
symbol <fs>. The field symbol <fs> then "points" to the
contents of field f at runtime. This means that all changes to the
contents of f are visible in <fs> and vice versa. You declare
the field symbol <fs> using the statement FIELD-SYMBOLS: <fs>.
Reference syntax
Programming languages such as PASCAL and C use a dereferencing symbol
to indicate the difference between a reference and the object to which
it refers; so PASCAL would use p^ for a pointer instead of p, C would
use *p instead of p. ABAP does not have any such dereferencing symbol.
**     In PASCAL or C, if you assign a pointer p1 to a pointer p2,
you force p1 to point to the object to which p2 refers (reference semantics).
**     In ABAP, if you assign a field symbol <fs1> to a field
symbol <fs2>, <fs1> takes the value of the data object to
which <fs2> refers (value semantics).
**     Field symbols in ABAP are always dereferenced, that is,
they always access the referenced data object. If you want to
change the reference yourself in ABAP, you can use the ASSIGN statement
to assign field symbol <fs1> to field symbol <fs2>.
Using field symbols
You declare field symbols using the FIELD-SYMBOLS statement.
They may be declared either with or without a specific type.
At runtime you assign a field to the field symbol using the ASSIGN
statement. All of the operations on the field symbol act on the field
assigned to it.
When you assign a field to an untyped field symbol, the field symbol
adopts the type of the field. If, on the other hand, you want to assign
a field to a typed field symbol, the type of the field and that of the
field symbol must be compatible.
A field symbol can point to any data object and from Release 4.5A,
they can also point to lines of internal tables.
The brackets (<>) are part of the syntax.
Use the expression <fs> IS ASSIGNED to find out whether the field
symbol <fs> is assigned to a field.
The statement UNASSIGN <fs> sets the field symbol <fs> so
that it points to nothing. The logical expression <fs>
IS ASSIGNED is then false. The corresponding negative expression
is IF NOT <fs> IS ASSIGNED.
An unassigned field symbol <fs> behaves as a constant with
type C(1) and initial value SPACE.
MOVE <fs>
TO dest     Transfers the initial value SPACE to the variable dest
MOVE 'A' to <fs>
Not possible, since <fs> is a constant
(runtime error).
To lift a type restriction, use the CASTING addition in the
ASSIGN statement. The data object is then interpreted as though
it had the data type of the field symbol. You can also do this
with untyped field symbols using the CASTING TYPE <type> addition.
The danger with pointers is that they may point to invalid areas.
This danger is not so acute in ABAP, because the language does not
use address arithmetic (for example, in other languages, pointer p
might point to address 1024. After the statement p = p + 10, it would
point to the address 1034). However, the danger does still exist, and
memory protection violations lead to runtime errors.
A pointer in ABAP may not point beyond a segment boundary. ABAP does
not have one large address space, but rather a set of segments.
Each of the following has its own segment:
*     All global data
*     All local data
*     Each table work area (TABLES)
*     Each COMMON PART
You should only let field symbols move within an elementary field or
structure where ABAP allows you to assign both within the global data
and beyond a field boundary.
Rgds
Umakanth

Field Symbols in Download to excel FM

Hi All,
I am trying to use something like below.
field-symbols : <gt_outtab> type any.
Here <gt_outtab> is a dynamic internal table.
It gives me an error message saying ""
i might be asking very silly question but am not able to find a solution.
Is the below code wrong...then is there any FM which supports usage of field symbols in FM to download data with field names.
another thing...is there any way to read the Component names in a field symbol...I am able to read the contents of the same using Assign component though.
CALL FUNCTION 'GUI_DOWNLOAD'
       EXPORTING
            filename   = 'C:\test1.xls'
            filetype   = 'ASC'
            append     = 'X'
       TABLES
            data_tab   = <gt_outtab>
            fieldnames = gt_fieldcat.
Any help is appreciated.
BR,
Krishna.

Hi Max,
thanks for that...I did get the structure and was able to create a Dynamic table using the Field catalog fieldnames.
Now I have all my values in <gt_outtab> table and the dynamic table created from the field catalog is <gt_fieldcat> .
DATA: it_create    TYPE REF TO cl_alv_table_create,
        it_dinamica     TYPE REF TO data,
        it_fieldcat_lvc TYPE lvc_t_fcat.
CALL METHOD it_create->create_dynamic_table(
              EXPORTING it_fieldcatalog = gt_save_fieldcat
          IMPORTING ep_table                = it_dinamica ).
ASSIGN it_dinamica->* TO <fs_dinamica>.
All I want is to Move corresponding from one fieldsymbol to another.
something like      move-corresponding <gt_outtab> to <gt_fieldcat> . But it gives me an error saying its not a structure etc.
I tried another way as well.
loop at <gt_outtab> assigning <gs_outtab>.
ASSIGN COMPONENT   MY_STRUCT->COMPONENTS-NAME
OF STRUCTURE <gs_outtab> TO <fs1>.
All I have now is a fieldcatalog..a table with all values...
Move corresponding doesn't work as it says this is not a structure or an internal table.
as this is not a static structure that I am referring to it doesnt allow me to do this.
I think there is no concept of type casting a Field Symbol like another field symbol at runtime.
like : field-symbols : <fs>, <fs1> , <fs2> type itab1.
assign <fs2> to <fs> casting. which then transforms <fs2> to structure <fs>.
for e.g :
<gt_fieldcat> :
orderno itemno adsize date price
<gt_outtab> has below values
orderno itemno price   date               adsize
400         10       200   10.10.2010        45
500         20       150   11.09.2010        55
All i need is the same field catalog and the rows in as per the fields in the <gt_fieldcat>.
When there is something gt_sp_groups while passing into the below method, the fieldcat and the output table are in same structure but after this method if I try to read the current Field catalog using method " get_frontend_fieldcatalog" ...it gives me a different one after applying the Groups etc.,in such cases I think the ALV excel download doesnt work. I tried checking SAP Notes for the same, but could not find anything. It will be helpful if I can get any notes related to that.
e.g.
CALL METHOD gr_alvgrid->set_table_for_first_display
EXPORTING
    is_layout                     = gs_layout
    it_special_groups             = gt_sp_groups
    it_toolbar_excluding          = gt_exclude .
Any one any ideas please....at the moment the only way i am trying is forcing all the fields as characters into the Excel which obvisouly limits if it is a Price columns.
Many thanks,
Krishna.
Edited by: Krishna on Nov 11, 2010 2:24 AM
Edited by: Krishna on Nov 11, 2010 5:56 PM

How to use field symbol in select

Hi,
    CONCATENATE 'WTG0' LV_MON INTO LV_FNAME.
    ASSIGN (LV_FNAME) TO <FS>.
    SELECT SINGLE <FS> FROM COSP INTO LV_SAPRST
         WHERE OBJNR = LV_OBJ AND GJAHR = LV_YEAR AND WRTTP = '4' AND KSTAR = GT_INOUT-SAKNR
   Error message :    Unknown column name "<FS>" . field list. . field list. field list.
   actually , if i use if command, i can do, but i want to use simple code by fieldsymbol.
   is it possible in select command?
Thanks in advance
Benjamin

Hi
Hope it will help you.
reward if help.
Field Symbols
Field symbols are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field symbols are similar to dereferenced pointers in C (that is, pointers to which the content operator * is applied). However, the only real equivalent of pointers in ABAP, that is, variables that contain a memory address (reference) and that can be used without the contents operator, are reference variables in ABAP Objects.
All operations programmed with field symbols are applied to the field assigned to it. For example, a MOVE statement between two field symbols moves the contents of the field assigned to the first field symbol to the field assigned to the second field symbol. The field symbols themselves point to the same fields after the MOVE statement as they did before.
You can create field symbols either without or with type specifications. If you do not specify a type, the field symbol inherits all of the technical attributes of the field assigned to it. If you do specify a type, the system checks the compatibility of the field symbol and the field you are assigning to it during the ASSIGN statement.
Field symbols provide greater flexibility when you address data objects:
If you want to process sections of fields, you can specify the offset and length of the field dynamically.
You can assign one field symbol to another, which allows you to address parts of fields.
Assignments to field symbols may extend beyond field boundaries. This allows you to address regular sequences of fields in memory efficiently.
You can also force a field symbol to take different technical attributes from those of the field assigned to it.
The flexibility of field symbols provides elegant solutions to certain problems. On the other hand, it does mean that errors can easily occur. Since fields are not assigned to field symbols until runtime, the effectiveness of syntax and security checks is very limited for operations involving field symbols. This can lead to runtime errors or incorrect data assignments.
While runtime errors indicate an obvious problem, incorrect data assignments are dangerous because they can be very difficult to detect. For this reason, you should only use field symbols if you cannot achieve the same result using other ABAP statements.
For example, you may want to process part of a string where the offset and length depend on the contents of the field. You could use field symbols in this case. However, since the MOVE statement also supports variable offset and length specifications, you should use it instead. The MOVE statement (with your own auxiliary variables if required) is much safer than using field symbols, since it cannot address memory beyond the boundary of a field. However, field symbols may improve performance in some cases.
check the below links u will get the answers for your questions
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/content.htm
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/field_sy.htm
http://searchsap.techtarget.com/tip/1,289483,sid21_gci920484,00.html
Syntax Diagram
FIELD-SYMBOLS
Basic form
FIELD-SYMBOLS <fs>.
Extras:
1. ... TYPE type
2. ... TYPE REF TO cif
3. ... TYPE REF TO DATA
4. ... TYPE LINE OF type
5. ... LIKE s
6. ... LIKE LINE OF s
7. ... TYPE tabkind
8. ... STRUCTURE s DEFAULT wa
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Untyped Field Symbols ad Cannot Use Field Symbols as Components of Classes.
Effect
This statement declares a symbolic field called <fs>. At runtime, you can assign a concrete field to the field symbol using ASSIGN. All operations performed with the field symbol then directly affect the field assigned to it.
You can only use one of the additions.
Example
Output aircraft type from the table SFLIGHT using a field symbol:
FIELD-SYMBOLS <PT> TYPE ANY.
DATA SFLIGHT_WA TYPE SFLIGHT.
ASSIGN SFLIGHT_WA-PLANETYPE TO <PT>.
WRITE <PT>.
Addition 1
... TYPE type
Addition 2
... TYPE REF TO cif
Addition 3
... TYPE REF TO DATA
Addition 4
... TYPE LINE OF type
Addition 5
... LIKE s
Addition 6
... LIKE LINE OF s
Addition 7
... TYPE tabkind
Effect
You can define the type of the field symbol using additions 2 to 7 (just as you can for FORM parameters (compare Defining the Type of Subroutine Parameters). When you use the ASSIGN statement, the system carries out the same type checks as for USING parameters of FORMs.
This addition is not allowed in an ABAP Objects context. See Cannot Use Obsolete Casting for FIELD SYMBOLS.
In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. See Defining Types Using STRUCTURE.
Effect
Assigns any (internal) field string or structure to the field symbol from the ABAP Dictionary (s). All fields of the structure can be addressed by name: <fs>-fieldname. The structured field symbol points initially to the work area wa specified after DEFAULT.
The work area wa must be at least as long as the structure s. If s contains fields of the type I or F, wa should have the structure s or at least begin in that way, since otherwise alignment problems may occur.
Example
Address components of the flight bookings table SBOOK using a field symbol:
DATA SBOOK_WA LIKE SBOOK.
FIELD-SYMBOLS <SB> STRUCTURE SBOOK
DEFAULT SBOOK_WA.
WRITE: <SB>-BOOKID, <SB>-FLDATE.
Related
ASSIGN, DATA
Additional help
Declaring Field Symbols

How to use field symbols in program

how to use field symbols can any one explain with example please..
Regards,
venki...

Hi
Field Symbols
Field symbols are placeholders or symbolic names for other fields. They do not physically reserve space for a field, but point to its contents. A field symbol cam point to any data object. The data object to which a field symbol points is assigned to it after it has been declared in the program.
Whenever you address a field symbol in a program, you are addressing the field that is assigned to the field symbol. After successful assignment, there is no difference in ABAP whether you reference the field symbol or the field itself. You must assign a field to each field symbol before you can address the latter in programs.
Field symbols are similar to dereferenced pointers in C (that is, pointers to which the content operator * is applied). However, the only real equivalent of pointers in ABAP, that is, variables that contain a memory address (reference) and that can be used without the contents operator, are reference variables in ABAP Objects.
All operations programmed with field symbols are applied to the field assigned to it. For example, a MOVE statement between two field symbols moves the contents of the field assigned to the first field symbol to the field assigned to the second field symbol. The field symbols themselves point to the same fields after the MOVE statement as they did before.
You can create field symbols either without or with type specifications. If you do not specify a type, the field symbol inherits all of the technical attributes of the field assigned to it. If you do specify a type, the system checks the compatibility of the field symbol and the field you are assigning to it during the ASSIGN statement.
Field symbols provide greater flexibility when you address data objects:
If you want to process sections of fields, you can specify the offset and length of the field dynamically.
You can assign one field symbol to another, which allows you to address parts of fields.
Assignments to field symbols may extend beyond field boundaries. This allows you to address regular sequences of fields in memory efficiently.
You can also force a field symbol to take different technical attributes from those of the field assigned to it.
The flexibility of field symbols provides elegant solutions to certain problems. On the other hand, it does mean that errors can easily occur. Since fields are not assigned to field symbols until runtime, the effectiveness of syntax and security checks is very limited for operations involving field symbols. This can lead to runtime errors or incorrect data assignments.
While runtime errors indicate an obvious problem, incorrect data assignments are dangerous because they can be very difficult to detect. For this reason, you should only use field symbols if you cannot achieve the same result using other ABAP statements.
For example, you may want to process part of a string where the offset and length depend on the contents of the field. You could use field symbols in this case. However, since the MOVE statement also supports variable offset and length specifications, you should use it instead. The MOVE statement (with your own auxiliary variables if required) is much safer than using field symbols, since it cannot address memory beyond the boundary of a field. However, field symbols may improve performance in some cases.
check the below links u will get the answers for your questions
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/content.htm
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/field_sy.htm
http://searchsap.techtarget.com/tip/1,289483,sid21_gci920484,00.html
Syntax Diagram
FIELD-SYMBOLS
Basic form
FIELD-SYMBOLS <fs>.
Extras:
1. ... TYPE type
2. ... TYPE REF TO cif
3. ... TYPE REF TO DATA
4. ... TYPE LINE OF type
5. ... LIKE s
6. ... LIKE LINE OF s
7. ... TYPE tabkind
8. ... STRUCTURE s DEFAULT wa
The syntax check performed in an ABAP Objects context is stricter than in other ABAP areas. See Cannot Use Untyped Field Symbols ad Cannot Use Field Symbols as Components of Classes.
Effect
This statement declares a symbolic field called <fs>. At runtime, you can assign a concrete field to the field symbol using ASSIGN. All operations performed with the field symbol then directly affect the field assigned to it.
You can only use one of the additions.
Example
Output aircraft type from the table SFLIGHT using a field symbol:
FIELD-SYMBOLS <PT> TYPE ANY.
DATA SFLIGHT_WA TYPE SFLIGHT.
ASSIGN SFLIGHT_WA-PLANETYPE TO <PT>.
WRITE <PT>.
Addition 1
... TYPE type
Addition 2
... TYPE REF TO cif
Addition 3
... TYPE REF TO DATA
Addition 4
... TYPE LINE OF type
Addition 5
... LIKE s
Addition 6
... LIKE LINE OF s
Addition 7
... TYPE tabkind
Effect
You can define the type of the field symbol using additions 2 to 7 (just as you can for FORM parameters (compare Defining the Type of Subroutine Parameters). When you use the ASSIGN statement, the system carries out the same type checks as for USING parameters of FORMs.
This addition is not allowed in an ABAP Objects context. See Cannot Use Obsolete Casting for FIELD SYMBOLS.
In some cases, the syntax rules that apply to Unicode programs are different than those for non-Unicode programs. See Defining Types Using STRUCTURE.
Effect
Assigns any (internal) field string or structure to the field symbol from the ABAP Dictionary (s). All fields of the structure can be addressed by name: <fs>-fieldname. The structured field symbol points initially to the work area wa specified after DEFAULT.
The work area wa must be at least as long as the structure s. If s contains fields of the type I or F, wa should have the structure s or at least begin in that way, since otherwise alignment problems may occur.
Example
Address components of the flight bookings table SBOOK using a field symbol:
DATA SBOOK_WA LIKE SBOOK.
FIELD-SYMBOLS <SB> STRUCTURE SBOOK
DEFAULT SBOOK_WA.
WRITE: <SB>-BOOKID, <SB>-FLDATE.
<b>Reward points for useful Answers</b>
Regards
Anji

FOR ALL ENTRIES... with FIELD SYMBOL

Is it possible to use FOR ALL ENTRIES with a FIELD-SYMBOL that points to a data reference of type STANDARD TABLE ?
I have the following:
SELECT * FROM mara
    INTO TABLE table
    FOR ALL ENTRIES IN another_table
    WHERE matnr EQ another_table-matnr.
The code above is what exists, (working), but I'm improving the program and one of the improvements is to allow dynamic querying by providing a field symbol instead of a hard-coded table like "another_table". But I get the message "the specified type has no structure and therefore no component called "MATNR".
My code just have the field symbol that points to a previously data reference created for a table passed as a parameter (this is working, having checked via debugging) replacing "another_table" and <fs>-matnr instead of "another_table-matnr".
What solutions would you guys suggest ?
Thanks
Avraham

Why is that that the commented line doesn't work, but under debugging I can reach <ls_items>-matnr ?
Everything is fine with <lt_items>, it contains 8 lines, and debugging shows <ls_items> receiving one line each loop pass, just as expected. I wanted to understand why/when does this error of "has no structure therefore there is no component"... appears.
LOOP AT <lt_items> INTO <ls_items>.
*    SELECT SINGLE * INTO ls_mara FROM mara WHERE mara~matnr = <ls_items>-matnr.
    IF sy-subrc = 0.
      APPEND ls_mara TO lt_mara.
    ENDIF.
ENDLOOP.

Field Symbol that call input field

Similar Messages

Maybe you are looking for