Two-way. Actuals flow into SAC from S/4HANA via live connection — so plan-vs-actual variance is always current without manual data loads. Plan data can retract from SAC back into S/4HANA (typically into CO-PA or profit centre planning objects) so that actual-vs-plan reporting works inside SAP as well. Master data (cost centres, profit centres, GL accounts, company codes) is sourced from S/4HANA into the planning model to ensure dimensional consistency. For organisations running SAP BPC Embedded alongside S/4HANA, SAC planning can coexist during transition — planning in SAC, with retraction flowing through to where S/4HANA finance expects it. Getting this retraction right requires knowledge of the S/4HANA finance backend — which is exactly why having the same partner deliver both S/4HANA and SAC planning reduces integration risk.

A value driver tree is a visual model that decomposes a financial outcome into its component drivers — for example, Revenue = Volume × Price × Mix, or EBITDA = Revenue – COGS – Opex. In SAC, value driver trees are interactive: adjust any driver and the financial impact cascades through the tree in real time. This transforms planning from "type a number into a cell" into "change the assumption and see what happens." Practically, value driver trees enable scenario simulation: "what if raw material costs increase 8%?", "what if headcount grows by 15 FTEs in Q3?", "what if we delay the capex project by two quarters?" Each scenario produces a full financial impact that the CFO can compare side by side. We design value driver trees as part of every planning model — they are the planning capability that most clearly differentiates SAC from Excel.

A BPC to SAC migration is a re-implementation, not a technical migration — there is no automated conversion tool. The work involves: inventorying your BPC models, script logic, input schedules, process chains and planning functions; designing equivalent SAC planning models with data actions (replacing script logic), SAC stories (replacing input schedules), calendar workflow (replacing process chains) and version management. Historical plan data can be migrated if needed. Timeline depends on BPC complexity: a straightforward BPC Standard implementation with 2–3 models migrates in 3–4 months; a complex multi-model BPC Embedded landscape may take 6–9 months. The practical approach is to run BPC and SAC in parallel for one planning cycle, validate outputs match, then cut over. Our team knows BPC well enough to estimate accurately — which prevents the underestimation that causes most BPC migration projects to overrun.

Smart Predict does not replace human judgment — it replaces the starting point. Instead of forecast holders typing their best guess into a cell, Smart Predict trains a time-series model on historical actuals and produces a statistically grounded baseline forecast with confidence intervals. The forecast holder then reviews, adjusts where they have market knowledge the model does not have (a new product launch, a lost customer, a regulatory change) and submits their adjusted forecast. This approach consistently produces more accurate forecasts than either pure manual estimation or pure machine learning — because it combines statistical pattern recognition with human context. We configure Smart Predict to seed directly into SAC planning versions so the workflow is seamless: model generates baseline → planner adjusts → manager approves → forecast version is locked.

For a single planning process — say opex budgeting with 15–30 cost centre owners — a typical implementation takes 10–14 weeks from discovery workshop to first live planning cycle. This covers: model design (2–3 weeks), build and connection to S/4HANA (3–4 weeks), workflow configuration and UAT (2–3 weeks) and training and first-cycle go-live support (2–3 weeks). For a full financial planning suite — P&L, balance sheet, cash flow, workforce, capex — delivered as a phased programme, expect 6–12 months with each planning domain going live in sequence. We always recommend timing the first go-live to coincide with an actual planning cycle (typically the annual budget cycle or a mid-year forecast resubmission) so the implementation is immediately validated in production rather than in a sandbox.