Internal table declaration

What is the difference between 'OCCURS 0' addition and 'INITIAL SIZE' .
CASE I :(Declaration With 'OCCURS 0' addition)
DATA:BEGIN OF I_TAB OCCURS 0,
       NAME(5) TYPE C,
       AGE(2) TYPE C,
     END OF I_TAB.
CASE II :(Declartion with inital size)
TYPES:BEGIN OF T_TAB,
             NAME(5) TYPE C,
             AGE(2) TYPE C,
           END OF T_TAB.
DATA:I_TAB TYPE STANDARD TABLE OF T_TAB INITIAL SIZE 0.
In the above cases which case is efficient for declaring internal table ?
Moderator message: please read ABAP documentation before posting.
Edited by: Thomas Zloch on Jun 27, 2011 4:23 PM

Similar Messages

DIFF: Field string ,Structure and Internal table declaration

Hai,
       what is the diference between Field string ,Structure in ABAP program and Internal table declaration and how it will work ?
Thank you
ASHOK KUMAR.

hi,
Look this u will get a good idea.
*& Report ZTYPES                                                      *
REPORT ZTYPES                                                  .
* Table declaration (old method)
DATA: BEGIN OF tab_ekpo OCCURS 0,             "itab with header line
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
END OF tab_ekpo.
*Table declaration (new method)     "USE THIS WAY!!!
TYPES: BEGIN OF t_ekpo,
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
END OF t_ekpo.
DATA: it_ekpo TYPE STANDARD TABLE OF t_ekpo INITIAL SIZE 0,      "itab
      wa_ekpo TYPE t_ekpo.                    "work area (header line)
* Build internal table and work area from existing internal table
DATA: it_datatab LIKE tab_ekpo OCCURS 0,      "old method
      wa_datatab LIKE LINE OF tab_ekpo.
* Build internal table and work area from existing internal table,
* adding additional fields
TYPES: BEGIN OF t_repdata.
        INCLUDE STRUCTURE tab_ekpo. "could include EKKO table itself!!
TYPES: bukrs TYPE ekpo-werks,
       bstyp TYPE ekpo-bukrs.
TYPES: END OF t_repdata.
DATA: it_repdata TYPE STANDARD TABLE OF t_repdata INITIAL SIZE 0,   "itab
      wa_repdata TYPE t_repdata.                 "work area (header line)
Regards
Reshma

Internal table declaration - work area and body

Hi all
I have declared my internal table in my program as
data : itab_wa type ZRESULT_LINE,
       itab    type ZRESULT_ROW.
Where ZRESULT_LINE and ZRESULT_ROW are the structure and table types.
Now I want to add
data: TCOLOR TYPE SLIS_T_SPECIALCOL_ALV.
in my internal table declaration. How can I do this. Please remember I need to have work area and body in my internal table as I have used work area and body in my code.
Waiting..............
Message was edited by: Raju Boda

HI,
See the Declarion types of workarea and Internal tables
* Table declaration (old method)
DATA: BEGIN OF tab_ekpo OCCURS 0,             "itab with header line
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
END OF tab_ekpo.
*Table declaration (new method)     "USE THIS WAY!!!
TYPES: BEGIN OF t_ekpo,
ebeln TYPE ekpo-ebeln,
ebelp TYPE ekpo-ebelp,
END OF t_ekpo.
DATA: it_ekpo TYPE STANDARD TABLE OF t_ekpo INITIAL SIZE 0,      "itab
      wa_ekpo TYPE t_ekpo.                    "work area (header line)
* Build internal table and work area from existing internal table
DATA: it_datatab LIKE tab_ekpo OCCURS 0,      "old method
      wa_datatab LIKE LINE OF tab_ekpo.
* Build internal table and work area from existing internal table,
* adding additional fields
TYPES: BEGIN OF t_repdata.
        INCLUDE STRUCTURE tab_ekpo. "could include EKKO table itself!!
TYPES: bukrs TYPE ekpo-werks,
       bstyp TYPE ekpo-bukrs.
TYPES: END OF t_repdata.
DATA: it_repdata TYPE STANDARD TABLE OF t_repdata INITIAL SIZE 0,   "itab
      wa_repdata TYPE t_repdata.                 "work area (header line
you need to maintain same structure for both workarea as well Internal table
Regards
Sudheer

TSV_TNEW_PAGE_ALLOC_FAILED with internal table declared with occurs 0

HI guys,
when the internal table is declared as occurs 0, the dump TSV_TNEW_PAGE_ALLOC_FAILED is encountered, when changing the declaration into standard table, th dump disappears. Why is this so?
Thanks!

There are three type of tables: Standard, sorted and hashed tables (see [here|http://help.sap.com/abapdocu_70/en/ABAPDATA_ITAB.htm]). When you define a table using the keyword OCCURS you're still defining a standard table.
Your exception indicates that you're running out of memory. The difference in the declarations that you mention shouldn't cause that. Main difference between the two declaration versions is probably that your table defined via OCCURS has a header line, whereas your other table doesn't (unless you declared it explicitly as WITH HEADER LINE).
I don't think though that with that little information anybody could explain the short dump. Actually it sounds rather odd that the change you mention should cause the dump (or make it go away). So I suspect you probably have to post further details. You might want to check the shortdump yourself and place a breakpoint at this place and run it for each version. Maybe you can see some difference...

Accessing internal table declared outside of BAdI implementation

I am working on a BAdI implementation and within the BAdI, I need to manipulate the data of an internal table that is declared in the calling routine. This internal table is not a parameter to the BAdI call. I am wondering is there a way to access the internal table that is not recognized by the BAdI implementation? If so, what's the syntax to do this?
I know in debug mode, I am able to access the content of the internal table by using (Program)Itab. But I get a syntax error when accessing the internal table using (Program)Itab syntax.
Any help is appreciated!

Thanks, Max.
I tried your method, but I am getting a short dump due to type conflict. I think it's because the internal table I'd like to access is declared using the following syntax:
data: begin of itab occurs 0,
end of itab.
Therefore, when processing the assign statement, the field-symbol is being treated as a structure...
I tried to change the field-symbol type to any, but after that, I can't modify the table content using loop at type of syntax..
Do you have any other suggestions?
Thanks very much!

Problem with internal table declaration in function gui_upload

hi friends,
can u tell me how should i define internal table when i use this function?
i get error that in oo my declaration not good.
thanks,
dana.

see this example:-
DATA: BEGIN OF itab OCCURS 0,
        tdname   TYPE mara-matnr,
        tdline1 TYPE tline-tdline,
        tdline2 TYPE tline-tdline,
        tdline3 TYPE tline-tdline,
        tdline4 TYPE tline-tdline,
        tdline5 TYPE tline-tdline,
              END OF itab.
DATA: BEGIN OF itab_error OCCURS 0,
        tdname TYPE mara-matnr,
        error   TYPE string,
      END OF itab_error.
DATA: lines    TYPE STANDARD TABLE OF tline WITH HEADER LINE.
DATA: temp     TYPE string.
DATA: tdspras TYPE thead-tdspras.
DATA: tdname   TYPE thead-tdname.
DATA: tdobject TYPE thead-tdobject.
DATA: tdid     TYPE thead-tdid.
DATA :flag     TYPE c.
At Selection Screen Event
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p1.
CALL FUNCTION 'F4_FILENAME'
    IMPORTING
      file_name = p1.
At Start of Selection Event
START-OF-SELECTION.
PERFORM upload_data.
PERFORM upload_text.
*&      Form upload_data
      text
--> p1        text
<-- p2        text
FORM upload_data .
temp = p1.
**& Upload Data from Excel
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename            = temp
      filetype            = 'ASC'
      has_field_separator = 'X'
    TABLES
      data_tab            = itab.
ENDFORM.                    " upload_data
*&      Form upload_text
      text
--> p1        text
<-- p2        text
FORM upload_text .
tdspras = 'EN'.
tdid = 'BEST'.
tdobject = 'MATERIAL'.
LOOP AT itab.
    REFRESH lines.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
      EXPORTING
        input = itab-tdname
      IMPORTING
        output = itab-tdname.
    TRANSLATE itab-tdname TO UPPER CASE.
    tdname = itab-tdname.
    PERFORM check_material.
    lines-tdline = itab-tdline1.
    APPEND lines.
    CLEAR lines.
    lines-tdline = itab-tdline2.
    APPEND lines.
    CLEAR lines.
    lines-tdline = itab-tdline3.
    APPEND lines.
    CLEAR lines.
    lines-tdline = itab-tdline4.
    APPEND lines.
    CLEAR lines.
    lines-tdline = itab-tdline5.
    APPEND lines.
    CLEAR lines.
    CALL FUNCTION 'CREATE_TEXT'
      EXPORTING
        fid       = tdid
        flanguage = tdspras
        fname     = tdname
        fobject   = tdobject
      TABLES
        flines    = lines.
ENDLOOP.
IF itab_error[] IS NOT INITIAL.
    WRITE : / 'PO Text For Following Material is not Uploaded'.
    WRITE : / .
    WRITE : / 'Material', '              Error'.
    LOOP AT itab_error.
      WRITE : / itab_error-tdname, '   ', itab_error-error.
    ENDLOOP.
ELSE.
    MESSAGE s001(38) WITH 'Data Uploaded Succcesfully'.
ENDIF.
ENDFORM.                    " upload_text
*&      Form check_material
      text
--> p1        text
<-- p2        text
FORM check_material .
DATA : w_matnr TYPE mara-matnr.
SELECT SINGLE matnr
INTO w_matnr
FROM mara
WHERE matnr = itab-tdname.
IF sy-subrc = 0.
    flag = 'X'.
ELSE.
    MOVE-CORRESPONDING itab TO itab_error.
    itab_error-error = 'Material does not exist'.
    APPEND itab_error.
ENDIF.
ENDFORM.                    " check_material

Internal table declaration -OO ABAP

Hi,
          I am looking to declare an internal table using OO objects. My declaration are as follows..
TYPES : Begin of itab,
                     f1 type c,
                     f2 type c,
             End of itab.
DATA : itab1 type standard table of itab.
DATA: wa_tab type itab.
I have an internal table to say itab_pa2001 which i am reading all the records of pernr into ITAB_PA2001.To get the text i want to select * from t5*** into ..... Finally wht am looking is to move some of the fields into the final table ITAB. Could you please let me know how to set this up as i am getting wrong values when i am looping as below.
how to declare a structure in ITAB using ABAP OO....??
LOOP at ITAB_PA2001 into wa_itab.
ENDLOOP.
Thanks,
Vind

Hi,
Please refer to following links :
[How to declare an internal table in OO-ABAP programming? |Re: How to declare an internal table in OO-ABAP programming?;
[sample object oriented ABAP program |http://wiki.sdn.sap.com/wiki/display/Snippets/sampleobjectorientedABAPprogram]
Hope this helps.
Regards,
Chandravadan

Include a type in a internal table declaration.

Hi.
How can I do this?:
TYPES: BEGIN OF ty_simples,
agr_name LIKE agr_define-agr_name,
text     LIKE agr_texts-text.
TYPES: END OF ty_simples.
Transacciones de GS.
TYPES: BEGIN OF ty_transacciones_gs,
tcode    LIKE agr_tcodes-tcode,
text     LIKE bmeniface-text.
TYPES: END OF ty_transacciones_gs.
And after:
DATA: begin of t_simples occurs 0.
include structure ty_simples.
include structure ty_transacciones_gs.
data: end of t_simples.
I have got a verification error.
Thanks!

Hi,
Use as follow,
TYPES: BEGIN OF ty_simples,
       agr_name LIKE agr_define-agr_name,
       text1 LIKE agr_texts-text.
TYPES: END OF ty_simples.
TYPES: BEGIN OF ty_transacciones_gs,
        tcode LIKE agr_tcodes-tcode,
        text2 LIKE bmeniface-text.
TYPES: END OF ty_transacciones_gs.
* INTERNAL TABLES
data: BEGIN OF t_simples occurs 0.
        INCLUDE TYPE ty_simples.
        INCLUDE TYPE type ty_transacciones_gs.
data: END OF t_simples.
Regards.
Marcelo Ramos

Problem in declaring internal table

hai experts ,
i am new to web dynpro abap .. my problem is i want to declare a internal table for a table using the web dynpro code wizard .. i found many threads regarding that .. but for mee its not working .. many of them posted that get_static_attributes_table method will solve the problem .. but i used the method in the wizard but it saying that method does not exist ..pls solve the problem ..
say where to enter the method in the wizard ..
thanks & kind regards
chinnaiya

Hi Chinnaiya,
Your post isnt that clear as to what you intend to do. Do you intend to just create an internal table declaration which would be able to hold your context nodes data or do you wish to use the get_static_attributes method to fetch all your tables data into this internal table?
If you want to just declare an internal table which can hold the data then you would have to do it manually. You can't generate your internal table declaration using the code wizard. Suppose your context nodes name is SFLIGHT then you can use the below syntax to declare a table & work area respectively.
DATA: lt_sflight TYPE wd_this->elements_sflight, " Internal table
wa_sflight TYPE wd_this->element_sflight. " Work area
For each node <node> of a controller context, a structure type element_<node> is implicitly generated in the interface IF_<ctrl>. The structure fields correspond to the attributes a node element consists of. Similarly for each node <node> of a controller context, a standard table type elements_<node> is implicitly generated in the interface IF_<ctrl>. The line type of this table is element_<node>. This constant can be used to
type an internal table that can hold the attributes of multiple node elements. So as how said here you can even declare the work area and internal table like shown below in your MAIN view:
DATA: lt_sflight TYPE if_main=>elements_sflight, " internal table
wa_sflight TYPE if_main=>element_sflight. " work area
But the disadvantage of this approach as how pointed out by Thomas in 1 of this earlier threads is that this coding works fine only for this particular view. If you copy the same code and try to use it in another view say VIEW1 then it wouldn't work as the interface name would have changed from if_main to if_view1. So its suggested to use the earlier approach.
Regards,
Uday

Short dump-internal table size issue

Hi,
I get the following message in the short dump analysis for a report.
No storage space available for extending table "IT_920".
You attempted to extend an internal table, but the required space was not available.
Error Analysis:
The internal table "IT_920" could not be enlarged further.
To extend the internal table, 9696 bytes of storage space was
needed, but none was available. At this point, the table "IT_920" has
1008240 entries.
Its an old report and I saw the internal table declaration using the "OCCURS" clause in the internal table declaration.
begin of itab occurs 100.
end of itab.
I tried the option of changing to "OCCURS 0", still issue persists.
Any help would be highly appretiated
CM

Hello CMV,
This is basic problem with SAP internal tables. For every internal table memory is alocated ( Max..256K)...once you cross the memory size/limit of the internal table it resuls in short dump.
Only way to overcome this problem is handle limited number of records at a time..
Please refer following sample code which will help you to avoid short dump while processing large number of records....
SORT TAB_RESULT.
DESCRIBE TABLE TAB_RESULT LINES W_RECORDS.
W_LOW      = 1.
W_UP       = 1000.
*Spliting the records from tab_result1 by pakage of 1000 at a time
*to avoid short dump in case of more records
WHILE W_LOW <= W_RECORDS.
    R_PKUNWE-SIGN = 'I'.
    R_PKUNWE-OPTION = 'EQ'.
    R_WERKS-SIGN = 'I'.
    R_WERKS-OPTION = 'EQ'.
    LOOP AT TAB_RESULT FROM W_LOW TO W_UP.
      MOVE TAB_RESULT-PKUNWE TO R_PKUNWE-LOW.
      MOVE TAB_RESULT-WERKS TO R_WERKS-LOW.
      APPEND R_PKUNWE.
      APPEND R_WERKS.
    ENDLOOP.
*fetch sold to party
     SELECT KUNNR NAME1
       FROM KNA1
       APPENDING CORRESPONDING FIELDS OF TABLE TAB_KNA1
       WHERE KUNNR IN R_PKUNWE.
*fetch plant
SELECT WERKS NAME1
         FROM T001W
         APPENDING CORRESPONDING FIELDS OF TABLE TAB_T001W
         WHERE WERKS IN R_WERKS.
   REFRESH: R_PKUNWE,
            R_WERKS.
    W_LOW = W_LOW + 1000.
    W_UP = W_UP + 1000.
ENDWHILE.
Hope this will help you to solve problem.
Cheers,
Nilesh

Submit report using internal table

Hi Experts!!,
REPORT 1
TYPES:   BEGIN OF ty_out_table,
         partner LIKE /sapsll/pntbp-partner,
         bpvsy   LIKE /sapsll/pntbp-bpvsy,
         country LIKE adrc-country,
        END OF ty_out_table.
internal table declaration & definition
DATA: gt_out_table TYPE STANDARD TABLE OF ty_out_table
               WITH KEY partner
                        bpvsy.
I have data in internal table gt_out_table.
I want to pass data gt_out_table in report 2. using SUBMIT REPORT.
How to do that ?
REPORT 2
select-options: s_partnr for /sapsll/pntbp-bpvsy.
parameters: p_upd,
                  p_value .
please suggest.
Thanks
Anee

hai,
... WITH SELECTION-TABLE rspar
Effect
If you specify this addition, parameters and selection criteria on the selection screen are supplied from an internal table rspar. You must specify an internal table with the row type RSPARAMS for rspar. The structured data type RSPARAMS is defined in the ABAP Dictionary and has the following components, all of which are data type CHAR:
SELNAME (length 8),
KIND (length 1),
SIGN (length 1),
OPTION (length 2),
LOW (length 45),
HIGH (length 45).
To supply parameters and selection criteria for the selection screen with specific values, the lines in the internal table rspar must contain the following values:
SELNAME must contain the name of a parameter or selection criterion for the selection screen in block capitals
KIND must contain the type of selection screen component (P for parameters, S for selection criteria)
SIGN, OPTION, LOW, and HIGH must contain the values specified for the selection table columns that have the same names as the selection criteria; in the case of parameters, the value must be specified in LOW and all other components are ignored.
If the name of a selection criterion is repeated in rspar, this defines a selection table containing several lines and passes it on to the selection criterion. If parameter names occur several times, the last value is passed on to the parameter.
The contents of the parameters or selection tables for the current program can be entered in the table by the function module RS_REFRESH_FROM_SELECTOPTIONS.
Notes
In contrast to selection tables, the data types of the components LOW and HIGH in table rspar are always of type CHAR and are converted to the type of the parameter or selection criterion during transfer, if necessary.
When entering values, you must ensure that these are entered in the internal format of the ABAP values, and not in the output format of the screen display.

Insert specific line in an internal table at a specific place

Hi
i have an internal table (itab) let's say
Name1 Name2 NUM1 NUM2 NUM3
Which already populater with data.
i have to do a subtotal for every NAME1 and insert a line just after the NAME1 in the internal table
and another subtotal by every NAME1 NAME2 and insert a line just after every NAME1 and NAME2 in the internal table
then another Grand total at the end of the table
My psudeo code is a bit like that but the insert is done in the wrong row
Index=1
LOOP at itab index
if itab-name1 NE old
insert structure in itab index
elseif itab-name1 NE old and itab-name2 NE old
insert structure in itab index
elseif itab EQ last line
insert structure in itab index
else
structure-num1 = structure-num1 + itab-num1
structure-num2 = structure-num2 + itab-num2
endif
index = index + 1
endloop
Do you think i need to use a temporary table here. can u guide me in code plz..

sort internal table by name1 and name2. <b>Have name1 and name2 as the first two variables in the internal table</b>
declare a work area and an internal table with the same structure as internal table.
declare num1 as type itab-num1.
num2 and i_num2 type itab-num2.
sort itab by name1 and name2.
loop the internal itab1.
append itab1 to itab2.
wa-num1 = structure-num1 + itab-num1
wa-num2 = structure-num2 + itab-num2.
i_num2 = i_num2 + itab-num2.
num1 = num1 + itab-num1.
num2 = num2 + itab-num2.
at end of name2.
append wa to itab2.
clear wa_name2.
endat.
at end of name1.
wa-num2 = i_num2.
append wa to itab2.
clear: i_num2, wa.
endat.
at last.
wa-num1 = num1.
wa-num2 = num2.
append wa_itab2.
endat.
endloop.
Thanks.

How to search for a field and its value in an internal table

Hi,
I want to search for a field(which i dont know whether it exists or not) in an internal table and on finding that field, I have to update the value of that field. How do I do it? I think its similar to how SEARCH works but i wanted to know the internal table eqivalent of it.

Hi Sujay,
this code will help ful to u, just gi through it,
TABLES : KNA1,VBAK,VBAP.
***********INTERNAL TABLE DECLARATIONS****************
DATA : IT_KNA1 TYPE TABLE OF KNA1,
       WA_KNA1 TYPE KNA1.
DATA : IT_VBAK TYPE TABLE OF VBAK,
       WA_VBAK TYPE VBAK.
DATA : IT_VBAP TYPE TABLE OF VBAP,
       WA_VBAP TYPE VBAP.
START-OF-SELECTION.
SELECT * FROM KNA1
INTO TABLE IT_KNA1
WHERE KUNNR = P_CUST.
IF NOT IT_KNA1 IS INITIAL.
    SELECT * FROM VBAK
    INTO TABLE IT_VBAK
    FOR ALL ENTRIES IN IT_KNA1
    WHERE KUNNR = IT_KNA1-KUNNR.
    IF NOT IT_VBAK IS INITIAL.
      SELECT * FROM VBAP
      INTO TABLE IT_VBAP
      FOR ALL ENTRIES IN IT_VBAK
      WHERE VBELN = IT_VBAK-VBELN.
    ELSE.
      WRITE : / 'Customer',P_CUST,'does not exist ......'.
    ENDIF.
ELSE.
    WRITE: / 'sales order does not exist for',P_CUST.
ENDIF.
Rewards points plz if useful
Ganesh.

How to get the data in one internal table? with 3 different tables..

Hi,
i need to get the all the ff data to put in an internal table. I'm using these data to my ALV. Thanks
   vkorg TYPE a005-vkorg,
   vtweg TYPE a005-vtweg,
   kschl TYPE a005-kschl,
   kondm TYPE mvke-kondm,
   matnr TYPE a005-matnr,
   kdgrp TYPE knvv-kdgrp,
   konda TYPE knvv-konda,
   kunnr TYPE a005-kunnr,
   datab TYPE a005-datab,

hi,
try this
*& Report ZPROGRAM
REPORT ZPROGRAM.
table declaration.
tables : zemployee, zdepartment,zproject.
*type-pools declaration
type-pools : slis , icon.
type specification
types : begin of ty_emp,
        empid type zempid,
        empname type zempname,
        empaddress type zempaddress,
        city type zcity,
        ponumber type zponumber,
        detid type zdeptid,
        end of ty_emp.
types : begin of ty_dept,
        detid type zdeptid,
        deptname type zdeptname,
        designation type zdesignation,
        projectid type zprojectid,
        end of ty_dept.
types : begin of ty_project,
        projectid type zprojectid,
        technology type ztechnology,
        clientname type zclientname,
        end of ty_project.
types : begin of ty_final,
        empid type zempid,
        empname type zempname,
        empaddress type zempaddress,
        city type zcity,
        ponumber type zponumber,
        detid type zdeptid,
        deptname type zdeptname,
        designation type zdesignation,
        projectid type zprojectid,
        technology type ztechnology,
        clientname type zclientname,
       average type p decimals 2,
        end of ty_final.
table type specification.
types : tt_emp type standard table of ty_emp,
        tt_dept type standard table of ty_dept,
        tt_project type standard table of ty_project,
        tt_final type standard table of ty_final.
work area creation.
data : wa_emp type ty_emp,
       wa_dept type ty_dept,
       wa_project type ty_project,
       wa_final type ty_final.
internal table declaration
data : itab_emp type tt_emp,
        itab_dept type tt_dept,
        itab_project type tt_project,
        itab_final type tt_final.
layout declaration
data : gd_layout type slis_layout_alv.
assigning current program name.
data : gd_repid like sy-repid.
         gd_repid = sy-repid.
fieldcatalog declaration.
data : d_fieldcat type slis_t_fieldcat_alv,
         d_fieldcat_wa type slis_fieldcat_alv.
header declaration.
data : t_header type slis_t_listheader,
         wa_header type slis_listheader,
         linecount(10) type c,
         line(10) type c.
selection-screen.
selection-screen : begin of block blk1 with frame title text-001.
select-options : s_empid for zemployee-empid.
parameters : p_dname like zdepartment-deptname.
parameters : p_proid like zproject-projectid.
selection-screen : begin of line.
parameters : p_rad1 radiobutton group r1.
selection-screen comment 3(10) text-002.
parameters : p_rad2 radiobutton group r1.
selection-screen comment 16(10) text-003.
selection-screen : end of line.
parameters : chk1 as checkbox.
selection-screen : end of block blk1.
end of selection screen.
start of selection.
select empid empname empaddress city ponumber detid from zemployee into corresponding fields of table itab_emp where empid in s_empid.
if not itab_emp is initial.
select detid deptname designation projectid from zdepartment into corresponding fields of table itab_dept for all entries in itab_emp where detid = itab_emp-detid .
if not itab_dept is initial.
select projectid technology clientname from zproject into corresponding fields of table itab_project for all entries in itab_dept where projectid = itab_dept-projectid.
endif.
endif.
*end of selection.
populating data into itab_final from itab_emp.
loop at itab_emp into wa_emp.
wa_final-empid = wa_emp-empid.
wa_final-empname = wa_emp-empname.
wa_final-empaddress = wa_emp-empaddress.
wa_final-ponumber = wa_emp-ponumber.
wa_final-city = wa_emp-city.
wa_final-detid = wa_emp-detid.
append wa_final to itab_final.
clear wa_final.
endloop.
*populating data into itab_final from itab_dept and itab_project
loop at itab_final into wa_final.
read table itab_dept into wa_dept with key detid = wa_final-detid.
if sy-subrc = 0.
wa_final-deptname = wa_dept-deptname.
wa_final-designation = wa_dept-designation.
wa_final-projectid = wa_dept-projectid.
modify itab_final from wa_final transporting deptname designation projectid .
endif.
read table itab_project into wa_project with key projectid = wa_final-projectid.
if sy-subrc = 0.
wa_final-technology = wa_project-technology.
wa_final-clientname = wa_project-clientname.
modify itab_final from wa_final transporting technology clientname.
endif.
endloop.
if p_rad1 = 'X' or chk1 = 'X'.
d_fieldcat_wa-fieldname = 'EMPID'.
d_fieldcat_wa-seltext_l = 'Employee Id'.
d_fieldcat_wa-emphasize = 'X'.
d_fieldcat_wa-col_pos = 1.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'EMPNAME'.
d_fieldcat_wa-seltext_l = 'Employee Name'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 2.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'EMPADDRESS'.
d_fieldcat_wa-seltext_l = 'Employee Address'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 3.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'CITY'.
d_fieldcat_wa-seltext_l = 'City'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 4.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'PONUMBER'.
d_fieldcat_wa-seltext_l = 'Postal Number'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 5.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'DETID'.
d_fieldcat_wa-seltext_l = 'Department Id'.
d_fieldcat_wa-emphasize = 'X'.
d_fieldcat_wa-col_pos = 6.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'DEPTNAME'.
d_fieldcat_wa-seltext_l = 'Department Name'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 7.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'DESIGNATION'.
d_fieldcat_wa-seltext_l = 'Designation'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 8.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'PROJECTID'.
d_fieldcat_wa-seltext_l = 'Project Id'.
d_fieldcat_wa-emphasize = 'X'.
d_fieldcat_wa-col_pos = 9.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'TECHNOLOGY'.
d_fieldcat_wa-seltext_l = 'technology'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 10.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'CLIENTNAME'.
d_fieldcat_wa-seltext_l = 'Client Name'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 11.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
endif.
if p_rad2 = 'X' or chk1 = 'X'.
refresh itab_emp.
d_fieldcat_wa-fieldname = 'DETID'.
d_fieldcat_wa-seltext_l = 'Department Id'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 6.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'DEPTNAME'.
d_fieldcat_wa-seltext_l = 'Department Name'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 7.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'DESIGNATION'.
d_fieldcat_wa-seltext_l = 'Designation'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 8.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'PROJECTID'.
d_fieldcat_wa-seltext_l = 'Project Id'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 9.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'TECHNOLOGY'.
d_fieldcat_wa-seltext_l = 'technology'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 10.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
d_fieldcat_wa-fieldname = 'CLIENTNAME'.
d_fieldcat_wa-seltext_l = 'Client Name'.
d_fieldcat_wa-emphasize = 'C710'.
d_fieldcat_wa-col_pos = 11.
append d_fieldcat_wa to d_fieldcat.
clear d_fieldcat_wa.
endif.
Grid display function module
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
   I_INTERFACE_CHECK                 = ' '
   I_BYPASSING_BUFFER                = ' '
   I_BUFFER_ACTIVE                   = ' '
    I_CALLBACK_PROGRAM                = gd_repid
    I_CALLBACK_PF_STATUS_SET          = 'SET_PF_STATUS'
   I_CALLBACK_USER_COMMAND           = ' '
    I_CALLBACK_TOP_OF_PAGE            = 'TOP_OF_PAGE '
   I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
   I_CALLBACK_HTML_END_OF_LIST       = ' '
   I_STRUCTURE_NAME                  =
   I_BACKGROUND_ID                   = ' '
    I_GRID_TITLE                      = 'EMPLOYEE DETAILS'
   I_GRID_SETTINGS                   =
    IS_LAYOUT                         = gd_layout
    IT_FIELDCAT                       = d_fieldcat
   IT_EXCLUDING                      =
   IT_SPECIAL_GROUPS                 =
   IT_SORT                           =
   IT_FILTER                         =
   IS_SEL_HIDE                       =
   I_DEFAULT                         = 'X'
   I_SAVE                            = ' '
   IS_VARIANT                        =
   IT_EVENTS                         =
   IT_EVENT_EXIT                     =
   IS_PRINT                          =
   IS_REPREP_ID                      =
   I_SCREEN_START_COLUMN             = 0
   I_SCREEN_START_LINE               = 0
   I_SCREEN_END_COLUMN               = 0
   I_SCREEN_END_LINE                 = 0
   I_HTML_HEIGHT_TOP                 = 0
   I_HTML_HEIGHT_END                 = 0
   IT_ALV_GRAPHICS                   =
   IT_HYPERLINK                      =
   IT_ADD_FIELDCAT                   =
   IT_EXCEPT_QINFO                   =
   IR_SALV_FULLSCREEN_ADAPTER        =
IMPORTING
   E_EXIT_CAUSED_BY_CALLER           =
   ES_EXIT_CAUSED_BY_USER            =
   TABLES
     T_OUTTAB                          = itab_final
EXCEPTIONS
    PROGRAM_ERROR                     = 1
    OTHERS                            = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
set pf_status for creating client specified icons.
form set_pf_status using rt_extab type slis_t_extab.
set pf-status 'NEWSTATUS'.
endform.
populating data into header using top_of_page
form top_of_page.
wa_header-typ = 'H'.
wa_header-info = 'ALV REPORT'.
append wa_header to t_header.
clear wa_header.
wa_header-typ = 'S'.
wa_header-key = 'Date :'.
Concatenate sy-datum+6(2) '.'
             sy-datum+4(2) '.'
             sy-datum(4) into wa_header-info.
append wa_header to t_header.
clear wa_header.
wa_header-typ = 'S'.
wa_header-key = 'Time :'.
Concatenate sy-Uzeit(2) '.'
             sy-datum+2(2) '.'
             sy-datum+4(2) into wa_header-info.
append wa_header to t_header.
clear wa_header.
describe table itab_final lines line.
wa_header-typ = 'A'.
linecount = line.
Concatenate 'Total number of records :' linecount into wa_header-info separated by space.
append wa_header to t_header.
clear wa_header.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      IT_LIST_COMMENTARY       = t_header
     I_LOGO                   = 'VMCADMIN'
    I_END_OF_LIST_GRID       =
    I_ALV_FORM               =
endform.
*designing layout.
form gd_layout.
gd_layout-zebra = 'X'.
gd_layout-edit = 'X'.
gd_layout-no_hotspot = ''.
gd_layout-no_colhead = ''.
gd_layout-colwidth_optimize = 'X'.
endform.
Reward with points if helpful.

Internal table in user exit

Hi,
I am using user exit "MV45AFZZ" - Sales order, I have declaired one internal table in userexit_save_document_prepare and storing some data in it.
FORM userexit_save_document_prepare.
ENDFORM.
I wish to use the data from internal table declared in userexit_save_document_prepare in
FORM userexit_save_document.
ENDFORM.
Should i declare the internal table at some other place so that it can be accessed from other user exits.

Hi Ganesh,
You are asking if your internal table can be declared globally. I don't believe there is an area (an include program for example) in SAPMV45A that allows customers to declare their own global data. This would of course be the most straight-forward solution, but if we don't have this option, you can always do something like this:
FORM userexit_save_document_prepare.
EXPORT my_itab TO MEMORY ID 'CUST_MEMORY'.
ENDFORM.
And then this:
FORM userexit_save_document.
IMPORT my_itab FORM MEMORY ID 'CUST_MEMORY'.
ENDFORM.
Regards,
Jamie

Internal table declaration

Similar Messages

Maybe you are looking for