Applications on SAP CAP
We build applications in the SAP Cloud Application Programming Model using Node.js or Java. Scope may include the service layer, data model, persistence, multi-tenancy and integration with existing SAP systems.
We build applications and extensions on SAP BTP using SAP CAP, Fiori, Workflow Service, Integration Suite and BTP AI Core. We develop functionality outside the ERP core, in line with the Clean Core approach. This is a key part of preparing for an SAP S/4HANA conversion under the Clean Core methodology.
Applications and extensions built on SAP BTP are not part of the ERP core. As a result, converting from ECC to S/4HANA does not require migrating every modification within the same model, shortening the timeline and reducing project risk.
Modifications within the core require additional testing at every upgrade and technical change. Extensions on BTP are decoupled from the SAP core, making them easier to maintain independently of ERP system updates.
SAP CAP and Fiori enable faster development of business applications and SAP extensions than a classic approach based solely on ABAP development within the core. In selected scenarios, this can cut delivery time by 50-70%.
SAP BTP AI Core, SAP AI Foundation and Joule extensions enable AI solutions tied to SAP processes. This allows AI to operate within the context of an organisation's data, permissions and processes, rather than as a separate, generic API.
We build applications in the SAP Cloud Application Programming Model using Node.js or Java. Scope may include the service layer, data model, persistence, multi-tenancy and integration with existing SAP systems.
We design SAP Fiori applications in UI5, extensions to standard applications, Fiori Launchpad configuration and integration with Fiori Elements. The goal is a consistent user experience across the SAP environment.
We build approval workflows, process automation and integrations with Action Center and SAP Build. Scope may include low-code workflow, approval processes and scenarios spanning SAP and other enterprise systems.
We deploy custom AI models in SAP BTP AI Core, integrate them with Joule, and design controlled access to SAP data. The goal is to put AI to work within SAP processes while preserving security and data-access principles.
We design and implement integrations between SAP and systems such as Salesforce, Workday, Microsoft Dynamics and custom applications. We work with iFlows, data mapping, integration monitoring and APIs.
We analyse custom code and modifications in ECC, prepare a migration plan to SAP BTP, and recommend refactoring or retiring selected extensions. This is a key part of preparing for an SAP S/4HANA conversion.
An SAP BTP project starts with a workshop involving the client's SAP team. We analyse key processes, existing modifications in the system, the S/4HANA conversion plan, and the areas worth moving outside the ERP core. On this basis we prepare a roadmap of extensions on SAP BTP: which functions should stay in the SAP core, which should move to BTP, and which can be simplified or retired. The first application or MVP is typically delivered in 8-12 weeks. Once the solution is validated, we extend the scope to further processes, integrations or applications. The whole engagement follows SAP Activate and Clean Core methodology, with an emphasis on reducing technical debt and preparing the organisation for a safer S/4HANA conversion.
Technology stack
The team's certifications in SAP BTP, SAP development, integration and enterprise systems confirm SNOK's readiness to deliver SAP BTP and Clean Core projects end to end.
Industrial manufacturer
Migration of ECC modifications to SAP BTP ahead of an S/4HANA conversion. The project reduced custom code in the system core by 70%.
Retail sector company
Custom Fiori apps for the order process, integrated with SAP S/4HANA Cloud.
Healthcare operator
Approval workflow on SAP BTP integrated with SAP HR and Document Understanding.
Classic ABAP development often involves modifications within the SAP core: Z* transactions, extensions and changes affecting the standard system. Clean Core assumes the core stays as untouched as possible, with extensions built outside it - for example on SAP BTP. This makes S/4HANA conversion, upgrades and long-term maintenance easier.
Yes. ABAP Cloud - in the Embedded Steampunk model or on SAP BTP - is a fully valid option aligned with Clean Core. Alternatively, applications can be built in Node.js, Java or TypeScript using SAP CAP. The choice of technology depends on the client team's skills and the type of extension.
SAP BTP's licensing model is consumption-based. An organisation pays for actual usage of the chosen components, so proper planning of the architecture and BTP commitments is important. SNOK helps optimise the scope of services before purchase and monitor consumption in the production environment.
Yes. We analyse Z* modifications and custom code in ECC, classify them by decision: keep in the core, move to SAP BTP, or retire. The result is a migration plan for extensions, particularly relevant ahead of an SAP S/4HANA conversion.