SAC live connection limitations: what you give up before you commit

A live connection is often the right call — real-time, governed, no data copy. But it comes with real trade-offs, and knowing them upfront saves you from designing yourself into a corner. Here's what you give up when you go live, stated plainly.

1. Planning is limited

This is the big one. SAC live connections are analytics-first: for full planning — data entry, versions (Actual/Budget/Forecast), data actions, allocations — you generally need an import (acquired) model. If your use case involves budgeting or forecasting, live alone usually won't cover it. That single fact decides many architectures.

2. Blending across sources is restricted

Combining data from several systems in one model is a strength of import models. On live connections, blending is limited — you're mostly working within the boundaries of the connected source. If your story needs to merge S/4HANA data with, say, a spreadsheet or a second system, that's friction on live.

3. Some story features behave differently

Not every SAC story or smart feature works identically on live versus import. Certain functions are restricted or behave differently because the data isn't stored in SAC. Always validate the specific features your stories rely on against your source type — the gaps vary by connection (S/4HANA, BW/4HANA, HANA, Datasphere) and by release.

4. Performance is only as good as the source

With live, SAC doesn't hold the data — it queries the source on every interaction. So a slow query in S/4HANA is a slow widget in SAC, and tuning lives on the source side, not in SAC. This is the opposite of an import model, where performance is self-contained. Plan capacity and query design in the source accordingly.

5. Cross-site cookies and SSO add setup complexity

Because the browser talks to the source directly (or via a tunnel), you inherit browser security constraints: modern SameSite cookie policies, HTTPS/SSL requirements, and SSO configuration to avoid a login popup on every story. None of this is a blocker, but it's real setup work with Basis and security teams — budget for it.

So when is live still the right choice?

Despite the list, live wins clearly when you need real-time data, a single source of truth, and governance (data never leaving the source) — and your use case is reporting, not planning. The limitations only hurt if you try to make live do a job it isn't built for. The clean decision framework is in SAC live connection vs import model, and for the setup specifics see connecting SAC live to S/4HANA.

If the limitations push you toward import/planning, the template catalog has free planning structures and the regulatory accelerators cover the harder standalone models.

Sources: SAP Help Portal — SAP Analytics Cloud live data connections and their restrictions; SAC Planning documentation. Feature availability changes each release and by source system — confirm against your version.