chapter 01_user exit and badi

8/10/2019 Chapter 01_User Exit and BADI

1/39

IBM Global Business Services

IBM Corporation 2013User Exits | Dec-2008

User Exits


2/39


IBM Corporation 20132 Dec-2008User Exits |

Objectives

The participants will be able to:

Discuss benefits to use User Exits

Different types of user exits.

Locate, code and implement User exit.

Identify Projects and Enhancements and use the transactions CMOD and SMOD.


3/39


4/39



Overview

There are some requirements which are not fulfilled by Standard Sap functionality.

To Avoid making changes in Standard functionality, SAP provided some exits

to accommodate custom functionality.

Exits allows you to write own development and allow to change SAP functionality

tosuityourneeds.

Since they do not affect the source code and are named as per the SAP naming

convention, they do not affect future software upgrade.

If appropriate exit is not available as per your requirement, then it is mandatory to

register SAP standard Object and get its access key to make changes.

To obtain the access key for changing a SAP Standard object, either run transaction

OSS1or go to the site www.service.sap.com.


5/39



Different Enhancement Techniques

SAP 3 Tier Architecture

PRESENTATION :

Screen Exits

Menu Exits

APPLICATION:

Program exits ( Function Exits, BAdis, Business

Transaction Events, Substitution Exits, Enhancement Spots)

DATABASE

Append Structure


6/39



Information on existing User-Exits

Using transaction SPRO, one can get detailed documentationon the Exits available for areas of concern.


7/39



Function-Exits

*------------------------------

----*

* include zxf05u01.*

*------------------------------

----*

This INCLUDE

program is where youwill write the

customer-specific

code.

call customer-

function 001...

function

exit_sapmf02k_001.

include zxf05u01.

endfunction.

SAP Original Code

SAPMF02K

Function Module INCLUDE Program

This INCLUDE program

will not be overwritten

with an SAP upgrade

because it is not SAP

original code.


8/39



Call Customer-Function Versus Call Function

The CALL CUSTOMER-FUNCTION

statement will only execute the

function module if the related

enhancement is Active.

call function EXIT_SAPMF02K_001

Both of these CALL statements refer

to the same function module

EXIT_SAPMF02K_001.


9/39



Business Case Scenario

UPDATE LOG

Vendor #Vendor name

When the user updates a vendor record, you want toinsert a record into an update log that contains the

vendor number and name of the updated record.


10/39



Steps to Coding a Function-Exit

1. Locate Function-Exit(s)

2. Go to Function Module

3. Create INCLUDE Program

4. Code in INCLUDE Program

5. Activate Function-Exit


11/39



Locate Function-Exit(s)

Open Main Program of Transaction Code to search function Exits


12/39




In main program SAPMF02K,

search for the string call

customer-function to find all of

the function-exit(s) in the main

program.


13/39




Double-click anywhere on

the call customer-function

001 statement to go to

that line in the SAP program.


14/39



Go to Function Module

Double-click on 001 of the

CALL CUSTOMER-FUNCTION

001 statement in the SAPprogram to go to the function

module EXIT_SAPMF02K_001.


15/39



Create INCLUDE Program

Double-click on the INCLUDE

ZXF05U01 statement in the

function module to create the

INCLUDE program.


16/39



Code in INCLUDE Program

*------------------------------

* INCLUDE ZXF05U01

*------------------------------

if sy-uname = SANGRAMC.

endif.

Write code in the include program. Whatever logic you add here will affect all

SAP standard transaction where this

particular User Exit is being called.

Put all your code within the username

check, while you are at the middle of theuser exit development. So, that your logic

in the exit (which is incomplete now) does

not affect others users in the system.

At the end of the development, when you

have tested that your logic is correct,

remove the username check. So, the

additional logic (tested & verified now) is

now triggered for all users in the system.


17/39



Activating Function-Exit

X

X

PROJECT 1

(can be activated/deactivated)

Enhancement

1

Enhancement

2

Function

Exit

Screen

Exit

Function

Exit

PROJECT 2

(can be activated/deactivated)

Enhancement

3

Function

Exit

You do not actually activate a single function-exit; instead, you activate aPROJECT that will include your user-exit(s).


18/39



User-Exit Transactions

CMOD: This transaction allows you to create a PROJECT by identifying itsENHANCEMENT(S). After determining all of the ENHANCEMENTS that are part

of the PROJECT, you will have to activate the PROJECT. Till you activate PROJECT

logic written in function exit will not execute.

SMOD: This transaction allows you to create an ENHANCEMENT, which you willinclude in a PROJECT, by identifying its COMPONENT(S). In many case SAP

has already created an ENHANCEMENT for its pre-defined user-exits, in this case

you will not need to use transaction SMOD; instead, you can direct add enhancemen

in PROJECT using transaction CMOD.


19/39



Transaction CMOD

In transaction CMOD, type yourproject name and press the

CREATE pushbutton.

IBM Gl b l B i S i


20/39



Transaction CMOD

Once you SAVE your project,

you can add as many

enhancements as you want by

pressing the SAP

enhancements pushbutton.

IBM Gl b l B i S i


21/39



Transaction CMOD

Add the enhancements you

want included in

the project.


22/39

IBM Gl b l B i S i


23/39



Transaction SMOD

With the name of the enhancement,

you can display its components.



24/39



Transaction SMOD

In the case of enhancement

SAPMF02K, there is only one

user-exita function-exit using

the function module

EXIT_SAPMF02K_001.



25/39



Additional Information

You can use table MODACT to find the Project an Enhancement is included in.You can use table MODSAP to find the Enhancement for a Function Exit.

Component or Function ExitEnhancement Name



26/39



Summary

You should avoid making modifications/repairs to SAP objects/code wheneverpossible.

It mandatory for users to register all manual changes to SAP source coding andSAP Dictionary objects through a procedure called SSCR.

Function exit, screen exit and Append structure are different types of exits inSAP.

CALL CUSTOMER-FUNCTION statement will only execute a exit functionmodule if the function module is activated.

CMOD: This transaction allows you to create a PROJECT by identifying itsENHANCEMENT(S).

SMOD: This transaction allows you to create an ENHANCEMENT, which you will

include in a PROJECT, by identifying its COMPONENT(S).



27/39



Questions

How do you obtain access key for changing a SAP standard object ? What are the steps for coding a Function Exits ?

What does CMOD and SMOD do ?


28/39



29/39



Objectives

The participants will be able to: Describe Business Add-Ins and their advantages over User Exits.

Analyze definition and Implementation of BAdi (Classic BADI) through transactions

SE18 and SE19.

Find Business Addins for a particular SAP transaction (if it has a BAdi).



30/39



What is BAdi

Business Add-Ins are a new SAP enhancement technique based on ABAPObjects. (It has Interfaces & Methods)

Business Add-Ins should be considered generalized Business Transaction Events

that can be used to bundle program, menu and screen enhancements into a

single add-in.

Business Add-Ins have two parts: One is the Definition and the other is itsImplementation. The definition can either be SAP provided or user may also

create it.


31/39



32/39



BAdi : Where to Find

Look for BAdi definition in IMG and in component hierarchy. (using transactionSE18)

Create own implementation of the add-in (complete coding for Methods) and

activate. (using transaction SE19)

Enhancement's active components are called at runtime.



33/39



BAdi Definition (SE18)Classic BADI

In the Definition view, an application programmer predefines exit points in asource that allow customers to attach additional software to standard SAP source

code without having to modify the original object.

To define a BAdi use Sap Menu -> Tools -> ABAP Workbench -> Utilities ->

Business Add-Ins -> Definition (transaction SE18).

Call the interface at the appropriate point in application program, where you want

to provide an exit to the customer

Customers can then select the add-in and implement it according to their needs



34/39



BAdi Implementation (SE19)Classic BADI

In the Implementation view, the usersof Business Add-Ins can customizethe logic they need or use a standardlogic if one is available.

Find the suitable Business Add-Ins

present in system (Use IMG orComponent hierarchy)

Use Add-Ins Documentation tounderstand functionality & to decidewhich Definition to implement.

Use SAP Menu ABAP Workbench->Utilities -> Business Add-Ins ->

Implementation (transaction SE19)



35/39


BAdi Implementation : Sequence of steps

1. Find the corresponding BAdi for the SAP transaction2. Create a custom Implementation for the BAdi

3. From the methods available in the BAdi and select the appropriate method

4. Enter custom code in the method and activate

5. Execute SAP transaction and test if method with custom code is being invoked


36/39



37/39


Implement Method

Select correct method from implementation and write your own code using BADIparameters.

Activate implementation. This is mandatory as till then new implementation is not

executed by SAP.

Methods and Parameters


38/39



39/39

Questions

What are BAdis ? Which transactions are used for BAdi Definition and Implementation ?

How do you locate BAdis defined by SAP for a SAP standard transaction ?

chapter 01_user exit and badi

Documents