User Exits for MM to hide screen field

Hi All,
I want to make input = 0 for a screen field (valuation price) in PR. Could you tell me the exits available to achieve this,
like field modification exits available for sales document processing.
Thanks
Pradeep

Hi,
I have achieved the result thru a BADI  ME_PROCESS_REQ_CUST and method FIELDSELECTION_ITEM_REFKEYS.
    if screen-name =  'MEREQ3320-PREIS'.                " valuation price
     SCREEN-INPUT = 0.
     MODIFY SCREEN.
    endif.
I tried doing it with the Exit you have mentioned, but it did not work, can you tell me in which include we can
get the result.
Thanks
Pradeep

Similar Messages

  • User exit for IW31 which capture screen field Po number

    Hi all
    I have the requirement that when we save work order created by IW31. It shud trigger any user exit or BADI.
    In that we have to validate the screen field Purchase order number BSTKD from the Ztable entries.
    My problem is that no user exit passes this value as export parameter. so without that how can I get this value in the include program. Please let me know the user exit which hit after save and passes PO value so I can validate this field.   Thanks!!!
    Quick answer will highly be appreciated!!
    Nikhilesh Vyas

    Hello Kiran
    Thanks for ur reply
    But this Badi does not have purchase order number as parameter in any method which call after user press save button.
    Please let me know any other alternative if u have ...thanks!!

  • User exit for me 51 to put field descryption  for ekbn-sakpto in screen 505

    hi .
    i have a requirement to put field descryption in screen 505 for me51 tcode(program sapmm06b) for field g/l account in screen 505(Account Assignment for item 00010).
    waiting for your resposne.
    bye.
    sita.

    Hi Seetaram,
    Hi,
    By using the below code you can find the User exits for a particular TCODE.Execute this program and the TCODE in selection screen.
    REPORT z_find_userexit NO STANDARD PAGE HEADING.
    *& Enter the transaction code that you want to search through in order
    *& to find which Standard SAP® User Exits exists.
    *& Tables
    TABLES : tstc, "SAP® Transaction Codes
    tadir, "Directory of Repository Objects
    modsapt, "SAP® Enhancements - Short Texts
    modact, "Modifications
    trdir, "System table TRDIR
    tfdir, "Function Module
    enlfdir, "Additional Attributes for Function Modules
    tstct. "Transaction Code Texts
    *& Variables
    DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
    DATA : field1(30).
    DATA : v_devclass LIKE tadir-devclass.
    *& Selection Screen Parameters
    SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
    SELECTION-SCREEN SKIP.
    PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
    SELECTION-SCREEN SKIP.
    SELECTION-SCREEN END OF BLOCK a01.
    *& Start of main program
    START-OF-SELECTION.
    Validate Transaction Code
    SELECT SINGLE * FROM tstc
    WHERE tcode EQ p_tcode.
    Find Repository Objects for transaction code
    IF sy-subrc EQ 0.
    SELECT SINGLE * FROM tadir
    WHERE pgmid = 'R3TR'
    AND object = 'PROG'
    AND obj_name = tstc-pgmna.
    MOVE : tadir-devclass TO v_devclass.
    IF sy-subrc NE 0.
    SELECT SINGLE * FROM trdir
    WHERE name = tstc-pgmna.
    IF trdir-subc EQ 'F'.
    SELECT SINGLE * FROM tfdir
    WHERE pname = tstc-pgmna.
    SELECT SINGLE * FROM enlfdir
    WHERE funcname = tfdir-funcname.
    SELECT SINGLE * FROM tadir
    WHERE pgmid = 'R3TR'
    AND object = 'FUGR'
    AND obj_name = enlfdir-area.
    MOVE : tadir-devclass TO v_devclass.
    ENDIF.
    ENDIF.
    Find SAP® Modifactions
    SELECT * FROM tadir
    INTO TABLE jtab
    WHERE pgmid = 'R3TR'
    AND object = 'SMOD'
    AND devclass = v_devclass.
    SELECT SINGLE * FROM tstct
    WHERE sprsl EQ sy-langu
    AND tcode EQ p_tcode.
    FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
    WRITE:/(19) 'Transaction Code - ',
    20(20) p_tcode,
    45(50) tstct-ttext.
    SKIP.
    IF NOT jtab[] IS INITIAL.
    WRITE:/(95) sy-uline.
    FORMAT COLOR COL_HEADING INTENSIFIED ON.
    WRITE:/1 sy-vline,
    2 'Exit Name',
    21 sy-vline ,
    22 'Description',
    95 sy-vline.
    WRITE:/(95) sy-uline.
    LOOP AT jtab.
    SELECT SINGLE * FROM modsapt
    WHERE sprsl = sy-langu AND
    name = jtab-obj_name.
    FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
    WRITE:/1 sy-vline,
    2 jtab-obj_name HOTSPOT ON,
    21 sy-vline ,
    22 modsapt-modtext,
    95 sy-vline.
    ENDLOOP.
    WRITE:/(95) sy-uline.
    DESCRIBE TABLE jtab.
    SKIP.
    FORMAT COLOR COL_TOTAL INTENSIFIED ON.
    WRITE:/ 'No of Exits:' , sy-tfill.
    ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'No User Exit exists'.
    ENDIF.
    ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'Transaction Code Does Not Exist'.
    ENDIF.
    Take the user to SMOD for the Exit that was selected.
    AT LINE-SELECTION.
    GET CURSOR FIELD field1.
    CHECK field1(4) EQ 'JTAB'.
    SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
    CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
    Reward if helpful,
    phani

  • How to create user exit for MIGO check  "item OK" Field select/unselect?

    Hi All,
       I want to know User Exit for MIGO Screen. when I click check button it will be show "Item OK " Field select or not.
    MIGO Screen post if Item ok field select both parent id and line id . otherwise it will be show error message?.
    Can Please  every one tell me how to do user exit for MIGO?
    mail id: [email protected]
    thanks,
    S.Muthu,

    Hi,
    check the BADI <b>MB_MIGO_BADI</b> ( method: POST_DOCUMENT).
    COMD enhancment <b>MBCF0005</b>
    Regards

  • User-exit for call new customize screen of another new program

    Hello, I'm very appreciate for all who read this topic and give me some advice.
    Anyone has an experience about customize standard program to create new screen
    and add new screen to pop-up when user click some standard button to do something
    for support business requirement and then continue to working the old step (such next old screen).
    In QA11 (Manual UD), For posting stock quantity (After click button "Stock for inspection lot")
    Business requirement need to avoid user to input stock quantity for unrestriced used (UR) and block
    by after click button "Stock for inspection lot". Need to customize to pop-up new created screen for user
    to choose sub-set of this inspection lot to post for UR or block by check box (Just overview)
    Then after finish to select, Need to go back old screen ("Record UD : Stock" Screen) and default sum
    of UR and block into screen (Automatic) for post to mvt.type 321, 350 later.
    After checked, Not have any screen-exit after clicked button "Stock for inspection lot".
    but i found 1 user-exit which was called after click above button.
    So, Can i use user-exit to call new customize screen?
    If need to go back from new customize screen to main screen, May have any problem? How to do it?
    If finish to do in new customzie screen and need to continue display next old screen. How to do it in PAI of new customize screen.
    Thank in advance

    Can anyone provide the documentation for this BADI? Also, I'm concerned about the layout of the screen. Can this BADI do the necessary changes on the layout of the screen?
    Thanks!

  • User Exit for IW32 accessrights check on fields

    Hello,
    i need to implement a check that enables me to block the access on a column within the table (transaction IW32) at the objects-tab for users of a specific role.
    That check could be done by showing an error message once the user presses SAVE or by blocking the input in that table. I checked the Userexit EXIT_SAPLCOIH_009  but that one only allows a check on the header data not on the data of the objects-tab.
    I hadnt found any other user exit that could do the trick. Is that only possible by SAP-code manipulation ?
    Could somebody help me out here ?
    Thanks and best regards,
    oliver

    Hello and thank you very much for the answers.
    Pete, i checked the BADI IWO1_SCREEN_MODIFY but im unsure if that would work because it only hides fields and doesnt allow to disable input. Another problem is that the screen-loop only runs over the input-fields above the tab and the table. (like Order, Sys. Status etc)
    But i need to modify the table itself. Any idea how i can access the table on the tab here ? I normally use ALVs so the question is too if the screen-loop even run over such old-styled-tables usually. Cant say that 100% but i thought it would. For me it looks it doesnt actually :/
    The loop-screen runs only over the elements of dynpro 1108 and not 0300 which contains the table.
    Any idea ?
    thanks again, your help is highly appreciated.
    oliver
    Edited by: Oliver Neumann on Jan 29, 2009 10:25 AM

  • BADI or User exit  for FB50 to update custom field in table COEP

    Hi all,
    i have added one custom field in table COEP through include CI_COBL .
    when i do posting through sales order(VA02) or purchase order(ME22n) that custom fields in COEP get updated with controlling document
    and through BADI AC_DOCUMENT i m updating that custom field in COEP.
    but when i do manual posting through FB50 controlling document is generated in COEP but i m not able to update that custom field
    because in this case BADI AC_DOCUMENT  is not get triggered.
    is there any BADI or User exit or enhancement spot for FB50 through which i can update that custom field in table COEP

    Hi Sandy,
    Thanks for u r reply,
    RFAVIS01 is not getting triggered through FB50
    and F180A001 ( EXIT_SAPLF048_001) is getting triggered but it doesnt contain COEP field in its parameter
    import - F180A_DOC_HEAD_TAB
                 F180A_DOC_ITEM_TAB
    changing - RELATION_TAB

  • BADI/user exit for me22n - disable/grey out field quantity (MEPO1211-MENGE)

    Dear all SAP gurus,
    When changing PO (ME22N), I need to disable (grey out) the quantity field on item (MEPO1211-MENGE), when all scheduled quantity is already received (EKET-MENGE = EKET-WEMNG).
    Have tried using LMEIGICJI and Handle_event method in CL_SCREEN_VIEW_MM. But still doesn't go to the screen that wants to be disabled.
    Tried using BADI ME_PROCESS_PO_CUST, but couldn't find how to disable the quantity field.
    (IF_EX_ME_PROCESS_PO_CUST~FIELDSELECTION_ITEM only works for custom field).
    Please kindly advise
    thanks in advance

    Hi Ahmad,
    No need of ABAP, follow this IMG Path.
    Material Management -> Purchasing - Purchase Order ->  Define Screen Layout at Document Level
    After Executing it . Choose ME22 from list and then choose display icon.
    than double click Quantity and Price here uncheck opt. Entry and check display.
    save your work.
    Hope this works.
    Regards
    Ahsan

  • PPCO0007 User Exit for  Changing Header Fields During Order  (CO40)

    .. Hi !!!!
      I need your help or suggestions,
      I need to change the standar order  before to save, i found the user exit PPCO0007,
      i assign the new value for the order, but when finish the fuction, EXIT_SAPLCOZV_001, the new values are
      lost, and finally the system set the standard order.
        Someona know how can change the order and the the batch.
         Thanks
    Noemí Huerta

    Hi Noemi
    You can use the enchancement PPCO0007 (exit when the production order is saved).
    Use the function module EXIT_SAPLCOZV_001 (User Exit for Checking or Changing Header Fields During Order Save) to update the field priority starting the information in the material-customer info record.

  • How to  find the user exit for a screen..

    Hi,
    plz help me how to find the user exit for a screen..?
    Regards
    Anbu

    Hi,
    check this program this will give you the list of user-exit and BADI for the perticular Tcode.
    REPORT  zuserexit_badi.
    TABLES : tstc,
    tadir,
    modsapt,
    modact,
    trdir,
    tfdir,
    enlfdir,
    sxs_attrt ,
    tstct.
    DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
    DATA : field1(30).
    DATA : v_devclass LIKE tadir-devclass.
    PARAMETERS : p_tcode LIKE tstc-tcode,
    p_pgmna LIKE tstc-pgmna .
    DATA wa_tadir TYPE tadir.
    START-OF-SELECTION.
      IF NOT p_tcode IS INITIAL.
        SELECT SINGLE * FROM tstc WHERE tcode EQ p_tcode.
      ELSEIF NOT p_pgmna IS INITIAL.
        tstc-pgmna = p_pgmna.
      ENDIF.
      IF sy-subrc EQ 0.
        SELECT SINGLE * FROM tadir
        WHERE pgmid = 'R3TR'
        AND object = 'PROG'
        AND obj_name = tstc-pgmna.
        MOVE : tadir-devclass TO v_devclass.
        IF sy-subrc NE 0.
          SELECT SINGLE * FROM trdir
          WHERE name = tstc-pgmna.
          IF trdir-subc EQ 'F'.
            SELECT SINGLE * FROM tfdir
            WHERE pname = tstc-pgmna.
            SELECT SINGLE * FROM enlfdir
            WHERE funcname = tfdir-funcname.
            SELECT SINGLE * FROM tadir
            WHERE pgmid = 'R3TR'
            AND object = 'FUGR'
            AND obj_name EQ enlfdir-area.
            MOVE : tadir-devclass TO v_devclass.
          ENDIF.
        ENDIF.
        SELECT * FROM tadir INTO TABLE jtab
        WHERE pgmid = 'R3TR'
        AND object IN ('SMOD', 'SXSD')
        AND devclass = v_devclass.
        SELECT SINGLE * FROM tstct
        WHERE sprsl EQ sy-langu
        AND tcode EQ p_tcode.
        FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
        WRITE:/(19) 'Transaction Code - ',
        20(20) p_tcode,
        45(50) tstct-ttext.
        SKIP.
        IF NOT jtab[] IS INITIAL.
          WRITE:/(105) sy-uline.
          FORMAT COLOR COL_HEADING INTENSIFIED ON.
    Sorting the internal Table
          SORT jtab BY object.
          DATA : wf_txt(60) TYPE c,
          wf_smod TYPE i ,
          wf_badi TYPE i ,
          wf_object2(30) TYPE c.
          CLEAR : wf_smod, wf_badi , wf_object2.
    Get the total SMOD.
          LOOP AT jtab INTO wa_tadir.
            AT FIRST.
              FORMAT COLOR COL_HEADING INTENSIFIED ON.
              WRITE:/1 sy-vline,
              2 'Enhancement/ Business Add-in',
              41 sy-vline ,
              42 'Description',
              105 sy-vline.
              WRITE:/(105) sy-uline.
            ENDAT.
            CLEAR wf_txt.
            AT NEW object.
              IF wa_tadir-object = 'SMOD'.
                wf_object2 = 'Enhancement' .
              ELSEIF wa_tadir-object = 'SXSD'.
                wf_object2 = ' Business Add-in'.
              ENDIF.
              FORMAT COLOR COL_GROUP INTENSIFIED ON.
              WRITE:/1 sy-vline,
              2 wf_object2,
              105 sy-vline.
            ENDAT.
            CASE wa_tadir-object.
              WHEN 'SMOD'.
                wf_smod = wf_smod + 1.
                SELECT SINGLE modtext INTO wf_txt
                FROM modsapt
                WHERE sprsl = sy-langu
                AND name = wa_tadir-obj_name.
                FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
              WHEN 'SXSD'.
    For BADis
                wf_badi = wf_badi + 1 .
                SELECT SINGLE text INTO wf_txt
                FROM sxs_attrt
                WHERE sprsl = sy-langu
                AND exit_name = wa_tadir-obj_name.
                FORMAT COLOR COL_NORMAL INTENSIFIED ON.
            ENDCASE.
            WRITE:/1 sy-vline,
            2 wa_tadir-obj_name HOTSPOT ON,
            41 sy-vline ,
            42 wf_txt,
            105 sy-vline.
            AT END OF object.
              WRITE : /(105) sy-uline.
            ENDAT.
          ENDLOOP.
          WRITE:/(105) sy-uline.
          SKIP.
          FORMAT COLOR COL_TOTAL INTENSIFIED ON.
          WRITE:/ 'No.of Exits:' , wf_smod.
          WRITE:/ 'No.of BADis:' , wf_badi.
        ELSE.
          FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
          WRITE:/(105) 'No userexits or BADis exist'.
        ENDIF.
      ELSE.
        FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
        WRITE:/(105) 'Transaction does not exist'.
      ENDIF.
    AT LINE-SELECTION.
      DATA : wf_object TYPE tadir-object.
      CLEAR wf_object.
      GET CURSOR FIELD field1.
      CHECK field1(8) EQ 'WA_TADIR'.
      READ TABLE jtab WITH KEY obj_name = sy-lisel+1(20).
      MOVE jtab-object TO wf_object.
      CASE wf_object.
        WHEN 'SMOD'.
          SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
          CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
        WHEN 'SXSD'.
          SET PARAMETER ID 'EXN' FIELD sy-lisel+1(20).
          CALL TRANSACTION 'SE18' AND SKIP FIRST SCREEN.
      ENDCASE.
    Reagards,
    Bharat.

  • How to find user exits for a specific field

    hi,
        How can we find a user exit for a specific fields .
    as i know Three ways to search user-exits
    1. SE80 look includes in a packages with name user-exits
    2.  by zreport which will fetch user-exit in a T-CODE
    3. SMOD
    but what if we have to find a user-exit for particular field for e.g bupla(bussiness place) in MIRO.
    Please suggest me.
    Thanks and  Regards ,
    Rahul Singh.

    Hi Rahul,
    Here is the procedure to create field exits.
    Step by step procedure for creating Field Exits
    There are eight steps to creating a field exit:
    Step 1: Determine Data Element
    Step 2: Go To Field Exit Transaction
    Step 3: Create Field Exit
    Step 4: Create Function Module
    Step 5: Code Function Module
    Step 6: Activate Function Module
    Step 7: Assign Program/Screen
    Step 8: Activate Field Exit
    Step 1: Determine Data Element
    u2022     Before you can begin adding the functionality for a field exit, you must know the corresponding data element.
    Step 2: Go To Field Exit Transaction
    u2022     The transaction to create field exits is CMOD.
    u2022     You can use the menu path Tools -> ABAP/4 Workbench -> Utilities -> Enhancements -> Project management.
    u2022     From the initial screen of transaction CMOD, choose the Text enhancements -> Field exits menu path.
    u2022     After choosing this menu path, you will be taken to the field exits screen. From here, you can create a field exit.
    NOTE : Even though you use transaction CMOD to maintain field exits, you do not need to create a project to activate field exits.
    Step 3: Create Field Exit
    u2022     From the field exit screen of transaction CMOD, choose the Field exit -> Create menu path.
    u2022     After choosing this menu path, a dialog box will prompt you for the appropriate data element .
    u2022     Enter the data element name and click the u2018Continueu2019 pushbutton.
    u2022     Now, you will be able to create the function module associated to the data elementu2019s field exit.
    Step 4: Create Function Module
    u2022     You will automatically be taken to the Function Library (SE37) after entering a data element name and clicking the u2018Continueu2019 pushbutton.
    u2022     In the u2018Function moduleu2019 field, a function module name will be defaulted by the system based on the data element specified. This name will have the following convention:
    FIELD_EXIT_<data element>
    u2022     You can add an identifier (an underscore followed by a single character ).
    u2022     The first function module for a data elementu2019s field exit must be created without an identifier.
    u2022     To create the function module, click on the u2018Createu2019 pushbutton, choose menu path Function module -> Create, or press u2018F5u2019.
    u2022     After choosing to create the function module, you will get the warning: "Function module name is reserved for SAP". This message is just a warning so a developer does not accidentally create a function module in the field exit name range. By pressing u2018Enteru2019, you will be able to go ahead and create the function module.
    u2022     Before coding the function module, you will have to specify the function modules attributes -- function group, application, and short text.
    Step 5: Code Function Module
    u2022     From the function moduleu2019s attributes screen, click on the u2018Source codeu2019 pushbutton or choose the Goto -> Function module menu path to the code of the function module.
    u2022     Here you will add your desired functionality for the field exit.
    u2022     Remember that field exitu2019s function module will have two parameters -- one importing parameter called "INPUT" and one exporting parameter called "OUTPUT". These parameters will be set up automatically by the system.
    u2022     You must remember to assign a value to the OUTPUT field. Even if the value does not change, it must be moved from the INPUT field to the OUTPUT field.
    Step 6: Activate Function Module
    u2022     After coding the function module, you must remember to activate it.
    u2022     Use the Function module -> Activate menu path to activate the function module.
    u2022     At this point, you can return to the field exit transaction.
    u2022     You should be able to 'green arrow' back to this transaction.
    u2022     When you return to the field exit transaction, you will see an entry for the newly created field exit.
    u2022     At this point, the field exit is global. That is, it applies to all screens that use a particular data element. On any screen that uses the data element, the corresponding field exit function module will be triggered, once it is active.
    u2022     Also, the field exit will not be triggered yet because it is inactive.
    Step 7: Assign Program/Screen
    u2022     This step is only needed if you want to make a field exit local.
    u2022     To make a field exit local, select the field exit and click on the u2018Assign prog./screenu2019 pushbutton.
    u2022     In the dialog box , indicate the appropriate program name and screen number.
    This information indicates that the field exit is local to the specified screen in the specified program.
    u2022     In the dialog box, you determine which function module gets executed for the field exit by specifying the identifier in the u2018Fld. Exitu2019 field.
    u2022     If this field is left blank, the function module triggered will be 'FIELD_EXIT_<data element>'.
    u2022     If a single-character identifier is entered into the field, the function module triggered will be 'FIELD_EXIT_<data element>_<identifier>'.
    Step 8: Activate Field Exit
    u2022     The field exit must be active for it to be triggered by the system.
    u2022     Activate the field exit by choosing the Field exit -> Activate menu path.
    u2022     After assigning the field exit to a change request, its status will change to u2018Activeu2019 and it will be triggered automatically on the appropriate screen(s).
    NOTE : In order to activate the field exit the profile parameter abap/fieldexit = YES must be set on all application servers
    Execute the transaction SE38 with PROGRAM NAME - RSMODPRF
    Then give the Data Element Name for which field you want to create the exit(Just cross check with your field data element) and execute.
    then it takes you to SE37 with the function module name FIELD_EXIT_<DATA ELEMENT NAME> and then create the same function module.
    and in the coding part, You can write your logic to display the output of that field. and activate it.
    once you complete the above,
    Again execute SE38 transaction with program RSMODPRF and again click on Execute button without any Data Element Name. Now you select the data element which you have created and click on Assign prog/ Screen button and assign the program name and screen number of the filed and click on the menu Field Exit and Activate.
    Hope it helps.
    Regards
    Radhika
    Edited by: Radhika Pande on Nov 26, 2009 7:58 AM

  • User-exit for autopopulate nickname field in pa40

    Hello Experts,
    In transaction PA40 Create Personal data there is a screen field named Nickname which is Mandatory.
    I want to autopopulate this nickname field when i enter first name last name, the first name field should enter the nickname.
    Is there any user-exit for such a requirement.
    Thanks in advance,
    Thanks & Regards,
    Nikhil K.

    Hi Nikihil,
    You can use the User Exit that you identified but the function exit to use is EXIT_SAPFP50M_001. This is one you should use to default values in infotypes and the EXIT_SAPFP50M_002 is used to do checks and not manipulate the valuse. This is one of the right ways to do it and I have implemented it before and it works fine. You may want to call the following  methods to get current Infotype values from the screen and the proposed values to be updated with.
    CALL METHOD cl_hr_pnnnn_type_cast=>prelp_to_pnnnn
                  EXPORTING
                    prelp =
                  IMPORTING
                    pnnnn = .
    and
    CALL METHOD cl_hr_pnnnn_type_cast=>pnnnn_to_prelp
                    EXPORTING
                      pnnnn =
                    IMPORTING
                      prelp = .

  • User exit for MB1A screen

    I  want to block the withdraw qty in MB1A screen.I used MBCFC003 AND MBCF0005 BUT I couldn't get the exact result.Is it user exit for MB1A screen -PPC00009.So can anyone tell me the exact user exit.
    Regards,
    Maran.d

    Dear Maran,
    What's your exact requirement?What do you want to block in MB1A T Code?
    You want to restrict for 261 movement for an order or reservation in MB1A?
    These are the exits that can be used for MB1A,
    MB_CF001                                Customer Function Exit in the Case of Updating a Mat. Doc.
    MBCF0011                                Read from RESB and RKPF for print list in  MB26
    MBCF0010                                Customer exit: Create reservation BAPI_RESERVATION_CREATE1
    MBCF0009                                Filling the storage location field
    MBCF0007                                Customer function exit: Updating a reservation
    MBCF0006                                Customer function for WBS element
    MBCF0005                                Material document item for goods receipt/issue slip
    MBCF0002                                Customer function exit: Segment text in material doc. item
    Regards
    S Mangalraj

  • Field Exit or User Exit for Maintenance Order field.

    Dear All,
    we need an field exit or an user exit for order(AUFNR)field in PM module.
    The Client wants that the value of this field should be validated and for certaion condition an error message should be given while saving an invoice for this order.
    Kindly provide the user exit ..
    Its urgent.
    Thansk in advance ..
    regards
    Ajay.

    Implement Field Exit within program   
    For this example I am using dta element 'EBELN' from table EKKO.                   
    Step 1: Execute program 'RSMODPRF', entering the data element of the field
    Step 2:Create function module when prompted, and add you code to the source section using the parameter 'INPUT' as the field value you are checking
    Step 3:      Save and activate Function and execute transaction 'CMOD'.
    Step 4:      Choose option: Goto-> Text Enhancements->Data elements->New DE cust docu.
    Step 3:      Save and activate Function and execute transaction 'CMOD'.
    Step 4:      Choose option: Goto-> Text Enhancements->Data elements->New DE cust docu.
    Step 5:      Enter data element
    Step 6:      Save and activate
    Step 7: Execute program 'RSMODPRF' again but this time leave data element field blank. Step 8: Select the checkbox for the data element you have just created and choose option: Field exit->Activate This will now be active for all instances of this data element, but you can assign specific program and screen combinations by pressing the 'Assign prog./screen' button. You can also change the code you entered in the field exit function module by pressing the 'Edit FM' button.
    regards
    vinod

  • How to find user exit for a perticular screen?

    Dear all,
    Can some one tell me how to find user exit for a perticular screen?
    ex: MC88 screen can we figure out are there any user exit for that screen!!
    Regards,
    Vj

    User exits are built into the Standard SAP code. You just activate them and insert your code into the include programs.
    Here is a program that will list the user exits per transaction code. Not perfect, but it may help.
    report z_find_user_exit no standard page heading.
    tables: tstc, tadir, modsapt, modact,
            trdir, tfdir, enlfdir, tstct.
    data : jtab like tadir occurs 0 with header line.
    data : hotspot(30).
    parameters : p_tcode like tstc-tcode obligatory.
    at line-selection.
      get cursor field hotspot.
      check hotspot(4) eq 'JTAB'.
      set parameter id 'MON' field sy-lisel+1(10).
      call transaction 'SMOD' and skip first screen.
    start-of-selection.
      perform get_data.
      perform write_list.
          FORM get_data                                                 *
    form get_data.
      select single * from tstc
                  where tcode eq p_tcode.
      check sy-subrc eq 0.
      select single * from tadir
                where pgmid = 'R3TR'
                  and object = 'PROG'
                  and obj_name = tstc-pgmna.
      if sy-subrc ne 0.
        select single * from trdir
                 where name = tstc-pgmna.
        if trdir-subc eq 'F'.
          select single * from tfdir
                         where pname = tstc-pgmna.
          select single * from enlfdir
                         where funcname = tfdir-funcname.
          select single * from tadir
                         where pgmid = 'R3TR'
                           and object = 'FUGR'
                           and obj_name eq enlfdir-area.
        endif.
      endif.
      select * from tadir into table jtab
                 where pgmid = 'R3TR'
                   and object = 'SMOD'
                   and devclass = tadir-devclass.
      select single * from tstct
              where sprsl eq sy-langu
                and tcode eq p_tcode.
    endform.
          FORM write_list                                               *
    form write_list.
      format color col_positive intensified off.
      write:/(19) 'Transaction Code - ',
      20(20) p_tcode,
      45(50) tstct-ttext.
      skip.
      if not jtab[] is initial.
        write:/(95) sy-uline.
        format color col_heading intensified on.
        write:/1 sy-vline,
        2 'Exit Name',
        21 sy-vline ,
        22 'Description',
        95 sy-vline.
        write:/(95) sy-uline.
        loop at jtab.
          select single * from modsapt
          where sprsl = sy-langu and
          name = jtab-obj_name.
          format color col_normal intensified off.
          write:/1 sy-vline,
          2 jtab-obj_name hotspot on,
          21 sy-vline ,
          22 modsapt-modtext,
          95 sy-vline.
        endloop.
        write:/(95) sy-uline.
        describe table jtab.
        skip.
        format color col_total intensified on.
        write:/ 'No of Exits:' , sy-tfill.
      else.
        format color col_negative intensified on.
        write:/(95) 'No User Exit exists'.
      endif.
    endform.
    SMOD, is where you can find the system modifications provided by SAP. CMOD is where you will implement them. If you are looking for all the enhancements provided, then go to CMOD, follow the menu, 'Utilities-->SAP Enhancements'. This will take you to a screen where if you just execute it, you will get all the enhancements provided by SAP.
    It is always difficult to find a user exit if all you have is a program name or a transaction code, unless you do a program like Rich suggested. But even there, you will not be able to find user exits that are implemented as sub-routines(also called forms not sapscript forms). Most of the user exits are documented under the corresponding task under IMG structure. So use transaction code SPRO, go to the IMG structure, choose the application area that your program or transaction might be and then you should find a task that talks about enhancements. If you execute that task most often it will take you to CMOD and sometimes to SE38. But all you want to know is there in the documentation attached to the task. Then you can go to CMOD and see which components are there.
    Regards,
    Amey

Maybe you are looking for