Re: Dialog Module

Dear All,
I Have to increase the height of the textbox in dialog module layout editor. can any one please suggest the solution for this problem.

You cannot increase the height. Instead use Text edit controls
class cl_gui_textedit. Search for this you will find various examples.

Similar Messages

  • How to create Dialog Module[Screen,Menu,object navigator]

    Dear All,
                kindly give me. How to create Dialog Module[Object Navigator,Screen,Menu,] steps with code.

    please see this  link   it is with  screen shot from the scrach ...
    <b>creating  struture 
    creating screen
    writing logic 
    table control
    creating tcode</b>  ...etc
    <a href="http://">http://www.sapdevelopment.co.uk/dialog/tabcontrol/tc_basic.htm</a>
    reward  points if it is usefull ...
    Girish

  • Custom infotype replacement for dialog modules

    Hi,
    I have been asked to recreate a custom OM infotype (created with PPCI and based on the Planned Compensation infotype) to the new SAP EHP4 environment.  Part of the infotype is a custom dialog maintenace module that allows the infotype to be viewed and maintain with the PP01 transaction (planned compensation is linked to a job).
    When I recreate the code in the new environment (I cannot use a transport), I am unable to recreate the dialog module because the system says "dialog modules are obsolete and no longer supported."  Can you tell me what is the new way to create the new maintenance screen and have it work with PP01.  Also, it seems that if I try to change the configuration table T777D (using SM30) with something other than a dialog module name, it doesn't accept it, so where does the new maintenance screen go in that table?
    Thank you in advance for your help.
    Christian Durini.

    Hi,
    whereever we create a custom OM infotype using PPCI transaction, the system will go to next level as with titles as
    - Module Pool Program
    - Screens
    - Tables and etc...
    so as per the structure of Module Pool Program, first of all we have to create Program (Double click on each Program after that the cursor will to next screen.here we have to click on create button). After that go to SE51 and enter the program and screen number, click on change button. 
    Normally whenever we create info type the system will maintain with screens as 1000, 2000, 3000
    follow above procedure for 3 screens.
    Ram.

  • Dialog Module and List Processing.

    Hi All,
    I am having a program in which after processing I get a basic list. Using PF-STATUS of the basic list a dialog module is called using 'CALL SCREEN'  which accepts date and has exectue and cancel buttons on it.
    What do I do to so that user when clicks on cancel button the dialog module disapperas and the original list processing is still seen.
    Thanks,
    DJ

    Hi,
    To pass control from the dialog processor to the list processor, you must include the following statement in one of the dialog modules:
    LEAVE TO LIST-PROCESSING [AND RETURN TO SCREEN <nnnn>].
    You can include this statement in either the PBO or the PAI event. Its effect is to start the list processor and display the basic list after the PAI processing of the current screen. The basic list contains any list output from all PBO and PAI modules that have been executed up to that point.
    regads,
    keerthi

  • Time constraints and Dialog module

    1.What is the difference between the time constraints A(IT exists just once from 01 Jan 1800 to 12 Dec 9999) and B(IT exists for maximum of once from 01 Jan 1800 to 12 Dec 9999)?
    2.What is the necessity of dialog module for a Infotype?

    Time Constraint A and B
    Infotypes with time constraint A & B must have no more than one record. The system automatically assigns the record a validity period from January 01, 1800 through December 31, 9999. This validity period cannot be subdivided.
    Infotype records with time constraint A CANNOT be deleted.
    Infotype records with time constraint B CAN be deleted.
    The difference is check the BOLD TEXT.
    As for ur second question, Function modules/dialog modules helps calling infotypes when called from any custom program ,and allows you to perform similar actions/tasks that you would perform on them from direct maintainance. ex: create,change, delete etc. also performing the same on multiple infotypes in a single go using a them is easier than writing a code to manipulate each single infotype.
    SAP exposed these functions to be exploited as there will come many situations in business scenarios where you require to work with them by writing custom code.
    hope its helpful

  • What is "No dialog module found" message?

    Hi,
    I'm trying to update a record in pa0558 table using hr_infotype_operation.
    The code looks something like this:
      SELECT SINGLE MAX( begda ) FROM pa0558 INTO begda WHERE pernr = pernr.
      SELECT SINGLE endda FROM pa0558 INTO endda WHERE pernr = pernr AND begda = begda.
      CLEAR i0558.
      i0558-pernr = pernr.
      i0558-infty = '0558'.
      i0558-begda = begda.
      i0558-endda = endda.
      i0558-nip00 = nip00.
      i0558-subty = ''.
      i0558-objps = ''.
      i0558-sprps = ''.
      i0558-seqnr = '000'.
      i0558-pesel = '77040642811'.
      CALL FUNCTION 'HR_INFOTYPE_OPERATION'
        EXPORTING
          infty         = '0558'
          number        = pernr
          validityend   = endda
          validitybegin = begda
          subtype       = ''
          recordnumber  = '000'
          record        = i0558
          operation     = 'MOD'
          tclas         = 'A'
          nocommit      = ' '
        IMPORTING
          return        = hr_return
          key           = key.
    etc.
    The problem is that no data is being updated, and the following message is being shown during debug: "No dialog module found ".
    What does it mean? Does it mean that something is missing, not installed or I don't know what else?
    Regards
    Ladislav
    PS. I'm new to ABAP.

    sample code
    <b>  loop  at ia586.
        move-corresponding ia586 to p0586.
        CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'
          EXPORTING
            NUMBER = p0586-pernr.
        CALL FUNCTION 'HR_INFOTYPE_OPERATION'
          EXPORTING
            INFTY         = '0586'
            NUMBER        = p0586-pernr
            LOCKINDICATOR = ''
            VALIDITYEND   = p0586-endda
            VALIDITYBEGIN = p0586-begda
            RECORD        = p0586
            OPERATION     = 'INS'
            NOCOMMIT      = ''
            tclas         = 'A'
          IMPORTING
            RETURN        = RETURN
          EXCEPTIONS
            OTHERS        = 0.
        CALL FUNCTION 'HR_EMPLOYEE_ENQUEUE'
          EXPORTING
            NUMBER = p0586-pernr.
        clear : p0586.
      endloop.</b>
    Regards
    Prabhu

  • Dialog modules are no longer supported

    Dear guys,
              I am developing a Custom PD infotype from scratch .
    But  i am not able to create a dialog module (se35) ,Now it says
    Dialog modules are an obsolete form of technology that is no longer supported.
    Instead, use transaction SE37 to create function modules.
    Need tips/suggestions on this issue ..
    regards ...

    Hi jose ,
                Thanks for  the quick reply ..
    Actually what you said was correct as SAP generates all the required objects..
    In my case the HRIXXXX structure that i created, was DEEP enhanced type .
    When changed to Char OR CHAR/NUMERIC enhancement type it worked well ..
    Sounds weird but this fixed the issue .
    Regards ..
    Ajay

  • Dialog/Module pool programming

    Can anyone give me a link where i can find some useful data related to dialog/module pool programming.

    Hi Jyotirmaye,
    Please take a look at this link.
    http://sap.mis.cmich.edu/sap-abap/abap09/
    Hope this will help.
    Regards,
    Ferry Lianto

  • Standard Dialog module RH_INFOTYP_1001 missing in E-Recruiting

    Hi Friends,
    We have e-Recruitment on a seperate server and connected it to HR using ALE. The object transfer "O(Organizational Unit)" shows error during PFAL transfer from HR to e-Recruiting.
    The problem is the standard dialog module "RH_INFOTYP_1001" does not exist when checked in SE35. When checked from PPCI also, it shows "Dialog module RH_INFOTYP_1001 does not exist".
    The table T777D, however, has dialog module entry for Infotype 1001 but the Dialog module name is RH_INFOTYP_S001 which exists.
    1. What needs to be done to load the dialog module RH_INFOTYP_1001 in 
        the e-Recruitment server ???
    2. Also, we have the folowing packages installed on our e-Rec server:
       SAP_OCS(SPAM/SAINT Update)
       SAP_ABA, SAP_BASIS, PI_BASIS, SAP_BW, ERECRUIT
       Do we also need to apply EA-HR and SAP_HR packages ?? Why ??
    Please advice.
    Thanks,
    Shashank Shirali

    Well,
    have you activated the E-Recruiting ALE Inbound processing?
    Take a look at IMG:
    SAP E-Recruiting->Technical settings -> SAP ERP Central Component integration -> Sofware running on different systems -> ALE Inbound Processing
    You need to activated BADI Implementations HRALE00SPLIT_INBOUND of BADI HR_INB_PROCESS_IDOC and HRALE00INBOUND_IDOC of BADI HRRCF00_DELETE_SPREL.
    This is needed because PA infotypes are not existing and the PD-Object P is just defined as external object.

  • Dialog module

    hi,
    plz tell the coding for addition program using dialog module .
    here my spec given below.
    two input fields,
    one output fields,
    two pushbuttons namely add, exit.
    while click the add button the two input number should be add and depicts in the output field
    i dont know how to set the properties of all gui components and program.
    regards
    surender.

    *& Module pool SAPMYSP2
    INCLUDE MYSP2TOP . " global Data
    INCLUDE MYSP2O01 . " PBO-Modules
    INCLUDE MYSP2I01 . " PAI-Modules
    INCLUDE MYSP2F01 . " FORM-Routines
    INCLUDE MYSP2_O01.
    INCLUDE MYSP2_I01.
    top include program
    *& Include MYSP2TOP Module pool SAPMYSP2
    PROGRAM SAPMYSP2.
    DATA:INPUT1 TYPE I,
    INPUT2  TYPE I,
    OUTPUT1  TYPE I,
    OK_CODE TYPE SY-UCOMM,
    SAVE_CODE LIKE OK_CODE.
    pbo program
    ***INCLUDE MYSP2_O01 .
    *& Module INIT_SCREEN_100 OUTPUT
    text
    MODULE INIT_SCREEN_100 OUTPUT.
    ENDMODULE. " INIT_SCREEN_100 OUTPUT
    pai program
    ***INCLUDE MYSP2_I01 .
    *& Module USER_COMMAND_0100 INPUT
    text
    MODULE USER_COMMAND_0100 INPUT.
    SAVE_CODE = OK_CODE.
    CLEAR OK_CODE.
    CASE SAVE_CODE.
    WHEN 'ADD'.
    OUTPUT1 = INPUT1 + INPUT2.
    WHEN 'SUB'.
    OUTPUT1 = INPUT1 - INPUT2.
    WHEN 'MUL'.
    OUTPUT1 = INPUT1 * INPUT2.
    WHEN 'EXIT'.
    LEAVE PROGRAM.
    ENDCASE.
    ENDMODULE. " USER_COMMAND_0100 INPUT
    REGARDS
    SURENDER

  • Infotype dialog module

    Hello!
    what's the dialog module?
    In PA40 for the applicant, the toolbar doesn't enable the buttons with function Keys NEXT and EPRV.
    In other words, Pa40 calls the report SAPFP50M and into this one the function Keys  NEXT and EPRV are insert into tb_excluding.
    What can i enable this buttons?
    Can i use the exit? Which one?
    Can i use EXIT_SAPFP50M_001?
    Regards.

    hi
    Firztly you didnt specify what you want to achieve. Function key NEXT for what purposes?
    However, I do not recommend making GUI changes to tcode PA40 as its a standard transaction to perform Personnel Actions.
    PA40 is for execute a few infotypes within an infogroup for an employee.

  • Error in Dialog Module  - INCLUDE report "%_HR9066" not found

    Hi,
    After upgrade from 4.6B to ECC 6.0.When i display/create/change Custom Infotype 9072  in transaction PA30. i encounter a dump stating
    INCLUDE report "%_HR9066" not found. It occurs when the program goes for CALL DIALOG... in the SAP standard program.
    Do advice on how to resolve this issue

    Hi Chayan,
    9066 is the custom infotype .
    After upgrading check for the following things which are related to infotype :
    1) Go to se51 and check for Program MP906600 and screen 2000 exist .If not there is a problem in calling the screen
    2)Go to se11 and check whether the table PA9066 and structure P9066 exist
    3)Check whether the infotype is assigned to the Infotypes in spro .(Optional)
    If everthing is suceessful , the infotype exist in the system . If not one of the objects might miss from the above list .
    Regards,
    Gajalkshmi

  • Input Help in Dialog Modules

    HI,
    I have to provide F4 help for many fields that are present in tabstrip control(with 5 tabs). I had set the option "Possible entries" in the layout. In the flow logic, I created a module for POV. How would I get the screen element name (i.e., the field) from which F4 was pressed? While debugging, I dont get the field name in SYST and SCREEN table. For each tab, I am thinking of creating of only one module in POV so that I can avoid hardcoding the field name.
    You can use DEMO_DYNPRO_F4_HELP_MODULE report in IDES if required.

    Try this out it worked for me,
    Will post in in 3 halves.
    1.     First half
    MODULE help_zterm INPUT.  "In POV
      PERFORM help_zterm.
    ENDMODULE.                 " HELP_ZTERM  INPUT
    FORM help_zterm .
      DATA: BEGIN OF svbap OCCURS 12,
              tabix LIKE sy-tabix,
            END OF svbap.
      DATA:   BEGIN OF xvbap OCCURS 125.
              INCLUDE STRUCTURE vbapvb.
      DATA:   END OF xvbap.
      DATA: da_display LIKE ddrefstruc-bool.
      DATA: da_value LIKE vbkd-zterm.
      DATA: da_dynpro_program  LIKE sy-repid.
      DATA: da_dynpro_number   LIKE sy-dynnr.
      DATA: BEGIN OF dynpfield_zterm OCCURS 1.
              INCLUDE STRUCTURE dynpread.
      DATA: END OF dynpfield_zterm.
      da_dynpro_program  = sy-repid.
      da_dynpro_number   = sy-dynnr.
      CLEAR dynpfield_zterm.
      REFRESH dynpfield_zterm.
      MOVE 'ZDEALHD-ZTERM' TO dynpfield_zterm-fieldname.  u201DZDEALHD-ZTERM u2013 screen field name
      APPEND dynpfield_zterm.
      CALL FUNCTION 'DYNP_VALUES_READ'     
        EXPORTING
          dyname     = da_dynpro_program
          dynumb     = da_dynpro_number
        TABLES
          dynpfields = dynpfield_zterm
        EXCEPTIONS
          OTHERS     = 11.
      IF sy-subrc <> 0.
        EXIT.
      ELSE.
        READ TABLE dynpfield_zterm WITH KEY fieldname =
                                    dynpfield_zterm-fieldname.
      ENDIF.
      LOOP AT SCREEN.
        CHECK screen-name = 'ZDEALHD-ZTERM' AND
              screen-input = '0'.
       DA_DISPLAY = CHARX.
      ENDLOOP.
      IF dynpfield_zterm-fieldinp EQ space.
       DA_DISPLAY = CHARX.
      ENDIF.
    Call SD Sales BAdI
      DATA:  da_line    LIKE sy-tabix,
             da_core_inactive TYPE xfeld,
             wa_svbap LIKE svbap,
             wa_xvbap LIKE xvbap.
    Determining Cursor
      CLEAR wa_xvbap.
      GET CURSOR LINE da_line.
      IF da_line GE 1.
        READ TABLE svbap INTO wa_svbap INDEX da_line.
        IF sy-subrc = 0.
          READ TABLE xvbap INTO wa_xvbap INDEX wa_svbap-tabix.
        ENDIF.
      ENDIF.
    Will send the second one and third one  in few seconds.
    Edited by: Abhijit Borkar on Jan 7, 2010 9:11 AM

  • Search help in dialog modules

    Hello gurus
    I struck with a problem while designing the search help .  The problem is described as below
    Three Screen field in my screen namely
    Itab1-vkorg Itab1-kunnr Itab1-vbeln
    My Screen flow logic :
    PROCESS AFTER INPUT.
      MODULE USER_COMMAND_0100.
    PROCESS ON VALUE-REQUEST.
      FIELD ITAB1-VBELN MODULE SALESINVOICE_HELP.
    My main Program :SALESINVOICE_HELP
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
        EXPORTING
          INPUT  = ITAB1-KUNNR
        IMPORTING
          OUTPUT = ITAB1-KUNNR.
      SELECT VBRKVBELN VBRKFKDAT
            INTO CORRESPONDING FIELDS OF TABLE INVOICE_SRCHLP
            FROM VBRK INNER JOIN VBRP ON VBRKVBELN EQ VBRPVBELN
            WHERE VBRK~FKART EQ 'ZF2' AND
                  VBRK~VKORG EQ ITAB1-VKORG AND
                  VBRK~KUNAG EQ ITAB1-KUNNR AND
                  VBRK~FKSTO NE 'X'.
      SORT INVOICE_SRCHLP BY FKDAT VBELN.
      DELETE ADJACENT DUPLICATES FROM INVOICE_SRCHLP.
      CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
        EXPORTING
       DDIC_STRUCTURE         = ' '
           RETFIELD             = 'VBELN'
         VALUE_ORG              = 'S'
        MULTIPLE_CHOICE        = ' '
        DISPLAY                = ' '
        CALLBACK_PROGRAM       = ' '
        CALLBACK_FORM          = ' '
        MARK_TAB               =
      IMPORTING
        USER_RESET             =
        TABLES
          VALUE_TAB              = INVOICE_SRCHLP
        FIELD_TAB              =
           RETURN_TAB             = ITAB_RETURN.
        DYNPFLD_MAPPING        =
      EXCEPTIONS
        PARAMETER_ERROR        = 1
        NO_VALUES_FOUND        = 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.
      ITAB1-VBELN = ITAB_RETURN-FIELDVAL.
    My problem is unable to retieve the screen fields contents. so kindly provide the solution.

    Hi U have to append the field names u want to read.
    Put this code before calling FM.
    REFRESH dynpro_values[]. CLEAR dynpro_values.
    dynpro_values-fieldname = Give ur screen field name u want to read.
    APPEND dynp_fields.
    Like this u have to append all the screen fields for which u want to read the data.
    The finally Call FM.
    After calling the FM read the table dynpro_values with key as field name. dynpro_values-FIELDVALUE contains the field content.
    Check below sample code for your reference.
    PARAMETERS: p_file   LIKE rlgrap-filename MEMORY ID upl.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
      DATA: dynp_fields LIKE dynpread OCCURS 0 WITH HEADER LINE.
      REFRESH dynp_fields. CLEAR dynp_fields.
      dynp_fields-fieldname = 'P_FILE'.
      APPEND dynp_fields.
      CALL FUNCTION 'DYNP_VALUES_READ'
           EXPORTING
                dyname               = sy-cprog
                dynumb               = sy-dynnr
           TABLES
                dynpfields           = dynp_fields
           EXCEPTIONS
                invalid_abapworkarea = 1
                invalid_dynprofield  = 2
                invalid_dynproname   = 3
                invalid_dynpronummer = 4
                invalid_request      = 5
                no_fielddescription  = 6
                invalid_parameter    = 7
                undefind_error       = 8
                OTHERS               = 9.
    Thanks,
    Vinod.
    Edited by: Vinod Reddy Vemuru on Jul 25, 2008 3:15 PM

  • In Dialog module programing how to navigate to previous screens?

    I have a REPORT program which displays a ALV output with custom menu buttons along with the ALV buttons on the menu bar.
    Once the custom button is clicked the REPORT program calls a custom SCREEN 1 the screen is displayed to the user and the screen has a custom menu which has some custom buttons.
    if the user selects any button the user is taken to the next SCREEN 2 .
    My Problm is when the processing is finished on the SCREEN 2 i would like the system to retrurn back to report out put screen and NOT on SCREEN 1.
    If i use the bwlow code in SCREEN 2 - PAI event it just returns me back to SCREEN 1 and not to the report output screen.
    SET SCREEN 0.
    LEAVE SCREEN.
    What coding needs to be done to return me back to the REPORT output screen from SCREEN 2.

    Hi,
    there is also possibility to specify  LEAVE TO LIST-PROCESSING.
    Please check following link
    http://help.sap.com/saphelp_nw04/helpdata/en/10/e7dbde82ba11d295a40000e8353423/content.htm
    Regards,
      Karol
    Edited by: Karol Seman on Oct 29, 2008 9:39 PM

Maybe you are looking for