[{"data":1,"prerenderedAt":608},["ShallowReactive",2],{"blog-\u002Fblog\u002Fone-exposure-from-operations-fqm-flow":3,"blog-related-\u002Fblog\u002Fone-exposure-from-operations-fqm-flow":586,"blog-surround-\u002Fblog\u002Fone-exposure-from-operations-fqm-flow":607},{"id":4,"title":5,"audience":6,"body":10,"cluster":516,"conversionGoal":517,"cornerstone":518,"date":519,"description":520,"draft":521,"extension":522,"factCheckedAt":523,"faq":524,"featured":521,"language":534,"meta":535,"minRead":536,"navigation":518,"order":537,"originalAsset":534,"path":538,"pillar":539,"primaryKeyword":540,"publicationOrder":541,"relatedProject":534,"releaseScope":542,"reviewCycle":543,"reviewMethod":544,"reviewStatus":545,"reviewedAt":534,"reviewedBy":546,"searchIntent":547,"seo":548,"sources":549,"stem":579,"tags":580,"type":584,"updated":523,"__hash__":585},"blog\u002Fblog\u002Fone-exposure-from-operations-fqm-flow.md","One Exposure from Operations & FQM_FLOW Explained",[7,8,9],"sap-treasury-consultant","solution-architect","treasury-system-lead",{"type":11,"value":12,"toc":505},"minimark",[13,41,46,65,72,76,83,93,103,124,128,148,159,166,280,291,302,314,317,329,335,350,354,371,375,378,402,412,425,429,480,489,492],[14,15,16,36,37,40],"p",{},[17,18,19,20,24,25,30,31,35],"strong",{},"One Exposure from Operations is the hub at the centre of S\u002F4HANA Cash Management — a single store (the table ",[21,22,23],"code",{},"FQM_FLOW"," — ",[26,27,29],"a",{"href":28},"\u002Fblog\u002Fsap-treasury-tables","where it sits among the treasury tables",") where every cash-relevant flow lands, so the cash position, the liquidity forecast and the reporting all read from ",[32,33,34],"em",{},"one"," source."," If you understand nothing else about S\u002F4HANA Cash Management, understand this: SAP replaced the old world of cash management keeping its ",[32,38,39],{},"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.",[42,43,45],"h2",{"id":44},"what-it-actually-is","What it actually is",[14,47,48,49,53,54,57,58,61,62,64],{},"Every treasury architecture needs a ",[26,50,52],{"href":51},"\u002Fblog\u002Ftreasury-system-of-record","single source of truth"," for its numbers. One Exposure from Operations is SAP's answer to that need for ",[32,55,56],{},"cash",": instead of many systems each keeping their own view of cash-relevant activity, they all feed ",[17,59,60],{},"one hub",", and everything downstream reads from it. ",[21,63,23],{}," is where that hub lives — the table that holds the flows.",[14,66,67,68,71],{},"That's the concept in a sentence. The reason it's worth an article is that the ",[32,69,70],{},"implications"," are large, and the documentation states the concept without walking you through them.",[42,73,75],{"id":74},"why-it-exists","Why it exists",[14,77,78,79,82],{},"Classic Cash Management maintained its own summary records, updated as documents posted. It worked, but it meant cash management held a ",[32,80,81],{},"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.",[14,84,85,86,88,89,92],{},"One Exposure narrows that class of problem sharply. Instead of cash management holding its own parallel summary, there's ",[32,87,34],{}," store of flows — fed from the operational sources — that the position and forecast read directly. It's the ",[26,90,91],{"href":51},"system-of-record discipline"," applied inside SAP: one collection point everything downstream trusts, rather than competing summaries maintained in parallel.",[14,94,95,96,99,100,102],{},"What it does ",[32,97,98],{},"not"," do is make reconciliation disappear. ",[21,101,23],{}," is still derived operational data: it's populated from the source applications, and SAP ships initialization, deletion and rebuild tools precisely because those flows can need regenerating or reconciling when configuration or postings change. The win isn't \"nothing to reconcile ever\" — it's \"one place to reconcile, not many disagreeing copies.\"",[104,105,107],"callout",{"type":106},"tip",[14,108,109,110,112,113,115,116,119,120,123],{},"The mental shift from classic: stop thinking \"cash management has its ",[32,111,39],{}," numbers that I reconcile to the documents.\" Start thinking \"there is ",[32,114,34],{}," store of flows, and the position and forecast are just ",[32,117,118],{},"views"," of it.\" Once you hold that model, most One Exposure questions answer themselves — including ",[32,121,122],{},"where"," to look when a flow is missing or wrong.",[42,125,127],{"id":126},"what-feeds-it","What feeds it",[14,129,130,131,137,138,142,143,147],{},"The value of the hub is only as good as what lands in it — so the first question on any implementation is ",[32,132,133,134,136],{},"what flows into ",[21,135,23],{},", from where, and by which route?"," The sources are the operational systems that generate cash-relevant activity: financial documents, purchasing and sales activity, treasury deals from ",[26,139,141],{"href":140},"\u002Fblog\u002Fwhat-is-sap-treasury-and-risk-management","TRM",", loans, manual\u002Fmemo records, and ",[26,144,146],{"href":145},"\u002Fblog\u002Felectronic-bank-statement-processing-in-sap","bank statement items",", among others. Each relevant flow is collected into the store so the whole cash picture is built from one consolidated set.",[14,149,150,151,154,155,158],{},"The important nuance is that they don't all arrive the same way. FI and MM documents are turned into flows by ",[17,152,153],{},"Flow Builder","; the other applications each activate as their own ",[32,156,157],{},"source application"," with its own integration. So \"what feeds One Exposure\" is really several integrations, not one — and that matters the moment a number looks wrong.",[14,160,161,162,165],{},"The route matrix below is a map of the main ones — for a flow that's missing or wrong, it tells you ",[32,163,164],{},"which"," integration to check first. SAP's own list of source applications is longer than this; treat the table as the routes you meet most, not a complete inventory:",[167,168,169,188],"table",{},[170,171,172],"thead",{},[173,174,175,179,185],"tr",{},[176,177,178],"th",{},"Source",[176,180,181,182,184],{},"Reaches ",[21,183,23],{}," via",[176,186,187],{},"Check first when a flow is missing\u002Fwrong",[189,190,191,204,215,228,241,254,267],"tbody",{},[173,192,193,199,201],{},[194,195,196],"td",{},[17,197,198],{},"FI documents",[194,200,153],{},[194,202,203],{},"Flow Builder; document cash relevance",[173,205,206,211,213],{},[194,207,208],{},[17,209,210],{},"MM (purchasing) documents",[194,212,153],{},[194,214,203],{},[173,216,217,222,225],{},[194,218,219],{},[17,220,221],{},"SD (sales) activity",[194,223,224],{},"Its own source application",[194,226,227],{},"The SD → cash integration",[173,229,230,235,238],{},[194,231,232],{},[17,233,234],{},"Treasury deals (TRM)",[194,236,237],{},"TRM's own integration (forecast)",[194,239,240],{},"The TRM → One Exposure integration",[173,242,243,248,251],{},[194,244,245],{},[17,246,247],{},"Loans",[194,249,250],{},"Loans' own integration (forecast)",[194,252,253],{},"The loans integration",[173,255,256,261,264],{},[194,257,258],{},[17,259,260],{},"Bank statement items",[194,262,263],{},"End-of-day statements: own source app",[194,265,266],{},"Statement processing \u002F posting",[173,268,269,274,277],{},[194,270,271],{},[17,272,273],{},"Manual \u002F memo records",[194,275,276],{},"Memo-record entry",[194,278,279],{},"The memo record itself",[14,281,282,283,286,287,290],{},"The pattern the matrix encodes: ",[17,284,285],{},"Flow Builder owns the FI\u002FMM route; the other applications each bring their own."," But don't turn that into \"Flow Builder is never involved elsewhere\", because the forecast and the actual take different paths. TRM and loans feed One Exposure with the ",[32,288,289],{},"expected"," flows from the deal or contract; when that deal settles and posts, the resulting FI document is Flow Builder's territory — SAP documents the financial-accounting Flow Builder analysing the document flow back to the source (original) document. Bank statements are the same shape: end-of-day statements are their own source application, but a statement that posts produces FI flows built by Flow Builder, and which branch you get depends on posting category and transfer mode. Intraday statements don't have a route of their own at all — they arrive as memo records.",[14,292,293,294,297,298,301],{},"So the question to ask first is whether you're chasing a ",[17,295,296],{},"forecast"," flow or a ",[17,299,300],{},"posted"," one. Forecast points you at the source application; posted points you at FI, and therefore at Flow Builder. Verify the exact routes for your release against SAP's documentation, since integration details differ by release and edition.",[14,303,304,305,308,309,313],{},"The practical consequence: if a source isn't feeding One Exposure correctly, the flow simply isn't in the position — and it fails ",[32,306,307],{},"silently",", exactly like the ",[26,310,312],{"href":311},"\u002Fblog\u002Finterface-monitoring-and-reconciliation","interface failures"," that plague any treasury landscape. Knowing what feeds the store, and by which route, is knowing what your numbers are made of.",[42,315,153],{"id":316},"flow-builder",[14,318,319,321,322,325,326,328],{},[17,320,153],{}," (and Flow Builder Plus) is the mechanism that generates flows from ",[17,323,324],{},"FI and MM"," documents and writes them into One Exposure. It's the bridge between the accounting\u002Flogistics world and the cash store — but it's ",[32,327,98],{}," the single pipe for everything. Treasury deals, loans and sales activity each activate as their own source application and feed their expected flows in directly, without Flow Builder.",[14,330,331,332,334],{},"Where that framing gets people into trouble is the word \"instead\". Those integrations carry the ",[32,333,296],{},". The moment the underlying deal, loan or statement actually posts, you have an FI document, and FI documents are Flow Builder's job — SAP's financial-accounting Flow Builder traces the document chain back to the source (original) document, so the flow keeps the account assignment it really came from. So a TRM-originated number can legitimately be a Flow Builder question; it depends on whether you're looking at what's expected or what's posted.",[14,336,337,338,340,341,344,345,349],{},"That distinction is practical, not pedantic. When people ask \"why is this flow in the position?\" or \"why isn't it?\", the first move is to identify ",[32,339,164],{}," source the flow should come from and ",[32,342,343],{},"which stage"," it's at — the source application's integration for an expected flow, Flow Builder for anything that has already hit FI. Reaching straight for Flow Builder every time is how you waste an afternoon; assuming it's never involved outside FI\u002FMM is how you waste the afternoon after that. The full method — why a flow is invisible, which source to check, when to rebuild — is in the ",[26,346,348],{"href":347},"\u002Fblog\u002Ffqm-flow-reconciliation-and-troubleshooting","FQM_FLOW reconciliation & troubleshooting guide",".",[42,351,353],{"id":352},"actuals-and-forecast-in-one-place","Actuals and forecast in one place",[14,355,356,357,360,361,365,366,370],{},"Because the hub holds cash-relevant flows with their timing, One Exposure naturally supports both the ",[32,358,359],{},"actual"," ",[26,362,364],{"href":363},"\u002Fblog\u002Fhow-to-build-a-daily-cash-position","cash position"," and the forward-looking ",[26,367,369],{"href":368},"\u002Fblog\u002F13-week-cash-flow-forecast","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\u002F4HANA 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.",[42,372,374],{"id":373},"the-model-that-makes-it-click","The model that makes it click",[14,376,377],{},"Hold these three sentences and most of S\u002F4HANA Cash Management falls into place:",[379,380,381,390,396],"ol",{},[382,383,384,387,388,349],"li",{},[17,385,386],{},"There is one store of cash-relevant flows"," — One Exposure, in ",[21,389,23],{},[382,391,392,395],{},[17,393,394],{},"Several integrations fill it"," — Flow Builder for FI\u002FMM and for anything that has posted to FI, and each other application (TRM, loans, SD, bank statements, memo records) feeding its expected flows through its own route.",[382,397,398,401],{},[17,399,400],{},"The position and forecast are views of it",", not separate copies you maintain — though the store itself is still derived and can be rebuilt.",[403,404],"diagram",{":hub":405,":outputs":406,":sources":407,"caption":408,"desc":409,"outputs-via":410,"title":411},"{\"label\":\"One Exposure from Operations\",\"sub\":\"table FQM_FLOW\"}","[{\"label\":\"Cash position\"},{\"label\":\"Liquidity forecast\"},{\"label\":\"Reporting\"}]","[{\"label\":\"FI documents\",\"via\":\"Flow Builder\"},{\"label\":\"MM (purchasing) documents\",\"via\":\"Flow Builder\"},{\"label\":\"SD (sales) activity\",\"via\":\"Its own integration\"},{\"label\":\"Treasury deals (TRM)\",\"via\":\"TRM's own integration\"},{\"label\":\"Loans\",\"via\":\"Loans' own integration\"},{\"label\":\"Bank statement items\",\"via\":\"End-of-day: own source app\"},{\"label\":\"Manual \u002F memo records\",\"via\":\"Memo-record entry\"}]","Flow Builder owns the FI\u002FMM route; the other applications bring their own. Verify the exact routes for your release against SAP's documentation, since integration details differ by release and edition.","Seven sources feed the FQM_FLOW store. Flow Builder carries FI and MM documents; SD, TRM, loans, bank statements and memo records each reach the store through their own integration. Those routes carry each application's own flows — forecast for TRM, loans and SD, actuals for end-of-day statements — and once a deal or statement posts, the resulting FI document is Flow Builder's. The cash position, liquidity forecast and reporting are views of that one store.","views of the store","How sources reach One Exposure from Operations",[14,413,414,415,419,420,424],{},"Everything else — ",[26,416,418],{"href":417},"\u002Fblog\u002Fliquidity-items-in-sap-cash-management","liquidity items",", ",[26,421,423],{"href":422},"\u002Fblog\u002Fplanning-levels-and-groups-in-sap","planning levels",", the reporting — hangs off that spine.",[42,426,428],{"id":427},"where-one-exposure-bites","Where One Exposure bites",[430,431,432,438,447,453,459,471],"ul",{},[382,433,434,437],{},[17,435,436],{},"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.",[382,439,440,443,444,446],{},[17,441,442],{},"Not knowing the sources."," No clear picture of what flows into ",[21,445,23],{},", so no one can explain — or fix — a number that looks off.",[382,448,449,452],{},[17,450,451],{},"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.",[382,454,455,458],{},[17,456,457],{},"Under-scoping the integrations."," Assuming Flow Builder brings in everything, so the TRM, loan or bank-statement flows that feed One Exposure through their own routes get missed — and go-live reveals flows that never arrive.",[382,460,461,464,465,467,468,470],{},[17,462,463],{},"Ruling Flow Builder out too early."," The mirror-image mistake: assuming Flow Builder is never involved outside FI\u002FMM, so a ",[32,466,300],{}," TRM, loan or statement flow — which reaches ",[21,469,23],{}," as an FI document, built by Flow Builder — gets chased in the wrong integration.",[382,472,473,476,477,479],{},[17,474,475],{},"Assuming it never needs reconciling."," Treating ",[21,478,23],{}," as if it can't drift because it's \"the single store\" — when it's derived data with initialization, deletion and rebuild tools for exactly the cases where it does.",[14,481,482,483,485,486,488],{},"Understand One Exposure as the single store, know ",[32,484,164],{}," integration feeds each flow into ",[21,487,23],{},", and treat the position and forecast as views of it — and S\u002F4HANA 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.",[490,491],"hr",{},[14,493,494],{},[32,495,496,497,501,502,349],{},"See also ",[26,498,500],{"href":499},"\u002Fblog\u002Fsap-cash-management-s4hana","SAP Cash Management in S\u002F4HANA"," and ",[26,503,504],{"href":51},"the treasury system of record",{"title":506,"searchDepth":507,"depth":507,"links":508},"",2,[509,510,511,512,513,514,515],{"id":44,"depth":507,"text":45},{"id":74,"depth":507,"text":75},{"id":126,"depth":507,"text":127},{"id":316,"depth":507,"text":153},{"id":352,"depth":507,"text":353},{"id":373,"depth":507,"text":374},{"id":427,"depth":507,"text":428},"cash-management","topic-hub",true,"2026-07-24","One Exposure from Operations is the hub at the centre of S\u002F4HANA Cash Management — a single store (FQM_FLOW) every cash-relevant flow feeds. Why it exists.",false,"md","2026-08-02",[525,528,531],{"question":526,"answer":527},"What is One Exposure from Operations in SAP?","One Exposure from Operations is the central hub in S\u002F4HANA Cash Management that consolidates all cash-relevant flows into a single store — the table FQM_FLOW. Instead of cash management maintaining its own separate summary records, every cash-relevant flow from across the system lands in this one place, and the cash position, liquidity forecast and reporting all read from it. It's SAP's implementation of a single source of truth for cash: one hub, many sources, one place everything downstream trusts.",{"question":529,"answer":530},"What is FQM_FLOW?","FQM_FLOW is the database table at the heart of One Exposure from Operations in S\u002F4HANA — it holds the cash-relevant flows that feed cash management. Relevant flows from across the system (financial documents, purchasing, sales, treasury deals, loans, memo records, bank statement items and more) are collected into it, so that the cash position and liquidity forecast are built from one consolidated store rather than from many separate summary records as in classic Cash Management. It is still derived operational data: SAP provides initialization, deletion and rebuild tools precisely because these flows can need regenerating or reconciling when source configuration or postings change.",{"question":532,"answer":533},"What is Flow Builder in SAP Cash Management?","Flow Builder (and Flow Builder Plus) is the mechanism that generates cash-relevant flows from FI and MM documents and writes them into One Exposure (FQM_FLOW). It is not the single pipe for everything: applications such as Treasury and Risk Management, loans and sales activate as their own source applications and feed their expected flows in directly, and memo records are entered by hand. The distinction that matters is forecast versus posted — those integrations carry the expected flow, but once the underlying deal or statement posts, the resulting FI document is Flow Builder's territory, and SAP's FI flow builder traces the document chain back to the originating source. Knowing which source a flow comes from, and whether you are looking at the expected or the posted version, is what lets you explain or fix a number that looks wrong.",null,{},10,3,"\u002Fblog\u002Fone-exposure-from-operations-fqm-flow","sap-treasury","one exposure from operations FQM_FLOW",80,"SAP S\u002F4HANA — verify against your release\u002Fedition; One Exposure behaviour and the initialization\u002Frebuild tools differ across releases and between on-premise and Cloud.","annual","editorial-and-factual","reviewed","Tan Gravam","informational",{"title":5,"description":520},[550,554,557,561,564,567,570,573,576],{"title":551,"url":552,"accessed":553},"SAP Help — One Exposure from Operations (SAP S\u002F4HANA)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fac319d8fa4ea4624b40a58d23e3c4627\u002Fabd32554225fea6fe10000000a423f68.html","2026-07-26",{"title":555,"url":556,"accessed":553},"SAP Help — Flow Builder (Cash and Liquidity Management)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_CLOUD\u002Fee9ee0ca4c3942068ea584d2f929b5b1\u002F835cc0f9ff554154bf06245b70c4c79b.html",{"title":558,"url":559,"accessed":560},"SAP Help — Integration with Source Applications in the Central System","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fac319d8fa4ea4624b40a58d23e3c4627\u002F83996156f5b61d58e10000000a4450e5.html","2026-08-01",{"title":562,"url":563,"accessed":560},"SAP Help — Build Cash Flows from Operations","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fac319d8fa4ea4624b40a58d23e3c4627\u002F3848ad639f0c4fcaae89467ed9443fb8.html",{"title":565,"url":566,"accessed":560},"SAP Help — Treasury and Risk Management in One Exposure from Operations","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fac319d8fa4ea4624b40a58d23e3c4627\u002Feb383c57e236d820e10000000a44147b.html",{"title":568,"url":569,"accessed":560},"SAP Help — Cash Flows from End-of-Day Bank Statements","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fac319d8fa4ea4624b40a58d23e3c4627\u002F0d4605c7e1c644f4b3a4dce4f4571d0f.html",{"title":571,"url":572,"accessed":560},"SAP Help — Flow Builder Plus","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fac319d8fa4ea4624b40a58d23e3c4627\u002F269afd61815d455a911ff2d58f222e31.html",{"title":574,"url":575,"accessed":523},"SAP Help — End-of-Day Bank Statements in One Exposure from Operations","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fac319d8fa4ea4624b40a58d23e3c4627\u002F0bddfa562f4fff7de10000000a441470.html",{"title":577,"url":578,"accessed":523},"SAP Help — Intraday Memo Records (Cash and Liquidity Management)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fac319d8fa4ea4624b40a58d23e3c4627\u002F06f8351bfac0478d95d94440060c2f45.html","blog\u002Fone-exposure-from-operations-fqm-flow",[581,582,516,583],"sap","treasury","s4hana","text","KaW0T4XSbp21VOI82ANralYh2QT1AXfFu8LaToeByu0",{"related":587,"prev":597,"next":600,"hasOrder":518,"place":603},[588,591,594],{"path":417,"title":589,"description":590},"Liquidity Items in SAP Cash Management","Liquidity items classify cash flows by purpose — receipts, payments, payroll, tax — so the forecast reads by category. Why derivation makes or breaks it.",{"path":422,"title":592,"description":593},"Planning Levels and Groups in SAP Cash Management","Planning levels and groups classify items for SAP cash management by certainty — levels on accounts, groups on business partners. The enduring concept, plainly.",{"path":145,"title":595,"description":596},"Electronic Bank Statement Processing in SAP","Electronic bank statement (EBS) processing in SAP imports, interprets and posts bank statements, clearing open items. The pain lives in the posting-rule config.",{"path":598,"title":599,"type":584,"language":534},"\u002Fblog\u002Fsap-bank-account-management-s4hana","SAP Bank Account Management (BAM) in S\u002F4HANA",{"path":347,"title":601,"type":602,"language":534},"FQM_FLOW Reconciliation & Troubleshooting in S\u002F4HANA","pattern",{"label":604,"position":537,"total":605,"hub":606},"Cash Management",8,"\u002Ftopics\u002Fsap-treasury",[],1787475404521]