ALV dynamic with deep structure

Hi All,
I need to program an ALV Report with a deep structure based on a outbound proxy structure, so I should pass to ALV function or ALV Method a dynamic table and a dynamic structure.
I tried to do it but I got a dump using this function module REUSE_ALV_GRID_DISPLAY with these parameters: STRUCTURE_NAME and T_OUTTAB.
Please, some suggestions about this.
Thanks in advance.
Alexis.

Hi Vasanth
this is my example:
DATA: tl_proxy TYPE TABLE OF zpidt_operacion.
DATA: sl_proxy TYPE zpidt_operacion.
sl_proxy-dt_operacion-dt_cab_operacion-vkorg = '0001'.
APPEND sl_proxy TO tl_proxy.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
EXPORTING
    i_callback_program = sy-repid
    i_structure_name   = 'ZPIDT_OPERACION'
TABLES
    t_outtab           = tl_proxy
EXCEPTIONS
    program_error      = 1
    OTHERS             = 2.
Please, could you tell me how I have to do it.
Thanks,
Alexis.

Similar Messages

Creating dynamic internal table with deep structure

Hi all,
I need to create an internal table with deep structure dynamically. I've already created tables with method 'create_dynamic_table' but I'm struggling with the deep structure.
I would need an internal table with the following structure:
DATA: BEGIN OF lt_t1,
s1 TYPE REF TO data,
s2 TYPE REF TO data,
END OF lt_t1.
S1 and S2 have to be tables.
It might be possible with RTTS but all the examples in the forums (that I've found so far) are related to at least one DDIC-structure. And that's my problem because both tables are created during runtime.
Thank you in advance
Nicola

Hi Frédéric,
I hope my english is good enough to explain it correctly:
We use a function builder for SEM-BPS which copies data from one Cube to another. This Cube is transactional, so you can't easily read a structure out of DDIC.
The export parameter of this function builder is a table with type 'any table'.
Until today we used a fixed definition e.g.:
TYPES:
    BEGIN OF xtyp_chas,
     /sie/sr_ocomp TYPE /b52/oisr_ocomp,
     /sie/ts_03psp TYPE /b52/oits_03psp,
     0activity     TYPE /bi0/oiactivity,
     0acty_elemt   TYPE /bi0/oiacty_elemt,
     0costelmnt    TYPE /bi0/oicostelmnt,
     0co_area      TYPE /bi0/oico_area,
     0creditor     TYPE /bi0/oicreditor,
     0currency     TYPE /bi0/oicurrency,
     0curtype      TYPE /bi0/oicurtype,
     0db_cr_ind    TYPE /bi0/oidb_cr_ind,
     0fiscper      TYPE /bi0/oifiscper,
     0fiscper3     TYPE /bi0/oifiscper3,
     0fiscyear     TYPE /bi0/oifiscyear,
     0metype       TYPE /bi0/oimetype,
     0network      TYPE /bi0/oinetwork,
     0part_actty   TYPE /bi0/oipart_actty,
     0part_cctr    TYPE /bi0/oipart_cctr,
     0piobjsv      TYPE /bi0/oipiobjsv,
     0project      TYPE /bi0/oiproject,
     0unit         TYPE /bi0/oiunit,
     0vtdetail     TYPE /bi0/oivtdetail,
     0vtstat       TYPE /bi0/oivtstat,
     0vtype        TYPE /bi0/oivtype,
     0bus_area     TYPE /bi0/oibus_area,
     0cashdetail   TYPE /bi0/oicashdetail,
     0cashtype     TYPE /bi0/oicashtype,
     0comp_code    TYPE /bi0/oicomp_code,
     0coorder      TYPE /bi0/oicoorder,
     0cs_dimen     TYPE /bi0/oics_dimen,
     0cs_unit      TYPE /bi0/oics_unit,
     0int_bus      TYPE /bi0/oiint_bus,
     0part_abcpr   TYPE /bi0/oipart_abcpr,
     0part_coord   TYPE /bi0/oipart_coord,
     0part_wbsel   TYPE /bi0/oipart_wbsel,
     0piovalue     TYPE /bi0/oipiovalue,
     0profit_ctr   TYPE /bi0/oiprofit_ctr,
     0ps_obj       TYPE /bi0/oips_obj,
     0statussys0   TYPE /bi0/oistatussys0,
     zfbwheroj     TYPE /bic/oizfbwheroj,
    END   OF xtyp_chas,
    BEGIN OF xtyp_kyfs,
      0amount      TYPE /bi0/oiamount,
      0quantity    TYPE /bi0/oiquantity,
      zf03oaws     TYPE /bic/oizf03oaws,
      zf03oqty     TYPE /bic/oizf03oqty,
      zf03ozsta    TYPE /bic/oizf03ozsta,
    END OF xtyp_kyfs,
    BEGIN OF xtyp_zf03g003,
      s_chas TYPE xtyp_chas,
      s_kyfs TYPE xtyp_kyfs,
    END   OF xtyp_zf03g003,
    xtyp_zf03g003_t TYPE HASHED TABLE OF xtyp_zf03g003
                      WITH UNIQUE KEY s_chas.
DATA: lt_ibm_data TYPE xtyp_zf03g003_t,
      ls_ibm_data TYPE xtyp_zf03g003.
So one table (s_chas) contains the characteristics of the Cube and the other (s_kyfs) contains the keyfigures. That's exactly the format we need for the export parameter. At the end of the program, we use the following coding to fill the export table (eto_chas):
loop at lt_ibm_data into ls_ibm_data.
collect ls_ibm_data-s_chas into eto_chas.
endloop.
So in this moment I give this table the structure that is needed to move the data into the cube. I can't change the requirement because it is a standard interface.
I would like to change that coding to be dynamically. Because if somebody changes a charasteristic or a keyfigure in the cube, we would have to change the function builder too. I don't think that the SEM-BPS department will let us know every time they've changed something anyway.
So I hope that my explanation wasn't too confusing
Nicola

How to use STRANS to translate XML to ABAP with deep structure

every experts, I want to use Tcode: STRANS to translate XML to ABAP, But it does not work well,
here is XML code，I want to translate this XML into an an Inter table gt_orders with deep structure of oeb, and colum oeb is also and intertable,how can I do this.
<?xml version="1.0" encoding="gb2312" ?><axmt410><ObjectID>setSalesOrder</ObjectID><azp01>000000</azp01><oea00>1</oea00><ta_oeaecn>SO-140227-3041</ta_oeaecn><oea03>25325017</oea03><oea02>2014-02-27 17:44:44.0</oea02><ta_oea002>2763.0</ta_oea002><ta_oea001>0.0</ta_oea001><oea14></oea14><oea15>25325017</oea15><oea23>RMB</oea23><oeaconf>S3</oeaconf><oea10></oea10><oeaud01>null</oeaud01><ta_oea007></ta_oea007><oea25>101</oea25><ta_oea008>0</ta_oea008><ta_oea009>null</ta_oea009><oeauser>Hanjingya</oeauser><ta_oeanday>2014-02-27 17:44:44.991</ta_oeanday><ta_oeamday>2014-02-28 08:30:14.866</ta_oeamday><ta_oeacday>2014-02-28 08:30:14.866</ta_oeacday><oeaud02>0</oeaud02><ta_oea030>null</ta_oea030><oeb><oeb03>1</oeb03><oeb04>7400208249</oeb04><oeb05>PCS</oeb05><oeb17>921.0</oeb17><oeb13>921.0</oeb13><oeb15></oeb15><oeb12>5</oeb12><oeb09>990001</oeb09><ta_oeb001></ta_oeb001><ta_oeb002>Yunnan</ta_oeb002><ta_oeb003>address1</ta_oeb003><ta_oeb004>zhangdagui、zhanglan</ta_oeb004><ta_oeb005>15974749998、15987782008</ta_oeb005><ta_oeb006>address and street</ta_oeb006><oebud01></oebud01></oeb><oeb><oeb03>2</oeb03><oeb04>7400208250</oeb04><oeb05>PCS</oeb05><oeb17>921.0</oeb17><oeb13>921.0</oeb13><oeb15></oeb15><oeb12>5</oeb12><oeb09>990001</oeb09><ta_oeb001></ta_oeb001><ta_oeb002>Yunnan</ta_oeb002><ta_oeb003>address2</ta_oeb003><ta_oeb004>zhangdagui、chenlan</ta_oeb004><ta_oeb005>15974749998、15987782008</ta_oeb005><ta_oeb006>address and street</ta_oeb006><oebud01></oebud01></oeb></axmt410>
I write these codes in SAP XSLT editor
<xsl:transform xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
   <xsl:output encoding="iso-8859-1" indent="yes" method="xml" version="1.0"/>
   <xsl:strip-space elements="*"/>
   <xsl:strip-space elements="*"/>
   <xsl:template match="/">
     <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
       <asx:values>
         <ORDERS>
           <xsl:apply-templates select="//axmt410"/>
         </ORDERS>
       </asx:values>
     </asx:abap>
   </xsl:template>
   <xsl:template match="axmt410">
     <OBJECTID>
       <xsl:value-of select="ObjectID"/>
     </OBJECTID>
     <AZP01>
       <xsl:value-of select="azp01"/>
     </AZP01>
     <OEA00>
       <xsl:value-of select="oea00"/>
     </OEA00>
     <TA_OEAECN>
       <xsl:value-of select="ta_oeaecn"/>
     </TA_OEAECN>
     <OEA03>
       <xsl:value-of select="oea03"/>
     </OEA03>
     <OEA05>
       <xsl:value-of select="oea05"/>
     </OEA05>
     <OEA02>
       <xsl:value-of select="oea02"/>
     </OEA02>
     <TA_OEA002>
       <xsl:value-of select="ta_oea002"/>
     </TA_OEA002>
     <TA_OEA001>
       <xsl:value-of select="ta_oea001"/>
     </TA_OEA001>
     <OEA14>
       <xsl:value-of select="ora14"/>
     </OEA14>
     <OEA15>
       <xsl:value-of select="ora15"/>
     </OEA15>
     <OEA23>
       <xsl:value-of select="ora23"/>
     </OEA23>
     <OEACONF>
       <xsl:value-of select="oeaconf"/>
     </OEACONF>
     <OEA10>
       <xsl:value-of select="ora10"/>
     </OEA10>
     <OEAUD01>
       <xsl:value-of select="oeaud01"/>
     </OEAUD01>
     <TA_OEA007>
       <xsl:value-of select="ta_oea007"/>
     </TA_OEA007>
     <OEA25>
       <xsl:value-of select="ora25"/>
     </OEA25>
     <TA_OEA008>
       <xsl:value-of select="ta_oea008"/>
     </TA_OEA008>
     <TA_OEA009>
       <xsl:value-of select="ta_oea009"/>
     </TA_OEA009>
     <TA_OEA013>
       <xsl:value-of select="ta_oea013"/>
     </TA_OEA013>
     <TA_OEA014>
       <xsl:value-of select="ta_oea014"/>
     </TA_OEA014>
     <TA_OEA015>
       <xsl:value-of select="ta_oea015"/>
     </TA_OEA015>
     <TA_OEA016>
       <xsl:value-of select="ta_oea016"/>
     </TA_OEA016>
     <TA_OEA017>
       <xsl:value-of select="ta_oea017"/>
     </TA_OEA017>
     <TA_OEA018>
       <xsl:value-of select="ta_oea018"/>
     </TA_OEA018>
     <TA_OEA019>
       <xsl:value-of select="ta_oea019"/>
     </TA_OEA019>
     <TA_OEA020>
       <xsl:value-of select="ta_oea020"/>
     </TA_OEA020>
     <TA_OEA021>
       <xsl:value-of select="ta_oea021"/>
     </TA_OEA021>
     <TA_OEA022>
       <xsl:value-of select="ta_oea022"/>
     </TA_OEA022>
     <TA_OEA028>
       <xsl:value-of select="ta_oea028"/>
     </TA_OEA028>
     <OEAUSER>
       <xsl:value-of select="oeauser"/>
     </OEAUSER>
     <TA_OEANDAY>
       <xsl:value-of select="ta_oeanday"/>
     </TA_OEANDAY>
     <TA_OEAMDAY>
       <xsl:value-of select="ta_oeamday"/>
     </TA_OEAMDAY>
     <TA_OEACDAY>
       <xsl:value-of select="ta_oeacday"/>
     </TA_OEACDAY>
     <OEAUD02>
       <xsl:value-of select="oeaud02"/>
     </OEAUD02>
     <TA_OEA030>
       <xsl:value-of select="ta_oea030"/>
     </TA_OEA030>
     <OEB>
       <xsl:for-each select="oeb">
         <OEB03>
           <xsl:value-of select="oeb03"/>
         </OEB03>
         <OEB04>
           <xsl:value-of select="oeb04"/>
         </OEB04>
         <OEB05>
           <xsl:value-of select="oeb05"/>
         </OEB05>
         <OEB17>
           <xsl:value-of select="oeb17"/>
         </OEB17>
         <OEB13>
           <xsl:value-of select="oeb13"/>
         </OEB13>
         <OEB15>
           <xsl:value-of select="oeb15"/>
         </OEB15>
         <OEB12>
           <xsl:value-of select="oeb12"/>
         </OEB12>
         <OEB09>
           <xsl:value-of select="oeb09"/>
         </OEB09>
         <TA_OEB001>
           <xsl:value-of select="ta_oeb001"/>
         </TA_OEB001>
         <TA_OEB002>
           <xsl:value-of select="ta_oeb002"/>
         </TA_OEB002>
         <TA_OEB003>
           <xsl:value-of select="ta_oeb003"/>
         </TA_OEB003>
         <TA_OEB004>
           <xsl:value-of select="ta_oeb004"/>
         </TA_OEB004>
         <TA_OEB005>
           <xsl:value-of select="ta_oeb005"/>
         </TA_OEB005>
         <TA_OEB006>
           <xsl:value-of select="ta_oeb006"/>
         </TA_OEB006>
         <OEBUD01>
           <xsl:value-of select="oebud01"/>
         </OEBUD01>
       </xsl:for-each>
     </OEB>
   </xsl:template>
</xsl:transform>
and I use below ABAP program for a test, but the items from XML can not translate into Interner table gt_orders-oeb[]
TYPE-POOLS abap.
CONSTANTS gs_file TYPE string VALUE 'C:\temp\order02.xml'.
* This is the structure for the data from the XML file
TYPES:
   BEGIN OF typ_s_oeb,
     oeb03     TYPE string,    "
     oeb04     TYPE string,    "
     oeb05     TYPE string,    "
     oeb17     TYPE string,    "
     oeb13     TYPE string,
     oeb15     TYPE string,
     oeb12     TYPE string,    "
     oeb09     TYPE string,    "
     ta_oeb001 TYPE string,    "
     ta_oeb002 TYPE string,    "
     ta_oeb003 TYPE string,    "
     ta_oeb004 TYPE string,    "
     ta_oeb005 TYPE string,    "
     ta_oeb006 TYPE string,    "
     ta_oeb013 TYPE string,    "
     ta_oeb014 TYPE string,    "
     ta_oeb015 TYPE string,    "
     ta_oeb016 TYPE string,    "
     ta_oeb017 TYPE string,    "
     ta_oeb018 TYPE string,    "
     ta_oeb019 TYPE string,    "
     ta_oeb020 TYPE string,    "
     ta_oeb021 TYPE string,    "
     ta_oeb022 TYPE string,    "
     oebud01   TYPE string,    "
   END OF typ_s_oeb.
TYPES: typ_t_oeb TYPE TABLE OF typ_s_oeb WITH KEY oeb03.
TYPES:
   BEGIN OF typ_s_order,
     objectid   TYPE string,   "
     azp01      TYPE string,   "
     oea00      TYPE string,   "
     ta_oeaecn TYPE string,   "
     oea03      TYPE string,   "
     oea02      TYPE string,   "
     ta_oea002 TYPE string,   "
     ta_oea001 TYPE string,   "
     oea14      TYPE string,   "
     oea15      TYPE string,
     oea23      TYPE string,   "
     oeaconf    TYPE string,   "
     oea10      TYPE string,   "
     oeaud01    TYPE string,   "
     ta_oea007 TYPE string,   "
     oea25      TYPE string,   "
     ta_oea008 TYPE string,   "
     ta_oea009 TYPE string,   "
     oeauser    TYPE string,   "
     ta_oeanday TYPE string,   "
     ta_oeamday TYPE string,   "
     ta_oeacday TYPE string,   "
     oeaud02    TYPE string,   "
     ta_oea030 TYPE string,   "
     ta_oea013 TYPE string,
     ta_oea014 TYPE string,
     ta_oea015 TYPE string,
     ta_oea016 TYPE string,
     ta_oea017 TYPE string,
     ta_oea018 TYPE string,
     ta_oea019 TYPE string,
     ta_oea020 TYPE string,
     ta_oea021 TYPE string,
     ta_oea022 TYPE string,
     ta_oea025 TYPE string,
     oeb        TYPE typ_t_oeb,
    END OF typ_s_order.
* Table for the XML content
DATA: gt_itab       TYPE STANDARD TABLE OF char2048,
       gs_itab       LIKE LINE OF gt_itab.
* Table and work ares for the data from the XML file
DATA: gt_orders     TYPE STANDARD TABLE OF typ_s_order,
       gs_orders     TYPE typ_s_order.
* Result table that contains references
* of the internal tables to be filled
DATA: gt_result_xml TYPE abap_trans_resbind_tab,
       gs_result_xml TYPE abap_trans_resbind.
* For error handling
DATA: gs_rif_ex     TYPE REF TO cx_root,
       gs_var_text   TYPE string.
* Get the XML file from your client
CALL METHOD cl_gui_frontend_services=>gui_upload
   EXPORTING
     filename                = gs_file
   CHANGING
     data_tab                = gt_itab
   EXCEPTIONS
     file_open_error         = 1
     file_read_error         = 2
     no_batch                = 3
     gui_refuse_filetransfer = 4
     invalid_type            = 5
     no_authority            = 6
     unknown_error           = 7
     bad_data_format         = 8
     header_not_allowed      = 9
     separator_not_allowed   = 10
     header_too_long         = 11
     unknown_dp_error        = 12
     access_denied           = 13
     dp_out_of_memory        = 14
     disk_full               = 15
     dp_timeout              = 16
     not_supported_by_gui    = 17
     error_no_gui            = 18
     OTHERS                  = 19.
IF sy-subrc <> 0.
   MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
           WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
* Fill the result table with a reference to the data table.
* Within the XSLT stylesheet, the data table can be accessed with
* "IPERSON".
GET REFERENCE OF gt_orders INTO gs_result_xml-value.
gs_result_xml-name = 'ORDERS'.
APPEND gs_result_xml TO gt_result_xml.
* Perform the XSLT styleshee
TRY.
     CALL TRANSFORMATION zfx_so_xml_to_abap
     SOURCE XML gt_itab
     RESULT (gt_result_xml).
   CATCH cx_root INTO gs_rif_ex.
     gs_var_text = gs_rif_ex->get_text( ).
     MESSAGE gs_var_text TYPE 'S'.
ENDTRY.
LOOP AT gt_orders INTO gs_orders.
ENDLOOP.

The simplest way seems to me is to use a XSL file for that. The <xsl:output> attributes doctype-system and doctype-public generate the DTD declaration <!DOCTYPE YOUR_ROOT SYSTEM "yourDTDfile.dtd"> and <!DOCTYPE YOUR_ROOT PUBLIC "yourDTDfile.dtd">, respectively.
When calling transformerInstance.transform() the XSLT processor performs the identity transformation - it just copies elements, attributes, content, processing instructions and comments to the result stream.
If you're using an xsl file for your transformation already, simply add <xsl:output doctype-system="yourDTDfile.dtd"/> to your existing XSL file.
If you're only using the identity transformation you'd need to change the line of code where you obtain the transformer instance from the TransformerFactory to:
t_factory.newTransformer(new StreamSource("test.xsl"));
and use this as test.xsl:
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
   <xsl:output doctype-system="yourDTDfile.dtd"/>
   
   <xsl:template match="*|@*|comment()|processing-instruction()|text()">
      <xsl:copy>
         <xsl:apply-templates select="*|@*|comment()|processing-instruction()|text()"/>
      </xsl:copy>
   </xsl:template>
</xsl:stylesheet>Good luck.

Dynamic Table - Deep Structure

Hi Gurus,
this is my first posting, so be patient!
I want to create a deep structure dynamic table via method
cl_alv_table_create=>create_dynamic_table, is this possible? Are there tricks to make it happen?
Background: i wanna create an alv with dynamic fieldcatalalog, in this case i want to colour special fields, which is done by lvc_s_layo-?csp_fieldname? in combination with a field in my internal table which is typed ?lvc_t_scol?. Is this possible under 6.2.43
thanxs for your replies
juergen
- ?i dont actually know by rote the correct fieldnames of lvc_xxxxx?

Hi Jurgen, I took on the challenge. This program provides a dynamic table with the ability to set the colors of the cells.
Create the structure ZCDF_CELL_COLOR in the dictionary as described in the program.
Create screen 100 as empty, with next screen set to 0, and the following flow logic:
PROCESS BEFORE OUTPUT.
MODULE initialization.
PROCESS AFTER INPUT.
REPORT zcdf_dynamic_table.
* Dynamic ALV Grid with Cell Coloring
DATA:
r_dyn_table      TYPE REF TO data,
r_wa_dyn_table   TYPE REF TO data,
r_dock_ctnr      TYPE REF TO cl_gui_docking_container,
r_alv_grid       TYPE REF TO cl_gui_alv_grid,
t_fieldcat1      TYPE lvc_t_fcat, "with cell color
t_fieldcat2      TYPE lvc_t_fcat, "without cell color
wa_fieldcat      LIKE LINE OF t_fieldcat1,
wa_cellcolors    TYPE LINE OF lvc_t_scol,
wa_is_layout     TYPE lvc_s_layo.
FIELD-SYMBOLS:
<t_dyn_table>    TYPE STANDARD TABLE,
<wa_dyn_table>   TYPE ANY,
<t_cellcolors>   TYPE lvc_t_scol,
<w_field>        TYPE ANY.
START-OF-SELECTION.
* Build field catalog based on your criteria.
wa_fieldcat-fieldname = 'FIELD1'.
wa_fieldcat-inttype   = 'C'.
wa_fieldcat-outputlen = '10'.
wa_fieldcat-coltext   = 'My Field 1'.
wa_fieldcat-seltext   = wa_fieldcat-coltext.
APPEND wa_fieldcat TO t_fieldcat1.
wa_fieldcat-fieldname = 'FIELD2'.
wa_fieldcat-inttype   = 'C'.
wa_fieldcat-outputlen = '10'.
wa_fieldcat-coltext   = 'My Field 2'.
wa_fieldcat-seltext   = wa_fieldcat-coltext.
APPEND wa_fieldcat TO t_fieldcat1.
* Before adding cell color table,
* save fieldcatalog to pass
* to ALV call.
t_fieldcat2[] = t_fieldcat1[].
* Add cell color table.
* ZCDF_CELL_COLOR is a structure in the
*   dictionary with one
*   field called T_CELL_COLOR of type LVC_T_SCOL.
wa_fieldcat-fieldname = 'T_CELLCOLORS'.
wa_fieldcat-ref_field = 'T_CELL_COLOR'.
wa_fieldcat-ref_table = 'ZCDF_CELL_COLOR'.
APPEND wa_fieldcat TO t_fieldcat1.
* Create dynamic table.
CALL METHOD cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog           = t_fieldcat1
    IMPORTING
      ep_table                  = r_dyn_table
    EXCEPTIONS
      generate_subpool_dir_full = 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.
* Get access to new table using field symbol.
ASSIGN r_dyn_table->* TO <t_dyn_table>.
* Create work area for new table.
CREATE DATA r_wa_dyn_table LIKE LINE OF <t_dyn_table>.
* Get access to new work area using field symbol.
ASSIGN r_wa_dyn_table->* TO <wa_dyn_table>.
* Get data into table from somewhere. Field names are
* known at this point because field catalog is already
* built. Read field names from the field catalog or use
* COMPONENT <number> in a DO loop to access the fields.
* A simpler hard coded approach is used here.
ASSIGN COMPONENT 'FIELD1' OF STRUCTURE <wa_dyn_table>
    TO <w_field>.
<w_field> = 'ABC'.
ASSIGN COMPONENT 'FIELD2' OF STRUCTURE <wa_dyn_table>
    TO <w_field>.
<w_field> = 'XYZ'.
APPEND <wa_dyn_table> TO <t_dyn_table>.
ASSIGN COMPONENT 'FIELD1' OF STRUCTURE <wa_dyn_table>
    TO <w_field>.
<w_field> = 'TUV'.
ASSIGN COMPONENT 'FIELD2' OF STRUCTURE <wa_dyn_table>
    TO <w_field>.
<w_field> = 'DEF'.
APPEND <wa_dyn_table> TO <t_dyn_table>.
* Color cells based on your criteria.
* In this example, a test on
* FIELD2 is used to decide on color.
LOOP AT <t_dyn_table> INTO <wa_dyn_table>.
    ASSIGN COMPONENT 'FIELD2' OF STRUCTURE <wa_dyn_table>
      TO <w_field>.
    ASSIGN COMPONENT 'T_CELLCOLORS'
      OF STRUCTURE <wa_dyn_table> TO <t_cellcolors>.
    CLEAR wa_cellcolors.
    wa_cellcolors-fname     = 'FIELD2'.
    IF <w_field> = 'DEF'.
      wa_cellcolors-color-col = '7'.
    ELSE.
      wa_cellcolors-color-col = '5'.
    ENDIF.
    APPEND wa_cellcolors TO <t_cellcolors>.
    MODIFY <t_dyn_table> FROM <wa_dyn_table>.
ENDLOOP.
CALL SCREEN 100.
* MODULE initialization OUTPUT
MODULE initialization OUTPUT.
* Set up for ALV display.
IF r_dock_ctnr IS INITIAL.
    CREATE OBJECT r_dock_ctnr
           EXPORTING
              side =
                cl_gui_docking_container=>dock_at_left
              ratio = '90'.
    CREATE OBJECT r_alv_grid
           EXPORTING i_parent = r_dock_ctnr.
*   Set ALV controls.
    wa_is_layout-ctab_fname = 'T_CELLCOLORS'.
*   Display.
    CALL METHOD r_alv_grid->set_table_for_first_display
      EXPORTING
        is_layout       = wa_is_layout
      CHANGING
        it_outtab       = <t_dyn_table>
        it_fieldcatalog = t_fieldcat2.
ELSE.     "grids already prepared
*   Refresh display.
    CALL METHOD r_alv_grid->refresh_table_display
      EXPORTING
        i_soft_refresh = ' '
      EXCEPTIONS
        finished       = 1
        OTHERS         = 2.
ENDIF.
ENDMODULE.                 " initialization OUTPUT

BLFA1 with deep structures in release 6/RFBIKR00

We are trying to upload VENDOR data in release 6 using RFBIKR00 program but when analizing the BLFA1 structure we found that is changed
there is a deep structure WRF_LFA1_BI_STY (for example)
that we do not know how to represent in the TXT file
We are not using this structure, but we asume that we have to send it as part of BLFA1 record.
Can somebody send me an example of how to write data for this BLFA1 record with this structure.
In advance Thanks.

Hi Kiril,
I see what approach you are thinking about and your explanation is not idiotic at all
What I understand is that you have 6 Tables with loads of foreign keys and you want to avoid heaps of "loop at" or "select" coding-nestings. What I don't understand is, why would you want to reproduce the logic of your tables, which you already have, upon your context? I'm not seeing through what your application works like for an end user yet, maybe that's why I'm confused.
In my opinion you won't have many options to avoid some coding which contains a bit of complex Loop-At or Join-Clauses. But if you build a class and outsource the code in some public static methods, this won't be as much work as you think, assuming you make the methods a bit dynamic and reusable.
Cheers, Lukas

Binding ALV GRID with Deep Internal Table

Hello all,
I am looking for a way to display ALV Grid with the Deep ITAB.
My ITAB is not too complex.
It has One Structure which gets whole DB table + One extra field.
Therefore my Itab looks as follows.
TYPES: BEGIN OF TY_TRIP,
        ZPM_UPLOAD LIKE ZDBTABLE, "ZDBTABLE is custom database table.
        TDTIME TYPE STRING,
       END OF TY_TRIP.
DATA: ITAB TYPE TABLE OF TY_TRIP,
      WA_ITAB LIKE LINE OF ITAB.
Now i am able to populate data into Deep ITAB.
If i call ALV Grid with ITAB then i get error. So how to call 'REUSE_ALV_GRID_DISPLAY' with this ITAB?
Thanks in advance.

Hello,
My senior asked me to use the below definition.
TYPES: BEGIN OF TY_TRIP.
        INCLUDE STRUCTURE ZDBTABLE.
TYPES: TDTIME TYPE STRING,
       END OF TY_TRIP.
DATA: ITAB TYPE TABLE OF TY_TRIP,
      WA_ITAB LIKE LINE OF ITAB.
If anyone else is looking to print in ALV, they can use this type of ITAB definition though it gives you the flexiblity to create ITAB and also making it FLAT and not DEEP.
But i am still looking for an answer for my first post.
Thanks.

Problem with deep structure in Adobe Forms

Hi ,
I am converting smartform into adobe forms. While converting the program code in the code initialization of the smart forms also get transformed to adobe forms the problem is my internal table is of type deep structure while passing it through the tables parameter i am getting error in adobe forms .But while passing the internal table through import parameter its not giving error.The same code works fine with smartforms. I dont know why its not taking the structure of internal table in adobe forms properly .It happens only for deep strucure formal normal tables it works fine in table parameters .If any one has come across this scenario please share your ideas.
Best Regards,
Sreeram

If I were you, I would never do this through any program. The only secure, reliable way is to rewrite everything by your own hands. Even if we could argue, your way works as well (and could be faster at the beginning), at the firt moment you will be asked to perform any tiny change in this "imported" thing, you will cry your eyes out (and understand why it is the only useful way to rewrite everything manually).
regards Otto

How to read xml with deep structure into intarnal table.

Hi,
Could you pls any body provide xslt code for deep structure convert into internal table.
sample xml file:
- <ns0:CREATIONOFCONTRACT xmlns:ns0="http://BPCreationXSD.CreationOfContract">
- <CREATIONOFCONTRACTDATA>
<RequestType>L0011</RequestType>
<ApplicationId>AN-12</ApplicationId>
<LoanId>QO-22</LoanId>
- <Borrowerguarantorinfo>
<Borrowerbpno>101020</Borrowerbpno>
<Co-borrower1BPNo>101021</Co-borrower1BPNo>
<Co-borrower2BPNo>101022</Co-borrower2BPNo>
<Guarantor1BPNo>101023</Guarantor1BPNo>
<Guarantor2BPNo>101024</Guarantor2BPNo>
<Branch>New Delhi</Branch>
</Borrowerguarantorinfo>
- <Loaninfo>
<Applicationtype>Fresh</Applicationtype>
<Purposeofloan>Home Purchase</Purposeofloan>
<Securedunsecuredflag>Secured</Securedunsecuredflag>
<Loantype>HL with MRTA</Loantype>
<Loancurrency>INR</Loancurrency>
<Loanproduct>MaxiHome Loan Package</Loanproduct>
<Loanscheme>MaxiHome ZEC</Loanscheme>
<Loanamount>1500000.00</Loanamount>
<Loantenure>60</Loantenure>
<Tiered>No</Tiered>
</Loaninfo>
<Periodfrom>01/07/2009</Periodfrom>
<Periodto>16/09/2019</Periodto>
<RateType>Fixed</RateType>
<Ratecode>10.25</Ratecode>
</CREATIONOFCONTRACTDATA>
</ns0:CREATIONOFCONTRACT>

Hi Ramesh,
Thanks for the info,but I found lot of tables unfortunately I am not getting the value for radio buttons. Also I found a FM FIELD_SELECTION_CUSTOMIZE , IMPORT_DYNPRO etc which will call that screen based on profile but it will not store data any where. I found several tables like TCATS, TFAWC, TFAWF, TFAWT etc.But I am not getting the value for raduio buttons.
Thanks & Regards,
Nagaraj Kalbavi

Selecting into an internal table with deep structure

Hi,
I am working in ECC 6.0 now and it is giving me a syntax error for the following code.
types: tt_bdc type standard table of bdcmsgcoll
      with default key.
data: begin of t_test occurs 0,
        vbeln like vbak-vbeln,
        tab   type tt_bdc,
      end of t_test.
select vbeln from vbak into table t_test
where aedat > '20081101'.
The error is:
+The work area (or internal table) "T_TEST" is not flat, or contains
reference or internal tables as components . components. components.
components. components.+
I've done this in countless other programs in the past. How can I use a deep structure this way? What am I missing?
Thanks very much!

Will this solve ur requirement -
types: tt_bdc type standard table of bdcmsgcoll
      with default key.
data: begin of t_test occurs 0,
        vbeln like vbak-vbeln,
        tab   type tt_bdc,
      end of t_test.
select vbeln from vbak into
CORRESPONDING FIELDS OF TABLE t_test
where aedat > '20081101'.

Problem with deep structure in OO Context

Dear All
As we know deep structures with occurs 0 cannot be declared in Object Oriented context (will give a syntax error). Can some1 please suggest a workaround. I need to declare the following structure in a BADI implementation. But it is a deep structure & gives a syntax error.
BEGIN OF WI
OCCURS 0,
MINDX LIKE SY-INDEX, "Index Merkmal
WINDX LIKE SY-INDEX, "Index in Datentabelle
WSELE TYPE C, "Kz. selektiert
WOHNE TYPE C, "Kz. ohne Wertedefinition
WWERT TYPE C, "Kz. weitere Werte vorhanden
ATSON TYPE C, "Kz. Sonderwerte erlaubt
ESWRT TYPE C, "Kz. Eingeschränkter Wertebereich
SSTRG TYPE C, "Kz. Stringsuche
STATU TYPE C, "Status
ATWRT LIKE CAWN-ATWRT, "Wert sprachneutral
ATFLV LIKE CAWN-ATFLV, "intern von
ATFLB LIKE CAWN-ATFLB, "intern bis
ATAWE LIKE CAWN-ATAWE, "abw. Einheit
ATAW1 LIKE CAWN-ATAW1, "abw. Einheit bis
ATCOD LIKE CAWN-ATCOD, "Operator-Ident.
ATTLV LIKE CAWN-ATTLV, "Toleranz von
X TYPE C,
ATTLB LIKE CAWN-ATTLB, "Toleranz bis
ATPRZ LIKE CAWN-ATPRZ, "Angabe in %
ATINC LIKE CAWN-ATINC, "Schrittweite
ATAUT LIKE AUSP-ATAUT, "Author
WSDEF LIKE CAWN-ATSTD, "Kz. Std.-Wert
ATZHL LIKE AUSP-ATZHL, "Zähler AUSP
TXTNR LIKE CAWN-TXTNR, "Text-Nr.
WTZHL LIKE CAWN-ATZHL, "Zähler CAWN
AENNR LIKE CAWN-AENNR, "Änderungsnr.
DATUV LIKE CAWN-DATUV, "Datum von aus Änderungsnr.
ATZHH LIKE CAWN-ATZHH, "Hierarchie: ATZHL des Parent
ATWHI LIKE CAWN-ATWHI, "Hierarchie: ATZHL ist Parent
ATVPL LIKE CAWN-ATVPL, "Kz. Vorplanung
NATWRT LIKE CAWN-ATWRT, "Sprachneutraler Wert
CATWRT LIKE CAWN-ATWRT, "CHAR-Wert in DDB
CATFLV LIKE CAWN-ATFLV, "NONCHAR-Wert in DDB
KNOBJ LIKE CAWN-KNOBJ, "Beziehungswissen
KNPRE TYPE C, "KNART: Precondition
KNACT TYPE C, "KNART: Action
KNPRO TYPE C, "KNART: Procedure
VL TYPE VALUE_DESCRIPTION OCCURS 5,
    est_atwrt like ausp-atwrt,      "Eingabestring    (für EH&S) 4.0c
END   OF WI.
Help needed urgently!!
Regards
Sudhir

Declare TYPES statement.
types: BEGIN OF WI,
MINDX LIKE SY-INDEX, "Index Merkmal
WINDX LIKE SY-INDEX, "Index in Datentabelle
WSELE TYPE C, "Kz. selektiert
WOHNE TYPE C, "Kz. ohne Wertedefinition
WWERT TYPE C, "Kz. weitere Werte vorhanden
ATSON TYPE C, "Kz. Sonderwerte erlaubt
ESWRT TYPE C, "Kz. Eingeschränkter Wertebereich
SSTRG TYPE C, "Kz. Stringsuche
STATU TYPE C, "Status
ATWRT LIKE CAWN-ATWRT, "Wert sprachneutral
ATFLV LIKE CAWN-ATFLV, "intern von
ATFLB LIKE CAWN-ATFLB, "intern bis
ATAWE LIKE CAWN-ATAWE, "abw. Einheit
ATAW1 LIKE CAWN-ATAW1, "abw. Einheit bis
ATCOD LIKE CAWN-ATCOD, "Operator-Ident.
ATTLV LIKE CAWN-ATTLV, "Toleranz von
X TYPE C,
ATTLB LIKE CAWN-ATTLB, "Toleranz bis
ATPRZ LIKE CAWN-ATPRZ, "Angabe in %
ATINC LIKE CAWN-ATINC, "Schrittweite
ATAUT LIKE AUSP-ATAUT, "Author
WSDEF LIKE CAWN-ATSTD, "Kz. Std.-Wert
ATZHL LIKE AUSP-ATZHL, "Zähler AUSP
TXTNR LIKE CAWN-TXTNR, "Text-Nr.
WTZHL LIKE CAWN-ATZHL, "Zähler CAWN
AENNR LIKE CAWN-AENNR, "Änderungsnr.
DATUV LIKE CAWN-DATUV, "Datum von aus Änderungsnr.
ATZHH LIKE CAWN-ATZHH, "Hierarchie: ATZHL des Parent
ATWHI LIKE CAWN-ATWHI, "Hierarchie: ATZHL ist Parent
ATVPL LIKE CAWN-ATVPL, "Kz. Vorplanung
NATWRT LIKE CAWN-ATWRT, "Sprachneutraler Wert
CATWRT LIKE CAWN-ATWRT, "CHAR-Wert in DDB
CATFLV LIKE CAWN-ATFLV, "NONCHAR-Wert in DDB
KNOBJ LIKE CAWN-KNOBJ, "Beziehungswissen
KNPRE TYPE C, "KNART: Precondition
KNACT TYPE C, "KNART: Action
KNPRO TYPE C, "KNART: Procedure
VL TYPE table of VALUE_DESCRIPTION,est_atwrt like ausp-atwrt, "Eingabestring (für EH&S) 4.0c
END OF WI.
types: t_wi type standard table of wi.
data: wa type wi,
        t_itab type t_wi.

How to work with deep structure

Hi !
I wanted to ask how to loop, modify, append tables located in deep structures. Deep structures i mean, structures consist of columns which are tables ( usualy exists in user-exit). Please give examples and reference help to this subject.
Thanks
Moshe

Hi
TYPES: T_TYBSEG TYPE STANDARD TABLE OF BSEG.
DATA: BEGIN OF T_DOCUMENTS,
        HEADER LIKE BKPF,
        ITEMS TYPE T_TYBSEG,
      END   OF T_DOCUMENTS.
DATA: T_BSEG TYPE T_TYBSEG,
      T_BKPF TYPE STANDARD TABLE OF BKPF WITH HEADER LINE.
Append data:
SELECT * FROM BKPF INTO TABLE T_BKPF WHERE ....
LOOP AT T_BKPF.
MOVE-CORRESPONDING T_BKPF TO T_DOCUMENTS-HEADER.
   SELECT * FROM BSEG INTO TABLE T_BSEG where ....
Here it uses the table t_bseg to append the items to T_DCOUMENTS-ITEMS: it's very import to clear this table before appending records.
If you don't clear the internal table you'll append several times the same records.
   REFRESH T_DOCUMENTS-ITEMS.
   APPEND LINES OF T_BSEG TO T_DOCUMENTS-ITEMS.
   APPEND T_DOCUMENTS.
ENDLOOP.
Read DATA:
LOOP AT T_DOCUMENTS.
    LOOP AT T_DOCUMENTS-ITEMS INTO BSEG.
    ENDLOOP.
ENDLOOP.
OR
READ TABLE T_DOCUMENTS (WITH KEY ...) (INDEX <INDEX>).
IF SY-SUBRC = 0.
     LOOP AT T_DOCUMENTS-ITEMS INTO BSEG.
     ENDLOOP.
ENDIF.
Modify
LOOP AT T_DOCUMENTS.
    LOOP AT T_DOCUMENTS-ITEMS INTO BSEG.
      IF BSEG-GJAHR = '2005'.
        BSEG-GJAHR = '2006'.
      ENDIF.
      MODIFY T_DOCUMETS-ITEMS FROM BSEG.
    ENDLOOP.
ENDLOOP.
So if you use this type of structure the table haven't an headerline, so you always use a workarea to read an update the data.
Max
Message was edited by: max bianchi

Create dynamic internal table with deep structure;cell coloring dynamic ALV

Hi,
My requirement is to do cell colouring for a dynamic ALV.
So I am creating a dynamic internal table using the following method.
CALL METHOD cl_alv_table_create=>create_dynamic_table
    EXPORTING
      it_fieldcatalog = i_fieldcatalog[]
    IMPORTING
      ep_table        = i_output.
But how do I define field COLORS which should be again an internal table ?
Is there any other way for cell colouring?
Putting my problem in another way:
How do I create a dynamic internal table with one field as another internal table.
Quick replies are highly appreciated.
Thanks,
Nisha Vengal.

halo Nisha
Before building the display table . you can add the field in the feild catalog right . This display table gets generated from the field catalog right
1 Create a global structute say ZEXTEND_FIELDCAT
2 Have fields like STYLE type lvc_t_styl
                         COLOR type LVC_T_SCOL.
3 Now you have to extend ur fieldcatalog
l_fieldcat-fieldname = COLOR'.
l_fieldcat-ref_field = 'COLOR'.
l_fieldcat-ref_table = 'ZEXTEND_FIELDCAT'.
APPEND l_fieldcat TO lt_field_catalog.
CLEAR l_fieldcat.

Complex mapping with deep structure

Hi all,
I need to create a complex mapping as follows:
Source message:
CreateOrder (0..1)
-sell-order (0..1)
--items-sell-order (0..1)
---items-sell-request (0..unbounded)
sell-discount (0..1)
sell-discount (0..unbounded)
discount-id (0..1)
discount-quantity (0..1)
description (0..1)
Target message:
MT_xxxx
-ORDER_V3 (0..1)
--TDESC (0..1)
---item (0..unbounded)
ITEM_NUMBER (0..1)
discount (0..unbounded)
REASON (0..1)
VALUE (0..1)
DESCRIPTION (0..1)
--TPLUGIN (0..1)
---item (0..unbounded)
ITEM_NUMBER (0..1)
discount (0..unbounded)
ID (0..1)
QUANTITY (0..1)
The mapping has some rules:
If sell-order - items-sell-order - items-sell-request - sell-discount - sell-discount - discount-id .length > 0 then the structure TPLUGIN must be filled
else
the structure TDESC must be filled
The problem is: the field ITEM_NUMBER is an index that is unique and must increment each record of node items-sell-request, and it is not mandatory an item to have discounts.
When I test with n items and all items with discount node, it works perfect. However, if I put for example 10 items in the source array, and for example the records 5 and 6 doesn't have discounts, the association item x discount makes the mapping get lost and mess all the target nodes.
Could anyone help me?
Thanks in advance.
Ricardo.

Hi Luis,
An example for source message could be something like:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:CreateOrder>
   <ns0:sell-order>
      <ns1:items-sell-order>
         <ns1:items-sell-request>
            <ns1:sell-discount>
               <ns1:sell-discount>
                  <ns1:discount-id>1</ns1:discount-id>
                  <ns1:discount-quantity>10</ns1:discount-quantity>
                  <ns1:description>Description1</ns1:description>
               </ns1:sell-discount>
            <ns1:sell-discount>
                  <ns1:discount-id>2</ns1:discount-id>
                  <ns1:discount-quantity>20</ns1:discount-quantity>
                  <ns1:description>Description2</ns1:description>
               </ns1:sell-discount>
            </ns1:sell-discount>
         </ns1:items-sell-request>
      <ns1:items-sell-request>
                *other fields not mentioned here, without sell-discount node*
         </ns1:items-sell-request>
           <ns1:items-sell-request>
            <ns1:sell-discount>
               <ns1:sell-discount>
                  <ns1:discount-id>A</ns1:discount-id>
                  <ns1:discount-quantity>50</ns1:discount-quantity>
                  <ns1:description>DescriptionA</ns1:description>
               </ns1:sell-discount>
               <ns1:sell-discount>
                  <ns1:discount-id>B</ns1:discount-id>
                  <ns1:discount-quantity>100</ns1:discount-quantity>
                  <ns1:description>DescriptionB</ns1:description>
               </ns1:sell-discount>
               <ns1:sell-discount>
                  <ns1:discount-id>C</ns1:discount-id>
                  <ns1:discount-quantity>200</ns1:discount-quantity>
                  <ns1:description>DescriptionC</ns1:description>
               </ns1:sell-discount>
            </ns1:sell-discount>
         </ns1:items-sell-request>
           <ns1:items-sell-request>
            <ns1:sell-discount>
               <ns1:sell-discount>
                  <ns1:discount-id>I</ns1:discount-id>
                  <ns1:discount-quantity>400</ns1:discount-quantity>
                  <ns1:description>DescriptionI</ns1:description>
               </ns1:sell-discount>
               <ns1:sell-discount>
                  <ns1:discount-id>II</ns1:discount-id>
                  <ns1:discount-quantity>500</ns1:discount-quantity>
                  <ns1:description>DescriptionII</ns1:description>
               </ns1:sell-discount>
            </ns1:sell-discount>
         </ns1:items-sell-request>
      </ns1:items-sell-order>
   </ns0:sell-order>
</ns0:CreateOrder>
And an example for target message related to this source is:
<?xml version="1.0" encoding="UTF-8"?>
<ns2:MT_xxxx">
<ORDER_V3>
     <TDESC>
          <item>
               <ITEM_NUMBER>4</ITEM_NUMBER>
               <discount>
                    <REASON>I</REASON>
                    <VALUE>400</VALUE>
                    <DESCRIPTION>DescriptionI</DESCRIPTION>
               </discount>
          </item>
     </TDESC>
     <TPLUGIN>
          <item>
               <ITEM_NUMBER>1</ITEM_NUMBER>
               <discount>
                    <ID>1</ID>
                    <QUANTITY>10</QUANTITY>
               </discount>
               <discount>
                    <ID>2</ID>
                    <QUANTITY>20</QUANTITY>
               </discount>
          </item>
          <item>
               <ITEM_NUMBER>3</ITEM_NUMBER>
               <discount>
                    <ID>A</ID>
                    <QUANTITY>50</QUANTITY>
               </discount>
               <discount>
                    <ID>B</ID>
                    <QUANTITY>100</QUANTITY>
               </discount>
               <discount>
                    <ID>C</ID>
                    <QUANTITY>200</QUANTITY>
               </discount>
          </item>
     </TPLUGIN>
</ORDER_V3>
</ns2:MT_GerarOrdVd_req>
Edited by: Ricardo Guedes on Oct 20, 2011 3:03 AM

Can we create a deep structure in RFC?

Hi,
My requirement is to create an RFC which has 3 output tables. out of which 1 table contains deep structure, but SAP is not allowing me to create an RFC with deep structure. Message shows only flat structures support in RFC. can any one tell is there any limitation of creating a deep structure in RFC?
Thanks,
Kumar.

Instead of a deep structure, you can define another internal table in your signature which will hold all of the data for all of th records of the other internal table, you just need a key value from the other internal table to be able to map which records go with what record in the original internal table. Does this make sense?
Regards,
Rich Heilman

ALV report with dynamic columns, and repeated structure rows

Hey Guys,
I've done some ALV programming, but most of the reports were straight forward. This one is a little interesting. So here go the questions...
Q1: Regarding Columns:
What is the best way to code a report with columns being dynamic. This is one of the parameters the user is going to enter in his input.
Q2: Regarding Rows:
I want to repeat a structure(say it contains f1, f2, f3) multiple time in rows. What is the best way to do it? The labels for these fields have to appear in the first column.
Below is the visual representation of the questions.
Jan 06 , Feb 06, Mar 06....(dynamic)
   material 1
Current Stock
current required
$Value of stock
   material 2
Current Stock
current required
$Value of stock
   material 3
Current Stock
current required
$Value of stock
Thanks for your help.
Sumit.

Hi Sumit,
Just check this sample from one of the SAP site
ABAP Code Sample for Dynamic Table for ALV with Cell Coloring
Applies To:
ABAP / ALV Grid
Article Summary
ABAP Code Sample that uses dynamic programming techniques to build a dynamic internal table for display in an ALV Grid with Cell Coloring.
Code Sample
REPORT zcdf_dynamic_table.
* Dynamic ALV Grid with Cell Coloring.
* Build a field catalog dynamically and provide the ability to color
* the cells.
* To test, copy this code to any program name and create screen 100
* as described in the comments. After the screen is displayed, hit
* enter to exit the screen.
* Tested in 4.6C and 6.20
* Charles Folwell - [email protected] - Feb 2, 2005
DATA:
r_dyn_table TYPE REF TO data,
r_wa_dyn_table TYPE REF TO data,
r_dock_ctnr TYPE REF TO cl_gui_docking_container,
r_alv_grid TYPE REF TO cl_gui_alv_grid,
t_fieldcat1 TYPE lvc_t_fcat, "with cell color
t_fieldcat2 TYPE lvc_t_fcat, "without cell color
wa_fieldcat LIKE LINE OF t_fieldcat1,
wa_cellcolors TYPE LINE OF lvc_t_scol,
wa_is_layout TYPE lvc_s_layo.
FIELD-SYMBOLS:
<t_dyn_table> TYPE STANDARD TABLE,
<wa_dyn_table> TYPE ANY,
<t_cellcolors> TYPE lvc_t_scol,
<w_field> TYPE ANY.
START-OF-SELECTION.
* Build field catalog based on your criteria.
wa_fieldcat-fieldname = 'FIELD1'.
wa_fieldcat-inttype = 'C'.
wa_fieldcat-outputlen = '10'.
wa_fieldcat-coltext = 'My Field 1'.
wa_fieldcat-seltext = wa_fieldcat-coltext.
APPEND wa_fieldcat TO t_fieldcat1.
wa_fieldcat-fieldname = 'FIELD2'.
wa_fieldcat-inttype = 'C'.
wa_fieldcat-outputlen = '10'.
wa_fieldcat-coltext = 'My Field 2'.
wa_fieldcat-seltext = wa_fieldcat-coltext.
APPEND wa_fieldcat TO t_fieldcat1.
* Before adding cell color table, save fieldcatalog to pass
* to ALV call. The ALV call needs a fieldcatalog without
* the internal table for cell coloring.
t_fieldcat2[] = t_fieldcat1[].
* Add cell color table.
* CALENDAR_TYPE is a structure in the dictionary with a
* field called COLTAB of type LVC_T_SCOL. You can use
* any structure and field that has the type LVC_T_SCOL.
wa_fieldcat-fieldname = 'T_CELLCOLORS'.
wa_fieldcat-ref_field = 'COLTAB'.
wa_fieldcat-ref_table = 'CALENDAR_TYPE'.
APPEND wa_fieldcat TO t_fieldcat1.
* Create dynamic table including the internal table
* for cell coloring.
CALL METHOD cl_alv_table_create=>create_dynamic_table
EXPORTING
it_fieldcatalog = t_fieldcat1
IMPORTING
ep_table = r_dyn_table
EXCEPTIONS
generate_subpool_dir_full = 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.
* Get access to new table using field symbol.
ASSIGN r_dyn_table->* TO <t_dyn_table>.
* Create work area for new table.
CREATE DATA r_wa_dyn_table LIKE LINE OF <t_dyn_table>.
* Get access to new work area using field symbol.
ASSIGN r_wa_dyn_table->* TO <wa_dyn_table>.
* Get data into table from somewhere. Field names are
* known at this point because field catalog is already
* built. Read field names from the field catalog or use
* COMPONENT <number> in a DO loop to access the fields. A
* simpler hard coded approach is used here.
ASSIGN COMPONENT 'FIELD1' OF STRUCTURE <wa_dyn_table> TO <w_field>.
<w_field> = 'ABC'.
ASSIGN COMPONENT 'FIELD2' OF STRUCTURE <wa_dyn_table> TO <w_field>.
<w_field> = 'XYZ'.
APPEND <wa_dyn_table> TO <t_dyn_table>.
ASSIGN COMPONENT 'FIELD1' OF STRUCTURE <wa_dyn_table> TO <w_field>.
<w_field> = 'TUV'.
ASSIGN COMPONENT 'FIELD2' OF STRUCTURE <wa_dyn_table> TO <w_field>.
<w_field> = 'DEF'.
APPEND <wa_dyn_table> TO <t_dyn_table>.
* Color cells based on your criteria. In this example, a test on
* FIELD2 is used to decide on color.
LOOP AT <t_dyn_table> INTO <wa_dyn_table>.
ASSIGN COMPONENT 'FIELD2' OF STRUCTURE <wa_dyn_table> TO <w_field>.
* Get access to internal table used to color cells.
ASSIGN COMPONENT 'T_CELLCOLORS'
OF STRUCTURE <wa_dyn_table> TO <t_cellcolors>.
CLEAR wa_cellcolors.
wa_cellcolors-fname = 'FIELD2'.
IF <w_field> = 'DEF'.
wa_cellcolors-color-col = '7'.
ELSE.
wa_cellcolors-color-col = '5'.
ENDIF.
APPEND wa_cellcolors TO <t_cellcolors>.
MODIFY <t_dyn_table> FROM <wa_dyn_table>.
ENDLOOP.
* Display screen. Define screen 100 as empty, with next screen
* set to 0 and flow logic of:
* PROCESS BEFORE OUTPUT.
* MODULE initialization.
* PROCESS AFTER INPUT.
CALL SCREEN 100.
* MODULE initialization OUTPUT
MODULE initialization OUTPUT.
* Set up for ALV display.
IF r_dock_ctnr IS INITIAL.
CREATE OBJECT r_dock_ctnr
EXPORTING
side = cl_gui_docking_container=>dock_at_left
ratio = '90'.
CREATE OBJECT r_alv_grid
EXPORTING i_parent = r_dock_ctnr.
* Set ALV controls for cell coloring table.
wa_is_layout-ctab_fname = 'T_CELLCOLORS'.
* Display.
CALL METHOD r_alv_grid->set_table_for_first_display
EXPORTING
is_layout = wa_is_layout
CHANGING
it_outtab = <t_dyn_table>
it_fieldcatalog = t_fieldcat2.
ELSE. "grid already prepared
* Refresh display.
CALL METHOD r_alv_grid->refresh_table_display
EXPORTING
i_soft_refresh = ' '
EXCEPTIONS
finished = 1
OTHERS = 2.
ENDIF.
ENDMODULE. " initialization OUTPUT
Regards
vijay

ALV dynamic with deep structure

Similar Messages

Maybe you are looking for