A Tour of the New Business Add-Ins (BAdIs)

Below is a snippet from one of hundreds of articles available to ERPtips subscribers.

If you would like a complimentary copy of the full article, please email
Mark.Downs@ERPtips.com
(include the title of the article in your email)

To subscribe to ERPtips, go to
www.ERPtips.com/Subscribe.asp.

ERPtips Journal is published by Klee Associates, Inc.

ERPtips University provides both public and onsite training for SAP clients.
For more about ERPtips University, including the current schedule, click here:
www.ERPtips.com/WorkshopSchedule.asp

A Tour of the New Business Add-Ins (BAdIs)

Pssstt…wanna check out something HOT in SAP? Take a look at the newly enhanced BAdIs available in

Click here to read this Snippet

 SAPtips4On ABAP / J2EE
A Tour of the New Business Add-Ins (BAdIs):
Page 
April/ May 2008 Volume VI Issue 2
A Guide for SAP Developers and Consultants
®
Editor’s Note: Pssstt…wanna check out something HOT
in SAP? Take a look at the newly enhanced BAdIs avail-
able in ECC 6.0. Rehan Zaidi addresses the benefits of
the new Business Add-Ins, how they differ from previ-
ous versions, their implementation, single vs. multi-use
BAdIs, and even answers this question: What is an
Enhancement Spot? Take a tour with Rehan and learn
how you can get the most out of the BAdIs in your SAP
system.
Introduction:
Over time, SAP has improved the ways it allows cus-
tomer-specific requirements to be incorporated into the
standard R/3 functionality. The enhancement options
are no exception. One example of such an improvement
is the introduction of the new BAdIs.
These BAdIs are faster in performance and are easy to
define and implement. For these reasons, having the
knowledge of the new BAdIs is an absolute must for
developers and consultants.
The aim of this article is to discuss the new Business
Add-ins (BAdIs) provided by SAP since ECC 6.0. I will
begin with an overview of the new features, and then
discuss the characteristics of multiple- and single-use
BAdIs. The structure of the new BAdIs will be examined
and examples will be presented. How to implement the
new BAdIs will be explained in detail.
SAPtipsJournal
These are some of the questions this article will address:
• What are the benefits of the new Business Add-ins?
How do they differ from classic BAdIs?
• What is the new Enhancement Framework, and what
is an Enhancement Spot?
• What would a typical call for the new BAdI look like?
• How do single-use and multiple-use BAdIs differ?
• How are the new BAdIs implemented?
SAPtips.com
By Rehan Zaidi, Siemens Pakistan
This article is primarily intended for ABAP developers.
I will assume that the reader is familiar with ABAP
programming, as well as the Classic BAdIs. For more
information, refer to the SAP documentation on
http://help.sap.com. All the screenshots in this article have
been taken from ECC 6.0.
These BAdIs are faster in
performance and are easy to
define and implement.
New Business Add-Ins (BAdI): An Overview
SAP has provided an improved and faster BAdI technol-
ogy in the ECC 6.0 release. The new BAdIs are based
upon the same concept of object orientation as classic
BAdIs. However, there are a few differences. The new
BAdIs are provided as part of the new Enhancement
Framework. In the new Enhancement Framework,
the BAdI becomes an optional enhancement, or an
anchor point into which coding may be plugged. The
new BAdIs reside in containers known as Enhancement
Spots. Each BAdI has an Interface composed of the
BAdI method(s). It is this method which is accessed in
the program.
Note: An entire discussion of Enhancement Framework
is beyond the scope of this article. It will be discussed,
however, in an upcoming article. For more on Classic
BAdIs, see my article Enhancing Standard Programs
Quickly & Easily Via Business Add-Ins (BADIs) in the
“ABAP, Java, and J2EE Development” category in the
SAPtips Document Library.
In addition to the benefits provided by the Classic BAdI,
one major advantage that comes with the new BAdIs is
that they are faster in execution.
SAPtips © 2008 Klee Associates, Inc.
 SAPtips4On ABAP / J2EE
Page 

April/ May 2008 Volume VI Issue 2

BAdIs may be developed by SAP or may be custom
defined. We refer to the developer of the BAdI or any
other enhancement option as the Option provider. The
methods and their signatures (or the parameters) for
each respective method’s imports, exports, changes, or
returns, are defined by the BAdI developer. The meth-
ods defined in the BAdI interface are implemented
by the BAdI implementer. The option provider (BAdI
creator) defines what has to be done, but it is the
implementer who carries out the actual implementation
of the BAdI. Within the new BAdIs, the actions of the
implementer are controlled by the option provider, who
controls the class upon which the BAdI is based.
A developer must use BAdI when he or she wants a par-
ticular procedure to be executed at a particular position,
but does not want to specify the exact content of that
procedure. This might happen if the procedure details
used are different among various potential implement-
ers. It might also occur if the procedure details are so
specific that the developer is not familiar with them, or
if adding different implementations at a later stage.
Note: In addition to BAdIs, the new Enhancement
Framework provides another option of enhancement
known as Source Code Plug-ins. The possibility of
attaching a source code plug-in is allowed when an
enhancement point in the code is inserted by the option
provider. The implementer may add her or his own
code at this enhancement point. This has a few dis-
advantages. Because the written code
is generally implemented later in the
development, the option provider has
no control over it. All the variables that
are visible in the enhanced modulariza-
tion unit may be accessed by the code
within this source code plug-in. There-
SAPtipsJournal
• The GET BADI statement is used to generate a new BAdI
object, and assigns the reference to this object to the
specified variable (in our example, g_BADI_ME59_
EXCLUDE). This is also termed as the handle to the
BAdI object.
Prior to the GET BADI statement, the variable used must
be defined based on the BAdI that is to be used.
In case you have defined filters for your BAdI, you may
include suitable filter values in your GET BADI statement.
The GET BADI statement will be changed as shown below:
GET BADI myobject filter = filters.
• The CALL BADI statement is then used to call the rel-
evant BAdI method. This method call may involve
importing, exporting, and changing parameters (see
Figure 1).
Multiple- and Single-Use Business Add-Ins
The new Business Add-ins may either be Single-use or
Multiple-use. These two types of BAdIs are quite dif-
ferent. In single-use BAdIs, the business logic requires
exactly one single calculation result. The program’s
next steps may need this result; therefore at least one
BAdI implementation is needed. In this case, exactly
one result is required because there is no way to handle
many return values. The system takes care that there is
exactly one active implementation in a single-use BAdI.

fore, the implementer is able to modify

the value of any variables. This may be
undesirable in some cases, and cannot
be prevented by the option provider.
In this case, there is no control over
the implementer. On the other hand,
the BAdIs provide more control to the
option provider.

A typical call of the new BAdI is shown

in Figure 1.

The BAdI method is accessed using two

new ABAP commands, namely GET BADI
and CALL BADI. Let us take a closer look
at the use of these two commands:
Figure 1: A New BAdI Call

SAPtips.com SAPtips © 2008 Klee Associates, Inc.