Steps for Finding User-Exit or Badis

Applies to:
SAP ECC 6.0. For more information, visit the ABAP homepage.

Summary
This document helps people to find the corresponding user exit or BADI available for SAP standard transaction code. Author: Sai Ram Reddy Neelapu

Company: Atos Origin - Singapore Created on: 23 March 2011

Author Bio
Sai Ram Reddy Neelapu is working as Sr. ABAP Consultant in Atos Origin for past 5+ years.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 1

Table of Contents
Purpose of Enhancements ................................................................................................................................. 3 Steps to find USEREXIT or BADI ................................................................................................................... 3
Method 1: (User Exits) ................................................................................................................................................. 3 Method 2: (Function Module Exit) ................................................................................................................................ 5 Method 3: (Identifying BADI) ........................................................................................................................................ 7

Related Content ................................................................................................................................................ 11 Disclaimer and Liability Notice .......................................................................................................................... 12

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 2

Steps for Finding User

Purpose of Enhancements
User-Exits or BADI allow you to add own functionality to SAP standard screen without modifying the standard program. User-exits are generally collected in includes and attached in standard program by SAP. As this document is intended mainly to find the list of user exits or BADI that are tied to standard transaction
0   ( ) " !  (  &     &   %  ' ! &  % $ # " !      !           

Steps to find USEREXIT or BADI

List of Transaction code x x x

CMOD SMOD SE18 Business Add-Ins: Definitions

Firstly, I will show you how to find the list of User-Exit that are available for standard transaction code.
Note: There are few different ways of finding out userit. scenarios are few ways of doing

Method 1: (User Exits) Business Scenario: When plant 101 store users are performing 311 movement type transfer from store to production in loc, they will like to auto populate the plant and material number into the text field. Step 1: Go to the relevant SPRO and look for the documentation.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 3

Steps for Finding User

P R

C Q

H 2

Step 2: Click on documentation button

, it will display all the available user exits.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 4

Steps for Finding User

Method 2: (Function Module Exit) Business Scenario: You want to check, whether there is any suitable exit available before vendor creation using transaction code XK01. Step 1: Go to transaction code SE93, enter transaction code XK01. Press Display

Step 2: Copy the program name that is tied to the transaction code.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 5

Steps for Finding User

Step 3: Go to transaction code SE37, enter Function module name as EXIT_<Program name>_* as shown below.
Note: Here program name which is identified in step 2.

Step 4: Press F4, value help. You will see all the available list of function modules.

As this document aim is to identify the user exits, I am not explaining much about the implementation of these user-exits or function module exits.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 6

Steps for Finding User

Method 3: (Identifying BADI) Business Scenario: You want to warn the user whenever user SAVE incoming invoice with zero amount in transaction code MIRO. MIRO transaction code. I will be using de-bugging technique here to identify the BADI. Overview of Debugging Keys:
a  b  " ' ! " ( ! g !  a !  ! &  )   f e d b   ) ( "  &  c b (     ( " " (    ( a !    ) ) ( &   (  a  `

Key

Description Action

Steps involved in identifying the BADI. 1) Go to transaction code SE37, and enter the following function module name press display
t r r y x w v r u t s r q p i h

2) Set a break-point, by selecting first line and clicking stop icon as highlighted below.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 7

Steps for Finding User

3) Run transaction code MIRO, program will stop at the break point that is set in step 2.
0 )   f e d " " !   ( b   ) )  a 0   (   ) % )   f e d

Double click on the name variable; it will display all the

Example: MRM_TRANSACT_DEFAULT (BADI name, Use SE18 to see the BADI attributes)

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 8

Steps for Finding User

4) As our intention is to find a BADI, when the save button is clicked in MIRO. Enter all the required information and press SAVE, as shown

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 9

Steps for Finding User

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 10

Make use of the relevant BADI that suits your requirement. Here in this Scenario will fulfill the requirement.

&

"

'

"

&

5) It will stop you in debugging mode; by pressing F8 it will show all MIRO save option.

BADI

Steps for Finding User

Related Content
www.help.sap.com For more information, visit the ABAP homepage

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 11

Steps for Finding User

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is not supported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade. SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document, and anyone using these methods does so at his/her own risk. SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article or code sample, including any liability resulting from incompatibility between the content within this document and the materials and services offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of this document.

SAP COMMUNITY NETWORK 2011 SAP AG

SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com | UAC - uac.sap.com 12

Steps for Finding User