Take two requests from the same business. Customers want a web page that shows the status of their sales orders. Finance wants a customer-specific pricing rule changed. Both are extensions to S/4HANA, and they belong in different places. The page belongs on SAP BTP. The pricing rule belongs in ABAP, inside the core. Deciding which goes where is the real work of a BTP extension strategy.
This example is illustrative, not a client case. The reasoning applies to any SAP estate.
The customer portal: a good fit for side-by-side
The order status page is used by people outside the company. It needs its own release cycle and its own user interface, and it must not put load on the ERP system. That is the case for building side-by-side on SAP BTP.
The page reads sales orders from S/4HANA through an OData service. If S/4HANA sits in a private network, the SAP Cloud Connector provides the secure link from BTP. The extension stores nothing that belongs in the ERP and changes nothing in it. If the portal is down, orders still flow.
The risks to plan for are authorisation and volume. Decide which customer can see which orders before the first line is built, and test how many calls the OData service can take.
The pricing rule: keep it in ABAP
A customer-specific pricing rule reads condition records and document data on every order line. It runs inside the transaction, and its result decides what the order is worth. Moving it to a separate platform means a network call in the middle of order entry. It also means a second place to maintain logic that finance already trusts.
This ABAP is business IP, not debt to purge. It encodes how the company sells. The sensible step is to modernise it where it stands: cleaner structure, tests, and the ABAP RESTful Application Programming Model (RAP) for anything new. Move it only if there is an architectural reason, not because a core without custom code looks tidier.
A test for each extension
Ask four questions of every custom object before choosing its home.
- Who uses it? External users and new interfaces point to BTP. Users inside a standard transaction point to the core.
- How tightly is it tied to SAP data? Logic that reads and writes core tables in the middle of a transaction stays in ABAP.
- How often does it change? Logic that changes on a different cycle from the ERP benefits from living apart from it.
- What happens if the link fails? If a failed call would stop order entry, do not put a network between the two.
Some extensions will answer in both directions. In that case, start in the core, and move out later if the case becomes clear.
Where to start
List your custom objects and sort them against these four questions. Most estates find a small group that clearly belongs on BTP, a larger group that clearly stays in ABAP, and a middle group that needs a closer look. The first two groups can be planned at once. The middle group is where an architecture review earns its time.
How ETZ Global helps
ETZ Global builds on SAP BTP and develops ABAP in the same team, so the decision about where an extension lives is made on its merits, not on the skills available. We assess your custom code, classify each extension, and modernise the code that should stay in the core.
Contact ETZ Global to review your BTP extension plan.