Extended at the edges,
standard at the core
We extend, connect and modernize SAP software, from the SAP ERP 6.0 application to the SAP S/4HANA® suite, and build each change on what SAP has released rather than on its internals, so each new release asks less of your team.
Thanks, we’ll be in touch soon.
{{ heroStatus }}
You’re in good company
A few of the companies we’ve worked with.
When custom code leans on what can change
Many systems running SAP software carry years of custom code, the programs a company adds to SAP’s standard, mostly written in the ABAP® programming language, often by people who have since moved on.
In many of them, a good part of it reads SAP’s internal tables or changes SAP’s own code, neither of which SAP promises to keep the same from one release, SAP’s next version of its software, to the next. Some of it isn’t used at all anymore.
So each upgrade, and the move to SAP S/4HANA, starts by finding it: what’s still used, what it touches, and what the new release changes underneath it.
What we build
The work we do around SAP software. Each change is placed where a new release leaves it standing, and reaches production through your transports, the way SAP moves a change from development to test to production.
Extensions in the core
Logic that runs inside SAP S/4HANA, in ABAP Cloud on the releases that offer it, at the extension points SAP provides and using only the objects SAP has released for it. Each one is tested and moved through your transports.
Apps and services beside the core
Apps and services on SAP Business Technology Platform (SAP BTP), built with SAP’s own frameworks, ABAP Cloud or the SAP Cloud Application Programming Model in Java or Node.js, that reach your system only through released APIs and events.
Custom code checked and lifted
Your ABAP code checked with SAP’s own tools, the ABAP test cockpit and SAP’s usage data, and graded as SAP’s extensibility guide does. What’s used is adapted or rewritten on released objects, and what isn’t is retired.
The move to SAP S/4HANA
A conversion of your existing system or a new implementation, chosen with you, as SAP describes each. The custom code and integrations are readied first, and every step is tried on a copy of the system.
Integrations through released APIs
Connections built on the released APIs SAP lists for its products on the SAP Business Accelerator Hub. Each runs as its own technical user, one only that connection signs in as, with only the authorizations, SAP’s word for permissions, that it needs.
Integrations moved off SAP Process Orchestration
Interfaces moved to SAP Integration Suite with SAP’s own Migration Assessment and migration tooling, on the dates SAP has set, each one tried with real messages before it moves.
SAP Fiori® apps
Apps for the jobs people do every day, built with SAP Fiori elements and SAPUI5, SAP’s own frameworks for them, and following SAP’s design guidelines where SAP asks.
Reports from released views
Reports and data for analysis read through the views SAP releases for them, its CDS views, never straight from SAP’s internal tables.
AI where it helps
Agents built in Joule Studio, SAP’s tool for building agents for its assistant, Joule, can use MCP, the open protocol that lets assistants use tools, and each works under the person’s own authorizations. We set them up for the jobs you agree, and build agents of your own where they fit.
- Connecting any of your systems:Systems & API Integration
- Automation across your tools:Workflow Automation
- Care once it’s live:Support & Maintenance
- Developers in your own team:Hire developers for SAP software
In the core, or beside it
SAP’s guidance is to keep the core, its standard software, as SAP ships it, and to build each change where a new release leaves it standing. SAP calls this a clean core.
A change can live in the system itself, written in ABAP Cloud, SAP’s way of writing ABAP code that uses only what SAP has released for it: released APIs, the interfaces SAP keeps stable, and extension points, the places SAP leaves for custom logic. Or it can live beside the system on SAP BTP, and reach it through released APIs and events.
Broadly, as SAP describes it, a change belongs in the system when it has to run as a standard step runs, on the same data, such as a check when an order is saved. It belongs beside the system when it serves people outside it, combines data from other systems, or runs at its own pace.
Existing code is graded by what it touches, from objects SAP has released, at the top of SAP’s four clean core levels, to changes made to SAP’s own code, at the bottom, and lifted one level at a time.
So each change is placed by what it needs, and new ones are built on released objects wherever your release offers them.
From the landscape to one extension
Your landscape: the core stays as SAP ships it. Changes live at its released edges, or beside it.
One process: the credit check runs as the order is saved, so it lives in the system, at an extension point. The delivery app serves drivers outside the system, so it lives beside it, through a released API.
One extension: it touches only what SAP has released, an extension point and a view of customer data, so a new release shouldn’t ask for it to be rewritten.
SAP keeps what it has released stable from one release to the next, so that’s what every new change is built on.
{{ coStatus }}
Dates you can plan around
SAP provides mainstream maintenance for SAP ERP 6.0, one of the SAP Business Suite 7 applications, until the end of 2027, for its latest three enhancement packages, and SAP says the dates haven’t changed. None of these dates switches a system off: past each one, it keeps running.
Optional extended maintenance follows until the end of 2030, at an extra charge. After that, systems that stay run under customer-specific maintenance, which SAP says can’t cover issues with third-party databases or Java comprehensively, as its agreements for them end with 2030.
Converting a system that runs on another company’s database to SAP S/4HANA is possible only until the end of 2030, SAP says. After that, a move means a new implementation.
SAP Process Orchestration 7.5 has the same dates, and SAP points to SAP Integration Suite as the way forward. For SAP S/4HANA, SAP has committed to keep at least one release in maintenance until the end of 2040.
So the custom code and the integrations are listed first, the path is chosen with them in view, and each step is tried on a copy.
Start with what your code touches
The review covers your system and its release, its database, and where each stands on SAP’s maintenance dates; its custom code: what’s used, from SAP’s usage data, what each piece touches, graded as SAP’s guide does, and what SAP’s checks for the target release find; changes made to SAP’s own code; each integration: whether it runs through SAP Process Orchestration, released APIs or older interfaces, with its technical user and its authorizations; your SAP Fiori apps and the other screens built for your teams; the roles and authorizations of people and integrations; any extensions on SAP BTP, and how changes reach production through your transports; and which features need which licenses or SAP BTP services, as SAP sets them out.
The first step is one piece the business relies on, such as a check, a report or one integration, rebuilt on released objects or moved to SAP Integration Suite, and tried on a copy of the system with real data.
You get a written review and a proposal for the first step.
Questions worth asking
Mainstream maintenance for SAP ERP 6.0 ends in 2027. What are our options?
Your system keeps running past it. SAP offers optional extended maintenance until the end of 2030, at an extra charge, and after that customer-specific maintenance, which SAP says can’t cover third-party databases or Java comprehensively. Or you move to SAP S/4HANA, by converting the system or starting a new one. For its largest and most complex customers, SAP’s Transition Option for SAP ERP supports business continuity from 2031 through 2033, for systems moved to SAP ERP, private edition on the SAP HANA® database before December 31, 2030, with further eligibility requirements. We plan the path with your custom code and integrations in view.
Should we convert our system or start with a new one?
It depends on your custom code, your data and how far your processes differ from SAP’s standard. A system conversion takes your existing system, with its data and adapted custom code, to SAP S/4HANA; a new implementation starts from SAP’s standard and brings across the data you choose, as SAP describes each. SAP says converting a system on another company’s database is possible only until the end of 2030. We weigh both against your system before you decide.
What happens to our custom code when we move?
SAP’s checks for the target release show what each piece needs, and SAP’s usage data shows what’s still used. Code that’s used is adapted or rewritten, on released objects where the release offers them, and code that isn’t is retired, so less of it comes across. How much that is varies from system to system.
Our integrations run on SAP Process Orchestration. What should we do?
There’s time to move them one at a time. SAP Process Orchestration 7.5 has mainstream maintenance until the end of 2027 and optional extended maintenance until the end of 2030, and SAP points to SAP Integration Suite as the way forward. SAP’s Migration Assessment shows what each interface needs, its migration tooling helps move it, and each one is tried with real messages before it moves.
Should a change live in our system or on SAP BTP?
It depends on what the change needs. One that has to run as a standard step runs, on the same data, usually belongs in the system, written in ABAP Cloud at an extension point. One that serves people outside the system, combines data from other systems or runs at its own pace usually belongs beside it on SAP BTP, reaching the system through released APIs and events.
Does it matter whether we run on our own servers or in SAP’s cloud?
For extensions, yes. In SAP’s public cloud edition of SAP S/4HANA, custom code in the system is written in ABAP Cloud, on released objects only. In its private cloud edition and on your own servers, classic ABAP is still possible, and SAP recommends ABAP Cloud for new work from release 2022 on. We check what your edition and release allow before anything is built.
Can you build SAP Fiori apps for our teams?
Yes. Apps for the jobs people do every day, built with SAP Fiori elements and SAPUI5 on the services your system releases. We start with one job and the people who do it, and try the app with them before it goes live.
Can AI assistants work with our SAP data?
Yes, through SAP’s own routes. Agents built in Joule Studio can use MCP, and SAP passes the person’s identity through, so an agent works under that person’s own authorizations. SAP also describes an MCP gateway in SAP Integration Suite that offers your APIs to agents as tools. We set them up for the jobs you agree, with each person’s access kept to what the job needs.
Can you connect our SAP software to our other systems?
Yes, through the APIs and events SAP releases for each product, or through SAP Integration Suite, each connection under its own technical user with only the authorizations it needs. We agree which system owns each record first, then build one connection and try it with real records before starting the next.
Can you build the reports our teams need?
Yes. Each report reads its data through the CDS views SAP releases for it, never straight from SAP’s internal tables, so it’s less likely to change under you at the next release.
Do we need more SAP licenses for this?
Sometimes. Some features need certain licenses or SAP BTP services, as SAP sets them out. We name each license or service the work depends on, and why, before anything is bought.
Can you take over our existing SAP work?
Yes. We start with the review, so we know what each piece of custom code, interface and app does and who answers for it, then take over the transports and the backlog one area at a time.
How do you keep our data secure?
People get roles with only the authorizations their job needs. Each integration and agent runs under its own technical user, with only what it needs. SAP’s security notes are applied as SAP publishes them, and code we add is reviewed before it’s transported.
What does it cost?
It depends on the work: the custom code, integrations and apps involved, whether a move to SAP S/4HANA is part of it, and whether each part is kept, lifted or rebuilt. Before any work starts, you get a written proposal with the scope, the price or rate, and how you pay.
Can we hire SAP developers for our own team?
Yes. We introduce developers who know SAP software within 48 hours of your request, working in your time zone. You meet them first, and decide who joins.
SAP, SAP S/4HANA, SAP ERP, SAP Business Suite, SAP Business Technology Platform, SAP BTP, SAP Cloud Application Programming Model, SAP Fiori, SAPUI5, ABAP, SAP HANA, SAP Integration Suite, SAP Process Orchestration, SAP Business Accelerator Hub, Joule and Joule Studio are the trademarks or registered trademarks of SAP SE or its affiliates in Germany and in other countries. Webair is independent of SAP SE, and isn’t sponsored by, endorsed by or affiliated with it.
Let’s build it better
Tell us which release you’re on, where your system runs, and what its custom code and integrations do. A short call is enough to agree where to start.
Thanks, we’ll be in touch soon.
{{ ctaStatus }}