1. CUSTOMER EXITS
Bonus material for 201 ABAP Interview questions
http://www.201interviewquestions.com/books/abap.htm
Material Code : BM01
Author : P.Renjith Kumar
Genie Press
2. Different types of Customer
exits
The main customer exits are
• Function Module exits
• Screen exits
• Menu exits
• Field exits
3. Purpose of Exits
Function Module Exits
• Generally for making the validation in the standard transaction code
field(s)
Screen Exits
• For adding the sub-screen in the standard transaction code
Menu exits
• To enable or disable the menu-bar in standard transaction code
Field exits
• To validate a particular screen field in standard transaction code
4. Dummy Project
Transaction code CO11N.
Requirements
• Add a new sub-screen to give the provision to user for
entering the HR data and save in standard table to show
the information in COOIS standard transaction code.
• Validate the field Execution start date should not be more
than 1 week from today’s date.
19. ANOTHER WAY TO FIND FUNCTION MODULE EXITS
• Go to se38 and give the program name and click the
menu utilities find in source code
• Now give Call customer in the search string
• And process as next slide
41. Field exits
• Go to transaction code RZ10 and check in instance profile
whether abap/fieldexit parameter value is yes or not.
• Now go to standard transaction code and take the data
element , screen name and screen no
• Now come to se38 run the program RSMODPRF.
47. Now come back and save the profile
• Now go to standard transaction code and take the data
element, screen name and screen no
• Here the standard transaction code is CS03
58. Caution and conclusion
• There is a chance that any customer exit is associated
with several number of standard transaction code. So if
any transaction code is not satisfying your requirement
deactivate the enhancement and proceed for the next
search
• It is a very sensitive programming area so it is necessary
for every programmer to take care of that by which
conflicts between standard and customization can be
avoided