In going through our SAP Treasury Management Workstation implementation project we’re building a list of important Treasury Management T-codes. I’m putting these down so I don’t forget them, so this isn’t a how-to (maybe later 😉 ):
FF.5 – Upload Electronic Bank Statements
Use FF.5 to upload electronic bank statements. You can upload your Prior Day and Current Day statements here.
FF.6 – View Bank Statements
Use FF.6 to view bank statements.
FF6B – Memo Records: List
This allows you to view and to “Convert” or archive off the memo records that are not set to automically archive off.
FF7A – Cash Management and Forecast
Use FF7A to run your Cash Position or Liquidity Forecast reports. From within these, you can Create Memo records. Click the Create “Single Record” button.
FF67 – Process Manual Bank Statements
Use FF67 to process Manual bank Statements. Click the Overview button to show a list of your accounts, and you can drill in to see the statements.
FEBAN, FEBA_LOCKBOX, FEBA_BANK_STATEMENT – Bank Statement Post-Processing
Use FEBAN for Post-processing of bank statements (FEBA_LOCKBOX and FEBA_BANK_STATEMENT are t-codes specific to either Lockboxes or regular Bank Statements). This allows you to make GL account or other corrections and post the transactions that didn’t go through on the initial upload. On the initial selection screen, you can just skip the selections and it will show you a tree of your House Bank IDs and it will mark entries that didn’t post with the Red dot icon .
SE38 – program RFEBKA40 – Post Memo Records
This will post memo records of your current day statements (you upload them through FF.5) so that they will show up in your Cash Position and Liquidity Forecast reports.
SE38 – program RFEBKA96 – Delete Bank Statements
Use RFEBKA96 to delete Bank Statements! Be very careful! This only deletes the statements, not the GL postings (you’ll have to reverse those some other way like in FB03 or FB08). You don’t have to enter anything into the selection screen. Once you’re in, click the Delselect All. Then manually (check the checkbox) select the statement(s) you want to delete.
OT83 – Configuration t-code for BAI codes, Account Symbols, and Assigning Bank Accounts
There are several functions under OT83. Here you create Account symbols and assign them to GL accounts. The functions also include Creating Posting Rules and posting Keys and assigning External Transaction Codes (BAI codes).
FI12 (also see FBZP) – Configure House Banks and Bank Accounts
The primary t-code for creating House Banks and their Bank Accounts. Here, they are assigned to Company Codes, GL Accounts, currency, etc.
FBZP – Payment Program Customizing
FBZP provides access to configuring:
- Company Codes
- Paying Company Codes
- Payment Methods in Country
- Payment Methods in Company Codes
- Bank Determination
- House Banks
DMEE – Payment Medium Workbench (PMW)
One of the requirements for Outbound bank payments is that you provide data in their specified file formats. While US Banks use the Fedwire network for wire transactions, they tend to have their own file formats. The DMEE Engine or Payment Medium Workbench allows you to configure custom file formats for these types of transactions. The PMW is accessed through t-code DMEE.
FDFD – Cash Management Implementation Tool
FDFD is a tool to help implement Cash Management and Forecasting. The 5 areas it touches are:
- Activate Company Code
- Vendor/Customer data
- Data Setup
- Data Reconciliation
- Data Correction
Take a look at the Application Help for further details.
TBB1 – Treasury: Post Flows
Generates financial accounting transaction from various financial instruments – FX, Money Market, Derivatives, Securities. This would be where a payment of a long term debt would get placed into your Payment Requests GL Account, which would get picked up in your F111 payment runs.
FIBLAPOP – Vendors – Payment Request
If you want to make a Fedwire payment to a vendor, you can use FIBLAPOP to create the Payment Request. You will need to have the Bank information set up on the Vendor Master. (Note: it is a good idea to have the bank info on the vendor master configured as sensitive fields for security and control purposes.) This generates a payment request similar to what FRFT does…see below.
FRFT – Rapid Entry with Repetitive Code
Create Fedwire payments with repetitive codes. You can optionally set up Repetitive Codes with your banks or use them internally with SAP. These identify the payment information for specific payees. You will be able to change the amounts and instructions at the time you create the payments. Having the Repetitive codes provides significant controls you have around the business partners that are eligible to receive wire payments.
Creates payment requests based on the entries in the a Payment Request GL account that you would specify in your Parameter definition.
F111 – Automatic Payment Transaction for Payment Requests
Creates payments based on the entries in the a Payment Request GL account that you would specify in your Parameter definition. You would first create a Payment Request through t-code FRFT (using Repetitive codes) or RVND (free form payment requests), but due to controls issues, FRFT and repetitive codes are recommended.
s_p99_41000099 – Payment List
The Payment List report (s_p99_41000099) will show the details for an F110 Check or ACH Payment run. Enter the run date and the Identification and it shows the vendors and invoices that make up the proposal list for the specified proposal run.
FCHN – Check Register
FCHN will display the checks for a Payment Run.
Note: to view the checks online (as they would look in the print out), you can (if you have rights to view them) go to System > Own Spool Requests, and then look for the spool files that say something like “Accounts Payable Checks…”. You may not have access to this in Production (but you might). Also, this only lets you see spool requests you created.
FCKR – Cashed Checks
FCKR (program RFEBCK00) allows you to upload file containing Cashed Checks. These files may be called Check Encashment files or Check Reconciliation files. You can post these to the GL to clear your outstanding checks account. You can also generate a test file using program RFEBCKT0, but I’ve had trouble getting it to upload :-(.
S_P99_41000099 – Payment List
Shows all payments, not just checks like FCHN does.
BD87 – View IDocs
While BD87 is not exactly a Treasury T-code, it does allow you to view IDocs and can be used in helping you to run down problems with your ACH (EDI) payments. Our IDoc payments have a Message Type of “PAYEXT”, so we can search on that message type for the day and see all of our payment IDocs. A status code of 16 means you sent and got back a confirmation.
Bonus – Tables for payment methods on vendor: LFB1
- SE16 and table LFB1 – gives you vendor data with Payment Methods
- Table LFA1 – gives you vendor name and address information
Hope that helps,