SAP ecosystem at a glance

Atlas targets one product — S/4HANA — but S/4HANA does not exist alone. It sits at the center of a small family of SAP products that share a database, a history, and a set of conventions. Knowing which family member does what is the difference between asking Atlas for something it can deliver cleanly and asking for something that has to live somewhere else.

SAP universe at a glance — Atlas's scope highlighted.

A useful way to read the diagram is from the inside out.

S/4HANA is the current-generation ERP — the transactional system of record for finance, logistics, and operations. This is where Atlas plans. Every CDS view it produces is meant to live here.

HANA is the database underneath S/4HANA. It is a column-store, in-memory engine, and it is the reason S/4HANA exists as a separate product from its predecessor: the earlier generation (ECC) was built for row-store databases and did not take advantage of column-store execution. Atlas cares about HANA because every CDS view it emits compiles to a single HANA SQL statement — the shape of that statement, and whether HANA can execute it in one pass, is what “a good CDS view” means.

ECC is that earlier generation. Atlas does not plan for ECC directly; it reads ECC structures only to understand what a conversion to S/4HANA is being asked to preserve.

BW is SAP’s analytical warehouse — a separate system for reporting and large aggregations. It shares conventions with S/4HANA but has its own modeling rules and its own notion of pushdown. Atlas interoperates with BW (it can read from and feed it) but does not plan against it.

BTP is the extension platform that sits outside the ERP core. It is where custom code, side-by-side services, and anything that would violate SAP’s clean-core principle belongs. When Atlas generates something that cannot cleanly live inside S/4HANA, BTP is where it goes.

Why this shape matters for how Atlas plans

Before Atlas writes code, it decides which of these systems the request belongs to, because the rules are different in each. A view targeted at the S/4HANA core is constrained by clean core: Atlas can extend but not modify. A view targeted at BW is constrained by BW’s pushdown rules, which differ from HANA’s. A service targeted at BTP is governed by BTP’s stability contract, which is weaker than the ERP core’s but gives you ownership of the surface.

That placement decision is made first. Only once Atlas knows where the work lives does the planner pick up the pieces of how to do it.