Ir al contenido principal

4 métodos para encontrar Customer/User Exit’s & BADi’s en transacciones std

 

In order to explain you in the simple manor I’ve taken ‘MM01 – Creation of Material Master’ transaction code as an example. Please follow the below steps to know the different ways of finding user exits and BADi’s.

Method 1:

    • Enter the transaction code in the command bar, for which you would like to search for an user exit and then click on enter, so that it would take you to the initial screen of the transaction.
    • Go to Menu bar – Click on ‘System‘ and then click on ‘Status‘ as shown in the below screen shot.

        1.PNG

    • Once you click on the ‘Status‘ below screen would get popped up. Here, double click on the program name.

        /wp-content/uploads/2014/04/2_436601.png

    • Once the program window is open, go to Menu Bar –> click on ‘Goto‘ and then click on ‘Object Directory Entry‘.
    • The above step would take you to a pop up window and here copy the Package Name as shown in the below screen shot.

          3.PNG

    • Once you get the package number execute the transaction code SE80 (We can also try with SE84) and then click on ‘Repository Information System’.
    • As soon as you done with the above step the system would display the respective Objects list, here drill down Enhancements and then Customer Exists.
    • Now, double click on Enhancements, which is under Customer Exists, so that the selections screen would get displayed in right side.
    • Here go to package field and paste the copied package number from the previous step (program) and then execute the transaction as shown in the below screen shot.

        4.PNG

    • As soon as you execute the above step, it would display the list of user exits for the relevant transaction / package number.

         5.PNG


In order to find out the relevant BADi for a transaction code, follow the above steps but instead of expanding Customer exits, expand Business Add-ins as shown below.

    • Drill down Business Add-ins and then double click on Definitions, so that the selection window would get open in the right side of the screen. Here enter the copied package number in the Package field and then execute the transaction as show below.

11.PNG

    • As soon as you execute the above step, it would display the list of BADi’s for the relevant transaction / package number.

/wp-content/uploads/2014/04/12_436635.png



Method 2:

    • Execute the transaction code SE93 –> enter the desired transaction code in Transaction Code field and then click on Display button as shown in the below screen shot.

6.PNG

    • Once you click on Display button it would show the below screen, double click on the program name.

/wp-content/uploads/2014/04/7_436606.png

    • Once the above step is done, go to Menu Bar–> click on ‘Goto‘ and then click on ‘Object Directory Entry‘.
    • As soon as you done with the above step, the system would pop up with a window as shown below, copy the Package name for the further process.

8.PNG

    • Once you get the package number execute the transaction code SMOD –> place cursor on Enhancement field and then press F4.
    • It would take you to the below screen (Repository Info Systems). Enter the package number, which has copied from the previous step. And then click on enter button.

9.PNG

    • As soon as you execute the above step, it would display the list of user exits for the relevant transaction / package number.

/wp-content/uploads/2014/04/10_436615.png


Method 3:

Along with above methods I would like to show the ways to find the Exist / BADi’s at configuration / SPRO as well.

Example: If you would like to know the relevant user exits at the functionality level like, ‘Logistics Invoice Verification’, follow the below steps.


    • Execute the transaction code SPRO and click on SAP Reference IMG –> drill down Materials Management –> Logistics Invoice Verification –> Maintain Customer Exits and Business Add-Ins –> click on IMG Activity Document on Maintain Customer Exits for Invoice Verification, so that it would show the list of Customer / User Exits for the functionality.

/wp-content/uploads/2014/04/13_436636.png

/wp-content/uploads/2014/04/14_436637.png


In order to find out the relevant BADi at the functionality level, follow the above steps but instead of clicking on click on IMG Activity Document for Maintain Customer Exits for Invoice Verification, click on IMG Activity Document for Maintain Business Add-Ins for Invoice Verification, so that it would display the , so that it would show the list of BADi’s for the functionality.


/wp-content/uploads/2014/04/15_436638.png


Method 4:

If you find difficulty in finding the exact node, follow the below steps


    • Execute the transaction code SPRO and click on SAP Reference IMG–> click on Find button or press Ctrl+F.
    • Once you click on find button the below pop up window gets displayed –> enter Customer Exits in the Search Term field and then press enter button.

16.PNG

    • Once you hit enter, the system would provide you the list of results for the search term, which you have entered. You should be very patience in finding the right node as the list would be very big. You can take the ‘In Area’ reference as that would provide the information about the functionality of the node. Refer the below screen shot for your info.

/wp-content/uploads/2014/04/17_436640.png

    • As soon as you find the right node, double click on it and it would take you to the configuration node, for which it belongs to.

/wp-content/uploads/2014/04/18_436641.png

  • Now you can click on IMG Activity Document for Maintain Customer Exits for Invoice Verification to display the relevant Exits.


Note: 1. Since I’ve already displayed the screen shot for the above step, not displaying the same for the 2nd time.

   2. Follow the same steps to get relevant BADi’s.


Hope the document might find you useful. Thanks for reading the document and I would welcome your comments for improving the document quality.


Source / Fuente:

https://blogs.sap.com/2014/04/19/methods-to-find-customeruser-exits-badis-for-a-transaction-code/


Comentarios

Entradas más populares de este blog

A to Z of OLE Excel in ABAP 7.4

  SAP users, both business and end users always need to download the output of a report to spreadsheet and do their analytics.   The standard excel output from a report is very simple process but it is old fashioned and the spreadsheet looks quite boring.  There is no default formatting and the users have to do all the hard work of changing the fonts, coloring the texts, marking the borders etc. Updated 16th Aug 2019  –  If you are working in non-ABAP 7.4 (below), there is complete reference program for you too. Go to the end of this article.  Thank you  Legxis  ( LeonievonK ) for the share. I acknowledge, whatever I mentioned above can be achieved in many ways programmatically. We can do it in the old traditional ABAP way but  providing multiple tabs in the spreadsheet and formatting is quite tricky with non  OLE  method. OLE = Object Linking and Embedding The high level agenda of this article is to be the  G.O.A.T.  (please google it if you do not know the full form)  of OLE Excel Gu
How to add custom field in Additional B Tab for SAP Sales Order In this article we want to explain step by step how to add custom field in SAP Sales Order transaction VA01/VA02/VA03. This time Mr ABAPGurus will give the tutorial of enhancement to add custom field in SAP Sales order. In this sample we will add new custom field for comments and customer satisfaction, this data will save into separate table from SAP Standard table ( VBAK / VBAP ). SAP provided us with ADDITIONAL TAB in the sales order transaction ( VA01/VA02/VA03 ) which allow customer to add custom fields.  T he different between ADDITIONAL A and ADDITIONAL B is the ADDITIONAL A for field which already predefine in Sales Order Header ( VBAK ) fields and ADDITIONAL B is for field that freely define. This sample we will use ADDITIONAL B because we will store data from customer satisfaction into Z database table. 1. Create one Z table using SE11 SAP Transaction code. 2.Using SE38 Transaction code and ope

VOFM

Creating VOFM custom routine, functionality same as SAP standard routine 103 with Additional Functionality 1.    Introduction 1.1   Document Purpose 1.2    This is the document helps you to create custom routine for sales order for below specific requirement: Functional description: In case of sale order with the SD document category ‘K’ or ‘L’ or ‘H’ related to an invoice, we need to fill the fixed value date (VBKD_VALDT) with the billing reference date (VBRK_FKDAT). For example: Invoice 90001111, the billing date is 22.07.2013 If we create a sale order related to this invoice, we want the fixed value date equal to the billing reference date. As per the requirement: Sap standard routine ‘103’ triggers whenever sales order is being created with reference. Sap standard routine is configured in VOFM transaction as: Sap standard routine ‘103’ has the functionality of copying the billing document header data and billing document line item data into the