Anyone who has managed an SAP landscape for over a decade knows this scenario well. The ERP system runs, processes tick along, but under the hood so many modifications, Z-reports, and custom extensions have accumulated that every upgrade turns into a multi-month project. The IT department is afraid to touch anything, because no one fully remembers why someone added that particular user exit back in 2014. Yet the business does not stand still – it needs new integrations, automation, and supporting applications.
Is there a way to extend the capabilities of an SAP system without adding further layers to an already complex core? The answer is SAP Business Technology Platform.
What does SAP BTP actually mean for organisations running on-premise systems?
SAP BTP is a cloud platform that allows you to build extensions, integrations, and automation beyond the boundaries of a traditional SAP system. It can be thought of as an external layer that communicates with the on-premise system through secure interfaces, while physically operating in a separate environment.
For organisations running SAP ERP or ECC, this represents a fundamental shift in approach. Instead of writing another ABAP program inside the system, you can build an application on the BTP platform that pulls data from the ERP, processes it according to business requirements, and returns the results. The source system remains untouched – no modifications to the standard, no problems during upgrades.
“We treat SAP BTP as a safe development zone,” explains Michał Korzeń, CTO at SNOK. “The client can experiment with new functionality, build integrations with external systems, and deploy automation without risking the stability of the production SAP environment. It changes the entire dynamic of development projects.”
The “clean core” strategy – why move logic outside the core?
The concept of a “clean core” is becoming increasingly important, particularly in the context of future S/4HANA conversions. The less custom code there is in the source system, the simpler and cheaper the transformation will be. But the benefits are visible much earlier.
First, updates and patches can be deployed without weeks of regression testing. When extensions run on an external platform, they do not collide with standard SAP objects. Second, the maintenance team gains clarity – it is clear what is vendor standard and what has been added by the organisation. Third, application lifecycle management becomes easier. An extension on BTP can be updated independently of the ERP system’s maintenance window.
Practical use cases for the platform
What does this look like in real projects? Let’s look at a few typical applications.
Document process automation. An organisation processes thousands of purchase invoices every month. Instead of extending the workflow inside SAP, you can build an application on BTP that pulls documents from the system, routes them through an approval process using artificial intelligence services for classification, and then returns the approved items for posting. The entire flow logic sits outside the ERP core.
Supplementary applications for business users. The sales department needs mobile access to inventory levels and customer order history. The traditional approach would require extending the system with dedicated transactions and an interface. The alternative? An application built in SAP Build Apps that connects to the ERP via secure APIs and presents the data in an accessible form on sales reps’ smartphones.
Integration with external platforms. A company uses a third-party CRM system and needs to synchronise customer master data with SAP. Instead of writing custom interfaces in ABAP, it can use SAP Integration Suite on the BTP platform. The tool offers ready-made adapters for popular systems and a visual designer for integration flows.
A bridge to cloud services. An organisation wants to use advanced analytics or machine learning models, but the data resides in the on-premise system. BTP allows selected data sets to be securely exposed to cloud analytics services, while retaining full control over what is shared and with whom.
Security and governance – the foundation of a hybrid architecture
Moving part of the logic to the cloud naturally raises questions about security. How do you control access? How do you monitor data flow? How do you meet regulatory requirements?
SAP BTP’s architecture has been designed with enterprise environments in mind. Communication between the on-premise system and the platform takes place through the SAP Cloud Connector – a component installed in the client’s network that creates an encrypted tunnel without the need to open inbound ports. The administrator precisely defines which SAP system resources are accessible to cloud applications.
Identity and access management is based on the SAP Identity Authentication Service. It can be integrated with a corporate user directory, support multi-factor authentication, and enforce consistent access policies across all applications on the platform. Every API call is logged, which makes auditing and anomaly detection easier.
“Securing the BTP layer requires deliberate design from day one,” emphasises Jarosław Kamil Zdanowski, Partner responsible for cybersecurity at SNOK. “Together with the client, we define what data may leave the on-premise system, who has access to it, and how we monitor its use. The platform provides the tools, but it is the solution architecture that determines the level of protection.”
How does SNOK support organisations through this transformation?
Moving to a model with a BTP layer is not just a technical matter. It requires rethinking the system development strategy, taking stock of existing modifications, and setting priorities for migration.
SNOK helps clients analyse their current SAP landscape – we identify the extensions that generate the greatest technical debt and are simultaneously the best candidates for migration to an external platform. We then design the target architecture, taking into account performance, security, and regulatory compliance requirements.
In the next step, we build prototypes of selected solutions to validate assumptions in practice. Only once we have confirmed that the new architecture meets expectations do we move on to full implementation. This approach minimises risk and allows the organisation to gradually build competence in the new platform.
“It’s not about moving everything to BTP overnight,” explains Jacek Bugajski, CEO of SNOK. “We help clients build a realistic roadmap. We start with the areas where benefits are visible fastest and risk is lowest. With each subsequent project, the organisation gains experience and confidence that the chosen direction is right.”
Preparing for the future
SAP BTP is not merely a response to current challenges in maintaining on-premise systems. It is also an investment in the future. Organisations planning an S/4HANA conversion within a few years can already start putting their landscape in order today. Extensions built on the BTP platform will work with both the current ECC system and the future S/4HANA – it will simply be a matter of reconfiguring the integration points.
What’s more, the skills gained from building applications on BTP – familiarity with modern development tools, microservices architecture, and API management – will pay off regardless of how the fate of any particular ERP system unfolds.
For organisations that want to retain control over their SAP environment while opening up to new automation and integration opportunities, SAP Business Technology Platform represents a natural next step – one that can be taken today, without waiting for a major transformation.
If you would like to discuss how SAP BTP could support the development of your SAP landscape, get in touch with the SNOK team. We can help assess the potential and plan the first steps.
#SAPArchitecture #SAPBTP #CleanCore #DigitalTransformation #TechThursdayWithSNOK #SNOK
Would you like to see this in practice or discuss an implementation for your organisation? Get in touch – we will respond within 48 hours.