Confusion b/w term.Roll area and Work area

Hi,
Can someone explain me these Two Term in simple english.
1)Roll Area
2)Work Area
How aou distinguish b/w them.
Thanks.
Samir.

Hi Samir,
Welcome to SDN.
1. The first & main difference is
   WORK AREA : Refers when we talk about ABAP Programming
   ROLL AREA : Refers when we talk about R/3 Instance
               (on server)
2. Work Area :
   We can call it nothing but a VARIABLE.
   But this variables/ terminology is used for the purpose
   of internal table.
   for eg.
   Loop at ITAB.
   (When itab is defined with header line,
    the header line becomes the work area,
   ie temporary storage)
   Loop at ITAB into wa.
   (here it is used when itab is not defined
    with header line, instead, a field-string WA
   is defined , same as itab structure)
3. ROLL AREA :
   SAP Gui <----
> R/3 Server
   There is a constant interaction between
   the above two.
   In a program, many variables are used,
   there are many screens each having
   their own logic.
   Many users are running the same program.
   To keep track of all these, the
   r/3 instance on the server,
   keeps information about EACH and EVERYTHING
   in its memory RAM.
   This BUNCH of INFORMATION
   about EACH SESSION and the PROGRAM
   is called work area.
I hope it helps.
Regards,
Amit M.
Message was edited by: Amit Mittal

Similar Messages

  • Runtime area and work area in PGA

    In 10g concept (http://download.oracle.com/docs/cd/B19306_01/server.102/b14220/memory.htm#sthref1418) it is written that
    "a big portion of the runtime area is dedicated to work areas"
    From the above statement we can conclude that runtime area contains work areas.
    However in 11g concept (http://download.oracle.com/docs/cd/E11882_01/server.112/e16508/memory.htm#i14490) figure 14-4
    it looks like runtime area do not contains work areas.
    My question is do runtime area include work areas?
    If work areas are not included in the runtime area then where is it located in shared server configuration?

    My question is do runtime area include work areas?I guess not. The work areas are the areas which contain the information about the workarea profiles of the operators like group by , sort and so on. These areas are created as and when required. Whereas, the runtime area is a part of the UGA which is going to keep the information about the query's execution status as well as, about the bind variables and so on. So IMO, the answer would be no but given that PGA is a very complex thing, I think you should wait for others also to get included in the thread.
    HTH
    Aman....

  • The type of the database table and work area (or internal table)...

    Hello
    I am trying to use a database and select all records from it and store them into an internal table.
    My code:
    Select * from xixi_dbcurrency into table gt_currency.
    The error:
    "The type of the database table and work area (or internal table) "GT_CURRENCY" are not Unicode-convertible . . . . . . . . . .     "
    Any suggestions?
    Thank you

    Hi Thomas,
    Thank you for your inputs above.
    But as you suggested is we use INTO CORRESPONDING FIELDS OF TABLE then it resolve the error.
    But I have below piece of code:
    DATA:    it_new_source TYPE STANDARD TABLE OF _ty_s_sc_1,
                  wa_source TYPE _ty_s_sc_1,
                  wa_new_source TYPE _ty_s_sc_1,
                  ls_target_key TYPE t_target_key.
    SELECT * INTO CORRESPONDING FIELDS OF TABLE it_new_source
           FROM /bic/afao06pa100
           FOR ALL ENTRIES IN SOURCE_PACKAGE
           where /bic/fcckjobno = SOURCE_PACKAGE-/bic/fcckjobno
           and /bic/fcckjitid = SOURCE_PACKAGE-/bic/fcckjitid.
    But since this is reading into corresponding fields of table the data load from one DSO to other DOS is running for long more that 15 hours and still not getting completed and giving dump.
    So if I switch the search to below:
    SELECT * FROM /bic/afao06pa100
       INTO TABLE it_new_source
           FOR ALL ENTRIES IN SOURCE_PACKAGE
           where /bic/fcckjobno = SOURCE_PACKAGE-/bic/fcckjobno
           and /bic/fcckjitid = SOURCE_PACKAGE-/bic/fcckjitid.
    Then I am getting below error:E:The type of the database table and work area (or internal table) "IT_NEW_SOURCE" are not Unicode convertible.
    Can you please advice on this, as performance need to improve in start routine code.
    Thank You.

  • The type of the database table and work area are not Unicode convertible

    ***Data declaration
    TYPES : BEGIN OF t_zle_lagerplanung,
                       SEl, "stores which row user has selected
                       kdauf TYPE zle_lagerplanung-kdauf,
                       kdpos TYPE zle_lagerplanung-kdpos,
                       etenr TYPE zle_lagerplanung-etenr,
                       papiermaschine TYPE zle_lagerplanung-papiermaschine,
                       runnr TYPE zle_lagerplanung-runnr,
                       prio TYPE zle_lagerplanung-prio,
                       werk TYPE zle_lagerplanung-werk,
                       durchmesser TYPE zle_lagerplanung-durchmesser,
                       breite TYPE zle_lagerplanung-breite,
                       anzle TYPE zle_lagerplanung-anzle,
                       lgpla TYPE zle_lagerplanung-lgpla,
                       lgtyp TYPE zle_lagerplanung-lgtyp,
                       art TYPE zle_lagerplanung-art,
                       anzhoehe TYPE zle_lagerplanung-anzle,
                       fa TYPE zle_lagerplanung-fa,
    END OF t_zle_lagerplanung.
    DATA : it_zle_lagerplanung TYPE STANDARD TABLE OF t_zle_lagerplanung INITIAL SIZE 0,
                wa_zle_lagerplanung TYPE t_zle_lagerplanung.
    Here I am getting the data in internal table by using thiis select statement.
    SELECT kdauf kdpos etenr papiermaschine runnr prio werk durchmesser breite
                  anzle lgpla lgtyp art anzhoehe fa
    FROM    zle_lagerplanung INTO CORRESPONDING FIELDS OF TABLE it_zle_lagerplanung
    WHERE  kdauf IN s_kdauf
    AND       KDPOS IN s_kdpos
    AND      werk = p_werks.
    But while updating the particular field in zle_lagerplanung using this statement
    UPDATE zle_lagerplanung from table it_zle_lagerplanung.
    it is giving syntax error
    "The type of the database table and work area (or internal table)
    "IT_ZLE_LAGERPLANUNG" are not Unicode convertible. "
    Could any one help me out how to resolve this problem....
    Thanks in advance

    Dear Shayamal,
    XXX....are not Unicode convertible
    This  error comes while inserting or updating database and the fields are not matching between  data base table and structure .
    Check you fields of data base table and  "zle_lagerplanung" and struture "it_zle_lagerplanung" . There fields must match.
    thanks and regrds,
    Anup Banerjee

  • Internal table and work area

    Hi,
           can anybody explain the concepts of Internal table and work area.Thanks in advance.

    hai,
    This may help u.
    WORKAREA is a structure that can hold only one record at a time. It is a collection of fields. We use workarea as we cannot directly read from a table. In order to interact with a table we need workarea. When a Select Statement is executed on a table then the first record is read and put into the header of the table and from there put into the header or the workarea(of the same structure as that of the table)of the internal table and then transferred top the body of the internal table or directly displayed from the workarea.
    Each row in a table is a record and each column is a field.
    While adding or retrieving records to / from internal table we have to keep the record temporarily.
    The area where this record is kept is called as work area for the internal table. The area must have the same structure as that of internal table. An internal table consists of a body and an optional header line.
    Header line is a implicit work area for the internal table. It depends on how the internal table is declared that the itab will have the header line or not.
    e.g.
    data: begin of itab occurs 10,
    ab type c,
    cd type i,
    end of itab. " this table will have the header line.
    data: wa_itab like itab. " explicit work area for itab
    data: itab1 like itab occurs 10. " table is without header line.
    Internal tables are used for storing records which are obtained as a result when we use select statement on database. internal tables are run time entities and doesn't occupy any memory. they are dynamic.
    internal tables are of types.
    1. internal tables with header line. [header and body]
    2. internal tables with out header line. [only body]
    Workarea is the concept which is mainly useful when working with internal tables with out header line.
    at any point of time we can access only one record through header of a internal table. every thing should be done [inserting,modifying, reading ] through header only.
    ex: data: itab like standard table of mara with header line.
    for internal tables with out header line we will create a work area [explicit header] as type of table for storing data into internal table.
    ex: data: itab like mara,
    wa like mara.
    more about internal table types:
    Standard table:
    The key access to a standard table uses a sequential search. The time required for an access is linearly dependent on the number of entries in the internal table.
    You should usually access a standard table with index operations.
    Sorted table:
    The table is always stored internally sorted by its key. Key access to a sorted table can therefore use a binary search. If the key is not unique, the entry with the lowest index is accessed. The time required for an access is logarithmically dependent on the number of entries in the internal table.
    Index accesses to sorted tables are also allowed. You should usually access a sorted table using its key.
    Hash table:
    The table is internally managed with a hash procedure. All the entries must have a unique key. The time required for a key access is constant, that is it does not depend on the number of entries in the internal table.
    You cannot access a hash table with an index. Accesses must use generic key operations (SORT, LOOP, etc.).
    Hashed tables
    This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index.
    The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always
    have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for
    processing large amounts of data.
    TYPES VECTOR TYPE HASHED TABLE OF I WITH UNIQUE KEY TABLE LINE.
    TYPES: BEGIN OF LINE,
    COLUMN1 TYPE I,
    COLUMN2 TYPE I,
    COLUMN3 TYPE I,
    END OF LINE.
    DATA ITAB TYPE HASHED TABLE OF SPFLI
    WITH UNIQUE KEY CARRID CONNID.
    with regards,
    B.Sowjanya,
    reward points if helpful.

  • Header line and work area

    Hi,
    can anyone please explain me wht is the difference between header line and work area???

    Hi,
    INTERNAL TABLES
    - Internal tables are used to obtain data from a fixed structure for
    dynamic use in ABAP.
    - Each line in the internal table has the same field structure.
    - The main use for internal tables is for storing and formatting data from
    a database table within a program.
    WORK AREAS
    - Work areas are single rows of data.
    - It should have the same format as any of the internal tables.
    - It is used to process the data in an internal table one line at a time.
    Internal Tables with Header Line : Here the system automatically creates the work area. The work area has the same data type as internal table. This work area is called the HEADER line. It is here that all the changes or any of the action on the contents of the table are done. As a result of this, records can be directly inserted into the table or accessed from the internal table directly.
    Internal Tables without Header Line : Here there is no work area associated with the table. Work area is to be explicitly specified when we need to access such tables. Hence these tables cannot be accessed directly.
    HEADER LINE----
    CREATED EXPLICITLY------
    1.Internal table created by referring to another table
    Syntax: Data <f> <type> with header line.
    <type> refers to a table data type or table data objects using type or like.
    Here internal table <f> is created of the type <type>.
    Example:
    DATA t_line TYPE line OCCURS 10 with header line.
    2. Internal table created by referring to existing structure
    Syntax: Data<f> <type> occurs n with header line.
    The lines of the internal table <f> have the data type specified in <type> (Can use either like or type).
    Example:
    DATA flight_tab LIKE sflight OCCURS 10.
    CREATED BY DEFAULT---
    3. Internal table created With a new structure
    Syntax: Data : Begin of <f> occurs <n>,
    <component declaration>,
    End of <f>.
    Work area is created by default.
    Example:
    Data : Begin of itab occurs 10,
    column1 type I,
    column2(4) type C,
    column3 like mara-ernam,
    End of itab.
    reward if useful
    Regards

  • Difference between Field symbols and work area for Internal tables

    Hi,
    In ECC versions we all know that we need to declare the internal tables without headerline, and for handling the internal tables we need to use exclusive work areas.
    Currently i have an issue that we have been asked to use field symbols instead of work areas...can any one help me how to use the field symbols and also let me know how it will improve the performance of the program..
    Thanks and Regards,
    Kathir

    Hi
    DATA: WA TYPE ITAB.
    LOOP AT ITAB INTO WA.
    IF WA-FIELD = .....
    ENDIF.
    ENDLOOP.[(code]
    FIELD-SYMBOLS <WA> TYPE ANY.
    LOOP AT ITAB ASSIGNING <WA>.
    ENDLOOP.
    Now the problem is you can't know the name of the fields of the table at runtime, so you can't write:
    IF <WA>-FIELD = .....
    ENDIF.
    Anyway you can create a field-symbols strcturated like the table:
    [code]FIELD-SYMBOLS <WA> TYPE ITAB.
    LOOP AT ITAB ASSIGNING <WA>.
      IF <WA>-FIELD = .....
      ENDIF.
    ENDLOOP.
    I don't know which are the differences for the performance between to use a field-symbol and to use a structure as work-area.
    The differnce between the field-symbols and work-area is the field-symbol is assigned directly to the record, so u don't need to do a MODIFY statament to change something:
    LOOP AT ITAB INTO WA.
      WA-FIELD =
      MODIFY ITAB FROM WA.
    ENDLOOP.
    LOOP AT ITAB ASSIGNING <WA>.
      <WA>-FIELD =
    ENDLOOP.
    These two pieces of abap code do the same action, so probably the field-symbol improve the performance because it do an access directly to the record without to use an external structure as workarea.
    Max

  • Structure of table and work area are not compatible - table control wizard

    Structure of table and work area are not compatible is the error i am getting when specifying my internal table and work area in my table control?  What am I doing wrong?

    hii
    this error comes when you have different structure of work area then internal table..so work area will not work here and you will not be able to append records in internal table.
    check strucure of internal table and work area.it should be like below.
    TYPES:
      BEGIN OF type_s_kna1,
         kunnr LIKE kna1-kunnr,            " Customer Number
         name1 LIKE kna1-name1,            " Name
         vbeln LIKE vbap-vbeln,            " Sales Document
      END OF type_s_kna1.
    * Internal Table And Work Area Declarations For Customer Details      *
      DATA : t_kna1 TYPE STANDARD TABLE OF type_s_kna1,
             fs_kna1 TYPE type_s_kna1.
    regards
    twinkal

  • Diff between header line and work area.

    Diff between header line and work area.

    Hi,
    These are table with header line.
    DATA: T_TABLE type table of <table_name> with header line.
    data: begin of t_table occurs 0,
                  field1 type ...
                  field2 type ...
                  field3 type ...
          end of t_table.
    <b>The result is:</b>
    <u><b>TABLE</b></u>    
    FIELD NAME  |FIELD1|FIELD2|FIELD3|  
    HEADER LINE |EE1   |EE2   |EE3   | <---- Line 5 content
               1|AA1   |AA2   |AA3   |  
               2|BB1   |BB2   |BB3   |  
               3|CC1   |CC2   |CC3   |
               4|DD1   |DD2   |DD3   |
               5|EE1   |EE2   |EE3   |
    These are table without header line.
    DATA: T_TABLE type table of <table_name>.
    DATA: T_TABLEX LIKE TABLE OF t_table.
    <b>The result is:</b>
    <u><b>TABLE</b></u>    
    FIELD NAME  |FIELD1|FIELD2|FIELD3|  
                     0|---   |---   |---   | <---- No header Line
                     1|AA1   |AA2   |AA3   |  
                     2|BB1   |BB2   |BB3   |  
                     3|CC1   |CC2   |CC3   |
                     4|DD1   |DD2   |DD3   |
                     5|EE1   |EE2   |EE3   |
    These are work areas:
    Tables <table>.
    DATA: wa type <table>.
    DATA: wa like t_table.
    DATA: wa type line of <table>.
    <b>The result is:</b>
    <u><b>WORK AREA</b></u>  
    |EE1   |EE2   |EE3   | <---- Content
    Regards.
    Marcelo Ramos

  • Payscale Area and Work hrs/period  - IT 0008

    Hi
    Can anyone please provide me with the linkage between the Payscale Area and Work hrs/period in Infotype 0008.
    The data for an employee reflects wrongly in the work hrs/period... Its ahould have a value 80.00 ad Biweekly and instead has 162.94 Monthly.
    Can anyone please tell me where these changes needs to be carried out
    Thanks,
    Sanjay

    Use Tcode SM30
    Type table  V_T508A
    Go to maintain
    Select your Work Schedule rule
    Go to details
    You will give the hours here that hour only disply in IT0007 and 0008
    Default that field is monthly hour field only it will display
    If you want to display Bi weekly hours you need to do the screen modifaction programming go to that field and put BI Weekly hours Data Element instead of Monthly hours field
    This will be not done with config only Abaper can do
    Best Regards

  • What is the difference between Structure and Work area

    Hi Guys,
    What is the difference between Structure and work area?
    Are they same with different names?
    Thanks,
    mini.

    hey buddies,*
    i had this same doubt for a long time and i have my finds with me ie wa and structure are the same but wa can hold a single record but structure cannot hold data in it but according to the previous posts  folks  say structure too holds data as wa does but i guess when debugging wa holds data and structure doesnt hold bcoz i tried.
    types : begin of str_mara,
                 matnr type mara-matnr,
                ernam type mara-ernam,
                end of str_mara.
    data it_mara type table of str_mara.
    select matnr ernam from mara into it_mara where matnr = '100-101'.
    *********************if folks say wa = structure,this should work,isn't it?*********************************
    loop at it_mara into str_mara.
    write:/ str_mara-matnr , str_mara-ernam.
    endloop.
    *******************but it throws an error saying that str_mara is not a wa*******************************
    i may not be correct too plz let me know if i'm wrong
    Edited by: arun_aime on Feb 12, 2010 4:41 PM

  • Staging area and target area

    hi..friends.
    should staging area and target area be same or different???
    if same what are the advantages and dis-advantages???
    and if not same what are the advantages and dis-advantages????
    I want your help..
    Thanks.

    Staging area is the place where transformation takes place.
    Basically c$,I$ tables gets created at this place and once processing is done , the same gets dropped .
    By defalut staging area and traget area are the same . But most of the DBA does not like to have the temp tables created at the target as this cause dbms performance, maintance issue in long term.
    Instead you can have a dedicated schema created just for staging and use the same in your interface.
    Plus when your target is non dbms then you need to go for a dedicated staging area which can be a separate schema in your database or it could be in memory schema. You will find performance issue if you are using in memory schema as your staging area in case the data volume increase.
    Thanks,
    Sutirtha

  • Def of dunning area and valuation area

    hi,
    pls tell me the exact defintions of dunning area and valuation area,

    Dunning areas are used if several organizational units are responsible for carrying out dunning within one company code. These organizational units are referred to as dunning areas. The dunning area can correspond, for example, to a profit center, a distribution channel, a sales organization or a business area.
    This is a combination betwwen SD and FI
    Organizational level at which the material is valuated. A valuation area can be one of the following:
    Plant
    All plants belonging to a company code, in which case the valuation area is the company code
    This is used in MM and can be used to assign in MM G/L accounts to a valuation area.
    It possible that valuation area is used on other places to with a compleet differenrt functionality
    Paul

  • In Firefox 4 how can I cause the date on downloaded files to be the current date? (Some are and some are not. In FF3 the dates were ALWAYS the current ones.)

    In Firefox 4 how can I cause the date on downloaded files to be the current date? (Some are and some are not. In FF3 the dates were ALWAYS the current ones.)
    == This happened ==
    Every time Firefox opened
    == I upgraded to Firefox 4 (beta)

    Firefox 3.6.* and earlier set the downloaded file's modification time to the current time. In Firefox 4.0 the behavior has been changed, if a server returns a timestamp telling when the file was last modified (Last-Modified header), it is used instead.
    You can revert to the previous behaviour by using the [https://addons.mozilla.org/en-US/firefox/addon/93121/ Download Timestamp] add-on.

  • Difference between business area and sales area

    Hi
    I am swetha i have one doubt
    1) what is the buisiness area and what purpose we use the business area
    2)  what is sales area and what purpose we use the sales area
    3)what is the main Difference between business area and sales area.
    Regards
    Swetha

    Hii..
    Business Areas in SAP are used to differentiate transactions originating from different points/lines/locations in business. Let me give some examples to elucidiate:-
    A company (say, ABC) is a huge company and has a variety of businesses under it. Let us say that it typically operates in 3 different domains like machinery manufacturing, trading and assembling of machine parts.
    There are 2 options here now -
    1. Either create different company codes for the 3 business operations (which would be the easiest and require no creativity)
    or
    2.) Create each of these business lines into business areas (the better option).
    The advantages of using the second option is:
    1. You can use these business areas if other company codes require the same areas
    2. The configuration is simpler as in case of company code, you would require to go through the entire configuration of creating Chart of Accounts, Fiscal Year variants, posting periods variants and so on. In the business area option, you just need to attach it to the company code and the rest of the details in Business area is attached by default from the company code you are using it in.
    3. Using the options in controlling (EC-PCA, Enterprise Controlling, Profit Centre Accounting), you can even draw up Balance Sheets and PL statements for your business areas and hence this is used for management accounting in some companies (like HP, Dell, etc) when it wants to know the operating profits for different business areas/lines.
    The above was an example when the company wanted to separate entries according to the lines it operates in... the other case could be when it wants to find out profitability during its operations in cities and differentiates these cities into Business
    Areas...
    Business Areas are not much relevant in FI but are much more relevant in CO.
    Hope this clears.
    What is mySAP SD?
    The SAP sales and distribution is part of the logistics module that support your customers, starting from quotations, sales order and all the way towards billing the customer.  It is tightly integrated with the MM and PP functional modules.  It allows companies to input their customer sales price, check for open orders and forecast etc.
    The most important basic functional features in the sd module are:
    - Pricing                                           - Availability Check
    - Credit Management                       - Material Determination
    - Output Determination                     - Text Processing
    - Tax Determination                          - Account Determination
    Regards,
    Aakash

Maybe you are looking for