Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Difference between user exit/Function exit / Customer exit and BADI

Former Member
0 Likes
1,004

Hi Guys,

I am confused with the types of exits-user exit/Function exit / Customer exit and BADI.

Can you tell me the difference between the different exits/Enhancements?

Classify the following:

what is the one which is shown in SMOD under enhancements? There are 3 sections in that - Function module, Screen and includes.

What is the one which are called using -

Call Customer-Function 001?

Regards,

Guru

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
680
3 REPLIES 3
Read only

Former Member
0 Likes
680

hi,

The standard applications do not offer some of the functionality you need. The R/3 enchancement concept allows you to add your own functionality to SAP's standard business applications.

Different types of enhancements

Enhancements using customer exits

Customers' potential requirements which are not included in the standard software are incorporated in the standard as empty modification 'shells'. Customers can then fill these with their own coding. Enhancements can relate to programs, menus and screens. Upward compatibility is assured. In other words, SAP guarantees that the jump from the standard software to the exit and the interface which call the exit will remain valid in future releases.

Enhancements to ABAP/4 Dictionary elements

These are ABAP/4 Dictionary enhancements (creation of table appends), text enhancements (customer-specific key words and documentation for data elements) and field exits (creation of additional coding for data elements).

advantages of enhancements

Do not affect standard SAP source code

Do not affect software upgrades

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.

Various types of customer exits

Menu exits

Screen exits

Function module exits

Keyword exits

Menu exit

Adding items to the pulldown menus in standard R/3 applications .

Screen exit

Adding fields to the screens within R/3 applications. SAP creates screen exits by placing special subscreen areas within a standard R/3 screen and calling a customer subscreen from within the standard dynpro's flow logic.

Function module exit

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

keyword exit

Add documentation to the data elements of key words defined in the ABAP/4 Dictionary. The system displays this documentation whenever a user presses F1 to get online help for a screen field

Hope this helps, Do reward.

Read only

0 Likes
680

Hi,

A use exit is a function module in which we can write our piece of code as per our requirements. For example if you want to populate a default valus in one of the fields in a standard transaction a User Exit can help you (only if there is one).

A Customer Exit can have different functionalities, say a new screen can be added to a transaction (with some config changes), it allows you to display or hide some fields/screens/tabs on the transaction. It's nothing but changing the standard transaction as per your requirement.

Thanks,

Anil.

Read only

Former Member
0 Likes
681