Вы находитесь на странице: 1из 3

Business Add-Ins are a new SAP enhancement technique based on ABAP Objects.

They can be inserted into the SAP System to accommodate user requirements too specific to be included in the standard delivery. Since specific industries often require special functions, SAP allows you to predefine these points in your software. As with customer exits two different views are available: In the definition view, an application programmer predefines exit points in a source that allow specific industry sectors, partners, and customers to attach additional software to standard SAP source code without having to modify the original object. In the implementation view, the users of Business Add-Ins can customize the logic they need or use a standard logic if one is available. In contrast to customer exits, Business Add-Ins no longer assume a two-level infrastructure (SAP and customer solutions), but instead allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Definitions and implementations of Business Add-Ins can be created at each level within such a system infrastructure. SAP guarantees the upward compatibility of all Business Add-In interfaces. Release upgrades do not affect enhancement calls from within the standard software nor do they affect the validity of call interfaces. You do not have to register Business Add-Ins in SSCR. The Business Add-In enhancement technique differentiates between enhancements that can only be implemented once and enhancements that can be used actively by any number of customers at the same time. In addition, Business Add-Ins can be defined according to filter values. This allows you to control add-in implementation and make it dependent on specific criteria (on a specific Country value, for example). All ABAP sources, screens, GUIs, and table interfaces created using this enhancement technique are defined in a manner that allows customers to include their own enhancements in the standard. A single Business Add-In contains all of the interfaces necessary to implement a specific task. The actual program code is enhanced using ABAP Objects. In order to better understand the programming techniques behind the Business Add-In enhancement concept, SAP recommends reading the section on ABAP Objects. More information about Business Add-Ins is contained in the following sections: Business Add-Ins: Architecture A Comparison of Different Enhancement Techniques Defining Business Add-Ins Calling Add-Ins from Application Programs Implementing Business Add-Ins Filter-Dependent Business Add-Ins Multiple Use Business Add-Ins Menu Enhancements Screen Enhancements Business Add-Ins: Import Procedure

Enhancements in SAP ABAP [ Introduction ]


Enhancements are the means by which we add our own/ modify existing functionality to SAP's standard business applications. If you try to modify any SAP standard program, it will ask you for access key which you can get from SAP market place by requesting SAP. But enhancements normally dont require any special access key and can be implemented directly There are 4 ways of doing enhancements in SAP:

1. User exits: These are technically modifications. SAP provides many subroutine(s) with name USEREXIT_ * (i.e ex: FORM USEREXIT_001 ) These are saved in many includes which can be found via SE80 >> Search for Package VMOD. These are also called as Form exits. Custom coding can be done in the subroutine. But the main disadvantage of these exits are : It requires Access key and only SD module supports this kind of enhancements. 2. Customer exits: Technically enhancements. Will not affect the source code of SAP program and hence no problem during upgrade. There are 3 kinds of Customer exits a) Function exits: Provided by means of FM's(Function modules) .The code for the function module is written by the developer. You are not writing the code directly in the function module, but in the 'Z' include that is implemented in the function module. Ex: open any Function module EXIT_* in se37 Ex: EXIT_SAPMF02K_001. but in the SAPMF02K program you will see this as CALL CUSTOMER-FUNCTION '001' It will have a Z include file , just edit the file directly . No Access key required. b) Menu Exits: Enhances the menu available in standard SAP program. Developer can add his/her own text and logic for the menu. Function codes for menu exits all start with "+". Format: +CUS (additional item in GUI status) c) Screen exits: Used to enhance the screen, add elements in screen etc Format: CALL CUSTOMER-SUBSCREEN CUSTSCR2 3. BADI's: Business Add-Ins may be simply defined as an object-oriented extension of the SAP enhancement technique. Multiple implementation for same BADI can be done as BADI supports encapsulation of data. 4. Enhancement Frameworks: This is the new kind of enhancement technique provided by SAP. These provides some hooks or places where custom logic can be coded in the standard program.There are 2 kinds of Enhancement frameworks:

a) Implicit and b) Explicit Enhancements We will cover all these enhancements techniques in details in upcoming posts.

Definition - What does Explicit Enhancement Point mean? An explicit enhancement point is an ABAP source code plug-in provided by SAP beginning in its Enterprise Core component version onwards. Prior to the release of the enterprise Core Component version, objects could be modified by either user-exits, business add-ins or by modifying the standard code of the SAP objects. Explicit enhancement points are part of the enhancement framework provided by SAP for reducing the complexity involved in the customer system landscape. They provide another source code enhancement technique that is flexible and provides upward compatibility. Techopedia explains Explicit Enhancement Point Explicit enhancement points and explicit enhancement sections are the two options available for explicit enhancements from enterprise core component version onwards. Unlike the explicit enhancement section, which activates customer code and deactivates the standard ABAP code if implemented, explicit enhancement points act like business add-ins or user-exits by providing additional space for code along with standard code. Unlike implicit enhancement points, which are provided at predefined points within ABAP code, explicit enhancement points are provided by SAP at different areas for different objects. The position of enhancement points in an ABAP programs is marked and has a general look and attributes: ENHANCEMENT-POINT <name> SPOTS <spot1> [<spot2>] [STATIC/DYNAMIC] ... Explicit enhancement points can be enhanced using the same enhancement techniques as in implicit enhancements and explicit enhancement sections.