#31 One App, Many Systems ​

A side-by-side app (#30) already runs outside the system it serves. Which invites a question worth asking out loud: how many systems can it serve?

More than one. The app lives on the SAP BTP ABAP Environment and reaches each S/4 system through its released APIs, so the connection is configuration rather than code.

That is a real SaaS shape, in ABAP — a sentence that would have raised eyebrows not very long ago. One codebase, deployed once, serving several customer tenants, each with its own system, its own data and its own release, none of them needing anything installed. Nobody transports into a customer system, nobody schedules a downtime there, and a fix reaches every tenant at once.

The nice part is that nothing was added to make this possible. It works because of what the earlier articles already established. The frontend is a shell that renders whatever arrives, so it does not care which system produced it. The app is one class with no artifacts beside it, so there is nothing per-tenant to deploy. And the state that makes a roundtrip work travels with the request, so no server holds a session belonging to one customer.

The limits are the ones the shape implies, and they are not small. Every tenant needs its released APIs reachable. Latency is now on the wire. And the tenant's data boundary is something the app has to enforce rather than something the system enforces for it. One app now sees several customers, and that is a responsibility the ABAP authorization concept was not asked to carry here.

A framework with nothing to install per system is a framework that can serve systems it was never installed on.