[{"data":1,"prerenderedAt":682},["ShallowReactive",2],{"blog-\u002Fblog\u002Fsap-treasury-fiori-apps":3,"blog-related-\u002Fblog\u002Fsap-treasury-fiori-apps":659,"blog-surround-\u002Fblog\u002Fsap-treasury-fiori-apps":681},{"id":4,"title":5,"audience":6,"body":10,"cluster":552,"conversionGoal":553,"cornerstone":554,"date":555,"description":556,"draft":554,"extension":557,"factCheckedAt":555,"faq":558,"featured":554,"language":553,"meta":571,"minRead":572,"navigation":573,"order":574,"originalAsset":553,"path":575,"pillar":576,"primaryKeyword":577,"publicationOrder":578,"relatedProject":553,"releaseScope":579,"reviewCycle":580,"reviewMethod":581,"reviewStatus":582,"reviewedAt":555,"reviewedBy":583,"searchIntent":584,"seo":585,"sources":586,"stem":650,"tags":651,"type":657,"updated":553,"__hash__":658},"blog\u002Fblog\u002Fsap-treasury-fiori-apps.md","SAP Treasury Fiori Apps: What Replaces Which Transaction",[7,8,9],"sap-treasury-consultant","treasury-system-lead","solution-architect",{"type":11,"value":12,"toc":540},"minimark",[13,27,34,39,51,63,67,70,137,145,149,173,177,185,264,280,295,299,302,361,373,377,456,469,473,480,488,492,514,525,528],[14,15,16,26],"p",{},[17,18,19,20,25],"strong",{},"The last reference I published mapped the ",[21,22,24],"a",{"href":23},"\u002Fblog\u002Fsap-treasury-transaction-codes","SAP Treasury transaction codes"," that matter; this one maps the Fiori apps that sit on top of them — and, more usefully, which classic transaction each app replaces, shadows or quietly outgrows."," The verification rule is the same as before, because the problem is the same: search for \"SAP treasury Fiori apps\" and you get scraped catalogs with invented app IDs. Every app on this page is checked against the SAP Fiori apps reference library and SAP Help; where I could verify an F-code app ID I print it, where I couldn't the app appears without one, and anything I couldn't verify at all is named in the exclusions section rather than silently included.",[14,28,29,30,33],{},"One structural thing to understand first, because it explains most of the confusion in this topic: ",[17,31,32],{},"app IDs come in three flavors."," Native Fiori apps carry F-numbers (F6157, F2332) unrelated to any transaction. Classic transactions wrapped for the launchpad keep their transaction code as the app ID — TBB1 is both a tcode and, in the app library, an app. And a few classic reports are listed under their tcode with a \"- Classic\" suffix, SAP's own label for \"still here, not the future\". Once you can read the three flavors, the catalog stops looking random.",[35,36,38],"h2",{"id":37},"the-deal-desk-manage-financial-transactions-f6157","The deal desk: Manage Financial Transactions (F6157)",[14,40,41,42,45,46,50],{},"The Transaction Manager's front-office and back-office codes — FTR_CREATE, FTR_EDIT, FTR_00 — get one Fiori counterpart that matters: ",[17,43,44],{},"Manage Financial Transactions (F6157)",". SAP describes it as the place to manage financial transactions across all instrument groups in one list, with navigation into the display and processing apps per deal. In practice it competes with FTR_00 for the back-office worklist role, and SAP publishes a feature comparison between the two precisely because the supported product categories differ — the comparison is linked from the same documentation set as the ",[21,47,49],{"href":48},"\u002Fblog\u002Fsap-transaction-manager","Transaction Manager"," apps catalog, and it's the document to read before a back office standardizes.",[14,52,53,54,58,59,62],{},"What F6157 is not: a replacement for deal entry. Creating and editing still runs through the classic transactions on-premise, wrapped GUI apps in the cloud. The honest summary is that F6157 replaces the ",[55,56,57],"em",{},"overview"," habit, not the ",[55,60,61],{},"capture"," habit.",[35,64,66],{"id":65},"reading-what-happened-the-f1754f1755f1867-trio","Reading what happened: the F1754\u002FF1755\u002FF1867 trio",[14,68,69],{},"This is the cleanest classic-to-Fiori mapping in the whole module, and the one I'd actually retrain a team on:",[71,72,73,89],"table",{},[74,75,76],"thead",{},[77,78,79,83,86],"tr",{},[80,81,82],"th",{},"Fiori app (ID)",[80,84,85],{},"Classic transaction",[80,87,88],{},"What it does",[90,91,92,104,115,126],"tbody",{},[77,93,94,98,101],{},[95,96,97],"td",{},"Display Treasury Position Values (F1867)",[95,99,100],{},"TPM12 (Treasury Position Values - Classic)",[95,102,103],{},"Positions in the treasury subledger with component values on any key date",[77,105,106,109,112],{},[95,107,108],{},"Display Treasury Position Flows (F1754)",[95,110,111],{},"TPM13 (Treasury Position Flows - Classic)",[95,113,114],{},"Position flows behind those values, operative and derived",[77,116,117,120,123],{},[95,118,119],{},"Display Treasury Posting Journal (F1755)",[95,121,122],{},"TPM20 (Treasury Posting Journal - Classic)",[95,124,125],{},"Accounting information for every posted flow",[77,127,128,131,134],{},[95,129,130],{},"Treasury Position History (F3966)",[95,132,133],{},"— (no classic equivalent)",[95,135,136],{},"How accounting key figures moved over a period, by entity\u002Fcurrency\u002Fasset",[14,138,139,140,144],{},"The \"why did it post that?\" walk I described in the transaction-codes reference — journal, flows, position — works identically here: F1755, then F1754, then F1867. The difference is availability: the F-apps are listed for both on-premise and Cloud Public Edition, while the \"- Classic\" tcode apps are the ones with an expiry date in their name. F3966 is the genuinely new member — a period-over-period reconciliation view that classic TPM12 never gave you, and the kind of thing the ",[21,141,143],{"href":142},"\u002Fblog\u002Fsap-treasury-tables","treasury tables"," used to be the only way to build.",[35,146,148],{"id":147},"hedge-management-where-fiori-is-the-only-way-even-on-premise","Hedge management: where Fiori is the only way even on-premise",[14,150,151,152,156,157,160,161,164,165,168,169,172],{},"The newer Hedge Management and Accounting of Net Open Exposures has no classic-transaction heritage to map to — it was built launchpad-first, which is why the ",[21,153,155],{"href":154},"\u002Fblog\u002Fhedge-management-in-sap","hedge management article"," treats it as a different discipline from THMEX-era hedge accounting. Two apps carry the daily work: the ",[17,158,159],{},"Hedge Management Cockpit"," (app ID TOENE — a wrapped ABAP app, no F-number exists) for the overview of FX exposures and hedge requests, and ",[17,162,163],{},"Process Hedge Requests"," (TOEHREQO) for working them. The balance-sheet FX variant has its own pair, including ",[17,166,167],{},"Process Hedge Requests - Balance Sheet FX Risk (F4764)",". If your team still asks \"what's the tcode for the cockpit,\" the answer is that TOENE ",[55,170,171],{},"is"," the identifier, and it only exists as a launchpad app — this corner of TRM is Fiori-only everywhere, not just in the cloud.",[35,174,176],{"id":175},"cash-position-and-forecasting","Cash position and forecasting",[14,178,179,180,184],{},"Cash management is where the Fiori story has the most layers, because SAP rebuilt this area around ",[21,181,183],{"href":182},"\u002Fblog\u002Fone-exposure-from-operations-fqm-flow","One Exposure"," and then iterated the apps on top of it:",[71,186,187,198],{},[74,188,189],{},[77,190,191,193,196],{},[80,192,82],{},[80,194,195],{},"Classic counterpart",[80,197,88],{},[90,199,200,211,222,233,243,253],{},[77,201,202,205,208],{},[95,203,204],{},"Cash Flow Analyzer (F2332)",[95,206,207],{},"FF7AN\u002FFF7BN territory",[95,209,210],{},"The working analysis surface: cash position and liquidity trend in one",[77,212,213,216,219],{},[95,214,215],{},"Cash Position (F1737)",[95,217,218],{},"FF7A → FF7AN",[95,220,221],{},"Forecasted cash position by country, company, bank, currency",[77,223,224,227,230],{},[95,225,226],{},"Liquidity Forecast (F0512A)",[95,228,229],{},"FF7B → FF7BN",[95,231,232],{},"90-day liquidity trend from memo records and One Exposure",[77,234,235,238,240],{},[95,236,237],{},"Short-Term Cash Positioning (F5380)",[95,239,133],{},[95,241,242],{},"Position from direct bank balances, driven by cash position profiles",[77,244,245,248,250],{},[95,246,247],{},"Check Cash Flow Items (F0735)",[95,249,133],{},[95,251,252],{},"The data audit: track problematic and missing flows behind the position",[77,254,255,258,261],{},[95,256,257],{},"Manage Memo Records (F2986\u002FF2986A)",[95,259,260],{},"FF63\u002FFF65 — SAP-documented replacement",[95,262,263],{},"Manual cash advices; 2.0 adds spreadsheet import",[14,265,266,267,270,271,274,275,279],{},"Two notes worth the table space. First, the memo records line is the one SAP states outright: the 1809 release notes say Manage Memo Records ",[17,268,269],{},"replaces"," the FF63\u002FFF65 apps — the strongest replacement language anywhere in this module, which is why I keep citing it. Second, the practical center of gravity has drifted to ",[17,272,273],{},"Cash Flow Analyzer",": SAP's current release notes keep enhancing F2332 as the integration point for the newer cash functions, and the library lists the Smart Business pair (F1737\u002FF0512A) for on-premise releases while the analyzer runs everywhere. If you're building a cash manager's launchpad today, F2332 is the tile they'll live in — the ",[21,276,278],{"href":277},"\u002Fblog\u002Fsap-cash-management-s4hana","S\u002F4HANA Cash Management overview"," covers the data model underneath it.",[14,281,282,283,286,287,290,291,294],{},"Rounding out daily cash operations: ",[17,284,285],{},"Make Bank Transfers (F0691)"," with its template sibling (F3760), ",[17,288,289],{},"Manage Cash Concentration (F3265)"," taking over from classic FF73, and ",[17,292,293],{},"Process Trade Requests (TPITRO)"," for working cash trade requests — the mechanism that turns a funding or investment decision into an instrument, extended in S\u002F4HANA 2020 to cover money-market fixed-term deposits and loans.",[35,296,298],{"id":297},"banks-and-bank-accounts-the-master-data-cluster","Banks and bank accounts: the master-data cluster",[14,300,301],{},"This cluster answers the \"manage banks fiori\" search, and it needs one deprecation warning up front:",[71,303,304,315],{},[74,305,306],{},[77,307,308,310,313],{},[80,309,82],{},[80,311,312],{},"Status \u002F classic counterpart",[80,314,88],{},[90,316,317,328,339,350],{},[77,318,319,322,325],{},[95,320,321],{},"Manage Banks - Cash Management (F1574A)",[95,323,324],{},"Successor of Manage Banks (F1574), now deprecated",[95,326,327],{},"Bank master data relevant to cash management, ratings, contacts",[77,329,330,333,336],{},[95,331,332],{},"Manage Banks - Master Data (F6437)",[95,334,335],{},"Bank directory maintenance",[95,337,338],{},"Create and display banks as master data",[77,340,341,344,347],{},[95,342,343],{},"Manage Bank Accounts (F1366A)",[95,345,346],{},"The BAM working surface",[95,348,349],{},"Create, edit, close, reopen bank accounts; lifecycle and signers",[77,351,352,355,358],{},[95,353,354],{},"Manage Bank Accounts - Hierarchy (F1366)",[95,356,357],{},"—",[95,359,360],{},"The same inventory viewed as a bank hierarchy",[14,362,363,364,367,368,372],{},"The pattern to internalize: ",[17,365,366],{},"F1574 (Manage Banks) is the answer you'll find on older lists, and it's the wrong one now"," — SAP's own documentation files it under \"Manage Banks (Deprecated)\" and recommends the split successors F1574A and F6437. Manage Bank Accounts (F1366A) is the front door of ",[21,369,371],{"href":370},"\u002Fblog\u002Fsap-bank-account-management-s4hana","Bank Account Management",", where bank accounts became governed master data instead of configuration — the shift that article walks through in detail. There is no classic transaction that maps cleanly onto F1366A, which is exactly the point: this is the part of S\u002F4HANA cash management where Fiori isn't an alternative UI, it's where the process lives.",[35,374,376],{"id":375},"bank-statements-and-payments","Bank statements and payments",[71,378,379,389],{},[74,380,381],{},[77,382,383,385,387],{},[80,384,82],{},[80,386,195],{},[80,388,88],{},[90,390,391,402,413,424,434,445],{},[77,392,393,396,399],{},[95,394,395],{},"Manage Bank Statements (F1564)",[95,397,398],{},"FF67 (manual statement)",[95,400,401],{},"Manage manual and electronic statements; spreadsheet upload",[77,403,404,407,410],{},[95,405,406],{},"Manage Incoming Payment Files (F1680)",[95,408,409],{},"FF.5 (import)",[95,411,412],{},"Bring statement files into the system",[77,414,415,418,421],{},[95,416,417],{},"Reprocess Bank Statement Items (F1520)",[95,419,420],{},"FEBA_BANK_STATEMENT",[95,422,423],{},"Post-process items that didn't clear automatically",[77,425,426,429,431],{},[95,427,428],{},"Bank Statement Monitor (F6388)",[95,430,133],{},[95,432,433],{},"Central view of statement arrival and errors, with history",[77,435,436,439,442],{},[95,437,438],{},"Approve Bank Payments (F0673A)",[95,440,441],{},"BNK_APP",[95,443,444],{},"Review, approve, reject, defer payment batches; mass approval",[77,446,447,450,453],{},[95,448,449],{},"Monitor Payments (F2388)",[95,451,452],{},"BNK_MONI's job",[95,454,455],{},"Track payment batches after release",[14,457,458,459,463,464,468],{},"The ",[21,460,462],{"href":461},"\u002Fblog\u002Felectronic-bank-statement-processing-in-sap","bank statement pipeline"," keeps its shape — import, post, repair — with F1680, F1564 and F1520 as the Fiori stations. F6388 is the addition worth adopting even in a GUI-habit shop, because \"which accounts haven't sent a statement today\" was always an awkward question for the classic transactions to answer. On the payments side, F0673A is the Fiori counterpart of the BNK_APP habit — documented in SAP's Cash and Liquidity Management pages, including mass approval of batches as a background job, the feature I flagged in the transaction-codes post as changing the approval conversation at volume. How the batches get there in the first place is ",[21,465,467],{"href":466},"\u002Fblog\u002Fbank-communication-management-bcm-sap","Bank Communication Management","'s story.",[35,470,472],{"id":471},"cloud-public-edition-fiori-only-with-a-precise-footnote","Cloud Public Edition: Fiori-only, with a precise footnote",[14,474,475,476,479],{},"In the transaction-codes reference I gave the planning rule: SAP S\u002F4HANA Cloud Public Edition is Fiori-only, and classic codes don't apply there. That's still the right planning assumption — but this page is where the precise version belongs. There is no SAP GUI client in Cloud Public Edition; everything is a launchpad app. What SAP ships there, alongside the native F-apps, is a set of classic treasury functions ",[17,477,478],{},"wrapped as launchpad apps whose app ID is the old transaction code",": the Cloud documentation lists Fix, Pay, and Post Flows with app ID TBB1, and the best-practice scripts open Fix, Pay and Post Flows (TBB1), Process Business Transactions (TPM10), Post Derived Business Transactions (TPM18) and Treasury Posting Journal - Classic (TPM20) straight from the launchpad. Cloud even gets scheduling apps the on-premise catalog doesn't list: Schedule Treasury Accountant Jobs (F2770), Schedule Treasury Back Office Jobs (F2771) and Schedule Treasury Middle Office Jobs (F2772), for running exactly these period-end steps as jobs.",[14,481,482,483,487],{},"So the muscle memory transfers better than the \"Fiori-only\" slogan suggests — but the wrapper is a compatibility measure, not a direction. Which deployment model puts you on which side of this line is the subject of the ",[21,484,486],{"href":485},"\u002Fblog\u002Fsap-treasury-deployment-and-edition-comparison","deployment and edition comparison",".",[35,489,491],{"id":490},"what-i-left-out-on-purpose","What I left out, on purpose",[493,494,495,502,508],"ul",{},[496,497,498,501],"li",{},[17,499,500],{},"F0733."," It's in the target list of half the scraped catalogs, usually attached to a bank app. The Fiori apps reference library has no app with that ID — the numbering goes F0731, F0732, then F0735 — and SAP Help doesn't document one. Excluded, and worth calling out precisely because it spreads.",[496,503,504,507],{},[17,505,506],{},"Retired apps that still circulate",": Manage Banks (F1574), Cash Position Details (F0737), Track Bank Transfers (F0692) and Bank Statement Monitor - End of Day (F1734) are all real, all in the library for older releases, and all absent from the current ones. They're history, not recommendations, so they don't get table rows.",[496,509,510,513],{},[17,511,512],{},"Apps I couldn't pin an ID to."," Where SAP documents an app name but I couldn't verify its app ID in the library or on SAP Help, the app appears above without an ID (the Hedge Management Cockpit's TOENE being the honest edge case — verified, but not an F-number). No app ID on this page is inferred.",[14,515,516,517,520,521,487],{},"Same closing caveat as the ",[21,518,519],{"href":23},"transaction-codes reference",", which remains the classic-side half of this pair: catalogs drift by release and edition, and this page states its verification scope in the frontmatter rather than pretending to be timeless. For what SAP Treasury actually is underneath both UIs, start with the ",[21,522,524],{"href":523},"\u002Fblog\u002Fwhat-is-sap-treasury-and-risk-management","module guide",[526,527],"hr",{},[14,529,530],{},[55,531,532,533,536,537,487],{},"See also ",[21,534,535],{"href":48},"SAP Transaction Manager"," and ",[21,538,539],{"href":277},"SAP Cash Management in S\u002F4HANA",{"title":541,"searchDepth":542,"depth":542,"links":543},"",2,[544,545,546,547,548,549,550,551],{"id":37,"depth":542,"text":38},{"id":65,"depth":542,"text":66},{"id":147,"depth":542,"text":148},{"id":175,"depth":542,"text":176},{"id":297,"depth":542,"text":298},{"id":375,"depth":542,"text":376},{"id":471,"depth":542,"text":472},{"id":490,"depth":542,"text":491},"transactions",null,false,"2026-08-02","A verified map of the Fiori apps for SAP Treasury and Cash Management in S\u002F4HANA — F6157 to F2332 — with the classic transaction each replaces or complements.","md",[559,562,565,568],{"question":560,"answer":561},"What is Fiori app F0733 in SAP Cash Management?","As far as SAP's own records go, nothing. F0733 appears on circulating app lists, but the SAP Fiori apps reference library has no app under that ID — its numbering runs F0731, F0732, then jumps to F0735 (Check Cash Flow Items) — and SAP Help doesn't document an F0733 either. The bank apps people are usually reaching for are Manage Banks - Cash Management (F1574A), Manage Banks - Master Data (F6437) and Manage Bank Accounts (F1366A). If a list you're holding says F0733, treat the rest of that list with suspicion too.",{"question":563,"answer":564},"Which Fiori apps replace TPM12, TPM13 and TPM20 in S\u002F4HANA?","The Fiori-native reporting siblings are Display Treasury Position Values (F1867) for TPM12, Display Treasury Position Flows (F1754) for TPM13, and Display Treasury Posting Journal (F1755) for TPM20. The classic transactions still exist — SAP's app catalog lists them with a '- Classic' suffix — but the F-apps are the ones available across both on-premise and Cloud Public Edition, so they're the ones worth standardizing an investigation routine on.",{"question":566,"answer":567},"Can you use TBB1 or TPM10 in SAP S\u002F4HANA Cloud Public Edition?","Yes, with a caveat: not as SAP GUI transactions, because there is no SAP GUI client in Cloud Public Edition, but SAP ships them as launchpad apps whose app ID is the old transaction code. SAP's Cloud documentation lists Fix, Pay, and Post Flows with app ID TBB1, and its best-practice test scripts tell you to open Fix, Pay and Post Flows (TBB1) and Process Business Transactions (TPM10) from the Fiori launchpad. The function survives; the GUI habit doesn't.",{"question":569,"answer":570},"Do SAP Fiori apps use the same app ID as the transaction they replace?","Only sometimes, and the pattern is worth knowing. Native Fiori apps carry F-numbers (F6157, F2332, F1755) that have no relation to any transaction code. Classic transactions that SAP wraps for the launchpad keep the transaction code as their app ID — TBB1, TPM10, TOENE for the Hedge Management Cockpit — and some classic reports get listed under their tcode with a '- Classic' name, like Treasury Posting Journal - Classic (TPM20). So an app ID that looks like a tcode is a wrapped classic screen, and an F-number is a genuine Fiori rebuild.",{},9,true,8.25,"\u002Fblog\u002Fsap-treasury-fiori-apps","sap-treasury","sap treasury fiori apps",191,"Verified against the SAP Fiori apps reference library for SAP S\u002F4HANA 2025 \u002F 2025 FPS01 (on-premise) and SAP S\u002F4HANA Cloud Public Edition 2602\u002F2608, plus SAP Help pages for those releases. Availability notes are per those releases and will drift.","annual","editorial-and-factual","reviewed","Tan Gravam","informational",{"title":5,"description":556},[587,590,593,596,599,602,605,608,611,614,617,620,623,626,629,632,635,638,641,644,647],{"title":588,"url":589,"accessed":555},"SAP Fiori apps reference library","https:\u002F\u002Ffioriappslibrary.hana.ondemand.com\u002Fsap\u002Ffix\u002FexternalViewer\u002F",{"title":591,"url":592,"accessed":555},"SAP Fiori apps reference library — Manage Financial Transactions (F6157)","https:\u002F\u002Ffioriappslibrary.hana.ondemand.com\u002Fsap\u002Ffix\u002FexternalViewer\u002Findex.html#\u002Fdetail\u002FApps('F6157')\u002FS32OP",{"title":594,"url":595,"accessed":555},"SAP Fiori apps reference library — Display Treasury Posting Journal (F1755)","https:\u002F\u002Ffioriappslibrary.hana.ondemand.com\u002Fsap\u002Ffix\u002FexternalViewer\u002Findex.html#\u002Fdetail\u002FApps('F1755')\u002FS32OP",{"title":597,"url":598,"accessed":555},"SAP Fiori apps reference library — Cash Flow Analyzer (F2332)","https:\u002F\u002Ffioriappslibrary.hana.ondemand.com\u002Fsap\u002Ffix\u002FexternalViewer\u002Findex.html#\u002Fdetail\u002FApps('F2332')\u002FS32OP",{"title":600,"url":601,"accessed":555},"SAP Fiori apps reference library — Manage Bank Accounts (F1366A)","https:\u002F\u002Ffioriappslibrary.hana.ondemand.com\u002Fsap\u002Ffix\u002FexternalViewer\u002Findex.html#\u002Fdetail\u002FApps('F1366A')\u002FS32OP",{"title":603,"url":604,"accessed":555},"SAP Fiori apps reference library — Approve Bank Payments Version 2 (F0673A)","https:\u002F\u002Ffioriappslibrary.hana.ondemand.com\u002Fsap\u002Ffix\u002FexternalViewer\u002Findex.html#\u002Fdetail\u002FApps('F0673A')\u002FS32OP",{"title":606,"url":607,"accessed":555},"SAP Fiori apps reference library — Hedge Management Cockpit (TOENE)","https:\u002F\u002Ffioriappslibrary.hana.ondemand.com\u002Fsap\u002Ffix\u002FexternalViewer\u002Findex.html#\u002Fdetail\u002FApps('TOENE')\u002FS32OP",{"title":609,"url":610,"accessed":555},"SAP Help — Apps for Treasury and Risk Management (SAP S\u002F4HANA)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002F2cb817564e8ff708e10000000a441470.html",{"title":612,"url":613,"accessed":555},"SAP Help — Manage Banks - Cash Management (Cash and Liquidity Management)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fac319d8fa4ea4624b40a58d23e3c4627\u002Fa4e4d58b503d4ab69f63d7ec92f3b1f9.html",{"title":615,"url":616,"accessed":555},"SAP Help — Manage Banks (Deprecated) (Cash and Liquidity Management)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fac319d8fa4ea4624b40a58d23e3c4627\u002F917f0e56a686fb37e10000000a44147b.html",{"title":618,"url":619,"accessed":555},"SAP Help — Approve Bank Payments (Cash and Liquidity Management)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fac319d8fa4ea4624b40a58d23e3c4627\u002Fc401ac923da649359cb8052438b0d9be.html",{"title":621,"url":622,"accessed":555},"SAP Help — Business Function: Cash and Liquidity Management","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fac319d8fa4ea4624b40a58d23e3c4627\u002Fc7999f525c5b224fe10000000a445394.html",{"title":624,"url":625,"accessed":555},"SAP Help — Manage Bank Statements","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F3cb1182b4a184bdd93f8d62e3f1f0741\u002Fe74a1f567afbdf21e10000000a4450e5.html",{"title":627,"url":628,"accessed":555},"SAP Help — Subitems of Bank Statement Items (What's New in SAP S\u002F4HANA Cloud 2408, App ID F1564)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_CLOUD\u002Fee9ee0ca4c3942068ea584d2f929b5b1\u002F0124564a69284414af9722440aa13df3.html",{"title":630,"url":631,"accessed":555},"SAP Help — Basic Cash Operations (What's New in SAP S\u002F4HANA 1809)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fe296651f454c4284ade361292c633d69\u002F55421ea96597486784ecc3b581175cb5.html",{"title":633,"url":634,"accessed":555},"SAP Help — Fix, Pay, and Post Flows (SAP S\u002F4HANA Cloud Public Edition, App ID TBB1)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_CLOUD\u002Fe5ec5859d8e54df98492d80564a734c0\u002F4219c55368511d4be10000000a174cb4.html",{"title":636,"url":637,"accessed":555},"SAP Help — Post to General Ledger (SAP S\u002F4HANA Cloud Best Practices, TBB1 and TPM10 as Fiori apps)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_CLOUD_BEST_PRACTICES\u002F5d9bad597842a831529297b394f69f2f\u002Fd233811780d24b7c801abbf7cb7084ad.html",{"title":639,"url":640,"accessed":555},"SAP Help — New Filters in Cash Flow Analyzer (What's New in SAP S\u002F4HANA Cloud 2602, F2332)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_CLOUD\u002Fee9ee0ca4c3942068ea584d2f929b5b1\u002F247fdb44b04c48e0aa088cd7d4c91b61.html",{"title":642,"url":643,"accessed":555},"SAP Help — EMIR Fields Added to Manage Financial Transactions App (What's New in SAP S\u002F4HANA Cloud 2502, F6157)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_CLOUD\u002Fee9ee0ca4c3942068ea584d2f929b5b1\u002F40a426d12639482bba418270ca535430.html",{"title":645,"url":646,"accessed":555},"SAP Help — New Options for Automated Payment Runs (What's New in SAP S\u002F4HANA Cloud 2508, F2770\u002FF2771)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_CLOUD\u002Fee9ee0ca4c3942068ea584d2f929b5b1\u002F1575a437b85a49d3ba50091fb772efc8.html",{"title":648,"url":649,"accessed":555},"SAP Help — Cash Trade Requests for Money Market (What's New in SAP S\u002F4HANA 2020)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fe296651f454c4284ade361292c633d69\u002Fba3315584a8d4e3990fd214e5e0e64aa.html","blog\u002Fsap-treasury-fiori-apps",[652,653,654,655,656],"sap","treasury","trm","s4hana","cash-management","text","76wakzMfaNjwvpIwzcr-7L8ZddR8Xbe1i0Gq1yVH-6c",{"related":660,"prev":673,"next":675,"hasOrder":573,"place":677},[661,665,669],{"path":662,"title":663,"description":664},"\u002Fblog\u002Fsap-trm-product-types-and-transaction-types","SAP TRM Product Types and Transaction Types, Explained","How SAP Treasury classifies deals: fixed product categories, configurable product types like 51A and 60A, transaction types, and the layers below.",{"path":666,"title":667,"description":668},"\u002Fblog\u002Fsap-trm-position-management-and-valuation","SAP TRM Position Management and Valuation","How SAP TRM turns captured deals into managed positions and values them under parallel accounting bases, posting the results to Financial Accounting.",{"path":670,"title":671,"description":672},"\u002Fblog\u002Fsap-trm-accounting-and-posting-architecture","SAP TRM Accounting & Posting Architecture","How a treasury deal becomes a G\u002FL posting in SAP TRM: account determination via symbols, valuation areas for parallel accounting, and ledger reconciliation.",{"path":23,"title":674,"type":657,"language":553},"SAP Treasury Transaction Codes: The Ones That Matter",{"path":142,"title":676,"type":657,"language":553},"SAP Treasury Tables: Where Deals, Flows and Positions Live",{"label":678,"position":679,"total":572,"hub":680},"Transactions",4,"\u002Ftopics\u002Fsap-treasury",[],1785748597514]