Doubt : userexit/badi

Question

hi experts,
if someone asks you to give atleast three differenece between badi and userexits,then what would be the answer??
Please i need these difference.
Points will be awarded for sure.....
Thanks,
Gaurav

Answer 1

Hi Gaurav,
  Difference Between BADI and User Exits
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.
These are two different ways of implmenting similar functionality.
1. BADI's - Use Classes / Methods to implement the custom functionality
2. User Exits - Use functions to implement the same.
Badi is a OO concept.
You can do multiple implementation of BADI but user exit only once.
For badi use se18 and se19 t-code
for user exit use smod and cmod t-code
BADI is just an object-oriented version of user-exit. Instead of entering program code into some function module (as in customer-exit), you define some class which has to implement predefined methods and those methods are fired at predefined points just like an old user-exit. Some BADI can have multiple independent implementations which is much better for software deployment as several developers can implement the same BADI independently.
Difference between BADI and User Exits
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
BADI
Business Add-Ins are a new SAP enhancement technique based on ABAP Objects.
Badi’s allow for a multi-level system landscape (SAP, partner, and customer solutions, as well as country versions, industry solutions, and the like). Business Add-Ins can be created at each level within such a system infrastructure
Some BADI can have multiple independent implementations which is much better for software deployment as several developers can implement the same BADI independently.
Customer-exit
CUSTOMER EXITS(enhancements) are FUNCTIONS so they are called using CALL FUNCTION (or more exactly CALL CUSTOMER FUNCTION
customer exits assumes a two-level infrastructure (SAP and customer solutions)
Customer-exit implemented in one project cannot be implemented in other.
User-exits(modifications)
USER EXITS are FORMS and are called by SAP standard programs using PERFORM.
Inside the form (user exit) you can read and change almost any global data from host program.
User exits are more flexible because you have more information to use in your code but on the other hand , it is very easy to manipulate erroneously global data and lead the standard program to a dump or even to make database inconsistent.
User-exit doesn’t have any classification.
Basically designed For SD module
User-exits can be written only using access-key
With user-exits the code , the developer has written will not be there for next version unless modification assistance tool is used
http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/badi-vs-user-exit-405324
http://www.sapfans.com/forums/viewtopic.php?t=172792
http://sap.ittoolbox.com/groups/technical-functional/sap-r3-dev/badi-vs-user-exit-405324
http://www.sapfans.com/forums/viewtopic.php?t=172792
http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
diff between badi n customer exits........
http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
https://forums.sdn.sap.com/click.jspa?searchID=519283&messageID=2515351
https://forums.sdn.sap.com/click.jspa?searchID=519283&messageID=2627911
https://forums.sdn.sap.com/click.jspa?searchID=519283&messageID=2847358
https://forums.sdn.sap.com/click.jspa?searchID=519283&messageID=2584155
https://forums.sdn.sap.com/click.jspa?searchID=519283&messageID=2826338
https://forums.sdn.sap.com/click.jspa?searchID=519283&messageID=2859102
Reward points If it is useful.
kushagra