BAPI_QUALNOT_CREATE and field Reference no.

Hi masters.
I need to create Quality Notifications via BAPI, but the bapi BAPI_QUALNOT_CREATE does not have a field to fill out the "
External Reference Number"
How can I set this field via BAPI calls ?
It is the field REFNUM in the table QMEL

Sorry. Currently no way in standard BAPI.
And more fields (reference QTY, malfunction date) are also not exist.
The only way is using the BAdI NOTIF_EVENT_SAVE.
Regards

Similar Messages

  • Key Figure Reference table and fields

    I am getting the following error:
    /BIC/CSSMMIMI1-/BIC/KFMI_LCHF (specify reference table AND reference field)
    I am aware that it is asking me to put a reference table and field for the field in the structure.
    However, what I am not sure about is should I do this action from SE11 or is there a program or other method which would be more suitable (this is not business content)?
    Thanks

    Hi Edwin,
    Thanks for that, the currency type and quantity type are hard coded in the key figure for most of the key figures apart from one, i.e for the quanity I hard code PCS
    From RSD2 I just check the repair option is that correct

  • How to update Tr code FB02   and update the field reference key1 (bseg-xref

    Can any body
    help me how to update   Tr code   fb02
    and  update the field  reference  key1 (bseg-xref1)  with the interest amount
    calculated.
    Below i have  written My  program  flow logic
    The program should read the open items i.e debit items in the customer account,
    Based on the  invoice date and customer payment terms  calculate the due date and then the  interest should be  calculated on that item based on the due date.
    Use the  transaction  fb02  and update the field  reference  key 1 (BSEG-xref1)
    with the interest amount calculated
    Only  consider  customers whose  interest indicator  knb1-vzskz = 'vk'.
    Interest is to be  calculated for every  30  days
    at the rate of  1% .please see example below.
    Document date is 01.01.2007
    for amount  1000SGD   payment  term  7  days
    It becomes  due  on  08.01.2007
    until  06.02.2007 you should not  consider  for calculation of interest
    SGD  on   7.02.2007 run you can consider this  item for interest calculation

    Hi Robert,
    Thanks for answering.
    I am looking at Ref 2 should flow automatically to clearing document from the accounitng document for billing.
    Ex: Billing document is created and accounted. Ref 2 is AB
    Now when receipt is accounted for this biling document this AB should flow automatically to Ref 2 field.
    Thanks
    NNS.

  • Reference Table and Fields for Units and Currency

    Can anyone advise on what the reference tables and fields are for currency and quantity key figures? Thanks
    I think for currency the table is TCURC and field is WAERS, does this make sense, not sure for the quantity though
    Message was edited by:
            Niten Shah

    Hi try these -
    TCURC          (Currency codes)
    TCURF          (Translation factors)
    TCURN          (Notations)
    TCURS          (Exchange Rate Spreads)
    TCURT          (Description of the Currency Code)
    TCURV          (Exchange rate types for currency translation)
    TCURW     (Use of exchange rate types)
    TCURX          (Decimal places of the currencies)
    Regards
    Vikash

  • ABAP field symbols and PERL reference variables to unnamed arrays.

    Rob -
    Please do NOT delete this post even though it contains this link:
    ABAP field symbols and PERL reference variables to unnamed arrays.
    to a question I posted in the Scripting Languages forum.
    It's a question that should be of interest to ABAP programmers, and they may miss if they don't frequent the SL forum ...
    Thanks for your forbearance here (in advance, of course) ...
    Best
    djh
    Edited by: Rob Burbank on Jul 11, 2011 1:26 PM

    If interested, please reply in the original thread. We don't want multiple conversations at cross purposes do we?
    Rob

  • Reference table and  field for Quantity

    what is the reference table and field for quantity ??

    HI,
    FOR A FIELD TYPE MENGE_D IN THE CURRENCY/QUANTITY FIED TAB,
    FILL IN REFERENCE FIELD WITH YOUR TABLE NAME AND AND REF FIELD WITH MEINS
    THANKS
    VENKI

  • Question -- ME22N - Field Reference obligatory and with a matchcode.

    Hi!
    The user has a new crazy requirement.
    The user needs the field REFERENCE (IHREZ) from tab Communication of TRX ME22N to be OBLIGATORY and alse wants a matchcode with two values.
    Any help is welcome.
    Regards.
    Bettina

    We added the values to the domain and we use some user exits to validate that the user complete the field.

  • Reg: Field Symbol and Data Reference

    Hi,
    What is the difference Between a FieldSymbol and Data Reference.
    could anyone explain with an example the difference.
    The Link I am Going Through ---> [SAP HELP|http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb3860358411d1829f0000e829fbfe/frameset.htm]
    I couldnt get a clear idea
    regards

    Hi,
    In ABAP/4 programs, field symbols are placeholders for existing fields. A field symbol does not physically reserve space for a field, but points to a field, which is not known until runtime of the program. Field symbols are comparable to the concept of pointers as used in the programming language C. In ABAP/4, however, there is no real equivalent to pointers in the sense of variables, which contain a memory address and can be used without the content operator. You can only work with the data object to which a field symbol points.
    uF076     Concept of Field Symbols
    Sometimes you only know which field you want to process, and how you want to process it, at runtime.
    For this purpose, you can create field symbols in your program. At runtime, you can assign real fields to such field symbols. All operations, which you have programmed with the field symbol, are then carried out with the assigned field. After successful assignment, there is no difference in ABAP/4 whether you reference the field symbol or the field itself.
    Field symbols can point to any data object in ABAP/4 and to structures defined in the ABAP/4 Dictionary.
    You can create field symbols either without or with type specifications. In the first case, the field symbol adopts all the attributes of the assigned field. In the second case, the system checks during the assignment process whether the assigned field matches the type of the field symbol. Whichever applies, you must first assign a field to your field symbol before you can work with it in your program.
    Field symbols provide some features that make them very flexible:
    uF071     You can specify the offset and length of the assigned field as variables.
    uF071     You can assign field symbols to other field symbols and even specify offset and length there.
    uF071     Assignments to field symbols may extend beyond field boundaries. This allows effective access to regularly stored data.
    uF071     You can force a field symbol to be of a different type and to have a different number of decimal places than the assigned field.
    uF071     Field symbols may have a structure that you can use to point to individual components of structures.
    Since you can assign data objects to field symbols which may not be known 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. Therefore, you should use field symbols only in cases where you are absolutely sure of what you are doing, or if there are no other ABAP/4 statements you can use to solve your problem. The advantage of field symbols is that they can improve response times in some cases.
    uF076     Defining Field Symbols
    uF0D8     Defining Field Symbols for Internal Fields
    To define a field symbol for an internal data object, use the FIELD-SYMBOLS statement as follows:
    Syntax-
    FIELD-SYMBOLS <FS> [<type>].
    This statement defines a field symbol <FS>.
    for data reference follow this link
    http://help.sap.com/saphelp_nw04s/helpdata/en/14/11e70b0c5c11d3b9350000e8353423/frameset.htm
    Regards,
    Flavya

  • Plz help me to find out tables and fields........based on SD,PM,FICO Module

    Hi plz help me to find out the table name and field names as i am unable to find .....In the spec am given requirements in the following pattern.
    Description          SAP-Term                                       Explaination
    1.Salesman        Equipment AC Mgr.                          VBPA2 – this is the salesman code - I need the                                                                               
    description for this.
    2.Vendor              MEPO_TOPLINE-SUPERFIELD     Vendor field is pull from me23n where the                                                                               
    condition will be that COBL-KDAUF (this is a
                                                                                    structure from me23n in item data-account
                                                                                    assignment-sales order. The number here should
                                                                                    be the corresponding contract number. This field
                                                                                    should include a multiple selection function. User                                                                               
    can put more than one description to search for.
    3. Val. Period   Val. Period Category                           Val. Period Category from va41 header-contract
        Category                                                               data. This field should include a multiple selection                                                                               
    function. User can put more than one description                                                                               
    to search for.
    4. Service Order/    CAUFVD-GSTRP/                         This should be the document date where by it is in
        Purchase Order      MEPO_TOPLINE-BEDAT          between the range the user input
        Document Date    
    5. B2B Vendor      MEPO_TOPLINE-SUPERFIELD     Vendor field is pull from me23n where the condition                                                                               
    will be that COBL-KDAUF (this is a structure from
                                                                                    me23n in item data-account assignment-sales                                                                               
    order. The number here should be the                                                                               
    corresponding contract number.
    6. B2B Cost         MEPO1211-NETPR                       This cost is pulled from PO (me23n) however take
                                                                                    note that the price will be pulled out base on line                                                                               
    item Net Price. Make sure that price is taken                                                                               
    corresponding only to the equipment tied to it.                                                                               
    Check on Number 7 to see how is the line item tied                                                                               
    to the equipment.                                                                               
    If this is in other currency please make it to SGD                                                                               
    with the exchange rate field Exchange rate                                                                               
    (MEPO1226-WKURS)
                                                                                  NOTE:: I need to know the table from which I can                                                                               
    determine the currency type as can be seen in the                                                                               
    ME23N transaction and also te exchange rate for                                                                               
    that particular currency.
    7. No of faults                                                          The service order (CAUFVD-AUFNR) created base                                                                               
    on the equipment in Number 8. This should exclude                                                                               
    the service order of type RD08. Service order can be                                                                               
    access by IW33.
    8. Faults Completed                                                This would be the number of faults (Number 13)                                                                               
    which has a system status (CAUFVD-STTXT) of                                                                               
    TECO. System status can be viewed in IW33 Sys.                                                                               
    Status. Take note service order type RD08 will be                                                                               
    excluded
    9. Time Spent on Fault   AFVGD-ISMNW                   This field is in IW41 in confirmation base on the                                                                               
    order created. This field will be the actual time                                                                               
    spent. This will correspond to the Faults                                                                               
    Completed (Number 14). This means only orders                                                                               
    with system status TECO will be pull. Take not                                                                               
    service order type RD08 will be excluded
    10. Fault Cost         RIHAUFK_LIST- DGESKOSIST   This will be the total cost for a service order which                                                                               
    have the status TECO. Those which are not TECO                                                                               
    will not be needed. This field can be obtain from                                                                               
    IW39 (standard report). Execute the report and                                                                               
    there will be a field for Total Actual Cost. You might                                                                               
    need to change the screen layout to be able to view                                                                               
    this. Take note service order type RD08 will be                                                                               
    excluded
    11. PM Hours      AFVGD-ISMNW                            This field is in IW41 in confirmation base on the
                                                                                 order created. This field will be the actual time
                                                                                 spent. This will correspond to the Faults Completed
                                                                                 This means only orders with system
                                                                                 status TECO will be pull. Take note service only
                                                                                 take order type RD08.
    12. Spare Cost   Spare part cost                              This field will be in IW33 under cost tab, and cost
                             PMCOEA-IKOSTENKGR                tab in item level. This will be the actual cost of spare
                                                                                 part after TECO. This will include all order type.
    13. Credit Note   Credit Memo                                 The programs need to pull out credit memo which is
                                                                                 reference from the contract. If there is a credit memo
                                                                                 reference from the contract then the value will be net
                                                                                 price per equipment.

    Can u tell me purpose of this spec ?
    Regards,
    pandu.

  • What are  the tables and fields  in fico & sd module

    what are  the tables and fields  in fico & sd module

    Hi,
    <b> Sales and Distribution:</b>
    Customers KNA1 General Data
    KNB1 Customer Master – Co. Code Data (payment method, reconciliation acct)
    KNB4 Customer Payment History
    KNB5 Customer Master – Dunning info
    KNBK Customer Master Bank Data
    KNKA Customer Master Credit Mgmt.
    KNKK Customer Master Credit Control Area Data (credit limits)
    KNVV Sales Area Data (terms, order probability)
    KNVI Customer Master Tax Indicator
    KNVP Partner Function key
    KNVD Output type
    KNVS Customer Master Ship Data
    KLPA Customer/Vendor Link
    Sales Documents VBAKUK VBAK + VBUK
    VBUK Header Status and Administrative Data
    VBAK Sales Document – Header Data
    VBKD Sales Document – Business Data
    VBUP Item Status VBAP Sales Document – Item Data
    VBPA Partners
    VBFA Document Flow
    VBEP Sales Document Schedule Line
    VBBE Sales Requirements: Individual Records
    SD Delivery DocumeLIPS Delivery Document item data, includes referencing PO
    LIKP Delivery Document Header data
    Billing Document VBRK Billing Document Header
    VBRP Billing Document Item
    SD Shipping Unit VEKP Shipping Unit Item (Content)
    VEPO Shipping Unit Header
    <b>Financial Accounting</b>
    FBAS             Financial Accounting “Basis”
    BKPF             Accounting Document Header              BUKRS / BELNR / GJAHR
    BSEG             Accounting Document Segment             BUKRS / BELNR / GJAHR / BUZEI
    BSIP             Index for Vendor Validation of Double   BUKRS / LIFNR / WAERS / BLDAT /
                     Documents                               XBLNR / WRBTR / BELNR / GJAHR / BUZEI
    BVOR             Inter Company Posting Procedure         BVORG / BUKRS / GJAHR / BELNR
    EBKPF            Accounting Document Header (docs from   GLSBK / BELNR / GJHAR / GLEBK
                     External Systems)
    FRUN             Run Date of a Program                   PRGID
    KLPA             Customer / Vendor Linking               NKULI / NBUKR / NKOAR / PNTYP
                                                             / VKULI / VBUKR / VKOAR
    KNB4             Customer Payment History                KUNNR / BUKRS
    KNB5             Customer Master Dunning Data            KUNNR / BUKRS / MABER
    KNBK             Customer Master Bank Details            KUNNR / BANKS / BANKL / BANKN
    KNC1             Customer Master Transaction Figures     KUNNR / BUKRS / GJHAR
    KNC3             Customer Master Special GL Transactions KUNNR / BUKRS / GJAHR / SHBKZ
                     Figures
    LFB5             Vendor Master Dunning Data              LIFNR / BUKRS / MABER
    LFBK             Vendor Master Bank Details              LIFNR / BANKS / BANKL / BANKN
    LFC1             Vendor Master Transaction Figures       LIFNR / BUKRS / GJHAR
    LFC3             Vendor Master Special GL Transactions   LIFNR / BUKRS / GJHAR / SHBKZ
                     Figures
    VBKPF            Document Header for Document Parking    AUSBK / BUKRS / BELNR / GJHAR
    FBASCORE         Financial Accounting General Services “Basis”
    KNB1             Customer Master (Company Code)          KUNNR / BUKRS
    LFA1             Vendor Master (General Section)         LIFNR
    LFB1             Vendor Master (company Code Section)    LIFNR / BUKRS
    SKA1             G/L Account Master (Chart of Accounts)  KTOPL / SAKNR
    SKAT             G/L Account Master (Chart of Accounts – SPRAS / KTOPL / SAKNR
                     Description)
    MAHNS            Accounts Blocked by Dunning Selection   KOART / BUKRS / KONKO / MABER
    MHNK             Dunning Data (Account Entries)          LAUFD / LAUFI / KOART / BUKRS /
                                                             KUNNR / LIFNR / CPDKY / SKNRZE /
                                                             SMABER / SMAHSK / BUSAB
    FI-GL-GL (FBS)   General Ledger Accounting: Basic Functions- G/L Accounts
    SKAS             G/L Account Master (Chart of Accounts – SPRAS / KTOPL / SAKNR / SCHLW
                     Key Word list)
    SKB1             G/L Account Master (Company Code)       BUKRS / SAKNR
    FI-GL-GL (FBSC)  General Ledger Accounting: Basic
                     Functions - R/3 Customizing for G/L Accounts
    FIGLREP          Settings for G/L Posting Reports        MANDT
    TSAKR            Create G/L account with reference       BUKRS / SAKNR
    FI-GL-GL (FFE)   General Ledger Accounting: Basic
                     Functions - Fast Data Entry
    KOMU             Account Assignment Templates for G/L    KMNAM / KMZEI
                     Account items
    FI-AR-AR (FBD)   Accounts Receivable: Basic Functions - Customers
    KNKA             Customer Master Credit Management :     KUNNR
                     Central Data
    KNKK             Customer Master Credit Management :     KUNNR / KKBER
                     Control Area Data
    KNKKF1           Credit Management : FI Status data      LOGSYS / KUNNR / KKBER / REGUL
    RFRR             Accounting Data – A/R and A/P           RELID / SRTFD / SRTF2
                     Information System
    FI-BL-PT         Bank Accounting: Payment (BFIBL_CHECK_D)  Transactions – General Sections
    PAYR             Payment Medium File                     ZBUKR / HBKID / HKTID / RZAWE /
                                                             CHECT
    PCEC             Pre-numbered Check                      ZBUKR / HBKID / HKTID / STAPL
    FI-BL-PT-AP(FMZA)Bank Accounting: Payment Transactions – Automatic Payments
    F111G            Global Settings for Payment Program for MANDT
                     Payment Requests
    FDZA             Cash Management Line Items in Payment   KEYNO
                     Requests
    PAYRQ            Payment Requests                        KEYNO
    Hope this solves your concern...
    Regards,
    Habeeb
    Assign points if helpful

  • In accounting document ..field reference / assignment (invoice no) is empty

    Dear all
    I opened  VF03 and open accounting document saw field reference / assignment (invoice no) is empty because of that  field reference (invoice no )  display empty in FBL5N.
    Sanj

    Its a very basic question.
    Based on your sales process.
    Refer following copying control header you need to maintain reference & assignement number based on your business requirement.
    For your reference.
    TCODE
    Sales Process
    Assignment Number
    Reference number
    VTFA
    order related billing
    B-Sales order number
    A-Purchase order number
    VTFL
    delivery related billing
    B-Sales order number
    A-Purchase order number
    Regards
    JP

  • XREF1(Reference Key1) and XREF2(Reference Key2) in FBl5N report

    what is the significance of XREF1(Reference Key1) and XREF2(Reference Key2) in FBl5N report. In my report I can see profit center being populated in most of the Reference Key2 values. But in some they are missing. So I want to know the significance of them, and how they are mapped. Please help me out.

    Hi Prasana
    As per your issue 1st you have maintain the required entry in filed status group level as well as at posting key level in the General TAB and select Reference specification 1/2 as a require entry after that you have to MAP in the T code OB32 at account type level
    Eg:  D        BSEG-XREF1        Reference key 1
           D        BSEG-XREF2        Reference key 2
          S      BSEG-XREF1           Reference key 1
          S      BSEG-XREF2           Reference key 2
          S      BSEG-XREF3           Reference key 3
    Like above based your requirement you have to maintain
    - Document change rules line item (TC: OB32)
    - Posting key (TC: OB41)
    - Field status groups (SPRO -> FI -> FI Global settings -> Ledgers -> Fields -> Define field status variants)
    - Special field display (SPRO -> FI -> GL Accounting -> Master Data -> GL Accounts -> Line items -> Define Special Fields for Line item display)
    - Doccument change rules header (SPRO -> FI -> FI Global settings -> Document -> Rules for changing documents -> Document change rules, document header)
    After that while you posting  any transaction data you have to enter reference key1 and 2 filed at more data Tab  where you can see  at header level tabs
    Finally  you can able see in the FBL5N report...same case we have faced previously it was resolved
    I hope it will helps you
    Thanks and Regards
    sudharshana vamsi

  • REP-1213: Field  references column at a frequency below its group

    Is there a way of making a field which is on a lower level group to be displayed in a group which is at a higher level in the report?
    I have a field which is within a lower level group on a report and I want it to appear as a header, within a group which is a level above its own group. The field should remain in its original group but should not appear on the report as a column within its original group but should appear as part of the heading.
    I have tried it and got error REP-1213: Field references column at a frequency below its group, but how can I achieve what I want to do without getting this error? Is there a way of showing this field on the header without actually moving it into the header group? Should I create an alias or a function or what and how?
    Please help.

    user8655468 wrote:
    Sorry, I don't seem to get you. MY report has 2 repeating groups. The first group has student_name, course_code, course_name and the 2nd group has academic_year, module_name, module_code and module_grade. Academic_year which is in the 2nd group has to appear as a heading together with the items in the first group but it can not be moved from its original group as it goes together with modules. The report displays a history of a student's modules from 1st year to current year so the Academic year on the header will have to show the current Academic year for a student.
    I don't understand how I should use a summary column to achieve what I want to do. Please can you explain further. Thanks.I think you know about summary column. If your academic year is number filed, you can use it at summary column. Where summary function is sum. You take this summary column at 1st group and select source from 2nd group. Then display it at 1st frame.
    Hope this will help you..
    If someone's response is helpful or correct, please mark it accordingly.

  • Field symbols and field groups

    Hi friends plz send me the answer for this query:
    What are field symbols and field groups.? what is the"component idx of structure" clause with field groups?

    Hi,
    A field group combines several existing fields together under one name
    like
    FIELD-GROUPS: fg.
    then you can use one insert statement to insert values in fields of field-group.
    INSERT f1 f2 ... INTO fg.
    Field symbols
    If u have experience with 'C', then understand this to be similar to a pointer.
    It is used to reference another variable dynamically. So this field symbol will simply point to some other variable. and this pointer can be changed at runtime.
    FIELD-SYMBOLS <FS>.
    DATA FIELD VALUE 'X'.
    ASSIGN FIELD TO <FS>.
    WRITE <FS>.
    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 Groups:
    A field group is a user-defined grouping of characteristics and basic key figures from the EC-EIS or EC-BP field catalog.
    Use
    The field catalog contains the fields that are used in the aspects. As the number of fields grows, the field catalog becomes very large and unclear. To simplify maintenance of the aspects, you can group fields in a field group. You can group the fields as you wish, for example, by subject area or responsibility area. A field may be included in several field groups.
    When maintaining the data structure of an aspect, you can select the field group that contains the relevant characteristics and basic key figures. This way you limit the number of fields offered.
    Field Groups / Extracts
    http://help.sap.com/saphelp_46c/helpdata/EN/9f/db9ede35c111d1829f0000e829fbfe/frameset.htm
    Field Symbols
    http://help.sap.com/saphelp_46c/helpdata/EN/fc/eb387a358411d1829f0000e829fbfe/frameset.htm
    Regards,
    Priyanka.

  • Field Symbols, Field String, and Field Group.

    Hi,
    Can you differentiate between filed symbols, field strings and field groups,
    With regards,
    Bharath Mohan B

    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.
    Related
    ASSIGN, DATA
    Additional help
    Declaring Field Symbols
    FIELD GROUPS
    are used to hold/handle large amount of data when the internal table are not useful
    we use EXTRACT statement, HEADER structure in them
    see the example
    REPORT demo_extract.
    NODES: spfli, sflight.
    FIELD-GROUPS: header, flight_info, flight_date.
    START-OF-SELECTION.
      INSERT: spfli-carrid spfli-connid sflight-fldate
                INTO header,
              spfli-cityfrom spfli-cityto
                INTO flight_info.
    GET spfli.
      EXTRACT flight_info.
    GET sflight.
      EXTRACT flight_date.
    END-OF-SELECTION.
      SORT STABLE.
      LOOP.
        AT FIRST.
          WRITE / 'Flight list'.
          ULINE.
        ENDAT.
        AT flight_info WITH flight_date.
          WRITE: / spfli-carrid , spfli-connid, sflight-fldate,
                   spfli-cityfrom, spfli-cityto.
        ENDAT.
        AT flight_date.
          WRITE: / spfli-carrid , spfli-connid, sflight-fldate.
        ENDAT.
        AT LAST.
          ULINE.
          WRITE: cnt(spfli-carrid), 'Airlines'.
          ULINE.
        ENDAT.
      ENDLOOP.
    FIELD STRING is nothing but a string with  one row of records.
    Reward points if useful
    regards
    Anji

Maybe you are looking for