Concept card

Seamless Planning

As of 2026-10-10

Edited by Cédric Mary, sole editor and publication director — 27 years in the SAP ecosystem. How these pages are produced, and where automation is used.

What is Seamless Planning?

Seamless Planning is SAC Planning with its model data persisted in SAP Datasphere: one copy of the plan, no replication between the two, plan versions readable in Datasphere the moment they are saved — GA since Q1 2025, the planning layer of Business Data Cloud. It does not write plan values into S/4HANA.

What it is

Seamless Planning is SAP's name for planning in SAP Analytics Cloud whose model data lives in SAP Datasphere. The planning model is still built and operated in SAC Planning (companion C019) — data entry, versions, allocations, calculations and workflow stay in SAC — but its fact and master data are persisted in a Datasphere space, on the HANA Cloud memory of the Datasphere tenant, instead of inside the SAC tenant. SAP announced it in 2024, ran a controlled release in Q4 2024 and made it generally available with the Q1 2025 SAC release; it is positioned as the planning layer of SAP Business Data Cloud (companion C009) and needs no separate BDC licence. For SAP analytics consultants it is the architectural conversation that turns "we are moving off Excel" into a Datasphere + SAC Planning programme, because plan and actuals now share one governed data layer.

Why it matters

With plan data persisted in Datasphere there is one copy of the plan and no reconciliation job — the integration work that used to be the engagement disappears, and governance of the Datasphere space becomes the design decision.
Plan versions are readable by every Datasphere consumer the moment they are saved, which is what makes planning a Business Data Cloud capability rather than an SAC-only feature.
The pattern turns a single-tool complaint into a Datasphere + SAC Planning programme — a bigger deal shape than standalone Planning, but honest only if the client does not expect S/4 write-back from it.

Key points

Mechanism: the planning model is built and run in SAC; its fact and master data are persisted in a Datasphere space — not in the SAC tenant.
No replication between SAC and Datasphere in either direction: one copy of the plan, nothing to reconcile.
Plan versions are Datasphere objects: readable by views, analytic models and data products the moment they are saved.
Live versions (QRC4 2025) mount Datasphere fact views into the planning model as versions — actuals without copying.
Not S/4 write-back: exporting plan data to S/4HANA is a separate SAC capability, scoped and governed on its own.
Direction discipline that survives: sources → Datasphere for actuals; a plan never replaces an actual.
Prerequisites SAP states: one SAC tenant linked 1:1 to one Datasphere tenant, same data centre, SAC on HANA Cloud; no separate BDC licence.
Status: GA since the Q1 2025 SAC release (controlled release Q4 2024); positioned as the planning layer of BDC (companion C009).
SAP Connect (Oct 2026): no Seamless Planning news found; per ERP Today EPM apps (Enterprise Planning, Enterprise Financial Consolidation) are packaged with BDC core capacity from the Q1 2027 roadmap — confirm in writing how that interacts with the Seamless licence position.

Terms used on this page

Seamless Planning: SAC Planning whose model data is persisted in SAP Datasphere: one copy of the plan, no replication, GA since Q1 2025.
Persistence layer: The Datasphere space (HANA Cloud of the Datasphere tenant) that holds the planning model's fact and master data.
Live version: A Datasphere fact view mounted into a planning model as a version — actuals read without replication (QRC4 2025).
Plan export to S/4HANA: A separate SAC capability that writes plan data into S/4HANA; not part of Seamless Planning.
Direction discipline: Sources → Datasphere for actuals; a plan never replaces an actual. The SAC ↔ Datasphere leg is no longer a copy at all.
Five use cases: Finance close · sales planning · workforce planning · S&OP · cash-flow planning.
Tenant link: One SAC tenant linked 1:1 to one Datasphere tenant, same data centre, SAC on HANA Cloud — SAP's stated prerequisite.
Audit-trail Day-1: Cell-level change history enabled at model creation. Cannot retrofit (companion C019).

Sources

Full card available to members. What the full card adds: the full decision framework · the SAP vs Snowflake / Databricks / Fabric comparison · the common pitfalls and their fix · the cheat sheet · the architecture schemas · the code blocks · the facts worth quoting.

Open in the app →

Guides that answer with this page

These guides cite this page as one of the sources their answer rests on.