Many existing SAP customers will be migrating from the “classic” cash management in SAP ERP to the new Cash Management in SAP S/4HANA (full scope).

This blog describes migration and data conversion activities for this process and building Liquidity Planner data and cash flow data in One Exposure from Operations.

However even if “classic” cash management in SAP ERP was not active, activation of Cash Management – BAM lite scope is needed. Subsequently migrating bank and bank account master data is required.

SAP S/4HANA Cash Management got a new design and more functionalities

The New Cash Management in SAP S/4HANA was significantly redesigned then compared to “classic” Cash Management. It offers better user experience (FIORI based) and more features.

Once customer have installed SAP S/4HANA, SAP S/4HANA Finance for cash management is the only compatible cash management product to be used. The classic Cash and Liquidity Management (Cash Management and Liquidity Planner) is not officially available in SAP S/4HANA. An SAP Business Suite customer using classic Cash and Liquidity Management needs to activate the new SAP S/4HANA Finance for cash management after converting to SAP S/4HANA (note 2270400).

Also, customers which previously didn’t use the “classic” cash management will have to start using the Bank Account master data functionality (now part of Cash Management – BAM lite scope).

SAP’s treasury and cash management applications are integral parts of the SAP S/4HANA digital core. The treasury and cash management components in SAP S/4HANA provide complete, straight-through processing capabilities for operational tasks such as trading, confirmation, payments, and bank statements. They allow the complete control of the end-to-end processes from cash and liquidity management to transaction.

Two deployment options for the new cash management

There are different deployment options for SAP Cash Management powered by SAP HANA (Q1.2020):

  • Side-by-side (aka sidecar) One of these landscapes should be selected if the operating modules (Financial Accounting [FI], materials management [MM], sales and distribution [SD], and Project System [PS]) remain on ECC, and only the SAP Cash Management and SAP Treasury and Risk Management functionalities are running on SAP S/4HANA.
  • Integrated SAP Cash Management solution running on S/4 HANA

In this blog we assume that the integrated Cash Management solution is used.

Regardless of your decision to implement Cash Management in SAP S/4HANA, you will need to use at least the basic functions for banks, house banks, and house bank accounts provided by the basic version called as BAM Lite. You may want to use this opportunity to review/cleanse your bank master data.

Transaction FI12 for maintaining house bank data were disabled and customer should use SAP Fiori app — Manage Bank Accounts:

Datavard Transaction FI12

Another option in case Fiori App is not available is NWBC – Web dynpro transactions (see note 2424544).

Bank account transformation

These steps are applicable for almost all SAP customers, which use Finance (S/4HANA with BAM – lite solution). During S/4HANA conversion original ECC tables T012K/T012T become compatibility views and they are redirected to the new data model which is using new FCLM* tables:

Datavard Transition Dictonary
  • FCLM_BAM_AMD – bank account master data
  • FCLM_BAM_AMD_CUR – banks vs. currency
  • FCLM_BAM_AMD_T – description
  • FCLM_BAM_ACLINK2 – Linkages Between Bank Account and House Bank Accounts
  • FCLM_BAM_AC_LINK – Linkages Between House Bank Accounts and Bank Accounts
  • FCLM_BAM_REQACNT – revisions

Table conversion into the new data model is done by report FCLM_BAM_MIGRATION_REPORT (without conversion House Bank account related processes are disabled)

Datavard Housebank Account

Cash Management and Liquidity planner data transformation

Steps described below are relevant for Customers which previously used Cash Management and Liquidity Planner and decided to use the full scope of Cash Management in S/4HANA.

Simplification Item check reports /SDF/RC_START_CHECK indicates use of classic Cash Management in the source system (ECC):

Datavard Simplification

If the indicator for Cash Management is active for the active company codes, we recommend checking the following manually:

Check the table entries in one of the following tables: FDM1, FDM2, FDMV, FDS1, FDS2, FDSB, FDSB2, FDSBDIST, FDSP, FDSR, FDSR2, FDSRDIST, FDT1, FDW1, FDD1, FDES, FDESDIST, FDFIEP, FDI1, FDLF, FDLF2, FDRE. If you find any entries, it means classic Cash Management is used.

Check the table entries in the tables: FLQSUM and FLQSUM_FC. If you find any entries, it means Liquidity Planner is used.

If classic Cash Management and Liquidity Planner were used, you need to reimplement the new SAP S/4HANA Finance for cash management. Only following part of configuration can be reused:

  • Planning level and planning group configurations
  • Memo record settings (manual planning)
  • Grouping definition and settings
  • Settings for distributed cash management

It is not subject of this blog to advise how Cash Management with full scope is configured. We will assume the configuration is done and tested and customer naturally plans to migrate cash management data from the classic Cash Management.

Target data model

One Exposure is a central data structure of all transaction data that has an impact on financial exposure. All external data is stored in a database table with a time stamp and an identifier. One Exposure integrates data from different applications and modules even in a distributed system landscape.

The technical name of One Exposure is Financial Quantity Management (FQM). The underlying table for One Exposure is FQM_FLOW and it replaces classic Cash Management (FD*) and classic Liquidity Planner (FLQ*) tables. The Memo record table (FDES) is still in use.

To build or rebuild Cash Management, SAP has developed a number of tools that you need run to build your cash management data step by step based on operative data (FI postings, Banks Statements, FI-CA documents, Purchase Orders etc.). There is no direct migration procedure from classic Cash Management to Cash Management on S/4HANA.

Transaction with possible enhancements for rebuilding Cash Management in new Data Model can be found in the spro menu – Financial Supply Chain Management -> Cash and Liquidity Management -> Cash Management-> Data setup:

Datavard CashManagement

Transaction FQM_UPD_HBK_HKT – rebuild house bank and house bank account data for accounting documents. If you want to use historical cash management data in the Cash Management applications, you need to execute this program first to insert house bank (field HBKID) and house bank account (field HKTID).

Transaction FDFD  – Rebuild Planning Levels, Groups, Dates in Accounting Documents. You can use this Customizing activity to:

  • Enter planning groups into customer and vendor master records
  • Data setup for table BSEG
  • Check Cash Management Customizing

Transaction FQM_UPD_LITEM as initial load – rebuild liquidity items for accounting document. In this activity, you can derive liquidity items for line items that are already posted to ledgers but are missing or contain incorrect liquidity items.

Transaction FQM_UPD_ FLOW_TYPE – rebuild flow types for accounting document have already been posted without or with incorrect flow types.

You can load transaction data from different source applications into One Exposure from Operations using Transaction FQM_INITIALIZE. If selective migration to S/4HANA is done for FI documents, FI-CA etc. it is important to consider if Cash Management related fields (planning level, flow types, liquidity items etc. ) are filled correctly e.g. BSEG. Process of rebuilding FQM_FLOW – tr. FCLM_FLOW_BUILDER can be repeated until Cash Management reports are reconciled.

Post go-live validation

You will need to validate the results from the New Cash Management in SAP S/4HANA against the results got from the classic Cash Management reports such as Transaction FF7A and Transaction FF7B as well as validate the actual cash flows from the Liquidity Planner.

There is big dependency on how other financial but also non-financial data were migrated to S/4HANA system.