User Exits

AGENDA
hIntroduction
hSD user exits Orders, Delivery, Billing, Pricing
hCustomer Exits Overview
hProjects / Enhancements
hBTEs

DESIGN APPROACH

OBJECTS TECHNICALLY

USER EXITS
User exits are a type of system enhancement that were originally
developed for the R/3 SD.
The SAP developer creates a special include in a module pool.
These includes contain one or more subroutines that satisfy the
naming convention userexit_<name>. The calls for these
subroutines have already been implemented in the R/3 program.
A user exit is considered as a modification, since technically
objects in the SAP namespace are being modified.
After delivering them, SAP never alters includes created in this
manner; if new user exits must be delivered in a new release, they
are placed in a new include program.

CONVENTIONAL USER EXITS IN SD

2 well known includes having conventional user exits in SD are MV45AFZZ and
MV45AFZB.
Most notable user exits available are as follows
MV45AFZZ
USEREXIT_FIELD_MODIFICATION To modify screen attributes
USEREXIT_SAVE_DOCUMENT To perform operations when user hits Save
USEREXIT_SAVE_DOCUMENT_PREPARE Document number not yet generated
USEREXIT_MOVE_FIELD_TO_VBAK When user header changes are moved to
header work area.
USEREXIT_MOVE_FIELD_TO_VBAP When user item changes are moved to SAP
item work area
MV45AFZB
USEREXIT_CHECK_VBAK Header check
USEREXIT_CHECK_VBAP Item Check
USEREXIT_SOURCE_DETERMINATION Plant / Item category determination

CONVENTIONAL USER EXITS IN SD CONTD

SD Pricing User Exits
Include LV69AFZZ has pricing user exits
USEREXIT_FIELD_MODIFICATION To modify screen attributes in pricing
screen
USEREXIT_PRICING_CHECK To check user entered pricing details

Delivery Note User Exits

Includes MV50AFZ1, MV50AFZZ have delivery note user exits.
USEREXIT_SAVE_DOCUMENT
USEREXIT_SAVE_DOCUMENT_PREPARE
USEREXIT_LGORT_DETERMINATION Determine storage location

Billing User Exits

Includes RV60AFZC
USEREXIT_FILL_VBRK_VBRP Fill fields at billing document header / Item

REAL TIME SCENARIOS

AUTOMATIC DELIVERY BLOCK SETTING IN SALES
ORDER CREATION
NEW FIELD IN THE SALES ORDER SCREEN

Q&A ?

CUSTOMER EXITS

TYPES OF CUSTOMER EXITS

h There are three main types of customer exits: function module exits, screen exits and
menu exits
Function Module Exit: allows customer to add code via a function module at a specific location in an
SAP application program
Format:

CALL CUSTOMER-FUNCTION '004'

Menu Exit: allows customer to add items to a pull down menu in a standard SAP program. These
items may be used to call add-on programs or custom screens.

Format:

+CUS ( additional item in GUI status )

Screen Exit: allows customer to add fields to a screen in an SAP program via a subscreen. The
subscreen is called within the standard screens flow logic.

Format:

CALL CUSTOMER-SUBSCREEN CUSTSCR2

OBJECT HIERARCHY

LOCATING CUSTOMER EXITS

1.Method 1 : Execute the transaction and enter in to

debugging mode -> keep a break point at statement
CALL CUSTOMER-FUNCTION .
2.Method 2 : Global search for statement CALL CUSTOMERFUNCTION in the main program .
3.Method 3 : SMOD Browse project .
4.Method 4 : SE81 Browse application area .
5.Method 5 : Repository Information system ->
Enhancements -> Customer Exits tree and double-click
Enhancements entry.

SAP PROJECTS - CMOD

h CMOD Vs SMOD
h SMOD provides the list of actual enhancements
h CMOD provides customers to create custom projects and to
activate / deactivate these enhancements.

h Using CMOD
h Assign enhancement packages to the project via the
Enhancement Assignment option.
h Each enhancement package may be assigned to only one
project
h When activating/deactivating a project, every implemented
component of each assigned package will be affected

REAL TIME SCENARIO

Inbound IDOC Scenario

Q&A ?