The document discusses different types of customer exits in ABAP including function module exits, screen exits, menu exits, and field exits. It provides examples of using each type of exit to customize the standard transaction code CO11N. Specifically, it demonstrates how to add a new sub-screen to collect HR data using a screen exit, and how to validate a field using a field exit. The steps shown include searching for existing exits in SE38, creating new function module and screen exits, and setting validation for a field using transaction RZ10 and program RSMODPRF. It cautions that customer exits may impact multiple standard transactions so careful testing is needed.

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.

5. CO11N Standard Screen

6. Required Screen

7. Searching the Function Exits
• First take the program name of the standard transaction
code.
• Now come to se38 and give that name to check package

10. STEP I
Tcode SMOD

11. STEP II

12. STEP III

13. Dbl click

14. STEP IV

15. Dbl click
STEP V

16. Dbl click STEP VI

17. STEP VII

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

22. Press Enter

23. Dbl click
Required Screen

24. Dbl Click
Required Screen

26. • Now come to SMOD and proceed as
STEP I and STEP II

29. HOW TO FIND SCREEN EXIT
• Proceed as mentioned in STEP I and
STEP II

32. Process flow
• Do as per STEP IV

33. Dbl click

34. Click
Here

36. CMOD

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.

42. STEP I
Transaction code
RZ10
Click

44. STEP II
Press Display Or
Change

45. Check the parameter value
If it is not there create
the new parameter

46. Press

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

49. Press Execute

50. Execute

51. Press create to create your
function module and
activate

52. Now again come to se38 initial screen and run RSMODPRF
and execute it in the selection screen don’t define any data
element

53. Execute

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

59. THANK YOU