Field Symbol as Subroutines name?

Dear all,
I am writing a program which includes different routines; it will be the best for me to separate different routines into different sub-routines for calling. However, it depends different parameters that I passed in, can I use a field symbol as the subroutine name for calling?
In the following sample:
DATA: program_name(20) TYPE C.
FIELD-SYMBOLS: <BDC_NAME> TYPE ANY.
CONCATENATE 'ZBDC_' i_program_name INTO program_name.
ASSIGN program_name TO <BDC_NAME>.
PERFORM <BDC_NAME> .
The error of the above code is <The FORM "<BDC_NAME>" does not exist> I think the problem may be the type of field-symbol, since I am assigning a parameter with type = C. SAP may not be able to recognize and convert it into a subroutine name. Is there any possible solution in doing this?
Regards,
Mandy Au

Thanks all for your fast response.
However, when I changed my code into the new one, error still occurs.
i_program_name = 'ZTEST'.
data: program_name(20) type c.
"FIELD-SYMBOLS: <BDC_NAME> type any.
concatenate 'ZBDC_' i_program_name into program_name.
"assign program_name to <BDC_NAME>.
perform (program_name) using i_output_date i_region .
ERROR: Routine name not specified
The i_program_name is a parameter passed in the upper level of the subroutine, which will be passed during runtime, therefore there is no actual name passed in. That is why I think of using the <Field-symbols>.
Regards,
Mandy Au

Similar Messages

HOW CAN I SEND FIELD SYMBOL TO SUBROUTINE

HAI,
 HOW CAN I SEND FIELD SYMBOL TO SUBROUTINE
 HOW CAN I COME BACK FROM 5TH INTERACTIVE REROT TO 2ND
INTERACTIVE REPORT.
THANK YOU.
ASHOK

Hi
Write some code in the program to come to 2nd list from 5th list
if sy-lsind = 5.
 sy-lsind = 2.
endif.
for field symbols see the doc
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
Reward points if useful
Regards
Anji

Passing Field Symbols in subroutines

Hi all,
Can any body tell me how to pass field symbols in a suboutine and will that effect orignal value of that symbl if i change it in subroutine.
Any Help will be awarded.
Sachin

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.
Reward points for useful Answers
Regards
Anji

Field symbols as Table name and in where condition in a select statement

Hello All,
I have a scenario where I need to get user input on table name and old field value and new field value. Then based on user input, I need to select the record from the database. The column name for all the tables in question is different in the database, however there data type is the same and have same values.
I am not able to use a field symbol for comparing the old field value to fetch the relevant record in my where clause.
I cannnot loop through the entire table as it has 10 millilon records, please advice on how to add the where clause as field symbol as the table name is also dynamically assigned.
Here is my code:
DATA: TAB LIKE SY-TNAME,
 TAB_COMP1 LIKE X031L-FIELDNAME,
 TAB_COMP2 LIKE X031L-FIELDNAME,
 NO_OF_FLD TYPE N.
DATA: BEGIN OF BUFFER,
 ALIGNMENT TYPE F,
 C(8000) TYPE C,
 END OF BUFFER.
FIELD-SYMBOLS: <WA> TYPE ANY,
 <COMP1> TYPE ANY,
 <COMP2> TYPE ANY.
GET TABLE NAME GIVEN BY USER IN LOCAL VARIABLE
TAB = TAB_NAME.
CREATE FIELD NAME BASED ON THE TABLE NAME ENTERED.
CASE TAB_NAME.
WHEN 'OIUH_RV_GL'.
 KEY FIELD
 TAB_COMP1 = 'GL_GL_SYS_NO'.
 NO_OF_FLD = 1.
WHEN 'OIUH_RV_OPSL'.
 KEY FIELD
 TAB_COMP1 = 'OPSL_GL_SYS_NO'.
 NO_OF_FLD = 1.
WHEN 'OIUH_RV_OTAX'.
 NOT THE ONLY KEY FIELD
 TAB_COMP1 = 'OTAX_GL_SYS_NO'.
 TAB_COMP2 = 'OTAX_TAX_POS_NO'.
 NO_OF_FLD = 2.
WHEN 'OIUH_RV_GTAX'.
 NOT THE ONLY KEY FIELD
 TAB_COMP1 = 'GTAX_GL_SYS_NO'.
 TAB_COMP2 = 'GTAX_TAX_POS_NO'.
 NO_OF_FLD = 2.
WHEN OTHERS.
 EXIT.
ENDCASE.
SET FIELD SYMBOL WITH APPROPRIATE TYPE TO BUFFER AREA.
ASSIGN BUFFER TO <WA> CASTING TYPE (TAB).
How to add where clause and remove the if condition in the select -- endselect
SELECT * FROM (TAB) INTO <WA>.
ASSIGN COMPONENT TAB_COMP1 OF STRUCTURE <WA> TO <COMP1>.
IF NO_OF_FLD = 2.
 ASSIGN COMPONENT TAB_COMP2 OF STRUCTURE <WA> TO <COMP2>.
ENDIF.
IF <COMP1> = OLD_SYS_NO.
 code for updating table would come here
 WRITE: 'MATCH FOUND'.
 EXIT.
ENDIF.
ENDSELECT.
Please advice. Thanks much.
Edited by: Shipra Jhunjhunwala on Jul 22, 2009 1:33 PM
Edited by: Shipra Jhunjhunwala on Jul 22, 2009 1:34 PM
Edited by: Shipra Jhunjhunwala on Jul 22, 2009 1:35 PM

1. Create single column table for holding field name depending on the table entered.
2. Take input from user: for e.g. table_name
3. Using case load single column table with required fields
 for e.g.
CASE TAB_NAME.
 WHEN 'OIUH_RV_GL'.
 Append 'GL_GL_SYS_NO' to KEY_FIELD --> KEY_FIELD is the single line internal table as mentioned in step 1.
 WHEN 'OIUH_RV_OPSL'.
 Append 'OPSL_GL_SYS_NO'.
 WHEN 'OIUH_RV_OTAX'.
 Append 'OTAX_GL_SYS_NO' to KEY_FIELD.
 APPEND 'OTAX_TAX_POS_NO' to KEY_FIELD.
 WHEN 'OIUH_RV_GTAX'.
 Append 'GTAX_GL_SYS_NO' to KEY_FIELD.
 APPEND 'OTAX_TAX_POS_NO' to KEY_FIELD.
 WHEN OTHERS.
 EXIT.
 ENDCASE.
 Now depending on the table name you have required column ready
4. Create dynamic internal table using following sudo code
 Fill the fieldcatlog using the single column field table and DD03L table, See what all columns from DD03L you want to fill in field catlog table
 loop at internal table with all the fields.
 move it to field catalog.
 append field catalog.
 endloop.
5. Pass this field catalog table to static method create_dynamic_table method
 DATA table TYPE REF TO DATA. --> data object for holding handle to dynamic internal table.
 call method cl_alv_table_create=>create_dynamic_table
 exporting
 it_fieldcatalog = fieldcatalog_tab
 importing
 ep_table = table.
6. Now assign table reference to field symbol of type table.
 ASSIGN table->* to <field-tab>.
7. Also create work area <field-wa> using refrence of table.
 create data object wa LIKE LINE OF <field-tab>.
 ASSIGN wa->* to <field-wa>.
8. Also define field symbol for field name.
 for e.g. <field_name>
4. Dynamic internal table is ready
5. Now execute the select statement as follows:
 SELECT (KEY_FIELD)
 INTO <ITAB> --> created dynamically above
 FROM (TABLE_NAME)
 WHERE (WHERE). --> WHERE is single line internal table having line type of CHAR72. So for every old value there will be one line
 Where condition is same as like we give in static way only difference in this case it will stored in internal table line wise.
 In this case you need to append all your where condition line by line in to WHERE.
5. To fill this dynamic internal table using ASSIGN COMPONENT <Comp_number> OF STRUCTURE <field-wa> TO <field-name>
 So in this case if first field of structure STRUCT1 is user_id then sudo-code will be
 loop at internal table containing list of fields into field_wa --> single column field table
 ASSIGN COMPONENT field_wa OF STRUCTURE <field-wa> TO <field>. "Here field_wa is wa area for single column internal table holding all the fieldnames.
 Now <field-name> points to user_id field. Move some value into it as nornally we do with variables.
 Move <your_new_value> to <field-name>. --> Assign new value
 or
 <field-name> = <your_new_value>.
 Endloop.
6. After completing all the fields one row will be ready in <field_wa>.
 APPEND <field_wa> to <field_tab>.
Hope this helps you.
Thanks,
Augustin.

Can I verify a field-symbol using its component name?

Hello experts,
I am looping at my field-symbol and I need to know what are its component name.
I need to create an IF or CASE statement checking whether the field-symbol's
component name is equal to that of the value that I declared. I want to do
something like this:
LOOP AT <fs_dyntable> ASSIGNING <wa_dyntable>.
ASSIGN COMPONENT sy-index OF STRUCTURE <wa_dyntable>
 TO <component>.
 IF sy-subrc <> 0.
 EXIT.
 ENDIF.
if component name = '2000'.
 condition...
elseif component name = '1999'.
 condition...
elseif component name = '1998'.
 condition...
endif.
endloop.
Again, thank you guys and take care!

Hi,
I am not clear on your doubt , but you can use field-symbol fields like below:
* if <component>-fld1 = '2000'.
condition...
elseif <component>-fld1 = '1999'.
condition...
elseif <component>-fld1 = '1998'.
condition...
endif.
endloop.
LOOP AT x_table ASSIGNING <wa_table>.
IF <wa_table>-fld1 EQ 100.
-----your code
ENDIF.
ENDLOOP.
Regards
Appana

Problem after assigning field-symbol in read statement...

Hello Experts,
I want to use a universal field-symbol in reading my internal tables so
I can avoid declaring multiple work areas. Here is my code:
FIELD-SYMBOLS: <fs_any> type any.
READ TABLE lt_orderadm_h INDEX 1 ASSIGNING <fs_any>.
Now when I try to insert this code:
IF NOT <fs_any>-object_id IS INITIAL.
ENDIF.
It says that <fs_any> has no structure and therefore no component called object_id.
I think that I need to use assign component for this but I don't know the code.
Thank you guys and take care!

Hi
DATA : WA_ITORDERADM_H LIKE LINE OF IT_ORDERADM_H.
**Try to assign the work area rather type any**
FIELD-SYMBOLS: <fs_any> type WA_ITORDERADM_H.
READ TABLE lt_orderadm_h INDEX 1 ASSIGNING <fs_any>.
Now when I try to insert this code:
IF NOT <fs_any>-object_id IS INITIAL.
ENDIF.
Check this program
This works for me
Simple program.
TYPES: BEGIN OF NAME,
NEXTNAME(10),
FIRSTNAME(10),
LASTNAME(10),
END OF NAME.
FIELD-SYMBOLS <F> TYPE NAME.
DATA: LINE(30).
LINE = 'JOHN SMITH SHRI'.
ASSIGN LINE TO <F> CASTING.
WRITE: / 'Lastname:', <F>-LASTNAME,
'Firstname:', <F>-FIRSTNAME,
'Nextname :', <F>-NEXTNAME
Award points if helpful
Thanks
VENKI

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

How to pass dynamic name to a field-symbol?

Hi All,
I have a requirement like I need to create dynamic internal table with dynamic name. Say like,
Create a new Table
 CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = it_fieldcat_fin[]
 IMPORTING
 ep_table = new_table.
 IF sy-subrc EQ 0.
Create a new Line with the same structure of the table.
 ASSIGN new_table->* to (<fs_table>).
In the above code, (<fs_table>) is a variable. Actually it is in the loop, so that first time it comes, it has to create an internal table with name as <fs_01>, next time <fs_02> and so on. Hope I am clear.
Please help me. I am sure that i will mark the helpful answers.

DATA: DREF TYPE REF TO DATA,WA_REF TYPE REF TO DATA.
FIELD-SYMBOLS: <TEMP_TAB> TYPE TABLE, <TEMP_WA> TYPE ANY.
*& Form DYNAMIC_TABLE
 text
--> p1 text
<-- p2 text
FORM DYNAMIC_TABLE.
CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
 EXPORTING
 IT_FIELDCATALOG = LT_LVCFIELDCAT
 IMPORTING
 EP_TABLE = DREF.
ASSIGN dref->* TO <TEMP_TAB>.
ENDFORM. " DYNAMIC_TABLE
the above is the procedure to create dynamic internal tables.
now <TEMP_TAB> points to the contents of the table table in DREF.
field symbol it self is meant for dynamic.
then y r u using (<fs_table>).
when everytime the same fieldsymbol is pointing to new contents, y u need new name everytime?
i mean as the data is not static, so what is the use of naming a field symbol every time?.
if u want to store the data in an internal table with a name,
then u can do like below,
data: tabname type string, i type i.
concatenate '<fs_' i into tabname.
"let i be the variable which stores the internal tables count
"MOVE <temp_tab> to tabname.

FIELD-SYMBOLS as parameter subroutine that point to table

Hi everyone,i have question. We often send table through subroutine using keyword TABLE.
FORM f_xxx TABLES pt_xxx
Now my question is possible send this internal table through field symbols? If so, how to do this?
1. FORM f_xxx USING <fs_xxx> STRUCTURE ty_xxx or
2. FORM f_xxx CHANGING <fs_xxx> STRUCTURE .... or
3. FORM f_yyy TABLES <fs_yyy>
Thank you.
Regards,
Satria

Hi everyone,i have question. We often send table through subroutine using keyword TABLE.
FORM f_xxx TABLES pt_xxx
Now my question is possible send this internal table through field symbols? If so, how to do this?
1. FORM f_xxx USING <fs_xxx> STRUCTURE ty_xxx or
2. FORM f_xxx CHANGING <fs_xxx> STRUCTURE .... or
3. FORM f_yyy TABLES <fs_yyy>
Thank you.
Regards,
Satria

Field name referenced by field symbol

Hi,
I would like to get the field name referenced by a field symbol at rutime. In the code below, besides the type and length of the field, I also would like to get the field names 'AA', 'BB' and 'CC' .
Can you please tell me how I can get this information?
DATA: BEGIN OF g_test,
 aa(10) TYPE c,
 bb TYPE i,
 cc(20) TYPE c,
 END OF g_test.
DATA: l_type(20),
 l_len TYPE i.
FIELD-SYMBOLS <fs>.
START-OF-SELECTION.
DO 3 TIMES.
 ASSIGN COMPONENT sy-index OF STRUCTURE g_test TO <fs>.
 DESCRIBE FIELD <fs> TYPE l_type OUTPUT-LENGTH l_len.
 WRITE: /5 sy-index, l_type, l_len.
Would like output as:
 1 AA C 10 instead of 1 C 10
 2 BB I 11 instead of 2 I 11
 3 CC C 20 instead of 3 C 20
ENDDO.
Regards,
Rao A

Hi,
Using your sample structure you can do it using such a code:
DATA: BEGIN OF G_TEST,
 AA(10) TYPE C,
 BB TYPE I,
 CC(20) TYPE C,
 END OF G_TEST.
TYPE-POOLS: ABAP.
DATA: COMP TYPE LINE OF ABAP_COMPDESCR_TAB.
DATA: STRUCT_REF TYPE REF TO CL_ABAP_STRUCTDESCR.
STRUCT_REF ?= CL_ABAP_STRUCTDESCR=>DESCRIBE_BY_DATA( G_TEST ).
LOOP AT STRUCT_REF->COMPONENTS INTO COMP.
 WRITE:/ COMP-NAME, COMP-TYPE_KIND, COMP-LENGTH, COMP-DECIMALS.
ENDLOOP.
Krzys

Problem in accessing field symbols passed as parameters to subroutine

Hi,
I have different internal tables/structures,i am populating those tables dynamically using field symbols. If i put that logic in perform, i am getting error while accessing the field symbol insdie the form.
For ex: My code looks like below.
tab1 is my int table, fs1 is my work area,
declared <fs1> as
data: <fs1> type fs1. <fs1> is my structure type.
perform populate tables tab1
 using <fs1>
 fs1.
form populate tables p_tab
 using p_fs
 p_wa.
assign p_wa to p_fs.
endform.
i am getting the error in the assign stmt
logic without form...endform is
assign fs1 to <fs1>
logic was working fine wihtout perform.
Regards,
sowjanya

Hi Sowjanya,
Try this one, Hope it will solve your issue
REPORT ztest_fs_create.
DATA: gt_final TYPE STANDARD TABLE OF pernr_d,
 wa_final TYPE pernr_d.
NODES pernr.
TABLES pa0001.
FIELD-SYMBOLS: <tab> TYPE pernr-pernr.
GET pernr.
ASSIGN pernr-pernr TO <tab>.
PERFORM get_pernr USING <tab>.
END-OF-SELECTION.
LOOP AT gt_final INTO wa_final.
 WRITE:/1 wa_final.
ENDLOOP.
*& Form gt_pernr
 text
 -->P_TAB text
FORM get_pernr USING p_tab TYPE any.
APPEND p_tab TO gt_final.
ENDFORM. "gt_pernr
Cheers
Pavan

Field symbols not working in data transfer VOFM routine

Hi,
I have been trying to set a value using field symbols, however for some reasons its not working. I am using a field symbol in a data transfer routine and the value which I am trying to set is a standard field outside the VOFM routine code.
I am trying to set a field gla_subrc which is actually a changing parameter.
The actual paramter is gn_subrc of type sy-subrc and within the form the name is gla_subrc. I need to set this changing parameter gla_subrc using the data transfer routine.
Is there a specific rule that field symbols dont work for changing paramters within subroutine or is there a specific syntax.
The syntax I am using is
ASSIGN ('(SAPLV50S)gla_subrc') to <fs>.
I also used the local program name instead of main program but still that does not work. Tried using the actual parameter as well.
Can someone please help me in this.
Thanks & Regards,
Naresh.

I need to stop outbound delivery creation against STO using vl10b transaction. The only way to stop creation is using data transfer delivery VOFM routine.
If i give an error message MESSAGE E001, this will give a hard error which is not acceptable. To avoid this, i use a perform message statment with message id and certain parameters which can displayed in a log.
However to make sure this message is displayed in log, I am clearing a work area having specific data needed for delivery creation.
Because of this clear, my error message gets captured in log but along with this another fake message is displayed in log which caused by the clear message.
The user gets confused as he now sees 2 messages, 1 which is correct and other 1 which is fake and that confuses him.
Data transfer routine is not the best place to give messages in log but we have very few options. The only way the system can give 1 message is if i set gla_subrc to 1. This is a variable which will help the system understand that the delivery should not be created as there is something wrong because the value is 1. Hence it will stop the creation and instead display whatever message i had passed to the log.
I need to somehow set this variable to 1 based on lot of analysis that has been done in the past.
Please let me know if there is any way by which we can fix this.
Thanks & Regards,
Naresh.

Passing unassigned field symbols to a method

Hello Gurus,
I work with a field symbol in a method and after the work is finished i have to use it i my program that i call the method from.
The problem is that the field symbol gets assigned only in the method so i can`t get the field symbol as a changing parameter in my method because it is not assigned yet.
I thought that i can return the field symbol from the method after it has been assigned, but i don`t know how. The <fs> is a dynamic itab that i created within the method.
Can anyone help please ??

Although already answered this code snippet might make it clearer
my_line is your data structure typically an itab structure.
For example
TYPES: BEGIN OF s_elements,
 tabname type DD02L-tabname,
 tabclass type dd02l-tabclass,
 as4user type dd02L-as4user,
 as4date type dd02l-as4date,
 as4time type DD02l-as4time,
 viewed(1) type c.
TYPES: END OF s_elements.
Data: my_line TYPE s_elements.
1) get the structure of your itab automatically so you can build an FCAT simply for any structure without the horrendous usual coding to manipulate and create FCATS.
CALL METHOD me->return_structure
 EXPORTING
 my_line = my_line.
You need to make a table ZOGT data available in the class definition either as an attribute if you are using the class builder SE24 or as DATA in the relevant class section.
data:
 zog LIKE LINE OF lr_rtti_struc->components .
data:
zogt LIKE TABLE OF zog .
method RETURN_STRUCTURE.
lr_rtti_struc ?= cl_abap_structdescr=>describe_by_data( my_line ).
 zogt[] = lr_rtti_struc->components.
endmethod.
Your structure details are now in table zogt.
Use this to build an FCAT.
CALL METHOD me->create_dynamic_fcat
 IMPORTING
 it_fldcat = it_fldcat.
method CREATE_DYNAMIC_FCAT.
LOOP AT zogt INTO zog.
 CLEAR wa_it_fldcat.
 wa_it_fldcat-fieldname = zog-name .
 wa_it_fldcat-datatype = zog-type_kind.
 wa_it_fldcat-inttype = zog-type_kind.
 wa_it_fldcat-intlen = zog-length.
 wa_it_fldcat-decimals = zog-decimals.
 wa_it_fldcat-coltext = zog-name.
 wa_it_fldcat-lowercase = 'X'.
 APPEND wa_it_fldcat TO it_fldcat .
 ENDLOOP.
endmethod.
Now having got your FCAT you can build your dynamic table.
 CALL METHOD me->create_dynamic_table
 EXPORTING
 it_fldcat = it_fldcat
 IMPORTING
 dy_table = dy_table.
(dy_table is defined as ref to data)
method CREATE_DYNAMIC_TABLE.
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = it_fldcat
 IMPORTING
 ep_table = dy_table.
endmethod.
Now populate your dynamic table as per sample code here
field_symbols:
<dyn_table> TYPE STANDARD TABLE.
<dyn_wa>.
data: dy_line TYPE REF TO data.
FORM populate_dynamic_itab.
ASSIGN dy_table->* TO <dyn_table>.
 CREATE DATA dy_line LIKE LINE OF <dyn_table>.
ASSIGN dy_line->* TO <dyn_wa>.
SELECT *
 FROM DD02L
 INTO CORRESPONDING FIELDS OF TABLE <dyn_table>
 WHERE TABNAME LIKE 'ZHR%'.
ENDFORM.
Now you can display your grid and process your data.
CALL METHOD z_object->display_grid
 EXPORTING
 g_outtab = <dyn_table>
 g_fldcat = it_fldcat
 i_gridtitle = i_gridtitle
 i_edit = i_edit
 i_zebra = i_zebra
 CHANGING
 it_fldcat = it_fldcat
 gt_outtab = <dyn_table>.
In the Method
method DISPLAY_GRID.
GET REFERENCE OF g_outtab INTO g_outtab1.
 GET REFERENCE OF g_fldcat INTO g_fldcat1.
 struct_grid_lset-edit = i_edit. "To enable editing
 struct_grid_LSET-zebra = i_zebra.
 struct_grid_lset-grid_title = i_gridtitle.
 struct_grid_lset-ctab_fname = 'T_CELLCOLORS'.
 struct_grid_lset-stylefname = 'CELLTAB'.
 CALL METHOD grid1->set_ready_for_input
 EXPORTING
 i_ready_for_input = '1'.
 CALL METHOD grid1->set_table_for_first_display
 EXPORTING
 is_layout = struct_grid_lset
 CHANGING
 it_outtab = gt_outtab
 it_fieldcatalog = it_fldcat.
ENDMETHOD.
You can even easily code your own column names if you so wish in the application program.
Before calling the method that displays the grid encode the following macro.
DEFINE col_name.
read table it_fldcat into wa_it_fldcat index &1.
wa_it_fldcat-coltext = &2.
wa_it_fldcat-outputlen = &3.
modify it_fldcat from wa_it_fldcat index &1.
END-OF-DEFINITION.
Then have a subroutine in your application code something like this
Form name_columns.
Here before displaying you can change the field catalog to
adjust your own column names.
*col_name col-nr 'your name' output length.
 col_name 1 'Table name' 30.
 col_name 2 'Table class' 12.
 col_name 3 'Changed By' 12.
 col_name 4 ' On' 12.
 col_name 5 ' At' 8.
 col_name 6 'Act' 3.
i_gridtitle = 'HR ESS / ITS ZHR Tables - Double click to display'.
i_zebra = 'X'.
i_edit = ' '.
endform.
Hope this clears it up a bit.
Once you get this stuff working you can re-use 99% of the code for almost any structure making the whole process of OO ALV grid applications really simple.
Yoy only need as well a standard dynpro with a custom container on it (se51).
Cheers
jimbo

How to use field symbols

can anyone tell me how to use field symbols. What effect it has on performance of a program?
what r its avantages?
iam working on a report where iam facing a lot of problems in performance issue. can anyone tell how field symbols are useful in this regard?
thanx to all

Check the below links
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/content.htm
FIELD-SYMBOLS
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.

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

Field Symbol as Subroutines name?

Similar Messages

Maybe you are looking for