Agenda

Concepts and Brief Introduction – Dharmaraj

Table & Text Enhancements - Dharmaraj

Types of Exits with Examples - Dharmaraj

Exits in SD Module - Rajesh Sujir

Exits in FI/CO- BTE- Rajesh Sujir

PP - BOM Demo (Screen Exit)- Anilkumar C

White paper Document – Anilkumar C 1

Concepts and Brief Introduction
By
Dharmaraj M

2
Objectives

 Understanding Enhancement and

User-Exits.
 Levels of Changes.
 Enhancement concept for programs,
screens, tables, data elements,
texts.

3
Overview of Changing the Standards

4
Definition - Enhancement
 As opposed to the term "modification", an addition
to an R/3 standard program made via a user exit
provided for making such additions. An
enhancement does not change R/3 Repository
objects. With the ABAP Workbench you can develop
any R/3 Repository objects you might need.
Enhancements are not affected by upgrading to a
new release.

5
Application Enhancement

SAP Application Enhancements

SAP Customer

Application
develops functions uses

Enhancement
defines components edits

puts together Application activates

enhancements

 SAP AG

6
Customer Enhancement

Customer Enhancement Projects

SAP Customer

Defines Defines
SAP enhancements enhancement projects

SMOD CMOD

 SAP AG

7
Enhancement Projects
SAP Enhancements and Customer Enhancement Projects

SAP Customer
K K E

E
P

K K E

K E
K

E P

K E
K
K

K E

K
R

K Component E SAP enhancement P Customer enhancement project

 SAP AG

8
Decision

9
Levels of changes

 There are four different ways of

changing the SAP system to fit
your needs
• 1) Customizing.
• 2) Modification.
• 3) Enhancement Concept.
• 4) Custom Development

10
Customizing
 Configuration of system parameters
via a special user interface (the
possible changes are preplanned
and organized by SAP)

11
Modification
 Alteration of SAP Repository objects
in the form of custom changes.
When SAP changes occur, the
customer version and the new SAP
version must be reconciled
manually.

12
Enhancement
 Changing of SAP Repository objects
by the customer without
modification

13
Customer Development
 Creation of custom objects within
the customer name range.

14
Definition-User Exit
 User Exits are empty shells residing in the
standard SAP programs which the
customer can use for his specific
requirement.
 They act as hooks where you can attach
or "hang" your own add-ons which may
be piece of code, a screen, help
documentation or even a menu status etc.
15
Types of User Exit
 User Exits are broadly of the following
types –
• Screen Exits.
• Menu Exits.
• Function module exits.
 Apart from these 3 features there are a
few more exits and each one of them
are dealt separately

16
How to Find Exits
 Information Systems-SE81.
 SMOD
 BADI
 Business Transaction Events (BTE)
 From Main Program especially SD
 SPRO.

17
Enhancements in FI Module
 Business Transaction Events (BTE)
 allow you to attach additional components, in
the form of a function module.
 Have predefined interfaces allowing customer
access.

18
Implementation Procedure

Implementing Enhancements in Customer Systems

Put together an E E
enhancement project
using SAP enhancements P

Function modules
Edit the enhancement
project’s components
Menu entries

Subscreens

Customer documentation:
Document the
enhancement project

Activate the R

enhancement project Activation

 SAP AG
19
The following are not allowed in
User Exits:
 CALL SCREEN, CALL DIALOG, CALL
TRANSACTION, SUBMIT
 COMMIT WORK, ROLLBACK WORK
 COMMUNICATION RECEIVE
 EXIT FROM STEP-LOOP
 MESSAGE I, MESSAGE W
 external PERFORM

20
Enhancements….?

The End

21
Creation Procedure

The SAP Enhancement Creation Procedure

Function module exits
Define customer exits
in application functions
Menu exits

Screen exits

Combine components to
form SAP enhancements C E

Document SAP documentation:

enhancements R

 SAP AG

22