Is your S/4HANA schema Live-Ready for a SAC finance model?
The hardest part of a live connection isn't the plumbing — it's whether your source fields map onto the dimensions and measures a template expects. Paste your field names below (ACDOCA / CDS names work directly) and get a compatibility verdict plus a proposed mapping against the Actual vs Budget vs Forecast — S/4HANA Live model. Field names only, never data — everything runs in your browser.
How to read the result
One S/4HANA specific: the Version dimension (Actual / Budget / Forecast) is modeled in SAC, not read from the source — live S/4 feeds only supply actuals, so the checker doesn't expect a version field in your schema. Budget and forecast live in the SAC model's Category dimension.
Compatible means every required field matched a known name. Compatible with adaptation means a match was inferred and should be confirmed (e.g. a field name that only partially matches). Partially compatible flags one missing required field; not compatible yet means core fields (like a company, fiscal period, account or amount) aren't present under a recognizable name — usually a naming or modeling gap, not a dead end.
This checks names, not semantics — it's a fast first pass, not an architecture review. If your schema lines up, the matching pack is Actual vs Budget vs Forecast — S/4HANA Live. Next: decide live vs import vs hybrid and read the connection setup and limits.