abap2UI5

Appearance

Use Cases ​

abap2UI5 fits many contexts, whether you work in a cloud-ready environment or with classic ABAP.

For a complete overview, see the Use Cases blog post.

On-Stack Extension ​

Tier 1 Extension ​

For clean-core compliance, build apps that follow "keep the core clean" principles to keep them cloud-ready and upgrade-stable: Tier 1 on-stack extension architecture diagram

Tier 2 Extension ​

If certain APIs you need aren't yet released, you can still build a cloud-ready abap2UI5 app by accessing them via a separate Tier 2 wrapper: Tier 2 on-stack extension with wrapper for unreleased APIs

Tier 3 Extension ​

For a classic extension approach, use unreleased APIs for more freedom to customize and extend your system: Tier 3 on-stack extension with unreleased API access

Side-by-Side Extension ​

Tier 1 Extension ​

Build apps separately from your S/4 system's lifecycle with remote API calls only. Stick to released APIs, and your apps will work with S/4HANA Public Cloud too: Tier 1 side-by-side extension with remote API calls

Tier 3 Extension ​

For more flexibility, build apps whose lifecycle is independent of your S/4 system, with remote API calls: Tier 3 side-by-side extension with remote API calls

Software as a Service (SaaS) ​

With a Tier 1 side-by-side extension, you can connect a single abap2UI5 app to multiple S/4 systems. Use the same abap2UI5 code across customer tenants and remote systems for a real SaaS setup: SaaS architecture connecting one abap2UI5 app to multiple S/4 tenants