Where is error about field-symbols?

I wrote a short program about field-symbols , but when I build it, I had issues with "WA is too short for <F1>." I don't know what is happen.
REPORT ZSKY061901.
data : wa(100) value '0123456789'.
data : begin of line1,
co1(6),
co2(4),
co3(5),
end of line1.
data : begin of line2,
co1 type i value 1,
co2 type i value 2,
end of line2.
data line3 like line2.
data itab like line2 occurs 10 with header line.
line3-co1 = 11.
line3-co2 = 22.
field-symbols:
 <F1> structure sbook default wa,
 <F2> structure line1 default wa,
 <F3> structure itab default line3.
write: / <F1>-mandt,<F1>-carrid,<F1>-connid,<F1>-fldate,
 / <F2>-co1,<F2>-co2,<F2>-co3,
 / <F3>-co1,<F3>-co2.

Hi,
field-symbols:
 <F1> structure sbook default wa,
 <F2> structure line1 default wa,
 <F3> structure itab default line3.
Lets take <F1>, here the Structure is SBOOK, so SBOOK will have some fields in it, count the total length of the fields in the SBOOK, it may come around 200 lenght, then the WA length should be 200....
Regards
Sudheer

Similar Messages

Can any one explain me about Field symbols in Genral Reports?

Can any one explain me about Field symbols in Genral Reports?
If possible, plz explain me with the code to explain me about the field symbols.
Regards,
Krishna Chaitanya

Syntax
FIELD-SYMBOLS <fs> { typing | STRUCTURE struc DEFAULT dobj }.
Extras:
1. ... typing
2. ... STRUCTURE struc DEFAULT dobj
Effect
The FIELD-SYMBOLS statement declares a field symbol <fs>. The naming conventions apply to the name fs. The angle brackets of the field symbols indicate the difference to data objects and are obligatory. You can declare field symbols in any procedure and in the global declaration section of an ABAP program, but not in the declaration section of a class or an interface. You can use a field symbol in any operand position in which it is visible and which match the typing defined using typing.
After its declaration, a field symbol is initial - that is, it does not reference a memory area. You have to assign a memory area to it (normally using the ASSIGN statement) before you can use it as an operand. Otherwise an exception will be triggered.
Addition 1
... typing
Effect
You can use the addition typing to type the field symbol. The syntax of typing is described under Syntax of Typing. The typing specifies which memory areas can be assigned to the field symbol (see Checking the Typing) and in which operand positions it can be used.
Note
You can omit the addition typing outside of methods. In this case, the field symbol has the complete generic type any and is implicitly assigned the predefined constant space during the declaration.
Addition 2
... STRUCTURE struc DEFAULT dobj
Effect
If you specify the addition STRUCTURE instead of typing for a field symbol, and struc is a local program structure (a data object, not a data type) or a flat structure from the ABAP Dictionary, this structure is cast for the field symbol <fs>. You have to specify a data object dobj that is initially assigned to the field symbol.
The field symbol copies the technical attributes of structure struc as if it were completely typed. When you assign a data object using the addition DEFAULT, or later using ASSIGN, its complete data type is not checked in non- Unicode programs. Instead, the system merely checks whether it has at least the length of the structure and its alignment.
In Unicode programs, we differentiate between structured and elementary data objects. For a structured data object dobj, its Unicode fragment view has to match the one of struc. In the case of an elementary data object, the object must be character-type and flat, and struc must be purely character-type. The same applies to assignments of data objects to field symbols typed using STRUCTURE when using the ASSIGN statement.
Note
Field symbols declared using the addition STRUCTURE are a mixture of typed field symbols and a utility for casting structured data types. You should use the additions TYPE or LIKE for the FIELD-SYMBOLS statement to type field symbols, while the addition CASTING of the ASSIGN statement is used for casting.
Example
The first example shows the obsolete usage of the addition STRUCTURE.
DATA wa1 TYPE c LENGTH 512.
FIELD-SYMBOLS <scarr1> STRUCTURE scarr DEFAULT wa1.
<scarr1>-carrid = '...'.
The second example shows the replacement of STRUCTURE with the additions TYPE and CASTING.
DATA wa2 TYPE c LENGTH 512.
FIELD-SYMBOLS <scarr2> TYPE scarr.
ASSIGN wa2 TO <scarr2> CASTING.
<scarr2>-carrid = '...'.
Also,
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

Details about Field symbols

Hi All,
Can anyone explain fully about field symbols in ABAP.
please provide with examples how to use in programming.
Thanks in advance.
Naba.

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 a field symbol before you can address it in a program.
Field symbols are similar to de-referenced pointers in the C programming language (that is, pointers to which the content operator * is applied). In ABAP, data references represent a real equivalent to pointers in the sense of variables that contain a memory address and can be used without the contents operator.
All operations programmed with field symbols are applied to the field assigned to it. A MOVE statement between two field symbols, for example, assigns the contents of the field assigned to another source field symbol to the field assigned to the target field symbol. The field symbols themselves point to the same fields after the MOVE statement as they did before the MOVEstatement.
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 during the field assignment whether the assigned field matches the type of field symbol.
Field symbols provide greater flexibility when you address data objects:
·        You can assign one field symbol to another, which allows you to address subfields.
·        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 properties than those of the field assigned to it (casting).
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. 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.
*& Chapter 24: Working with Field Symbols
REPORT CHAP2401.
Defining a Field Symbol
FIELD-SYMBOLS .
Variable for later use
DATA FIELD VALUE 'X'.
Assigning a field to a Field Symbol
ASSIGN FIELD TO .
Using a Field Symbol which has an assigned field
WRITE .

Error in field symbol

Hi all,
i'm converting a field symbol table to internat table, where field symbol table structure is defined at runtime. for that i'm using
call method cl_alv_table_create=>create_dynamic_table
 exporting
 it_fieldcatalog = ifc1
 importing
 ep_table = dy_table.
assign dy_table->* to <dyn_table>.
create data dy_line like line of <dyn_table>.
assign dy_line->* to <dyn_wa>.
LOOP AT <dyn_table> ASSIGNING <dyn_wa>.
MOVE-CORRESPONDING <dyn_wa> TO dy_line.
INSERT dy_line INTO TABLE dy_table.
endloop.
where
data: dy_table type ref to data,
 dy_line type ref to data,
But in execution time it show a error that dy_table is not a internal table.
pls give me ur suggestions.

Hi Ravish,
pls find yhe code, it;s throwing a error that dyn_table is not a internal table.
TABLES : SFLIGHT.
type-pools : abap.
field-symbols: <dyn_table> type standard table ,
 <dyn_wa>,
 <dyn_field>.
data: dy_table type ref to data,
 dy_line type ref to data,
 xfc type lvc_s_fcat,
 ifc type lvc_t_fcat,
 IFC1 TYPE LVC_T_FCAT.
selection-screen begin of block b1 with frame.
parameters: p_table(30) type c default 'SFLIGHT'.
*FIELD-SYMBOLS <F> TYPE table p_table.
data : field(10) type c.
SELECT-OPTIONS : P_FIELD FOR field.
selection-screen end of block b1.
start-of-selection.
perform get_structure.
perform get_selected_field.
perform create_dynamic_itab.
perform get_data.
perform write_out.
form get_structure.
data : idetails type abap_compdescr_tab,
 xdetails type abap_compdescr.
data : ref_table_des type ref to cl_abap_structdescr.
ref_table_des ?=
 cl_abap_typedescr=>describe_by_name( p_table ).
idetails[] = ref_table_des->components[].
loop at idetails into xdetails.
 clear xfc.
 xfc-fieldname = xdetails-name .
 xfc-datatype = xdetails-type_kind.
 xfc-inttype = xdetails-type_kind.
 xfc-intlen = xdetails-length.
 xfc-decimals = xdetails-decimals.
 append xfc to ifc.
endloop.
endform.
form get_selected_field.
data: wa like line of ifc.
loop at ifc into wa.
if wa-fieldname in p_field.
append wa to ifc1.
endif.
sy-index = sy-index + 1.
endloop.
if ifc1 is initial .
MESSAGE e000 WITH 'This field is not available in table'.
endif.
endform.
form create_dynamic_itab.
call method cl_alv_table_create=>create_dynamic_table
 exporting
 it_fieldcatalog = ifc1
 importing
 ep_table = dy_table.
assign dy_table->* to <dyn_table>.
create data dy_line like line of <dyn_table>.
assign dy_line->* to <dyn_wa>.
endform.
form get_data.
SELECT * INTO CORRESPONDING FIELDS OF TABLE <dyn_table>
FROM (p_table) UP TO 20 ROWS.
endform.
form write_out.
Write out data from table.
loop at <dyn_table> into <dyn_wa>.
 do.
 assign component sy-index
 of structure <dyn_wa> to <dyn_field>.
 if sy-subrc <> 0.
 exit.
 endif.
 if sy-index = 1.
 write:/ <dyn_field>.
 else.
 write: <dyn_field>.
 endif.
 enddo.
code for convert field symbol internal table to internal table.
LOOP AT <dyn_table> ASSIGNING <dyn_wa>.
MOVE-CORRESPONDING <dyn_wa> TO dy_line.
INSERT dy_line INTO TABLE dy_table. <----
Error point
endloop.
endform.

ABOUT FIELD SYMBOL

hi
i know what is a field symbol. but i am confused in which case i should use field symbol.
suppose i am modifying a standard internal table XITAB . then is it a good practice(or neccessary) to use field symbol instead of local work area or local internal table??

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. (For more information, see Data References).
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.
Reward If Helpful
Jagadish.

Query about field symbol

Hi,
Can we write a query like this using field symbol.
<FS> is a field symbol mapped onto an internal table.
select * from dbtab into corresponding field of internal_tab for all entries in <FS>
where field1 = <FS>-field1.
It gives a syntax error when I check this query. Even if I turn field1 into a field symbol <FS1> to hold the field name, it gives an error.
Could anyone advice in this context.
Thanks for the help in advance.
Regards,
Vijay

Vijay,
Its not a limitation.
You would have declared your table like this, right?
FIELD-SYMBOLS : <FT> TYPE TABLE.
Now, unless you assign this to table, the field symbols will not have a structure, right. This assignment happens only at runtime. So, there is no way that the system can identify <FT>-field1 at design time and compile the same, right?
However, the question is if you know the structure at design time, why do you want to use a field symbols for the table?
Regards,
Ravi
Note : Please mark the helpful answers

In getting error in field symbols

your attempted to assign a field to a type filed symbols but the field dose not have the required type.
iam getting runtimes error like this what should i do for this.
regards,
sivakumar

Hi,
Do not assign any particular data type to your field symbol definition.
field-symbols: <fs> type any.
assign p_matnr to <fs>.
assign sy-datum to <fs>.
regards
Subramanian

About field symbols

hi experts,
can any one send me the concept of the following topics,
1. FIELD SYMBOLS
2. SUBROUTINES
3. CONDENSE.
please send me some material about this topics with example programs.
thanks

hi,
FIELD-SYMBOLS
Check the below links
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/content.htm
Basic form
FIELD-SYMBOLS <fs>.
Additions
1. ... STRUCTURE s DEFAULT wa
2. ... TYPE t
3. ... TYPE LINE OF t
4. ... LIKE s
5. ... LIKE LINE OF s
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>.
TABLES SFLIGHT.
ASSIGN SFLIGHT-PLANETYPE TO <PT>.
WRITE <PT>.
Addition 1
... STRUCTURE s DEFAULT wa
Effect
Assigns any (internal) field string or structure to the field symbol from the ABAP/4 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.
Addition 2
... TYPE t
Addition 3
... TYPE LINE OF t
Addition 4
... LIKE s
Addition 5
... LIKE LINE OF s
Effect
You can use additions 2 to 5 to type field symbols in the same way as FORM parameters (see also Type assignment of subroutine parameters). ASSIGN performs the same type checks as with USING parameters of FORM s. .
condense
*Code to demonstrate CONDENSE command
DATA: ld_field(50) type c.
p_field = 'Welcome to SAPDev'.
CONDENSE p_field NO-GAPS. "P_field must be of type character
*Result of p_field would be: 'WelcometoSAPDev'
or
SHIFT ld_field RIGHT DELETING TRAILING SPACE.
SHIFT ld_field LEFT DELETING LEADING SPACE.
DATA: ld_field(50) type c.
P_field type ld_field.
p_field = ' Welcome To SAP '.
ld_field = p_field.
SHIFT ld_field RIGHT DELETING TRAILING SPACE.
SHIFT ld_field LEFT DELETING LEADING SPACE.
write ld_field .
Rgds
Anver

Error in Field symbol assignment

What is wrong in following code ???
At line --> (Bold) I am gettin sy-subrc 4.
field-symbols: <F> type any,
 <FSVALUE> type any.
 SPLIT P_QUOTATION_TEXT-TEXT_LINE AT CRLF INTO TABLE I_SPLIT.
 IF NOT I_SPLIT[] IS INITIAL.
 LOOP AT I_SPLIT ASSIGNING <F>.
--> ASSIGN COMPONENT SY-TABIX OF STRUCTURE <F> TO <FSVALUE>.
 IF SY-SUBRC = 0.
 WA_TEXT-ITM_NUMBER = P_QUOTATION_TEXT-ITM_NUMBER.
 WA_TEXT-TEXT_ID = C_HEADERTEXT.
 WA_TEXT-LANGU = 'EN'.
 WA_TEXT-FORMAT_COL = '*'.
 WA_TEXT-TEXT_LINE = <FSVALUE>.
 APPEND WA_TEXT TO I_TEXT.
 CLEAR WA_TEXT.
 ENDIF.
 ENDLOOP.

I'll try to get clearer
SPLIT P_QUOTATION_TEXT-TEXT_LINE AT CRLF INTO TABLE I_SPLIT.
You are splitting at CRLF, fine. I_split has only one field or none if you want to get more thecnical.
LOOP AT I_SPLIT ASSIGNING <F>.
Here you are starting to loop at each entry of i_split, assigning each entry to , again only one field
ASSIGN COMPONENT SY-TABIX OF STRUCTURE <F> TO <FSVALUE>.
Again, this will never work because as you are declaring it i_split doesn't have an structure, also doesn´t have an structure only one field
It doesn't make any sense that you are assigning the same field to another field-symbol when you already have one.
And even if you used the type I told you, it would only work in the first pass because only in the first pass you can assign the component 1 of the structure because the structure only has one field, there would not be any component 2,3... etc.
Again I don't understand what you are trying to do, if you want to assign that loop pass text to a table, just pass the field-symbol you already have

Getting a runtime error in block alv that field symbol has been assigned

hi to all experts ,
im getting a runtime error that field symbol has not been assigned in functionmodule reuse_alv_block_list_display
i tried a lot to rectify the error ,im unable to do it thats i have posted here
*& Report ZHAI_ALV_BLOCK_LIST
REPORT ZHAI_ALV_BLOCK_LIST.
type-pools:slis.
tables:mara.
DATA:BEGIN OF IT_MARA OCCURS 0,
 MATNR LIKE MARA-MATNR,
 MBRSH LIKE MARA-MBRSH,
 MATKL LIKE MARA-MATKL,
 END OF IT_MARA.
data: begin of IT_DESC OCCURS 0,
 MATNR like MAKT-MATNR,
 MAKTX like MAKT-MAKTX,
 end of IT_DESC.
data: begin of IT_MARD occurs 0,
 MATNR like mard-matnr,
 WERKS like mard-werks,
 LGORT like mard-lgort,
 LABST like mard-labst,
 end of IT_MARD.
data: IT_FCAT TYPE SLIS_T_FIELDCAT_ALV ,
 WA_FCAT LIKE LINE OF IT_FCAT,
 IT_FCAT1 type slis_t_fieldcat_alv,
 WA_FCAT1 LIKE LINE OF IT_FCAT1,
 IT_FCAT2 TYPE SLIS_T_FIELDCAT_ALV,
 WA_FCAT2 LIKE LINE OF IT_FCAT2,
 wa_layout type SLIS_LAYOUT_ALV,
 it_event type SLIS_T_EVENT,
 wa_event like line of it_event,
 wa_layout like line of it_layout,
 V_REPID LIKE SY-REPID.
select-options:so_matnr for mara-matnr.
start-of-selection.
perform f_select_data.
DEFINE ADD_CATALOGUE1.
WA_FCAT-COL_POS = &1.
WA_FCAT-fieldname = &2.
WA_fcat-tabname = &3.
wa_fcat-emphasize = &4.
wa_fcat-ref_tabname = &5.
APPEND WA_FCAT TO IT_FCAT.
END-OF-DEFINITION.
DEFINE ADD_CATALOGUE2.
WA_FCAT1-COL_POS = &1.
WA_FCAT1-fieldname = &2.
WA_fcat1-tabname = &3.
wa_fcat1-emphasize = &4.
wa_fcat1-ref_tabname = &5.
APPEND WA_FCAT1 TO IT_FCAT1.
END-OF-DEFINITION.
DEFINE ADD_CATALOGUE3.
WA_FCAT2-COL_POS = &1.
WA_FCAT2-fieldname = &2.
WA_fcat2-tabname = &3.
wa_fcat2-emphasize = &4.
wa_fcat2-ref_tabname = &5.
APPEND WA_FCAT2 TO IT_FCAT2.
END-OF-DEFINITION.
perform f_build_fcat.
*perform f_build_fcat1.
perform f_build_fcat2.
PERFORM F_BUILD_LAYOUT.
PERFORM F_BUILD_EVENTS.
PERFORM F_BLOC_DISPLAY.
*& Form f_select_data
FORM f_select_data .
select matnr
 mbrsh
 matkl
 from mara into table it_mara where matnr
in so_matnr.
if it_mara[] is not initial.
select matnr
 maktx
 from makt
 into table it_desc
 for all entries in it_mara
 where matnr eq it_mara-matnr.
endif.
if it_desc[] is not initial.
select matnr
 werks
 lgort
 labst
 from mard
 into table it_mard
 for all entries in it_desc
 where matnr eq it_desc-matnr.
endif.
ENDFORM. " f_select_data
*& Form f_build_fcat
FORM f_build_fcat .
ADD_CATALOGUE2:
'1' 'MATNR' 'IT_MARA' 'C500' 'MARA',
'2' 'MBRSH' 'IT_MARA' 'C600' 'MARA',
'3' 'MATKL' 'IT_MARA' 'C300' 'MARA'.
ENDFORM. " f_build_fcat
**& Form f_build_fcat1
FORM f_build_fcat1 .
ADD_CATALOGUE1:
'1' 'MATNR' 'IT_DESC' 'C500' 'MAKT',
'2' 'MAKTX' 'IT_DESC' 'C600' 'MAKT'.
ENDFORM. " f_build_fcat1
*& Form f_build_fcat2
FORM f_build_fcat2.
ADD_CATALOGUE3:
'1' 'MATNR' 'IT_MARD' 'C500' 'MARD',
'2' 'WERKS' 'IT_MARD' 'C600' 'MARD',
'3' 'LGORT' 'IT_MARD' 'C200' 'MARD',
'4' 'LABST' 'IT_MARD' 'C300' 'MARD'.
ENDFORM. " f_build_fcat2
*& Form F_BLOC_DISPLAY
 text
--> p1 text
<-- p2 text
FORM F_BLOC_DISPLAY .
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_INIT'
EXPORTING
 I_CALLBACK_PROGRAM = SY-REPID.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
 IS_LAYOUT = wa_layout
 IT_FIELDCAT = it_fcat
 I_TABNAME = 'IT_MARA'
 IT_EVENTS = it_event
IT_SORT =
I_TEXT = ' '
TABLES
 T_OUTTAB = IT_MARA
EXCEPTIONS
PROGRAM_ERROR = 1
MAXIMUM_OF_APPENDS_REACHED = 2
OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
 IS_LAYOUT = wa_layout
 IT_FIELDCAT = it_fcat1
 I_TABNAME = 'IT_DESC'
 IT_EVENTS = IT_EVENT
IT_SORT =
I_TEXT = ' '
TABLES
 T_OUTTAB = IT_DESC
EXCEPTIONS
PROGRAM_ERROR = 1
MAXIMUM_OF_APPENDS_REACHED = 2
OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
 IS_LAYOUT = wa_LAYOUT
 IT_FIELDCAT = IT_FCAT2
 I_TABNAME = 'IT_MARD'
 IT_EVENTS = IT_EVENT
IT_SORT =
I_TEXT = ' '
TABLES
 T_OUTTAB = IT_MARD
EXCEPTIONS
PROGRAM_ERROR = 1
MAXIMUM_OF_APPENDS_REACHED = 2
OTHERS = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_DISPLAY'.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " F_BLOC_DISPLAY
*& Form F_BUILD_LAYOUT
 text
--> p1 text
<-- p2 text
FORM F_BUILD_LAYOUT .
wa_layout-edit = 'X'.
wa_layout-window_titlebar = 'MOHAMMED ABDUL HAI'.
wa_layout-zebra = 'X'.
ENDFORM. " F_BUILD_LAYOUT
*& Form F_BUILD_EVENTS
 text
--> p1 text
<-- p2 text
FORM F_BUILD_EVENTS .
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
EXPORTING
 I_LIST_TYPE = 0
IMPORTING
 ET_EVENTS = IT_EVENT
EXCEPTIONS
 LIST_TYPE_WRONG = 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.
SORT IT_EVENT BY NAME.
READ TABLE it_event INTO wa_event WITH KEY NAME = 'TOP_OF_PAGE' bINARY
SEArch.
if sy-subrc eq 0.
wa_event-form = 'F_TOP_OF_PAGE'.
ENDIF.
MODIFY IT_EVENT FROM WA_EVENT INDEX SY-TABIX TRANSPORTING FORM.
READ TABLE IT_EVENT INTO WA_EVENT WITH KEY NAME = 'USER_COMMAND' BINARY SEARCH.
WA_EVENT-FORM = 'F_USER_COMMAND'.
MODIFY IT_EVENT FROM wa_event INDEX SY-TABIX TRANSPORTING FORM.
ENDFORM. " F_BUILD_EVENTS

Hi,
When does this runtime error occur? When displaying output (calling FM) or.....
I copied your coding and made a few minor changes and It's working fine for my now:
REPORT ZHAI_ALV_BLOCK_LIST.
TYPE-POOLS:slis.
TABLES:mara.
DATA:BEGIN OF it_mara OCCURS 0,
matnr LIKE mara-matnr,
mbrsh LIKE mara-mbrsh,
matkl LIKE mara-matkl,
END OF it_mara.
DATA: BEGIN OF it_desc OCCURS 0,
matnr LIKE makt-matnr,
maktx LIKE makt-maktx,
END OF it_desc.
DATA: BEGIN OF it_mard OCCURS 0,
matnr LIKE mard-matnr,
werks LIKE mard-werks,
lgort LIKE mard-lgort,
labst LIKE mard-labst,
END OF it_mard.
DATA: it_fcat TYPE slis_t_fieldcat_alv ,
 wa_fcat LIKE LINE OF it_fcat,
 it_fcat1 TYPE slis_t_fieldcat_alv,
 wa_fcat1 LIKE LINE OF it_fcat1,
 it_fcat2 TYPE slis_t_fieldcat_alv,
 wa_fcat2 LIKE LINE OF it_fcat2,
 wa_layout TYPE slis_layout_alv,
 it_event TYPE slis_t_event,
 wa_event LIKE LINE OF it_event,
* wa_layout like line of it_layout,
v_repid LIKE sy-repid.
SELECT-OPTIONS:so_matnr FOR mara-matnr.
START-OF-SELECTION.
PERFORM f_select_data.
DEFINE add_catalogue1.
 wa_fcat-col_pos = &1.
 wa_fcat-fieldname = &2.
 wa_fcat-tabname = &3.
 wa_fcat-emphasize = &4.
 wa_fcat-ref_tabname = &5.
 append wa_fcat to it_fcat.
END-OF-DEFINITION.
DEFINE add_catalogue2.
 wa_fcat1-col_pos = &1.
 wa_fcat1-fieldname = &2.
 wa_fcat1-tabname = &3.
 wa_fcat1-emphasize = &4.
 wa_fcat1-ref_tabname = &5.
 append wa_fcat1 to it_fcat1.
END-OF-DEFINITION.
DEFINE add_catalogue3.
 wa_fcat2-col_pos = &1.
 wa_fcat2-fieldname = &2.
 wa_fcat2-tabname = &3.
 wa_fcat2-emphasize = &4.
 wa_fcat2-ref_tabname = &5.
 append wa_fcat2 to it_fcat2.
END-OF-DEFINITION.
PERFORM f_build_fcat.
PERFORM f_build_fcat1.
PERFORM f_build_fcat2.
PERFORM f_build_layout.
PERFORM f_build_events.
PERFORM f_bloc_display.
*& Form f_select_data
FORM f_select_data .
SELECT matnr
mbrsh
matkl
FROM mara INTO TABLE it_mara WHERE matnr
IN so_matnr.
IF it_mara[] IS NOT INITIAL.
 SELECT matnr
 maktx
 FROM makt
 INTO TABLE it_desc
 FOR ALL ENTRIES IN it_mara
 WHERE matnr EQ it_mara-matnr.
ENDIF.
IF it_desc[] IS NOT INITIAL.
 SELECT matnr
 werks
 lgort
 labst
 FROM mard
 INTO TABLE it_mard
 FOR ALL ENTRIES IN it_desc
 WHERE matnr EQ it_desc-matnr.
ENDIF.
ENDFORM. " f_select_data
*& Form f_build_fcat
FORM f_build_fcat .
add_catalogue2:
'1' 'MATNR' 'IT_MARA' 'C500' 'MARA',
'2' 'MBRSH' 'IT_MARA' 'C600' 'MARA',
'3' 'MATKL' 'IT_MARA' 'C300' 'MARA'.
ENDFORM. " f_build_fcat
**& Form f_build_fcat1
FORM f_build_fcat1 .
add_catalogue1:
'1' 'MATNR' 'IT_DESC' 'C500' 'MAKT',
'2' 'MAKTX' 'IT_DESC' 'C600' 'MAKT'.
ENDFORM. " f_build_fcat1
*& Form f_build_fcat2
FORM f_build_fcat2.
add_catalogue3:
'1' 'MATNR' 'IT_MARD' 'C500' 'MARD',
'2' 'WERKS' 'IT_MARD' 'C600' 'MARD',
'3' 'LGORT' 'IT_MARD' 'C200' 'MARD',
'4' 'LABST' 'IT_MARD' 'C300' 'MARD'.
ENDFORM. " f_build_fcat2
*& Form F_BLOC_DISPLAY
* text
FORM f_bloc_display .
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_INIT'
 EXPORTING
 i_callback_program = sy-repid.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
is_layout = wa_layout
it_fieldcat = it_fcat1
i_tabname = 'IT_MARA'
it_events = it_event
*IT_SORT =
*I_TEXT =
TABLES
t_outtab = it_mara
EXCEPTIONS
program_error = 1
maximum_of_appends_reached = 2
OTHERS = 3
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
is_layout = wa_layout
it_fieldcat = it_fcat1
i_tabname = 'IT_DESC'
it_events = it_event
*IT_SORT =
*I_TEXT =
TABLES
t_outtab = it_desc
EXCEPTIONS
program_error = 1
maximum_of_appends_reached = 2
OTHERS = 3
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
EXPORTING
is_layout = wa_layout
it_fieldcat = it_fcat2
i_tabname = 'IT_MARD'
it_events = it_event
*IT_SORT =
*I_TEXT = ' '
TABLES
t_outtab = it_mard
EXCEPTIONS
program_error = 1
maximum_of_appends_reached = 2
OTHERS = 3
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_DISPLAY'.
IF sy-subrc <> 0.
 MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM. " F_BLOC_DISPLAY
*& Form F_BUILD_LAYOUT
FORM f_build_layout .
wa_layout-edit = 'X'.
wa_layout-window_titlebar = 'MOHAMMED ABDUL HAI'.
wa_layout-zebra = 'X'.
ENDFORM. " F_BUILD_LAYOUT
*& Form F_BUILD_EVENTS
FORM f_build_events .
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
 EXPORTING
 i_list_type = 0
 IMPORTING
 et_events = it_event
 EXCEPTIONS
 list_type_wrong = 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.
SORT it_event BY name.
READ TABLE it_event INTO wa_event WITH KEY name = 'TOP_OF_PAGE' BINARY
SEARCH.
IF sy-subrc EQ 0.
 wa_event-form = 'F_TOP_OF_PAGE'.
ENDIF.
MODIFY it_event FROM wa_event INDEX sy-tabix TRANSPORTING form.
READ TABLE it_event INTO wa_event WITH KEY name = 'USER_COMMAND' BINARY
SEARCH.
wa_event-form = 'F_USER_COMMAND'.
MODIFY it_event FROM wa_event INDEX sy-tabix TRANSPORTING form.
ENDFORM. " F_BUILD_EVENTS

Error in drill down of RRI- Field Symbol not assigned

Dear all,
I am trying to call a SAP transaction on click of the jump target. I have created the jump target in the following way ..let me know if I am wrong ..
Goto RBBS transaction . Specifed the sender report as 0SD_C01/0SD_C01_Q025 (Sales Volume Analysis) and target as r/3 client 210 and specifed the transaction Va01 as target.
But when I executed the report and did a right click ..on the context menu I coudl see the desription of the Jump target I have created and upon clicking I received a error ..field symbol not assigned ..
Can any let me know the cause of the error ..and how to resolve.. do i need to give any extra parameters while creating jump target..
Thanks,
Gupta

Hello Gayathri,
One you got the dump you can select debugger button in top-left corner screen.
That will take you to the execution snap shot where you can check all the field symbols and find out which one is not
assigned. accordingly you can find out what is missing on input side to avoid this dump.
Hope this helps!
Thanks,
Augustin.

Error: Field symbol not assigned

Hi all,
When I run a query (BW version 3.5) with a condition or an exception I receive an error message "Field symbol has not yet been assigned". The same query run fine on BW version 3.1.
SP 11 and SP12 are installed.
Any idea how to solve the problem??

Paolo,
Note 555143 can not be implemented. Probably because I am working in BW version 3.5 instead of BW version 3.1.
Thanks anyway.
Regards,
Hans

Issue with field symbol not assigned in SMQ2

We are facing an issue with an error in SMQ2.
The error is "field symbol not assigned". There is also short dump in ST22.
I have read the previous forum threads and it talks about going into the debugger mode.
However, which is the program to be debugged ?
How do I navigate from SMQ2 to the ABAP program.
Kindly let me know.
Regards,
Sanjay

Hi Sanjay,
You need to debug program RSTRFCM3. This is the program which drives SMQ2.
However just check if there are any support pack upgrades to the program recently since this is a standard program.
Regards
Abhii

Field Symbols - two explanations.

Hi,
Reading the documentation about field symbols, I find two explanations where I want to get to the bottom of it. More exactly:
1) During the assignment of field symbols which have a structure imposed (definition with structure), the system checks in non-Unicode programs whether the assigned data object has the same length.
2) (syntax) ASSIGN mem_area TO casting_spec range_spec.
The assigned memory area mem_area must be at least as long as the data type specified in casting_spec and must have the same alignment. If the data type determined in casting_spec is deep, the assigned memory area must have deep components of the same type at the same position.
Any exaple (ABAP code) will be well appreciated.
Thanks in advance for your kind help.
Regards,
 Giovanni
Edited by: Giovanni B on Feb 25, 2008 7:40 PM

Hi,
check this link
http://help.sap.com/saphelp_47x200/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/frameset.htm
DATA: wa(10) VALUE '0123456789'.
DATA: BEGIN OF line1,
 col1(3),
 col2(2),
 col3(5),
 END OF line1.
DATA: BEGIN OF line2,
 COL1(2),
 COL2 LIKE sy-datum,
 END OF line2.
FIELD-SYMBOLS: <f1> LIKE line1.
ASSIGN wa TO <f1> CASTING.
FIELD-SYMBOLS: <f2> LIKE line2.
ASSIGN wa TO <f2> CASTING.
WRITE: / <f1>-col1, <F1>-col2, <F1>-col3,
 / <f2>-col1, <F2>-col2.
the list appears as follows:
012 34 56789
01 2345/67/89
Regards

FIELD-SYMBOLS validation with MARA Table values

Hi,
FIELD-SYMBOLS: <itab> TYPE STANDARD TABLE.
I want to validate mara-matnr with <itab>. The values in <itab> is coming at runtime, so i want to validate first field values in <itab> for all the records with mara-matnr.
The values which are coming at runtime in <itab> is matnr, bukrs, lgort. I want to validate only matnr with mara-matnr.
I don't know about field-symbols validations?
anybody has an idea?
Thanks in advance,
Fractal

Hi,
use ASSIGN COMPONENT OF STRUCTURE.
Example.
LOOP AT <FS> ASSIGNING <FS_STRUCT>.
 ASSIGN COMPONENT 'MATNR' OF STRUCTURE <FS_STRUCT>
 TO <FS_RESULT>.
IF SY-SUBRC = 0.
 SELECT SINGLE * FROM MARA WHERE MATNR = <FS_RESULT>.
 CHECK SY-SUBRC = 0.
ENDIF.
ENDLOOP.
Thanks,
Naren

Where is error about field-symbols?

Similar Messages

Maybe you are looking for