Call transaction in module pool

Hi experts,
i have two transactions one is z1 and other is z2.
In z1 i have field called 'number' ,when i double click on 'number' it should call transaction z2 by skipping first screen.
it working fine,
but the main issues is the z2 tcode having three buttons in initial screen are create ,change,display.
so when i double click on z1 number i should call z2 tcode second screen in display mode by fetching all data of z2 based on number.
My main is issues is to display data in display mode in second screen of z2 tcode based on number when i double click on number.
z1 and z2 are ztcode.
Thanks and Regards
RAVI.

Hi, you can use SPA and GPA variables to pass a flag and the number you want to exchange between two tcodes. And check your GPA parameters in PBO of second tcode and make all fields input disabled with the SCREEN-INPUT = 0 option and write your data fetch logic to fill in the screen fields.
SCREEN is a system generated internal table which holds all screen fields as its contents and using this internal table, we can alter screen field properties like visibility and input etc.
Thanks,
Siva

Similar Messages

Calling Smartforms from Module pool: Most Urgent

Hi, Exeperts
how can I call smartforms from module pool.
I have done like below.
First Created a push button on screen and used
these code in user command through PAI
FORM CALL_SMARTFORMS .
DATA: V_FORM_NAME TYPE RS38L_FNAM.
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
EXPORTING
    FORMNAME           = 'ZSMART'
IMPORTING
    FM_NAME            = V_FORM_NAME
EXCEPTIONS
    NO_FORM            = 1
    NO_FUNCTION_MODULE = 2
    OTHERS             = 3.
ENDFORM.                    " CALL_SMARTFORMS
now I am getting form name in v_form_name, but it is not executing.
Please help me out.
Regards
Rajiv singh.

Well, as it's most urgent....
One you have a value in V_FORM_NAME you need to call this function module, passing the fields and strucures that make up the interface to your form.
Eg.
DATA: DEVICE TYPE SSFCTRLOP .
DEVICE-DEVICE = 'PRINTER'.
DEVICE-NO_DIALOG = 'X'.
CALL FUNCTION V_FORM_NAME
EXPORTING
   CONTROL_PARAMETERS         = device
   USER_SETTINGS              = 'X'
EXCEPTIONS
   FORMATTING_ERROR           = 1
   INTERNAL_ERROR             = 2
   SEND_ERROR                 = 3
   USER_CANCELED              = 4
   OTHERS                     = 5.
Regards,
Nick

Hiding navigation area from transaction screen--module pool

Using module pool, i am displaying a transaction screen at the click of a button.
This transaction screen also has a small navigation screen appearing on the left.I want to hide this navigation area.
How do I do it.

Hi,
Usually this is done by using the DOCKING container. You can call the method of SET_VISIBLE of the class CL_GUI_DOCKING_CONTAINER.
Regards,
Ravi
Note : Please mark the helpful answers

How to call a "Z"module pool program in a "z"report

Hi Guys,
I have two reports .
1. Report : uploads a tab delimited " .Txt1" file and update the "z1" table
    ".TXT1" : File contains 4 fields
2. Module pool. :Uploads a a tab delimited " .Txt2" file and update another "z2" table
    ".TXT2" file contains the 4 fileds of ".TXT1" and also 2 extra fields.
I want to merge (call) the module pool program in the Report and perform the upload function using only one ".TXT" file.Please do guide me precisely .
*Report:*
REPORT zrswbgcs009 NO STANDARD PAGE HEADING MESSAGE-ID zwb
                     LINE-SIZE 185.
TABLES: zgcs_foc.      "FOC Parts Table
*data count buffer
DATA:    read_cnt(6)    TYPE p,        "Find read record
         update_cnt(6) TYPE p,        "OK record
         error_cnt(6)   TYPE p.        "Error record
*file buffer(FOC)
DATA: BEGIN OF FOC_inrec OCCURS 0,
        CUSTOMER(10),      "Customer
        PART_CODE(18),     "Parts Code
        REF_NO(35),        "Ref No.
        REF_DATE(10),      "Ref Date
        QTY(12),           "Parts Qty
        TEXT(100),         "Remark
      END OF FOC_inrec.
*file buffer
DATA: BEGIN OF inrec OCCURS 0,
        CUSTOMER(10),      "Customer
        PART_CODE(18),     "Parts Code
        REF_NO(35),        "Ref No.
        REF_DATE(10),      "Ref Date
        QTY(12),           "Parts Qty
        PRICE(15),         "Parts Price
        WAERK(5),          "Parts Currency
        TEXT(100),         "Remark
      END OF inrec.
DATA : v_file      LIKE rlgrap-filename.
DATA gt_zgcs_foc LIKE zgcs_foc OCCURS 0 WITH HEADER LINE.
DATA gs_zgcs_foc LIKE zgcs_foc.
*File name ACCEPT--------------------------------------------------
SELECTION-SCREEN SKIP 1.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
*Company code
PARAMETERS: p_comp LIKE zgcs_imei-company OBLIGATORY.
PARAMETERS: pcfile LIKE rlgrap-filename OBLIGATORY LOWER CASE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN POSITION 1.
PARAMETERS: HQfile RADIOBUTTON GROUP b2.
SELECTION-SCREEN COMMENT 7(20) text-101 FOR FIELD HQfile.
SELECTION-SCREEN POSITION 31.
PARAMETERS: SUBfile RADIOBUTTON GROUP b2.
SELECTION-SCREEN COMMENT 37(20) text-102 FOR FIELD SUBfile.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END   OF BLOCK b1.
SELECTION-SCREEN SKIP 1.
SELECTION-SCREEN BEGIN OF BLOCK box WITH FRAME.
SELECTION-SCREEN: COMMENT /2(40) text-011, COMMENT 42(40) text-001,
                  ULINE,
                  COMMENT /2(40) text-012, COMMENT 42(40) text-002,
                  COMMENT /2(40) text-013, COMMENT 42(40) text-003,
                  COMMENT /2(40) text-014, COMMENT 42(40) text-004,
                  COMMENT /2(40) text-015, COMMENT 42(40) text-005,
                  COMMENT /2(40) text-016, COMMENT 42(40) text-006,
                  COMMENT /2(40) text-017, COMMENT 42(40) text-007,
                  COMMENT /2(40) text-018, COMMENT 42(40) text-008,
                                           COMMENT /42(40) text-009.
SELECTION-SCREEN END OF BLOCK box.
* -- AT SELECTION SCREEN ON
AT SELECTION-SCREEN ON VALUE-REQUEST FOR pcfile.
CALL FUNCTION 'WS_FILENAME_GET'
       EXPORTING
            def_filename     = space
            def_path         = 'C:\'
            mask             = ',*.txt,*.TXT.'
            mode             = 'O'
            title            = ' '
       IMPORTING
            filename         = pcfile
       EXCEPTIONS
            inv_winsys       = 1
            no_batch         = 2
            selection_cancel = 3
            selection_error = 4
            OTHERS           = 5.
*-----------------------------start--------------------------------
START-OF-SELECTION.
CLEAR: read_cnt, update_cnt, error_cnt.
REFRESH gt_zgcs_foc.        CLEAR gs_zgcs_foc.
PERFORM file_upload_from_pc.
SORT gt_zgcs_foc.
DELETE ADJACENT DUPLICATES FROM gt_zgcs_foc
         COMPARING COMPANY CUSTOMER PART_CODE REF_NO REF_DATE.
*// customer code check
DATA: LT_ZESTD LIKE ZESTD OCCURS 0 WITH HEADER LINE.
IF NOT gt_zgcs_foc[] IS INITIAL.
    SELECT COMPANY CUSTOMER CURRENCY
      INTO CORRESPONDING FIELDS OF TABLE LT_ZESTD
      FROM ZESTD
       FOR ALL ENTRIES IN gt_zgcs_foc
     WHERE COMPANY = gt_zgcs_foc-COMPANY
       AND CUSTOMER = gt_zgcs_foc-CUSTOMER.
ENDIF.
SORT LT_ZESTD BY COMPANY CUSTOMER.
*// part code check
DATA: LT_MARA LIKE MARA OCCURS 0 WITH HEADER LINE.
IF NOT gt_zgcs_foc[] IS INITIAL.
    SELECT *
      INTO TABLE LT_MARA
      FROM MARA
       FOR ALL ENTRIES IN gt_zgcs_foc
     WHERE MATNR = gt_zgcs_foc-PART_CODE.
ENDIF.
SORT LT_MARA BY MATNR.
LOOP AT gt_zgcs_foc.
*// customer code check
    READ TABLE LT_ZESTD WITH KEY
            COMPANY = gt_zgcs_foc-COMPANY
            CUSTOMER = gt_zgcs_foc-CUSTOMER.
    IF SY-SUBRC <> 0.
      WRITE:/'Invalid Customer code ',
         gt_zgcs_foc-COMPANY, ' ',
         gt_zgcs_foc-CUSTOMER.
      STOP.
    ENDIF.
*// part code check
    READ TABLE LT_MARA WITH KEY MATNR = gt_zgcs_foc-PART_CODE
      BINARY SEARCH.
    IF SY-SUBRC <> 0.
      WRITE:/ 'Invalid part code ', gt_zgcs_foc-PART_CODE.
      STOP.
    ENDIF.
*// REF_NO
    TRANSLATE gt_zgcs_foc-REF_NO     TO UPPER CASE.
    SHIFT gt_zgcs_foc-REF_NO     LEFT DELETING LEADING SPACE.
    IF gt_zgcs_foc-REF_NO = SPACE.
      WRITE:/'Ref No. is blank'.
      STOP.
    ENDIF.
*// REF_DATE
    IF gt_zgcs_foc-REF_DATE = 0.
      WRITE:/'Invalid Ref Date'.
      STOP.
    ENDIF.
*// QTY
*    IF gt_zgcs_foc-QTY CO ' 0123456789'.
*    ELSE.
*      WRITE:/ gt_zgcs_foc-QTY, ' Invalid Qty value'.
*      STOP.
*    ENDIF.
ENDLOOP.
* Insert/Update table
* MODIFY zgcs_foc FROM TABLE gt_zgcs_foc.
INSERT zgcs_foc FROM TABLE gt_zgcs_foc.
IF sy-subrc EQ 0.
    COMMIT WORK.
    DESCRIBE TABLE gt_zgcs_foc LINES update_cnt.
    error_cnt = read_cnt - update_cnt.
ELSE.
    ROLLBACK WORK.
    error_cnt = read_cnt - update_cnt.
ENDIF.
ULINE.
FORMAT COLOR 3.
WRITE: / 'Read count                :', read_cnt.
WRITE: / 'Insert/Update count       :', update_cnt.
WRITE: / 'Error count               :', error_cnt.
FORMAT COLOR OFF.
*end-of-selection--------------------------------------------------
END-OF-SELECTION.
*&      Form FILE_UPLOAD_FROM_PC
FORM file_upload_from_pc.
IF pcfile IS INITIAL.
    WRITE: / 'SELECT UPLOAD FILE !'.
ELSE.
    MOVE pcfile TO v_file.
* HQ file upload
    IF HQfile EQ 'X'.
      CALL FUNCTION 'WS_UPLOAD'
           EXPORTING
                filename                = v_file
                filetype                = 'DAT'
           TABLES
                data_tab                = FOC_inrec
           EXCEPTIONS
                conversion_error        = 1
                file_open_error         = 2
                file_read_error         = 3
                invalid_type            = 4
                no_batch                = 5
                unknown_error           = 6
                invalid_table_width     = 7
                gui_refuse_filetransfer = 8
                customer_error          = 9
                OTHERS                  = 10.
      IF sy-subrc <> 0.
        WRITE: / 'FILE UPLOAD                :', sy-subrc.
      ENDIF.
      LOOP AT FOC_inrec.
        ADD 1 TO read_cnt.
        call function 'CONVERSION_EXIT_ALPHA_INPUT'
             exporting
                  input = FOC_inrec-customer
             importing
                  output = FOC_inrec-customer.
        call function 'CONVERSION_EXIT_ALPHA_INPUT'
             exporting
                  input = FOC_inrec-part_code
             importing
                  output = FOC_inrec-part_code.
        MOVE-CORRESPONDING FOC_inrec TO gs_zgcs_foc.
        MOVE p_comp          TO gs_zgcs_foc-company.
        MOVE gs_zgcs_foc-qty TO gs_zgcs_foc-balan.
        MOVE sy-uname        TO gs_zgcs_foc-ERNAM.
        MOVE sy-datum        TO gs_zgcs_foc-ERDAT.
        MOVE sy-UZEIT        TO gs_zgcs_foc-ERZET.
* Source(1:HQ,2:SUB,0:Etc)
        MOVE '1'             TO gs_zgcs_foc-source.
        APPEND gs_zgcs_foc TO gt_zgcs_foc.
      ENDLOOP.
* SGE file upload
    ELSE.
      CALL FUNCTION 'WS_UPLOAD'
           EXPORTING
                filename                = v_file
                filetype                = 'DAT'
           TABLES
                data_tab                = inrec
           EXCEPTIONS
                conversion_error        = 1
                file_open_error         = 2
                file_read_error         = 3
                invalid_type            = 4
                no_batch                = 5
                unknown_error           = 6
                invalid_table_width     = 7
                gui_refuse_filetransfer = 8
                customer_error          = 9
                OTHERS                  = 10.
      IF sy-subrc <> 0.
        WRITE: / 'FILE UPLOAD                :', sy-subrc.
      ENDIF.
      LOOP AT inrec.
        ADD 1 TO read_cnt.
        call function 'CONVERSION_EXIT_ALPHA_INPUT'
             exporting
                  input = inrec-customer
             importing
                  output = inrec-customer.
        call function 'CONVERSION_EXIT_ALPHA_INPUT'
             exporting
                  input = FOC_inrec-part_code
             importing
                  output = FOC_inrec-part_code.
        MOVE-CORRESPONDING inrec TO gs_zgcs_foc.
        MOVE p_comp          TO gs_zgcs_foc-company.
        MOVE gs_zgcs_foc-qty TO gs_zgcs_foc-balan.
        MOVE sy-uname        TO gs_zgcs_foc-ERNAM.
        MOVE sy-datum        TO gs_zgcs_foc-ERDAT.
        MOVE sy-UZEIT        TO gs_zgcs_foc-ERZET.
* Source(1:HQ,2:SUB,0:Etc)
        MOVE '2'             TO gs_zgcs_foc-source.
        APPEND gs_zgcs_foc TO gt_zgcs_foc.
      ENDLOOP.
    ENDIF.
ENDIF.
ENDFORM.
*MODULE POOL::*
*& Module Name      : Warranty Bill
*& Sub-Module       : W/B
*& Description      : Parts Q'ty Adjust(Sales & Warranty)
*& Program Name     : ZRSWBP004
*& History
*& Date             Author            Reason
*& 2007.05.08       Song, Ji-Hyun     Initial Coding     Req.by WH.Song
*& Logic Process
* - CONDITIONS
*    Company, Customer, Material
* - PROCESS
*    Display,Insert,Update data in the T/B ZESP04
REPORT zrswbp004 NO STANDARD PAGE HEADING
                  MESSAGE-ID 00
                  LINE-SIZE 250
                  LINE-COUNT 50.
*               G L O B A L    V A R I A B L E S                       *
TABLES : zesp04.
DATA : BEGIN OF itab_list OCCURS 0,
        company       LIKE zesp04-company,
        customer      LIKE zesp04-customer,
        material      LIKE zesp04-material,
        adj_date      LIKE zesp04-adj_date,
        adjust        LIKE zesp04-adjust,
        reason        LIKE zesp04-reason,
        reason_code   LIKE zesp04-reason_code,
        doc_no        LIKE zesp04-doc_no,
        in_date       LIKE zesp04-in_date,
        create_id     LIKE zesp04-create_id,
      END OF itab_list.
DATA : itab_upload LIKE TABLE OF zesp04 WITH HEADER LINE.
DATA : s_mode(10).
DATA : table_name(10) VALUE 'ZESP04'.
DATA : tot_cnt TYPE i.
DATA : ref_flag(1).
*               M A C R O    D E F I N E                               *
DEFINE conversion_kunnr.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
       exporting
            input = &1
       importing
            output = &1.
END-OF-DEFINITION.
DEFINE conversion_material.
call function 'CONVERSION_EXIT_MATN1_INPUT'
       exporting
            input = &1
       importing
            output = &1.
END-OF-DEFINITION.
*               S E L E C T I O N   S C R E E N                        *
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE title1.
PARAMETERS     : company LIKE zesp04-company MEMORY ID buk MODIF ID v1
                 OBLIGATORY.
SELECT-OPTIONS : customer   FOR zesp04-customer MEMORY ID kun
                                                MODIF ID v1.
SELECT-OPTIONS : material   FOR zesp04-material MEMORY ID mat
                                                MODIF ID v1.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN POSITION 3.
SELECTION-SCREEN COMMENT 3(12) text-002 MODIF ID v2.
PARAMETERS : up_flag AS CHECKBOX MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(12) text-001 MODIF ID v2.
PARAMETERS : p_fname(300) LOWER CASE MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE title2.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(53) text-003 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(10) text-004 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(12) text-005 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(12) text-006 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(15) text-007 MODIF ID v2.
PARAMETERS : df1 TYPE c RADIOBUTTON GROUP grp1.
SELECTION-SCREEN COMMENT 24(13) text-012 MODIF ID v2.
PARAMETERS : df2 TYPE c RADIOBUTTON GROUP grp1.
SELECTION-SCREEN COMMENT 41(11) text-013 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(14) text-008 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(11) text-009 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(14) text-010 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(10) text-011 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK b2.
INCLUDE zrswbp004_pbo.
INCLUDE zrswbp004_pai.
INITIALIZATION.
title1 = ' Parts Quantity Adjustment '.
title2 = ' Text File Layout '.
*            S T A R T   O F   S E L E C T I O N                       *
TOP-OF-PAGE.
PERFORM write_header.
TOP-OF-PAGE DURING LINE-SELECTION.
PERFORM write_header.
START-OF-SELECTION.
IF up_flag = 'X'.
    PERFORM upload_data.
ELSE.
    PERFORM select_data.
    SET PF-STATUS 'PF01' EXCLUDING 'SAVE'.
    PERFORM display_data.
ENDIF.
AT USER-COMMAND.
PERFORM user_command.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fname.
PERFORM get_filename.
*&      Form SELECT_DATA
*       Select Data for Display
FORM select_data.
SELECT * FROM (table_name)
    INTO CORRESPONDING FIELDS OF TABLE itab_list
   WHERE company = company
     AND customer IN customer
     AND material IN material.
CHECK sy-subrc <> 0.
WRITE: 'No data found with your option.'.
ENDFORM.                    " SELECT_DATA
*&      Form DISPLAY_DATA
*       Display Data following Condition
FORM display_data.
LOOP AT itab_list.
    FORMAT COLOR 2 INTENSIFIED.
    WRITE : / '|' NO-GAP.
    WRITE : (07) itab_list-company    CENTERED   NO-GAP, '|' NO-GAP,
             (10) itab_list-customer   CENTERED   NO-GAP, '|' NO-GAP,
             (20) itab_list-material   CENTERED   NO-GAP, '|' NO-GAP,
             (10) itab_list-adj_date   CENTERED   NO-GAP, '|' NO-GAP,
             (15) itab_list-adjust RIGHT-JUSTIFIED NO-GAP, '|'
NO-GAP,
             (55) itab_list-reason LEFT-JUSTIFIED NO-GAP, '|' NO-GAP,
             (11) itab_list-reason_code CENTERED NO-GAP, '|' NO-GAP,
             (10) itab_list-doc_no      CENTERED NO-GAP, '|' NO-GAP,
             (10) itab_list-in_date CENTERED   NO-GAP, '|' NO-GAP,
             (12) itab_list-create_id CENTERED   NO-GAP, '|' NO-GAP.
    FORMAT INTENSIFIED OFF.
    HIDE itab_list.
ENDLOOP.
WRITE : / sy-uline(171).
ENDFORM.                    " DISPLAY_DATA
*&      Form WRITE_HEADER
*       Write Report Header
FORM write_header.
DATA : line(1024).
CLEAR line WITH '-'.
DESCRIBE TABLE itab_list LINES tot_cnt.
FORMAT INTENSIFIED ON.
WRITE : 15 'Parts Quantity Adjustment'.
SKIP.
WRITE : / 'Total Count : ', tot_cnt.
WRITE : /.
WRITE : (171) sy-uline.
WRITE : / '|' NO-GAP.
WRITE : (07) 'Company' CENTERED   NO-GAP, '|' NO-GAP,
          (10) 'Customer' CENTERED   NO-GAP, '|' NO-GAP,
          (20) 'Material' CENTERED   NO-GAP, '|' NO-GAP,
          (10) 'Adj. Date' CENTERED   NO-GAP, '|' NO-GAP,
          (15) 'Adjust' CENTERED   NO-GAP, '|' NO-GAP,
          (55) 'Reason' CENTERED   NO-GAP, '|' NO-GAP,
          (11) 'Reason Code' CENTERED   NO-GAP, '|' NO-GAP,
          (10) 'Doc No' CENTERED   NO-GAP, '|' NO-GAP,
          (10) 'IN DATE' CENTERED   NO-GAP, '|' NO-GAP,
          (12) 'CREATE ID' CENTERED   NO-GAP, '|' NO-GAP.
WRITE : /(171) sy-uline.
FORMAT INTENSIFIED OFF.
ENDFORM.                    " WRITE_HEADER
*&      Form UPLOAD_DATA
*       Data Upload from File
FORM upload_data.
DATA : l_filename LIKE rlgrap-filename,
         temp_dateformat TYPE dateformat.
IF df1 = 'X'.
    temp_dateformat = 'YYYY.MM.DD'.
ELSE.
    temp_dateformat = 'DD.MM.YYYY'.
ENDIF.
MOVE p_fname TO l_filename.
CHECK l_filename NE space.
CALL FUNCTION 'WS_UPLOAD'
       EXPORTING
            filename                = l_filename
            filetype                = 'DAT'
            dat_d_format            = temp_dateformat
       TABLES
            data_tab                = itab_list
       EXCEPTIONS
            conversion_error        = 1
            file_open_error         = 2
            file_read_error         = 3
            invalid_type            = 4
            no_batch                = 5
            unknown_error           = 6
            invalid_table_width     = 7
            gui_refuse_filetransfer = 8
            customer_error          = 9.
IF sy-subrc NE 0.
    MESSAGE s000 WITH 'File upload is failed!'.
    STOP.
ELSE.
    CLEAR : itab_upload, itab_upload[].
    LOOP AT itab_list.
      MOVE-CORRESPONDING itab_list TO itab_upload.
      conversion_kunnr    itab_upload-customer.
      conversion_material itab_upload-material.
      itab_upload-mandt     = sy-mandt.
      itab_upload-in_date   = sy-datum.
      itab_upload-create_id = sy-uname.
*>>>>Insert by GSCHOI 2007.11.08
      IF itab_list-adj_date+0(6) NE sy-datum+0(6).
        MESSAGE i368 WITH 'Adjust month must same as current month!'.
        ROLLBACK WORK.
        STOP.
      ENDIF.
*<<<<End
      APPEND itab_upload.
      INSERT INTO (table_name) VALUES itab_upload.
      IF sy-subrc EQ 0.
        CONTINUE.
      ELSEIF sy-subrc EQ 4.
        MESSAGE s368 WITH 'Duplicated Data Error!'.
        ROLLBACK WORK.
        STOP.
      ELSE.
        MESSAGE s368 WITH 'File Error!'.
        ROLLBACK WORK.
        STOP.
      ENDIF.
    ENDLOOP.
ENDIF.
IF sy-subrc EQ 0.
    MESSAGE s368 WITH 'Uploaded Successfully!'.
ENDIF.
ENDFORM.                    " UPLOAD_DATA
*&      Form USER_COMMAND
*       User Command Execution in Screen 1000
FORM user_command.
MOVE-CORRESPONDING itab_list TO zesp04.
CASE sy-ucomm.
    WHEN 'INSERT'.
      PERFORM insert_item.
    WHEN 'UPDATE'.
      PERFORM update_item.
    WHEN 'DISPLAY'.
      PERFORM display_item.
    WHEN 'REFRESH'.
      PERFORM refresh_list.
ENDCASE.
IF ref_flag = 'Y'.
    PERFORM refresh_list.
    CLEAR ref_flag.
ENDIF.
ENDFORM.                    " USER_COMMAND
*&      Form INSERT_ITEM
*       When Clicking Insert Button
FORM insert_item.
CLEAR : s_mode.
CLEAR : zesp04.
s_mode = 'INSERT'.
CALL SCREEN '100'.
ENDFORM.                    " INSERT_ITEM
*&      Form UPDATE_ITEM
*       When Clicking Update Button
FORM update_item.
CLEAR : s_mode.
s_mode = 'UPDATE'.
CALL SCREEN '100'.
ENDFORM.                    " UPDATE_ITEM
*&      Form DISPLAY_ITEM
*       When Clicking Display Button
FORM display_item.
CLEAR : s_mode.
s_mode = 'DISPLAY'.
CALL SCREEN '100'.
ENDFORM.                    " DISPLAY_ITEM
*&      Form REFRESH_LIST
*       When Clicking Refresh Button or Returning Display Screen
FORM refresh_list.
CLEAR : itab_list, itab_list[].
PERFORM select_data.
sy-lsind = sy-lsind - 1.
PERFORM display_data.
ENDFORM.                    " REFRESH_LIST
*&      Form GET_FILENAME
*       Get Filename
FORM get_filename.
DATA: l_fname LIKE ibipparms-path .
DATA : p_name LIKE sy-repid.
p_name = sy-repid.
CALL FUNCTION 'F4_FILENAME'
       EXPORTING
            program_name = p_name
            dynpro_number = sy-dynnr
            field_name    = ''
       IMPORTING
            file_name     = l_fname.
p_fname = l_fname.
ENDFORM.                    " GET_FILENAME
Edited by: Matt on Nov 24, 2008 11:24 AM - surrounded the ABAP with tags

Hi,
    Use SUBMIT statement in your first Report zrswbgcs009 at the end, to call the Modulepool program zrswbp004.
do a search in SDN you will get lot of threads on SUBMIT statement with selection screen.
SUBMIT... [VIA SELECTION-SCREEN]
           [USING SELECTION-SET <var>]
           [WITH <sel> <criterion>]
           [WITH FREE SELECTIONS <freesel>]
           [WITH SELECTION-TABLE <rspar>].
http://help.sap.com/saphelp_nw04/Helpdata/EN/9f/dba51a35c111d1829f0000e829fbfe/content.htm
Regards
Bala Krishna

Calling subscreen in module pool

Hi friends,
I am trying to call sub-screen in module pool.
but it is giving me an error as "." or "ID ... FIELD ..." expected after "SUBSCREEN".
i am using followning statement
CALL SUBSCREEN SUB INCLUDING SY-REPID '0101'.
OR
CALL SUBSCREEN SUB. (SUB is screen i have created in layout).
I tried it a lot, but not able to solve it.
Kindly help me.

Hi Kiran,
<li>Subscreen concept is like this. You have one main screen. You want another screen which has to be displayed on main screen when you run main screen.
<li>First we need to create subscreen area on main screen. Goto layout and click subscreen element and place on main screen and name to that subscreen area as SUB.
<li>Now create another screen type subscreen. place fields on that and write logic.
<li> Check REPORT demo_dynpro_subscreens.
Thanks
venkat.O

Is there a user exit called when a module pool program is launch ?

Hello,
I know the exit 'EXIT_SAPLSABE_010' and it's very usefull for adding code before a report is launch.
But this exit is not called when a program is a "Module pool" type.
Is there a way to add my own code before this kind of program is launch ?
Thanks in advance,
Simon
Edited by: Simon Desbonnets on Mar 9, 2010 2:23 PM

Thanks for your answer.
No it's not for initializing values. It's for logging statistics into a specific table (program name, date ...).
The event "load-of-program" can be use for one program, it's not what I'm looking for.
I would like to know if there is an exit that is called each time a module pool program is executed.

Calling webdynpro in module pool screen

Hi All,
I need to display webdynpro application in module pool custom container.
I am using method cl_wd_utilities=>construct_wd_url , then i am using G_HTML_CONTROL->SHOW_URL to show the webdynpro component.
Issue is it is taking to logon screen in module pool and after login, it is working as desired.
Any idea how to suppress this logon screen.
Thanks in advance

Hi,
The SSO needs to be configured.
Also, try the function module WDY_EXECUTE_IN_PLACE, and pass the parameters appropriately.
Integration of Web Dynpro ABAP Applications in GUI Applications - Web Dynpro for ABAP - SAP Library
You can directly create a parameter tcode using WDYID.So that you can call wd applicaiton's tcode directly in gui which launches the application with SSO
Please refer the below link
Single Sign On from SAP GUI to Webdynpro
Hope this helps you.
Regards,
Rama
Message was edited by: Ramakrishnappa Gangappa

Calling infotypes in module pool programming

Hi experts,
I want to guide end user to infotype 2003 using pa30 in dialog programming. I am able to take it to pa30 by 'call transaction' but i want it to directly go to 2003 in pa30 for the same employee.
Need you help please.

Hello Rekha
you can use :
   set parameter 'PER'   <employee number>
   set parameter 'ITP'   '2003'
set parameter 'SUB'   <Subtype>
call transaction 'PA30' skip first screen.
Reward points if helpful

How to write module pool program

hai,
what is the module -pool program ?
what are the procedures to write the module-pool program.
plz give the simple program for module-pool programs?
regards
surender

Hi
This component though is not attached to the screen painter, plays important role in transaction. Normally, for reports, on line executable programs are written but for transaction, Module Pool Programs are written. The module pool program contains only modules to handle various events associated with screen and data declaration statements.
System divides the module pool program into several include program. These are global field, PBO modules, and PAI modules. It is entirely users decision whether to use these modules or write directly into main program.
Creation of Module Pool Program
You can create module pool program either through
Object browser
System automatically creates the module pool program and for these program which are created through object browser, system creates the include modules.
Or
ABAP/4 editor
It is similar to normal program creation. Type of program should be given M and is not created by system.
Communication between Dynpro and Module Program
For each screen, the system executes the flow logic, which contains corresponding events. The control is passed to Module Pool Program. Module Pool Program handles the code for these events and again passes back control to the flow logic and finally to screen. Unlike on line program, in this case, the control remains with flow logic. The switching of control between flow logic and module pool program and back is common process when user executes transaction.
Creation of a Complete Transaction
Steps involved to create a complete transaction
     Create module pool program.
     From screen painter create screens.
     Write flow logic for each screen.
     Write code for all the events in module pool program.
     Check for any error in screen and flow logic.
     Generate each and every component of screen i.e. flow logic and screen.
     Single screen can be tested using Screen Painter.
     Create transaction code through object browser.
     Generate the transaction code.
     User can execute the transaction by entering the transaction code in the command field.
Handling Function Code
The function code or OKCODE is the last field of Field list. Function code can be handled as follows:
During the Designing of the screen, a function code is assigned to pushbutton.
     In field list, developer needs to specify OKCODE as last field.
     In module program it is a global field and can be evaluated in the PAI event.
     A function code is treated in the same way, regardless it comes from pushbutton, menu item or any other GUI element.
When the user clicks on the Display button, you want to display details of sflight, with corresponding carrid and connid (which is entered by the user).
Module pool program to handle this particular screen is as follows:
Program YVTEST7.
TABLES: SFLIGHT.
DATA: OKCODE (4).
MODULE INPUT1 INPUT,
CASE OKCODE.
   WHEN DISP.
     SELECT * FROM SFLIGHT
            WHERE CARRID = SFLIGHT CARRID AND
                           CONNID = SFLIGHT CONNID.
     ENDSELECT.
     LEAVE TO SCREEN 200.
   WHEN EXIT. LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE.               INPUT1 INPUT
MODULE USER_COMMAND_0200 INPUT.
CASE OKCODE.
WHEN BACK. LEAVE TO SCREEN 100.
ENDCASE.
ENDMODULE.                    USER_COMMAND_0200 INPUT
When the user clicks on display, control is transferred to screen no. 200 on which you display sflight details & on the same screen, when user clicks on BACK button, he comes back to main screen.
Flow logic for screen 100 is as follows:
PROCESS AFTER INPUT.
MODULE INPUT.
Flow logic for screen 200
PROCESS AFTER INPUT.
USER_COMMAND_0200.
MODULES: Modules are handled in module pool program.
You need to write flow logic for screen 200 and design screen 200.
In case of transaction transfer of data from program to screen is automatic i.e. you need not transfer the data from program to screen explicitly. The fields, which you define in the screen receives the data from program and displays the same.
The Field Checks
As already mentioned Transaction is the only method, which SAP recommends to update the database tables. Data entered in the database table should be valid and correct. Data entered is validated at each and every point. ABAP/4 offers various methods to validate data and those are as follows:
     Automatic field checks
     Checks performed in the flow logic
     Checks performed in the ABAP/4 module pool program
Automatic Field Checks
These checks are based on the field information stored in the dictionary. These checks are performed by the system automatically when the user enters the data for the screen field. System performs these checks before PAI event is triggered. Types of field checks performed by system are as follows:
     Required input
While designing the screen, for particular screen field if you click the Req. Entry checkbox, the field becomes mandatory. When the transaction is executed if user leaves this particular field blank, the system displays error message. User cannot proceed until the user enters some data.
     Proper Data Format
Each field has its own data format whether it is table field or screen field. Whenever data is entered, system checks for the proper format of the data. For example date. Each user has its own format for date, which is defined in the user master record. If the date defined in the user master record is in the format DD/MM/YYYY, if the user enters the date, say, in YY/DD/MM, the user displays the error message. System also checks for the value of month or days. For example if month entered is greater than twelve then the error message is displayed.
     Valid Value for the Field
In data dictionary two tables are related by Primary key-Foreign key relationship. Whenever the user enters the data, the system checks for the check table values.   Also in Domain, if you have fixed values, then the system checks for these values.
Automatic field checks are repeated each time the user enters the data.
About at Exit Command
Automatic field checks can be avoided by AT EXIT-COMMAND, which works exactly the same way as Cancel works on application tools bar. In the R/3 screen, if you want to quit the processing of that particular screen without entering the mandatory fields, user can click the Cancel button. Same functionality can be incorporated in the user-defined transaction by using AT EXIT-COMMAND. This module can be called before the system executes the automatic field checks and it goes without saying that before PAI event. Code for AT EXIT-COMMAND in flow logic and in module pool program can be written as follows:
In Flow Logic
Process After Input.
Module exit AT EXIT-COMMAND.
         In module pool program.
Module exit.
Case okcode.
When Exit.
Leave to screen 0.
To achieve this kind of functionality a pushbutton or menu item should be assigned a function type E. It tells the system to process this particular module before carrying out any field checks.
Flow Logic Validations
Consider the case where you want user to enter only LH and SQ for sflight-carrid. In this case, you are restricting value of a screen field. This cannot be achieved by automatic field check. Hence there is a need of additional validation. It can be done in flow logic by using following statement:
Field -
Values
Syntax
PAI.
Field sflight-carrid values (LH).
For multiple values
PAI.
Field sflight-carrid values (LH SQ).
Field sflight-price values (between 1000 and 2000).
In this case when the user enters the value, PAI is triggered and field is checked for that particular value. If the value entered happens to be wrong, that field is enabled for user to enter. If you have multiple Field statements in your flow logic, it is sequential execution.
Consider the following case:
PAI.
Module assign.
Field sflight-carrid values (LH SQ).
In ABAP/4
Module assign.
Data: carrid1 like sflight-carrid.
Carrid1 = sflight-carrid.
Endmodule.
In this case, Sflight-carrid is used in the flow logic before the field statement. The system will give invalid value or some previous value as the field sflight-carrid is used in module before it is checked i.e., field statement is after the module in which sflight-carrid is being used. The field is not available to the system unless it executes the field statement. Field statement transfers the values to the program and is done only once. If you dont have Field statement in your flow logic, transfer of values takes place in PAI event.
Consider one more case where you have multiple field statement
PAI.
Field Sflight-carrid values (LH).
Field Sflight-connid values (0400 0500).
In this case if the user enters only carrid wrong, then this particular field is enabled and rest of the fields are disabled for user to input. Many times if the user enters wrong value for one field, then you might want to give option to user to enter all the fields, which is not possible by using Field statement only. This functionality can be achieved by CHAIN ENDCHAIN.
Syntax
Chain.
Field sflight-carrid value (LH).
     Field sflight-connid values (between 200 and 500).
Endchain.
Field sflight-price values (100 1000).
In this case, if the user enters wrong value only for carrid, both the fields i.e. carrid and connid are enabled as they are grouped together in the Chain statement. The field price will be disabled for input. Usually, logically related fields are grouped together with Chain-Endchain statement.
Module Pool Program Validations
Checking fields ABAP/4 program includes
     Field statement in flow logic.
     Module statement in ABAP/4 module pool Program.
Syntax
PAI.
Field sflight-carrid module <name>.
This module can be handled in the main program i.e. module pool program.
In ABAP/4 program
Module Check.
Select single * from sflight where carrid = sflight-carrid.
If sy-subrc ne 0.
     Message e001.
Endif.
In this case, field sflight-carrid is checked in the table for its existence.
Dynamically Calling the Screens
About Displaying Next Screen
Transaction is a sequence of screens, which are displayed one after the other. The next screen displayed depends upon the attributes of first screen. In attributes you need to give Next Screen number i.e. if next screen displayed should be 200 screen, then this number should be given in next Screen attributes. These are static attributes of the screen. By default, if nothing is specified in the program, the system branches out to the screen number, which is specified in the attribute screen.
In this case, if user selects MARA pushbutton, then fields from Mara table are displayed. When the user clicks on the MARD, then the fields from MARD table are displayed. Depending upon users selection, the screen is branched out and this has to be done during runtime. This functionality can be achieved by dynamically calling the screen in module pool program.
The screen can branch out to new screen depending upon user selection. Following command in module pool program can do this:
     SET SCREEM
     CALL SCREEN
     LEAVE TO SCREEN <NUMBER>
All these commands override the specifications given in the attributes. This overriding is temporary. The values stored in the attribute are not changed.
Set Screen
Syntax
Set screen <number>.
In module pool program
Case okcode.
     When DISP.
          Set screen 200.
     When LIST.
          Set screen 300.
Endcase.
In this case, the entire processing of current screen takes place and then the system branches out to next screen. If you want to branch out to the next screen without processing the current screen, LEAVE SCREEN should be used along with the SET SCREEN.
For Example:
Case okcode..
     When DISP.
          Set screen 200.
          Leave Screen.
     When LIST.
          Set screen 300.
          Leave Screen.
Endcase.
When SET SCREEN is used, control cannot be transferred to the main screen or previous screen, unless you write code for the same.
Call Screen
Usually used for pop up screens. Many times, there is a need for user to enter additional information or secondary information on another screen or pop up screen. Once the user enters the data, he should be able to go back to main screen or to the screen where he started. This is not possible by using SET SCREEN. CALL SCREEN achieves this functionality.
Syntax
Call Screen 200.
Will simply call a screen number 200 from a main screen. Once the screen is displayed the user can enter all the data and return to the main screen by clicking BACK button.
To call screen as pop up screen the syntax is
Call screen starting at <col.no.> <line no>
                     Ending at <col no> <line no>.
In this case window will be popped as window and user can close it by using BACK button.
Leave to screen
To SET a new screen without processing current screen, you need to use the following two statements together:
SET SCREEN 200.
LEAVE SCREEN.
Or a Single statement
LEAVE TO SCREEN 200.

Search Help For a Field in Module Pool Programming

Hi,
I have a field called status in Module Pool for which i need to write a search help.
This is the piece of code i have written.
TYPES: BEGIN OF ty_status,
         stat type i,
         status type string,
    END OF ty_status.
DATA: lt_emp_status TYPE STANDARD TABLE OF ty_status,
        lw_emp_status TYPE ty_status.
REFRESH lt_emp_status.
lw_emp_status-stat = '1'.
lw_emp_status-status = 'Draft'.
APPEND lw_emp_status TO lt_emp_status.
CLEAR lw_emp_status.
lw_emp_status-stat = '2'.
lw_emp_status-status = 'Employee Review'.
APPEND lw_emp_status TO lt_emp_status.
CLEAR lw_emp_status.
REFRESH lt_emp_status.
   CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield        = 'STATUS'
      value_org       = 'S'
    TABLES
      value_tab       = lt_emp_status
      return_tab      = t_return
    EXCEPTIONS
      parameter_error = 1
      no_values_found = 2
      OTHERS          = 3.
IF sy-subrc = 0.
    READ TABLE t_return INDEX 1.
    MOVE t_return-fieldval TO LV_EMP_status.
ENDIF.
But i am getting the following error.
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_SY_ASSIGN_CAST_ILLEGAL_CAST', was
not caught in
procedure "F4IF_INT_TABLE_VALUE_REQUEST" "(FUNCTION)", nor was it propagated by
a RAISING clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
The error occurred at a statement of the form
   ASSIGN f TO <fs> CASTING.
   ASSIGN f TO <fs> CASTING TYPE t.
or
   ASSIGN f TO <fs> CASTING LIKE f1.
or
   at table statements with the addition
   ASSIGNING <fs> CASTING.
The following error causes are possible:
1. The type of field f or the target type determined by <fs>, t or f1
contains data references, object references, strings or internal tables
as components.
Could some one help me how to resolve this issue.
Thanks in advance.

Hi,
Please see this sample code below:
*To fetch the classification data on the sel screen
DATA: BEGIN OF IT_KLAH OCCURS 0,
      CLINT TYPE CLINT,
      CLASS TYPE KLASSE_D,
      END OF IT_KLAH.
SELECT CLINT CLASS FROM KLAH UP TO 500 ROWS
INTO TABLE IT_KLAH.
IF SY-SUBRC <> 0 .
    MESSAGE TEXT-006 TYPE 'E'.
ELSE.
    CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
DDIC_STRUCTURE = ' '
    RETFIELD = 'CLASS'
PVALKEY = ' '
    DYNPPROG = SY-REPID
    DYNPNR = SY-DYNNR
    DYNPROFIELD = 'p_s_clascn_low'      "i had to put the f4 help on the selection screen's select option low value,
                                                                 "here basically you have to give the internal table name inside quotes in which
                                                                 "you want to retrieve your data
    VALUE_ORG = 'S'
    DISPLAY = ' '
    TABLES
    VALUE_TAB = IT_KLAH.
ENDIF.
Hope it helps,
Regards,
Mansi

Hi guys please give me sample code for call transaction that handles error

hi guys, please give me sample code for call transaction that handles error,
please send me the sample code in which there should be all decleration part and everything, based on the sample code i will develop my code.
please do help me as it is urgent.
thanks and regards.
prasadnn.

Hi Prasad,
Check this code.
Source Code for BDC using Call Transaction
*Code used to create BDC
*& Report ZBDC_EXAMPLE                                                *
*& Example BDC program, which updates net price of item 00010 of a     *
*& particular Purchase order(EBELN).                                   *
REPORT ZBDC_EXAMPLE NO STANDARD PAGE HEADING
                      LINE-SIZE 132.
Data declaration
TABLES: ekko, ekpo.
TYPES: BEGIN OF t_ekko,
    ebeln TYPE ekko-ebeln,
    waers TYPE ekko-waers,
    netpr TYPE ekpo-netpr,
    err_msg(73) TYPE c,
END OF t_ekko.
DATA: it_ekko TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_ekko TYPE t_ekko,
      it_error TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_error TYPE t_ekko,
      it_success TYPE STANDARD TABLE OF t_ekko INITIAL SIZE 0,
      wa_success TYPE t_ekko.
DATA: w_textout            LIKE t100-text.
DATA: gd_update TYPE i,
      gd_lines TYPE i.
*Used to store BDC data
DATA: BEGIN OF bdc_tab OCCURS 0.
        INCLUDE STRUCTURE bdcdata.
DATA: END OF bdc_tab.
*Used to stores error information from CALL TRANSACTION Function Module
DATA: BEGIN OF messtab OCCURS 0.
        INCLUDE STRUCTURE bdcmsgcoll.
DATA: END OF messtab.
*Screen declaration
SELECTION-SCREEN BEGIN OF BLOCK block1 WITH FRAME
                                    TITLE text-001. "Purchase order Num
SELECT-OPTIONS: so_ebeln FOR ekko-ebeln OBLIGATORY.
SELECTION-SCREEN END OF BLOCK block1.
SELECTION-SCREEN BEGIN OF BLOCK block2 WITH FRAME
                                    TITLE text-002. "New NETPR value
PARAMETERS: p_newpr(14)   TYPE c obligatory. "LIKE ekpo-netpr.
SELECTION-SCREEN END OF BLOCK block2.
*START-OF-SELECTION
START-OF-SELECTION.
Retrieve data from Purchase order table(EKKO)
SELECT ekkoebeln ekkowaers ekpo~netpr
    INTO TABLE it_ekko
    FROM ekko AS ekko INNER JOIN ekpo AS ekpo
      ON ekpoebeln EQ ekkoebeln
   WHERE ekko~ebeln IN so_ebeln AND
         ekpo~ebelp EQ '10'.
*END-OF-SELECTION
END-OF-SELECTION.
Check data has been retrieved ready for processing
DESCRIBE TABLE it_ekko LINES gd_lines.
IF gd_lines LE 0.
Display message if no data has been retrieved
    MESSAGE i003(zp) WITH 'No Records Found'(001).
    LEAVE TO SCREEN 0.
ELSE.
Update Customer master data (instalment text)
    LOOP AT it_ekko INTO wa_ekko.
      PERFORM bdc_update.
    ENDLOOP.
Display message confirming number of records updated
    IF gd_update GT 1.
      MESSAGE i003(zp) WITH gd_update 'Records updated'(002).
    ELSE.
      MESSAGE i003(zp) WITH gd_update 'Record updated'(003).
    ENDIF.
Display Success Report
Check Success table
    DESCRIBE TABLE it_success LINES gd_lines.
    IF gd_lines GT 0.
    Display result report column headings
      PERFORM display_column_headings.
    Display result report
      PERFORM display_report.
    ENDIF.
Display Error Report
Check errors table
    DESCRIBE TABLE it_error LINES gd_lines.
If errors exist then display errors report
    IF gd_lines GT 0.
    Display errors report
      PERFORM display_error_headings.
      PERFORM display_error_report.
    ENDIF.
ENDIF.
*&      Form DISPLAY_COLUMN_HEADINGS
      Display column headings
FORM display_column_headings.
WRITE:2 ' Success Report '(014) COLOR COL_POSITIVE.
SKIP.
WRITE:2 'The following records updated successfully:'(013).
WRITE:/ sy-uline(42).
FORMAT COLOR COL_HEADING.
WRITE:/      sy-vline,
          (10) 'Purchase Order'(004), sy-vline,
          (11) 'Old Netpr'(005), sy-vline,
          (11) 'New Netpr'(006), sy-vline.
WRITE:/ sy-uline(42).
ENDFORM.                    " DISPLAY_COLUMN_HEADINGS
*&      Form BDC_UPDATE
      Populate BDC table and call transaction ME22
FORM bdc_update.
PERFORM dynpro USING:
      'X'   'SAPMM06E'        '0105',
      ' '   'BDC_CURSOR'      'RM06E-BSTNR',
      ' '   'RM06E-BSTNR'     wa_ekko-ebeln,
      ' '   'BDC_OKCODE'      '/00',                      "OK code
      'X'   'SAPMM06E'        '0120',
      ' '   'BDC_CURSOR'      'EKPO-NETPR(01)',
      ' '   'EKPO-NETPR(01)' p_newpr,
      ' '   'BDC_OKCODE'      '=BU'.                      "OK code
Call transaction to update customer instalment text
CALL TRANSACTION 'ME22' USING bdc_tab MODE 'N' UPDATE 'S'
         MESSAGES INTO messtab.
Check if update was succesful
IF sy-subrc EQ 0.
    ADD 1 TO gd_update.
    APPEND wa_ekko TO it_success.
ELSE.
Retrieve error messages displayed during BDC update
    LOOP AT messtab WHERE msgtyp = 'E'.
    Builds actual message based on info returned from Call transaction
      CALL FUNCTION 'MESSAGE_TEXT_BUILD'
           EXPORTING
                msgid               = messtab-msgid
                msgnr               = messtab-msgnr
                msgv1               = messtab-msgv1
                msgv2               = messtab-msgv2
                msgv3               = messtab-msgv3
                msgv4               = messtab-msgv4
           IMPORTING
                message_text_output = w_textout.
    ENDLOOP.
Build error table ready for output
    wa_error = wa_ekko.
    wa_error-err_msg = w_textout.
    APPEND wa_error TO it_error.
    CLEAR: wa_error.
ENDIF.
Clear bdc date table
CLEAR: bdc_tab.
REFRESH: bdc_tab.
ENDFORM.                    " BDC_UPDATE
      FORM DYNPRO                                                   *
      stores values to bdc table                                    *
--> DYNBEGIN                                                      *
--> NAME                                                          *
--> VALUE                                                         *
FORM dynpro USING    dynbegin name value.
IF dynbegin = 'X'.
    CLEAR bdc_tab.
    MOVE: name TO bdc_tab-program,
           value TO bdc_tab-dynpro,
           'X' TO bdc_tab-dynbegin.
    APPEND bdc_tab.
ELSE.
    CLEAR bdc_tab.
    MOVE: name TO bdc_tab-fnam,
           value TO bdc_tab-fval.
    APPEND bdc_tab.
ENDIF.
ENDFORM.                               " DYNPRO
*&      Form DISPLAY_REPORT
      Display Report
FORM display_report.
FORMAT COLOR COL_NORMAL.
Loop at data table
LOOP AT it_success INTO wa_success.
    WRITE:/      sy-vline,
            (10) wa_success-ebeln, sy-vline,
            (11) wa_success-netpr CURRENCY wa_success-waers, sy-vline,
            (11) p_newpr, sy-vline.
    CLEAR: wa_success.
ENDLOOP.
WRITE:/ sy-uline(42).
REFRESH: it_success.
FORMAT COLOR COL_BACKGROUND.
ENDFORM.                    " DISPLAY_REPORT
*&      Form DISPLAY_ERROR_REPORT
      Display error report data
FORM display_error_report.
LOOP AT it_error INTO wa_error.
    WRITE:/      sy-vline,
            (10) wa_error-ebeln, sy-vline,
            (11) wa_error-netpr CURRENCY wa_error-waers, sy-vline,
            (73) wa_error-err_msg, sy-vline.
ENDLOOP.
WRITE:/ sy-uline(104).
REFRESH: it_error.
ENDFORM.                    " DISPLAY_ERROR_REPORT
*&      Form DISPLAY_ERROR_HEADINGS
      Display error report headings
FORM display_error_headings.
SKIP.
WRITE:2 ' Error Report '(007) COLOR COL_NEGATIVE.
SKIP.
WRITE:2 'The following records failed during update:'(008).
WRITE:/ sy-uline(104).
FORMAT COLOR COL_HEADING.
WRITE:/      sy-vline,
          (10) 'Purchase Order'(009), sy-vline,
          (11) 'Netpr'(010), sy-vline,
          (73) 'Error Message'(012), sy-vline.
WRITE:/ sy-uline(104).
FORMAT COLOR COL_NORMAL.
ENDFORM.                    " DISPLAY_ERROR_HEADINGS
Hope this resolves your query.
Reward all the helpful answers.
Regards

Caling smart form from module pool

Hi,
i want to call smartform from module pool screen when click on some pushbutton.
ex i want to call smart form of sales order by passing perticular S.O number from module pool screen.
plz help me o get this.
thanks.

Hi,
Enable hotspot option in the field catalog for the .SO.NUMBER field. On clicking on SO.Number
get the cursor field value and call the smart form in the PAI (ie., in user_command module).
Probably pick ucomm triggers with hotspot.
Venkat.

RE-FX:call transaction using bdc-tab:No bdc_okcode for swapping table-entry

Hello,
I am trying to call transaction RERAOP (module RE-FX) to make an accounting transaction. There is 1 debit posting and 1 credit posting in a grid. Selecting the debit posting, a details scrren is shown, consisting of 2 registers.
On the first register you have to fill different fields. At this point it isn't possible to select the second register. The second (credit) posting is diplayed when you hit the enter key. After the fields in the details screen of this (credit) postings have been filled, it is possible to swap back to the first (debit) posting with a double-click on the first entry of the postings-table.
Finally I come to the point ...
If I record these steps (batch-input recorder) and generate an report of this code there is no bdc_okcode for the above mentioned swap back to the debit posting. While executing this report I get a lot of error message because the swap back to the debit posting doesn't work (--> because of the missing bdc_okcode) and therefore the batch input tries to fill fields which are not on the active screen (because they are on the 2. register which is not displayed).
Hope that there is someone out there who:
1. Understands my miserable english and
2. has an advice for me.
Thanks in advance!!!
Stephan
Edited by: Stephan Scholze on Apr 22, 2008 1:34 PM
Edited by: Stephan Scholze on Apr 22, 2008 2:24 PM
Edited by: Stephan Scholze on Apr 22, 2008 3:19 PM

Not sure how much I can help as we don't run RE-FX (RERAOP - what's the program name btw?) at any sites I work at, but a couple of general BDC things you might try (based on problems I've had with BDCs to other Tcodes)...
When you are in that transaction normally do a right click to see what function codes are defined as there might be one there that allows you to switch between these debit & credit data entry places (how are they rendered, btw - are they ALV grids or what? If they are table controls then you should be able to position the cursor on row 1 and trigger an F2 double-click)... also look at the PF-STATUS carefully in case (once again) there is a function code that lets you swap from DR to CR & vice versa... and even browse the source code in the user-command for the screen might give a clue as to how to achieve this. Of course it may not be possible if the data entry is control based i.e. the input areas are provided in the SAPGui not the application server (such as the text editor & ALV grids)... in which case you start hunting for BAPIs and function modules and the like, or end up having to pass data into the transaction via something like an "export" and catch it inside a user exit or enhancement via an "import"... all rather messy, but quite possible.
Jonathan

Call module pool without a transaction

Hi people,
I want to know if there is any way to call a Module Pool program without having a transaction.
I heard about a function, but I can't find.
I need this just to test my program before ask for a transaction.
Tks

I don't think we can do this with our creating transaction code.
Thanks,
Naveen.I

Calling a report from Module Pool

While calling a report from the module pool I'm not able to display th alv. The skeleton of the ALV is coming. But the data and headings are also not displayed.
But where as calling the same program from a report it is coming properly. can somebody please guide me where did I go wrong?

MODULE user_command_1001 INPUT.
w_ok_code = ok_code.
CLEAR ok_code.
CASE w_ok_code.
    WHEN 'BACK'.
      LEAVE PROGRAM .
    WHEN 'CREATE'.
      CALL TRANSACTION 'Z_FIRST_TIME'.
    WHEN 'SYNC'.
      CALL TRANSACTION 'Z_SYNC'.
    WHEN 'APPROVE'.
     SUBMIT zds_xx_approval_status WITH po_aname EQ sy-uname AND RETURN.
    WHEN 'OVERVIEW'.
      PERFORM show_all_reqids.
ENDCASE.
ENDMODULE.

Call transaction in module pool

Similar Messages

Maybe you are looking for