User Exits

  • Uploaded by: meghagoyal
  • 0
  • 0
  • June 2020
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View User Exits as PDF for free.

More details

  • Words: 510
  • Pages: 59
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

Different types of Customer exits The main customer exits are • Function Module exits • Screen exits • Menu exits • Field exits

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

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.

CO11N Standard Screen

Required Screen

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

STEP I Tcode SMOD

STEP II

STEP III

Dbl click

STEP IV

Dbl click

STEP V

Dbl click

STEP VI

STEP VII

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

Press Enter

Dbl click

Required Screen

Dbl Click

Required Screen

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

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

Process flow • Do as per STEP IV

Dbl click

Click

Here

CMOD

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.

Click

STEP I Transaction code RZ10

STEP II Press Display Or Change

If it is not there create the new parameter

Check the parameter value

Press

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

Press Execute

Execute

Press create to create your function module and activate

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

Execute

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

THANK YOU

Related Documents

User Exits
November 2019 11
User Exits
June 2020 7
Finding User Exits
June 2020 3
Exits
November 2019 11
Menu Exits
November 2019 12
Field Exits
November 2019 12

More Documents from ""