Reference
Look up a code
Every field-level code this site documents, in one place — 169 entries lifted straight from the reference articles. Type what is in front of you; the code links to the section that explains it.
169 of 169
SAP
81 codesSAP Treasury Transaction Codes: The Ones That Matter
- FTR_CREATE
- Create Financial Transaction · Enter a deal — money market, FX, derivatives, securities, commodities
- FTR_EDIT
- Process (Edit) Financial Transaction · Change, settle or work an existing deal
- FTR_DISPLAY
- Display Financial Transaction · Look at a deal without touching it
- FTR_00
- Collective Processing: Transaction Management · The back-office worklist — settle and confirm deals in bulk
- BP
- Maintain Business Partner · Counterparties — every deal needs one before FTR_CREATE will save it
- FWZZ
- Securities class master data · The security (class) a securities deal references
- FTR_COMONI
- Correspondence Monitor · All correspondence objects — outgoing confirmations and their matching
- TBB1
- Treasury: Post Flows · Post the flows of financial transactions to the general ledger
- TPM10
- Fix, Post or Reverse Transactions · Fix, post, reverse business transactions from positions (S/4HANA app name: Process Business Transactions)
- TPM18
- Fix and Post Derived Business Transactions · Post derived business transactions — e.g. at contract close in FX hedge accounting
- TPM1
- Execute Valuation · Key-date valuation of positions, per valuation area
- TPM2
- Reverse Valuation · Undo a valuation run
- TPM44
- Run Accrual/Deferral · Accrue and defer expenses and revenues at period end
- TI10
- Create Adjustment - Rates/Prices · Interest rate adjustment (fixings) for variable-rate deals
- TPM60
- Calculate Net Present Values · NPV calculation feeding valuation and reporting
- TPM12
- Treasury Position Values - Classic · Position list — what you hold, at what value
- TPM13
- Treasury Position Flows - Classic · Position flow list / subledger cash flow
- TPM20
- Treasury Posting Journal - Classic · Every posting the treasury subledger generated
- TBDM
- Market Data File Interface: Import Rates and Prices · Import rates and prices from a file
- TBEXN
- Market Data Transfer from Spreadsheet · Pull market data in from a spreadsheet
- TBD4
- Request Current Market Data - Datafeed · Request current data through the datafeed interface
- OB08
- Maintain Currency Exchange Rates · The exchange rate table (TCURR) everything reads
- THMEX
- Hedge Plan / Hedge Plan List · Hedge plans and hedging relationships (Hedge Accounting for Exposures, E-HA)
- THM80
- Hedging Relationships: Effectiveness Test · Run and review effectiveness tests (E-HA)
- TPM100
- Hedging relationships processing · Check and release designated hedging relationships
- TPM120
- Release Hedging Business Transactions · Release hedging business transactions for posting
- TPM121
- Reverse Release of Hedging Business Transactions · Undo that release
- FTREX1
- Raw Exposures (Exposure Management 2.0) · Enter and process the raw exposures you hedge against
- JBRX
- Analyze NPV · Single-position NPV analysis in the Market Risk Analyzer
- AISGENKF
- Calculate Market Risk Key Figures · Batch calculation of market-risk key figures
- TBL1
- Manage Limits · Maintain counterparty/limit structures
- TBLB
- Review Limit Utilizations · What's using the limits right now
- KLNACHT
- End-of-Day Processing · The Credit Risk Analyzer's end-of-day run
- FF7AN
- Display Cash Position (S/4HANA) · Today's cash, from One Exposure and memo records
- FF7BN
- Display Liquidity Forecast (S/4HANA) · The medium-term view from the same data
- FF7A / FF7B
- Cash Position / Liquidity Forecast · The classic ECC pair the above replaced
- FF63 / FF65
- Create / Display Memo Record · Manual cash advices — classic; Fiori Manage Memo Records replaced these apps
- FF67
- Manual Bank Statement · Key in a statement by hand
- FF.5
- Import Electronic Bank Statement · Load MT940/CAMT.053 statement files
- FEBA_BANK_STATEMENT
- Reprocess Bank Statement Items · Post-process what the import couldn't clear
- F110
- Payment run (AP/AR) · The standard payment program for vendors and customers
- F111
- Payment run for payment requests · The treasury one — pays the payment requests TRM deals generate
- BNK_APP
- Approve Payments · Release payment batches in Bank Communication Management
- BNK_MONI
- Batch and Payment Monitor · Track what happened to every batch after approval
SAP Treasury Fiori Apps: What Replaces Which Transaction
- F1867
- Display Treasury Position Values · TPM12 (Treasury Position Values - Classic) · Positions in the treasury subledger with component values on any key date
- F1754
- Display Treasury Position Flows · TPM13 (Treasury Position Flows - Classic) · Position flows behind those values, operative and derived
- F1755
- Display Treasury Posting Journal · TPM20 (Treasury Posting Journal - Classic) · Accounting information for every posted flow
- F3966
- Treasury Position History · — (no classic equivalent) · How accounting key figures moved over a period, by entity/currency/asset
- F2332
- Cash Flow Analyzer · FF7AN/FF7BN territory · The working analysis surface: cash position and liquidity trend in one
- F1737
- Cash Position · FF7A → FF7AN · Forecasted cash position by country, company, bank, currency
- F0512A
- Liquidity Forecast · FF7B → FF7BN · 90-day liquidity trend from memo records and One Exposure
- F5380
- Short-Term Cash Positioning · — (no classic equivalent) · Position from direct bank balances, driven by cash position profiles
- F0735
- Check Cash Flow Items · — (no classic equivalent) · The data audit: track problematic and missing flows behind the position
- F2986/F2986A
- Manage Memo Records · FF63/FF65 — SAP-documented replacement · Manual cash advices; 2.0 adds spreadsheet import
- F1574A
- Manage Banks - Cash Management · Successor of Manage Banks (F1574), now deprecated · Bank master data relevant to cash management, ratings, contacts
- F6437
- Manage Banks - Master Data · Bank directory maintenance · Create and display banks as master data
- F1366A
- Manage Bank Accounts · The BAM working surface · Create, edit, close, reopen bank accounts; lifecycle and signers
- F1366
- Manage Bank Accounts - Hierarchy · — · The same inventory viewed as a bank hierarchy
- F1564
- Manage Bank Statements · FF67 (manual statement) · Manage manual and electronic statements; spreadsheet upload
- F1680
- Manage Incoming Payment Files · FF.5 (import) · Bring statement files into the system
- F1520
- Reprocess Bank Statement Items · FEBA_BANK_STATEMENT · Post-process items that didn't clear automatically
- F6388
- Bank Statement Monitor · — (no classic equivalent) · Central view of statement arrival and errors, with history
- F0673A
- Approve Bank Payments · BNK_APP · Review, approve, reject, defer payment batches; mass approval
- F2388
- Monitor Payments · BNK_MONI's job · Track payment batches after release
SAP Treasury Tables: Where Deals, Flows and Positions Live
- VTBFHA
- The financial transaction itself — contract data for every Transaction Manager product type
- VTBFHAZU
- Activity-level data — contract date (DVTRAB), FX transaction rate (KKURS), swap rate (KSWAP)
- VTBFHAPO
- The flows — SAP's migration documentation calls it the source of "main flow information"
- VTBFINKO
- The conditions of a transaction — interest and repayment terms
- VTBZV
- Payment details
- VTBPA
- Partner assignments — which business partner plays which role on the deal
- FEBKO
- Bank statement header
- FEBEP
- Bank statement item
- FEBRE
- Notes to payee / memo line
- FEBRE_ORIG
- Original notes to payee / memo line
- FEBCL
- Clearing assignment — proposals are stored here
- FEBCL_EXT
- Clearing assignment with machine-learning fields
- BNKA
- Bank master data — SAP's Bank API is "built using CDS views based" on it
- T012
- House banks
- T012K
- House bank accounts
- FCLM_BAM_AMD
- Bank account master data — the S/4HANA Bank Account Management table
- FCLM_BAM_ACLINK2
- Named alongside FCLM_BAM_AMD in SAP's BAM replication configuration
SWIFT MT
8 codesISO 20022
60 codespain.002 Status and Reject Codes: Reading the Bank's Reply
- RCVD
- Payment initiation has been received by the receiving agent.
- ACTC
- Authentication and syntactical and semantical validation are successful.
- ACCP
- Preceding check of technical validation was successful; customer profile check was also successful.
- ACSP
- All preceding checks such as technical validation and customer profile were successful; accepted for execution.
- ACSC
- Settlement on the debtor's account has been completed (group set); settlement completed (transaction set).
- ACCC
- Settlement on the creditor's account has been completed.
- ACWC
- Instruction is accepted but a change will be made, such as date or remittance not sent.
- PART
- A number of transactions have been accepted, whereas another number have not yet achieved 'accepted' status.
- PDNG
- Payment instruction is pending; further checks and status update will be performed.
- RJCT
- Payment instruction has been rejected.
- AC01
- Account number is invalid or missing.
- AC02
- Debtor account number invalid or missing.
- AC03
- Creditor account number invalid or missing.
- AC04
- Account number specified has been closed on the bank of account's books.
- AC06
- Account specified is blocked, prohibiting posting of transactions against it.
- AM01
- Specified message amount is equal to zero.
- AM02
- Specific transaction/message amount is greater than allowed maximum.
- AM04
- Amount of funds available to cover specified message amount is insufficient.
- AM05
- Duplication.
- RC01
- Bank identifier code specified in the message has an incorrect format.
- RC02
- Bank identifier is invalid or missing.
- AGNT
- Agent in the payment workflow is incorrect.
- CNOR
- Creditor bank is not registered under this BIC in the CSM.
- DNOR
- Debtor bank is not registered under this BIC in the CSM.
- FF01
- File format incomplete or invalid.
- DT01
- Invalid date (e.g. wrong or missing settlement date).
- DT02
- Invalid creation date and time in Group Header (e.g. historic date).
- CH03
- Value in Requested Execution Date is too far in the future.
- CH04
- Value in Requested Execution Date is too far in the past.
- TM01
- Message, payment information block or transaction received after agreed processing cut-off time.
- DUPL
- Payment or charge is a duplicate of another payment or charge.
- RF01
- Transaction reference is not unique within the message.
- BE01
- Identification of end customer is not consistent with associated account number.
- BE04
- Specification of creditor's address, required for payment, is missing or not correct.
- MD07
- End customer is deceased.
- RR01
- Regulatory: debtor account or unique identification insufficient or missing.
- RR02
- Regulatory: debtor name and/or address insufficient or missing.
- RR03
- Regulatory: creditor name and/or address insufficient or missing.
- RR04
- Regulatory reason.
- AM07
- Amount specified in message has been blocked by regulatory authorities.
- CURR
- Currency of the payment is incorrect.
- CUST
- Cancellation requested by the Debtor.
- MS02
- Reason has not been specified by end customer.
- MS03
- Reason has not been specified by agent.
- NARR
- Reason is provided as narrative information in the additional reason information.
camt.053 Structure: Reading the Statement Field by Field
- OPBD
- Opening booked — book balance at the start of the reporting period; always equals the previous closing booked balance
- CLBD
- Closing booked — opening booked plus all entries booked in the period
- OPAV
- Opening available — what was at the owner's disposal at the start
- CLAV
- Closing available — what is at the owner's disposal at the end
- ITBD
- Interim booked — calculated during the business day, subject to change
- ITAV
- Interim available — the available equivalent, also intraday
- FWAV
- Forward available — funds at the owner's disposal on a specified future date
- PRCD
- Previously closed booked — the prior period's closing balance, restated
- XPCD
- Expected — booked entries plus known pending items, projecting the end-of-day balance
- INFO
- Informational only
- <MsgId>
- GroupHeader · The bank — unique per message
- <AcctSvcrRef>
- Entry · The bank — its own reference for the booking
- <PmtInfId>
- TransactionDetails · You — the payment-information (debit batch) level of your instruction; batch booking
- <InstrId>
- TransactionDetails · You — your instruction reference; single booking
- <EndToEndId>
- TransactionDetails · You — set in pain.001, carried through the chain
BAI2
20 codesBAI2 File Format: Records, Type Codes and How to Read One
- 001–099
- Account status (balances, float)
- 100
- Total Credits summary
- 101–399
- Credit summary and detail codes
- 400
- Total Debits summary
- 401–699
- Debit summary and detail codes
- 700–799
- Loan summary and detail codes
- 900–999
- Customized, bank-defined codes
- 010
- Opening Ledger · End-of-day and intraday
- 015
- Closing Ledger · End-of-day
- 030
- Current Ledger · Intraday
- 040
- Opening Available · End-of-day and intraday
- 045
- Closing Available · End-of-day
- 060
- Current Available · Intraday
- 063
- Total Float · Where the bank reports float
- 072
- 1-Day Float · With 074 (2+ days) and 075 (3+ days)
- Z
- Unknown (default) · Nothing
- 0, 1, 2
- Whole amount available in 0 / 1 / 2+ days · Nothing
- V
- Value dated · Value date (YYMMDD), then optional value time
- S
- Distributed availability · Three amounts: immediate, one-day, two-or-more-days
- D
- Distributed availability · A count, then that many day/amount pairs
Every entry is read out of the articles above when the site is built, so a correction there is a correction here. Those articles carry the primary sources each code was verified against.