The language SAP is written in, what gets built with it, and why your custom code is the biggest variable in a migration.
ABAP (Advanced Business Application Programming) is the language SAP's applications are written in, and the language customers use to extend them. Reports, interfaces, data conversions, enhancements and forms are all ABAP. On HANA the emphasis shifted to pushing logic down into the database through CDS views rather than looping in application code.
Custom ABAP is where a migration budget is actually decided. Every customer accumulates code: reports someone needed in 2012, interfaces to systems since retired, enhancements written around a process that changed. At migration each one has to be assessed, and the proportion that is still used is almost always far lower than anyone expects.
Custom reporting where standard output does not fit. Historically the largest category, and the one most reducible.
User exits, BAdIs and enhancement points that alter standard behaviour at defined places.
IDoc processing, file handling and API calls to and from surrounding systems.
Invoices, purchase orders and statements through SmartForms or Adobe Forms.
Core Data Services define the model close to the database; RAP builds OData services for Fiori on top of it.
A business needs an extra field on the sales order to carry a customer's internal reference. There are three ways to deliver it, and the choice determines the cost of every upgrade for the next decade.
The worst is to modify the standard include directly. It works immediately, and at every upgrade the modification is flagged and someone has to reconcile it by hand — forever, by a person who was probably not there when it was written. The middle option is an append structure plus a sanctioned enhancement point: still in the core, but using interfaces SAP commits to keeping, so upgrades pass through cleanly. The best, where the requirement allows, is to hold the extension outside the core entirely and read it through an API, which leaves the core untouched.
The three take roughly similar effort to build. They differ by an order of magnitude in what they cost to own. This is why the useful question to ask a developer is not whether they can do it but which of the three they are proposing — and why a custom code inventory for a migration is largely an exercise in finding out how many times the first option was chosen.
| Term | What it means |
|---|---|
| Report / program | A standalone executable, historically the most common form of custom ABAP. |
| Enhancement point | A sanctioned place to add logic without modifying SAP's code, so upgrades stay clean. |
| Modification | A direct change to SAP-delivered code. Flagged at upgrade and requires manual adjustment every time. |
| ABAP Dictionary | Where tables, structures and data elements are defined. Changes here ripple widely. |
| Clean core | The principle of keeping custom logic out of the core, with extensions side-by-side instead. |
You cannot scope a migration without knowing what exists and what actually runs. Usage statistics usually surprise people.
Modification rather than enhancement makes every upgrade an adjustment exercise. Use the extension points.
Classic ABAP patterns that pull data and loop are slow on HANA. Push the work down.
Retirement is a legitimate outcome. Code with no execution history in a year rarely needs migrating.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Modifications vs enhancements | How much custom logic sits in the upgrade path. Modifications should be near zero. | |
| Dead custom objects | Programs never executed in the last year. Typically a large share, and free to retire. | |
| Objects with no documentation | Maintenance risk, and the first thing that bites when the author leaves. | |
| Code inspector findings | Static analysis results for performance and security. Cheap to run and routinely skipped. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.