Field symbol showing only 10 character

<FIELD1> TYPE ANY,
declraing like above is displaying on 10 character?

data : <header > type any,
          <field1> type any.
*Create dynamic internal table
CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
    EXPORTING
      IT_FIELDCATALOG = LT_LVC_CAT1
    IMPORTING
      EP_TABLE        = LP_TABLE1.
ASSIGN LP_TABLE1->* TO <LT_DATA1>.
*Create structure = structure of the internal table
CREATE DATA LP_STRUCT1 LIKE LINE OF <LT_DATA1>.
ASSIGN LP_STRUCT1->* TO <HEADER1>.
LOOP AT IT_MATNR INTO WA_MATNR.
    MOVE WA_MATNR-MATNR TO L_COL.
*&--Assinging Data to table
    ASSIGN COMPONENT 'MATNR' OF STRUCTURE <HEADER1> TO <FIELD1>.
    <FIELD1> = WA_MATNR-MATNR.
above <field1> and header accamodating only 10 charcter while matnr is 18 char flds.

Similar Messages

GBP currency symbol showing an extra character.

Hi
We're using Oracle Apps 11.5.10 running under Linux with XML Publisher 5.6.
We are developing an invoice template (RTF) that is muti currency. Our instance is defaulted to NLS_TERRITORY=AMERICA but when we are running a concurrent program to generate the XML file and base on the billing currency, we set the session to its corresponding language (ex: NLS_TERRITORY=UNITED KINGDOM'). In the case of GBP, the XML file does show the "£" in the invoice amount field. But when you look at the PDF file that it generates, the invoice amount has an extra character before the sterling pound symbol:
Â£1,000.00
I tried the <?format-currency:INVOICE_AMOUNT;'GBP'?> but to no avail.
Any help would greatly appreciated.

Hi,
Please check the thread Re: Â£ is being reported in Oracle reports instead of £
Cheers!
Gautam

What is field symbols?

Hi all,
Can anyone explains what is Fiels symbol and significance of that with examples?
Thanks
Shiva

HI Shiva
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
To declare a field symbol, use the statement
FIELD-SYMBOLS <FS> [<type>|STRUCTURE <s> DEFAULT <wa>].
For field symbols, the angle brackets are part of the syntax. They identify field symbols in the program code.
If you do not specify any additions, the field symbol <FS> can have data objects of any type assigned to it. When you assign a data object, the field symbol inherits its technical attributes. The data type of the assigned data object becomes the actual data type of the field symbol.
Note: it is possible to assign reference variables and structured data objects to untyped field symbols. However, the static field symbol is only a pointer to the field in memory, and does not have the complex type attributes of a reference or structured field until runtime. You can only use the field symbol to address the whole field (for example, in a MOVE statement). Specific statements such as CREATE OBJECT <FS> or LOOP AT <FS> are not possible.
Typing Field Symbols
The <type> addition allows you to specify the type of a field symbol. When you assign a data object to a field symbol, the system checks whether the type of the data object you are trying to assign is compatible with that of the field symbol. If the types are not compatible or convertible, the system reacts with a syntax or runtime error. If however, you want to assign the type of the field symbol to the data object by means of casting, you must do so explicitly using the ASSIGN statement. The system then treats the assigned data object as if it had the same type as the field symbol.
You specify the type of a field symbol using the same semantics as for formal parameters in procedures. For <type> you can enter either TYPE <t> or LIKE <f>. You can specify the type either generically or in full. If you specify a generic type, the type of the field symbol is either partially specified or not specified at all. Any attributes that are not specified are inherited from the corresponding data object in the ASSIGN statement. If you specify the type fully, all of the technical attributes of the field symbol are determined when you define it. You can then only assign data objects to it that have exactly the same data type.
You should always specify a type for each field symbol. If you cannot avoid defining a generic field symbol, make this clear by using an appropriate generic type declaration.
Generic Type Specification
The following types allow you more freedom when using actual parameters. The data object only needs to have the selection of attributes specified.
Typing
Check for data object
No type specification
TYPE ANY
All types of data object are accepted. The field symbol adopts all of the attributes of the data object.
TYPE C, N, P, or X
Only data objects with type C, N, P, or X are accepted. The field symbol adopts the field length and DECIMALS specification (type P) of the data object.
TYPE TABLE
The system checks whether the data object is a standard internal table. This is a shortened form of TYPE STANDARD TABLE (see below).
TYPE ANY TABLE
The system checks whether the data object is an internal table. The field symbol inherits all of the attributes (line type, table type, key) from the data object.
TYPE INDEX TABLE
The system checks whether the data object is an index table (standard or sorted table). The field symbol inherits all of the attributes (line type, table type, key) from the data object.
TYPE STANDARD TABLE
The system checks whether the data object is a standard internal table. The field symbol inherits all of the remaining attributes (line type, key) from the data object.
TYPE SORTED TABLE
The system checks whether the actual parameter is a sorted internal table. The field symbol inherits all of the remaining attributes (line type, key) from the data object.
TYPE HASHED TABLE
The system checks whether the actual parameter is a hashed internal table. The field symbol inherits all of the remaining attributes (line type, key) from the data object.
If you specify a type generically, remember that the attributes inherited by the field symbol from the program are not statically recognizable in the program. You can, at most, address them dynamically.
TYPES: BEGIN OF line,
         col1 TYPE c,
         col2 TYPE c,
       END OF line.
DATA: wa TYPE line,
      itab TYPE HASHED TABLE OF line WITH UNIQUE KEY col1,
      key(4) TYPE c VALUE 'COL1'.
FIELD-SYMBOLS <fs> TYPE ANY TABLE.
ASSIGN itab TO <fs>.
READ TABLE <fs> WITH TABLE KEY (key) = 'X' INTO wa.
The internal table ITAB is assigned to the generic field symbol <FS>, after which it is possible to address the table key of the field symbol dynamically. However, the static address
READ TABLE <fs> WITH TABLE KEY col1 = 'X' INTO wa.
is not possible syntactically, since the field symbol does not adopt the key of table ITAB until runtime. In the program, the type specification ANY TABLE only indicates that <FS> is a table. If the type had been ANY (or no type had been specified at all), even the specific internal table statement READ TABLE <FS> would not have been possible.
If you adopt a structured type generically (a structure, or a table with structured line type), the individual components cannot be addressed in the program either statically or dynamically. In this case, you would have to work with further field symbols and the method of assigning structures component by component.
Specifying the Type Fully
When you use the following types, the technical attributes of the field symbols are fully specified. The technical attributes of the data objects must correspond to those of the field symbol.
Typing
Technical attributes of the field symbol
TYPE D, F, I, or T
The field symbol has the technical attributes of the predefined elementary type
TYPE <type>
The field symbol has the type <type>. This is a data type defined within the program using the TYPES statement, or a type from the ABAP Dictionary
TYPE REF TO <cif>|DATA
The field symbol is a reference variable for the class or interface <cif>, or for a data object.
TYPE LINE OF <itab>
The field symbol has the same type as a line of the internal table <itab> defined using a TYPES statement or defined in the ABAP Dictionary
LIKE <f>
The field symbol has the same type as an internal data object <f> or structure, or a database table from the ABAP Dictionary
When you use a field symbol that is fully typed, you can address its attributes statically in the program, since they are recognized in the source code. If you fully specify the type of a field symbol as a reference or structured data object, you can address it as you would the data object itself, once you have assigned an object to it. So, for example, you could address the components of a structure, loop through an internal table, or create an object with reference to a field symbol.
REPORT demo_field_symbols_type .
DATA: BEGIN OF line,
         col1(1) TYPE c,
         col2(1) TYPE c VALUE 'X',
       END OF line.
FIELD-SYMBOLS <fs> LIKE line.
ASSIGN line TO <fs>.
MOVE <fs>-col2 TO <fs>-col1.
The field symbol <FS> is fully typed as a structure, and you can address its components in the program.
Attaching a structure to a field symbol
The STRUCTURE addition forces a structured view of the data objects that you assign to a field symbol.
FIELD-SYMBOLS <FS> STRUCTURE <s> DEFAULT <f>.
The structure <s> is either a structured local data object in the program, or a flat structure from the ABAP Dictionary. <f> is a data object that must be assigned to the field symbol as a starting field. However, this assignment can be changed later using the ASSIGN statement.
When you assign a data object to the field symbol, the system only checks that it is at least as long as the structure. You can address the individual components of the field symbol. It has the same technical attributes as the structure <s>.
If <s> contains components with type I or F, you should remember the possible effects of alignment. When you assign a data object to a field symbol with a structure, the data object must have the same alignment, otherwise a runtime error may result. In such cases, you are advised to assign such data objects only to structured field symbols, which retain the same structure as the field symbol at least over the length of the structure.
The STRUCTURE is obsolete; you should no longer use it. Field symbols defined using the STRUCTURE addition are a mixture of typed field symbols and a utility for casting to either local or ABAP Dictionary data types. If you want to define the type of a field symbol, include the TYPE addition in a FIELD-SYMBOLS statement. If you want to use casting, include the CASTING addition in an ASSIGN statement.
Example using the obsolete STRUCTURE addition:
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> STRUCTURE line1 DEFAULT wa,
               <f2> STRUCTURE line2 DEFAULT wa.
WRITE: / <f1>-col1, <f1>-col2, <f1>-col3,
       / <f2>-col1, <f2>-col2.
Example using the correct syntax (TYPE and CASTING):
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.
In both cases, the list appears as follows:
012 34 56789
01 2345/67/89
This example declares two field symbols to which different structures are attached. The string WA is then assigned to each of them. The output shows that the field symbols assign the strings component by component according to the type of the components.
Assigning Components of Structures to a Field Symbol
For a structured data object <s>, you can use the statement
ASSIGN COMPONENT <comp> OF STRUCTURE <s> TO <FS>.
to assign one of its components <comp> to the field symbol <FS>. You can specify the component <comp> either as a literal or a variable. If <comp> is of type C or a structure that has no internal tables as components, it specifies the name of the component. If <comp> has any other elementary data type, it is converted to type I and specifies the number of the component. If the assignment is successful, SY-SUBRC is set to 0. Otherwise, it is set to 4.
This statement is particularly important for addressing components of structured data objects dynamically. If you assign a data object to a field symbol either generically or using casting, or pass it generically (or using casting) to the parameter interface of a procedure, you cannot address its components either statically or dynamically. Instead, you must use the above statement. This allows indirect access either using the component name or its index number.
DATA: BEGIN OF LINE,
        COL1 TYPE I VALUE '11',
        COL2 TYPE I VALUE '22',
        COL3 TYPE I VALUE '33',
      END OF LINE.
DATA COMP(5) VALUE 'COL3'.
FIELD-SYMBOLS: <F1>, <F2>, <F3>.
ASSIGN LINE TO <F1>.
ASSIGN COMP TO <F2>.
DO 3 TIMES.
ASSIGN COMPONENT SY-INDEX OF STRUCTURE <F1> TO <F3>.
WRITE <F3>.
ENDDO.
ASSIGN COMPONENT <F2> OF STRUCTURE <F1> TO <F3>.
WRITE / <F3>.
The output is:
11         22         33
33
The field symbol <F1> points to the structure LINE, <F2> points to the field COMP. In the DO loop, the components of LINE are specified by their numbers and assigned one by one to <F3>. After the loop, the component COL3 of LINE is specified by its name and assigned to <F3>. Note that ASSIGN COMPONENT is the only possible method of addressing the components of <F1>. Expressions such as <F1>-COL1 are syntactically incorrect.
Regards,
Laxmi.

Text field not showing record set options

I entered the following php code to a text field in a form:
<p>
      <label for="date">Select Available Date</label>
      <select name="date" class="text" id="date">
        <option value="0" selected="selected">select your preferred travel date</option>
            <?php while ($row_rsDep = mysql_fetch_assoc($rsDep)) {
                  echo '<option>' . date('d.m.Y',strtotime($row_rsDep['Start_Date_Eur'])) . ' - ' . date('d.m.Y',strtotime($row_rsDep['End_Date_Del'])) . '-' . $row_rsDep['Itinerary_Code'] . '</option>';
          ?>
      </select>
    </p>
In the text field it shows only the option=0 "select your preferred travel date" and does not show the rest of the options as available from the database.
Any idea what is wrong with my code?
Thanks,
zabberwan

I do have it showing in the sidebar showing as a repeating region. I commented it out and entered your code, but this time it shows nothing at all, not even an error!
The problem may have to do with "VIEWS" as I am working partly with Views on the external server. The server guys are having problems allowing Views. They did allow it for my account, but somehow this is not working. So I update my database leaving out the 3 tables created as views out of a total of 8. On the contrary on the local server the database is working fine, so that may not be the problem after all.
I had got it work a fortnight back, but lost it as I had to redo a few things with the forms it is in. On the sidebar it is working fine otherwise as a repeating region and showing all the dates of all itineraries. Only it's not working in the form, where it shows the preselected string (select your preferred travel date), but not the rest of the options.
About changing the email, one has to change the whole ID and profile etc. and then you can't log into your own account with the same user name, you have to have a different one, so that your own thread is no longer your own. What a pile of goons at the wheels! And what a disappointment with otherwise such a great bunch of forums.. I'll now have to contact the staff and would like them wipe out all my ID's and Profiles at Adobe and make a new one. It's such a rotten mess. This thing even ruined my ID at Adobe Browser Lab.
I suppose we'll leave it for Mr. Nobody to fix it, like so many other things especially around Christmas!
zabberwan

SQL Subscription field shows * only with Dynamic Text Label in SQL query

We are using Hyperion Analyzer 7.2.x for showing budget and actual data. I have to show this financial data based on the security e.g. person in IT can see only IT dept. data. Hence I want to use dynamic text label <<userid>> for the security based on the person logging in to Analyzer.
But when I use dynamic text label <<userid>> in the SQL query in SQL Spreadsheet, SQL Subscription field shows * only selection option. Does anyone have idea how to solve this problem?
Thanks in advance for your help.
-SV

Hi
Okay i know this is a bit crazy way.....but i think this is the solution for your issue.
Create a report without the where clause (<<useris>>) then add a filter (sql subscription) then you can find all the values that are there in the SQL field (try to increase the query limit it is set to 250 as default) then edit the spreadsheet and add the where clause (<<userid>>).
This will help you having the filter and the dynamic text label. I think there is an issue when you try to filter it with a where clause.
Hope it helps.
CK

Even though am using Field-Symbol correctly, showing error!!!

Hello
Below is my code,
LOOP AT itab_data INTO <fs_data>.
   CHECK <fs_data>-error_flag = 'X'.
   READ TABLE itab_docnum INTO <fs_docnum>
    WITH KEY docnum = <fs_data>+4(16)
    BINARY SEARCH.
LOOP AT itab_data INTO <fs_data>.
   CHECK <fs_data>+1(10) <> 'END_REC'(025) AND
         <fs_data>+1(10) <> 'BEGIN_REC'(026).
     ASSIGN <fs_data>+1(*) TO <fs_edid2> CASTING.
     <fs_data> = <fs_edid2>.
   MOVE-CORRESPONDING <fs_data> TO w_edi_dd.
   <fs_data>+1    = w_edi_dd.
But, am getting the below error message in SLIN/Extended Prog Check.
Fieldsymbol <FS_DATA> is not assigned to a field
(The message can be hidden with "#EC *)
1) I do not understand why am getting this (if itab contains any data then ONLY the loop will be executed right?)
2) How to correct this?
Thank you

Hello,
Correct method of using a field-symbol is to assign it first with the structure.
You use INTO if working with work area. Example:
LOOP AT itab_data INTO w_data.
Use assigning keyword when using field-symbol in case of LOOP...ENDLOOP.
LOOP AT itab_data ASSIGNING <fs_data>.
Check below link on 'Assigning Data Objects to Field Symbols':
http://help.sap.com/SAPhelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/frameset.htm
Hope it helps!
Regards,
Saba
Edited by: Saba Sayed on Feb 27, 2011 11:35 PM

Jpa native query returns only first character of a field

Hi,
I've a JPA native query that returns two fields from my oracle database. The first field is a CHAR(2) field with two char values in it, like 'OZ' etc.
The problem is, as soon as the query is executed it returns only first character of field1. If the actual value of field1 is like 'OZ' then it returns only 'Z'.
Query nativeQueryForProfileInfo = getManager().createNativeQuery(queryToRun);
List list = nativeQueryForProfileInfo.getResultList();
Please help,
thanks

There could be several explanations here and it's difficult to say without having more details, possibilities are
There is something wrong with your display logic.
There is something wrong with your mapping.

Copying an internal table data to a field symbol(only corresponding field)

Hi,
   Iam having field symbol type standard table which has 4 fields in it already.
I am having an internal table which has 10 columns in it.
Now i want to copy the data from internal table to field symbol .But the problem is the fields which are matched in field symbol alone should be copied from the internal table.
for eg.
field symbol type table.
field1.
field2.
field3.
itab type internal table.
field1
field2
field3
field4
field5
field6.
i want to copy the first 3 fields alone from the internal table itab to the field symbols. Can anyone help me on how to do this. thanks...
Regards,
Rose.

Hi,
Chk below example, and match with ur scenario.
data: begin of itab,
      a , b ,c , d,e,
      end of itab,
      wa like itab,
      jtab like table of itab,
      begin of fsy,
      a, b ,c,
      end of fsy.
field-symbols:<fs> type any.
     assign fsy to <fs>.
     wa-a = 'x'. wa-b = 'y'. wa-c = 'z'. wa-d = 'r'.
     append wa to jtab.
      loop at jtab into wa.
        move-corresponding wa to <fs>.
      endloop.
REGARDS,
SENTHIL KUMAR.S

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

Loop at field-symbol (any table) into string ?

Hi Everyone,
I need little help, I have a requirement to extract table content with columns names as the header.
After doing some search I figured out the best way to this since table name will be only avaialbe at runtime through
a selection field . my problem is to loop through field-symbol and convert a structure to string value so that I can
write to the file.
REPORT zlab_tbl_export.
DATA table_name(30) VALUE 'ZSMARTTS_HTML'.
DATA v_file(100) VALUE 'c:\sap_export.txt'.
DATA line(1000).
DATA: o_data TYPE REF TO data.
CREATE DATA o_data TYPE TABLE OF (table_name).
FIELD-SYMBOLS: <table> TYPE ANY TABLE.
ASSIGN o_data->* TO <table>.
SELECT * UP TO 100 ROWS FROM (table_name) INTO TABLE <table>.
OPEN DATASET v_file FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
>>>>>>> LOOP at <table> into line.   >>>>>>>>>>>> " Here the code breaks and fail
TRANSFER line to v_file.
WRITE :/ line.
ENDLOOP.
CLOSE DATASET v_file.
Exception Message
|Error analysis                                                                                |
|    You attempted to move one data object to another.                                             |
|    This is not possible here because the conversion of a data object                             |
|    of type "v" to type "C" is not supported.                                                     |
|                                                                                |
|      List of internal ABAP types:                                                                |
|                                                                                |
|      C    Text (Character)                                                                       |
|      N    Numerical text                                                                         |
|      D    Date (YYYYMMDD)                                                                        |
|      T    Time (HHMMSS)                                                                          |
|      X    Hexadecimal                                                                            |
|      I    Integer                                                                                |
|      P    Packed number                                                                          |
|      F    Floating point number                                                                  |
|                                                                                |
|      h    Internal table                                                                         |
|      r    Object reference                                                                       |
|      l    Data reference                                                                         |
|      g    String of type C                                                                       |
|      y    String of type X                                                                       |
|      s    2-byte integer with plus/minus sign                                                    |
|      b    1-byte integer without plus/minus sign                                                 |
|      u    Structure (flat structure)                                                             |
|      v    Structure (deep structure)                                                             |

Hi Everyone, I need little help, I have a requirement to extract table content with columns names as the header. After doing some search I figured out the best way to this since table name will be only avaialbe at runtime through a selection field . my problem is to loop through field-symbol and convert a structure to string value so that I can write to the file.
thie is the code
REPORT zlab_tbl_export.
DATA table_name(30) VALUE 'ZSMARTTS_HTML'.
DATA v_file(100) VALUE 'c:\sap_export.txt'.
DATA line(1000).
DATA: o_data TYPE REF TO data.
CREATE DATA o_data TYPE TABLE OF (table_name).
FIELD-SYMBOLS: <table> TYPE ANY TABLE.
ASSIGN o_data->* TO <table>.
SELECT * UP TO 100 ROWS FROM (table_name) INTO TABLE <table>.
OPEN DATASET v_file FOR OUTPUT IN TEXT MODE ENCODING DEFAULT.
LOOP at <table> into line.   " Fail here
TRANSFER line to v_file.
WRITE :/ line.
ENDLOOP.
CLOSE DATASET v_file.
and this is the exception:
Error analysis
You attempted to move one data object to another.
    This is not possible here because the conversion of a data object
    of type v to type C is not supported.
Edited by: Misbah on Jan 7, 2010 11:50 PM

Assign Type conflict with field symbols

I have two tables tab1 & tab2, want to assign field values from tab1 to tab2 suing field symbols. Deatils are :
TYPES: BEGIN OF ty_tab1,
    item1   TYPE char20,
    item2   TYPE char20,
    val1 type i,
    val2 type i,
END OF ty_tab1,
BEGIN OF ty_tab2,
    item1 TYPE char20,
    item2 TYPE char20,
END OF ty_tab2.
DATA: it_tab1 TYPE TABLE OF ty_tab1,
            it_tab2 TYPE TABLE OF ty_tab2.
FIELD-SYMBOLS <fs_tab1> TYPE ty_tab1.
                 <fs_tab2t> type ty_tab2.
LOOP AT it_tab1 assigning <fs_tab1>.
    READ TABLE it_tab2 assigning <fs_tab2> WITH KEY item1 = <fs_tab1>-item1
                                                                                item2 = <fs_tab1>-item2.
    IF sy-subrc EQ 0.
      ASSIGN COMPONENT 'ITEM1' OF STRUCTURE <fs_tab1> TO <fs_tab2>.
     ASSIGN COMPONENT 'ITEM2' OF STRUCTURE <fs_tab1> TO <fs_tab2>.
    endif.
endloop.
Getting error msg
You attempted to assign a field to a typed field symbol, but the field does not have the required type.
whats the reason of error.
Edited by: Matt on May 27, 2011 8:59 AM - added tags

Taken from example dump
A new value is to be assigned to the field "...", although this field is
entirely or partly protected against changes.
The following are protected against changes:
- Character literals or numeric literals
- Constants (CONSTANTS)
- Parameters of the category IMPORTING REFERENCE for functions and
methods
- Untyped field symbols not yet assigned a field using ASSIGN
- TABLES parameters if the actual parameter is protected against changes
- USING reference parameters and CHANGING parameters for FORMs, if the
actual parameter is protected against changes and
- Accesses using field symbols if the field assigned using ASSIGN is
protected (or partially protected, e.g. key components of an internal
table with the type SORTED or HASHED TABLE) against changes
- Accesses using references, if the field bound to the reference is
protected (or partially protected) against changes
- External write accesses to READ-ONLY attributes,
- Content of a shared object area instance accessed using a shared lock
(ATTACH_FOR_READ).
You likely fall in one of these cases. Check each and if still unsure please share your code so we can reproduce the error.
Regards
Marcin

Problem with field-symbol values not updating

H i ,
      I have following piece of code :
Assigning Dynamic Table to Field Symbol
    ASSIGN ist_dyn_table->* TO <gs_dyn_table>.
*   Creating Structure for dynamic table
    CREATE DATA gs_dyn_line LIKE LINE OF <gs_dyn_table>.
*   Creating line type for the Dynamic Values
    ASSIGN gs_dyn_line->* TO <gs_line>.
*   Populating values in the dynamic table
    LOOP AT ist_pwcl_main INTO wa_pwcl_main.
      ASSIGN COMPONENT gc_fld_werks OF STRUCTURE <gs_line> TO <gs_field>.
   1   IF sy-subrc EQ 0.
   2        <gs_field> = wa_pwcl_main-werks.
   3      ENDIF.
   5 IF <gs_field> IS ASSIGNED.
   6     <gs_field> = wa_pwcl_main-vbeln.
      ENDIF.
7 IF <gs_field> IS ASSIGNED.
8 <gs_field> = wa_pwcl_main-posnr.
      ENDIF.
   IF <gs_field> IS ASSIGNED.
        <gs_field> = wa_pwcl_main-quant.
      ENDIF.
on debugging at line 2 <gs_filed> contains the value of werks .
but at line 6 <gs_field> contains value of vbeln as 0 and at 8 of posnr as 0 .
What can be the problem ? Other values are getting assigned properly .
Plz help ...
Regards .

Hi,
Assigning Dynamic Table to Field Symbol
    ASSIGN ist_dyn_table->* TO <gs_dyn_table>.
Creating Structure for dynamic table
    CREATE DATA gs_dyn_line LIKE LINE OF <gs_dyn_table>.
Creating line type for the Dynamic Values
    ASSIGN gs_dyn_line->* TO <gs_line>.
Populating values in the dynamic table
    LOOP AT ist_pwcl_main INTO wa_pwcl_main.
      ASSIGN COMPONENT gc_fld_werks OF STRUCTURE <gs_line> TO <gs_field>.
   1   IF sy-subrc EQ 0.
   2        <gs_field> = wa_pwcl_main-werks.
   3      ENDIF.
   5 IF <gs_field> IS ASSIGNED.
   6     <gs_field> = wa_pwcl_main-vbeln.
      ENDIF.
7 IF <gs_field> IS ASSIGNED.
8 <gs_field> = wa_pwcl_main-posnr.
      ENDIF.
   IF <gs_field> IS ASSIGNED.
        <gs_field> = wa_pwcl_main-quant.
      ENDIF.
Based on your coding above, <gs_field> has been assigned with data type 'WERKS' (i'd assume component gc_fld_werks found from structure <gs_line> is a plant typed), which is a CHAR(4) data type.
Meaning, if <gs_field> is assigned with Plant type value, e.g. <gs_field> = '1000', field symbol <gs_field> will contain 4 character only.
At line 6, if wa_pwcl_main-vbeln = '0000201000', <gs_field> is only capturing '0000' only. This is also happened to line 8.
However, it looks like that <gs_field> is getting over-write if ASSIGNED statement returns SY-SUBRC = 0.
Hope this helps.
Regards,
Patrick

Declaring Field Symbols in a work area

Hi all!
I'm triying to learn the use of FieldSymbols, and I wrote in my code this:
REPORT zpractica01.
Types
TYPES: BEGIN OF ty_tabla,
        name(25)    TYPE c,
        address(60) TYPE c,
        monto(3)     TYPE p decimals 2,
        END OF ty_tabla.
Internal Table
DATA: t_tabla TYPE STANDARD TABLE OF ty_tabla.
*Work Area
DATA: vl_variable TYPE c LENGTH 512.
Field Symbols
FIELD-SYMBOLS <linea> STRUCTURE st_tabla DEFAULT vl_variable.
If I try to activate the code I see this error:
In the Unicode context, the structure <LINEA> typed using STRUCTURE can only contain character-type components (type C,N,D,T).
I can see that the problem begins when I use a type P inside the structure, but I need to have a type P, so I would like to know how can i use it.
Could you please teach me how I should declare my field symbols in order to use as an structure with a type P field within a loop at - endloop?
I'll really appreciate your help.
Best regards!
Gaby
Edited by: gpsoria on Aug 24, 2009 4:30 PM

Hello Gaby,
You are getting the error because the structure st_tabla & variable vl_variable are not mutually convertible in a Unicode environment.
Just change the definition of vl_variable & you code will activate.
REPORT zpractica01.
* Types
TYPES: BEGIN OF ty_tabla,
name(25) TYPE c,
address(60) TYPE c,
monto(3) TYPE p decimals 2,
END OF ty_tabla.
* Internal Table
DATA: t_tabla TYPE STANDARD TABLE OF ty_tabla.
*Work Area
DATA: st_tabla TYPE ty_tabla. "--> Add this line
DATA: vl_variable TYPE ty_tabla. "c LENGTH 512.
* Field Symbols
FIELD-SYMBOLS <linea> STRUCTURE st_tabla DEFAULT vl_variable.
*I will suggest decalre like this:
FIELD-SYMBOLS <linea1> TYPE ty_tabla.
Hope i am clear.
BR,
Suhas

Field symbols in SMARTFORMS

Hi all,
I have to show the Item wise amount in a Purchase order thro SMARTFORM. I don't have any problem when the purchase order has currency 'INR'. But when the Purchase order contains foreign currency, I have to show the amount upto 4 decimals. How can I show amount upto 4 decimals only when the amount is in foreign currency?I have tried to create a field-symbol with type ANY.But it's showing error.Please help.

try this
&symbol(.N)& Display upto N decimal places
other options:
&symbol(Z)& Omit Leading Zeros
&symbol(S)& Omit Leading Sign
&symbol(<)& Display Leading Sign to the Left
&symbol(>)& Display Leading Sign to the Right
&symbol(C)& Compress Spaces
&symbol(.N)& Display upto N decimal places
&symbol(T)& Omit thousands separator
&symbol(R)& Right justified
&symbol(I)& Suppress output of the initial value
reward if helpful

Field symbols in objects

Hi Guys
I am using a field sym in the foll way and iam getting a dump.
ls_fcat = mod_fcat( ls_fcat ).
method mod_fcat.
   field-SYMBOLS: <l> like line of rt.
    LOOP AT rt ASSIGNING <l>.
      CASE <l>-fieldname.
        WHEN 'VALUE_CONTRACT_E'.
        CLEAR: <l>-ref_field,<l>-ref_table.
        <l>-coltext   = text-h01. <l>-SCRTEXT_L = text-h01.
        <l>-SCRTEXT_M = text-h02. <l>-SCRTEXT_S = text-h02.
        WHEN OTHERS.
      ENDCASE.
    ENDLOOP.
ENDMETHOD.
endmethod.
When the control goes to clear it gives me a dump.I dont understand why coz iam already assignin <l> at every loop pass.
Please help!!
Thanks

Hi Guys
This is the error i get
A new value is to be assigned to the field "<L>", although this field is entirely or partly protected against changes.
The following are protected against changes:
- Character literals or numeric literals
- Constants (CONSTANTS)
- Parameters of the category IMPORTING REFERENCE for functions and
methods
- Untyped field symbols not yet assigned a field using ASSIGN
- TABLES parameters if the actual parameter is protected against changes
- USING reference parameters and CHANGING parameters for FORMs, if the
actual parameter is protected against changes and
- Accesses using field symbols if the field assigned using ASSIGN is
protected (or partially protected, e.g. key components of an internal
table with the type SORTED or HASHED TABLE) against changes
- Accesses using references, if the field bound to the reference is
protected (or partially protected) against changes
- External write accesses to READ-ONLY attributes,
- Content of a shared object area instance accessed using a shared lock
(ATTACH_FOR_READ).
Thanks

Field symbol showing only 10 character

Similar Messages

Maybe you are looking for