Transfer ALV Output through Function Module

Hi All,
I have a requirement where I am dealing with two systems.
1) There is a report program which run in ECC Server and it makes an RFC Call to trigger another program in APO Server
2) The target program generates an ALV Output and I just want to bring back the output into ECC system
3) How to achieve this ? How can transport the AVL Output throug the parameters of the RFC Function Module.
Any help/clue on this would be highly appreciated
Thanks,
Babu Kilari

Hello Babu,
If you are submitting the standard report in background mode, try this algo:
1. You can export the output list to the ABAP memory using the EXPORTING LIST TO MEMORY.
2. Then get the list details using the FM: LIST_FROM_MEMORY. Return the resultant internal table to your RFC.
Hope this helps.
BR,
Suhas

Similar Messages

Printing ALV Report output through Function Modules

Hi All,
I want to print my ALV Grid output through function modules/statement (not through print option in menu).
This is because, i am generating a PDF from spool when user clicks on a button. If any changes happened in the ALV output layout, they will be captured in spool through printing it.
So can you please tell me how to print the ALV Output through FMs or sending the ALV output to spool.
Thanks & Regards,
Senthil.
Edited by: senthil nathan on May 17, 2010 2:49 PM

Hi Dev,
Thanks for the reply.
I want to print the ALV when the user clicks on a button in toolbar. Lets say the user has made some changes to the layout, (E.g hiding a field) and when i print that output it should use the changed layout, If i use the FM suggested by you, i cant acheive this.
If you try to print this manually, the system uses the changed layout and not the original. Thats why i want to know FMs/statement to print.
Regards,
Senthil.

Possible to trigger output type through Function module?

Hi,
Is it possible to trigger output type through Function modules or through some codings or any standard FM's?
Regards
Bala.

You did not specify what area you need to retrigger an output type for, but here is a sample to retrigger a delivery output.
CALL FUNCTION 'BAPI_LIKP_PROCESS_MSG_DIRECT'
    EXPORTING
DYNAMICOUTPUTDEVICE       =
      processing                       = PROCESSING
SORTMESSAGE               = 1
    TABLES
      deliverynumber                 = delnbrs
      outputtype                       = outputs
      messageprotocol              = bapimsgprot
      return                              = bapiret2.
Thanks

How Procurement cost can be captured in product master through functional module?

Hi
I have following Queries
1) How Procurement cost can be captured in product master through functional module in SAP APO?
2) How we can transfer procurement cost to product master in SAP APO through BAPI?
Thanks
Poorna

Hi Poorna,
Could you please check FM /SAPAPO/DM_PRODUCTS_POST.
Table it_matloc of this FM can used to update Cost .

Binding Data through function module in adobe to display charts

Hello Gurus,
This is the requirement :-
Through function module output i have to display the chart.
For ex:-In sales order transaction there is a field called status.For every order there is status (open, complete, inprocess). Display the chart based on the order status that how many open, complete and inprocess are there.
Thanks,
Karan

post Adobe related questions to RIA forum at
User Interface Technology

ALV Tree using Function Modules

Hi,
I want a simple example of ALV Tree using Function Modules which can display multiple Columns in the Hierarchically arranged fashion along with nodes & icons.
Also should be able to handle the events.
Thanks in Advance..

Hi Ramesh,
Here is a example of alv tree
*& Report BCALV_TREE_DEMO                                             *
report bcalv_tree_demo.
class cl_gui_column_tree definition load.
class cl_gui_cfw definition load.
data tree1 type ref to cl_gui_alv_tree.
data mr_toolbar type ref to cl_gui_toolbar.
include <icon>.
include bcalv_toolbar_event_receiver.
include bcalv_tree_event_receiver.
data: toolbar_event_receiver type ref to lcl_toolbar_event_receiver.
data: gt_sflight      type sflight occurs 0,      "Output-Table
      gt_fieldcatalog type lvc_t_fcat, "Fieldcatalog
      ok_code like sy-ucomm.           "OK-Code
start-of-selection.
end-of-selection.
call screen 100.
*&      Module PBO OUTPUT
*       process before output
module pbo output.
set pf-status 'MAIN100'.
if tree1 is initial.
    perform init_tree.
endif.
call method cl_gui_cfw=>flush.
endmodule.                             " PBO OUTPUT
*&      Module PAI INPUT
*       process after input
module pai input.
case ok_code.
    when 'EXIT' or 'BACK' or 'CANC'.
      perform exit_program.
    when others.
      call method cl_gui_cfw=>dispatch.
endcase.
clear ok_code.
call method cl_gui_cfw=>flush.
endmodule.                             " PAI INPUT
*&      Form build_fieldcatalog
*       build fieldcatalog for structure sflight
form build_fieldcatalog.
* get fieldcatalog
call function 'LVC_FIELDCATALOG_MERGE'
       exporting
            i_structure_name = 'SFLIGHT'
       changing
            ct_fieldcat      = gt_fieldcatalog.
* change fieldcatalog
data: ls_fieldcatalog type lvc_s_fcat.
loop at gt_fieldcatalog into ls_fieldcatalog.
    case ls_fieldcatalog-fieldname.
      when 'CARRID' or 'CONNID' or 'FLDATE'.
        ls_fieldcatalog-no_out = 'X'.
        ls_fieldcatalog-key    = ''.
      when 'PRICE' or 'SEATSOCC' or 'SEATSMAX' or 'PAYMENTSUM'.
        ls_fieldcatalog-do_sum = 'X'.
    endcase.
    modify gt_fieldcatalog from ls_fieldcatalog.
endloop.
endform.                               " build_fieldcatalog
*&      Form build_hierarchy_header
*       build hierarchy-header-information
*      -->P_L_HIERARCHY_HEADER strucxture for hierarchy-header
form build_hierarchy_header changing
                               p_hierarchy_header type treev_hhdr.
p_hierarchy_header-heading = 'Hierarchy Header'.         "#EC NOTEXT
p_hierarchy_header-tooltip =
                         'This is the Hierarchy Header !'. "#EC NOTEXT
p_hierarchy_header-width = 30.
p_hierarchy_header-width_pix = ''.
endform.                               " build_hierarchy_header
*&      Form exit_program
*       free object and leave program
form exit_program.
call method tree1->free.
leave program.
endform.                               " exit_program
*&      Form build_header
*       build table for html_header
* --> p1        text
* <-- p2        text
form build_comment using
      pt_list_commentary type slis_t_listheader
      p_logo             type sdydo_value.
data: ls_line type slis_listheader.
* LIST HEADING LINE: TYPE H
clear ls_line.
ls_line-typ = 'H'.
* LS_LINE-KEY: NOT USED FOR THIS TYPE
ls_line-info = 'ALV-tree-demo: flight-overview'.       "#EC NOTEXT
append ls_line to pt_list_commentary.
* STATUS LINE: TYPE S
clear ls_line.
ls_line-typ = 'S'.
ls_line-key = 'valid until'.                          "#EC NOTEXT
ls_line-info = 'January 29 1999'.                      "#EC NOTEXT
append ls_line to pt_list_commentary.
ls_line-key = 'time'.
ls_line-info = '2.00 pm'.                              "#EC NOTEXT
append ls_line to pt_list_commentary.
* ACTION LINE: TYPE A
clear ls_line.
ls_line-typ = 'A'.
* LS_LINE-KEY: NOT USED FOR THIS TYPE
ls_line-info = 'actual data'.                          "#EC NOTEXT
append ls_line to pt_list_commentary.
p_logo = 'ENJOYSAP_LOGO'.
endform.
*&      Form create_hierarchy
*       text
* --> p1        text
* <-- p2        text
form create_hierarchy.
data: ls_sflight type sflight,
        lt_sflight type sflight occurs 0.
* get data
select * from sflight into table lt_sflight
                        UP TO 200 ROWS .
sort lt_sflight by carrid connid fldate.
* add data to tree
data: l_carrid_key type lvc_nkey,
        l_connid_key type lvc_nkey,
        l_last_key type lvc_nkey.
loop at lt_sflight into ls_sflight.
    on change of ls_sflight-carrid.
      perform add_carrid_line using    ls_sflight
                              changing l_carrid_key.
    endon.
    on change of ls_sflight-connid.
      perform add_connid_line using    ls_sflight
                                       l_carrid_key
                              changing l_connid_key.
    endon.
    perform add_complete_line using ls_sflight
                                     l_connid_key
                            changing l_last_key.
endloop.
* calculate totals
call method tree1->update_calculations.
* this method must be called to send the data to the frontend
call method tree1->frontend_update.
endform.                               " create_hierarchy
*&      Form add_carrid_line
*       add hierarchy-level 1 to tree
*      -->P_LS_SFLIGHT sflight
*      -->P_RELEATKEY   relatkey
*     <-->p_node_key    new node-key
form add_carrid_line using     ps_sflight type sflight
                               p_relat_key type lvc_nkey
                     changing p_node_key type lvc_nkey.
data: l_node_text type lvc_value,
        ls_sflight type sflight.
* set item-layout
data: lt_item_layout type lvc_t_layi,
        ls_item_layout type lvc_s_layi.
ls_item_layout-t_image = '@3P@'.
ls_item_layout-fieldname = tree1->c_hierarchy_column_name.
ls_item_layout-style   =
                        cl_gui_column_tree=>style_intensifd_critical.
append ls_item_layout to lt_item_layout.
* add node
l_node_text = ps_sflight-carrid.
call method tree1->add_node
    exporting
          i_relat_node_key = p_relat_key
          i_relationship   = cl_gui_column_tree=>relat_last_child
          i_node_text      = l_node_text
          is_outtab_line   = ls_sflight
          it_item_layout   = lt_item_layout
       importing
          e_new_node_key = p_node_key.
endform.                               " add_carrid_line
*&      Form add_connid_line
*       add hierarchy-level 2 to tree
*      -->P_LS_SFLIGHT sflight
*      -->P_RELEATKEY   relatkey
*     <-->p_node_key    new node-key
form add_connid_line using     ps_sflight type sflight
                               p_relat_key type lvc_nkey
                     changing p_node_key type lvc_nkey.
data: l_node_text type lvc_value,
        ls_sflight type sflight.
* set item-layout
data: lt_item_layout type lvc_t_layi,
        ls_item_layout type lvc_s_layi.
ls_item_layout-t_image = '@3Y@'.
ls_item_layout-style   =
                        cl_gui_column_tree=>style_intensified.
ls_item_layout-fieldname = tree1->c_hierarchy_column_name.
append ls_item_layout to lt_item_layout.
* add node
l_node_text = ps_sflight-connid.
call method tree1->add_node
    exporting
          i_relat_node_key = p_relat_key
          i_relationship   = cl_gui_column_tree=>relat_last_child
          i_node_text      = l_node_text
          is_outtab_line   = ls_sflight
          it_item_layout   = lt_item_layout
       importing
          e_new_node_key = p_node_key.
endform.                               " add_connid_line
*&      Form add_cmplete_line
*       add hierarchy-level 3 to tree
*      -->P_LS_SFLIGHT sflight
*      -->P_RELEATKEY   relatkey
*     <-->p_node_key    new node-key
form add_complete_line using   ps_sflight type sflight
                               p_relat_key type lvc_nkey
                     changing p_node_key type lvc_nkey.
data: l_node_text type lvc_value.
* set item-layout
data: lt_item_layout type lvc_t_layi,
        ls_item_layout type lvc_s_layi.
ls_item_layout-fieldname = tree1->c_hierarchy_column_name.
ls_item_layout-class   = cl_gui_column_tree=>item_class_checkbox.
ls_item_layout-editable = 'X'.
append ls_item_layout to lt_item_layout.
l_node_text = ps_sflight-fldate.
call method tree1->add_node
    exporting
          i_relat_node_key = p_relat_key
          i_relationship   = cl_gui_column_tree=>relat_last_child
          is_outtab_line   = ps_sflight
          i_node_text      = l_node_text
          it_item_layout   = lt_item_layout
       importing
          e_new_node_key = p_node_key.
endform.                               " add_complete_line
*&      Form register_events
*       text
* --> p1        text
* <-- p2        text
form register_events.
* define the events which will be passed to the backend
data: lt_events type cntl_simple_events,
        l_event type cntl_simple_event.
* define the events which will be passed to the backend
l_event-eventid = cl_gui_column_tree=>eventid_expand_no_children.
append l_event to lt_events.
l_event-eventid = cl_gui_column_tree=>eventid_checkbox_change.
append l_event to lt_events.
l_event-eventid = cl_gui_column_tree=>eventid_header_context_men_req.
append l_event to lt_events.
l_event-eventid = cl_gui_column_tree=>eventid_node_context_menu_req.
append l_event to lt_events.
l_event-eventid = cl_gui_column_tree=>eventid_item_context_menu_req.
append l_event to lt_events.
l_event-eventid = cl_gui_column_tree=>eventid_header_click.
append L_EVENT to lt_events.
l_event-eventid = cl_gui_column_tree=>eventid_item_keypress.
append L_EVENT to lt_events.
call method tree1->set_registered_events
    exporting
      events = lt_events
    exceptions
      cntl_error                = 1
      cntl_system_error         = 2
      illegal_event_combination = 3.
if sy-subrc <> 0.
    message x208(00) with 'ERROR'.                       "#EC NOTEXT
endif.
* set Handler
data: l_event_receiver type ref to lcl_tree_event_receiver.
create object l_event_receiver.
set handler l_event_receiver->handle_node_ctmenu_request
                                                        for tree1.
set handler l_event_receiver->handle_node_ctmenu_selected
                                                        for tree1.
set handler l_event_receiver->handle_item_ctmenu_request
                                                        for tree1.
set handler l_event_receiver->handle_item_ctmenu_selected
                                                        for tree1.
endform.                               " register_events
*&      Form change_toolbar
*       text
* --> p1        text
* <-- p2        text
form change_toolbar.
* get toolbar control
call method tree1->get_toolbar_object
          importing
              er_toolbar = mr_toolbar.
check not mr_toolbar is initial.
* add seperator to toolbar
call method mr_toolbar->add_button
          exporting
              fcode     = ''
              icon      = ''
              butn_type = cntb_btype_sep
              text      = ''
              quickinfo = 'This is a Seperator'.         "#EC NOTEXT
* add Standard Button to toolbar (for Delete Subtree)
call method mr_toolbar->add_button
          exporting
              fcode     = 'DELETE'
              icon      = '@18@'
              butn_type = cntb_btype_button
              text      = ''
              quickinfo = 'Delete subtree'.              "#EC NOTEXT
* add Dropdown Button to toolbar (for Insert Line)
call method mr_toolbar->add_button
          exporting
              fcode     = 'INSERT_LC'
              icon      = '@17@'
              butn_type = cntb_btype_dropdown
              text      = ''
              quickinfo = 'Insert Line'.           "#EC NOTEXT
* set event-handler for toolbar-control
create object toolbar_event_receiver.
set handler toolbar_event_receiver->on_function_selected
                                                      for mr_toolbar.
set handler toolbar_event_receiver->on_toolbar_dropdown
                                                      for mr_toolbar.
endform.                               " change_toolbar
*&      Form init_tree
*       text
* --> p1        text
* <-- p2        text
FORM init_tree.
* create fieldcatalog for structure sflight
perform build_fieldcatalog.
* create container for alv-tree
data: l_tree_container_name(30) type c,
        l_custom_container type ref to cl_gui_custom_container.
l_tree_container_name = 'TREE1'.
if sy-batch is initial.
    create object l_custom_container
      exporting
            container_name = l_tree_container_name
      exceptions
            cntl_error                  = 1
            cntl_system_error           = 2
            create_error                = 3
            lifetime_error              = 4
            lifetime_dynpro_dynpro_link = 5.
    if sy-subrc <> 0.
      message x208(00) with 'ERROR'.                       "#EC NOTEXT
    endif.
endif.
* create tree control
create object tree1
    exporting
        parent              = l_custom_container
        node_selection_mode = cl_gui_column_tree=>node_sel_mode_single
        item_selection      = 'X'
        no_html_header      = ''
        no_toolbar          = ''
    exceptions
        cntl_error                   = 1
        cntl_system_error            = 2
        create_error                 = 3
        lifetime_error               = 4
        illegal_node_selection_mode = 5
        failed                       = 6
        illegal_column_name          = 7.
if sy-subrc <> 0.
    message x208(00) with 'ERROR'.                       "#EC NOTEXT
endif.
* create Hierarchy-header
data l_hierarchy_header type treev_hhdr.
perform build_hierarchy_header changing l_hierarchy_header.
* create info-table for html-header
data: lt_list_commentary type slis_t_listheader,
        l_logo             type sdydo_value.
perform build_comment using
                 lt_list_commentary
                 l_logo.
* repid for saving variants
data: ls_variant type disvariant.
ls_variant-report = sy-repid.
* create emty tree-control
call method tree1->set_table_for_first_display
     exporting
               is_hierarchy_header = l_hierarchy_header
               it_list_commentary   = lt_list_commentary
               i_logo               = l_logo
               i_background_id      = 'ALV_BACKGROUND'
               i_save               = 'A'
               is_variant            = ls_variant
     changing
               it_outtab            = gt_sflight "table must be emty !!
               it_fieldcatalog      = gt_fieldcatalog.
* create hierarchy
perform create_hierarchy.
* add own functioncodes to the toolbar
perform change_toolbar.
* register events
perform register_events.
* adjust column_width
call method tree1->COLUMN_OPTIMIZE.
ENDFORM.                    " init_tree
regards,
venu.

Problem in transfer rules-- Calling the function module.

Hi All,
when we r extracting the data from r3, the infoobject 0wbs_elem the data pulled is in internal format in which wbs element is stored.
wbs element gets stored in a different way compared to front end.
Eg. The external format is /abc/123 the internal format is 00012300.
I have written a transfer routine using the function module CONVERSION_EXIT_ABPSP_OUTPUT.
the code goes like this
data ifield(30) type c.
call function CONVERSION_EXIT_ABPSP_OUTPUT
Exporting
input = tran_structure-wbselem (Field in transfer structure---name of the field in source system) .
Importing
output = ifield.
result = ifield.
End of code.
Problem
When I am Scheduling the package the job doesnt get completed for a long time and fails.Is there a problem with the code. When trying for the Simulation of the datapackets, the system says no data package number could be determined.
Please help me out...
Thank You
Mahesh

Hi Mahesh,
Could you please check ST22 and see if there is any short dumps ?
try to do test run for the FMs using SE37 and see what is the output for your input.
Do you have PSA for the load ? It may also have been deleted. You get this message when there is no PSA available.
hope it helps
Thanks
Soumya

Generic Extraction business Requirement, through function module,

Generic Extraction business Requirement, specifically through function module and source code in function module.

Dear Karthik,
Go to transaction SBIW -> Generic Datasource -> Maintain Generic Datasources -> Choose Master/Transaction Data -> Maintain proper entries (Application Component, Descriptions) -> Extraction by FM if you want to extract using FM.
Maintaining Generic DataSources - Independently of application, you can create and maintain generic DataSources for transaction data, master data attributes or texts from any kinds of transparent tables, database views, InfoSets of the SAP query or using a function module. As a result, you can make use of the generic extraction of data.
Creating a Generic DataSource
       1.      Select the DataSource type and give it a technical name.
       2.      Choose Create. The creating a generic DataSource screen appears.
       3.      Choose an application component to which the DataSource is to be assigned.
       4.      Enter the descriptive texts. You can choose any text.
       5.      Choose from which datasets the generic DataSource is to be filled.
                            a.      Choose Extraction from View, if you want to extract data from a transparent table or a database view. Enter the name of the table or the database view.
After generation, you get a DataSource whose extract structure is congruent with the database view or the transparent table view.
For more information about creating and maintaining database views and tables, see the ABAP Dictionary Documentation.
                            b.      Choose Extraction from Query, if you want to use a SAP query InfoSet as the data source. Select the required InfoSet from the InfoSet catalog.
After generation, you now have a DataSource whose extract structure matches the InfoSet.
For more information about maintaining the InfoSet, see the System Administration documentation.
                            c.      Choose Extraction using FM, if you want to extract data using a function module. Enter the function module and extract structure.
The data must be transferred by the function module in an interface table E_T_DATA.
For information about the function library, see the ABAP Workbench: Tools documentation.
                            d.      With texts, you also have the option of extraction from domain fixed values.
Maintain the settings for delta transfer where appropriate.
       7.      Choose Save.
Note when extracting from a transparent table or view:
If the extract structure contains a key figure field, that references to a unit of measure or currency unit field, this unit field must appear in the same extract structure as the key figure field.
A screen appears in which you can edit the fields of the extract structure.
       8.      Editing the DataSource:
       Selection
When scheduling a data request in the BW Scheduler, you can enter the selection criteria for the data transfer. For example, you may want to determine that data requests are only to apply to data from the previous month.
If you set the Selection indicator for a field within the extract structure, the data for this field is transferred in correspondence with the selection criteria in the scheduler.
       Hide field
You should set this indicator to exclude an extract structure field from the data transfer. As a result of your action, the field is no longer made available in BW when setting the transfer rules and generating the transfer structure.
       Inversion
Reverse postings are possible for customer-defined key figures. For this reason, inversion is only possible for certain transaction data DataSources. These include DataSources that have a field that is indicated as an inversion field, for example, the field update mode in the DataSource 0FI_AP_3. If this field has a value, then the data records are interpreted as reverse records in BW.
Set the Inversion indicator if you want to carry out a reverse posting for a customer-defined field (key figure). The value of the key figure is then transferred in inverted form (multiplied by 1) into BW.
       Field only known in exit
You can enhance data by extending the extract structure for a DataSource using fields in append structures.
The indicator Field only known in Exit is set for fields of an append structure. In other words, by default these fields are not passed onto the extractor from the field list and selection table.
Deselect the indicator Field Only Known in Exit to enable the Service API to pass on the append structure field to the extractor together with the fields of the delivered extract structures in the field list as well as in the selection table.
9. Choose DataSource -> Generate.
The DataSource is now saved in the source system.
Maintaining Generic DataSources
·        Change the DataSource
To change a generic DataSource, in the initial screen of DataSource maintenance, enter the name of the DataSource and choose Change.
You can change the assignment of a DataSource to an application component as well as the texts of a DataSource. Double-clicking on the name of the table, view, InfoSet or extract structure takes you to the appropriate maintenance screen. Here you can make changes required to add new fields. You can fully swap transparent tables and database views, but not InfoSets. If you return to the DataSource maintenance and choose Create, the screen for editing a DataSource appears. To save the DataSource in the SAP source system, choose DataSource -> Generate.
If you want to test extraction in the source system independently of a BW system, choose DataSource -> Test Extraction.
·        Delta DataSource
In the Change Generic DataSource screen, you can delete any DataSources that are no longer relevant. If you are extracting data from an InfoSet, delete the associated query. If you want to delete a DataSource, this must not be connected to a BW system.
Also visit :[Data Extraction from SAP Source System | http://help.sap.com/saphelp_nw04/helpdata/en/28/4c553c42360a40e10000000a114084/content.htm]
Regards,
Naveen.

Save EAN11 field while creating POrder creation through Function module

Hi All,
I want to update EAN11 field in material master while creating Purchase Order through function module. I am using function module BAPI_PO_CREATE1 for creating purchase order. There are no structures in the PO creation FM in which EAN11 field is there. I have also tried using function module MEPO_DOC_ITEM_PROCESS for updating EAN11 field. It is not working. Please suggest some method to do that.
Note: I am receiving EAN11 through an external system by proxy.
Thanks,
Chinmay

Hi,
Use BAPI_MATERIAL_SAVEDATA to updat ean numbers for materials.
tables INTERNATIONALARTNOS is used to update EAN.
Regards,
Shanmugavel Chandrasekaran

Example of a Simple ALV Report using Function Modules (not OO)

Hi,
I am new to ABAP. Where can I get a proper Example of a Simple ALV Report using Function Modules? I searched the forum but did not find a proper solution. Kindly help.
Smruthi.
Edited by: Smruthi Acharya on Jan 29, 2009 7:13 PM

Hi,
Use this demo code:-
REPORT z_alv01 MESSAGE-ID zmsg.
*          TABLES
TABLES : ekpo.
*          TYPE POOLS
TYPE-POOLS : slis.
*          TYPE DECLARATION
TYPES : BEGIN OF t_ekpo,
          ebeln TYPE ekpo-ebeln,
          ebelp TYPE ekpo-ebelp,
          matnr TYPE ekpo-matnr,
          werks TYPE ekpo-werks,
          menge TYPE ekpo-menge,
        END OF t_ekpo.
*          PARAMETERS
PARAMETERS : s_var TYPE disvariant-variant.
*          DATA DECLARATION
*VARIABLES
DATA : check(1),
       rep_id TYPE sy-repid.
*INTERNAL TABLE TYPE OF ZEKPO
DATA : it_ekpo TYPE STANDARD TABLE OF t_ekpo WITH HEADER LINE.
*FIELD CATALOG
DATA : it_field TYPE slis_t_fieldcat_alv,
       wa_field TYPE slis_fieldcat_alv.
*SORTING
DATA : it_sort TYPE slis_t_sortinfo_alv,
       wa_sort TYPE slis_sortinfo_alv.
*FOR TOP OF THE PAGE
DATA : it_top TYPE slis_t_listheader,
       wa_top TYPE slis_listheader.
*FOR END OF THE PAGE
DATA : it_end TYPE slis_t_listheader,
       wa_end TYPE slis_listheader.
*TO CAPTURE EVENTS AND HANDLE
DATA : it_event TYPE slis_t_event,
       wa_event TYPE slis_alv_event.
*FOR GRID TITLE
DATA : wa_title TYPE lvc_title.
*FOR LAYOUT
DATA : wa_layout TYPE slis_layout_alv.
*FOR EXCLUDING STANDARD BUTTON FROM ALV TOOLBAR
DATA : it_exclude TYPE slis_t_extab,
       wa_exclude TYPE slis_extab.
*FOR VARIANT
DATA : wa_variant TYPE disvariant.
*          INITIALIZATION
INITIALIZATION.
check = 'X'.
rep_id = sy-repid.
wa_variant-report = sy-repid.
*GET DEFUALT ON THE SELECTION SCREEN FOR DEFAULT DISPLAY
CALL FUNCTION 'REUSE_ALV_VARIANT_DEFAULT_GET'
    EXPORTING
      i_save        = 'A'
    CHANGING
      cs_variant    = wa_variant
    EXCEPTIONS
      wrong_input   = 1
      not_found     = 2
      program_error = 3
      OTHERS        = 4.
IF sy-subrc = 0.               " IF DEFAULT VARIANT FOUND
    s_var = wa_variant-variant. " PASS THE DEFAULT VARIANT TO THE SELECTION SCREEN FIELD
ENDIF.
*          AT-SELECTION SCREEN ON VALUE REQUEST
*          TO GET THE F4 HELP FOR VARIANT
AT SELECTION-SCREEN ON VALUE-REQUEST FOR s_var.
CALL FUNCTION 'REUSE_ALV_VARIANT_F4'
    EXPORTING
      is_variant                = wa_variant
*   I_TABNAME_HEADER          =
*   I_TABNAME_ITEM            =
*   IT_DEFAULT_FIELDCAT       =
     i_save                    = 'A'
*   I_DISPLAY_VIA_GRID        = ' '
   IMPORTING
*   E_EXIT                    =
     es_variant                = wa_variant
   EXCEPTIONS
     not_found                 = 1
     program_error             = 2
     OTHERS                    = 3.
IF sy-subrc = 0.
    s_var = wa_variant-variant. " PASS THE SELECTED VARIANT TO THE SELECTION SCREEN FIELD
ENDIF.
*          AT-SELECTION SCREEN
*          TO CHECK THE EXISTENCE FOR VARIANT
AT SELECTION-SCREEN.
wa_variant-variant = s_var.
CALL FUNCTION 'REUSE_ALV_VARIANT_EXISTENCE'
    EXPORTING
      i_save        = 'A'
    CHANGING
      cs_variant    = wa_variant
    EXCEPTIONS
      wrong_input   = 1
      not_found     = 2
      program_error = 3
      OTHERS        = 4.
IF sy-subrc <> 0.
    MESSAGE w001.
ENDIF.
*          START OF SELECTION
START-OF-SELECTION.
SELECT ebeln
         ebelp
         matnr
         werks
         menge
         FROM ekpo
         INTO TABLE it_ekpo.
*          FIELD CATALOG
wa_field-fieldname = 'EBELN'.
wa_field-tabname = 'IT_TAB'.
wa_field-outputlen = 10.
wa_field-seltext_l = 'PO #'.
APPEND wa_field TO it_field.
CLEAR wa_field.
wa_field-fieldname = 'EBELP'.
wa_field-tabname = 'IT_TAB'.
wa_field-outputlen = 10.
wa_field-seltext_l = 'Line Item'.
APPEND wa_field TO it_field.
CLEAR wa_field.
wa_field-fieldname = 'MATNR'.
wa_field-tabname = 'IT_TAB'.
wa_field-outputlen = 15.
wa_field-seltext_l = 'Material'.
* wa_field-input = check.
* wa_field-edit = check.
APPEND wa_field TO it_field.
CLEAR wa_field.
wa_field-fieldname = 'WERKS'.
wa_field-tabname = 'IT_TAB'.
wa_field-outputlen = 6.
wa_field-seltext_l = 'Plant'.
* wa_field-input = check.
* wa_field-edit = check.
APPEND wa_field TO it_field.
CLEAR wa_field.
wa_field-fieldname = 'MENGE'.
wa_field-tabname = 'IT_TAB'.
wa_field-outputlen = 10.
wa_field-seltext_l = 'Qty.'.
* wa_field-input = check.
* wa_field-edit = check.
wa_field-do_sum = check.
APPEND wa_field TO it_field.
CLEAR wa_field.
*          SORT W.R.T. PURCHASE ORDER NUMBER
wa_sort-spos = 1.
wa_sort-fieldname = 'EBELN'.
wa_sort-tabname = 'IT_EKPO'.
wa_sort-up = check.
wa_sort-subtot = check.
APPEND wa_sort TO it_sort.
CLEAR wa_sort.
*          FOR GRID TITLE
wa_title = 'Hello'.
*          FOR LAYOUT
wa_layout-zebra = check.
*          FOR EXCLUDING STANDARD BUTTONS FROM ALV TOOLBAR
wa_exclude-fcode = '&OUP'.
APPEND wa_exclude TO it_exclude.
CLEAR wa_exclude.
wa_exclude-fcode = '&ODN'.
APPEND wa_exclude TO it_exclude.
CLEAR wa_exclude.
wa_exclude-fcode = '&OAD'.
APPEND wa_exclude TO it_exclude.
CLEAR wa_exclude.
* wa_exclude-fcode = '&AVE'.
* APPEND wa_exclude TO it_exclude.
* CLEAR wa_exclude.
wa_exclude-fcode = '&INFO'.
APPEND wa_exclude TO it_exclude.
CLEAR wa_exclude.
*          POPULATE ALL EVENTS INTO INTERNAL TABLE
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
    EXPORTING
      i_list_type     = 0
    IMPORTING
      et_events       = it_event
    EXCEPTIONS
      list_type_wrong = 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.
READ TABLE it_event INTO wa_event WITH KEY name = 'END_OF_LIST'.
wa_event-form = 'END'.
MODIFY it_event FROM wa_event INDEX sy-tabix.
CLEAR wa_event.
*          DISPLAY RECORDS IN ALV GRID
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
   EXPORTING
*   I_INTERFACE_CHECK                 = ' '
*   I_BYPASSING_BUFFER                = ' '
*   I_BUFFER_ACTIVE                   = ' '
   i_callback_program                = rep_id
*   i_callback_pf_status_set          = 'PF'
   i_callback_user_command           = 'COMMAND'
   i_callback_top_of_page            = 'TOP'
*   I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
*   I_CALLBACK_HTML_END_OF_LIST       = ' '
*   I_STRUCTURE_NAME                  =
*   I_BACKGROUND_ID                   = ' '
   i_grid_title                      = wa_title
*   I_GRID_SETTINGS                   =
   is_layout                         = wa_layout
   it_fieldcat                       = it_field
   it_excluding                      = it_exclude
*   IT_SPECIAL_GROUPS                 =
   it_sort                           = it_sort
*   IT_FILTER                         =
*   IS_SEL_HIDE                       =
*   I_DEFAULT                         = 'X'
   i_save                            = 'A'
   is_variant                        = wa_variant
   it_events                         = it_event
*   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                          = it_ekpo
EXCEPTIONS
   program_error                     = 1
   OTHERS                            = 2.
IF sy-subrc <> 0.
ENDIF.
*&      Form top
*       TO WRITE THE HEADER
FORM top.
REFRESH it_top.
wa_top-typ = 'S'.
wa_top-key = text-001.
wa_top-info = rep_id.
APPEND wa_top TO it_top.
CLEAR wa_top.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      it_list_commentary       = it_top
*   I_LOGO                   =
*   I_END_OF_LIST_GRID       =
*   I_ALV_FORM               =
ENDFORM.                    "top
*&      Form end
*       TO WRITE THE FOOTER
FORM end.
REFRESH it_end.
wa_end-typ = 'S'.
wa_end-key = text-001.
wa_end-info = rep_id.
APPEND wa_end TO it_end.
CLEAR wa_end.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
    EXPORTING
      it_list_commentary       = it_end
*   I_LOGO                   =
*   I_END_OF_LIST_GRID       =
*   I_ALV_FORM               =
ENDFORM.                    "end
*&      Form pf
*       FOR PF-STATUS WITH USER DEFINED BUTTONS
*      -->RT_EXTAB   text
FORM pf USING rt_extab TYPE slis_t_extab.
SET PF-STATUS 'ZTG_PF_ALV'.
ENDFORM.                    "pf
*&      Form command
*       TO HANDLE USER ACTIONS AGAINST PF-STATUS
*      -->UCOMM      text
*      -->SELFIELD   text
FORM command USING ucomm LIKE sy-ucomm selfield TYPE slis_selfield.
DATA : ok_code TYPE sy-ucomm.
ok_code = ucomm.
CASE ok_code.
    WHEN 'T_DOWN'.
      CALL FUNCTION 'POPUP_TO_INFORM'
        EXPORTING
          titel = 'HELLO'
          txt1 = 'USER COMMAND'
          txt2 = 'TOTAL DOWN'.
    WHEN 'DOWN'.
      CALL FUNCTION 'POPUP_TO_INFORM'
        EXPORTING
          titel = 'HELLO'
          txt1 = 'USER COMMAND'
          txt2 = 'DOWN'.
    WHEN 'UP'.
      CALL FUNCTION 'POPUP_TO_INFORM'
        EXPORTING
          titel = 'HELLO'
          txt1 = 'USER COMMAND'
          txt2 = 'UP'.
    WHEN 'T_UP'.
      CALL FUNCTION 'POPUP_TO_INFORM'
        EXPORTING
          titel = 'HELLO'
          txt1 = 'USER COMMAND'
          txt2 = 'TOTAL UP'.
ENDCASE.
ENDFORM.                    "command
Hope this helps you.
Thanks & Regards,
Tarun Gambhir

Exporting Custom table through function module

<b>How can i Export Custom table through function module.</b> when we add some table in the function module table tab it asks for a ref. table which is some table in database .. but i want to add some custom table with some user defined column names..how can i do this
<b>n plz tell me how to loop thru select options</b>
i have to loop thru select option and assign all the values to a variable.
plz help me out
Message was edited by:
Karan Chopra

Hi Karan,
Do one thing, Just in the tables tab give the name of the table and don't write anything else. no TYPE and no ANY.
Hope it will resolve issue.
reward points if useful.
Regards,
Atish

Modify TRIP through function module( HRTRV_IF_MODIFY_TRIP )

Hi Experts,
I am trying to modify existing trip for employee through function module HRTRV_IF_MODIFY_TRIP in se37 in this i am passing employee no, trip no, framedata and in changing parameter fcode as "MOD". There is also a field as trip_guid whos value i don't know so left it blank. When i execute it in return table show message as "No suitable trip schema could be found".
Can any one help me in this case. Our java developer using this fmi to change a trip.
Thanks And Regards
Ranjeet Singh

Hi,
The system tries to read a valid trip schema in table T706S and no relevant entry found.
Sujay
PS: Please don't post all bold
Edited by: Sujay Venkateswaran Krishnakumar on Oct 15, 2010 4:54 PM

Alv grid using function module

hi all,
i am using editable alv grid. but i need to add a functionality by adding a button on toolbar on click on button a new blank row should be appended below where user can enter the new records. please suggest on this i am using alv grid using function module.

Hi
check this program
BCALV_TEST_GRID_EDITABLE
when u execute the program, there is an alv which displays a set of records.
where we have a option to add new row to the alv.check it.
Hope this helps you.

Display the long text in alv by using function modules

Hi all,
How to display the long text in alv by using function modules ?
Send me any sample code.
Thanks in advance
krupali.

Hello KR,
Use READ_TEXT and concatenate the first lines of the text.
CALL FUNCTION 'READ_TEXT'
     EXPORTING
          id       = 'F01'
          language = sy-langu
          name     = lv_name " purchase order with leading zeroes
          object   = 'EKKO'
     TABLES
          lines    = t_lines
     EXCEPTIONS
          OTHERS   = 8.
You can loop at t_lines and concatenate header in to some other field.
Best Regards,
Sasidhar Reddy Matli.
Edited by: Sasidhar Reddy Matli on Aug 13, 2008 12:25 PM

Delete a Infocube Request through Function module

Hi Experts,
I need to delete a request in Infocube through Function module. i have written a logic which request we have to delete, but i'm unable to find the exact function module to delete particular request.
Quick response would be appriciated greatly and points will be assigned.
Regards,
Navin Achanta

Hi,
All the requests of InfoCube are available in table RSICCONT, so u create a function module to delete a records from this table.
Hope this helps u a lot.........
Assigning points is the way of saying Thanks in SDN
Regards
Ramakrishna Kamurthy

Transfer ALV Output through Function Module

Similar Messages

Maybe you are looking for