1. Business Add-Ins

2. Modifications and Enhancements
Flexibility
Modifications
Assisted modifications
Business Add-Ins
Customer exits
Ease of Use

3. Modifying the R/3 System to Meet Your Needs
Customer
Development
Modifications
Hook Techniques
Exit Techniques and Add-Ins
Customizing

4. Architecture: Business Add-Ins
Customer extension
Add-In-
Adapter:
Publish & Subscribe
Filter
Control
Interface
Interface
CORE
R/3
Industry
solution
Interface

5. Add-ins are points in an object’s source code where additional
Add-Ins: Definition
Add-ins are points in an object’s source code where additional
functions or statements can be inserted. Add-ins are defined by
the object’s initial developer and allow other developers to easily
include additional code in a subsequent phase of development
without having to ‘modify’ the original. Additional advantages:
No change licences necessary
Interfaces are upwardly compatible
Less work at upgrade

6. Business Add-Ins
Delivery of implemented add-ins (country-specific versions, IBU solutions, partner software, ...)
Technique can be used by other software vendors
Delivery and correction of default solutions (4.6C)
Filter-dependent implementation possible
‘Event-like’ add-ins (Publish & Subscribe)
Integrated administration and documentation
Trace possibilities

7. Business Add-Ins should be viewed as expanded
Why Business Add-Ins?
Perform calls in programs / using tables
Flexible <-> Fuzzy interface (global data,...)
Customer exits (SMOD/CMOD)
System infrastructure: SAP - customer
Naming convention not compatible with namespace extension
Business Transaction Events (Open FI)
No bundle of objects that belong together
No interface elements
Business Add-Ins should be viewed as expanded
and enhanced business transaction events

8. Architecture Application Customer IF_app_exit Generate class mth1 mth2
Program XXX.
Data:
exit type
ref to if_app_exit.
Create object...
Call method...
Generate class
mth1
mth2
mth3
...
CL_imp_app_exit
mth1
mth2
mth3
...

9. Example Program REPORT BADI . DATA EXIT TYPE REF TO IF_EX_BADI.
DATA WORD(15) TYPE C.
CALL METHOD CL_EXITHANDLER=>GET_INSTANCE CHANGING INSTANCE = EXIT.
START-OF-SELECTION.
WRITE:/ 'Please click here'.
AT LINE-SELECTION.
NEW-PAGE.
WORD = 'Business add in'.
WRITE:/ 'Original word: ', WORD.
CALL METHOD EXIT->METHODE
CHANGING
PARAMETER = WORT.
WRITE:/ 'Changed word: ', WORD.

10. Filter Dependence Type of filter: data element with search help
Sometimes it is important for partners to be able to implement and deliver a single add-in with different filter values (for different countries, for example). For this reason, add-ins can be defined for specific filter values.
Type of filter: data element with search help
Parameter flt_val must be suitably filled when the add-in is called.
Add-in must be implemented for a specific filter value.

11. Filter-Dependent Add-Ins
Add-in definition
Add-in implementation
IF_app_exit
Type of filter dependency:
country-specific
... Exit type ref to IF_app_exit.
Country = ‚J‘.
Call method exit->mth1
exporting
flt_val = country.
Exit call
...
Country: China
Country: Japan

12. Business Add-In Manager
Definition part (SE18)
Specification of common Interface (method collection)
Define Add-In Type (publish & subscribe, filter dependent)
Automatic generation of adapter classes
Implementation (SE19)
Select filter value (e.g. country code)
Supply code for interface methods
Activate Add-In