DB user exit/screen exit/function module exit/menu exit/ BADI

[Former Member]

hi,

1)what is difference between user exit/screen exit/function module exit/menu exit/ BADI?

2)what is the advantages of BAPI?

3)how to handle the table control during BDC recording?

POints will be rewarded

thanks in advance

[Former Member]

User exit - A user exit is a three character code that instructs the system to access a program during system processing.

SXX: S is for standard exits that are delivered by SAP. XX represents the 2-digit exit number.

UXX: U is for user exits that are defined by the user. XX represents the 2-digit exit number

Customer exit - The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications. SAP creates customer exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks. *-- Mani

The following document is about exits in SAP :-

The R/3 enhancement concept allows you to add your own functionality to SAP’s standard business applications without having to modify the original applications.

SAP creates user exits for specific programs, screens, and menus within standard R/3 applications. These exits do not contain any functionality. Instead, the customer exits act as hooks. You can hang your own add-on functionality onto these hooks.

Types of Exits

There are several different types of user exits. Each of these exits acts as hooks where you can attach or "hang" your own add-ons.

Menu Exits

Menu exits add items to the pulldown menus in standard SAP applications. You can use these menu items to call up your own screens or to trigger entire add-on applications.

SAP creates menu exits by defining special menu items in the Menu Painter. These special entries have function codes that begin with "+" (a plus sign). You specify the menu item’s text when activating the item in an add-on project.

Screen Exits

Screen exits add fields to screens in R/3 applications. SAP creates screen exits by placing special subscreen areas on a standard R/3 screen and calling a customer subscreen from the standard screen’s flow logic.

Function Module Exits

Function module exits add functions to R/3 applications. Function module exits play a role in both menu and screen exits.

When you add a new menu item to a standard pull down menu, you use a function module exit to define the actions that should take place once your menu is activated.

Function module exits also control the data flow between standard programs and screen exit fields. SAP application developers create function module exits by writing calls to customer functions into the source code of standard R/3 programs.

These calls have the following syntax:

CALL CUSTOMER-FUNCTION ‘001’.

Field Exits

Field exits allow you to create your own programming logic for any data element in the Dictionary. You can use this logic to carry out checks, conversions, or business-related processing for any screen field. Example: The data element BBBNR identifies a company’s international location number. You might want to set up your R/3 System so that all international location numbers are larger than 100.

The field exit concept lets you create a special function module that contains this logic.

You assign the special function module to the data element BBBNR. You then assign the module to any programs and screens in which users can add new international location numbers. When you activate your field exit, the system automatically triggers your special routine whenever a user enters a company location number.

regards.

aswin.

[Former Member]

Advantages of Using BAPIs

Use

BAPIs are standardized methods of SAP Business Objects that enable customers and third parties to integrate their software components with the R/3 System and the Business Framework. This section lists some of the advantages of using BAPIs as a means of accessing the SAP Business Objects.

Business Standard

SAP Business Objects and their BAPIs are the standard for the business functions in the R/3 System. They enable the R/3 System and other software products to be integrated on one business level.

Standards Conformance

BAPIs are being developed as part of the SAP joint initiative with customers, partners, and leading standards organizations. BAPIs are becoming a communication standard between business systems.

You can access SAP Business Objects and their BAPIs by using object-oriented interfacing technologies such as Microsoft's COM/DCOM (Component Object Model/Distributed Component Object Model).

The SAP Business Objects already comply with the Object Application Group (OAG) specifications, and, in conjunction with ObjectBridge from VisualEdge, conform to the Object Management Group's CORBA (Common Object Request Broker Architecture) guidelines.

Stability and Downwards Compatibility

Once SAP has developed and released a BAPI, its interface definition and parameters remain stable for the long term. This ensures that application programs are not affected by changes to the underlying R/3 software and data.

SAP can make any necessary extensions to the BAPIs, for example, add optional parameters, without destabilizing the operation of existing applications and, at the same time, can offer the enhanced functionality to new applications.

For information on SAP BAPI policy see SAP Enhancements to BAPIs.

Object Orientation

As methods of the SAP Business Objects, BAPIs provide access to R/3 data and processes following an object-oriented programming model. BAPIs can be called using object-oriented interfacing technologies, such as COM/DCOM, thus enabling software components from SAP and third parties to interact freely.

Openness

You can access BAPIs from all development platforms that support the SAP Remote Function Call (RFC) protocol.

regards,

aswin.

[Former Member]

Hi

chech these links for user exists its usefull

http://www.allsaplinks.com/user_exit.html

http://help.sap.com/saphelp_47x200/helpdata/en/dd/561602545a11d1a7020000e829fd11/frameset.htm

http://www.sap-basis-abap.com/sapab013.htm

http://www.sap-img.com/abap/what-is-user-exits.htm

for bapis

1. BAPI's are the RFC enabled function modules, i.e u can connect to 3rd party systems using this. In BDC's we can't do this, it is local to SAP

2. BDC's use transaction screen flow to update data base, but BAPI's use standard function modules to do this.

3. Explicit commit work should be done to BAPI's, for BDC it is automatically done..

Just check the link below for all the links for each and every topic.

/thread/196182 [original link is broken]

to handle the table control during BDC recording

go thr this

-charitha

[Former Member]

Hi Jayasree,

1) User-exit: Is a place where u define modification to SAP Standards with out

effecting SAP Standards.

2)Screen-exit:This comes in user-exit. Or the screen exit/field exit/menu exit is a componend of user-exit. Okay Now screen exit is a place where i add subscreens to SAP standard Transaction codes. Note: Only Subscreen can be added to SAP Standard transaction by using screen-exits.

3) Function Exit.: Is a place where u write the code for an screen exit/field exit/menu exit.

4)Menu exit: Is a place where u add custom menu options to SAP Standard transaction.

5)BADI: Like SAP always provides developers with new and easier way of developments.BADI is also provided as an advancement for user-exits. There r many benifits apon user-exits.

6) Advantages of BADI:

i)To modify a standard tcode some times many User-exits are involved but if u use BADI then one BADI can solve the problem.

ii) There is one good feature in BADI which is not in user-exit and that is filter types. Filters will filter the number of times that BADI will triger.

7) Table controls can be handeled but the line number given benith every table control in a transaction.(not sure but this could help).

Kind Regards,

Sharat Chandra.

[Former Member]

Difference between a BADI and UserExits

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.

Regards,

~Sri.