Unable to disable input field in modal dialog box

Hi All, I have a screen typed modal dialog box with a table control.
I want to disable field input in the table control when some conditions meet.
I write the following code in the PBO, but it's not working. The group1 has been set.
LOOP AT SCREEN.
       IF screen-group1 = 'DSP'.
         screen-input = 0.
         MODIFY SCREEN.
       ENDIF.
ENDLOOP.
Would anyone help me? Thanks in advance!

Hi,
Loop over table control and then modify the table control. Check the below threads for reference:
enble / disable table control column at runtime.
Table Control Enable / Disable Row | SCN
Table Control  Fields Disable. | SCN
hope this helps u,
Regards,
Kiran

Similar Messages

  • Saerch help for Date field on Modal Dialog box

    Hi ,
    I have made a screen of Modal Dialog box type . I have one date field on that screen . I have given datatype datum to that field but the serch help for that field is not coming . There is no search help for that field .. Please help..
    Thanks in advance....

    hi,
    in the pop up box for that field just checjk whether the data type is date.

  • Unable to close Modal dialog box

    Hello Friends,
    I am displaying a list in a Modal Dialog box. When I try to close the Modal dialog box. It is not getting closed.I have defined a gui status for this modal dialog box. PBO and PAI Coding is given below .
    module STATUS_0300 output.
      SET PF-STATUS 'STATUS_300'.
    SUPPRESS DIALOG.
      LEAVE TO LIST-PROCESSING AND RETURN TO SCREEN 0 .
      IF p_week IS NOT INITIAL.
        WRITE : text-009 COLOR 1.
      ENDIF.
      IF p_month IS NOT INITIAL.
        WRITE : text-010 COLOR 1.
      ENDIF.
      LOOP AT g_t_wkmon_error INTO g_s_wkmon_error.
        WRITE :/ g_s_wkmon_error-matnr,
                 g_s_wkmon_error-period,
                 g_s_wkmon_error-quantity.
      ENDLOOP.
    LEAVE SCREEN.
    endmodule.  
    module USER_COMMAND_0300 input.
    CASE ok_code.
      WHEN 'OK'.
       LEAVE PROGRAM.
    ENDCASE.
    endmodule. 
    Thanks in Advance.
    Hari

    Hi,
    Check the below thread
    Re: Unable to close modal dialog box
    " Make sure you select the Radio Button DIalog BOX Typ while creating the Status in PBO
    You can use SET SCREEN 0 In the above Thread
    MODULE user_command_0100 INPUT.
      CASE ok.
        when 'CANCEL'. " You Standard GUI options shown in The GUI Screen
          SET SCREEN 0.
      ENDCASE.
    ENDMODULE.                 " USER_COMMAND_0100  INPUT
    module STATUS_0100 output.
    SET PF-STATUS 'ABC'. " This is of type Dailog Box type
    *  SET TITLEBAR 'xxx'.
    endmodule.                 " STATUS_0100  OUTPUT
    Hope this would resolve your Issue.
    Cheerz
    Ram
    Edited by: Ramchander Krishnamraju on Apr 16, 2010 1:16 PM

  • Blocking application input without a modal dialog

    Hi,
    Is it possible to block all input to a Swing application while still having the EDT running? I'd want the effect of opening a modal dialog without showing the dialog itself. This is required in order to wait for a SwingWorker thread to execute.
    The API documentation of SwingWorker.get() states that "When you want the SwingWorker to block on the Event Dispatch Thread we recommend that you use a modal dialog." However, I'm using a ProgressMonitor to monitor the progress of the worker which opens its own dialogs, so I don't want any other extra dialogs popping up. If the EDT simply waits for the worker, the ProgressMonitor dialog pops up but does not paint itself.
    I guess it might be possible to open an modal dialog that is invisible, but it probably can't be guaranteed to be invisible in all environments and not to show up in window lists.
    Is this possible using the normal API, or do I need to duplicate the functionality of ProgressMonitor using an always-open modal dialog (which would seem like quite a waste of code)?
    Also, is there any method that could be called at intervals and which would handle any pending EDT events? I've seen this in some other toolkits (for example GTK+), and it would simplify working in the EDT a lot.

    Thanks for the comments. Especially the page about the disabled glass pane summarized both methods well.
    However, my application may have sevelar application panes and dialogs open that modify the document. Disabling and re-enabling all of them manually would be quite a hassle. Unless somebody can give instructions on replicating the disabling effect of a modal dialog, I guess there are two possibilities left:
    1. Using a modal dialog that opens always, even for short tasks.
    2. Re-implementing the functionality of ProgressMonitor and blocking the EDT for the 0.5 - 1 seconds while it evaluates whether the task is long enough to open the dialog or not.

  • How to remove the default icons from the toolbar of modal dialog box screen

    Hello Friends,
    Iam calling a screen from function module using CALL SCREEN statement.
    The screen is of type Modal Dialog Box. I created some input fields and buttons in the screen. When the screen is displayed, I can see the tool bar at the bottom along with the input fields and buttons in the screen.
    These icons are Continue(Enter), Check, Cancel. How can I supress this??
    I mean in my screeen I want only my input fields and buttons but not the default toolbar. How to do that?
    Regards,
    Raju

    Hi Raju,
    Try this...
    First try to capture the F-codes of ur button apppearing on the dialog box and then exclude it from the PF-status by passing it to itab.
    types: begin of tab_type,
            fcode like rsmpe-func,
           end of tab_type.
    data: tab type standard table of tab_type with
                   non-unique default key initial size 10,
          wa_tab type tab_type.
    clear tab.
    move 'DELE' to wa_tab-fcode.
    append wa_tab to tab.
    move 'PRIN' to wa_tab-fcode.
    append wa_tab to tab.
    set pf-status 'STA3' excluding tab.
    Cheers,
    Simha.
    Reward all the helpful answers..

  • Screen sequence processing when using modal dialog box

    I have been struggling with a dialog program which I have written.  I have a screen which has 2 radiobuttons and a check box (screen 100).  If the checkbox is marked, a modal dialog screen pops up (screen  150).  If I complete both input fields on  screen 150, I can go through to screen 200, then back out of screen 200 to screen 100, and then I can back out 100 to screen 0.
    The problem I have is the validation I have put in screen 150 if one or both input fields have no values or if I want to exit screen 150.  If I exit screen 150, in order to get back to screen 100 in the main screen I need to do CALL SCREEN 100 as if I use SET SCREEN 100, 100 then appears in my modal dialog box screen.
    If I try to back out of screen 100 to screen 0, the program then brings up screen 150 in the PAI part of the module and then go to screen 0 when I close screen 150 even though I have coded SET SCREEN 0. LEAVE SCREEN. in the user command module of screen 100.  Here is my code:
    <u><b>screen 100</b></u>
    PROCESS BEFORE OUTPUT.
      MODULE status_0100.
    PROCESS AFTER INPUT.
      MODULE user_command_0100.
    <b>
    <u>Modules for 100</u></b>
    *&      Module  STATUS_0100  OUTPUT
    *       text
    MODULE status_0100 OUTPUT.
      SET PF-STATUS 'ZL_PWB_GR1'.
      SET TITLEBAR  'ZL_PWB_GR1'.
      CLEAR: w_hse_stock, w_new_product, wa_sto, w_reverse,
             mara-matnr,  mkpf-mblnr.
      PERFORM release_lock.
      REFRESH CONTROL 'TC_GR' FROM SCREEN 0200.
    ENDMODULE.                 " STATUS_0100  OUTPUT
    *&      Module  USER_COMMAND_0100  INPUT
    *       text
    MODULE user_command_0100 INPUT .
      CASE ok_code.
        WHEN 'ENTER'.
          IF w_reverse = space.
            CALL SCREEN 0200.
          ELSE.
            CALL SCREEN 0150 STARTING AT 30 2
                             ENDING AT   75 5.
          ENDIF.
        WHEN 'BACK' OR 'EXIT' OR 'CANC'.
          w_pai = c_yes.
          SET SCREEN 0.
          LEAVE SCREEN.
      ENDCASE.
    ENDMODULE.                 " USER_COMMAND_0100  INPUT
    <u><b>screen 150</b></u>
    PROCESS BEFORE OUTPUT.
      MODULE status_0150.
    PROCESS AFTER INPUT.
      MODULE exit_command_0150 AT EXIT-COMMAND.
      FIELD  mara-matnr MODULE check_matnr.
      FIELD  mkpf-mblnr MODULE check_art_doc.
    <u><b>Modules for 150</b></u>
      MODULE user_command_0150.
    *&      Module  STATUS_0150  OUTPUT
    *       text
    MODULE status_0150 OUTPUT.
      SET PF-STATUS 'GR_REV'.
      SET TITLEBAR 'GR_REV'.
    ENDMODULE.                 " STATUS_0150  OUTPUT
    *&      Module  exit_COMMAND_0150  INPUT
    *       text
    MODULE exit_command_0150 INPUT.
      IF sy-ucomm = 'EXIT'.
        CALL SCREEN 100.
      ENDIF.
    ENDMODULE.                 " exit_COMMAND_0150  INPUT
    *&      Module  check_matnr  INPUT
    *  Check if issues has been filled and if issue is a valid article no.
    MODULE check_matnr INPUT.
      DATA: l_matnr TYPE matnr.
      IF mara-matnr IS INITIAL.
        MESSAGE i010(ad) WITH 'Issue no. required'.
        EXIT.
      ELSE.
        SELECT SINGLE matnr FROM mara INTO l_matnr
         WHERE matnr = mara-matnr.
        IF sy-subrc NE 0.
          CLEAR l_matnr.
          MESSAGE i010(ad) WITH 'Issue does not exist'.
        ENDIF.
      ENDIF.
    ENDMODULE.                 " check_matnr  INPUT
    *&      Module  check_art_doc  INPUT
    *       text
    MODULE check_art_doc INPUT.
      IF mkpf-mblnr IS INITIAL.
        MESSAGE i010(ad) WITH 'Article document no. required'.
        EXIT.
      ELSE.
        PERFORM get_art_doc USING mara-matnr
                                  mkpf-mblnr.
        IF sy-subrc NE 0.
          MESSAGE i010(ad) WITH 'No article document exists for this issue'.
        ENDIF.
      ENDIF.
    ENDMODULE.                 " check_art_doc  INPUT
    *&      Module  USER_COMMAND_0150  INPUT
    *       text
    MODULE user_command_0150 INPUT.
      CASE sy-ucomm.
        WHEN 'ENTE'.
          IF mara-matnr NE space AND mkpf-mblnr NE space.
            CALL SCREEN 200.
          ELSE.
    *        MESSAGE i010(ad) WITH 'Please fill in both fields'.
            SET SCREEN 150.
          ENDIF.
      ENDCASE.
    ENDMODULE.                 " USER_COMMAND_0150  INPUT
    Any suggestions or pointers would be greatly appreciated as I am going round in circles.
    Thanks
    Larissa

    Have got around this by removing the references to SET SCREEN 150.  This way, I can get around the screen sequencing.  It just means that I cannot keep my screen 150 in view if a validation message occurs but for now it will do for what I need.
    Thank you for your help anyway.
    Larissa

  • Is it possible to call a subscreen/modal dialog box from the global class

    Hi,
    Is it possible to call a subscreen or modal dialog box from the global class ..
    or is there any option to display a pop screen or subscreen in order to get the values from user which as to be implemented
    in the global class..
    thanks and regards,
    Poornima.

    Hi Poornima,
    you should follow Uwe's suggestion. The only alternative I can imagine is dynamic document in a dialog container. But I don't know any standardized classes to make use with minimum effort. Have a look at report DD_ADD_FORM_INPUT. Here they put the input field in a container control in a screen; you can put the container control on a dialog container (CL_GUI_DIALOGBOX_CONTAINER).
    We will not get rid of any screen for the time being, but if your application is started from any screen, the DIALOGBOX_CONTAINER can start from there.
    Regards,
    Clemens

  • Problem in modal dialog box

    Hello,
    I've created a function which call a modal dialog box. In this one, the user has to choose a value in a listbox. It's like a popup for the user.
    The screen is called like below:
    CALL SCREEN 0500 STARTING AT 5 5
                       ENDING   AT 100 10.
    The screen is defined with a pf-status containing only one icon(pf-key) with value VALID. In the process after input, I'm controlling the value like below:
    MODULE USER_COMMAND_0500 INPUT.
    data : save_ok like sy-ucomm.
    save_ok = lv_code.
      case save_ok.
        when  'VALID'.
          if lv_prio(2) lt 4.
            message s098(ze).
          else.
            set screen 0.
            leave screen.
          endif.
        when others.
        message s098(ze).
      endcase.
    ENDMODULE.                 " USER_COMMAND_0500  INPUT
    I have a bug when the program is calling twice the function means the popup.
    Instance of program Z.
    loop at X.
       call function YY.......
    endloop.
    The table X contain two values.
    When the popup is called the first time in the loop, all is ok, but when the popup is called the next time, if the user doesn't choose a value in the listbox and just press on the keyboard Enter, then the system go completly out of the program Z and doesn't go in the user_command !!!!
    I've defined the field (listbox) as required, but no effect.
    Is it a bug of the system ? or do I defined the screen incorrectly or ???
    Thanks a lot for your help.

    Hi merle,
    i  have u debugged the program ?  Is it coming to user-command event ?
    What is the type of this field lv_prio ?
    comment set screen 0  & use leave to screen 0
    if lv_prio(2) lt 4.
    message s098(ze).
    else.
    leave to screen 0.
    endif.

  • ALV in modal dialog box

    Hi,
    I have an ALV on suppose screen 3000, I have created a button in the tool bar to call another ALV, but my question is, can we display ALV in modal dialog box screen(because the requirement is to display ALV as a popup)
    So when i changed the screen type to normal screen, my alv is coming,,but when i change the screen type to modal dialog box, then no ALV is being displayed in the output. Only blank screen is displayed.
    Can you please help me.
    Thanks.

    Hello
    The problem is that you have to take into account that the ALV in the popup (or modal dialogbox) is displayed on a different screen level:
    level 0 = main screen
    level 1 = 1st popup
    level 2 = 2nd popup
    We have up to 9 screen level available.
    The following sample report ZUS_SDN_ALV_IN_POPUP is a variant of my sample report ZUS_SDN_TWO_ALV_GRIDS.
    Depending on whether you mark P_POPUP or not the second ALV grid is additionally displayed on a popup.
    *& Report  ZUS_SDN_ALV_IN_POPUP
    *& Thread: ALV in modal dialog box
    *& https:||<a class="jive_macro jive_macro_thread" href="" __jive_macro_name="thread" modifiedtitle="true" __default_attr="762642"></a>
    *& Screen '0100' contains no elements.
    *& ok_code -> assigned to GD_OKCODE
    *& Flow logic:
    *  PROCESS BEFORE OUTPUT.
    *    MODULE STATUS_0100.
    *  PROCESS AFTER INPUT.
    *    MODULE USER_COMMAND_0100.
    REPORT  zus_sdn_alv_in_popup.
    TYPE-POOLS: abap.
    DATA:
      gd_okcode        TYPE ui_func,
      gd_repid         TYPE syst-repid,
    " containers and ALV grids for main screen
      go_docking       TYPE REF TO cl_gui_docking_container,
      go_splitter      TYPE REF TO cl_gui_splitter_container,
      go_cell_top      TYPE REF TO cl_gui_container,
      go_cell_bottom   TYPE REF TO cl_gui_container,
      go_grid1         TYPE REF TO cl_gui_alv_grid,
      go_grid2         TYPE REF TO cl_gui_alv_grid,
    " container and ALV grid for popup
      go_docking3      TYPE REF TO cl_gui_docking_container,
      go_grid3         TYPE REF TO cl_gui_alv_grid,
      gs_layout        TYPE lvc_s_layo.
    DATA:
      gt_knb1          TYPE STANDARD TABLE OF knb1,
      gt_knvv          TYPE STANDARD TABLE OF knvv.
    PARAMETERS:
      p_popup AS CHECKBOX DEFAULT ' '.
    *       CLASS lcl_eventhandler DEFINITION
    CLASS lcl_eventhandler DEFINITION.
      PUBLIC SECTION.
        CLASS-METHODS:
          handle_double_click FOR EVENT double_click OF cl_gui_alv_grid
            IMPORTING
              e_row
              e_column
              es_row_no
              sender.
    ENDCLASS.                    "lcl_eventhandler DEFINITION
    *       CLASS lcl_eventhandler IMPLEMENTATION
    CLASS lcl_eventhandler IMPLEMENTATION.
      METHOD handle_double_click.
    *   define local data
        DATA:
          ls_knb1      TYPE knb1.
        CHECK ( sender = go_grid1 ).
        READ TABLE gt_knb1 INTO ls_knb1 INDEX e_row-index.
        CHECK ( ls_knb1-kunnr IS NOT INITIAL ).
        IF ( p_popup = abap_true ).
          CALL METHOD cl_gui_cfw=>set_new_ok_code
            EXPORTING
              new_code = 'POPUP'
    *        IMPORTING
    *          rc       =
        ELSE.
    *     Triggers PAI of the dynpro with the specified ok-code
    *  *    CALL METHOD cl_gui_cfw=>set_new_ok_code( 'DETAIL' ).  " not on 4.6c
          CALL METHOD cl_gui_cfw=>set_new_ok_code
            EXPORTING
              new_code = 'DETAIL'
    *        IMPORTING
    *          rc       =
        ENDIF.
      ENDMETHOD.                    "handle_double_click
    ENDCLASS.                    "lcl_eventhandler IMPLEMENTATION
    START-OF-SELECTION.
    " Select data
      SELECT        * FROM  knb1 INTO TABLE gt_knb1
             WHERE  bukrs  = '1000'.
      PERFORM init_controls.
    * Display data
      gs_layout-grid_title = 'Customers'.
      CALL METHOD go_grid1->set_table_for_first_display
        EXPORTING
          i_structure_name = 'KNB1'
          is_layout        = gs_layout
        CHANGING
          it_outtab        = gt_knb1
        EXCEPTIONS
          OTHERS           = 4.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      gs_layout-grid_title = 'Customers Details (Sales Areas)'.
      CALL METHOD go_grid2->set_table_for_first_display
        EXPORTING
          i_structure_name = 'KNVV'
          is_layout        = gs_layout
        CHANGING
          it_outtab        = gt_knvv  " empty !!!
        EXCEPTIONS
          OTHERS           = 4.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      gs_layout-grid_title = 'Customers Details (Sales Areas)'.
      CALL METHOD go_grid3->set_table_for_first_display
        EXPORTING
          i_structure_name = 'KNVV'
          is_layout        = gs_layout
        CHANGING
          it_outtab        = gt_knvv  " empty !!!
        EXCEPTIONS
          OTHERS           = 4.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * Link the docking container to the target dynpro
      gd_repid = syst-repid.
      CALL METHOD go_docking->link
        EXPORTING
          repid                       = gd_repid
          dynnr                       = '0100'
    *      CONTAINER                   =
        EXCEPTIONS
          OTHERS                      = 4.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * Link the docking container to the popup
      gd_repid = syst-repid.
      CALL METHOD go_docking3->link
        EXPORTING
          repid                       = gd_repid
          dynnr                       = '0200'
    *      CONTAINER                   =
        EXCEPTIONS
          OTHERS                      = 4.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * NOTE: dynpro does not contain any elements
      CALL SCREEN '0100'.
    * Flow logic of dynpro (does not contain any dynpro elements):
    *PROCESS BEFORE OUTPUT.
    *  MODULE STATUS_0100.
    *PROCESS AFTER INPUT.
    *  MODULE USER_COMMAND_0100.
    END-OF-SELECTION.
    *&      Form  INIT_CONTROLS
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM init_controls .
    * Create docking container
      CREATE OBJECT go_docking
        EXPORTING
          parent = cl_gui_container=>screen0  " main screen -> level 0 !!!
          ratio  = 90
        EXCEPTIONS
          OTHERS = 6.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * Create splitter container
      CREATE OBJECT go_splitter
        EXPORTING
          parent            = go_docking
          rows              = 2
          columns           = 1
    *      NO_AUTODEF_PROGID_DYNNR =
    *      NAME              =
        EXCEPTIONS
          cntl_error        = 1
          cntl_system_error = 2
          OTHERS            = 3.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * Get cell container
      CALL METHOD go_splitter->get_container
        EXPORTING
          row       = 1
          column    = 1
        RECEIVING
          container = go_cell_top.
      CALL METHOD go_splitter->get_container
        EXPORTING
          row       = 2
          column    = 1
        RECEIVING
          container = go_cell_bottom.
    * Create ALV grids
      CREATE OBJECT go_grid1
        EXPORTING
          i_parent = go_cell_top
        EXCEPTIONS
          OTHERS   = 5.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * Set event handler
      SET HANDLER: lcl_eventhandler=>handle_double_click FOR go_grid1.
      CREATE OBJECT go_grid2
        EXPORTING
          i_parent = go_cell_bottom
        EXCEPTIONS
          OTHERS   = 5.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      " Create container and grid for popup.
    * Create docking container
      CREATE OBJECT go_docking3
        EXPORTING
          parent = cl_gui_container=>screen1 " !!! popup !!!
          ratio  = 90
        EXCEPTIONS
          OTHERS = 6.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      " NOTE: Starting from a main dynpro (screen level 0) the first popup
      "       (or modal dialogbox) is on level 1 !!!
      " Using cl_gui_container=>screen0 fails to display ALV grid.
      CREATE OBJECT go_grid3
        EXPORTING
          i_parent = go_docking3
        EXCEPTIONS
          OTHERS   = 5.
      IF sy-subrc <> 0.
    *   MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *              WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " INIT_CONTROLS
    *&      Module  STATUS_0100  OUTPUT
    *       text
    MODULE status_0100 OUTPUT.
      SET PF-STATUS 'STATUS_0100'.  " contains push button "DETAIL"
    *  SET TITLEBAR 'xxx'.
    * Refresh display of detail ALV list
      CALL METHOD go_grid2->refresh_table_display
    *    EXPORTING
    *      IS_STABLE      =
    *      I_SOFT_REFRESH =
        EXCEPTIONS
          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.
    ENDMODULE.                 " STATUS_0100  OUTPUT
    *&      Module  USER_COMMAND_0100  INPUT
    *       text
    MODULE user_command_0100 INPUT.
      CASE syst-dynnr.
        WHEN '0100'.
          CASE gd_okcode.
            WHEN 'BACK' OR
                 'END'  OR
                 'CANC'.
              SET SCREEN 0. LEAVE SCREEN.
    *   User has pushed button "Display Details"
            WHEN 'DETAIL'.
              PERFORM entry_show_details.
            WHEN 'POPUP'.
              PERFORM entry_show_details.
              go_grid3->refresh_table_display( ). " required
              CALL SCREEN '0200' STARTING AT 5 5
                                 ENDING   AT 150 30.
            WHEN OTHERS.
          ENDCASE.
        WHEN '0200'.
          set screen 100. leave screen.
      ENDCASE.
      CLEAR: gd_okcode.
    ENDMODULE.                 " USER_COMMAND_0100  INPUT
    *&      Form  ENTRY_SHOW_DETAILS
    *       text
    *  -->  p1        text
    *  <--  p2        text
    FORM entry_show_details .
    * define local data
      DATA:
        ld_row      TYPE i,
        ls_knb1     TYPE knb1.
      CALL METHOD go_grid1->get_current_cell
        IMPORTING
          e_row = ld_row.
      READ TABLE gt_knb1 INTO ls_knb1 INDEX ld_row.
      CHECK ( syst-subrc = 0 ).
      SELECT        * FROM  knvv INTO TABLE gt_knvv
             WHERE  kunnr  = ls_knb1-kunnr.
    ENDFORM.                    " ENTRY_SHOW_DETAILS
    Regards
      Uwe

  • Calling Selection Screen in Modal dialog box

    Hi Experts.
    I have created screen 9000 having user interface and in tool bar there is create button in the screen 9000
    The create button 9001 will call another screen with different I/O fields (9001 is Modal dialog screen).
    In the 9001 there is push button for which the selection screen is called 9002.
    I have declared 9002 as subscreen and called the screen 9002 in user command.
    In the Screen 9001 when user clicks the push button i need to get pop up screen where the user select some data.
    How i need to do ?
    I am getting error can't call subscreen in modal dialog box.
    Thanks,
    ERPSAP

    HI,
    HOpe this will help you
    How to call table control in subscreen in module pool program
    http://sap.ittoolbox.com/groups/technical-functional/sap-dev/reg-tab-strip-control-module-pool-abap-444944
    http://12go.com/sap/search?query=title%3A(calling%20subscreens%20in%20module%20pool)
    Regards,
    Pravin

  • How to set width for this modal dialog box?

    Hi All,
    How to set width to this modal dialog box:
    <input id="btnVote" onclick="javascript:SP.UI.ModalDialog.showModalDialog({ url: &#39;../Lists/Sports%20Activities%20Voting/NewForm.aspx&#39;, title: &#39;User Survey&#39;}); return false;" type="button" value="Vote"/>
    Thanks in advance!

    set as bellow:
    <input id="btnVote" onclick="javascript:SP.UI.ModalDialog.showModalDialog({ url: &#39;../Lists/Sports%20Activities%20Voting/NewForm.aspx&#39;, title: &#39;User Survey&#39;,width:700,height:350}); return false;" type="button" value="Vote"/>
    yaşamak bir eylemdir

  • Can't access Modal dialog box via Powershell script

    Hi,
    I have a powershell script to login to an IE website and everything works fine excepting when I call a modal dialog box.  I've attached the line where the modula dialog is invoked.  When it gets to this part the script hangs and I'm unable
    to get past this.  I've googled a few articles where it suggests I should run an a scheduled task to scrape for the modal dialog box but I've tried it without much luck.  If you can please give me some pointers on resolving this issue. 
    Thnx
    Sue.
    $ie.Document.getElementsByTagName("button") | ? { $_.innerText -eq 'UNLOCK User' } | Select-Object -first 1 | % { $_.Click() }
    Sue

    Hi,
    I have a powershell script to login to an IE website and everything works fine excepting when I call a modal dialog box.  I've attached the line where the modula dialog is invoked.  When it gets to this part the script hangs and I'm unable
    to get past this.  I've googled a few articles where it suggests I should run an a scheduled task to scrape for the modal dialog box but I've tried it without much luck.  If you can please give me some pointers on resolving this issue. 
    Thnx
    Sue.
    $ie.Document.getElementsByTagName("button") | ? { $_.innerText -eq 'UNLOCK User' } | Select-Object -first 1 | % { $_.Click() }
    Sue

  • How to create application toolbar in modal dialog box in selection-screen

    Hi Experts,
    how to create application toolbar in modal dialog box in selection-screen?
    Regards,
    Swapnika

    Hi,
    Check the following link regarding Model dialog box and appication toolbar
    http://help.sap.com/saphelp_nw70/helpdata/en/d1/801b84454211d189710000e8322d00/frameset.htm
    It helps in solving your problem.
    Thanks.
    Ramya.

  • Standard 'X' in a modal dialog box not working

    Hi,
    I have created a module pool and calling screen from main screen using Call screen.... Starting... ending... statement.
    It is a modal dialog box screen. As a standard a [X] appears on top right corner. But when I click it doesn't work. it does not even fire PBO. How can I make it work?

    Hi,
    Set next screen as 0, not the screen itself. Then you are able to close it this way.
    Regards
    Marcin
    I was wrong, this will only close the modal box each time after the dialog step is completed. To activate this magic 'X' (allow closing the window with ALT+F4) in PBO set status (type dialog box ) and activate CANCEL and CONTINUE buttons. Now when you try closing the window either by CANCEL button or using X, sy-ucomm (ok_code of the screen) will store CANCEL function code. This way you can simply say LEAVE SCREEN . That works fine, I checked.
    Regards
    Marcin
    Edited by: Marcin Pciak on Mar 17, 2009 11:16 PM

  • How do i disable the open/save image dialog box in firefox? I want to directly save the image file to the drive.

    How do i disable the open/save image dialog box in firefox? I want to directly save the image file to the drive without clicking on save option everytime when saving an image. I'm using firefox ver 35.0.1 for windows 7.

    Click on the Firefox menu. Then click "Options". Go to "Applications" tab. Search for jpg and png file type. You will find they have "Always ask" action attribute. Change it to "Save file".
    Hope it will work fine for you.

Maybe you are looking for