| Status | Approved |
| Owner | |
| Stakeholders | |
| LeanIX Link |
Introduction
This section provides the background, scope, and key requirements for SyWay’s adoption of SAP Business Technology Platform (BTP) as the cornerstone of its global SAP landscape.
Purpose
The purpose of this Application Architecture document is to define a single, authoritative blueprint for how SAP BTP services will be organized, secured, integrated, and managed across all programme phases and regions. It serves as the reference for solution architects, development teams, operations, and audit stakeholders when designing or reviewing any BTP‑based workload
Scope & Objectives
The architecture covers the full BTP footprint required for the SyWay programme, including— but not limited to—Integration Suite, Build Work Zone, Datasphere, PaPM Cloud, Sustainability solutions, Asset Performance Management, Advanced Financial Closing, Global Track & Trace, Document Reporting Compliance, Cloud Identity services, Observability tooling, and SAP Cloud Transport Management.
Primary objectives are to:
Provide scalable and resilient platform services that meet a 99.9 % SLA for production.
Ensure end‑to‑end security and compliance with EU GDPR, US SOX, and China cybersecurity regulations.
Enable efficient DevSecOps with automated transport, continuous integration, and central logging.
Minimise total cost of ownership through sub‑account consolidation, quota pooling, and auto‑suspend for non‑prod runtimes.
Deliver a governed naming and role model that supports audit‑ready change control and segregation of duties.
Key Decisions and Requirements
The following table lists the core requirements that the BTP architecture must satisfy.
| Requirement Identifier | Requirement Description |
|---|---|
Configure SSO for all BTP applications via SAP IAS (proxied to Microsoft Entra ID) | As part of SyWay, a common authentication mechanism (SAML/OIDC via IAS) ensures unified user experience, centralised policy enforcement, and reduced credential sprawl. SSO is enforced in the trust and application configurations. |
Enforce HTTPS/TLS for all endpoints; use SNC for SAPGUI/RFC where applicable | In line with SyWay’s “encrypt-in-transit” approach, HTTP is disabled or redirected. TLS 1.2+ is mandated with managed certificate lifecycle; RFC/SAPGUI channels use SNC to maintain end-to-end confidentiality and integrity |
Segregate environments and regions with dedicated BTP subaccounts | Clear isolation between DEV/INT/TRN/UAT/PAR/PRD and Europe/China/US Sovereign prevents cross-environment impact, simplifies access control, and supports per-region operations and data handling |
Standardise change & transport using Cloud Transport Management (cTMS) with gated approvals | Ensures predictable, auditable promotion of BTP artefacts (e.g., iFlows, APIs, UI apps). Aligns with SyWay release governance, reduces drift, and supports rollback/traceability. |
Use Cloud Connector with Location IDs and principal propagation; secure Destinations (OAuth2/x509 | Provides controlled, audited access to SAP RISE endpoints, avoids embedded credentials, and preserves user identity across hops for fine-grained authorisation. Outbound access is restricted to approved destinations |
Application Architecture
Architectural Decisions
Below Table provides the details of the architectural decisions made based on the rationale.
| Architectural Decision | Description | Rationale |
|---|---|---|
Application Architecture Design
Application Architecture Components
Web Dispatcher
Gateway Server
S/4HANA
ADFS
Application Security
Classification
Authentication
Authorisation
Communication Security
Data Security
Other Controls
System Landscape
Development Environment
Project Test Environment
Quality Environment
Production Environment
Operation Architecture
Change and Configuration Management
Transport Management
Release Management
Monitoring
Application Monitoring
System Monitoring
Sizing
High Availability
Disaster Recovery
Backup/Restore
Maintenance Plan
Service Introduction
Application Category
Support Team
Skill required
Checklist
Exceptions
See also
Change log
Workflow history
| Title | Last Updated By | Updated | Status | |
|---|---|---|---|---|
| There are no pages at the moment. | ||||