| Status | Approved |
| Owner | |
| Stakeholders |
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, Finance‑close services, Global Track & Trace, Document Reporting Compliance, identity services, observability tooling, and 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.
Requirements
The following table lists the core non‑functional requirements that the BTP architecture must satisfy.
| Requirement Identifier | Requirement Description |
|---|---|
| NFR‑SEC‑01 | All data in transit must be encrypted using TLS 1.2+ (HTTP) and SNC (SAP GUI). |
| NFR‑SEC‑02 | 100 % of productive users must authenticate via Single Sign‑On (IAS ↔ Entra ID). |
| NFR‑AVA‑01 | Productive BTP services shall achieve ≥ 99.9 % monthly availability. |
| NFR‑PERF‑01 | Integration Suite must handle a sustained throughput of 250 messages/sec. |
| NFR‑SCAL‑01 | Datasphere spaces must support burst scaling to at least 4 vCPUs per space. |
| NFR‑COST‑01 | Non‑prod runtimes shall auto‑suspend during idle windows, targeting ≥ 30 % cost saving. |
| NFR‑OBS‑01 | All sub‑accounts must forward logs to Cloud Logging with a lag ≤ 5 minutes. |
| NFR‑TRN‑01 | Transport approvals and artefact versions must be retained for audit for 7 years. |
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. | ||||