SAP Enhancements: - Bhavannarayana .S

SAP
ENHANCEMENTS
-Bhavannarayana .S
1
Enhancements
1. User Exits
2. Customer Exits
2.1 Menu
2.2 Screen
2.3Field
3. Badi(Business Add Ins)
3.1Classical
3.2 kernel
4. Implicit / Explicit Enhancement
5. BTE(Business Transaction Events)
2
User Exits
• User Exits are called as modifications not enhancements as we are
modifying the standard programs.
• We need access key to change the standard programs using user exits.
As soon as we click on change button of standard programs it will
ask for access key.
• In User Exits, We will write the code inside of Form-End forms.
• The data is available globally as it is a global program.
Note: Ex, we have standard programs/includes like MV45AFZZ

( V1, Sales order)
MV50AFZ1 ( V2, Delivery)
RV60AFZZ ( V3, Billing )
3
User Exits Continued…
We will be required access key as above. Once we get access key from SAP
Market Place, SAP will not support us further on this Object.
4
Customer Exits
• These are enhancements where we don’t require access key
• We have to create project in CMOD to implement customer exits.

Relationship between exist and Project is On-to-One. I.e we can
create only one project to an Exit.
• We will write the code in Function modules
• We will see an example for customer exits in below slide.
5
Customer Exits Continued..
• My requirement is to validate a customer at time of Save with Country
Filter. The below is the one of process to find out the suitable Exit for this
requirement.
• First we need to find the package of the Tcode XD01(Cust. Creation).
• Go to the program for XD01->GOTO->Attributes. Here package is “VS”.
We have a TCode to find out the exit: SMOD, click on F4
6
• We have only one exit SAPMF02D.
• Once We get the exit, we have to implement it in CMOD
by creating a Project.
7
Click on Enhancement assignments and give your Exit name there.
Click on Components. Click on function exit

“EXIT_SAPMF02D_001”, You will find a custom include in it. Write
the code inside of it.
8
“I_KNA1” is the parameter of
the FM.
Once we are done with code, Activate the project as below.
9
Go to XD01 and create a

customer with country ‘IN’.
10
We can see a popup Note@ 1. We can get exits

with our code. using in another way using
SE84 as below.
11
Menu Exit
Menu exit is nothing but adding an item in the menu bar. We will see
an example below.
I would like to add an item in the menu of SE38.
12
Menu Exit Continued…
Click on GUI Status.
13
If we have “+CUS” in any one of the menu bar items, only then we can
create menu exit.
Now get the package and then proper exit to implement the Menu exit.
14
Now go to SMOD and find the exit name.
15
Now we get 2 exits, among them
We will set and create the project
with the proper one.
16
Create project in CMOD Go to Components and Assign the exit as follows
.
17
As we have both menu and function exits here to implement, first
implement menu exit SAPLWBABAP later function exit
EXIT_SAPLWBABAP_010
Double click on menu exit

and follow as below.
Click on COPY as below.
18
Now implement function exit and write the below

code.
19
Now go back and activate the
project.
20
Now We can see the implemented Menu exit in SE38
Click on “Call SE11”
21
Implicit Enhancements
Rather than getting the access key to modify the standard programs, SAP has
provided an option to write the code at the beginning of the form or at the ending
of the form. i.e. Implicit enhancement.
If we are ok to write the code at the above mentioned places we can go and write
the code without access key as mentioned below.
Click on Spiral Icon ->EDIT-

>Enhancement options->Show Implicit
Enh. Options
22
Implicit Enhancements Contd…
Then we get ‘’’’’’’’’ lines at beginning of the form, ending of the form as
mentioned.
Right Click on it and follow as below.
23
24
Click on “Code”
25
Click on “Create” symbol to create our implicit Enh.

26
Click on ‘OK’.
27
Select out Enhancement and ‘OK’.
28
Now we can write our logic in our enhancement where the entire
MV45AFZZ program Is input disable.
Note@ We will work on implicit only when we are ok to write the code at
earlier mentioned places else we have to go for Access key to modify the
code.
29
Field Exit
Field exit is nothing but to change the field label of a standard data element.
We will see one example as below.
Note@ SAP has provided a provision to

use the existing fields for the custom
requirements rather than creating new
fields.
Here we have some fields which are
available and we are going to use them.
So based on our requirement we will
change the field label of the Screen field.
30
Field Exit Continued…
The data element for

Attribute fields in
XD01/2/3 are.
So now we will change the data element KATR1.

31
To do Field exit, we use Tcode CMOD and follow the below path.
32
Now I have changed the label as “Field Exit”. The same will be reflected
now in XD01/2/3 Screen.
33
Based on Client needs, we can change the filed label of the Screen fields.
34
Screen Exit
Screen exit is nothing but adding a field(s) to the standard SAP screen.
Lets try an example for CJ01/2/3.
We find out the exit

CNEX0006 to add fields at
project level.
35
Screen Exit Continued…
Now we will create a project in
CMOD.
Click on “Enhancement assignment”
36
As mentioned earlier, we can
assign exit to only one project.
Here this exit is already assigned
in some other proj. See the error
below in the screenshot.
Now we have to open the existing
project and add our enhancement.
Note@ We can see this

information in MODSAP/
MODACT tables where which
exit is assigned to which project.
37
First we have to create/append the fields in “CI_PROJ”

38
Lets create the sub
screen as below.
We have added these appended fields in the sub screen 0600.
39
We have created a sub screen 0600 as below.
Now lets write the code in both the function exits to move the data from
screen field to table and table to screen field.
40
Code inside “EXIT_SAPLCJWB_002”
Code inside “EXIT_SAPLCJWB_003”
Finally activate the project and test the scenario.

41
Click as below. Then you can see the newly added fields.
42
We are done with Screen exit.
43
BADI (Business Addin’s)
• Badi stands for “Business Addin’s”.
• We have an option to create no.of implementations for Badi’s which is
not available in Customer exits.
• Badi is purely on OOP’s concept.
• We will get an interface (Null Methods) when we create an
implementation for a Badi.
• Let us look into an example on Badi.
Note: We can see Badi definition at SE18 and Implement a Badi at SE19.
44
BADI (Business Addin’s) Contd..
Scenario: Popup when saving a material based on UOM.
Finding a Badi: We have a class CL_EXITHANDLER.
In this we have a method GET_INSTANCE, put the break
point at this method and run your tcode(MM01). We will get
many Badi’s. We will choose suitable Badi and implement.
For our requirement we get the

Badi “BADI_MATERIAL_CHECK”
and we can see the type as “Multiple Use”
means we can have multiple
implementations.
45
Now lets implement the Badi and write the code in SE19.
46
Now click on tab “Interface” and write the code in method “Check_data”
Now we have to activate the implementation. Now test the scenario.
47
Our code is triggered.
Note@ We can create many implementations for this Badi. All the active
implementations will get triggered in “Alphabetical Order”. If we want to change
the order of triggering we have another Badi “BADI_SORTER” for that.
48
Kernel BADI
• Kernel Badi’s are nothing but new Badi’s.

• We can create new Badi’s in Enhancement Spot.
49
Kernel BADI Continued…
Create a Badi with name

Save the Spot. “ZKERNAL_BADI”.
50
Click on “Interface” and create it along with Method(s)
51
• We are done with Interface creation and method in it.

• Now we have to implement the kernal badi with our Code in
SE19.
52
Create the Enhancement implementation and continue.
53
Continue.
54
Create Implementing class and implement the method as follows.
55
Code is done. Activate the Enhancement Implementation.

Now lets write the code in a custom program as follows.
56
Execute
Lets create as many methods you want with

parameters and start working on kernal Badi’s
57
Explicit Enhancement.
• We can create Explicit enhancements in Enhancement Spot.
• We have two options in Explicit enhancements
• Enhancement-Point
• Enhancement-Section
• Enhancement-Point: If We write code here our custom code will

be executed along with standard/Existing
code.
• Enhancement-Section: Only custom code will be executed not the
existing/standard code.
58
Explicit Enhancement Continued.
Lets create an example as above.
59
Now we are creating Enhancement-Point in Spot “ZBHAVAN_ES”

60
Right click on Spot name and do as below.
We can create implicit enhancements as below and write our own logic.
61
We can create as many enhancements like this.
The code triggering will depend on SECTION/POINT.
62
BTE- Business Transaction Events
• Business transaction Events are purely designed for FI Enhancements.
• We will see an example on BTE now.
• Scenario: In general, FI documents are parked(FBV1). The same

document shouldn't be posted(FBV0) by another user.
• First we will see how to find the BTE.
63
BTE- Business Transaction Events Contd…
Open T-code “FIBF” and click as below.
Execute on below screen.
64
We find the suitable BTE.
Now we have to implement the selected BTE. Select the

BTE and click on “Sample Function Module”
65
Copy it to a FM and write the

code as below..
66
Now assign the BTE.

T-code: FIBF
Create a product as below.
67
Now follow as below. Open T-code FIBF
Configure the BTE,FM and Product as below.
68
69

SAP Enhancements: - Bhavannarayana .S

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Enhancements: - Bhavannarayana .S

Uploaded by

Copyright:

Available Formats

SAP

Note: Ex, we have standard programs/includes like MV45AFZZ

• We have to create project in CMOD to implement customer exits.

• We will write the code in Function modules

• We will see an example for customer exits in below slide.

Click on Components. Click on function exit

Once we are done with code, Activate the project as below.

Go to XD01 and create a

We can see a popup Note@ 1. We can get exits

Click on GUI Status.

Now go to SMOD and find the exit name.

Double click on menu exit

Now implement function exit and write the below

Click on “Call SE11”

Click on Spiral Icon ->EDIT-

Click on “Create” symbol to create our implicit Enh.

Select out Enhancement and ‘OK’.

Note@ SAP has provided a provision to

The data element for

So now we will change the data element KATR1.

We find out the exit

Click on “Enhancement assignment”

Note@ We can see this

First we have to create/append the fields in “CI_PROJ”

We have added these appended fields in the sub screen 0600.

Code inside “EXIT_SAPLCJWB_002”

Code inside “EXIT_SAPLCJWB_003”

Finally activate the project and test the scenario.

We are done with Screen exit.

For our requirement we get the

Now we have to activate the implementation. Now test the scenario.

Our code is triggered.

• Kernel Badi’s are nothing but new Badi’s.

Create a Badi with name

Click on “Interface” and create it along with Method(s)

• We are done with Interface creation and method in it.

Create the Enhancement implementation and continue.

Create Implementing class and implement the method as follows.

Code is done. Activate the Enhancement Implementation.

Lets create as many methods you want with

• Enhancement-Point: If We write code here our custom code will

Lets create an example as above.

Now we are creating Enhancement-Point in Spot “ZBHAVAN_ES”

The code triggering will depend on SECTION/POINT.

• Business transaction Events are purely designed for FI Enhancements.

• We will see an example on BTE now.

• Scenario: In general, FI documents are parked(FBV1). The same

• First we will see how to find the BTE.

Execute on below screen.

We find the suitable BTE.

Now we have to implement the selected BTE. Select the

Copy it to a FM and write the

Now assign the BTE.

Create a product as below.

Configure the BTE,FM and Product as below.

You might also like