[{"data":1,"prerenderedAt":1000},["ShallowReactive",2],{"blog-\u002Fblog\u002Fsap-treasury-transaction-codes":3,"blog-related-\u002Fblog\u002Fsap-treasury-transaction-codes":979,"blog-surround-\u002Fblog\u002Fsap-treasury-transaction-codes":999},{"id":4,"title":5,"audience":6,"body":10,"cluster":834,"conversionGoal":835,"cornerstone":836,"date":837,"description":838,"draft":836,"extension":839,"factCheckedAt":837,"faq":840,"featured":836,"language":835,"meta":853,"minRead":854,"navigation":855,"order":856,"originalAsset":835,"path":857,"pillar":858,"primaryKeyword":859,"publicationOrder":860,"relatedProject":835,"releaseScope":861,"reviewCycle":862,"reviewMethod":863,"reviewStatus":864,"reviewedAt":837,"reviewedBy":865,"searchIntent":866,"seo":867,"sources":868,"stem":971,"tags":972,"type":977,"updated":835,"__hash__":978},"blog\u002Fblog\u002Fsap-treasury-transaction-codes.md","SAP Treasury Transaction Codes: The Ones That Matter",[7,8,9],"sap-treasury-consultant","treasury-system-lead","solution-architect",{"type":11,"value":12,"toc":821},"minimark",[13,21,30,33,38,138,146,149,153,255,267,275,278,282,330,338,342,400,411,415,495,503,507,576,584,588,679,692,696,754,762,766,769,791,804,807],[14,15,16,20],"p",{},[17,18,19],"strong",{},"If you work in SAP Treasury and Risk Management, you live in perhaps forty transaction codes: FTR_CREATE and FTR_EDIT for the deals, TBB1 and the TPM family for postings and period-end, TPM12\u002FTPM13\u002FTPM20 for finding out what actually happened, and a ring of cash, hedge, market-data and payment codes around them."," That's the whole list, and this page is a reference for it. The reason it exists: search for \"SAP treasury tcodes\" and you get 400-row table dumps, scraped from each other, listing codes that were retired two releases ago next to codes that never belonged to TRM in the first place. So I did it the slow way — every code below is checked against SAP's own documentation, and anything I couldn't verify there didn't make the page. A shorter list you can trust beats a longer one you have to re-verify yourself.",[14,22,23,24,29],{},"Grouping is by working area, the way the ",[25,26,28],"a",{"href":27},"\u002Fblog\u002Fsap-transaction-manager","Transaction Manager"," itself is organized, with a note per group on what a consultant actually opens daily versus what exists but rarely gets touched.",[14,31,32],{},"One scope note before the tables: these are the GUI transactions of S\u002F4HANA on-premise and private edition (and their ECC ancestors). SAP's app catalog now lists several of them with a \"- Classic\" suffix, which tells you where the Fiori-first direction is heading — and in S\u002F4HANA Cloud Public Edition the classic codes aren't available at all. More on that at the end.",[34,35,37],"h2",{"id":36},"the-deal-desk-ftr_-and-the-master-data-under-it","The deal desk: FTR_* and the master data under it",[39,40,41,57],"table",{},[42,43,44],"thead",{},[45,46,47,51,54],"tr",{},[48,49,50],"th",{},"Code",[48,52,53],{},"SAP's name",[48,55,56],{},"What you use it for",[58,59,60,72,83,94,105,116,127],"tbody",{},[45,61,62,66,69],{},[63,64,65],"td",{},"FTR_CREATE",[63,67,68],{},"Create Financial Transaction",[63,70,71],{},"Enter a deal — money market, FX, derivatives, securities, commodities",[45,73,74,77,80],{},[63,75,76],{},"FTR_EDIT",[63,78,79],{},"Process (Edit) Financial Transaction",[63,81,82],{},"Change, settle or work an existing deal",[45,84,85,88,91],{},[63,86,87],{},"FTR_DISPLAY",[63,89,90],{},"Display Financial Transaction",[63,92,93],{},"Look at a deal without touching it",[45,95,96,99,102],{},[63,97,98],{},"FTR_00",[63,100,101],{},"Collective Processing: Transaction Management",[63,103,104],{},"The back-office worklist — settle and confirm deals in bulk",[45,106,107,110,113],{},[63,108,109],{},"BP",[63,111,112],{},"Maintain Business Partner",[63,114,115],{},"Counterparties — every deal needs one before FTR_CREATE will save it",[45,117,118,121,124],{},[63,119,120],{},"FWZZ",[63,122,123],{},"Securities class master data",[63,125,126],{},"The security (class) a securities deal references",[45,128,129,132,135],{},[63,130,131],{},"FTR_COMONI",[63,133,134],{},"Correspondence Monitor",[63,136,137],{},"All correspondence objects — outgoing confirmations and their matching",[14,139,140,141,145],{},"The honest usage split: a front office lives in FTR_CREATE and FTR_EDIT; a back office lives in FTR_00. ",[25,142,144],{"href":143},"\u002Fblog\u002Fbusiness-partner-configuration-sap-treasury","Business partner setup"," via BP is the thing that blocks the first deal on every new implementation, so it belongs in this group even though it's not a treasury-only code. FTR_COMONI is the one people forget exists until an auditor asks how confirmations are matched — the correspondence monitor is the answer, and SAP documents it as the overview of all correspondence objects.",[14,147,148],{},"S\u002F4HANA note: SAP documents a Fiori app, Manage Financial Transactions (app ID F6157), alongside FTR_00, including a feature comparison between the two — the comparison is worth reading before you decide which one your back office standardizes on, because the supported product categories differ.",[34,150,152],{"id":151},"posting-and-period-end-tbb1-and-the-tpm-family","Posting and period-end: TBB1 and the TPM family",[39,154,155,165],{},[42,156,157],{},[45,158,159,161,163],{},[48,160,50],{},[48,162,53],{},[48,164,56],{},[58,166,167,178,189,200,211,222,233,244],{},[45,168,169,172,175],{},[63,170,171],{},"TBB1",[63,173,174],{},"Treasury: Post Flows",[63,176,177],{},"Post the flows of financial transactions to the general ledger",[45,179,180,183,186],{},[63,181,182],{},"TPM10",[63,184,185],{},"Fix, Post or Reverse Transactions",[63,187,188],{},"Fix, post, reverse business transactions from positions (S\u002F4HANA app name: Process Business Transactions)",[45,190,191,194,197],{},[63,192,193],{},"TPM18",[63,195,196],{},"Fix and Post Derived Business Transactions",[63,198,199],{},"Post derived business transactions — e.g. at contract close in FX hedge accounting",[45,201,202,205,208],{},[63,203,204],{},"TPM1",[63,206,207],{},"Execute Valuation",[63,209,210],{},"Key-date valuation of positions, per valuation area",[45,212,213,216,219],{},[63,214,215],{},"TPM2",[63,217,218],{},"Reverse Valuation",[63,220,221],{},"Undo a valuation run",[45,223,224,227,230],{},[63,225,226],{},"TPM44",[63,228,229],{},"Run Accrual\u002FDeferral",[63,231,232],{},"Accrue and defer expenses and revenues at period end",[45,234,235,238,241],{},[63,236,237],{},"TI10",[63,239,240],{},"Create Adjustment - Rates\u002FPrices",[63,242,243],{},"Interest rate adjustment (fixings) for variable-rate deals",[45,245,246,249,252],{},[63,247,248],{},"TPM60",[63,250,251],{},"Calculate Net Present Values",[63,253,254],{},"NPV calculation feeding valuation and reporting",[14,256,257,258,261,262,266],{},"This is the period-end backbone, and it's the group where the confusion concentrates, because three codes have names that sound like the same job. The working distinction: ",[17,259,260],{},"TBB1 posts your deals' flows; TPM10 and TPM18 handle the business transactions the system derives from positions."," SAP ERP documentation names TPM10 \"Fix, Post or Reverse Transactions\" and puts it in the period-end closing process; the S\u002F4HANA app catalog calls the same code \"Process Business Transactions\". TPM18 appears throughout SAP's hedge accounting documentation — contract close in FX hedge accounting runs through it. If your close checklist has only TBB1 on it, positions will quietly drift from the ledger; the ",[25,263,265],{"href":264},"\u002Fblog\u002Fsap-trm-accounting-and-posting-architecture","posting architecture"," article explains what each of these actually writes.",[14,268,269,270,274],{},"TPM1 is the other daily-critical one: valuation runs per valuation area, one per accounting principle, and ",[25,271,273],{"href":272},"\u002Fblog\u002Fsap-trm-position-management-and-valuation","position management"," decides what it values. TPM2 exists because you will need it — a valuation run with wrong market data is a matter of when, not if.",[14,276,277],{},"A current-release detail worth knowing: SAP S\u002F4HANA 2025 documents new payment-control options in what it now calls the \"Fix, Pay and Post Flows (TBB1)\" app — same code, growing job.",[34,279,281],{"id":280},"reading-what-happened-the-reporting-trio","Reading what happened: the reporting trio",[39,283,284,295],{},[42,285,286],{},[45,287,288,290,293],{},[48,289,50],{},[48,291,292],{},"SAP's name (S\u002F4HANA app catalog)",[48,294,56],{},[58,296,297,308,319],{},[45,298,299,302,305],{},[63,300,301],{},"TPM12",[63,303,304],{},"Treasury Position Values - Classic",[63,306,307],{},"Position list — what you hold, at what value",[45,309,310,313,316],{},[63,311,312],{},"TPM13",[63,314,315],{},"Treasury Position Flows - Classic",[63,317,318],{},"Position flow list \u002F subledger cash flow",[45,320,321,324,327],{},[63,322,323],{},"TPM20",[63,325,326],{},"Treasury Posting Journal - Classic",[63,328,329],{},"Every posting the treasury subledger generated",[14,331,332,333,337],{},"These three are what I open on any \"why did it post that?\" call (the ",[25,334,336],{"href":335},"\u002Fblog\u002Fsap-treasury-tables","tables behind them"," have a reference of their own), in reverse order: TPM20 to see the posting, TPM13 to see the flows behind it, TPM12 to see the position they belong to. Since S\u002F4HANA 1909, TPM20 can show reversals and the postings they reversed on separate lines, which sounds cosmetic and saves real time in a messy close. Note the \"- Classic\" suffix in all three official app names — SAP's label, not mine, and a clear signal about the direction of travel.",[34,339,341],{"id":340},"market-data","Market data",[39,343,344,354],{},[42,345,346],{},[45,347,348,350,352],{},[48,349,50],{},[48,351,53],{},[48,353,56],{},[58,355,356,367,378,389],{},[45,357,358,361,364],{},[63,359,360],{},"TBDM",[63,362,363],{},"Market Data File Interface: Import Rates and Prices",[63,365,366],{},"Import rates and prices from a file",[45,368,369,372,375],{},[63,370,371],{},"TBEXN",[63,373,374],{},"Market Data Transfer from Spreadsheet",[63,376,377],{},"Pull market data in from a spreadsheet",[45,379,380,383,386],{},[63,381,382],{},"TBD4",[63,384,385],{},"Request Current Market Data - Datafeed",[63,387,388],{},"Request current data through the datafeed interface",[45,390,391,394,397],{},[63,392,393],{},"OB08",[63,395,396],{},"Maintain Currency Exchange Rates",[63,398,399],{},"The exchange rate table (TCURR) everything reads",[14,401,402,403,407,408,410],{},"Nobody plans time for market data and everybody loses time to it: TPM1 fails or produces nonsense, and the cause is a missing rate, a stale curve, or a datafeed translation entry — the ",[25,404,406],{"href":405},"\u002Fblog\u002Fsap-treasury-market-data-management","market data article"," covers the plumbing. OB08 is plain FI rather than TRM, but treasury valuations read it constantly, so it earns its row. One correction to the usual dump lists: the spreadsheet transfer code SAP's current S\u002F4HANA documentation names is ",[17,409,371],{}," — the older TBEX appears on tcode sites, not in the S\u002F4HANA documentation I checked.",[34,412,414],{"id":413},"hedge-management-and-hedge-accounting","Hedge management and hedge accounting",[39,416,417,427],{},[42,418,419],{},[45,420,421,423,425],{},[48,422,50],{},[48,424,53],{},[48,426,56],{},[58,428,429,440,451,462,473,484],{},[45,430,431,434,437],{},[63,432,433],{},"THMEX",[63,435,436],{},"Hedge Plan \u002F Hedge Plan List",[63,438,439],{},"Hedge plans and hedging relationships (Hedge Accounting for Exposures, E-HA)",[45,441,442,445,448],{},[63,443,444],{},"THM80",[63,446,447],{},"Hedging Relationships: Effectiveness Test",[63,449,450],{},"Run and review effectiveness tests (E-HA)",[45,452,453,456,459],{},[63,454,455],{},"TPM100",[63,457,458],{},"Hedging relationships processing",[63,460,461],{},"Check and release designated hedging relationships",[45,463,464,467,470],{},[63,465,466],{},"TPM120",[63,468,469],{},"Release Hedging Business Transactions",[63,471,472],{},"Release hedging business transactions for posting",[45,474,475,478,481],{},[63,476,477],{},"TPM121",[63,479,480],{},"Reverse Release of Hedging Business Transactions",[63,482,483],{},"Undo that release",[45,485,486,489,492],{},[63,487,488],{},"FTREX1",[63,490,491],{},"Raw Exposures (Exposure Management 2.0)",[63,493,494],{},"Enter and process the raw exposures you hedge against",[14,496,497,498,502],{},"Which of these you touch depends entirely on which hedge accounting flavor you run — the distinction the ",[25,499,501],{"href":500},"\u002Fblog\u002Fhedge-management-in-sap","hedge management article"," is built around. THMEX and THM80 belong to classic Hedge Accounting for Exposures; the newer Hedge Management and Accounting of Net Open Exposures is Fiori-first (the Hedge Management Cockpit is an app, not a tcode), with the TPM1xx codes doing the release-and-post mechanics underneath. FTREX1 is easy to overlook because it sits in Exposure Management rather than the Transaction Manager, but without released raw exposures there's nothing to designate against.",[34,504,506],{"id":505},"analyzers-and-limits","Analyzers and limits",[39,508,509,519],{},[42,510,511],{},[45,512,513,515,517],{},[48,514,50],{},[48,516,53],{},[48,518,56],{},[58,520,521,532,543,554,565],{},[45,522,523,526,529],{},[63,524,525],{},"JBRX",[63,527,528],{},"Analyze NPV",[63,530,531],{},"Single-position NPV analysis in the Market Risk Analyzer",[45,533,534,537,540],{},[63,535,536],{},"AISGENKF",[63,538,539],{},"Calculate Market Risk Key Figures",[63,541,542],{},"Batch calculation of market-risk key figures",[45,544,545,548,551],{},[63,546,547],{},"TBL1",[63,549,550],{},"Manage Limits",[63,552,553],{},"Maintain counterparty\u002Flimit structures",[45,555,556,559,562],{},[63,557,558],{},"TBLB",[63,560,561],{},"Review Limit Utilizations",[63,563,564],{},"What's using the limits right now",[45,566,567,570,573],{},[63,568,569],{},"KLNACHT",[63,571,572],{},"End-of-Day Processing",[63,574,575],{},"The Credit Risk Analyzer's end-of-day run",[14,577,578,579,583],{},"The risk team's corner, and the least-opened group on this page — which is the point of listing it honestly. On most corporate installations JBRX gets opened when someone challenges a valuation, TBLB gets opened when a dealer hits a limit block, and KLNACHT is scheduled as a background job that nobody looks at until it fails. The ",[25,580,582],{"href":581},"\u002Fblog\u002Fsap-credit-risk-analyzer","Credit Risk Analyzer"," article covers what that end-of-day run actually maintains.",[34,585,587],{"id":586},"cash-management","Cash management",[39,589,590,600],{},[42,591,592],{},[45,593,594,596,598],{},[48,595,50],{},[48,597,53],{},[48,599,56],{},[58,601,602,613,624,635,646,657,668],{},[45,603,604,607,610],{},[63,605,606],{},"FF7AN",[63,608,609],{},"Display Cash Position (S\u002F4HANA)",[63,611,612],{},"Today's cash, from One Exposure and memo records",[45,614,615,618,621],{},[63,616,617],{},"FF7BN",[63,619,620],{},"Display Liquidity Forecast (S\u002F4HANA)",[63,622,623],{},"The medium-term view from the same data",[45,625,626,629,632],{},[63,627,628],{},"FF7A \u002F FF7B",[63,630,631],{},"Cash Position \u002F Liquidity Forecast",[63,633,634],{},"The classic ECC pair the above replaced",[45,636,637,640,643],{},[63,638,639],{},"FF63 \u002F FF65",[63,641,642],{},"Create \u002F Display Memo Record",[63,644,645],{},"Manual cash advices — classic; Fiori Manage Memo Records replaced these apps",[45,647,648,651,654],{},[63,649,650],{},"FF67",[63,652,653],{},"Manual Bank Statement",[63,655,656],{},"Key in a statement by hand",[45,658,659,662,665],{},[63,660,661],{},"FF.5",[63,663,664],{},"Import Electronic Bank Statement",[63,666,667],{},"Load MT940\u002FCAMT.053 statement files",[45,669,670,673,676],{},[63,671,672],{},"FEBA_BANK_STATEMENT",[63,674,675],{},"Reprocess Bank Statement Items",[63,677,678],{},"Post-process what the import couldn't clear",[14,680,681,682,686,687,691],{},"Strictly this is ",[25,683,685],{"href":684},"\u002Fblog\u002Fsap-cash-management-s4hana","Cash Management",", not TRM — but no treasury consultant gets to ignore it, and the tcode-dump sites mix the two indiscriminately, so better to draw the line deliberately. The S\u002F4HANA story matters here more than anywhere else on this page: FF7AN and FF7BN read One Exposure, and SAP's release notes are explicit that the Fiori Manage Memo Records app replaced the FF63\u002FFF65 apps. Day-to-day reality is bank-statement processing: FF.5 in the morning, FEBA_BANK_STATEMENT for the items that didn't clear — the ",[25,688,690],{"href":689},"\u002Fblog\u002Felectronic-bank-statement-processing-in-sap","electronic bank statement article"," walks through that pipeline.",[34,693,695],{"id":694},"payments-and-bank-communication","Payments and bank communication",[39,697,698,708],{},[42,699,700],{},[45,701,702,704,706],{},[48,703,50],{},[48,705,53],{},[48,707,56],{},[58,709,710,721,732,743],{},[45,711,712,715,718],{},[63,713,714],{},"F110",[63,716,717],{},"Payment run (AP\u002FAR)",[63,719,720],{},"The standard payment program for vendors and customers",[45,722,723,726,729],{},[63,724,725],{},"F111",[63,727,728],{},"Payment run for payment requests",[63,730,731],{},"The treasury one — pays the payment requests TRM deals generate",[45,733,734,737,740],{},[63,735,736],{},"BNK_APP",[63,738,739],{},"Approve Payments",[63,741,742],{},"Release payment batches in Bank Communication Management",[45,744,745,748,751],{},[63,746,747],{},"BNK_MONI",[63,749,750],{},"Batch and Payment Monitor",[63,752,753],{},"Track what happened to every batch after approval",[14,755,756,757,761],{},"F111 versus F110 is a distinction worth being pedantic about: treasury settlements flow as payment requests, and F111 is the program that pays them — plenty of go-live payment incidents reduce to \"someone ran the wrong one.\" BNK_APP and BNK_MONI are the working pair of ",[25,758,760],{"href":759},"\u002Fblog\u002Fbank-communication-management-bcm-sap","Bank Communication Management","; S\u002F4HANA also documents an Approve Bank Payments app that can mass-approve batches as a background job, which changes the approval workflow conversation on bigger volumes.",[34,763,765],{"id":764},"what-i-left-out-on-purpose","What I left out, on purpose",[14,767,768],{},"Three categories didn't make the page, and the reasons are the useful part:",[770,771,772,779,785],"ul",{},[773,774,775,778],"li",{},[17,776,777],{},"Codes I couldn't verify in SAP's current documentation."," TBEX is the clearest case — S\u002F4HANA documentation names TBEXN for the spreadsheet transfer. Likewise the statement-postprocessing code circulating as FEBAN: what SAP's S\u002F4HANA documentation names is FEBA_BANK_STATEMENT. When a dump site and the SAP Help disagree, believe the Help.",[773,780,781,784],{},[17,782,783],{},"Configuration transactions."," The IMG side (posting specs, valuation areas, product types) is a different discipline with a different audience, and mixing it into a working-tcode list is how those 400-row dumps got unusable.",[773,786,787,790],{},[17,788,789],{},"The long tail that exists but you'll rarely open"," — securities corporate actions, archiving runs, migration utilities. Real, documented, and not what this page is for.",[14,792,793,794,798,799,803],{},"And the standing caveat, same as everywhere in this ",[25,795,797],{"href":796},"\u002Fblog\u002Fwhat-is-sap-treasury-and-risk-management","SAP treasury guide",": codes and app availability differ by release and edition. On-premise and private edition keep the GUI transactions; SAP S\u002F4HANA Cloud Public Edition is Fiori-only, and if that's your target, this page is a translation table, not a map. If you're mid-move, the ",[25,800,802],{"href":801},"\u002Fblog\u002Fmigrating-sap-treasury-ecc-to-s4hana","ECC to S\u002F4HANA migration article"," covers what changes underneath these codes — because the codes surviving the migration doesn't mean their behavior did.",[805,806],"hr",{},[14,808,809],{},[810,811,812,813,816,817,820],"em",{},"See also ",[25,814,815],{"href":27},"SAP Transaction Manager"," and ",[25,818,819],{"href":264},"SAP TRM accounting and posting architecture",".",{"title":822,"searchDepth":823,"depth":823,"links":824},"",2,[825,826,827,828,829,830,831,832,833],{"id":36,"depth":823,"text":37},{"id":151,"depth":823,"text":152},{"id":280,"depth":823,"text":281},{"id":340,"depth":823,"text":341},{"id":413,"depth":823,"text":414},{"id":505,"depth":823,"text":506},{"id":586,"depth":823,"text":587},{"id":694,"depth":823,"text":695},{"id":764,"depth":823,"text":765},"transactions",null,false,"2026-08-02","A verified reference of SAP Treasury and Risk Management transaction codes — FTR_CREATE to TPM20 — grouped by working area and checked against SAP Help.","md",[841,844,847,850],{"question":842,"answer":843},"What transaction code do you use to create a deal in SAP TRM?","FTR_CREATE (Create Financial Transaction) creates deals across the Transaction Manager's product areas — money market, foreign exchange, derivatives and securities. FTR_EDIT changes an existing transaction, FTR_DISPLAY shows it, and FTR_00 is the collective-processing worklist the back office uses to settle and confirm deals in bulk. In S\u002F4HANA, SAP additionally documents the Manage Financial Transactions Fiori app (app ID F6157) alongside the classic transactions.",{"question":845,"answer":846},"What is the difference between TBB1 and TPM10 in SAP Treasury?","TBB1 (Post Flows) posts the flows of your financial transactions to the general ledger, and SAP's own documentation calls it Treasury: Post Flows; in recent S\u002F4HANA releases it surfaces as the Fix, Pay and Post Flows app. TPM10 is what SAP ERP documentation calls Fix, Post or Reverse Transactions and the S\u002F4HANA app catalog lists as Process Business Transactions — it fixes, posts and reverses the business transactions generated from positions. TPM18 (Fix and Post Derived Business Transactions) is its sibling that SAP's hedge accounting documentation uses, for example at contract close. A period-end close typically runs more than one of them, which is exactly why people mix them up.",{"question":848,"answer":849},"Are classic SAP treasury transaction codes replaced by Fiori apps in S\u002F4HANA?","Partly, and SAP is explicit about the direction. The same GUI codes still run in S\u002F4HANA on-premise and private edition, but the app catalog lists several under names like Treasury Posting Journal - Classic (TPM20), and SAP documents Fiori successors for specific cases: Manage Memo Records replaced the FF63\u002FFF65 apps, FF7AN and FF7BN carry the cash position and liquidity forecast, and Manage Financial Transactions (F6157) sits alongside FTR_00. In SAP S\u002F4HANA Cloud Public Edition the classic transactions are not available at all, so a Fiori-first habit is worth building now.",{"question":851,"answer":852},"Which transaction code shows what treasury posted to the general ledger?","TPM20, the Treasury Posting Journal, is the first stop: it lists the postings the Treasury subledger generated, and since S\u002F4HANA 1909 it can show reversals and reversed postings on separate lines. TPM13 (position flows) shows the flows behind those postings, and TPM12 (position values) shows the position they belong to. On a posting investigation you typically walk exactly that chain: journal, flows, position.",{},8,true,8.2,"\u002Fblog\u002Fsap-treasury-transaction-codes","sap-treasury","sap treasury transaction codes",186,"SAP S\u002F4HANA on-premise\u002Fprivate edition (classic transactions noted against SAP ERP\u002FECC where the documentation is ECC-specific). SAP S\u002F4HANA Cloud Public Edition is Fiori-only; most codes here do not apply there.","annual","editorial-and-factual","reviewed","Tan Gravam","informational",{"title":5,"description":838},[869,872,875,878,881,884,887,890,893,896,899,902,905,908,911,914,917,920,923,926,929,932,935,938,941,944,947,950,953,956,959,962,965,968],{"title":870,"url":871,"accessed":837},"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":873,"url":874,"accessed":837},"SAP Help — Apps for Processing Financial Transactions (SAP S\u002F4HANA)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002F0f19c55368511d4be10000000a174cb4.html",{"title":876,"url":877,"accessed":837},"SAP Help — Feature Comparison for Collective Processing Apps for Financial Transactions","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002Fef7f3a881b514f24a826becbfa43c3b6.html",{"title":879,"url":880,"accessed":837},"SAP Help — Negative Prices in Commodity Futures and Commodity Swaps (Finance)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F888cbe952a0e4a729f8b823d69860929\u002F86d627cacd2a4f9ab591d7984cba962f.html",{"title":882,"url":883,"accessed":837},"SAP Help — Securities Lending (Treasury and Risk Management)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002Fac15da531198434de10000000a174cb4.html",{"title":885,"url":886,"accessed":837},"SAP Help — Free Text Search (Treasury and Risk Management)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002Fcc369a51021a9302e10000000a44538d.html",{"title":888,"url":889,"accessed":837},"SAP Help — Correspondence Monitor (Treasury and Risk Management)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002F6d0cda531198434de10000000a174cb4.html",{"title":891,"url":892,"accessed":837},"SAP Help — Term End-Postings after Migration","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F8308e6d301d54584a33cd04a9861bc52\u002F27647bfe638d4a9c82607b298c2e62d6.html",{"title":894,"url":895,"accessed":837},"SAP Help — New Options for Automated Payment Runs (What's New in SAP S\u002F4HANA 2025)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Ff5d3e1005efd4e86acf9a65abf428082\u002F34169a4b185546b5b7ff094d3953b0e5.html",{"title":897,"url":898,"accessed":837},"SAP Help — Period-End Closing (SAP ERP Treasury and Risk Management)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_ERP\u002F4d6b9b32599844ee81b23a443efedb7f\u002F7a237f586d809344e10000000a4450e5.html",{"title":900,"url":901,"accessed":837},"SAP Help — Hedge Accounting for Positions (P-HA)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002F49bff48439731b93e10000000a42189b.html",{"title":903,"url":904,"accessed":837},"SAP Help — Reverse Valuation (Treasury and Risk Management)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002F8719c55368511d4be10000000a174cb4.html",{"title":906,"url":907,"accessed":837},"SAP Help — Parallel Processing in the Transaction Manager","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002F8d76795346efe747e10000000a441470.html",{"title":909,"url":910,"accessed":837},"SAP Help — Net Payment for Cross-Currency Interest Rate Swaps (What's New in SAP S\u002F4HANA 2021)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fe296651f454c4284ade361292c633d69\u002Fc061826edf44483e844260408523224b.html",{"title":912,"url":913,"accessed":837},"SAP Help — Reporting on Forward Loan Purchases","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002F4991557524454b6ba6538867d3c38e57.html",{"title":915,"url":916,"accessed":837},"SAP Help — Mass Price Adjustment for Raw Exposures","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002Fa103b06b87c64e6c80a761489a2e26c7.html",{"title":918,"url":919,"accessed":837},"SAP Help — DCS Based Market Data Provision","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F8308e6d301d54584a33cd04a9861bc52\u002F81a2268a15a149888b4180b9bb4c83b4.html",{"title":921,"url":922,"accessed":837},"SAP Help — Activate Additional Checks in Translation Table for Currencies, Datafeed (What's New in SAP S\u002F4HANA 2025)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Ff5d3e1005efd4e86acf9a65abf428082\u002Fa12437ba25b444a0a9cd8e1fc4979581.html",{"title":924,"url":925,"accessed":837},"SAP Help — Exchange Rate (SAP S\u002F4HANA Data Migration)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F29193bf0ebdd4583930b2176cb993268\u002F3f7a1a6504ea4a6f966bf196ffde5518.html",{"title":927,"url":928,"accessed":837},"SAP Help — Archiving Effectiveness Tests with TRTM_HMLOG","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002F4ea2a1515a2f4f58e10000000a42189e.html",{"title":930,"url":931,"accessed":837},"SAP Help — Releasing Commodity Hedging Relationships (TPM100)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F8308e6d301d54584a33cd04a9861bc52\u002Fe4fec81d50b94021a6b92515fa578fe9.html",{"title":933,"url":934,"accessed":837},"SAP Help — Exposure Management 2.0","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F848f8ce21bcd4f67bce77494799e2257\u002F4c3af7c7b48f1ca9e10000000a42189e.html",{"title":936,"url":937,"accessed":837},"SAP Help — TRM, New Apps on SAP Fiori Launchpad (What's New in SAP S\u002F4HANA 1709)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F4c6c3c99e6e94a92a626f424add61cba\u002Fc49666453f6b491aabf024aa34c611b7.html",{"title":939,"url":940,"accessed":837},"SAP Help — Cash Position (SAP ERP Cash and Liquidity Management)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_ERP\u002F495b05f6dbb24b1da46e4027d3a28fef\u002F65a264947e934a059eaa44d1e06267af.html",{"title":942,"url":943,"accessed":837},"SAP Help — Liquidity Forecast (SAP ERP Cash and Liquidity Management)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_ERP\u002F495b05f6dbb24b1da46e4027d3a28fef\u002F3219206619b44cd6aeeb2cec9dd6c137.html",{"title":945,"url":946,"accessed":837},"SAP Help — Display Cash Position (What's New in SAP S\u002F4HANA 1610)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fe296651f454c4284ade361292c633d69\u002F26fd967701b1417f9c7b70da543e924d.html",{"title":948,"url":949,"accessed":837},"SAP Help — Display Liquidity Forecast (What's New in SAP S\u002F4HANA 1610)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fe296651f454c4284ade361292c633d69\u002Fac2dcd9d87844a368f0b1b13df64074e.html",{"title":951,"url":952,"accessed":837},"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":954,"url":955,"accessed":837},"SAP Help — Payment Application Hierarchy (Loans Management, FS-CML)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F99fb46a79ab241d5984df80fe7a9aa32\u002F59a8ce7064a54238b7dbca7d900dac87.html",{"title":957,"url":958,"accessed":837},"SAP Help — Down Payment Integration with SD (Central Finance)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F26c2d5e366bc44c1a98f2a9212a0c49d\u002F66e9a64f930a4117a764d937f1cda9b4.html",{"title":960,"url":961,"accessed":837},"SAP Help — Merge Payments (Payments and Bank Communication)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fe200555127f24878bed8d1481c9d5a0b\u002F367ad0531d8b4208e10000000a174cb4.html",{"title":963,"url":964,"accessed":837},"SAP Help — Approve Payments, BNK_APP (SAP ERP, Roles in SAP Business Client)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_ERP\u002F5cea947f5ec44813bdb75bc2d5115450\u002Fca43348438e5430b971bf4843a8a6214.html",{"title":966,"url":967,"accessed":837},"SAP Help — Unique End-to-End Transaction Reference (UETR) Reporting (Financial Operations)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002F3cb1182b4a184bdd93f8d62e3f1f0741\u002F10a228aed3184d388cfb3102db01389a.html",{"title":969,"url":970,"accessed":837},"SAP Help — Approve Bank Payments (What's New in SAP S\u002F4HANA 2022)","https:\u002F\u002Fhelp.sap.com\u002Fdocs\u002FSAP_S4HANA_ON-PREMISE\u002Fe296651f454c4284ade361292c633d69\u002F29eae0d6e321430a989134ef649b9d37.html","blog\u002Fsap-treasury-transaction-codes",[973,974,975,976],"sap","treasury","trm","s4hana","text","UY-oTBIUktNRu1tagq8XxqSU6uXs-NPC1jOoz5vpz70",{"related":980,"prev":990,"next":992,"hasOrder":855,"place":994},[981,984,987],{"path":264,"title":982,"description":983},"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":500,"title":985,"description":986},"Hedge Management in SAP","Hedge Management in SAP is the risk half of SAP's Hedge Management and Accounting area — Hedge Accounting, switched on separately, designates and posts.",{"path":272,"title":988,"description":989},"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":27,"title":991,"type":977,"language":835},"SAP Transaction Manager: Deals and Instruments",{"path":335,"title":993,"type":977,"language":835},"SAP Treasury Tables: Where Deals, Flows and Positions Live",{"label":995,"position":996,"total":997,"hub":998},"Transactions",3,7,"\u002Ftopics\u002Fsap-treasury",[],1785696769129]