One Exposure from Operations & FQM_FLOW Explained

One Exposure from Operations is the hub at the centre of S/4HANA Cash Management — a single store (the table FQM_FLOW) where every cash-relevant flow lands, so the cash position, the liquidity forecast and the reporting all read from one source. If you understand nothing else about S/4HANA Cash Management, understand this: SAP replaced the old world of cash management keeping its own separate summary records with a single hub that everything feeds and everything reads. Get this one idea and the whole module stops feeling arbitrary. Miss it, and you'll spend the project fighting symptoms — a position that doesn't tie, a forecast missing flows — without seeing the cause.

What it actually is

Every treasury architecture needs a single source of truth for its numbers. One Exposure from Operations is SAP's answer to that need for cash: instead of many systems each keeping their own view of cash-relevant activity, they all feed one hub, and everything downstream reads from it. FQM_FLOW is where that hub lives — the table that holds the flows.

That's the concept in a sentence. The reason it's worth an article is that the implications are large, and the documentation states the concept without walking you through them.

Why it exists

Classic Cash Management maintained its own summary records, updated as documents posted. It worked, but it meant cash management held a derived, separate copy of reality — and separate copies drift, need reconciling, and quietly disagree with the source. Anyone who ran classic knows the feeling: the position looks wrong, and now you're reconciling cash management's records back to the documents that fed them.

One Exposure removes that whole class of problem by design. There's no separate summary to drift — there's one hub of flows, fed from the operational sources, that the position and forecast read directly. It's the system-of-record discipline applied inside SAP: one authoritative place, no competing copies.

What feeds it

The value of the hub is only as good as what lands in it — so the first question on any implementation is what flows into FQM_FLOW, from where? The sources are the operational systems that generate cash-relevant activity: financial documents, purchasing and sales activity, treasury deals from TRM, manual/memo records, and bank statement items, among others. Each relevant flow is represented in the hub so the whole cash picture is built from one consolidated set.

The practical consequence: if a source isn't feeding One Exposure correctly, the flow simply isn't in the position — and it fails silently, exactly like the interface failures that plague any treasury landscape. Knowing what feeds the hub is knowing what your numbers are made of.

Flow Builder

The mechanism that populates the hub is Flow Builder — it reads the relevant source data across the system and writes the corresponding flows into One Exposure. Think of it as the bridge between the operational world (documents, orders, deals) and the cash hub. When people ask "why is this flow in the position?" or "why isn't it?", the answer almost always lives in what Flow Builder is bringing in, and from where. It's the first place I look when a One Exposure number is questioned.

Actuals and forecast in one place

Because the hub holds cash-relevant flows with their timing, One Exposure naturally supports both the actual cash position and the forward-looking liquidity forecast — they're different views over the same underlying flows rather than two separate builds. That's a big part of why the S/4HANA design is cleaner than classic once you understand it: the position and the forecast stop being two things you maintain and become two lenses on one source.

The model that makes it click

Hold these three sentences and most of S/4HANA Cash Management falls into place:

1. There is one hub of cash-relevant flows — One Exposure, in FQM_FLOW.
2. Flow Builder fills it from the operational sources.
3. The position and forecast are views of it, not separate copies.

Everything else — liquidity items, planning levels, the reporting — hangs off that spine.

What usually goes wrong

• Treating it as a black box. Trusting the hub without understanding what feeds it, so a missing or wrong source is discovered late, as a wrong position.
• Not knowing the sources. No clear picture of what flows into FQM_FLOW, so no one can explain — or fix — a number that looks off.
• Carrying classic assumptions across. Expecting cash management to hold its own reconciled records, and being confused when the model is "views over one hub" instead.
• Ignoring Flow Builder in design. Under-scoping what has to feed the hub, so go-live reveals flows that never arrive.

Understand One Exposure as the single hub, know what Flow Builder feeds into FQM_FLOW, and treat the position and forecast as views of it — and S/4HANA Cash Management stops being a maze and becomes a clean, single-source design. It's the idea the whole module is built on, and the one the documentation most assumes you already have.

Part of the SAP Treasury & Cash Management guide. See also SAP Cash Management in S/4HANA and the treasury system of record. The newsletter sends one finance-systems pattern every two weeks.