User Exit - Explicit Enhancement Point

"When an enhancement is used inside a custom program without disturbing the source code, it is called Explicit enhancement. Here the program is not SAP standard one. That is why it is called explicit. If it is standard one then it will be called implicit. We already have covered the implicit enhancement. Explicit enhancement is saved in a package and transport in a similar way of implicit enhancement. Explicit enhancement has two types. 

1. Enhancement Point – when we use point, we can add additional functionality to the original program. Here the original program executes with enhanced function. 
2. Enhancement Section – when we use section, the original program is not executed. The enhanced program is executed. 

In the following example we have demonstrated an explicit enhancement point. In this program originally we have printed the output of a program with no header information. Now we create an explicit enhancement point where the header information has been implemented. Hence the final output shows the complete output of the Airline information." - Author: SANDIP ROY

Read the full article here

Enhancement Framework – Introduction

The ABAP Enhancement Implementation concept allows you to easily enhance the standard SAP delivered functionality with your desired one. The ABAP Enhancement Implementation concepts have been in SAP for quite some time now.

What is an Enhancement

An enhancement is used when you need to enhance any standard SAP delivered functionality by introducing new code. There are certain ways to achieve the enhancement:

• Core Modification – You obtain the access key by registering the object with SAP and make the necessary changes. This is more dangerous and thus least preferable among other techniques. What makes it more dangerous is when SAP provides any OSS note, or during an upgrade, there is a chance of losing your changed functionality if you don’t perform the proper SPAU activity.
• User Exit – You find SAP delivered Subroutines (PERFORM) which begins with USEREXIT_ in the standard SAP programs. To implement the user exit, you would need to also register the object through OSS. They are little bit safer from an upgrade point of view as they are in a separate include.
• Customer Exit – You find SAP provided function exits with CALL CUSTOMER FUNCTION ‘001’. This would be a FM with an include. This include would not be delivered by SAP. If you need your new functionality, you need to create the include and implement your code. You would need to create Customer Enhancement Project in CMOD using the Enhancement which houses the Exit function SMOD.
• BADI (Business Add Ins) – are based on the Object Oriented Concept. Std SAP provides you with the BADI calls. You would need to Create the BADI implementation based on the BADI definition. Then you can add your code in the implementation which is essentially a method in the class. You can implement the same BADI multiple times, if the BADI is set for multiple implementations.