DSAG Technologietage 2025 in Wiesbaden: We at buco together with Henkel provided insights into a project that is particularly close to our hearts: the introduction of SAP Build as a central service on the SAP Business Technology Platform

This year, we at buco together with Henkel provided insights at the DSAG Technologietage 2025 in Wiesbaden into a project that is particularly close to our hearts: the introduction of SAP Build as a central service on the SAP Business Technology Platform. The response in the room – and especially the conversations afterwards – showed: Many companies are facing exactly the same questions around governance, security, scaling, and migration of their workflow and automation solutions.

Together with Mirko Feisel (Henkel), Detlev Belser and Reiner Prieß from buco outlined how Henkel established SAP Build as a platform-wide, centrally operated service on the BTP - from architecture principles via Zero-Trust security patterns to operational and migration strategies.

The decision for a central BTP service model wasn't made off the cuff: It addresses fragmentation, accelerates problem resolution, creates uniform architecture and security guardrails, and enables end-to-end monitoring with efficient scaling. In short: Consistency, security, and speed - without silos.

The centerpiece is Henkel's Architecture Shield: a set of binding architecture principles for SAP Build, derived from the group's BTP guidelines. These include:

• Automate Everything – consistent automation of development and operational processes,
• Integrate Wisely – reusability via APIs, Events, Business Rules, and Actions,
• Standardization via SAP API Management (generalization/templatization) and AD-based participant management.

These principles give developers clear recommendations, enforce security requirements, and ensure support and monitoring capability of solutions.

For SAP Build Process Automation, a Zero-Trust design is implemented - including inbound API security and fine-grained scopes via API keys. At the same time, Henkel strictly distinguishes between Design-Time and Run-Time permissions through SAP Build Environments, which increases security, clarity, and changeability.

Advantages of the concept:

• Clean separation of Development/Run-Time,
• Additional security for workflows and integrations,
• Scalability and clear responsibilities,
• Comprehensive governance via CTMS, policies, and logging.

In migration, Henkel compares Reuse vs. Rebuild:

• Reuse: faster to start, familiar options remain – but less future-proof.
• Rebuild: "All-in-one" and future-proof, but requires more time and selective redesign, as not every WFM function is available 1:1.
  Our result: Blueprints for both integrations and developments in Build Process Automation – compliant with architecture principles and Zero-Trust requirements.

• Think centrally, enable decentrally: A central team sets guardrails, projects deliver value – on a unified platform.
• Security by Design: Zero Trust, AD groups, API scopes, and CTMS are not optional, but a basic requirement.
• Standardization beats individual solutions: Templates, policies, and reusable artifacts reduce time-to-value.
• Transparency in operations: Uniform E2E monitoring and auditing (e.g., via SAP CALM/Signavio connection) make quality measurable.

Wiesbaden delivered: full rooms, short distances, lots of energy. Particularly valuable were the discussions after the session – from concrete questions about role and authorization architecture to migration paths and DevOps automation. The exchange with customers, partners, and SAP colleagues was informative, open, and fruitful – exactly what makes a community strong.

Thanks to everyone who participated – and to Henkel and the DSAG Technologietage 2025.

Anyone who wants to dive deeper into governance, Zero-Trust security, or migration strategies with SAP Build on the BTP is welcome to contact us. We're happy to share our first-hand experiences.