2008 Feb 05 9:41 AM
hi experts,
i have doubt in these three points.can anybody explain these in detail.
1.BAdi is global presence in the sense means that implemented exit can also be used for another standard program or tcode whereas it's not possible with user-exit.
2.we can set filters (like where conditions) in BADI.
3.we can define our own badi's but we cannot implement our own userexits.
points will be awarded for each answer sure.
Thanks,
Gaurav
hi experts,
i have doubt in these three points.can anybody explain these in detail.
1.BAdi is global presence in the sense means that implemented exit can also be used for another standard program or tcode whereas it's not possible with user-exit.
2.we can set filters (like where conditions) in BADI.
3.we can define our own badi's but we cannot implement our own userexits.
points will be awarded for each answer sure.
Thanks,
Gaurav
2008 Feb 05 9:46 AM
2)filters (like where conditions) in BADI.
just go to se18 and give ur BADI name..
then Select 'Attributes' Tab ,there u will find option Filter-Dependent in window named "type"..
check tht filter dependent checkbox and give ur data element/field in the Filter type field say u can give 'MOLGA' ..save and come back..
now go to se19 and implement this BADi and there u can give filter values for filed MOLGA..
i hope this will help..
2008 Feb 05 9:47 AM
2008 Feb 05 9:48 AM
3.we can define our own badi's but we cannot implement our own userexits
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.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |