1 of 107

AB1012 - Enhancements, Exits and BADI's

2 of 107

Enhancements, Exits and BADI's

1

Introduction

2

Syntax Description

3

Demonstration

4

Exercises

5

HelpMe

3 of 107

Enhancements, Exits and BADI's

1

Introduction

2

Syntax Description

3

Demonstration

4

Exercises

5

HelpMe

4 of 107

Introduction

Purpose
Use
Challenges

EXIT s are nothing but the R/3 Enhancements which allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications.

5 of 107

Introduction

Purpose

To introduce the techniques of enhancement in standard SAP system. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.

6 of 107

Introduction

Use

They do not affect standard SAP source code.

When you add new functionality to your SAP System using SAP’s exits, you do not alter the source code of standard SAP programs in any way. The code and screens you create are encapsulated as separate objects. These customer objects are linked to standard applications, but exist separately from SAP’s standard software package.

They do not affect software updates.

When you add new functionality to your SAP System using SAP’s exits, your objects (called customer objects) must adhere to strict naming conventions. When it comes time to upgrade a to a new software release, customer objects’ names ensure that they will not be affected by any changes or new additions to the standard software package.

7 of 107

Introduction

Challenges

Customer exits are not available for all programs and screens found in the SAP System.

8 of 107

9 of 107

Any change made to an SAP object in a customer system is called a modification. Customers usually modify their systems for one of two reasons. Either they make changes to the SAP standard in order to adjust the R/3 System to their specific business needs (actual modifications), or they alter individual SAP objects in order to correct an error (as recommended in an SAP error note).

You should only modify the SAP standard if the modifications you want to make are absolutely necessary for optimizing work flow in your company. Be aware that good background knowledge of application structure and flow are important prerequisites for deciding what kind of modifications to make and how these modifications should be designed.

10 of 107

1

3

4

2

11 of 107

Enhancements, Exits and BADI's

1

PrepareMe

2

Syntax description

3

Demonstration

4

Exercises

5

HelpMe

12 of 107

ABAP DICTIONARY

Table Enhancements: There are two ways that you can add additional fields to tables without modifying your system.

Append Structures:
Append structures allow you to enhance tables by adding fields to them that are not part of the standard. With append structures, customers can add their own fields to any table or structure they want.
Append structures are created for use with a specific table. However, a table can have multiple append structures assigned to it.

Customizing Includes:
If customers know in advance that one of the tables or structures delivered to them by SAP needs to have customer-specific fields added to it, an SAP application developer can include these fields in the table using a Customizing include statement.
The same Customizing include can be used in multiple tables or structures. This provides for consistency in these tables and structures whenever the itself include is altered.

Append structures allow you to attach fields to a table without actually having to modify the table itself.

Append structures may only be assigned to a single table. A table may, however, have several append structures attached to it. Whenever a table is activated, the system searches for all active append structures for that table and attaches them to the table. If an append structure is created or changed and then activated, the table it is assigned to is also activated, and all of the changes made to the append structure take effect in the table as well.

You can use append structures in ABAP programs just as you would any other structure.

Note: When you copy tables that have append structures attached to them, the fields that were found in the append structure of the original table become part of the actual body of the target table.

Some of the tables and structures delivered with the R/3 standard contain special include statements calling Customizing includes. These are often inserted in those standard tables that need to have customer-specific fields added to them.

In contrast to append structures, Customizing includes can be inserted into more than one table. This provides for data consistency throughout the tables and structures affected whenever the include is altered.

Customizing include programs are part of the customer namespace: all of their names begin with 'CI_'. This naming convention guarantees that nonexistent Customizing includes do not lead to errors. No code for Customizing includes is delivered with the R/3 standard.

You create Customizing includes using special Customizing transactions. Some are already part of SAP enhancements and can be created by using project management (see the unit on 'Enhancements using Customer Exits').

The Customizing include field names must lie in the customer namespace just like field names in append structures. These names must all begin with either 'YY' or 'ZZ'.

When adding the fields of a Customizing include to your database, adhere to same rules you would with append structures.

13 of 107

ABAP DICTIONARY

Field Exits:

Field exits take you from a screen field with a data element reference to a function module. Field exits can be either global or local.

Field exit function modules adhere to the following naming convention:
prefix: FIELD_EXIT_
name: <data element name>_
suffix (optional): 0 to 9, A to Z

Global field exits are not limited to a particular screen. If a global field exit's data element is used on multiple screens, you will branch to a function module from all of these screens once the exit has been activated. Here you can, for example, edit the contents, force a new entry to be made by outputting an error message, or prohibit certain users from proceeding further.

Local field exits are valid for one screen only. If you assign a screen from a specific program to the data element, then you will only branch to a function module from this screen once the exit has been activated. To be able to allow different functionality on different screens referring to the same data element, you can assign exit numbers to data elements. Each exit number refers to a different function module.

prefix: FIELD_EXIT_

name: <data element name>_

suffix (optional): 0 to 9, A to Z

14 of 107

ABAP DICTIONARY

Text Enhancements:

Possible text enhancements include customer keywords and customer documentation of data elements.

Text enhancements differ from other application enhancements in that they take effect globally in all related SAP applications after activation (global enhancements).

Possible text enhancements include customer keywords and customer documentation of data elements.

Text enhancements differ from other application enhancements in that they take effect globally in all related SAP applications after activation (global enhancements).

Use the project management function to edit text enhancements.

Just as with field exits, use the menu entry Global enhancements to access the enhancement functions for keywords and data element documentation

SAP application programmers define keywords in different lengths and a short description for each data element. Use the project management function (transaction CMOD) to change these keywords and short texts.

All screen fields that use the keyword text of data elements can be renamed in this manner.

A new short text in a data element will show up in the F1 help of the screen field.

In order for keyword changes to take effect on a screen, SAP application programmers have to maintain the MOD attribute (keyword modification indicator) of the affected field accordingly in the Screen Painter field list.

The MOD attribute must have one of the following values:

SPACE: the keyword that best fits the field length�1: short keyword�2: medium keyword�3: long keyword�4: keyword for header�V: variable text transfer from the ABAP Dictionary�F: fixed, no text transfer

If the attribute contains an 'F', it is fixed on the screen and cannot be modified. In all other cases, screens that refer to that particular data element will show the changed keyword.

15 of 107

SAP Application Enhancement

16 of 107

Customer Enhancement Projects

SAP application programmers create SAP enhancements in transaction SMOD using function module exits, menu exits, and screen exits.

Customers are given a catalog containing an overview of existing SAP enhancements. They can then combine the SAP enhancements they want into an enhancement project using transaction CMOD.

SAP enhancements are made up of component parts. These components include function module exits, menu exits, and screen exits. A specific component may be used only once in a single SAP enhancement (this guarantees the uniqueness of SAP enhancements).�

Customer enhancement projects consist of SAP enhancements. Each individual SAP enhancement may be used only once in a single customer enhancement program (this guarantees the uniqueness of a customer project).

SAP application programmers preplan function module exits, menu exits, and screen exits for their applications and combine them to create useful enhancements for the R/3 System.

Customers create their own enhancement projects for their systems using SAP enhancements. You can customize the individual components of an enhancement project by creating your own include programs (for function module exits), texts (for menu exits), and subscreens (for screen exits).

17 of 107

Customer Exits

Function Module Exits
Menu Exits
Screen Exits

Function Module Exits

Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits. When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated. Function module exits also control the data flow between standard programs and screen exit fields.

Menu Exits

Menu exits add items to the pull down menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.

SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu item’s text when activating the item in an add-on project.

Screen Exits

Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special sub screen areas on a standard R/3 screen and calling a customer sub screen from the standard screen’s flow logic.

18 of 107

Implementation of Enhancement in Customer System

19 of 107

Creating Customer Enhancement Projects

20 of 107

Assigning SAP Enhancement to customer projects

21 of 107

Editing Components

Activating Enhancement Projects

22 of 107

Business Transaction Events

It is also called as Open FI enhancement technique which is based on the following principle:�

Application developers must define their interface in a function module. An assignment table is read in the corresponding (generated) code, and the customer modules assigned are called dynamically.

This technique differentiates between enhancements that are only allowed to have one implementation and enhancements that can call multiple implementations in any sequence desired. Both industry-specific and country-specific enhancements may be defined.

23 of 107

Enhancement Framework

The new enhancement concept of the ABAP Workbench enables the integration of different concepts for modifying and enhancing development objects. The enhancement concept is supported by the Enhancement Builder tool and ABAP language elements.
The objective of the Enhancement Framework is to provide a technology to create modification-free enhancements and to unify all possible ways of modifying or enhancing Repository objects.

24 of 107

Multilayer Support

25 of 107

Enhancement Spots

Enhancement Spots can only be of type source code Enhancement or BAdI.
Enhancement Spots manage explicit Enhancement Options

While implicit enhancement options always exist and do not require any special management, explicit enhancement options created in an initial system must be made known to developers in target systems via Enhancement Spots.

26 of 107

Enhancement Implementations

Enhancement implementations manage their enhancements.
Enhancements made by developers in follow-on systems are managed as Enhancement Implementations. This applies to all enhancement options, both explicit and implicit.

27 of 107

Composite Enhancement Spots

Composite Enhancement Spots are used to organize Enhancements Spots in a tree structure.
Container Objects
Can contain

Other Composite Enhancement Spots
[Simple] Enhancement Spots

Container Objects
Can contain Enhancement Elements

28 of 107

Composite Enhancement Implementation

Composite Enhancement Implementations are used to organize Enhancement Implementations in a tree structure.
Container Objects
Can contain

Other Composite Enhancement Implementations
[Simple] Enhancement Implementations

Can contain Enhancement Implementation Elements

29 of 107

Composite Enhancement Implementation

The first tab displays which (Simple) Enhancement Implementations are contained.
The second tab displays which other Composite Enhancement Implementations are contained.

30 of 107

Enhancement Relations

31 of 107

Source Code Enhancement

It is possible to enhance ABAP source code – without modifications – using source code enhancements.
You can insert enhancements at implicit and explicit enhancement options. The Enhancement Builder tools for defining explicit enhancement options and for implementing enhancements are integrated in the ABAP Editor.

32 of 107

Features of explicit & Implicit enhancement options�

Features of explicit enhancement options

More stable, pre-defined
Few changes in definition to expect
Only at valid source code locations

Features of implicit enhancement options

Enhancement of “arbitrary” objects
No enhancement spots necessary

33 of 107

Difference: Explicit and Implicit Option

Explicit Enhancement Options

In ABAP programs, developers can select either a position or a program section as an explicit enhancement option. In follow-up systems (partners and customers) can implement source code plugins at such a position or they replace the selected section.

Implicit Enhancement Options

Implicit enhancement options always exist.

34 of 107

Explicit Enhancement Options

To mark a position in an ABAP program as an explicit enhancement option, the following ABAP statement is used:

ENHANCEMENT-POINT enh_id SPOTS spot1 spot2 ...

To mark a section in an ABAP program as an explicit enhancement option, the following ABAP statement is used:

ENHANCEMENT-SECTION enh_id SPOTS spot1 spot2 ...
END-ENHANCEMENT-SECTION.

Currently it is only possible to assign an enhancement point/section to one Enhancement spot.

35 of 107

Implicit Enhancement Options

Implicit enhancement options can be displayed in the ABAP Editor by following the path Edit → Enhancement Operations → Show Implicit Enhancement Options and then implemented using source code enhancements.
Implicit enhancement options always exist and no enhancement spot is assigned to them.
In ABAP programs, implicit enhancement options are predefined at the following places:

End of an include (with exceptions, e.g. not at the end of a method include)
End of the PUBLIC-, PROTECTED-, PRIVATE-SECTION of a local class
End of the implementation part of a class (before the ENDCLASS, which belongs to CLASS …IMPLEMENTATION)
End of a interface definition (before the ENDINTERFACE)
End of a structure definition (before TYPES END OF, DATA END OF, CONSTANTS END OF and STATICS END OF)
Begin and End of a procedure (FORM, FUNCTION, METHOD), that is after command FORM, FUNCTION und METHOD and before statement ENDFORM, ENDFUNCTION and ENDMETHOD.
End of the CHANGING-, IMPORTING-, EXPORTING-parameter list of a method. These enhancement options are located in the middle of a statement.

36 of 107

Enhancement Type

ENHANCEMENT-POINT <name> SPOTS <spot1> [<spot2>] ..[STATIC]

Static: Additional data declaration
Dynamic: Additional source code

ENHANCEMENT-SECTION <name> SPOTS <spot1> [<spot2>] ..[STATIC]

Static: Replace an existing data declaration
Dynamic: Replace source code

Data declarations are always static, even if they are inside an implementation of a dynamic enhancement point.
Form routines, methods and local classes can‘t be part of dynamic enhancement points/sections. Therefore it is necessary to place them into static enhancement points/sections.
Static enhancement points/sections are marked with the addition “STATIC” in source code. Dynamic enhancement points/sections do not contain an addition.

37 of 107

Functional Module Enhancement

Function Module Enhancements allow

Adding new optional parameters to existing function modules
Enhance the source code

38 of 107

Class/Interface Enhancement

Class/Interface Enhancements allow addition of:

Optional parameters to existing methods
Methods
Events and event handlers
References to interfaces
Exits to existing methods

Pre-Exit – Called at the beginning of a method
Post-Exit – Called at the End of a method
Overwrite-Exit – Replaces the original method

39 of 107

Enhancements, Exits and BADI's

1

PrepareMe

2

Syntax Description

3

Demonstration

4

Exercises

5

HelpMe

40 of 107

User Exits

41 of 107

Demonstration

Function Module Exits

42 of 107

Demonstration

Menu Exits

43 of 107

Demonstration

Screen Exits

44 of 107

Demonstration

Field Exits – It is triggered at field level.

It is attached at data element

Specific to one screen only or to all the screen where field appears.

Field exit is not allowed in SAP version 4.7 and above .

Example with screen shots for consultants working in

SAP V 4.6 below version.

45 of 107

46 of 107

47 of 107

48 of 107

49 of 107

Business Add-Ins (BAdI)

50 of 107

What are BAdIs?

is an anticipated point of extension – these points act like sockets and exist in the original source code
based on ABAP Objects. BAdI defines an interface that can be implemented by BAdI-implementations that are transport objects of their own
Important! There are 2 roles: Enhancement Option-provider & Implementer.
In the above context, Enhancement Implementation can be done only if option (hook) is provided by the Option-provider. In simple words there are no implicit BAdIs.

Note: In the following slides, Definitions are created so as to understand the method of BAdI definition & for example purpose. As stated above this is the role of Enhancement Option-Provider.

Classic BAdIs already exist since SAP Release 4.6

BAdIs have been Re-implemented in ECC7.0 under the new Enhancement Framework & Switch Framework

51 of 107

Classic BAdIs

To understand what a powerful pattern a BAdI is, we will now define & then implement a BAdI

BAdI Class (Proxy Class)

Uncheck the ‘Multiple Use’ checkbox. We want to allow only one implementation.

Function Code Enhancements

Screen Enhancements

SE18: BAdI Definition

BADI Class is created automatically.

The various options are described below in detail:

1. Enhanceable: Enhanceability of filter types can only be specified for filter-dependent BADI definitions under very special conditions. For example, the domain belonging to the filter type must be linked with a value table that is of the type E or G. A BADI implementation can then be created in one step by creating a new filter value that is automatically entered into the value table at save and also copied into the transport order of the BADI implementation. In addition, it is also possible to create a new filter value and, at the same time, a BADI implementation with the same name. Naturally, you can also specify existing filter values.

You should select this feature if there is a prerequisite that a new filter value is created together with a new BADI implementation - that is, that BADI implementations are not created solely with existing filter values, although this, too, is possible.

2. Multiple-Use

3. Filter-Dependent

52 of 107

Classic BAdIs

Double Click on the Interface Name to define methods, parameters, exceptions for that interface

Class Builder Screen will open up.

53 of 107

Classic BAdIs

Add a Method & specify it as Instance Method

Click on Parameters to add Importing / Exporting Parameters

Click on ‘Exceptions’ to define exceptions that will be handled

54 of 107

Classic BAdIs

Add any Exception. For Class-based exceptions check the ‘Exception Classes’ option

Add an Event Name

Add an Event Handler Method

Adding event handling & exception(s) is not a necessary step…

55 of 107

Classic BAdIs

Save and activate the BAdI definition!

56 of 107

BADI Implementation

BAdI Implementation (SE19)

Double Click on the Method to modify the Method code (Class Builder)

SE19: BAdI Implementation

57 of 107

BADI Implementation

Save and activate the BAdI implementation!

58 of 107

Using the BAdI…(Calling the BAdI)

Execute the Report Program.

59 of 107

Implementation for SAP provided BAdI…

Roles: (BADI Definition & Implementation)

Developer: Enhancement (BAdI) Option-Implementer
SAP: Option-Provider

BAdI as a ‘controlled’ Enhancement Option:

Option-provider defines the interface and limits the implementer to the class that the implements the BAdI
Assured that BAdI implementer can only change the parameters handed over to the BAdI by the option provider

Steps:

Search for the BAdI corresponding to the transaction
Create a custom Implementation for the BAdI by adding code in the appropriate method
Test that the method with custom code is invoked on executing the transaction.

60 of 107

BAdI Implementation

Create Material using MM01. Copy from existing Material.

Select the required views.

61 of 107

BAdI Implementation

Enter mandatory data and click on Save.

Check the Exit Name ‘BADI_MATERIAL_CHECK’. This is the BAdI we are going to implement.

62 of 107

Implementing the BAdI ‘BADI_MATERIAL_CHECK’

Go to SE18 & check the BAdI definition (Methods)

We will be using the ‘CHECK_DATA’ method. Double Click to see the Method Parameters.

63 of 107

Implementing BADI

Go to SE19. Specify a name for the BAdI Implementation.

Enter the Definition Name.

Double-click the method ‘CHECK_DATA’ to enter the source code

64 of 107

Implementing BADI

Enter code inside the ‘Method…End Method’

We are only showing an message in this case; if division in ‘Basic Data’ tab of Material Creation is not entered.

The structure CMARA is defined as ‘Exporting Parameter’. Data can be modified using this.

65 of 107

BAdI Implementation

Activate the Implementation

66 of 107

Testing the BAdI

MM01 / MM02 and create / change material and save. On clicking Save, our BADI will trigger.

Testing the BAdI implementation (BADI_MATERIAL_CHECK)

Message is displayed (Division not entered)

67 of 107

BAdIs…in the new Enhancement Framework (ECC 6.0)

How the new BAdIs differ from the Classic BAdI?
Good news is that…basic thing about the BAdI remains the same!
Differ in the manner in which new BAdI is embedded in the container-structure of the Enhancement Framework
Better performance & Lower Memory consumption
Evaluates as much information as possible during compile time
40-600 times faster than Classic BAdIs
Internal handle-class integrated in the SAP Kernel
Provides ‘switchable’ implementation(s) through use of Switch Framework
Special optimizations with ‘GET BADI’ & ‘CALL BADI’ (new ABAP commands)
Implementation Inheritance

68 of 107

Usage of old (classic) BAdIs versus New BAdIs…

Two new ABAP commands for the new BAdI:

GET BADI <handle> : returns a handle to all ‘active’ instances of the implementations of the respective BAdI
CALL BADI <handle> 🡪 <method> : all active implementations are selected and the method of BAdI is called (amounts to a loop with different method calls in it)

69 of 107

Enhancement Spot as a container for BAdI…

Enhancement Framework has containers for BAdI implementations as well

70 of 107

New BAdIs

Create a new Enhancement Spot

71 of 107

Defining & Implementing the new BAdI

Create BAdI Definition

SE18 (BAdI Definition) Screen has additional option (Enhancement Spot)

72 of 107

BAdI definition

Enter name for the Interface and click on ‘Change’

Create Method & it’s parameters

73 of 107

BAdI definition

Click on this to create an Enhancement Implementation

Specify a ‘Fallback Class’ to be executed if no active Implementation is found

74 of 107

BAdI Implementation

Expand the Node for ‘Implementing Class’

Specify the ‘Implementing Class’ and click on Change

Report program to call BADI:

DATA: handle type ref to <BAdI_Name>

GET BADI handle

CALL BADI handle 🡪 <method_name>

EXPORTING …

IMPORTING …

75 of 107

Filter-dependent BAdI

What is a Filter-Dependent BAdI?

GET BADI <handle> FILTER <filter_name> = <filter_value>. Implementations meeting the filter conditions are chosen
Example: GET_VAT (Country-Code Specific). Create 2 implementations for GB & US. It does not make sense to call both of them, hence the Definition is marked as Single-Use (only single active implementation can exist).
We define a filter (remember this is the role of BAdI provider) say ‘COUNTRY’
Add a filter value corresponding to the BADI Implementation, i.e. Implementation for GB has Filter Value = ‘GB’ & that for US has Filter value = ‘US’

76 of 107

Filter-dependent BAdI

Create a new Implementation for the same BADI definition we created earlier.

77 of 107

Filter-dependent BAdI Implementation

78 of 107

Filter-dependent BAdI Implementation

79 of 107

Filter-dependent BAdI Implementation

80 of 107

Filter-dependent BAdI Implementation

81 of 107

Multiple-use BAdI

What are Multiple-use BAdI?

Multiple-use BAdIs can have more than one implementations
Option is provided by the Enhancement Option-provider (in the BAdI definition)

Example: BAdI that converts data for different output devices. Hence, call of a method of a multiple-use BAdI is akin to sending a message. It does not matter how many services react to the message. It is similar to Publish & Subscribe mechanism.

82 of 107

Context Objects (new concept in Enhancement Framework)

How are they defined & used?

DATA <context> TYPE REF TO <cl_myctx>

GET BADI <handle> CONTEXT <context>

Whenever ‘GET BADI’ is called with the same context & a filter value which leads to the same implementation class, the already created instance is used.

Advantages of using Contexts:

Performance Improvement
Holds data over different method calls or even BAdI calls

What do you mean by Contexts?

Context Class is a class implementing ‘if_badi_context’ (only a marker interface) & Context reference is reference to an instance of Context Class
used to control the instantiation of BAdIs

83 of 107

Switch Implementations (new Switch Framework)�

Active implementations are evaluated at compile time and included in the load of BAdI handle
only implementations that are switched on by the Switch Framework in at least one client are considered

84 of 107

Enhancement Framework

85 of 107

Editor Modes for Enhancements

Use Change Mode for creating enhancement points & sections.

use button “Display <-> Change” to switch to change mode.

Use Enhancement Mode for creating enhancement implementations.

use button “Change Enhancements” to switch to Enhancement mode
use button “Display <-> Change” to leave Enhancement mode

86 of 107

Source Code plug-in

Transaction Code: SE18

Enter name of the enhancement spot and click on display button

87 of 107

Source Code plug-in

On double clicking on any of the enhancement-point, system will display the code behind each of them

88 of 107

Source Code plug-in

To insert new implementation for enhancement point, click on the spiral button.

89 of 107

Source Code plug-in

In order to create an implementation for an enhancement point, right click on enhancement point and then select create option from context menu.

90 of 107

Source Code plug-in

Click on create button to create enhancement implementation

91 of 107

Source Code plug-in

Enter the name of the enhancement implementation and short text, and then choose this option

92 of 107

Source Code plug-in

Select the newly created enhancement implementation and then select this option

93 of 107

Source Code plug-in

You can include your source code here.

94 of 107

Function Module Enhancement

Specify Implementation name and its short text

Inorder to enhance the functional module with new parameter, choose this option

You can enhance the parameter interface of a function module with new, optional formal parameters.
You cannot include an exceptions.

95 of 107

Function Module Enhancement

Before Activation

After Activation

96 of 107

Class/Interface Enhancement

97 of 107

Class/Interface Enhancement

Importing, Exporting and Changing Parameter

For every existing method importing, exporting and changing parameters can be additionally created inside a class enhancement.
It is not possible to add a returning parameter or an exception to an existing method.

Optional

Additional parameters are always optional.
Hint: The flag “optional“ is not checked for exporting parameters, because they are always optional, even if they are not in an enhancement.

98 of 107

Class/Interface Enhancement

Add new methods

Constructor and Class-Constructor can not be created as class enhancements.

99 of 107

Class/Interface Enhancement: Pre/Post Exits

Pre Exit

A pre-method is called directly after the call of the existing method before the first statement.

Post Exit

A post-method is called after the last statement of the existing method before ENDMETHOD (only if the method is exited using ENDMETHOD).

Access to attributes

The pre and the post method do only have access to the public attributes/methods of the class.

Pre/Post Exits versus source code plugins

Higher abstraction level due to a separate address space.
Less adjustment effort than source code enhancements during upgrade. (only when parameters are changed).
All Exits are stored in a local enhancement class. The class can have attributes to exchange data between the methods.

100 of 107

Enhancements, Exits and BADI's

1

Introduction

2

Syntax Description

3

Demonstration

4

Exercises

5

HelpMe

101 of 107

Exercises

Table enhancement - Append structure (2 Char fields ) for Table SFLIGHT**

To trigger all the customer exit (Function , Menu and Screen Exit) for Program SAPBC425_FLIGHT**

Create a project using following Components

SBC**E01(Function Exit)

SBC**E02(Menu Exit)
SBC**E03 (Screen Exit)

(** => ranges from 00 to 18)

102 of 107

Name of the Functionality

1

Introduction

2

Syntax Description

3

Demonstration

4

Exercises

5

HelpMe

103 of 107

HelpMe

Tips and Tricks
Additional Info

104 of 107

HelpMe

Tips and Tricks

SAP application programmers use the ABAP statement CALL CUSTOMER-FUNCTION 'nnn' to call function modules (where 'nnn' is a three-digit number). They must also create the function module they want z CALL CUSTOMER-FUNCTION )

These function modules are always belong to function groups whose names begin with X (X function groups).��

The following naming convention applies to these function modules:

prefix: EXIT

name of the program that calls the function module

suffix: three-digit number��

The three parts of the name are separated by two underscores.��

The CALL CUSTOMER-FUNCTION statement is not executed until the corresponding enhancement project is activated. Multiple calls of the same function module are all activated at the same time.

105 of 107

HelpMe

Additional Info

SAP application programmers can declare global data in include program LxaaaTAP.��
You declare your own global data in include program ZXaaaTOP.��
Include program LXaaaTOP also contains the FUNCTION-POOL statement, which may not be changed. Therefore, you must always include the message class in parentheses when outputting messages.

SAP application programmers can supply customers with default subroutines in include LXaaaF00.��
Subroutines, modules, and interactive events (AT…) are created as include programs and included enhancements using include program ZXaaaZZZ.��
Additional includes must adhere to the following naming convention:��
ZXaaaFnn for subroutines,�ZXaaaOnn for PBO modules,�ZXaaaInn for PAI modules,�ZXaaaEnn for events.

106 of 107

Searching BADI: Method 1

Search for BAdI corresponding to the transaction:

Method 1: Search for the CL_EXITHANDLER=>GET_INSTANCE in the main program

107 of 107

Searching BADI: Method 2

Put a breakpoint at the following code and execute the transaction (e.g. MM01)

We want to implement a BAdI on Saving Material Data.