Creating Types and Internal table

Hi,
I created
Types: begin of itab,
           field 1 ...
            Field 30,
        End of itab.
Data: lt_itab type table of itab.
I need to create a second type itab1 with all the itab fields and also new fields field31 and field32.
I dont want to declare all the 30 fields again for the second one.
Can any one tell me how to create this?
Thanks.
rajesh

You can INCLUDE TYPE.
Types: begin of itab,
       field1 type string,
       field2 type string,
*      More Fields in here.
       Field30 type string,
       End of itab.
Data: lt_itab type table of itab.
TYPES BEGIN OF new_itab.
       INCLUDE type itab.
TYPES: field31 type string,
       field32 type string,
END OF new_itab.
Regards,
Rich Heilman

Similar Messages

Difference between line type and internal table?

Hi..
I wanted to know, what is the difference between Line type and Internal Table?

Hi,
Before the 4.7 release in SAP if we want to define an internal table we have to write the defination using the occurs statement and we need to define all the fields using INCLUDE STRUCTURE or indidually all the fields ine by one.
From 4.7 release of R/3 SAP introduced the Line type concept and it's part of the ABAP OOPS concept. for internal table defination we don't need to use the occur statements. Instead INCLUDE structure we need to create a Line type for that structure in Se11 and then we can define the internal table like :
DATA : ITAB TYPE TABLE OF <LINE_TYPE>.
Only thing is this table will be a table without header. So for internal table processing we need to define a work area structure of type line of line type . EX:
DATA: WA_ITAB TYPE LINE OF <LINE_TYPE>.
Hope this helps.
Thanks,
Greetson

Table types and internal table

Hi all,
What is the relationship between table type in ABAP dictionary and internal table?
Moderator message : Search for available information OR read ABAP documentation. Thread locked.
Edited by: Vinod Kumar on Jul 16, 2011 11:16 AM

You can INCLUDE TYPE.
Types: begin of itab,
       field1 type string,
       field2 type string,
*      More Fields in here.
       Field30 type string,
       End of itab.
Data: lt_itab type table of itab.
TYPES BEGIN OF new_itab.
       INCLUDE type itab.
TYPES: field31 type string,
       field32 type string,
END OF new_itab.
Regards,
Rich Heilman

Diference between DATA: and TYPES: on internal tables

Hi people,
Can somebody help me. I wanna know whats the diference between DATA: and TYPES: on internal tables
and whitch has the best performance, here is a eg:
DATA: BEGIN OF ti_sbook occurs 0,
          carrid   LIKE sbook-carrid,
          fldate   LIKE sbook-fldate,
          customid LIKE sbook-customid,
          loccuram LIKE sbook-loccuram,
       END OF ti_sbook.
AND
TYPES: BEGIN OF ti_sbook ,
          carrid   LIKE sbook-carrid,
          fldate   LIKE sbook-fldate,
          customid LIKE sbook-customid,
          loccuram LIKE sbook-loccuram,
       END OF ti_sbook.
DATA: gw_sbook       TYPE TABLE OF ti_sbook,
gs_sbook       TYPE ti_sbook.
witch of both types is better?
thanks.

Hi Marcelo,
For compatibility matters is better to create internal tables with a work area separately. So yes it's better to use types. When you work with Object Oriented coding you will need to use internal tables defined with types. Also when defining tables with types is the new way of coding, the another coding is getting obsolete defined by SAP. That's why when working in ABAP with OO (Object Oriented) code you'll have to define tables with types and not the other way.
Hope it helps.
Regards,
Gilberto Li

Error while creating a dynamic internal table refers to custom field

Hi all,
I am getting the exception TYPE_NOT_FOUND when I try to create a dynamic internal table using:-
DATA: gr_desc TYPE REF TO cl_abap_typedescr.
gr_desc = cl_abap_typedescr=>describe_by_name( p_field ).
The field p_field is a Z-field inside a DB table, (e.g. a user added field in MARA). The statement fails at that point and gives a runtime exception. Any suggestions to how I may solve this problem? Or any alternatives for the same? I guess we face this issue for all custom fields..has SAP released a note for this??
Thanks..

that's just the wrong method, you should use DESCRIBE_BY_DATA
gr_desc = cl_abap_typedescr=>describe_by_data( p_field ).
Note: DESCRIBE_BY_NAME is to be used for referencing a DDIC type by its name. Example:
gr_desc = cl_abap_typedescr=>describe_by_name( 'MARA-ZZFIELD' ).

Assigning value to Field - Symbol ( which is type of internal table field )

Hi All,
I am facing problem to assign the value to a field symbol. My requirement is creating a dynamic internal table and populate values into that internal table, so that i can display the values .
I am having a structure with fields like status , Plant1 name , Plant2 name.....Plant n .
So i declared an internal table it_tab with this structure.
I am having one more table which having number of records for Plant1 ,Plant 2 ,....Plant n based on some condition.
I need to count the number of records for Plant1 and i need to put in the internal table it_tab.
For this i created field-symbol .
Here, t_deployment table will have the plants 1,2,3...and
 t_devobject will have some records for these plants.
LOOP AT T_DEPLOYMENT.
clear w_count.
LOOP AT T_DEVOBJECT WHERE ZDEPLOYMENT = T_DEPLOYMENT-DOMVALUE_L AND
 ZADSTATUS = '10'.
w_count = w_count + 1.
ENDLOOP.
concatenate 'it_tab-' t_deployment-domvalue_l into var_bet_name.
assign var_bet_name to <bet_var_name>.
now my internal table field i.e. it_tab-plant1 came into <bet_var_name> . But i want to assign a value for it.
at last what i need is it_tab-plant1 = w_count.
whaterver the w_count has value that needs to assign to it_tab-plant1. But i don't want to assign directly it it_tab-plant1. I want to assign dynamically. Because tommorrow some more plants added to t_deployments , i don't want to make changes to my program. It should take care....w/o changing the program.
I tried the following statement.
(<bet_var_name>) = w_count. But its not working.
Please let me know how i can get this.
Thanks in Advance.
Pavan.

Hi pavan,
As ur requirement is creating a dynamic internal table,
try the following way,
remember the fieldcat should be of type LVC not SLIS.
BUILD LT_LVCFIELDCAT in a way that, the value from the internal table becomes the fieldname
ex:-
loop at it_models INTO WA_MODELS.
 LS_LVCFIELDCAT-FIELDNAME = WA_models-MODEL.
 LS_LVCFIELDCAT-SELTEXT = WA_models-MODEL.
append ls_lvcfieldcat to lt_lvcfieldcat.
endloop.
DATA: DREF TYPE REF TO DATA,WA_REF TYPE REF TO DATA.
FIELD-SYMBOLS: <TEMP_TAB> TYPE TABLE, <TEMP_WA> TYPE ANY.
CALL METHOD CL_ALV_TABLE_CREATE=>CREATE_DYNAMIC_TABLE
 EXPORTING
 IT_FIELDCATALOG = LT_LVCFIELDCAT
 IMPORTING
 EP_TABLE = DREF.
ASSIGN dref->* TO <TEMP_TAB>.
now basing on the fieldcatalog <temp_tab> is build.
NOW FILL <TEMP_TAB>.
WHILE FILLING, ASSIGN COMPONENT IDX/NAME.....
this statement will be very usefull.
i hope this will be help full.
pls reward the points if it helps u.
regards
Hyma

SAP QUERY LOOPS AND INTERNAL TABLE

Hi All, I have a query which i have made. It runs from Table EKPO which has PO details and what I want to do is now via ABAP Code pull through the total of goods receipt for the PO and Line Item into a field. Sounds Easy enough..Problem now,
The table which contains the GR data is EKBE which agains a PO and Line Item can have many 101 movements and 102 movements so what I want is an ABAP Statent to basically sum up the total of 101 for the PO & LINE ITEMS and then minus this from the total of 102 for the PO & LINE ITEMS and post the result in to this new field I have created.
I am pretty decent with ABAP Code in Querys I.e Select statements etc but from what I can see i need to create an internal table and do a loop and collect statement but I keep on failing due to not enough knowledge. Please can some one help me with this and provide me with the code and explanation as i would like to understand,
POINTS WILL BE REWARDED
Thanks
Kind Regards
Adeel Sarwar

Hi,
This is the full code i have entered but its not working. Any help would be appreciated. If you could rectify the code and internal tables that would be great.
Thanks
TABLES: EKBE.
DATA: PurO LIKE EKPO-EBELN,
      POLI LIKE EKPO-EBELP.
*New Table and Vars defined
DATA:   BEGIN OF IT_EKBE,
          IT_EKBE LIKE EKBE,
        END OF IT_EKBE.
DATA: BEGIN OF IT_SUM OCCURS 0,
          EBELN TYPE EBELN,
          EBELP TYPE EBELP,
          DMBTR TYPE DMBTR,
          MENGE TYPE MENGE,
      END OF IT_SUM.
CLEAR: QTYD.
MOVE: EKPO-EBELN TO PurO,
      EKPO-EBELP TO POLI.
SELECT * FROM EKBE INTO IT_EKBE
    WHERE EBELN = PurO
    AND   EBELP = POLI
    AND   BEWTP = 'E'
LOOP AT IT_EKBE.
MOVE CORRESPOING IT_EKBE TO IT_SUM.
IF IT_EKBE-BWART = '102'.
    IT_SUM-DMBTR = IT_SUM-DMBTR * -1.
    IT_SUM-MENGE = IT_SUM-MENGE * -1.
ENIDF.
COLLECT IT_SUM.
CLEAR IT_SUM.
ENDLOOP.
ENDSELECT.
If sy-subrc = 0.
QTYD = IT_SUM.
ELSE.
QTYD = 0.
ENDIF.

Dynamic Structures and Internal Tables

Hi All,
I am doing a report to create condition records based on the condition type and condition table. Assume the condition type as PR00 and it as condition table of 304,305,306.Each condition table as its own header and item fields.Based on the condition table that the user specifies in the selection screen
the header and item structures of my report should change dynamically and these should be moved to the dynamic internal table that contains both header and item fields.Can anyone give an idea how to achieve it. Thanks in advance.
Regards,
Chakradhar.

Hi All,
Thanks for your replies.
SPLIT i_string_line-input_str AT cl_abap_char_utilities=>horizontal_tab
INTO i_header_line-header
          i_header_line-vkorg
          i_header_line-vtweg
          i_header_line-pltyp
         i_header_line-waerk.
In the above syntax based on the condition table I selected on selection screen my flat file is as below.
case 1: If condition table given is 304
H    SalesOrganization    DistributionChannel    Customer
I    Material    Releasestatus    Amount    Currency    ValidFrom    ValidTo
case 2: If condition table given is 305
H    SalesOrganization    DistributionChannel
I    Material    Releasestatus    Amount    Currency    ValidFrom    ValidTo
case 3: If condition table given is 306
H    SalesOrganization    DistributionChannel     PriceListType     DocumentCurrency
I    Material    Releasestatus    Amount    Currency    ValidFrom    ValidTo
In the above code i_string_line-input_str contains the following heading of fields based on the condition table we select in selection screen.when I want to split them into respective fields
using INTO clause my structure should change dynamically.How can I achieve it and my entire program is in OOPS ALV.Thanks in Advance.
Regards,
Chakradhar.

Dynamic ALV and internal table.

Hi all,
I have a requirement of creating a dynamic field catelog based on input values in selection screen.
Example:
1) When I enter date range, say 20/03/2008 to 25/03/2008 I should have 6 columns in the output for each date with column heading as date itself.
2) For entering values for these date columns, i need to create an dynamic internal table.(values in the column will be some numbers like 10 on 20/03/2008, 15 on 21/03/2008 etc)
A rough output format would look like this:
Component | 20/03/2008 | 21/03/2008 | ..... |25/03/2008
comp1 | 10 | 15 | | 5
comp2 | 20 | 10 | | 10
Please let me know how can i achieve this...
Need it very urgently..
Regards,
Dhareppa

Hi Dhareppa,
Refer the code below. Its almost on the same line as your requirments.
REPORT zglo2fr_master_planing_sedul NO STANDARD PAGE HEADING.
 P R O G R A M H E A D E R *
 ArthroCare Corporation *
Program : ZGLO2FR_MASTER_PLANING_SEDUL *
Author : Munvar Basha *
Creation Date : 11Mar08 *
Release : SAP ECC 6.0 *
Request : D01K904032 *
Description : Master Schedule Planning *
Change log (Revisions) *
Author Date Request Description *
 P R O G R A M *
 DATA DECLARATION *
**--Structure to hold matrial & plant combination records.
TYPES : BEGIN OF ty_marc,
 matnr TYPE matnr,
 werks TYPE werks_d,
 dispo TYPE dispo,
 beskz TYPE beskz,
 mtart TYPE mtart,
 END OF ty_marc.
**--structure to hold MRP LIST Data.
TYPES : BEGIN OF ty_mrp_list,
 matnr TYPE matnr,
 werks TYPE werks_d,
 maktx TYPE maktx,
 meins TYPE meins,
 mtart TYPE mtart,
 week TYPE kweek,
 mng01 TYPE mng01,
 delkz TYPE delkz,
 END OF ty_mrp_list.
**--structure to hold no of weeks.
TYPES: BEGIN OF ty_week,
 week TYPE kweek,
 END OF ty_week.
**--structure to hold output data.
TYPES : BEGIN OF ty_final,
 matnr TYPE matnr,
 werks TYPE werks_d,
 maktx TYPE maktx,
 meins TYPE meins,
 mtart TYPE mtart,
 week TYPE kweek,
 mng01 TYPE mng01,
 END OF ty_final.
TYPES : BEGIN OF ty_range,
 sign TYPE sign,
 option TYPE option,
 low TYPE sy-datum,
 high TYPE sy-datum,
 END OF ty_range.
 Definitions of Table types. *
TYPES : ty_marctab TYPE STANDARD TABLE OF ty_marc.
 Definitions of Ranges *
*RANGES ran_delkz FOR mdez-delkz.
DATA : i_ran_delkz TYPE RANGE OF mdez-delkz,
 wa_ran_delkz LIKE LINE OF i_ran_delkz,
 wa_date type ty_range.
 Definitions of internal tables. *
data : i_marc type standard table of ty_marc,
 i_mrp_list type standard table of ty_mrp_list,
 i_week type standard table of ty_week,
 i_final type standard table of ty_final,
 i_mdps type standard table of mdps,
 i_mdez type standard table of mdez,
 i_mdsu type standard table of mdsu.
 Definitions of work areas for internal tables *
DATA : wa_marc TYPE ty_marc,
 wa_mrp_list TYPE ty_mrp_list,
 wa_week TYPE ty_week,
 wa_final TYPE ty_final,
 wa_mt61d TYPE mt61d,
 wa_mdez TYPE mdez.
 Definitiions of General variables *
DATA : v_matnr TYPE mara-matnr, " Material Number
 v_mtart TYPE mara-mtart, " Material Type
 v_beskz TYPE marc-beskz, " Procurement Type
 v_werks TYPE marc-werks, " Plant
 v_dispo TYPE marc-dispo. " MRP Controller (Materials Planner)
DATA : v_mng01 TYPE mng01. "Requirement Quantity
DATA : v_year TYPE char4,
 v_week TYPE char2,
 v_ok_code TYPE sy-ucomm.
 Definitiions of Constants *
CONSTANTS : k_slash TYPE c VALUE '/',
 k_6 TYPE char8 VALUE '6',
 k_x TYPE c VALUE 'X'.
 Definitiions of Field Catlog *
DATA : wa_fieldcat TYPE lvc_s_fcat,
 i_fieldcat TYPE lvc_t_fcat,
 v_container TYPE scrfname VALUE 'CONTAINER_OUTPUT',
 v_custom_container TYPE REF TO cl_gui_custom_container,
 v_grid TYPE REF TO cl_gui_alv_grid,
 i_gp_table TYPE REF TO data,
 wa_gp_line TYPE REF TO data.
FIELD-SYMBOLS: <gt_table> TYPE STANDARD TABLE,
 <gwa_table> TYPE ANY,
 <l_field> TYPE ANY,
 <l_matnr> TYPE ANY,
 <l_werks> TYPE ANY,
 <l_maktx> TYPE ANY,
 <l_meins> TYPE ANY,
 <l_mtart> TYPE ANY.
 DECLERATIONS FOR SELECTION SCREEN *
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS : s_matnr FOR v_matnr,
 s_mtart FOR v_mtart NO INTERVALS,
 s_beskz FOR v_beskz NO INTERVALS NO-EXTENSION,
 s_werks FOR v_werks NO INTERVALS NO-EXTENSION
 OBLIGATORY,
 s_dispo FOR v_dispo,
 s_date FOR sy-datum OBLIGATORY.
PARAMETERS : p_dattp TYPE dattp OBLIGATORY DEFAULT '1'.
SELECTION-SCREEN END OF BLOCK b1.
 INITIALIZATION EVENT *
INITIALIZATION.
CALL FUNCTION '/BEV4/PLPS__ADD_MONTH_TO_DATE'
 EXPORTING
 months = k_6
 olddate = sy-datum
 IMPORTING
 newdate = wa_date-high.
wa_date-low = sy-datum.
wa_date-option = 'EQ'.
wa_date-sign = 'I'.
APPEND wa_date to s_date.
 SELECTION SCREEN EVENT *
**--Validation for Material
AT SELECTION-SCREEN ON s_matnr.
PERFORM validate_material.
**--Validation for Plant
AT SELECTION-SCREEN ON s_werks.
PERFORM validate_plant.
 AT SELECTION-SCREEN ENENT *
AT SELECTION-SCREEN.
IF s_matnr IS INITIAL AND s_dispo IS INITIAL.
 MESSAGE text-002 TYPE 'E'.
ENDIF.
IF s_date-low LT sy-datum.
 MESSAGE text-003 TYPE 'E'.
ENDIF.
 START-OF-SELECTION EVENT *
START-OF-SELECTION.
**--refreshing the internal tables
REFRESH : i_marc,
 i_mrp_list,
 i_week,
 i_final,
 i_mdps,
 i_mdez,
 i_mdsu.
**--clearing the work areas of internal tables.
CLEAR : wa_marc,
 wa_mrp_list,
 wa_week,
 wa_final,
 wa_mt61d,
 wa_mdez.
To get all the matrial(s) and plant combination records
SELECT a~matnr
 a~werks
 a~dispo
 a~beskz
 b~mtart
 INTO TABLE i_marc
 FROM marc AS a INNER JOIN
 mara AS b
 ON a~matnr = b~matnr
 WHERE a~werks IN s_werks AND
 a~matnr IN s_matnr AND
 a~dispo IN s_dispo AND
 a~beskz IN s_beskz AND
 b~mtart IN s_mtart.
IF sy-subrc <> 0.
 MESSAGE text-005 TYPE 'S'.
 LEAVE LIST-PROCESSING.
ENDIF.
SORT i_marc BY matnr werks.
Ranges to Filter the MRP list only for the following MRP Elements.
MRP Elements are : BA, BE, FE, LE and PA
wa_ran_delkz-sign = 'I'.
wa_ran_delkz-option = 'EQ'.
wa_ran_delkz-low = 'BA'.
APPEND wa_ran_delkz TO i_ran_delkz.
CLEAR wa_ran_delkz-low.
wa_ran_delkz-low = 'BE'.
APPEND wa_ran_delkz TO i_ran_delkz.
CLEAR wa_ran_delkz-low.
wa_ran_delkz-low = 'FE'.
APPEND wa_ran_delkz TO i_ran_delkz.
CLEAR wa_ran_delkz-low.
wa_ran_delkz-low = 'LE'.
APPEND wa_ran_delkz TO i_ran_delkz.
CLEAR wa_ran_delkz-low.
wa_ran_delkz-low = 'PA'.
APPEND wa_ran_delkz TO i_ran_delkz.
CLEAR wa_ran_delkz-low.
LOOP AT i_marc INTO wa_marc.
 CALL FUNCTION 'MD_MRP_LIST_API'
 EXPORTING
 matnr = wa_marc-matnr
 werks = wa_marc-werks
 sinfg = k_x
 inper = p_dattp
 IMPORTING
 e_mt61d = wa_mt61d
 TABLES
 mdpsx = i_mdps
 mdezx = i_mdez
 mdsux = i_mdsu
 EXCEPTIONS
 mrp_list_not_found = 1
 material_plant_not_found = 2
 error = 3
 OTHERS = 4.
 IF sy-subrc = 0.
 LOOP AT i_mdez INTO wa_mdez WHERE dat00 IN s_date AND
 delkz IN i_ran_delkz.
 CALL FUNCTION 'DATE_GET_WEEK'
 EXPORTING
 date = wa_mdez-dat00
 IMPORTING
 week = wa_mrp_list-week
 EXCEPTIONS
 date_invalid = 1
 OTHERS = 2.
 IF sy-subrc = 0.
 wa_mrp_list-matnr = wa_mt61d-matnr.
 wa_mrp_list-werks = wa_mt61d-werks.
 wa_mrp_list-maktx = wa_mt61d-maktx.
 wa_mrp_list-meins = wa_mt61d-meins.
 wa_mrp_list-mtart = wa_mt61d-mtart.
 wa_mrp_list-delkz = wa_mdez-delkz.
 wa_mrp_list-mng01 = wa_mdez-mng01.
 APPEND wa_mrp_list TO i_mrp_list.
 CLEAR : wa_mrp_list,
 wa_mdez.
 ENDIF.
 ENDLOOP.
 ENDIF.
 CLEAR: wa_marc.
ENDLOOP.
IF i_mrp_list IS INITIAL.
 MESSAGE text-006 TYPE 'S'.
 LEAVE LIST-PROCESSING.
ENDIF.
CLEAR : v_mng01.
LOOP AT i_mrp_list INTO wa_mrp_list.
 v_mng01 = v_mng01 + wa_mrp_list-mng01.
 AT END OF week.
 wa_final-matnr = wa_mrp_list-matnr.
 wa_final-werks = wa_mrp_list-werks.
 wa_final-maktx = wa_mrp_list-maktx.
 wa_final-meins = wa_mrp_list-meins.
 wa_final-mtart = wa_mrp_list-mtart.
 wa_final-week = wa_mrp_list-week.
 wa_final-mng01 = v_mng01.
 wa_week-week = wa_mrp_list-week.
 APPEND : wa_final TO i_final,
 wa_week TO i_week.
 CLEAR : v_mng01,
 wa_final,
 wa_week.
 ENDAT.
 CLEAR : wa_mrp_list.
ENDLOOP.
**-- Populate the Field catalog
PERFORM populate_fieldcat.
**--Create table dynamically
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = i_fieldcat
 IMPORTING
 ep_table = i_gp_table.
ASSIGN i_gp_table->* TO <gt_table>.
**--fill table with final output data
PERFORM fill_table.
CALL SCREEN 100.
 SUB ROUTINES *
*& Form validate_material *
 Validating Material Number(s) *
FORM validate_material .
TYPES : BEGIN OF l_ty_matnr,
 matnr TYPE matnr,
 END OF l_ty_matnr.
DATA : l_i_matnr TYPE STANDARD TABLE OF l_ty_matnr.
SELECT matnr
 FROM mara
 INTO TABLE l_i_matnr
 WHERE matnr IN s_matnr.
IF sy-subrc <> 0.
 MESSAGE text-004 TYPE 'E'.
ENDIF.
ENDFORM. " validate_material
*& Form validate_plant *
 Validating Plant Number *
FORM validate_plant .
DATA : l_v_werks TYPE werks_d.
SELECT SINGLE werks
 FROM t001w
 INTO l_v_werks
 WHERE werks = s_werks-low.
IF sy-subrc <> 0.
 MESSAGE e019(zartc) WITH s_werks-low.
ENDIF.
ENDFORM. " validate_plant
*& Form populate_fieldcat
 text
--> p1 text
<-- p2 text
FORM populate_fieldcat .
DATA : l_v_colname TYPE char7.
SORT i_week BY week.
DELETE ADJACENT DUPLICATES FROM i_week COMPARING week.
LOOP AT i_week INTO wa_week.
 AT FIRST.
 wa_fieldcat-row_pos = 0.
 wa_fieldcat-col_pos = 1.
 wa_fieldcat-fieldname = 'MATNR'.
 wa_fieldcat-scrtext_l = text-007.
 wa_fieldcat-scrtext_m = text-007.
 wa_fieldcat-scrtext_s = text-007.
 wa_fieldcat-fix_column = 'X'.
 wa_fieldcat-outputlen = 18.
 wa_fieldcat-tooltip = text-007.
 APPEND wa_fieldcat TO i_fieldcat.
 CLEAR wa_fieldcat.
 wa_fieldcat-row_pos = 0.
 wa_fieldcat-col_pos = 2.
 wa_fieldcat-fieldname = 'WERKS'.
 wa_fieldcat-scrtext_l = text-008.
 wa_fieldcat-scrtext_m = text-008.
 wa_fieldcat-scrtext_s = text-008.
 wa_fieldcat-fix_column = 'X'.
 wa_fieldcat-outputlen = 4.
 wa_fieldcat-tooltip = text-008.
 APPEND wa_fieldcat TO i_fieldcat.
 CLEAR wa_fieldcat.
 wa_fieldcat-row_pos = 0.
 wa_fieldcat-col_pos = 3.
 wa_fieldcat-fieldname = 'MAKTX'.
 wa_fieldcat-scrtext_l = text-009.
 wa_fieldcat-scrtext_m = text-010.
 wa_fieldcat-scrtext_s = text-011.
 wa_fieldcat-tooltip = text-009.
 wa_fieldcat-outputlen = 40.
 APPEND wa_fieldcat TO i_fieldcat.
 CLEAR wa_fieldcat.
 wa_fieldcat-row_pos = 0.
 wa_fieldcat-col_pos = 4.
 wa_fieldcat-fieldname = 'MEINS'.
 wa_fieldcat-scrtext_l = text-012.
 wa_fieldcat-scrtext_m = text-013.
 wa_fieldcat-scrtext_s = text-014.
 wa_fieldcat-outputlen = 4.
 wa_fieldcat-tooltip = text-012.
 APPEND wa_fieldcat TO i_fieldcat.
 CLEAR wa_fieldcat.
 wa_fieldcat-row_pos = 0.
 wa_fieldcat-col_pos = 5.
 wa_fieldcat-fieldname = 'MTART'.
 wa_fieldcat-scrtext_l = text-015.
 wa_fieldcat-scrtext_m = text-015.
 wa_fieldcat-scrtext_s = text-016.
 wa_fieldcat-tooltip = text-015.
 APPEND wa_fieldcat TO i_fieldcat.
 CLEAR wa_fieldcat.
 ENDAT.
 v_year = wa_week-week+0(4).
 v_week = wa_week-week+4(2).
 CONCATENATE v_week k_slash v_year INTO l_v_colname.
 wa_fieldcat-row_pos = 0.
 wa_fieldcat-col_pos = 6 + sy-index.
 wa_fieldcat-fieldname = wa_week-week.
 wa_fieldcat-quantity = 'X'.
 wa_fieldcat-outputlen = 18.
 wa_fieldcat-scrtext_l = l_v_colname.
 wa_fieldcat-tooltip = l_v_colname.
 APPEND wa_fieldcat TO i_fieldcat.
 CLEAR : wa_fieldcat,
 l_v_colname,
 wa_week.
ENDLOOP.
ENDFORM. " populate_fieldcat
*& Form fill_table
 text
--> p1 text
<-- p2 text
FORM fill_table .
**--Create Work Area Dynamically
CREATE DATA wa_gp_line LIKE LINE OF <gt_table>.
ASSIGN wa_gp_line->* TO <gwa_table>.
DATA : l_v_col TYPE char25,
 l_v_val TYPE char25.
LOOP AT i_final INTO wa_final.
 l_v_col = wa_final-week.
 ASSIGN COMPONENT l_v_col OF STRUCTURE <gwa_table>
 TO <l_field>.
 IF <l_field> IS ASSIGNED.
 l_v_val = wa_final-mng01.
 CONDENSE l_v_val.
 <l_field> = l_v_val.
 clear : l_v_val,
 l_v_col.
 ENDIF.
 AT END OF matnr.
 READ TABLE i_final INTO wa_final WITH KEY matnr = wa_final-matnr
 BINARY SEARCH.
 IF sy-subrc = 0.
 ASSIGN COMPONENT 'MATNR' OF STRUCTURE <gwa_table>
 TO <l_matnr>.
 IF <l_matnr> IS ASSIGNED.
 <l_matnr> = wa_final-matnr.
 ENDIF.
 ASSIGN COMPONENT 'WERKS' OF STRUCTURE <gwa_table>
 TO <l_werks>.
 IF <l_werks> IS ASSIGNED.
 <l_werks> = wa_final-werks.
 ENDIF.
 ASSIGN COMPONENT 'MAKTX' OF STRUCTURE <gwa_table>
 TO <l_maktx>.
 IF <l_maktx> IS ASSIGNED.
 <l_maktx> = wa_final-maktx.
 ENDIF.
 ASSIGN COMPONENT 'MEINS' OF STRUCTURE <gwa_table>
 TO <l_meins>.
 IF <l_meins> IS ASSIGNED.
 <l_meins> = wa_final-meins.
 ENDIF.
 ASSIGN COMPONENT 'MTART' OF STRUCTURE <gwa_table>
 TO <l_mtart>.
 IF <l_mtart> IS ASSIGNED.
 <l_mtart> = wa_final-mtart.
 ENDIF.
 APPEND <gwa_table> TO <gt_table>.
 CLEAR <gwa_table>.
 ENDIF.
 ENDAT.
ENDLOOP.
ENDFORM. " fill_table
*& Module STATUS_0100 OUTPUT
 text
MODULE status_0100 OUTPUT.
SET PF-STATUS 'ZMUNNA'.
SET TITLEBAR 'MRP'.
IF v_custom_container IS INITIAL.
 CREATE OBJECT v_custom_container
 EXPORTING
 container_name = v_container.
 CREATE OBJECT v_grid
 EXPORTING
 i_parent = v_custom_container.
 CALL METHOD v_grid->set_table_for_first_display
 CHANGING
 it_outtab = <gt_table>
 it_fieldcatalog = i_fieldcat.
ENDIF.
ENDMODULE. " STATUS_0100 OUTPUT
*& Module USER_COMMAND_0100 INPUT
 text
MODULE user_command_0100 INPUT.
v_ok_code = sy-ucomm.
CLEAR sy-ucomm.
CASE v_ok_code.
 WHEN 'EXIT'.
 PERFORM exit_program.
 SET SCREEN 000.
ENDCASE.
ENDMODULE. " USER_COMMAND_0100 INPUT
*& Form exit_program
 text
--> p1 text
<-- p2 text
FORM exit_program .
CALL METHOD v_custom_container->free.
CALL METHOD cl_gui_cfw=>flush.
ENDFORM. " exit_program
Reward points if that helps.
Manish

Passing SELECT-OPTIONS and Internal Tables to SUBROUTINES

Hi Guys
In the code below my colleague has created her own table types in order to pass a select option and internal tables to her subroutine. Is there an easier way of making them known to the subroutine.
data : v_vbeln type vbeln_vf,
      it_bdoc type table of vbrp,
      it_t006 type table of t006a,
      wa_bdoc type vbrp,
      wa_t006 type t006a,
      it_bdoc2 type table of zsswathi_st_vbeln,
      wa_bdoc2 type zsswathi_st_vbeln
select-options s_vbeln for v_vbeln matchcode object zswathi_vbeln obligatory.
start-of-selection.
perform bdoc using s_vbeln[]
             changing it_bdoc
                      it_bdoc2
                      it_t006.
loop at it_bdoc2 into wa_bdoc2.
form bdoc using f_s_vbeln type ZSWATHI_ST_SELECT_OPTION_TA_TY       " all these are table types. for select options, a structure is created and then a table type for it is created.
        changing f_it_bdoc type zswathi_vbrp_ty_ta
                 f_it_bdoc2 type zswathi_vbeln_ty_ta
                  f_it_t006 type ZSWATHI_T006_TA_TY.
select * from vbrp into table f_it_bdoc where vbeln in f_s_vbeln.
      if f_it_bdoc is not initial.
      select vbeln sum( netwr ) prsdt from vbrp into table f_it_bdoc2 where vbeln in f_s_vbeln group by vbeln prsdt.
      sort f_it_bdoc2 by vbeln.
      "select * from t006a into table it_t006 for all entries in it_bdoc where msehi = it_bdoc-vrkme.
      select * from t006a into table f_it_t006 for all entries in f_it_bdoc where msehi = f_it_bdoc-vrkme.
   endif.
    endform.

Hi Brett,
1. you can use a select-options-range in a FORM subroutine also without passing it as a parameter because parameters and select-option range tables are global fields in their program.
2. If you need a parameter, declare it as type table or type standard table or type any table. You do not need any special table type.
Regards
Clemens

[Updated] How to create copies of internal table?

Dis is the detailed description of a problem i have and i
tried all i can to solve it without satisfied results.
I want to copy an internal table of a type defined in the
ABAP program itself, not dictionary. I have a function
that is supposed to accept the internal table as a
parameter of type 'any table'. The function should create
the new internal table using the field catalog of the
passed 'any table' and then create a new internal table
using "create_dynamic_table" and return the DATA pointer.
If anyone knows how it is done pls help me out.
I would like to get the field catalog of the following
internal table automatically by using some sap function..
TYPES:
BEGIN OF MYTYPE,
NAME TYPE SOMEZTABLE-NAME,
AGE TYPE SOMEZTABLE-AGE,
END OF MYTYPE.
DATA:
IT_TABLE TYPE TABLE OF MYTABLE INITIAL SIZE 0.
DATA:
COPY_OF_IT_TABLE TYPE REF TO DATA.
SELECT NAME AGE INTO TABLE IT_TABLE FROM S0MEZTABLE.
PERFORM CREATECOPY USING IT_TABLE CHANGING COPY_OF_IT_TABLE.
[I have used FORM 4 understanding purpose only. I
actually want to put the code in the form in a seperate
global class method. So, its not possible to define
field symbols in the main pgm and assign value to it
from within the FORM. Also we cant CREATE DATA of the
type 'mytype' within the FORM.]
FORM CREATECOPY
USING
IT_TABLE TYPE ANY TABLE
CHANGING
COPY_OF_IT_TABLE TYPE REF TO DATA.
[ Here i would like to create a copy the passed
internal table and return a reference to it. I donot want
to refer to the same table passed. I guess the use of
function CREATE_DYNAMIC_TABLE in the CL_ALV_TABLE_CREATE
clss is required. ]
ENDFORM.

Ravikumar,
All the example code i have got wil not work when i put the code in a method of a class..
The problem is not as simple as it sounds...
Pls try if u can and u will understand the basic problem..
If u can pls giv me ur email id as i can mail u the detailed description of the problem..

Create dynmic deep internal table

Dear all,
is it possible to create a dynamic internal table which has a deep structure. The catch here is that component tables of the main internal table will determined dynamically.
thanks a lot!!!
Navjot

Hi Navjot,
Dyanmic internal table with deep structure is specially useful when we have to create an ALV with Colors or Style etc. Since we have CL_ABAP_TABLEDESCR class from RTTS, it is also possible to create a dynamic internal table with the deep structure. To create an internal table with deep structure, we need to first get the object definition of the table type. Than we have to add that as a component of our table definition and that's it.
Try this :
*& Report ZNP_DYNAMIC_DEEP_TABLE.
*& Shows how to create dynamic internal table with deep strcuture
*& which can be used in the ALV to have Sytle table, Color table
* 2.1 Creating the Deep strcuture field
DATA: lo_tab TYPE REF TO cl_abap_tabledescr.
lo_tab ?= cl_abap_typedescr=>describe_by_name( 'LVC_T_SCOL' ).
la_comp-name = 'COLOR_TAB'.
la_comp-type = lo_tab.
APPEND la_comp TO lt_tot_comp.
CLEAR: la_comp.
Regards
Abhinab Mishra

How to create dynamic nested internal table

Hi Experts,
Pleae tell me or give sample code, how to create dynamic nested internal table ?
I have seen threads saying creation of dynamic internal tables using some table structure only. But now the requirement is to create dynamic nested internal table.
For example the internal table contains two fields viz., one is field1 of dynamic internal table and other is normal field2 and values as shown below:
Nested internal table:
field1 | field2 ...
<table content1> | value2..
<table content1> | value2..
Here the [table content] should also a dynamic internal table.
Let me know if you need any other info.
regards
Saravanan R

see the complete code..i am currently working in ECC6.0 EHP4. just check which version you are using..
REPORT yst_test_000.
DATA:
 lt_comptab TYPE cl_abap_structdescr=>component_table,
 ls_comp LIKE LINE OF lt_comptab,
 lref_newstr TYPE REF TO cl_abap_structdescr,
 lref_tab_type TYPE REF TO cl_abap_tabledescr,
 lt_fcat TYPE lvc_t_fcat,
 ls_fcat TYPE lvc_s_fcat,
 ls_dd03p TYPE dd03p,
 lt_data type ref to data.
field-symbols: <fs_table> type standard table.
CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
EXPORTING
 i_structure_name = 'SCARR'
CHANGING
 ct_fieldcat = lt_fcat
EXCEPTIONS
 inconsistent_interface = 1
 program_error = 2
 OTHERS = 3.
IF sy-subrc NE 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
 WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
LOOP AT lt_fcat INTO ls_fcat.
IF ls_fcat-ref_table IS NOT INITIAL.
 CLEAR ls_dd03p.
 CALL FUNCTION 'BUS_DDFIELD_GET'
 EXPORTING
 i_tabnm = ls_fcat-ref_table
 i_fldnm = ls_fcat-fieldname
 IMPORTING
 e_dd03p = ls_dd03p
 EXCEPTIONS
 field_not_found = 1
 OTHERS = 2.
 IF sy-subrc EQ 0.
 ls_comp-name = ls_fcat-fieldname.
 ls_comp-type ?= cl_abap_datadescr=>describe_by_name( ls_dd03p-rollname ).
 APPEND ls_comp TO lt_comptab.
 CLEAR ls_comp.
 ENDIF.
ELSE.
 ls_comp-name = ls_fcat-fieldname.
 ls_comp-type ?= cl_abap_datadescr=>describe_by_name( ls_fcat-rollname ).
 APPEND ls_comp TO lt_comptab.
 CLEAR ls_comp.
ENDIF.
ENDLOOP.
*Now for the Field which you want deep table then you can do like this
ls_fcat-fieldname = 'NESTED_TABLE'.
ls_fcat-inttype = 'C'.
ls_fcat-intlen = '000006'.
ls_fcat-rollname = 'SFLIGHT_TAB1'. "For SFLIGHT
APPEND ls_fcat TO lt_fcat.
ls_comp-name = ls_fcat-fieldname.
ls_comp-type ?= cl_abap_datadescr=>describe_by_name( ls_fcat-rollname ).
APPEND ls_comp TO lt_comptab.
CLEAR ls_comp.
lref_newstr = cl_abap_structdescr=>create( lt_comptab ).
lref_tab_type = cl_abap_tabledescr=>create( lref_newstr ).
create data lt_data type handle lref_tab_type.
assign lt_data->* to <fs_table>.
break-point.
Edited by: Vijay Babu Dudla on Apr 28, 2009 8:05 AM

Difference between work area and internal tables.

Hi I wanna know the difference between work area and internal tables.
what happend if i give with out header line in internal table.
also how to assosiate work area to internal table in that scenario.

Hi Balaji..
The internal table is an ABAP runtime object which has two parts the Body and the header.
Whereas a work area cannot have a body.. It is mere a field or group of fields which can hold values at runtime..
In the SAP higher versions mySAP ERP, the use of tables with header line is made obsolete.. But there is absolutely no problem with the same..
Just think that when you define an internal table with occurs or with header line statement, the system automatically creates a workarea with this table, using which you can access the contents in the bosy of tyhe table.. You can read a record from the table body to this header or add a record in the header to the internal table body..
When you work with a table ITAB without a header line, you can not use statements like READ TABLE, APPEND, INSERT etc without giving an explicit work area..
Suppose i have an internal table like:
DATA : itab TYPE STANDARD TABLE OF t001.
This table will not have a header with it.
If you will use APPEND itab. The compilor will give error.
Here i will create a work area with same structure of the table.
DATA : e_wa TYPE t001.
Now i will write:
APPEND e_wa TO itab.
READ TABLE itab INTO e_wa WITH KEY xxxxxx
LOOP AT itab INTO e_wa... etc..
In a better approach we use Field symbols with such tables, instead of structures
FIELD-SYMBOLS: <fs_itab> TYPE t001.
So,
LOOP AT itab ASSIGNING <fs_itab>
READ TABLE itab ASSIGNING <fs_itab> etc.. However we can not use field symbols in few cases..
I hope this will help you..
Thanks and Best Regards,
Vikas Bittera.
**Points for usefull answers**

Export - Import In ABAP ( for variables and internal table)

how can we pass value for the variable and internal table using Export and Import?
data: var type sy-uzeit.
var = sy-uzeit.
EXPORT var TO MEMORY ID 'TIME'.
data: var type sy-uzeit.
IMPORT var FROM MEMORY ID 'TIME'.
write:/ var,sy-subrc,sy-uzeit.
i found var value 0 while importing.
what is the right syntax for passing value of variable and internaltable.
regards,
dushyant.

Hi,
There are two possible solutions.
Solution1:
Program1.Should be run before atleast once so that TIME should be filled.
data: var type sy-uzeit.
var = sy-uzeit.
EXPORT var TO MEMORY ID 'TIME'.
Program2.IF the TIME is filled,then only it will produce the result.
data: var type sy-uzeit.
clear var.
IMPORT var FROM MEMORY ID 'TIME'.
write:/ var, sy-subrc, sy-uzeit.
Solution2:
Single program:
data: var type sy-uzeit.
var = sy-uzeit.
EXPORT var TO MEMORY ID 'TIME'.
clear var.
IMPORT var FROM MEMORY ID 'TIME'.
write:/ var, sy-subrc, sy-uzeit.
Kindly reward points by clikcing the star on the left of reply,if it helps.

Creating Types and Internal table

Similar Messages

Maybe you are looking for