User Exit Documentation

User Exits are a method whereby the end user can add extra functionality or change to a certain degree the way that SAP performs certain functions. How are they implemented ? User Exits are implemented in such a way that unli e changes to SAP standard code! they will sur"i"e across upgrades and hot pac applications. #hey are also User $b%ects and can therefore be implemented without the need of re&uesting an SS'( from SAP. )ithin the standard SAP programs at ey points are calls to function modules starting with *E+,#-*. #hese function modules generally accept as input parameters structures containing for example the entire $rder Header ./0A12 of the sales order %ust entered! or perhaps a table of the $rder ,tems. #hese function calls are placed at points such as %ust before the $rder is sa"ed or %ust before it is printed and so on.
S.Sath"i Page 1 of 6

User Exit Documentation

#hese function modules contain a single include statement. #he name of this include is in the User domain and starts with 3. #his enables it to be edited without the need for an SS'( and also pre"ents it being o"erwritten during upgrades. $nce this include has been created and acti"ated! and the user exit is acti"ated the User exit becomes functional. ,mplementing a User Exit. User Exits are implemented using the transaction code *S4$D*. Enter this in the command line and press the Enter ey. #his will then show the S4$D parameter screen5 .Embedded image mo"ed to file5 pic67879.%pg2 User Exits are assigned a pro%ect name which begins with 3. Ha"ing entered the rele"ant name in the *Pro%ect* field! clic the 'reate .or 'hange2 button as applicable.
S.Sath"i Page 2 of 6

User Exit Documentation

)hen you are creating a new pro%ect! the pro%ects attribute screen will be displayed. #his allows you to enter a title for the pro%ect and allows access to the Enhancements .User Exits2 that you want to assign to the pro%ect and the components that you wish to use within those enhancements. #his screen allows you to enter a description of the pro%ect. $nce you ha"e done this! clic the sa"e button. :ou will be as ed as usual to assign a de"elopment class and create a transport. $nce the transport has been created you can then go on to assign the enhancements that you wish to use to the pro%ect. ;ocating #he Enhancements <or A Pro%ect. Unfortunately , ha"e access to a =.>' system only so therefore this description is based around that. #o find enhancements for a particular program locate the De"elopment 'lass
S.Sath"i Page 3 of 6

User Exit Documentation

for the rele"ant program. (un the transaction and on the first input screen clic on the Status button. #his pro"ides the program name. Another method of finding the program name is to use transaction SE7? which is the 'reate@4odify #ransaction transaction. Enter the transaction code and clic display. ,n either case! cut the program name and then enter it into transaction SE?8 ? the A0AP program editor. Select the *Attributes* radio button and clic display. Aote the De"elopment 'lass. ,n =>'! go bac to the S4$D main screen! enter the pro%ect name and select the *Enhancement Assignment* radio button. 'lic the change button. #his will display the enhancement assignment screen. Position the cursor in the first field and press the B<=C ey. #his will display the ,nput Help personal list window! a standard window that you should be familiar with. 'lic the *,nformation System* button and
S.Sath"i Page 4 of 6

User Exit Documentation

enter the de"elopment class located abo"e into the de"elopment class field. 'lic the green tic . .Embedded image mo"ed to file5 picD9==E.%pg2 #his will display a list of enhancements for that particular de"elopment category with a short description of what they do. .Embedded image mo"ed to file5 picF6EF>.%pg2 Select rele"ant description which will be transferred bac to the Enhancement Assignment screen. <or "ersions other than =>'! use transaction SE?E which is the <unction 4odule editor! in the function module name field press the B<=C ey and select further options. $ne of these will be the de"elopment class. 'lic ing the enhancement button pro"ides information on the enhancement. #he information displayed in this report includes whether the enhancement
S.Sath"i Page 5 of 6

User Exit Documentation

has been implemented! and is acti"e. .Green things scattered throughout the report2. 'lic ing the Exit name .,n this case *E+,#-SAP;/>DA-DDF* will display the rele"ant function module5 #o create the enhancement! double clic the ,nclude name. #his then ta es you into SE?8 where you can edit the include to your hearts content.

S.Sath"i

Page 6 of 6