Professional Documents
Culture Documents
1. Customer Exits.
2. Business Transaction Events (BTE).
3. Enhancement frame work.
4. User Exits.
5. Business ADdIns (BADI).
6. Functional Routines
1).Customer Exits:
Customer Exits are available in most of the functional areas such are SD- Sales
and Distribution, Material Management (MM), Finance and Controlling (FI/CO)….
Etc.
They are used to add the additional functionalities in the standard applications or
programs, without using access key to break them.
Access key:
It is the unique key provided by the basis consultant or SAP People to break the
standard applications or programs.
The application or program will become custom development once they
are broken.
a) Field Exits.
b) Function Exits.
c) Menu Exits.
d) Screen Exits.
a).Field Exits:
They are used to change the field labels of the standard data elements.
b).Function Exits:
They are used to add an additional functionality to the standard applications or program
without breaking them.
BY MR. BABU (OASIS TECHNOLOGIES)
Each Function Exit contain a custom include program which starts with Z* to
implement the customer specific additional business logic.
The Function Exit is the three digit number which is called using the ABAP
statement
CALL CUSTOMER_FUNCTION.
Ex:
*Function Exit
IMPORTING
im_param =
..
TABLES
FUNCTION <funct_exit_name>.
Z<INCLUDE_NAME>
SELECT….
ENDFUNCTION.
Note: In the real time we mostly work with function exits.
c).Menu Exits: They are used to add the custom specific menu items and
corresponding additional functionality based on the selected menu item.
d).Screen Exits: They are used to add the additional screen elements and the
corresponding additional functionality to the standard screens, or application or
transaction codes.
The T-Code SMOD and CMOD is used to work with the Customer Exits.
T-Code SMOD: It is used to find the Customer Exits of the standard package.
Note: It is not possible to assign an enhancement or exit to more than one project.
BY MR. BABU (OASIS TECHNOLOGIES)
Different ways to find Exits: Following are different ways to find Exits.
a)Finding Packages:
Ex: VA02/VL02.
Ex: VA/MGA…
Click on execute.
2) Find the correct exit by analyzing the system given short text or by using
Note: All the Exits which are called using the statement
Note: Set the session break points for all the found locations up to 30 only at a time.
Perform the required action in the T-Code to stop the correct Exits.
The standard table MODSAP or MODACT can also be used to list out the
enhancement projects.
Scenario on Field Exit: Change the field table of the standard data element
DWERK_EXT – Deliver plant in the T-Codes VA01, VA02, VA03.
2. Finding Exit:
Execute the T-Code SMOD.
Click on utilities menu item.
Enter the required found package name.
Ex: SEDT/MGA/VA…..
Click on execute icon.
Click on find icon.
BY MR. BABU (OASIS TECHNOLOGIES)
Enter the required find string.
Ex: Attributes/check/save/function.
Press enter button.
Copy the font Exit names by pressing (Ctrl + Y).
Cancel the find windows.
Click on back.
Note: 1.Color of the traffic light will become green, once the project is activated.
Red – Inactive.
Green – Active.
2. The tick marks are appeared under Impl. Column once the Exits are Implemented.
Note: Follow the similar steps to implement any number of Exits by double
clicking on them.
Scenario on MENU Exits: Add an additional custom menu item and the
corresponding additional functionality to the standard T-Code MC94 – Change plan.
2. Find Exits:
3. Project Creation:
Note: 1.An Icon undo activation is used to de-activate the enhancement project.
2. Click on back icon then use activate icon in case of not appeared in the
Components Screen.
Note: Press enter button then create an include program name for the first time.
Note:- The additional functionality such as call another T-code (SE11) is happened
Scenario on Screen Exits: Add the additional screen fields with the transaction
code MP01 (Maintain Approved manufacture parts).
Once the package name of the application or T-code is found then execute
SMOD.
Click on utilities menu item.
Click on find icon.
Enter the required found package name (ME).
Click on execute icon.
Click on find icon.
Enter appropriate find string (screen).
Press enter button.
Click on required found string.
Read the system given short text.
Copy the found exit name.
Note: -- Activate and Deactivate project in an initial screen of CMOD if they are not
appeared.
Double click on the system provided sub screen number of screen exit.
Press enter button.
Enter short description.
Click on layout button.
Click on dictionary or program fields windows (F6).
Enter the required table or structure name.
Ex: AMPL
Select the required additional field.
Ex: MATKL
Press enter button.
Place if on the screen by pressing left mouse button.
Click on activate icon.
Enter the package name.
Click on save icon.
Click on yes button.
BY MR. BABU (OASIS TECHNOLOGIES)
Click on the button maintain original language.
Click on back.
Click on flow logic and add the additional functionality.
Note: -- Use the system provided for exits.
Make sure the screen type ‘Sub screen’ is selected under attributes tab while
defining the sub screen.
The Business Transaction Events are also called Source code plug-ins to add an
additional functionality in the standard program or T-Code.
Each BTE is linked with the system provided interface to which the custom
function module can be assign.
The BTE are called using the function
OPEN_FI_PERFORM* and OUTBOUND_CALL*.
Ex:--
Standard program.
.
CALL FUNCTION ‘OPEN_FI_PERFORM
(or) OUTBOUND_CALL’…
BTE-0001490
ZCUSTOM_FUNCTION
The T-Code BERE and FIBF are used to work with BTE’s.
BY MR. BABU (OASIS TECHNOLOGIES)
T-Code BERE: It is used to find the BTE’s.
Scenario on BTE: It gives an information message while saving the vendor data (or)
sends a purchase order as a PDF attachment to an Email of the vendor.
T-code—XK02/XK01
Tables – LFA1/LFB1
Find BTE:
TO FM: ZB20_CUST_INTERFACE_00001400
*Give message.
1. Create Product:
They are pre coded by SAP and provided at the specific location in the standard
programs.
There are two types of Explicit Enhancement.
1. ENHANCEMENT-SECTION.
2. ENHANCEMENT-POINTS.
1. ENHANCEMENT-SECTION:
It is used to copy, change the existing standard source code and add additional
business logic to the standard program.
BY MR. BABU (OASIS TECHNOLOGIES)
The ABAP statement ENHANCEMENT-SECTION is used to specific the
enhancement sections.
2. ENHANCEMENT-POINT:
It is used add or plug-in the additional customer specific business logic to the
standard program.
Make the physical file path name in the standard migration program.
Ex: RMDATIND/etc.
Note:-- The system inserts the double coated lines (“ ” ” ”) in the certain locations
in the standard program.
Right click on the system inserted double coated line at the required location
such as beginning of the program or end of the program or end or beginning of
the subroutine… etc.
Click on enhancement implementation.
Click on create.
Click on create enhancement implementation icon (F8).
Enter the enhancement implementation name.
Enter short text.
Click on yes button.
Enter the package name.
Click on save icon.
Create TR by pressing create request icon.
Click on yes button.
Select the created enhancement name.
Click on yes button.
Implement the required customer specific additional business logic within the
system generated statement.
BY MR. BABU (OASIS TECHNOLOGIES)
Ex: -- “”””””””””””””””””””””””””””””””””””””””””””””””
ENHANCEMENT <n> <ZB20_IMPLICIT_ENHANCEMENT>
*Implement customer specific additional business logic
AT SELECTION-SCREEN OUTPUT.
LOOP AT SCREEN OUTPUT.
LOOP AT SCREEN.
IF SCREEN-NAME = “%%%_PHY”.
SCREEN-REQUIRED = ‘1’.
MODIFY SCREEN.
EXIT.
ENDIF.
ENDLOOP.
ENDENHANCEMENT.
Click on activate enhancement buttons.
Press enter button.
Change the default value for an input field “Transactions per commit unit from
500 to 1000” in the standard report (RMDATIND) material master data upload.
Once the standard program is in display mode.
Right click on the system provided explicit enhancement section or point.
After an icon enhance is pressed.
Click on enhancement implementation.
Click on create.
Click on create enhancement implementation (F8).
Enter enhancement implementation name.(ZB20_EXPLICIT_ENHANCEMENT)
Enter short description.
Click on yes button.
Click on save icon.
Create the TR by pressing create request icon.
Click on yes button.
Select the created enhancement implementation name.
Click on yes button.
Implement the required customer specific additional business logic.
Note:-- Change the existing standard source code in case of enhancement
section.
BY MR. BABU (OASIS TECHNOLOGIES)
Sample:
“or ENHANCEMENT-SECTION
*$*$....start : BMVDEF00_03….
ENHANCEMENT 30 ZB20_EXPLICIT_ENHANCEMENT
MAX_COMM = 1000.
ENDENHANCEMENT.