Beruflich Dokumente
Kultur Dokumente
Enhancements are the means by which we add our own/ modify existing functionality to SAP's
standard business applications.
Generally when we try to modify or change the SAP standard Program, it will ask u Access key
which you can get from SAP market place by requesting SAP.
But coming to enhancements, normally dont ask any Access key and can be implement directly.
There are 4 ways of doing enhancements in SAP:
1. User exits
2. Customer exits
3. BADI's
4. Enhancement Frameworks
User exits
These are technically modifications. SAP provides many subroutine(s) with name USEREXIT_ * (i.e
ex: FORM USEREXIT_001)
These are saved in many includes which can be found via SE80 >> Search for Package VMOD.
These are also called as Form exits.
Custom coding can be done in the subroutine. But the main disadvantage of these exits is, It
requires Access key and only SD module supports this kind of enhancements.
Function exits
Customer exits:
Menu Exits
Screen exits
Function exits
Provided by means of FMs (Function modules) .The code for the function module is written
by the developer. You are not writing the code directly in the function module, but in the 'Z'
include that is implemented in the function module.
Ex: open any Function module EXIT_* in se37
It will have a Z include file, just edit the file directly. No Access key required.
Menu Exits
Enhances the menu available in standard SAP program. Developer can add his/her own text
and logic for the menu. Function codes for menu exits all start with "+".
EX: Format: +CUS (additional item in GUI status)
Screen Exits
Used to enhance the screen, add elements in screen etc.
Format: CALL CUSTOMER-SUBSCREEN CUSTSCR2.
BADI's
Business Add-Ins may be simply defined as an object-oriented extension of the SAP
enhancement technique. Multiple implementation for same BADI can be done as BADI
supports encapsulation of data.
Classical are the old ones which you can see and implement thru SE18. Kernel Badi's belong to the
new enhancement frame work. These can be viewed both in SE18 and SE19. The main difference is
that Kernel Badi's belong to an enhancement spot but classical badi's are stand alone Badi's.
Calssical Badi's:
1. SE18
Kernel Badis:
1. SE18/SE19
2. Called thru GET badi and CALL Badi.
3. Execution is faster than the classical Badi.
4. Are always assigned to an enhancement spot.
Enhancement Frameworks:
This is the new kind of enhancement technique provided by SAP. These provides some hooks or
places where custom logic can be coded in the standard program.There are 2 kinds of Enhancement
frameworks:
a) Implicit and
b) Explicit Enhancements
In order to understand the enhancement framework, you need to understand the terms used in
SAP and their hierarchy.
1. Enhancement Spot.
2. Enhancement point/Enhancement Section
3. Enhancement Implementations.
4. Kernel Badi
Spot: is nothing but a container for the points/sections. Assume something like a transport which
holds different objects. The objects that the spot hold will be either a point/section/kernel Badi or a
combination of these.
Points are the actual enhancements. These can be implicit point or explicit point.
Implicit: are always available in any SAP programs (programs/includes/FMs etc). Right click enhancement operations - show implicit enhancements. You have to click on the spiral icon to modify
these implicit enhancements.
Explicit points are those that are provided by SAP. These are defined by the SAP programmer.
Something like a customer exit. The SAP programmer has assigned this to an spot.
Section: Similar to explicit. These are defined by SAP and assigned to a spot. The difference
between explicit point and section is that, when you implement a section, the existing code in the
section by SAP will be replaced by the customers code. In case of EP, both SAPs and customers
code are executed.
Enhancement implementations are the actual implementations that we create inside a point/section.
*&---------------------------------------------------------------------\*
*& Report ZZ_EXIT_FIND
*&
*&---------------------------------------------------------------------\*
*&
*&
*&---------------------------------------------------------------------\*
REPORT ZZ_EXIT_FIND.
*&---------------------------------------------------------------------\*
*& Enter the transaction code that you want to search through in order *
*& to find which Standard SAP User Exits exists.
*& Tables
*&---------------------------------------------------------------------\*
TABLES : tstc, "SAP Transaction Codes
tadir, "Directory of Repository Objects
modsapt, "SAP Enhancements - Short Texts
modact, "Modifications
trdir, "System table TRDIR
tfdir, "Function Module
enlfdir, "Additional Attributes for Function Modules
tstct, "Transaction Code Texts
RSSTCD,
TRKEY.
*&---------------------------------------------------------------------\*
*& Definition of Types
*
*&---------------------------------------------------------------------\*
TYPES: BEGIN OF t_badi_list,
obj_name TYPE sobj_name ,
devclass TYPE devi_class ,
dlvunit TYPE dlvunit,
imp_name TYPE exit_imp ,
packname TYPE devclass ,
dlvunit2 TYPE dlvunit,
text TYPE sxc_attrt-text,
END OF t_badi_list.
TYPES: BEGIN OF t_badi_list2,
obj_name TYPE sobj_name ,
devclass TYPE devi_class ,
dlvunit TYPE dlvunit,
END OF t_badi_list2.
*&---------------------------------------------------------------------\*
*& Data Declaration
*
*&---------------------------------------------------------------------\*
vline.
WRITE:/(95) sy-uline.
LOOP AT jtab.
SELECT SINGLE * FROM modsapt
EXCEPTIONS
ACTION_CANCELED
ACCESS_FAILURE
BADI_NOT_EXIXTING.
ELSE.
ENDIF.