2006 Sep 27 11:16 AM
Hi Everybody
I have some doubts related to enhancement concepts and ALE/EDI. Please clarify the following doubts:---
1) There are differnt enhancement methods as provided by SAP. So can you tell me the difference between User-Exit, BADI ,Enhancment spots, Implicit Enhancemtnts??
2) What is the difference between ALE and EDI, whil both technology uses IDOCS for distributed processing???
Please help me by clarifying the doubts.
Hi Everybody
I have some doubts related to enhancement concepts and ALE/EDI. Please clarify the following doubts:---
1) There are differnt enhancement methods as provided by SAP. So can you tell me the difference between User-Exit, BADI ,Enhancment spots, Implicit Enhancemtnts??
2) What is the difference between ALE and EDI, whil both technology uses IDOCS for distributed processing???
Please help me by clarifying the doubts.
2006 Sep 27 11:20 AM
Difference Between BADI and User Exits:
i) BADI's can be used any number of times, where as USER-EXITS can be used only one time.
Ex:- if your assigning a USER-EXIT to a project in (CMOD), then you can not assign the same to other project.
ii) BADI's are oops based.
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.
Best Regards,
Vibha
*Reward points if it helps
2006 Sep 27 11:27 AM
Hi,
here some infos
Sap provided various type of exit
User-exit : the classical exit . Is implemented by a function module standard called in a standard program that contain a custom include that u can modify.
Screen-exit : with this kind of exit, u can add fields to dynpro standard.Sap provdies also function modules that u can modify to rwad / write data from your custom fields
Field-exit : custom code that u can attach at field-level processi. For example if u want that a field contains olny a certain value, u can use a field-exit
Standard user-exit : in this kind of exit, u must modify the standard code, but sap never write on that exit.
Hope it's clear
Bye
Andrea
2006 Sep 27 11:29 AM
HI,
1. BADI is <b>latest development</b> in enhancements. it uses <b>class concept</b>. normal user-exit does not use any class concept. enhancement spot may be the point where u have call to enhancment like <b>CALL CUSTOMER-FUNCTION 'xxx'.</b>
2. ALE, EDI both technologies use IDoc interface for distributed processing.
only difference b/n ALE and EDI is that in ALE the partner u will be communicating is another SAP system, so it can understand the IDoc format u r sending.
but in EDI, u will be communicating with an <b>EDI subsystem</b>,it will understand the IDoc format u r sending and converts it to a file format. this file format is received and can be understood by the partner which is a <b>non-sap system</b>.
hope it is clear.
reward if useful...
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |