Sei sulla pagina 1di 21

Data Setup Guide PUBLIC

Document version: 1.0 – 2015-01-15

Data Setup Guide for SAP Cash Management


powered by SAP HANA
Document History

Caution
Before you start the implementation, make sure you have the latest version of this document. You can find the
latest version at the following location:service.sap.com/erp-inst.

The following table provides an overview of the most important document changes.

Table 1
Version Date Description

1.0 2015-02-15 Initial version of Data Setup Guide for SAP Cash Management powered by SAP HANA

PUBLIC
© Copyright 2014 SAP SE or an SAP affiliate company. Data Setup Guide for SAP Cash Management powered by SAP HANA
2 All rights reserved. Document History
Content

1 Data Setup for SAP Cash Management powered by SAP HAHA . . . . . . . . . . . . . . . . . . . . . . . . . . 5


1.1 Purpose and Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

2 Data Setup Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6


2.1 Create Bank Account Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
  Bank Account Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
  Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
  Generate Bank Account Master Data from Existing House Bank Accounts . . . . . . . . . . . . . . . . . . . 9
  Import and Export Bank Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
2.2 Set Up Cash Management Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
  Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
  Build Key Information in Accounting Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
  Load Data to the Exposure Hub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3 Integrate with Remote Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

PUBLIC
Data Setup Guide for SAP Cash Management powered by SAP HANA © Copyright 2014 SAP SE or an SAP affiliate company.
Content All rights reserved. 3
PUBLIC
© Copyright 2014 SAP SE or an SAP affiliate company.
4 All rights reserved. Data Setup Guide for SAP Cash Management powered by SAP HANA
1 Data Setup for SAP Cash Management
powered by SAP HAHA

1.1 Purpose and Target Groups

This guide introduces the activities that you need to perform to migrate and set up data before you go live with
SAP Cash Management powered by SAP HANA, as part of the SAP Simple Finance add-on for SAP Business Suite
powered by SAP HANA.

The guide is applicable to the following customers:


● Customers who have been using the classic SAP Cash and Liquidity Management and would like to migrate
relevant master data and transactional data to the new SAP Cash Management powered by SAP HANA.
● Customers who want to migrate cash management relevant information stored in remote systems (either
SAP systems or non-SAP systems) to the SAP Cash Management powered by SAP HANA system.
Table 2
Release SAP Simple Finance add-on 1.0 SPS 03 or higher support
package stacks for SAP Business Suite powered by SAP
HANA

Application Component FIN-FSCM-CLM

Target Groups (Roles) Application Consultants

1.2 Prerequisites

You have fulfilled the following prerequisites before you continue with the activities documented in this guide:
● You have installed SAP ERP 6.0 Enhancement Package 7 SP06 or above, and has upgraded the financials
application component to SAP Simple Finance add-on 1.0 SPS 03 or higher for SAP Business Suite powered
by SAP HANA.

For more information, see the Installation Guide in SAP Library at help.sap.com/sfin100.
● You have finished the migration for SAP Accounting powered by SAP HANA.

For more information, see the Migration Guide in SAP Library at help.sap.com/sfin100.
● You have switched on the business function FIN_FSCM_CLM.
● Make sure you apply all the mentioned notes in SAP Note 2034655 (Release Information Note: SAP Cash
Management powered by SAP HANA) according to your product version.
● Your user is assigned with the PFCG role SAP_SFIN_CASH_MANAGERor a role copied from this role.

PUBLIC
Data Setup Guide for SAP Cash Management powered by SAP HANA © Copyright 2014 SAP SE or an SAP affiliate company.
Data Setup for SAP Cash Management powered by SAP HAHA All rights reserved. 5
2 Data Setup Activities

2.1 Create Bank Account Master Data

2.1.1 Bank Account Master Data

Before you start to use SAP Cash Management powered by SAP HANA, you must set up the bank account master
data. Each bank account master record contains the following attribute categories.

Note
Not all the attributes below are mandatory to bank account master data. You can choose to migrate only
attributes that are essential to your business operation and select the migration tool correspondingly.
Below are the two migration tools available for migrating bank account master data, you can choose to use
either of them or both of them, according to your business needs.

For more information, see:


● Generate Bank Account Master Data from Existing House Bank Accounts [page 9]
● Import and Export Bank Accounts [page 10]

Table 3
Category Details

General Data Common account properties such as bank account number,


IBAN, properties for bank statement import, contact
persons, and so on.

Payment Signatories Payment signatories for approving payments against this


bank account.

Overdraft Limits Overdraft limits for this bank account

Additional Data Additional data such as closing dates, organizational data,


and technical data.

Connectivity Path Linkages between the bank account and the corresponding
house bank account or other account records in either local
or remote systems.

2.1.2 Configurations

Before you migrate cash management data, make sure you have properly configured the following settings:

PUBLIC
© Copyright 2014 SAP SE or an SAP affiliate company. Data Setup Guide for SAP Cash Management powered by SAP HANA
6 All rights reserved. Data Setup Activities
2.1.2.1 Number Ranges for Bank Account Technical IDs

In bank account master data, each bank account is assigned with a technical ID when created. To configure the
technical ID assignment rules, proceed as follows:
1. Define number ranges for bank account technical IDs in SAP Customizing Implementation Guide Financial
Supply Chain Management Cash and Liquidity Management Bank Account Management Basic
Settings Define Number Ranges for Bank Account Technical IDs .
2. Specify a number range for bank account technical IDs in SAP Customizing Implementation Guide
Financial Supply Chain Management Cash and Liquidity Management Bank Account Management Basic
Settings Define Settings for Bank Account Master Data Bank Account Master Data Setting .

2.1.2.2 Banks and House Banks

● Before you migrate bank account master data, maintain banks in your cash management system.
You can either create banks manually in transaction FI01, or use a bank upload tool in SAP Customizing
Implementation Guide Cross-Application Components Bank Directory Bank Directory Data Transfer .
● For bank accounts used by payments, bank statements, or bank transfers locally in the SAP Cash
Management powered by SAP HANA system, their corresponding house bank and house bank accounts
must be configured.
You can use transaction FI12 to maintain the house banks and house bank accounts that you want to
manage locally in your cash management system.

2.1.2.3 Business Partners for Banks

With Bank Account Management, each bank in use must be represented by a business partner instance and with a
linkage maintained between the bank (entry in table BNKA) and the business partner instance. To configure the
business partners for banks, do either of the following:
● If there are already business partners defined for banks in the system, we recommend that you proceed as
follows:
1. Determine the banks to be used in your corporate group and identify their corresponding business
partners defined in the system.
2. Open the view Linkages Between Banks and Business Partners using transaction FCLM_BAM_BNKA_BP.
3. Define the linkages between banks and business partners.
● If there is no business partner defined for banks, we recommend that you define the bank hierarchy first.
After you define the position of a bank in the bank hierarchy, the system automatically creates a business
partner, and establish the linkage between the business partner and the bank.
1. In the SAP NetWeaver Business Client (NWBC) menu, enter PFCG role SAP_SFIN_CASH_MANAGER or the
role copied from it.
2. From the menu, choose Bank Account Management Bank Accounts .
3. In the bank hierarchy view, choose the Edit button.
4. From the list, select a node under which you want to add the bank.

PUBLIC
Data Setup Guide for SAP Cash Management powered by SAP HANA © Copyright 2014 SAP SE or an SAP affiliate company.
Data Setup Activities All rights reserved. 7
5. Choose the Add Existing Bank button and specify the Bank Country and Bank Key of the bank to be
added.

6. After the bank is added to the hierarchy, the system automatically performs the following:
○ Creates a business partner instance for the bank, with bank identification bank country and bank
key.
○ Establishes the linkage between the bank and its business partner.
○ Maintains the business partner relationship according to the position of the bank in the bank
hierarchy.

7. To check the created business partners and the established linkages, check the entries in
transactionFCLM_BAM_BNKA_BP .

2.1.2.4 Business Partners for External Contacts (Optional)

Note
This activity is only required if you plan to import Contact at Bank and Bank Relationship Manager using the
Import and Export Bank Accounts tool.

In the bank account import file, you may maintain the Contact at Bank and Bank Relationship Manager fields. After
the file is imported, the specified contact persons can be assigned to the bank account automatically and also
assigned to the bank's business partner automatically. As the two contact persons are external to the company,
they can only be represented by a business partner instance with the BP Role of BUP001 Contact Person.

To use these two fields for external contacts, you must create business partner for external contacts and
configure the relationship between contact business partners and bank business partners. To do so, choose
either of the following two methods:

Note
Note down the ID of business partners for external contacts. Later when you specify the Contact at Bank and a
Bank Relationship Manager field in the Excel, make sure you use the ID of business partners. • Import business
partners and configure business partner relationship using a Microsoft Excel file.

● Import business partners and configure business partner relationship using a Microsoft Excel file. For more
information on how to use the tool, see SAP Library at help.sap.com/erp600, under SAP ERP SAP
Strategic Enterprise Management Business Consolidation (SEM-BCS) Master Data and Hierarchies
Organizational Unit Consolidation Unit Business Partner Data Uploading Business Partner Data with a
Microsoft Excel File .
● Create business partners manually using the program Maintain Business Partner (transaction BP). To assign
a contact person to a bank, in transaction BP, find the business partner of this bank, and then assign the
business partner that represents the contact person to this bank by using relationship FBUR001 Has Contact
Person.

PUBLIC
© Copyright 2014 SAP SE or an SAP affiliate company. Data Setup Guide for SAP Cash Management powered by SAP HANA
8 All rights reserved. Data Setup Activities
2.1.3 Generate Bank Account Master Data from Existing
House Bank Accounts

If you are upgrading from the classic SAP Cash and Liquidity Management to the new SAP Cash Management
powered by SAP HANA, you are recommended to use this tool to migrate your bank account data from existing
house bank accounts. It enables you to generate bank account master data from house bank accounts with the
most essential business data including:
● Key information such as bank account number, bank key, bank country, and bank name.
● The connectivity between bank accounts and house bank accounts

Procedure

1. To start the program you can either run transaction FCLM_BAM_MIGRATION, or choose from SAP Menu
Accounting Financial Supply Chain Management Cash and Liquidity Management Tools Bank
Account Management From House Bank Account Generate Bank Account Master Data .
2. Select the house bank accounts that you want to use to generate bank accounts and specify a date in the
Opened On field.
3. The generated bank accounts are assigned with the specified date as the account opening date.

Recommendation
We recommend that you check with your business department before you decide which house bank
account to include, in case that some of the house bank accounts in the system are already closed or no
longer active.

4. Execute the program.


5. The system generates bank accounts based on selected house bank accounts. You can check the migration
status by checking the status icon displayed at the end of each house bank account entry:
○ Green
The corresponding bank account master record was successfully created in the system.
To check the migrated bank accounts, in the SAP NetWeaver Business Client (NWBC) menu, choose
Bank Account Management Bank Accounts , and then switch to the Account List view.
○ Red
The bank account master data creation failed.
You can check the migration log for more information. To access the log, from transaction SLG1, choose
object BAM_MIGRATE.
For more information on the program, see the program documentation by choosing the blue Information
button.
6. The following information is not stored with house bank accounts and therefore they cannot be created by
the program automatically. If necessary, in the NWBC application, you can manually maintain the following
attributes for each bank account individually, or use the Import and Export Bank Accounts tool to massively
import data from an XML file:
○ General data: unspecified fields, such as bank statement data, payment data, contact persons, and so
on.
○ Payment signatories

PUBLIC
Data Setup Guide for SAP Cash Management powered by SAP HANA © Copyright 2014 SAP SE or an SAP affiliate company.
Data Setup Activities All rights reserved. 9
○ Overdraft limits
○ Additional data
○ Connectivity path: Linkages to account records in remote systems

2.1.4 Import and Export Bank Accounts

If your bank account data is stored in remote systems, you are recommended to use this tool to migrate your data
from either SAP systems or non-SAP systems to the system where SAP Cash Management powered by SAP
HANA is installed.
With this tool, you can download a template XML file in spreadsheet format, with which you may prepare the bank
account master data and attributes from your remote systems. Once you have finished preparing the file, you
may import it to SAP Cash Management powered by SAP HANA.
The tool helps you migrate the following data:
● General data
● Payment signatories
● Overdraft limits
● Connectivity path
You can build the connectivity between a bank account and a house bank account or other account records
in either the central system or other remote systems,
● Additional data

Prerequisites

● To use the Import and Export Bank Account tool, make sure the following SAP Notes have been applied to
your system:
○ SAP Note 2111290
○ SAP Note 2112418
○ SAP Note 2111363
○ SAP Note 2112375
● You use Microsoft Office 2010 or higher that contains Microsoft Excel.
● To enable the Developer tab in Microsoft Excel, go to File Options Customize Ribbon .
From Customize the Ribbon, select the Developer checkbox and choose OK.
For more information about the tool, refer to the attached user guide in SAP Note 2111290.

Procedure

1. To launch the NetWeaver Business Client, enter transaction code NWBC, and then specify the role
SAP_SFIN_CASH_MANAGER, or the role copied from SAP_SFIN_CASH_MANAGER.
2. From the menu, choose Tool Import and Export Bank Accounts .

PUBLIC
© Copyright 2014 SAP SE or an SAP affiliate company. Data Setup Guide for SAP Cash Management powered by SAP HANA
10 All rights reserved. Data Setup Activities
3. To prepare bank account data to be migrated, download the template by choosing Download XML
Spreadsheet Template.
4. Save and open the file XML_SpreadSheet_Template.xml.
5. The template contains the follow sheets. You may choose to maintain information that is essential to your
business operations either by manual entering data or by copying and pasting data to the corresponding
sheets.
○ General Data
If you want to import data for the following two fields, enter the corresponding business partner IDs.
○ Contact at Bank
○ Bank Relationship Manager
○ Payment Signatories
○ Overdraft Limits
○ Additional Data
○ Connectivity Path
6. Once the source file is ready, specify the import path and then choose Import to transfer the bank account
data contained in the source file to your SAP Cash Management powered by SAP HANA system.

Recommendation
We recommend that you first choose Import with Test Run to simulate the import and check potential
issues.

7. If you encounter errors, select an entry and then choose the Details button to check the details.

2.2 Set Up Cash Management Data

This activity is to set up transactional data that will be used by Cash Management applications. Applications in
SAP Cash Management powered by SAP HANA consumes data from the following sources:
● Imported bank Statements (database tables FEB*) for balances on the bank side
● Accounting document line items (database table BSEG) for cash flows booked in the system
● Memo records (database table FDES)
● Exposure Hub (database table FQM_FLOW) for data from other components like TRM, CML, FI-CA, or
integrated data from remote system.
To use the new SAP Cash Management powered by SAP HANA, perform the following data setup activities:
● Build Key Information in Accounting Documents [page 16] (database table BSEG):
Configure the following attributes so that they can be consumed by Cash Management applications. For
more information, see Configurations.
○ Flow type
○ Flow types classify information from different source components or different steps in the cash flow
lifecycle from forecast to actual.
○ Liquidity item
○ Liquidity items represent the business purpose of the cash flow. Typically with liquidity items and the
defined hierarchical structures, cash flows can be classified into different categories and sub-categories

PUBLIC
Data Setup Guide for SAP Cash Management powered by SAP HANA © Copyright 2014 SAP SE or an SAP affiliate company.
Data Setup Activities All rights reserved. 11
in a hierarchical view, for example, cash flows for operations, cash flows for financing, and cash flows for
investment.
○ Planning level and planning group
The two attributes enable the integration between Cash Management and other components.
○ House bank and house bank account
○ House bank accounts specify the bank accounts used or to be used for payments.
● Load Data to the Exposure Hub [page 17]:
Load data from Treasury and Risk Management (TRM), Loans Management (FS-CML), Contract Accounts
Receivable and Payable (FI-CA), imported bank balances, and remote systems into the Exposure Hub.

2.2.1 Configurations

Before you migrate cash management data, make sure you have properly configured the following settings in
SAP Customizing Implementation Guide Financial Supply Chain Management Cash and Liquidity
Management Cash Management .

2.2.1.1 Source Applications

For company codes that are going to use Cash Management related functions, you need to determine which
information sources are relevant for Cash Management for each company code. To do so, activate source
applications for company codes using either of the following two activities under SAP Customizing
Implementation Guide Financial Supply Chain Management Cash and Liquidity Management Cash
Management Tools :
● Activate Individual Source Applications: Activate a single source application for a company code
● Activate Multiple Source Applications: Activate several source applications for a company
You may need to activate the following source applications
● To build key information in accounting documents, activate source application FI General Ledger.
● To use data of a particular category that stored in the Exposure Hub, activate the corresponding source
application if necessary.
○ CML Customer and Mortgage Loans
○ FICA Contract Accounts Receivable and Payable
○ TRM Treasury and Risk Management

2.2.1.2 Flow Types

Definition
Flow Types classify the lifecycle of cash flows, for example, it distinguishes forecasted cash flows from confirmed
cash flows. Only data assigned with flow types can be consumed and used in Cash Management applications.

PUBLIC
© Copyright 2014 SAP SE or an SAP affiliate company. Data Setup Guide for SAP Cash Management powered by SAP HANA
12 All rights reserved. Data Setup Activities
SAP predefines a set of flow types. If you do not have special requirements, you can rely on the standard flow
types delivered by SAP.
You can view the standard flow types in database table FQMI_FLOW_CAT. The numbers of the flow type IDs
suggest how reliable the associated cash flows are. For example, forecast data are assigned with smaller ID
numbers, while confirmed cash flows are assigned with 90* ID numbers. Different applications consume different
sets of flow types. For instance, Cash Position consumes data with flow types ranging from 70* to 90*, while
Liquidity Forecast consumes data with flow types ranging from 30* to 60*.

Derive Flow Types for Accounting Documents


Flow types in database table BSEG are derived from G/L account values in accounting document line items. The
derivation logic for the following G/L accounts are predefined by SAP. You only need to configure the G/L
accounts according to your business needs.
● G/L accounts representing bank accounts are associated with cash flows that have been confirmed by
banks. They are always assigned with flow type 900000 or 900001 automatically, depending on whether it is
an inflow or outflow.
You define this type of G/L accounts by assigning them to house bank accounts using SAP Customizing
Implementation Guide Financial Accounting (new) Bank Accounting Bank Accounts Define House
Banks .
● G/L accounts representing bank clearing accounts are associated with payments made in the system but not
yet confirmed by banks. They are assigned with flow type 800000 or 800001 automatically, depending on
whether it is an inflow or outflow.
You define bank clearing accounts using SAP Customizing Implementation Guide Financial Accounting
(new) Bank Accounting Business Transactions Payment Transactions Payment Handling Bank
Clearing Account Determination .
● G/L accounts representing clearing accounts for payment requests are associated with payment requests
that are ready for payment run (transaction F111). They are assigned with flow types from 700000 to
700005.
You define payment request clearing accounts using SAP Customizing Implementation Guide Financial
Supply Chain Management Treasury and Risk Management Transaction Manager General Settings
Payment Management Payment Requests Define Clearing Account for Payment Requests .
● G/L accounts representing tax accounts are associated with forecasted tax payments. They are assigned
with flow type 300010 or 300011, depending on whether it is an input tax or output tax.
You define tax accounts for account payable and receivable using SAP Customizing Implementation
Guide Financial Accounting (new) Bank Accounting Business Transactions Outgoing Invoices /
Credit Memos Define Tax Accounts for Outgoing Invoices Bank Clearing Account Determination .
● G/L accounts representing vendor accounts (reconciliation accounts) are assigned with flow type 600001 or
600010.
You define vendor accounts with the account type K – Vendors sing transaction FS00.
● G/L accounts representing customer accounts (reconciliation accounts) are assigned with flow type
600000 or 600011.
You define customer accounts with the account type D – Customers using transaction FS00.

Default Flow Type Assignment


All accounting document items that associated with an account classified as bank account, bank clearing account,
payment request clearing account, vendor, customer, or tax, are assigned with a flow type based on the debit/
credit indicator (table BSEG-SHKZG) as the table below.

PUBLIC
Data Setup Guide for SAP Cash Management powered by SAP HANA © Copyright 2014 SAP SE or an SAP affiliate company.
Data Setup Activities All rights reserved. 13
If the default derivation logic is sufficient for you, no extra configuration is required. However, if you want to
overrule the assignment below or assign flow types to additional G/L accounts, you can do so in SAP
Customizing Implementation Guide Financial Supply Chain Management Cash and Liquidity Management
Cash Management Flow Types Assign Flow Types to G/L Accounts .

Example
You need additional bank clearing accounts for bank transfers.

To do so, configure your clearing accounts using SAP Customizing Implementation Guide Financial
Accounting (new) Bank Accounting Business Transactions Payment Transactions Payment Request
Define Clearing Accts for Receiving Bank for Acct.Transfer, or, Define Clearing Accounts for Cross-Country Bank
Account Transfers .

The system does not assign default flow types to these bank clearing accounts, therefore you need to define
them in SAP Customizing Implementation Guide Financial Supply Chain Management Cash and Liquidity
Management Cash Management Flow Types Assign Flow Types to G/L Accounts

Table 4
Account classified as Debit/credit indicator Flow Type

Bank S 900000

H 900001

Bank Clearing S 800004

H 800003

Payment Request Clearing S 700000

H 700001

Vendor S 600001

H 600010

Customer S 600000

H 600011

Tax (output tax; BSEG-MWART = ‘A’) S 300010

H 300001

Tax (input tax; BSEG-MWART = ‘V’) S 300000

H 300011

Flow Types in the Exposure Hub

The Flow Type field in the Exposure Hub (database table FQM_FLOW) is derived according to fixed logic in the
program. The table below lists the default assignment
If the default derivation logic is sufficient for you, no extra configuration is required. However, if you want to
overrule the assignment below, you can do so using SAP Customizing Implementation Guide Financial Supply
Chain Management Cash and Liquidity Management Cash Management Flow Types Assign Flow Types to
G/L Accounts .

PUBLIC
© Copyright 2014 SAP SE or an SAP affiliate company. Data Setup Guide for SAP Cash Management powered by SAP HANA
14 All rights reserved. Data Setup Activities
Table 5
Data in Exposure Hub Flow Type

Treasury and Risk Management (TRM) 900100, 900101

Loans Management (FS-CML) 900104, 900105

Contract Accounts Receivable and Payable (FICA) 900106, 900107

Classic Cash Management data from remote system 900108, 900109, 900110, 900111

Classic Liquidity Planner data from remote system 900112, 900113

Uploaded Bank Account Balance 900102, 900103

2.2.1.3 Liquidity Items and Liquidity Item Hierarchies

Liquidity items represent the source and use of cash flows in your company. It serves as an import dimension for
financial planning and reporting in SAP Cash Management powered by SAP HANA. Configure the following under
SAP Customizing Implementation Guide Financial Supply Chain Management Cash and Liquidity
Management Cash Management Liquidity Items .

Define Liquidity Items and Liquidity Item Hierarchies


● To define liquidity items, use the Edit Liquidity Items activity.
● To group liquidity items into hierarchical structures, define hierarchies using the Define Liquidity Item
Hierarchies activity.
The hierarchies defined here can be used by Cash Management applications to display cash flows in
categories and sub-categories in a hierarchical view.

Derive Liquidity Items for Accounting Documents


● For accounting documents (in database table BSEG), if Liquidity Item can be determined by G/L accounts,
you may use the Define Default Liquidity Items for G/L Accounts activity to define the derivation rules.
● If you need more complex logic to derive liquidity items from various fields of the accounting document, then
you need to define queries and query sequences using the following activities:
○ Define Queries for Liquidity Item Derivation
○ Define Query Sequences
○ Assign Queries to Query Sequences
You should always specify the OriginasD (invoices) or C (other types of accounting documents) when
defining queries and query sequences, as the Origin D or C are applied to accounting document line
items. When deriving liquidity items, the system first tries to apply the assigned query sequences; if not
successful, then it turns to the default liquidity items defined for G/L accounts.

Derive Liquidity Items for Data in the Exposure Hub Integrated Locally
For data integrated into the Exposure Hub from local TRM, CML, or FI-CA data, there is no default derivation rules
for liquidity items. You need to define query and query sequences for this purpose. In this case, you should always
specify the Origin as X, meaning that the derivation logic is executed against the structure of the Exposure Hub.

PUBLIC
Data Setup Guide for SAP Cash Management powered by SAP HANA © Copyright 2014 SAP SE or an SAP affiliate company.
Data Setup Activities All rights reserved. 15
Derive Liquidity Items for Data in the Exposure Hub Integrated Remotely
Data integrated from remote systems falls into the following types:
● Classic Cash Management data from remote systems: Define queries and query sequences with the Origin as
X.
● Classic Liquidity Planner data from remote systems: You can either choose to define queries and query
sequences with the Origin as X, or keep the original Liquidity Item field values in the source data
● Uploaded bank account balance: Liquidity items do not apply to this case.

2.2.1.4 Planning Levels and Planning Groups

The planning level reflects typical financial transactions, for example, posting to a bank account, posting to a
clearing account, confirmed or unconfirmed payment notes, and so on. It explains the origin of the data and thus
enables you to better estimate its reliability. A planning group represents a group of customers or vendors with
particular characteristics, behaviors or risks. With this attribute, you can break down incoming and outgoing
payments according to the amount, the probability of the cash inflow or outflow, and the type of business
relationship.
Before you use SAP Cash Management powered by SAP HANA, configure planning levels and planning groups
under Cash Management Planning Levels and Planning Groups.
Note the following:
● To populate key information for cash management in accounting entries for G/L line items, assign planning
levels to relevant G/L account, for example bank G/L Accounts, bank clearing G/L Accounts, payment
request G/L Accounts.
● To populate key information for cash management in accounting entries for vendor and customer line items,
in customer and vendor master records, specify the planning group information.
● To populate planning level information for Treasury deals in Exposure Hub, assign planning levels for
company code and product type in SAP Customizing Implementation Guide Financial Supply Chain
Management Treasury and Risk Management Transaction Manager General Settings Link to Cash
Management/Assign Planning Levels .

2.2.1.5 House Bank Accounts

By default, house bank and house bank account are optional fields in payments and bank statements. To ensure
the information is recorded for relevant transactions, you may consider to set the two fields as mandatory for G/L
accounts that work as bank clearing accounts and bank accounts by using SAP Customizing Implementation
Guide Financial Accounting (New) Accounts Receivable and Accounts Payable Business Transactions
Incoming Payments Incoming Payments Global Settings Make and Check Document Settings .

2.2.2 Build Key Information in Accounting Documents

Data such as liquidity items, flow types, house banks, and house bank accounts are key to the calculation of Cash
Management. To build key information in account documents, perform the following activities under SAP

PUBLIC
© Copyright 2014 SAP SE or an SAP affiliate company. Data Setup Guide for SAP Cash Management powered by SAP HANA
16 All rights reserved. Data Setup Activities
Customizing Implementation Guide Financial Supply Chain Management Cash and Liquidity Management
Cash Management Tools :
● Rebuild Flow Types in Table BSEG
● Rebuild Liquidity Items in Table BSEG
● Insert House Bank and House Bank Account Data to Table BSEG
● Prepare Production Setup and Data Setup

This activity is to populate attributes or attribute changes to customers and vendors master data in one shot.
With the Data Setup function, you can rebuild the Planning Level and Planning Group fields in database table
BSEG. When you change the assignment of planning levels to G/L accounts, or the assignment of planning
groups to customers or vendors, you can execute the Data Setup function to fill in the updated planning level
and planning group information into the existing BSEG records.

2.2.3 Load Data to the Exposure Hub

The Exposure Hub is a real-time collection point and storage location for operational data that is relevant for
managing cash and liquidity. The provision of the data in the Exposure Hub facilitates funds planning and risk
management across multiple companies. Currently, SAP Cash Management powered by SAP HANA uses the
Exposure Hub to acquire the following data:
● Treasury and Risk Management (TRM)
● Loans Management (FS-CML)
● Contract Accounts Receivable and Payable (FI-CA)
● Bank account balances uploaded via Excel
● Data of classic SAP Cash and Liquidity Management from remote systems imported via iDoc
To configure the integration with the Exposure Hub, preform the Customizing activities in the table below.

For more information, refer to the corresponding SAP Customizing Implementation Guide documentation.
Table 6
Usage Customizing Activities

Load Transaction Data from Source applications into the SAP Customizing Implementation Guide Financial Supply
Exposure Hub Chain Management Cash and Liquidity Management
Cash Management Tools Load Transaction Data to Table
FQM_FLOW

Configure the Integration of Data from Remote Systems into Activities under SAP Customizing Implementation Guide
the Exposure Hub Financial Supply Chain Management Cash and Liquidity
Management Cash Management Tools Distributed
Note Cash Management F>
These activities are only relevant for customers who want
to use data from remote systems and have adopted the
side-by-side landscape in deployment.

PUBLIC
Data Setup Guide for SAP Cash Management powered by SAP HANA © Copyright 2014 SAP SE or an SAP affiliate company.
Data Setup Activities All rights reserved. 17
2.3 Integrate with Remote Systems

The following data in remote systems that can be consumed by SAP Cash Management powered by SAP HANA
using the Exposure Hub.
● Bank account balances uploaded via Excel
To access the tool , launch transaction FQM21, or from the SAP Easy Access Menu, choose Accounting
Financial Supply Chain Management Cash and Liquidity Management Tools Exposure Hub - Import
Bank Cash Balances .
● Data of classic SAP Cash and Liquidity Management from remote systems imported via iDoc
To access the tools, from the SAP Easy Access menu, choose Accounting Financial Supply Chain
Management Cash and Liquidity Management Tools Distribution .
To enable the Exposure Hub to retrieve bank account balances and data of classic SAP Cash and Liquidity
Management from remote systems, configure the following under SAP Customizing Implementation Guide
Financial Supply Chain Management Cash and Liquidity Management Cash Management :
● To enable the integration with remote systems, configure the activities under Cash Management Tools
Distributed Cash Management .
● To define liquidity item derivation rules, configure queries and query sequences accordingly under Cash
Management Liquidity Items .
○ For Classic Cash Management data from remote system, define queries and query sequences with the
Origin as X.
○ For Classic Liquidity Planner data from remote systems, you can either choose to define queries and
query sequences with the Origin as X, or keep the original Liquidity Item field values in the source data.
● When uploading bank cash balances into the Exposure Hub, only flow types are assigned to the transactions
generated. If you want to differentiate according to planning level as well when evaluating a cash position, you
have to assign the relevant planning levels to the flow types in Flow Types Assign Planning Levels to Flow
Types .
● When uploading data from classic SAP Cash and Liquidity Management in a remote system to the Exposure
Hub in the local system, the uploaded data is assigned with flow type information. If you want to differentiate
according to planning level as well when evaluating a cash position, assign the flow types to planning levels
that represent confirmed cash in Flow Types Assign Flow Types to Planning Levels .

PUBLIC
© Copyright 2014 SAP SE or an SAP affiliate company. Data Setup Guide for SAP Cash Management powered by SAP HANA
18 All rights reserved. Data Setup Activities
Typographic Conventions

Table 7
Example Description

<Example> Angle brackets indicate that you replace these words or characters with appropriate entries
to make entries in the system, for example, “Enter your <User Name>”.

Example Example Arrows separating the parts of a navigation path, for example, menu options

Example Emphasized words or expressions

Example Words or characters that you enter in the system exactly as they appear in the
documentation

www.sap.com Textual cross-references to an internet address

/example Quicklinks added to the internet address of a homepage to enable quick access to specific
content on the Web

123456 Hyperlink to an SAP Note, for example, SAP Note 123456

Example ● Words or characters quoted from the screen. These include field labels, screen titles,
pushbutton labels, menu names, and menu options.
● Cross-references to other documentation or published works

Example ● Output on the screen following a user action, for example, messages
● Source code or syntax quoted directly from a program
● File and directory names and their paths, names of variables and parameters, and
names of installation, upgrade, and database tools

EXAMPLE Technical names of system objects. These include report names, program names,
transaction codes, database table names, and key concepts of a programming language
when they are surrounded by body text, for example, SELECT and INCLUDE

EXAMPLE Keys on the keyboard

PUBLIC
Data Setup Guide for SAP Cash Management powered by SAP HANA © Copyright 2014 SAP SE or an SAP affiliate company.
Typographic Conventions All rights reserved. 19
PUBLIC
© Copyright 2014 SAP SE or an SAP affiliate company.
20 All rights reserved. Data Setup Guide for SAP Cash Management powered by SAP HANA
www.sap.com

© Copyright 2014 SAP SE or an SAP affiliate company. All rights


reserved.
No part of this publication may be reproduced or transmitted in any
form or for any purpose without the express permission of SAP SE
or an SAP affiliate company.
SAP and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks
of SAP SE (or an SAP affiliate company) in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/
index.epx#trademark for additional trademark information and
notices.
Some software products marketed by SAP SE and its distributors
contain proprietary software components of other software
vendors. National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company
for informational purposes only, without representation or warranty
of any kind, and SAP SE or its affiliated companies shall not be liable
for errors or omissions with respect to the materials. The only
warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty
statements accompanying such products and services, if any.
Nothing herein should be construed as constituting an additional
warranty.
In particular, SAP SE or its affiliated companies have no obligation to
pursue any course of business outlined in this document or any
related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and
SAP SE's or its affiliated companies' strategy and possible future
developments, products, and/or platform directions and
functionality are all subject to change and may be changed by SAP
SE or its affiliated companies at any time for any reason without
notice. The information in this document is not a commitment,
promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various
risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak
only as of their dates, and they should not be relied upon in making
purchasing decisions.