SAP BTP MTA & Approuter Architect | Multi-Target Application Generator

⚙️ MTA Architecture Options

Approuter Architecture Pattern

Managed Approuter (SAP Build Work Zone)

Serverless, zero Cloud Foundry compute cost. HTML5 app repo hosted.

Standalone Approuter (Node.js Container)

Custom middleware, custom session headers, Dedicated CF application.

MTA Project ID

Unique reverse-domain identifier for the MTA deployment.

Backend Extension Service

BTP Destination Name

Destination defined in BTP Cockpit pointing to S/4HANA Cloud / on-premise.

HTML5 Fiori App Module Name

Sub-folder and module name containing the UI5/Fiori webapp.

Custom XSUAA Scope Name

Scope assigned to Role Templates in xs-security.json.

# Generating mta.yaml...

// Generating xs-app.json...

// Generating xs-security.json...

# Generating build and deploy script...

🛡️ Clean Core MTA Architecture Verification

Decoupled UI Layer

Fiori application is compiled into static assets and deployed to the BTP HTML5 Application Repository, freeing backend S/4HANA from BSP/MIME static asset hosting.

Destination-Driven Connectivity

Zero hardcoded URLs. Backend calls route through SAP BTP Destination Service with X.509 User Certificate propagation or OAuth2SAMLBearerAssertion.

Automated Dependency Orchestration

MTA lifecycle manages declarative provisioning of XSUAA, Destination, and HTML5 repo services. One-command deployment via mbt build && cf deploy.

⚙️ MTA Architecture Options

🛡️ Clean Core MTA Architecture Verification

Master SAP BTP & Clean Core Architecture