FF7A — Cash Position (Classic Cash Management)
FF7A displays the cash position in classic SAP Cash Management: balances on bank accounts and bank clearing accounts plus expected short-term flows, grouped by date, account and currency. Treasury uses it to decide daily funding, sweeps and short-term investments. In S/4HANA, SAP Cash Management provides Fiori apps for the cash position instead.
Shows short-term cash per bank account and currency from posted bank balances and expected flows in classic Cash Management.
Published 31 Oct 2026· 475 words
What FF7A is for
Treasury needs to know each morning how much cash is available on which account and what will move in the next days. The cash position combines posted bank balances with planning-relevant items such as payment advices and cleared amounts not yet on the statement, grouped into planning levels, so the treasurer can see shortfalls and surpluses by account.
When it is used
It is used daily by treasury and cash managers in companies running classic Cash Management on ECC, especially before deciding transfers between accounts, cash pooling sweeps or short-term borrowing. It is also used to check that bank statements were imported and that planning levels are assigned correctly.
How it is used in practice
Select the company code, grouping and display date, choose the display in days or weeks and the currency. Drill down from groupings to accounts and to individual items. Planned items can be created as payment advices to reflect expected flows. Results depend on planning levels assigned in the GL account and vendor or customer master data.
Fields and objects that matter
- Company code, grouping and display date
- Planning levels and planning groups that classify flows
- Bank accounts and bank clearing accounts included in the grouping
- Payment advices for manually planned items
- Display currency and the choice of days or weeks for the columns
How to prove it in the data
Compare the opening balance for a bank account in FF7A with the GL bank account balance in FAGLB03 and with the last imported bank statement. Differences usually come from unposted statements or missing planning level assignments. Each planning level total should be traceable to its source items by drill-down.
ECC vs S/4HANA
In S/4HANA, SAP Cash Management uses Fiori apps such as Cash Position, based on a common flow table and liquidity items. Classic FF7A and FF7B are associated with the ECC Cash Management; check your release and licensing before relying on them.
Common pitfalls and how they show up
The cash position is only as accurate as the master data behind it.
- GL accounts without planning levels, so balances are missing
- Bank statements not imported before the review
- Old payment advices never archived, inflating expected flows
- Comparing it with the liquidity forecast without understanding the different horizons
Whose problem this is
Treasury and cash management own the report and the planning level setup. Accounts payable and receivable own the data that feeds it, and the bank accounting team owns the timely import of bank statements, without which the morning cash position is incomplete.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Learn this properly
Lessons and topics
Source: ERPClimb — https://erpclimb.com/sap-tcodes/ff7aERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.