Enhancements in SAP ABAP: Types & Step-by-Step Guide

How to Implement Enhancement in SAP ABAP | Step by Step Manual with Practical Example

Every SAP project eventually hits the same wall: the standard programme does 90% of what the business wants and the last 10% needs custom logic. Repackaging stock code is dangerous and breaks on upgrade. Here is where SAP ABAP enhancements come into play.

Contents

• What Is Enhancement in SAP ABAP?
• Change vs Improvement
• Types of enhancement in SAP ABAP are:
• Enhancement Options in SAP ABAP (Enhancement Framework)
• Enhancement Point vs Enhancement Section : What’s the Difference
• Disadvantages ofImplicit Enhancement in SAP
• SAP ABAP Step by Step (Practical example) Enhancement
• ABAP Enhancements – Best Practices
• SAP S/4HANA Enhancements
• FAQs (Frequently Asked Questions)

SAP ABAP Enhancement What is Enhancement?

An enhancement in SAP ABAP is a controlled way to add custom functionality to a standard SAP object (a programme, function module, class or screen) without changing the original SAP delivered code. The custom logic is in a separate object and SAP invokes it at a predefined or available location.

In simple terms, if you need to validate an additional field, change an output value, or add a new column to a standard report, you use an enhancement instead of modifying SAP’s source code directly.

Characteristics of an enhancement:

• It does not touch SAP standard code.
• It is stored in its own repository object, so it's easy to follow.
• It is generally maintained during upgrades and support package updates.
• It is handled like any other development object.

Modification vs Improvement

These two terms are often confused by newcomers and it’s worth getting clear.

Aspect	Change	Improvement
Modifies standard code?	No custom code added	Yes, standard code modified
Upgrade impact	Low, generally survives upgrades	High, needs adjustment through SPAU/SPDD
Access to Key required	Not required for most enhancements	Access to Dev and object required
Traceability	Simple	Complex
SAP advice	Preferred	Last resort

SAP strongly suggests that a standard solution should be extended through an enhancement and not through a change.

Types of Enhancements in SAP ABAP

When searching for enhancements types in SAP ABAP, you are generally talking about the techniques SAP has introduced over the years. Here are the big ones.

1. User Leaves

User exits are enhancements based on includes. Most of them are in SD (e.g. MV45AFZZ in sales order processing). Developers write code within predefined FORM routines. They are simple but restricted to specific modules and are modification-style as the include belongs to SAP's namespace.

2. User Exits

The customer exits are processed using transaction SMOD (display enhancements) and CMOD (create project and activate). They provide function module exits, screen exits and menu exits. They are older, but you’ll find them in many ECC systems.

3. Business Transaction Events (BTE)

BTEs are principally used in financial accounting. They are working on publish and subscribe model where SAP publishes an event and your custom function module subscribes it. They are set up in transaction FIBF.

4. Business Add-Ins (BAdIs)

BAdIs are object-oriented extensions. There are two generations:

• Classic BAdIs are interface-based and are defined in SE18 and implemented in SE19.
• New BAdIs belong to the Enhancement Framework, are defined via enhancement spots and are created with the GET BADI and CALL BADI statements. They support various implementations and filtering.

BAdIs are considered the most flexible and cleanest enhancement technique in general.

5. Enhancement Framework

With the introduction of SAP NetWeaver 7.0 (Enhancement Package 2), the Enhancement Framework unifies the older techniques and adds implicit and explicit enhancement options inside source code. We discuss this in detail in the next section.

6. Includes to Append and Structures and Customising

If you need more fields on a standard table, append structures (and customising includes if available) allow you to add custom fields without changing the original table definition.

7. Field Exits (Obsolescent)

Logic was added to a single screen field using field exits. SAP no longer recommends them, and they are only mentioned here for completeness.

Summary table at a glance

Type of enhancement	Typical area	Transaction	Recommended today?
User exit	SD and others	SE38, SE80	Only if no other exists
CMOD, SMOD Customer Exit	Cross Module		Legacy
BTE	Finance	FIBF	Where applicable
Classic BAdI	Cross-module	SE18, SE19	Yes, if no new BAdI is present
New BAdI	Cross-module	SE18, SE19	Yes (recommended)
Enhancement Framework	Source code level	SE80, SE19	Yes, with care
Table 11. Structure append		SE11	Yes

Enhancement Options in SAP ABAP (Enhancement Framework)

SAP ABAP Enhancement Framework provides two types of enhancement options, implicit and explicit.

Implied Enhancement Opportunities

SAP doesn’t have to mark them. There are implicit options that automatically exist in certain places in the code. Typical locations are:

• FORM routine start and finish
• The beginning and the end of a function module
• The start and finish of method
• end of an include or programme
• End of a structure definition End of a public, protected or private section of a class

SAP has never put a marker there, but you can add your own code in those places.

Enhancement options explicit

SAP developers put explicit options in the source code on purpose. They come in two types:

• ENHANCEMENT-POINT Declared with Enhancement points
• Sections to improve, declared with ENHANCEMENT-SECTION ... END-SECTION-ENHANCEMENT

Explicit options can be grouped into enhancement spots, so they can be easier to find and manage.

Other Capabilities of Framework

• Plug-ins to source code, where the code is injected into an existing object
• Class enhancements, allowing you to add pre-methods, post-methods and overwrite-methods to existing class methods
• Enhancements in function groups: You can insert new function modules or global data

Enhancement Point Enhancement Section

It is one of the most common interview questions in SAP ABAP. The basic idea is straightforward. An enhancement point adds code, while an enhancement section replaces code.

Feature	Enhanced point	Enhanced section
Statement	ENHANCEMENT-POINT	ENHANCEMENT-SECTION... END-SECTION-ENHANCEMENT
Purpose	Insert additional code at that location	Code within section, replace the
Original code	Remains, still runs	Is replaced when an active implementation exists
Multiple implementations	Supported, all can run	Overlapping implementations may conflict, need coordination
Typical use	Add a validation, log or extra step	Change or substitute standard logic
Risk level	Lower	Higher, as standard logic is avoided

In simple terms, to remember this: Use an enhancement point to extend the standard behaviour. Use an enhancement section to override the standard behaviour.

The disadvantages of implicit enhancement in SAP

Implicit improvements are powerful but not always the best choice. The primary disadvantages of implicit enhancement in SAP are:

• Risk of Upgrades: SAP does not guaranty that code positions will not change. After an upgrade or support package the surrounding standard code may change and your logic might behave differently or need rework.
• Poor visibility: There is no marker in the source, so other developers may easily overlook them. More work is required to find all implicit improvements in a programme.
• Hard to debug and trace: A bug may occur in normal code, but the true reason is hidden in an implicit implementation.
• No reusability/grouping: Implicit options do not offer a clean interface like enhancement spots and BAdIs and can not be turned on and off as easily with switch framework logic.
• Conflict potential: If multiple teams improve the same site, the order of execution and shared variables can lead to unexpected side effects.
• Close coupling to internal code. You often rely on local variables and internal structure that SAP never meant to be stable.
• Not fit for clean core: SAP prefers released and stable extension points in modern S/4HANA landscapes over unmarked internal positions.

So an experienced consultant has a simple rule of thumb: check for a BAdI or an explicit enhancement point first, and only use an implicit enhancement if nothing else is available.

Improvement in SAP ABAP Step by Step (Practical Example)

Let us make an implicit enhancement. The example below is illustrative and the names are examples you should adapt to your own programme.

Scenario: Standard report generates output table `gt_output`. The business requires a custom flag (zflag) to be set to X for all rows where the net value is over 100,000 so that we can use a custom ALV column to highlight it.

Requirements:

• A custom field zflag which was already added to the output structure through an append structure (SE11).
• Developer authorisation and a customising or workbench transport request

Step 1: Find the Standard Programme

Complete the transaction and go to System > Status to find the programme name. Another way to find the programme is by using transaction code SE93. You can open the programme in SE80 or SE38.

Step 2 Find the Right Place to Improve

Search the code for the routine that prepares the output, e.g. FORM prepare_output. Use the debugger if you need to , to verify the logic runs where you think it does .

Step 3: Turn on Enhancement Mode

Open the ABAP editor, select Edit -> Enhancement Operations -> Show Implicit Enhancement Options. The available positions are now marked by a clear line in the editor. You can also choose the enhancement (spiral) icon in the toolbar.

Step 4: Develop the Enhancement Implementation

Place the cursor on the implied option at the end of the form, right-click and select Enhancement Implementation > Create Implementation. Or select Edit > Enhancement Operations > Create Implementation.

Step 5: Package and Name Your Implementation

Name the implementation clearly in the customer namespace (e.g. ZEI_FLAG_HIGH_VALUE), add a short description, assign a package and a transport request.

Step 6: Custom Code Coding

Paste the logic into the editor area that opens:

abap
* Implicit enhancement at end of FORM prepare_output
DATA ls_output TYPE ty_output .

LOOP AT gt_output INTO DATA(ls_output).
IF ls_output-netwr GT 100000.
ls_output-zflag = 'X'
EXPORTING zflag FROM gt_output TO ls_output.
IF ELSE.
ENDLOOP

Keep the code short. Add comments explaining why the enhancement.

Step 7. Review & Enable

Perform the syntax check (Ctrl+F2) and start the enhancement implementation (Ctrl+F3). The enhancement is effective only when it is activated.

8. Run the Test

Process a normal transaction, run the report with test data, and verify that the zflag is set correctly. Use the debugger and set a breakpoint inside your enhancement to make sure that it is called.

Step 9: Let the Transporter Loose

After testing, release the transport request to move the change to quality and production systems.

Re-using the same flow for Badi's

If there is a BAdI then the steps are similar but cleaner:

• You can either use SE18 to find the BAdI or you can search for CL_EXITHANDLER=>GET_INSTANCE in the programme (classic) or GET BADI (new).
• Make an implementation in SE19.
• Write your logic in implementing class and implement the method.
• Activate and verify.

ABAP enhancements: Best practice

• Choose BAdI first, explicit enhancement option second, implicit enhancement last
• Document each enhancement with a clear description and reference to the change request.
• Keep logic small Migrate complex code into a user-defined class or function module
• Avoid hard-coding values, use configuration tables whenever possible.
• Use enhancement spots and composite implementation to group related changes together.
• Find out which enhancements already exist on an object using the Enhancement Information System (SE84 > Enhancements).
• Retest all enhancements after each upgrade or support package.
• Use a naming convention so you can easily identify custom objects.

SAP S/4HANA Enhancements

In SAP S/4HANA the focus lies on the clean core principle. On-stack extensibility, key user extensibility (custom fields, logic and UIs) and side-by-side extensibility on SAP BTP are encouraged. Heavy changes to standard code are discouraged. The classic enhancement techniques still work in on-premise and private cloud editions, but the developers who understand both the classic Enhancement Framework and the newer extension models are the most valuable on projects.

FAQs

What is Upgrade in SAP ABAP?

SAP ABAP enhancement allows you to add your own logic or fields to standard SAP objects without modifying the original code. The advantage of this is that the change is more secure and easier to maintain during upgrades.

What are the types of enhancement in SAP ABAP ?

The main types are user exits, customer exits, Business Transaction Events, classic and new BAdIs, the Enhancement Framework (with implicit and explicit options) and append structures.

Difference between Enhancement point and Enhancement section?

The enhancement point allows you to insert code that runs in parallel with the original code. An enhancement section lets you override the code in the section, to bypass the original logic.

Disadvantages of Implicit Enhancement in SAP – What are they?

They are hard to find, hard to debug, and subject to upgrade changes because SAP never marked those positions as stable extension points. They can also come into conflict where several developers upgrade the same site.

What is best enhancement technique in SAP ABAP?

BAdIs are usually preferred. They are object-oriented, support multiple implementations and are defined by SAP as stable extension points.

Can improvements be transferred between systems?

Yes. Enhancement implementations are repository objects and therefore follow the usual transport request process from development to quality and production.

Do I need an access key to submit an enhancement?

For most enhancement techniques – including BAdIs and the Enhancement Framework – you don’t need an object access key, which you would need if you were to modify standard code directly.

Summary

Enhancements in SAP ABAP is one of the must-know topics for any developer who aspires to work on real SAP projects. First know what is enhancement in SAP ABAP, learn the major types of enhancement in SAP ABAP and practice the enhancement in SAP ABAP step by step flow given above. Remember the difference between enhancement point and enhancement section and use the disadvantages of implicit enhancement in SAP carefully so your solutions remain stable after upgrades.

Want practical skills with real project examples? ERPVITS provides SAP ABAP online training where you will learn enhancements, BAdIs, RAP and ABAP on HANA with experienced trainers. Reach out to the ERPVITS team to schedule a free demo session today.