P. 1
BCDWBCEX

BCDWBCEX

|Views: 558|Likes:
Published by Ajax Yadav

More info:

Published by: Ajax Yadav on May 25, 2011
Copyright:Attribution Non-commercial

Availability:

Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less

06/02/2011

pdf

text

original

Due to the necessity of adjusting R/3 to meet the specific needs of a variety of customers,
several different enhancement techniques were developed in the past. A short description of
each of the various enhancement techniques follows.

Business Transaction Events (Open FI)

The Open FI enhancement technique was developed in the Financial Accounting component.
Open FI is based upon the following principles:
Application developers must define their interface in a function module, an assignment table is
read in the accompanying (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.
The concepts behind the Business Add-Ins enhancement technique and Open FI are basically
the same. However, the two enhancement techniques do differ from each other in the following
points:
• Open FI can only be used to make program enhancements, that is, you can only enhance
source code using Open FI. You cannot enhance user interface elements with Open FI like
you can with Business Add-Ins.
• Open FI assumes that enhancement will only take place on three levels (SAP - partners -
customers), whereas with Business Add-Ins you can create and implement enhancements in
as many software layers as you like.
• Open FI uses function modules for program enhancements. With Business Add-Ins, ABAP
Objects are used enhance programs.

Enhancements in Transactions SMOD/CMOD

Making enhancements using the transactions SMOD/CMOD [Page 40] has the following
disadvantages:
• This enhancement technique assumes a two-tiered system infrastructure (SAP – customers).
• The naming conventions in effect do not tolerate name extension.

Taking Stock of Your Options:

None of the techniques mentioned above can easily be extended to fulfill the requirements of a
system infrastructure containing country versions, industry solutions, partners, and customers.
Business Add-Ins should be considered generalized Business Transaction Events that can be
used to bundle menu and program enhancements into a single add-in (and in the future, screen
and table enhancements as well). Business Add-Ins can be created and employed in each of the
various software levels.

April 2001

81

Changing the SAP Standard (BC)

SAP AG

Defining Business Add-Ins

You're Reading a Free Preview

Download
scribd
/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->