Skip to Content

Simplified DB Tables in SAP S/4HANA for Cash Management

In classic Cash and Liquidity Management (Cash Management solution in ECC), there are two relatively isolated solution, i.e. Cash Management and Liquidity Planner, both of which have own database tables, details as followings:

For Cash Management (we can find all tables in package FF), here are main tables:

FDSB CMF Totals Records for G/L Accounts

FDSB2 CMF Totals Records for G/L Accounts (As of Release 604)

FDSR CMF Totals Records for Planning Groups

FDSR2 CMF Totals Records for Planning Groups (As of Release 604)

FDES Cash Management and Forecast: Memo Records

FDFIEP CM: FI Line Items (OP of Deb/Cred for Drilldown)

FDM1 Cash Management & Forecast: Line Items of MM Documents

FDM2 Cash management line items from MM purchase requisition

FDS1 Cash Management & Forecast: Line Items of SD Documents

FDS2 CM&F Line Items in SD Documents (fromr Release 4.0)

FDMV Cash Planning Line Items of Earmarked Funds (*)

FDRE Cash Management Line Items from RE-FX (Real Estate) (*)

FDT1 CMF Line Items for Forex, Money Market, Derivatives

FDW1 Cash Mgt and Forecast – Securities Line Items- Planned Flows

For Liquidity Planner (we can find all tables in package FFLQ), here are main tables:

FLQSUM Liquidity Calculation – Totals Records

FLQITEMBS Liquidity Calculation – Line Items for Bank Statement Docs

FLQITEMFI Liquidity Calculation – Line Items for Other FI Documents

FLQSUM_FC Liquidity Calculation – Forecast Totals Records

FLQITEMD1_FC Liquidity Calculation: Forecast Line Items from Loans

FLQITEMFI_FC Liquidity Calculation – Forecast Line Items for FI Documents

FLQITEMMMPARK_FC Liquidity Calculation – Forecast Line Items for MM Documents (*)

FLQITEMPARK_FC Liquidity Calculation – Forecast Line Items for FI Documents (*)

FLQITEMPO_FC Liquidity Calculation – Forecast Line Items for MM POs

FLQITEMPR_FC Liquidity Calc. Forecast – Line Items, Purchase Requisitions

FLQITEMSO_FC Liquidity Calculation-Forecast Line Items from Sales Orders

FLQITEMT1_FC Liquidity Calculation: Forecast Line Items from TR Trans

The major difference between cash management and liquidity planner from business point of view is focusing on different analysis dimensions that cash management is for planning level/planning group analysis and focus on future forecast, while liquidity planner is for liquidity item analysis and focus on the historical actual cash flows.

In new cash management (SAP S/4HANA for Cash Management), besides tables for Bank Account Management, there are only two tables: FQM_FLOW (aka, One Exposure) + FDES (Memo Records, the same as in classic cash management) are in use for cash management applications, for example, cash position analysis, liquidity forecast analysis and actual cash flow analysis. The exceptional case is for FF7AN/FF7BN, which consumes data from FQM_FLOW for all business process data which have been integrated in One Exposure + classic cash tables FD* for processes not yet in One Exposure.

For example, if there is one FI document on bank G/L account, to integrate information in classic Cash and Liquidity Management, there are flows in both FDSB (+FDFIEP) and FLQSUM (+FLQITEMFI) to serve different reports/analysis in each area. While in new cash management, there is only one entry in FQM_FLOW, including both liquidity item and planning level/planning group information, can serve both cash position analysis (on planning level/planning group) and actual cash flow analysis (on liquidity item). And you can also find that there is no separated table for line item and totals comparing with classic cash.

The advantages of new design:

1.       Save database memory, which is precious for SAP HANA

2.       All analysis and reports based on line items offer more flexibility

3.       No need to reconcile line item and totals any longer

For A Glance of Cash Management in SAP S/4HANA, please refer to:

You must be Logged on to comment or reply to a post.
  • How are currency exchange rates handles. In the old SAP architecture table TCURR contained exchange rates for exchagne rate types, the currency pair combination and validity date, which could be feed with an interface. The exchange rates are stored in TCURR in a fixed numerical format 4 places before the decimal point and 5 behind the decimal point, limiting currency paris that have exchange rates that are greater than this for example in an african context. Has this limiation been overcome with S4HANA?

    • Hello, Dina-Vera:

      Sorry, I am not sure about this, this is not area for cash management. But I know we are still using the same mechanism to get valid exchange rate in cash management. Have you raised the issue/limitation to SAP via incident?

      BR, Lawrence

  • Hello Lawrence,

    As cash position details app is consuming database tables: FEBKO/FEBEP (bank statements), BSEG, FDES (memo records), and FQM_FLOW (one Exposure) , FF7AN/FF7BN use table FDES (memo records), and FQM_FLOW (one Exposure),  does this means FEBKO/FEBEP (bank statements) will not displayed in FF7AN/FF7BN?  Is caused due to system design , are there any other reason?


    • Hello, Naoya:

      Cash Position Details consumes FEB* only in SFIN2.0, which is because that we haven't integrated bank statement in that version. And yes, FF7AN doesn't consume bank statement, this will cause inconsistency if there are bank statement items which are not yet posted.

      Since SFIN3.0, bank statement is integrated to FQM_FLOW, and both cash position and FF7AN get the same set of data from FQM_FLOW.


      BR, Lawrence