0% found this document useful (0 votes)

107 views

Cash Flow 1

Uploaded by

7thk99nhgv

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

107 views

Cash Flow 1

Uploaded by

7thk99nhgv

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 168

2/24/2024

Cash and Liquidity Management

Generated on: 2024-02-24 12:33:34 GMT+0000

SAP S/4HANA | 1709 FPS02 (May 2018)

PUBLIC

Original content: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/ac319d8fa4ea4624b40a58d23e3c4627?locale=en-US&state=PRODUCTION&version=1709 002

Warning

This document has been generated from the SAP Help Portal and is an incomplete version of the oﬃcial SAP product documentation. The information included in custom
documentation may not re ect the arrangement of topics in the SAP Help Portal, and may be missing important aspects and/or correlations to other topics. For this reason, it is not
for productive use.

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
2/24/2024

Cash and Liquidity Management

Generated on: 2024-02-24 12:36:26 GMT+0000

SAP S/4HANA | 1709 FPS02 (May 2018)

PUBLIC

Original content: https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/ac319d8fa4ea4624b40a58d23e3c4627?locale=en-US&state=PRODUCTION&version=1709 002

Warning

For more information, please visit the https://help.sap.com/docs/disclaimer.

This is custom documentation. For more information, please visit the SAP Help Portal 1
2/24/2024

Cash and Liquidity Management

Use
Cash and Liquidity Management enables an organization’s cash or treasury department to manage bank accounts centrally, overview the cash operations and long-term liquidity
trends accurately and precisely. Cash managers can easily and intuitively get a high-level overview and detailed insights into bank accounts, cash position, and cash ows, which
enables them to make decisions and take actions directly. The major features are listed below.

 Note
This solution is intended for business use only. You should not use it for personal bank accounts or personal cash operations.

Bank Relationship Management

Bank Relationship Management allows you to manage your bank account master data centrally, using a process to govern the opening, closing, changing, and reviewing of
bank accounts. The streamlined work ow and dual control processes also help improve user eﬃciency in accomplishing compliance-related tasks.

Cash Operations

Cash Operations allows you to review the cash position to understand cash distribution, to establish whether bank accounts have suﬃcient funding (or a surplus) for the day’s
payment obligations, and to decide whether to invest available cash in the short term.

Liquidity Management

Liquidity Management allows you to analyze the past actual cash ows and forecast the medium-term liquidity trends. It also provides rolling plan cycle management and
planning status monitoring with variance analysis on plan, actual, and forecast data.

Related Information
Business Function: Cash and Liquidity Management
Con guration Guide for SAP S/4HANA Finance for Cash Management
Data Setup Guide for SAP S/4HANA Finance for Cash Management

SAP Liquidity Planner in One Exposure from Operations

Use
You can integrate allocated cash coming from SAP Liquidity Planner into One Exposure from Operations. In this integration scenario, the source application SAP Liquidity Planner and
One Exposure from Operations run in diﬀerent systems (side-by-side scenario). SAP Liquidity Planner runs in SAP Business Suite systems (releases SAP S/4HANA 6.0 EhP 6, EhP 7,
or EhP 8).

Allocated cash contains the following information from SAP Liquidity Planner:

Reference to the original data of SAP Liquidity Planner in the remote system

Account Assignments:

Company

Business Area

Bank Account

Liquidity Item

Certainty Level

One Exposure derives cash forecasts for items representing allocated cash. It stores this information with the certainty level ACTUAL.

Flow Type

The system uses the following ow types for forecasts in One Exposure:

Default Flow Types

900112 – Incoming Cash (LP)

900113 – Outgoing Cash (LP)

Liquidity Item

The system takes the liquidity item from the SAP Liquidity Planner in the remote system. The same liquidity items have to exist in the remote and in the central system.

You use transaction FQM_TRANSFER in the remote system for periodic transfer of data to the central system.

If errors occur during data upload, the system collects these errors in an application log in the remote system. Alternatively, you can also see the messages directly after executing
transaction FQM_TRANSFER in the remote system.

This is custom documentation. For more information, please visit the SAP Help Portal 2
2/24/2024
Prerequisites
To derive a bank account, you have to maintain connectivity path information for remote bank accounts in the bank account master data of the activity Manage Bank Accounts in the
central system. There, you need to ll the ID category eld with Remote System: G/L Account, and enter the company code and G/L account from the remote system.

In the central system, you have to con gure a Web service based on the service de nition FQM_WS_DISTRIBUTE. In the remote system, you have to de ne a logical port for each
remote system based on the consumer proxy CO_FQM_WS_DISTRIBUTE.

Features
In the remote system, you have the following additional functions

In the event of errors in already transferred data, you can trigger an exceptional transfer with transaction FQM_TRANSFER_MANUAL.

You can trigger the deletion of all existing data or the source application LPA from One Exposure in the remote systems with transaction FQM_DELETE.

Activities
Customizing Activities

Central System

Reassign Company Codes

In this Customizing activity, you assign the paying company codes (FLQ*-ZBUKRS) and company codes (FLQ*-BUKRS) of the remote system to company codes in the central
system.

Convert Sender Business Areas

In this Customizing activity, you assign the business areas of the remote system to business areas in the central system.

Delete Data from One Exposure from Operations Hub

If you want to use a new starting point within an implementation project, you can use this Customizing activity to delete all existing data or the source application LPA from
One Exposure. You do this for each company code and source application.

Remote System

Activate Source Application Liquidity Planner for Transfer to One Exposure

You use this Customizing activity to con gure for which companies you transfer allocated cash, and the earliest transaction date for each company.

You nd this Customizing activity under: Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner Tools

More Information
For more information on how to set up the remote and the central system, see Integration with Remote Systems.

The information is then consumed by cash management apps, such as:

Cash Flow Analyzer

Check Cash Flow Items

For further information, see One Exposure from Operations

Apps for Cash Management

Additional Implementation Activities for All Finance Apps

Use

 Note
If you use “SAP Fiori Cloud for SAP S/4HANA”, this information is not relevant for you. You don’t need to install individual apps. Instead, you connect your back-end system to the
SAP Cloud Platform.

For more information, see the product documentation for “SAP Fiori Cloud for SAP S/4HANA” on the SAP Help Portal at http://help.sap.com/ oricloud_s4hana .

In addition to the overall SAP S/4HANA installation tasks described in the UI Technology Guide for SAP S/4HANA and the implementation tasks speci c to each app explained in the
SAP Fiori apps reference library, you must perform several implementation tasks speci c to apps for Finance.

These additional tasks are as follows:

Install Required Software Component Version for Job Scheduling Apps

Create a System Alias for Design Studio Apps

This is custom documentation. For more information, please visit the SAP Help Portal 3
2/24/2024
Activate Additional OData Services and ICF Nodes

 Note
These tasks are linked to the application type of an app. You can nd the application type for a speci c app in the SAP Fiori apps reference library, which is available at
https://boma0d717969.hana.ondemand.com/sap/ x/externalViewer/

Install Required Software Component Version for Job Scheduling Apps

Software Component Version Needed:UIBAS001

Purpose:

If you use apps that have Generic Job Scheduling Framework as their application type in the SAP Fiori apps reference library, ensure that the UIBAS001 software component is also
installed on your front-end server. These apps need generic services and UIs in this software component to run properly.

How?

For more information, see the Installation Guide for SAP S/4HANA.

Create System Alias for Design Studio Apps

System Alias Needed:S4FIN

Purpose:

If you want to use analytical apps that have Design Studio as their application type in the SAP Fiori apps reference library, create the S4FIN system alias for your SAP Gateway.

How?

Create this alias in the SAP Customizing Implementation Guide (SPRO transaction) under SAP NetWeaver SAP Gateway OData Channel Con guration Connection Settings
SAP Gateway to SAP System Manage SAP System Aliases .

Enter the following mandatory parameters:

Field name Value to be entered

SAP System Alias S4FIN

Description <free text>

RFC Destination S4FIN_RFC

For more information, see the Installation Guide for SAP S/4HANA.

For more information on setting up RFC connections to back-end systems, see the UI Technology Guide for SAP S/4HANA.

Activate Additional OData Services and ICF Nodes

For general information about this activation process, see the UI Technology Guide for SAP S/4HANA.

For All Apps (Regardless of Application Type)

OData Service: FIN_USER_DEFAULTPARAMETER

ICF Node: FIN_ACC_USERPAR

Purpose:

The n.central.user.defaultparameter application plug-in is called for determining the value for certain user default parameters (for example, company code) from the ABAP back
end. The plug-in is called in two situations:

A Fiori app is started that requires a certain user default parameter.

The FLP maintenance UI for the user default parameter is opened.

How?

1. On your ABAP front-end server, activate the FIN_USER_DEFAULTPARAMETER OData service.

To do this, use the /IWFND/MAINT_SERVICE transaction and add this service. Alternatively, you can activate the services in the SAP Customizing Implementation Guide
(SPRO transaction) under SAP NetWeaver SAP Gateway OData Channel Administration General Settings Activate and Maintain Services .

 Note
If you have multiple ABAP back-end servers, you must activate the FIN_USER_DEFAULTPARAMETER_SRV technical services on each ABAP back-end server by listing each
system alias.

This is custom documentation. For more information, please visit the SAP Help Portal 4
2/24/2024
The activation on the ABAP front-end server triggers automatically the activation of the FIN_USER_DEFAULTPARAMETER_SRV technical service on your ABAP front-end
server. You can check this using the SICF transaction. Check under defaulthost sap opu odata sap .

2. On your ABAP front-end server, activate the FIN_ACC_USERPAR ICF service . Use the SICF transaction and check under defaulthost sap bc ui5_ui5 sap .

3. In the SAP Fiori Launchpad Designer, in all new business catalogs that you create for your Finance apps, create a reference to the target mapping of the Shell semantic
object with the plugin action, which is delivered in the SAP_TC_FIN_ACC_COMMON technical catalog. Note: This target mapping is already referenced in the template
business catalogs delivered by SAP.

For All Apps (Regardless of Application Type)

ICF Node Needed on Front End: FIN_LIB

Purpose:

The activation of the Central Simple Finance Fiori Reuse Library provides a collection of central functions used by all Finance Fiori apps.

How?

Use the SICF transaction to ensure that the following two nodes are active:

default_host sap bc ui5_ui5 sap n_lib

default_host sap bc bsp sap n_lib

If they are not active, activate them.

For more information on the Central Simple Finance Fiori Reuse Library, especially for information about other mandatory SAP Notes that must be implemented, see SAP
Note2117762 .

For Apps with the SAP Smart Business Application Type

OData Service Needed: /SSB/SMART_BUSINESS_RUNTIME_SRV (1)

Purpose:

Ensures that analytical apps that have SAP Smart Business as their application type in the SAP Fiori apps reference library run properly.

How?

Use the /IWFND/MAINT_SERVICE transaction.

For Apps with the Design Studio Application Type

ICF Nodes Needed:

/sap/bw/ina/GetServerInfo

/sap/bw/ina/GetResponse

Purpose:

Ensures that analytical apps that have Design Studio as their application type in the SAP Fiori apps reference library run properly.

How?

Use the SICF transaction. Note: If your front-end and back-end servers are running on diﬀerent systems, activate these nodes on both the front-end and back-end servers.

More Information
If you need more help, try the “SAP Fiori - Troubleshooting Guide for Financial Apps”, which is available on the SAP Community Network at http://scn.sap.com/docs/DOC-70278

Actual Cash Flow

Use
With this app, you can gain an overview of the daily cash ows for the past 90 days. This KPI helps you identify unusual in ows and out ows and take action accordingly. You can lter
and drill down by various dimensions. This app is available for the roles of Cash Manager and Cash Management Specialist.

Calculation Logic
The calculation logic is simple. The numbers on the app tile are the same as those in the top-right corner of the app.

The amount is the actual amount in bank account currency. The actual cash ows are calculated based on the transaction data from memo records and the One Exposure from
Operations hub.

Key Features
This is custom documentation. For more information, please visit the SAP Help Portal 5
2/24/2024
Display the aggregated cash ows

Display cash ows by company code

Display cash ows by liquidity item

Filter the data with various dimensions, such as calendar day, planning group, and so on

Navigate to the Check Cash Flow Items application to display the line item details for each cash ow

Switch the display mode between charts and tables

Monitor the daily actual cash ows for the past days

If your company uses SAP Jam, you can post comments there. You can also send emails from this app.

In addition, the app supports the following technical features and options:

This app uses the C_Actualcashflowanalytics CDS view.

Caching is enabled for this app for better performance. You can click the refresh icon on the app tile and in the bottom-left corner of the app to refresh the data immediately. The data
is also updated automatically. The frequency is determined by the cache duration in the tile con guration. For more information, see Caching in Create Tile.

Supported Device Types

Desktop

Relevant Business Catalog

SAP_SFIN_BC_CM_LM

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Con guration Settings: Actual Cash Flow

Con guration Settings: Actual Cash Flow

This document contains con guration information for this app.

SAP Jam Integration

For information on how to con gure SAP Jam, see http://help.sap.com/sapjam .

SAP Smart Business Modeler

Before you can use this app, you need to con gure it using the SAP Smart Business Modeler. For more information, see SAP Smart Business Modeler Apps.

 Note
You can edit the following details related to an SAP-delivered evaluation:

Parameters values

Filter values

Thresholds

Semantic object and action

You can also revert the changes you make to SAP-delivered evaluations. When you upgrade to the next version of SAP Smart Business Modeler apps, the changes made to the
SAP-delivered evaluation in the existing version will be merged with the new version.

KPI: Cash Position

KPI ID: SAP.SFIN.CASHMGR.CFA90DAYS

KPI Description: Actual Cash Flow

Goal Type: Maximizing

Evaluations

The following evaluations are assigned to this KPI:

Cash Flows: EUR

Evaluation

This is custom documentation. For more information, please visit the SAP Help Portal 6
2/24/2024
Evaluation ID: SAP.SFIN.CASHMGR.CFA90DAYS

Evaluation Description: Cash Trend by Date.

Targets, Thresholds, and Trend

Parameter Value Example Value

Goal Type Maximizing

Value Type Fixed Value

Critical

Warning

Target

Trend

This table shows some example values.

Input Parameters and Filters

Input Parameters

Input Parameter Operator Example Value Explanation

P_DisplayCurrency Equal to EUR

For ows which have bank accounts,
choose a bank account currency that is
converted from the transaction
currency.

For ows without bank accounts,

choose the transaction currency as
there's no such conversion.

An entry in this eld is required.

P_DueDaysRange Equal to 90 Choose a number of days to de ne the date

range so as to display the actual cash ow. The
date range is from the current date number to
the number of the last day of the range before
the current date.

An entry in this eld is required.

The following tables show the input parameters, lters, and some precon gured example values. Use your own values where required, according to the data in your backend system.

Drill-Down: Aggregated Cash Flow

View ID: V20151029064115.3534540

View Title: Aggregated Cash Flow

Measure and Dimension:

Parameter Value

Dimension Calendar Day

KPI Measure Cash Flow

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Drill-Down: Cash Flow by Liquidity Item

View ID: V20151029064115.4822790

View Title: Cash Flow by Liquidity Item

Measure and Dimension:

Parameter Value

This is custom documentation. For more information, please visit the SAP Help Portal 7
2/24/2024

Parameter Value

Dimension
Liquidity Item

Liquidity Item Name

KPI Measure Cash Flow

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Drill-Down: Cash Flow by Company Code

View ID: V20151029064115.5119380

View Title: Cash Flow by Company Code

Measure and Dimension:

Parameter Value

Dimension Company Code

KPI Measure Cash Flow

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Bank

Purpose
You can use this app for the following purposes:

To display an overview of the bank data, such as:

Bank name

Bank key

Bank country

Key facts relevant in the business context. Key facts are important data prominently displayed in the app. This app shows the following key facts:

Address of the bank

SWIFT code

Bank number

As a starting point to navigate to additional information relevant in your business context, such as information about related business partners, related master data, or
related documents.

To navigate to apps with additional functions, such as editing or analyzing related business data.

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps
Searching for a Bank

Searching for a Bank

This document shows you how to search for banks.

Use
This is custom documentation. For more information, please visit the SAP Help Portal 8
2/24/2024
To nd a speci c bank, you can search for various attributes using the search eld. Before you enter any attributes in the search eld, you should select the category Banks.

You can, for example, enter a bank country to display all banks belonging to this country. To narrow down your search results, you can also combine several attributes, such as a bank
number and a SWIFT Code. The search takes into account the following business data:

Bank Country

Bank Key

Bank Name

SWIFT Code

A list of results is displayed. For the rst result, the display area includes the header, the summary, and details. For all other results, you only see a header and a summary. To display
the details of another search result, expand the display area.

To further limit your search results to the ones that are relevant to you, you can apply one or more lters, for example a speci c status. You can also sort the search results according
to your needs.

More Information
For general information about how to search for an object page, see Search.

Bank Risk

Use
With this app you can analyze deposit distribution in terms of bank ratings. This allows you to identify deposits in high-risk bank accounts.

This app is available for the role Cash Manager and Cash Management Specialist.

Calculation Logic
The calculation logic is simple. The number on the app tile is the same as that in the top-right corner of the app.

The amount is the deposit amount in display currency on the bank accounts that you select today. The bank risk is calculated based on the transaction data from memo records and
the One Exposure from Operations hub.

Key Features
Display balances in banks of low rating

Display balances by bank

Display balances by bank and company

 Note
The bank rating can be used for sorting. Items are sorted according to their rating values high to low (or low to high) rather than alphanumerically. The mappings of rating
order values and descriptions are maintained in the VN_TP06 view. You can include other threshold (critical) ratings by updating the VN_TP06 view and incorporating your
own rating system and ordering sequence. Low rating is de ned as values larger than 12.

To make ratings available, make sure that you have a proper business partner de ned and linked to each bank. To do so, proceed as follows:

1. Link a business partner to each of the banks.

For information on how to maintain the linkages, see the topic “Business Partners for Banks” in the “Data Setup Guide for SAP S/4HANA Finance for Cash
Management”.

2. In transaction BP, de ne the following for the relevant business partners:

On the Identi cation tab, specify the elds under the Identi cation as Bank section.

Specify necessary data on the Payment Transaction tab.

Specify necessary data on the Creditworthiness Data tab.

Switch the display mode between charts and tables

Export your search results to a spreadsheet

In addition, the app supports the following technical features and options:

Send emails

You can send an email with a URL that enables the recipients to check the app with exactly the same selection criteria as you are currently using.

Save as tile

You can create a tile that uses the current selection criteria as default settings.

This is custom documentation. For more information, please visit the SAP Help Portal 9
2/24/2024
This app uses the C_BANKRISKANALYTICS CDS view.

Navigation Targets
The app enables users to access other apps directly (for example to display detailed information).

 Note
These linked apps have to be already available in your system landscape or you have to implement them along with this app.

Check Cash Flow Items

Manage Bank Accounts

Manage Banks

Make Bank Transfers

Component for Customer Incidents

FIN-FSCM-CLM-COP

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library

Con guration Settings: Bank Risk

This document contains con guration information for this app.

SAP Jam Integration

For information on how to con gure SAP Jam, see http://help.sap.com/sapjam .

SAP Smart Business Modeler

Before you can use this app, you need to con gure it using the SAP Smart Business Modeler. For more information, see SAP Smart Business Modeler Apps.

 Note
You can edit the following details related to an SAP-delivered evaluation:

Parameters values

Filter values

Thresholds

Semantic object and action

KPI: Bank Risk

KPI ID: .SFIN.CASHMGR.BANKRISK

KPI Description: With this app, cash managers can analyze deposit distribution in terms of bank rating and identify deposits in high-risk bank accounts.

Goal Type: Minimizing

Evaluation

Evaluation ID: .SFIN.CASHMGR.BANKRISK

Evaluation Description: With this app, cash managers can analyze deposit distribution in terms of bank rating and identify deposits in high-risk bank accounts.

Targets, Thresholds, and Trend

Parameter Value Example Value

Goal Type Minimizing

Value Type Fixed Value

Critical 100000

This is custom documentation. For more information, please visit the SAP Help Portal 10
2/24/2024

Parameter Value Example Value

Warning 50000

Target 10000

Trend (Not applicable)

This table shows some example values.

Input Parameters and Filters

Input Parameters

Input Parameter Operator Example Value Explanation

P_DisplayCurrency Equal to EUR Choose a currency in which the currency

amounts should be displayed. Ensure that
exchange rates for this currency exist in your
system.

An entry in this eld is required.

P_ExchangeRateType Equal to M Choose an exchange rate type that is used to

convert the currency into the display currency.

An entry in this eld is required.

You can view the available exchange rate types

in customizing in the system under SAP
NetWeaver SAP NetWeaver General
Settings Currencies Check Exchange
Rate Types .

Filter

Filter Operator Example Value Explanation

CreditRating Larger than 12 A prede ned credit rating is used to indicate

the rating level for this bank in your system.

An entry in this eld is required.

The following tables show the input parameters, lters, and some precon gured example values. Use your own values where required, according to the data in your backend system.

Drill-Down: By Low Rating

View ID: .SFIN.CASHMGR.BANKRISK.VIEW1

View Title: By Low Rating

Measure and Dimension:

Parameter Value

Dimension Rating

KPI Measure Amount In Display Currency

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Drill-Down: By Bank

View ID: .SFIN.CASHMGR.BANKRISK.VIEW2

View Title: By Bank

Measure and Dimension:

Parameter Value

Dimension Bank

KPI Measure Amount In Display Currency

Visualization Type:

This is custom documentation. For more information, please visit the SAP Help Portal 11
2/24/2024
Bar

Single Axis

Absolute Values

Default Colors

Drill-Down: By Bank and Company

View ID: .SFIN.CASHMGR.BANKRISK.VIEW3

View Title: By Bank and Company

Measure and Dimension:

Parameter Value

Dimension
Bank

Company Code

KPI Measure Amount In Display Currency

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Bank Statement Monitor

Use
With this app you can monitor the import status of bank statements for all the bank accounts that are set to be monitored. This app provides you with an overall status of the
monitored bank accounts and also allows you to identify bank accounts with statement import errors. Then, you can communicate the issue to the responsible person using emails
directly from this app.

This app is available for the role Cash Manager.

Calculation Logic
The equation below illustrates how the number on the app tile is calculated and is followed by an explanation:

How Success Rate of Bank Statement Imports Is Calculated

The success rate of bank statement imports is calculated by dividing the number of bank accounts whose bank statements are successfully imported and posted by the total number
of bank accounts that are set to be monitored.

Key Features
Check the overall success rate of bank statement imports

Filter the bank accounts displayed using various lters, such as bank, contact person, house bank, and so on

Check the import status for bank accounts using the following dimensions:

By country

This is custom documentation. For more information, please visit the SAP Help Portal 12
2/24/2024
By company code

By bank and company

By company and bank

By bank account in a table view with contact person information displayed

Toggle between a chart view and a table view

In addition, the app supports the following technical features and options:

Send emails

You can send an email with a URL that enables the recipients to check the app with exactly the same selection criteria as you are currently using.

Save as tile

You can create a tile that uses the current selection criteria as default settings.

Navigation Targets
The app enables users to access other apps directly (for example to display detailed information).

 Note
These linked apps have to be already available in your system landscape or you have to implement them along with this app.

Make Bank Transfers

Supported Device Types

Desktop

Tablet

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps

Con guration Settings: Bank Statement Monitor

This document contains con guration information for this app.

SAP Jam Integration

For information on how to con gure SAP Jam, see http://help.sap.com/sapjam .

SAP Smart Business Modeler

Before you can use this app, you need to con gure it using the SAP Smart Business Modeler. For more information, see SAP Smart Business Modeler Apps.

 Note
You can edit the following details related to an SAP-delivered evaluation:

Parameters values

Filter values

Thresholds

Semantic object and action

KPI: Bank Statement Monitor

KPI ID: sap.hba.sfin.cashmgr.bankstatementmonitor

KPI Description:
With this app, cash managers can monitor the import status of bank statements for all the bank accounts that are set to be
monitored.

Goal Type: Maximizing

Evaluation

This is custom documentation. For more information, please visit the SAP Help Portal 13
2/24/2024
Evaluation Description: Bank Statement Monitor

Targets, Thresholds, and Trend

Parameter Value

Goal Type Maximizing

Value Type FIXED

Critical 0.600

Warning 0.800

Target 0.100

This table shows some example values.

Input Parameters and Filters

Input Parameters

Input Parameter Operator Example Value Explanation

P_WarnAsError Equal to True or false The parameter aﬀects how the import success
rate is calculated.

True: Bank statement imports with the

warning status are counted as errors.

False: Bank statement imports with the

warning status are counted as
successful imports.

The following tables show the input parameters, lters, and some precon gured example values. Use your own values where required, according to the data in your backend system.

Drill-Down: By Bank and Company

View Title: By Bank and Company

Measures and Dimensions:

Parameter Value

Dimensions
Bank

Company Code

Measures
Warning

Succeeded

Error

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Drill-Down: By Bank Account (Contact Person)

View Title: By Bank Account (Contact Person)

Measures and Dimensions:

Parameter Value

Dimensions
Bank

Company Code

Country

Bank Account

Contact Person

This is custom documentation. For more information, please visit the SAP Help Portal 14
2/24/2024

Parameter Value

Measures
Warning

Succeeded

Error

Visualization Type:

Table

Default Colors

Drill-Down: By Company Code

View Title: By Company Code

Measures and Dimensions:

Parameter Value

Dimension
Company Code

Measures
Warning

Succeeded

Error

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Drill-Down: By Country

View Title: By Country

Measures and Dimensions:

Parameter Value

Dimension
Country

Measures
Warning

Succeeded

Error

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Cash Flow Analyzer

With this app, you can view the aggregated amounts and line item details of cash position, medium- and -long term liquidity forecast, and actual cash ows. You can analyze cash ows
over days, weeks, months, quarters, or years for all bank accounts and liquidity items. The data presented in the app can be used to give a high-level overview and detailed insight into
the cash ow status to the management.

This app is available for users with the Cash Manager or Cash Management Specialist roles.

Key Features

This is custom documentation. For more information, please visit the SAP Help Portal 15
2/24/2024
Derive the currency based on transaction currency or account currency.

This is de ned in the Me Area under More => User Settings.

Select the default report between Cash Position, Liquidity Forecast and Actual Cash Flows, or create your own variant.

Display the default grouping variant in the structure of Currency => Company Code => Bank Account, or create your own variant.

Choose a calendar and shift the amounts in non-working days to the next or previous working days.

Display an end-of-period report by calendar end, or by the interval end of the period.

Switch between the balance view and the delta (net cash ows only) view.

Display the report in bank account groups hierarchy and liquidity item hierarchy.

The bank account groups are de ned in the Manage Bank Accounts - Bank Hierarchy View app. The liquidity items and the hierarchy are de ned in the Liquidity Item Hierarchy
app.

Navigate to the Check Cash Flow Items app to display the line item details for each cash ow.

Navigate to the Make Bank Transfers app to make necessary transfers on your bank accounts.

Integrate dynamic data sources from memo records, paymnet orders, payment requests and source applications that are stored in One Exposure from Operations.

In addition, the app supports the following technical features and options:

This app uses the following CDS views:

P_Fclm_Flow_Analyzer_Bkhview

P_Fclm_Flow_Analyzer_Overview

P_Fclm_Flow_Analyzer_Lqhview

Open this video in a new window

Supported Device Types

Desktop

Cash Flow - Detailed Analysis

Use
With this app you can get an overview of the daily cash in ows and out ows, and analyze them for the last weeks or months for all subsidiaries and liquidity items. You can then
identify the extraordinary and abnormal cash ows, ensure that they were accurate and compliant, and that they have taken the liquidity planning into account. The data presented in
the app can be used to give an overview of the cash ow status to the management.

 Note
If the Web Dynpro application type is set as a default for your app on the SAP Fiori launchpad, you can add the Design Studio version of this app to your launchpad. Go to the App
Finder in your Me Area and search for the name of your app.

Key Features
View the cash in ow, out ow, and net ow that has been con rmed by banks, using the actual value date of the bank statements

Perform multi-dimensional analysis by country, bank (account), company code, currency, business area, transaction date, and liquidity item hierarchy The liquidity item is
derived from invoice level to bank statement level by the Liquidity Planner in a batch job

This is custom documentation. For more information, please visit the SAP Help Portal 16
2/24/2024
Report in a particular currency for a particular date that the user has speci ed

Drill down by calendar day and all other reporting dimensions listed above

In addition, the app supports the following technical features and options:

This app uses the C_CashFlowDetailedAnalysisQ CDS view.

Supported Device Types

Desktop

Relevant Business Catalog

SAP_SFIN_BC_CM_LM

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library

Cash Position

Use
With this app you can check the forecasted cash positions for the current date by location, company, and currency. Cash position data is calculated based on memo records, and other
data sources from the One Exposure from Operations hub.

This app is available for the role Cash Manager.

Calculation Logic
The calculation logic is simple. The number on the app tile is the same as that in the top-right corner of the app.

The amount is the aggregated amount in display currency on the bank accounts that you select today. The cash position is calculated based on the transaction data from memo
records and the One Exposure from Operations hub.

Key Features
Display cash positions by the following analytical dimensions:

Bank country (with display currency)

Bank (with display currency)

Company (with display currency)

Bank and bank account currency

Bank account currency and country

Bank account currency

Bank account currency (Table View)

Bank group

Switch the display mode between charts and tables

Export your search results to a spreadsheet

In addition, the app supports the following technical features and options:

Send emails

You can send an email with a URL that enables the recipients to check the app with exactly the same selection criteria as you are currently using.

Save as tile

You can create a tile that uses the current selection criteria as default settings.

This app uses the C_CASHPOSITIONANALYTICS_CDS CDS view.

Navigation Targets
The app enables users to access other apps directly (for example to display detailed information).

This is custom documentation. For more information, please visit the SAP Help Portal 17
2/24/2024

 Note
These linked apps have to be already available in your system landscape or you have to implement them along with this app.

Make Bank Transfers

Component for Customer Incidents

FIN-FSCM-CLM-COP

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library

Con guration Settings: Cash Position

This document contains con guration information for this app.

SAP Jam Integration

For information on how to con gure SAP Jam, see http://help.sap.com/sapjam .

SAP Smart Business Modeler

Before you can use this app, you need to con gure it using the SAP Smart Business Modeler. For more information, see SAP Smart Business Modeler Apps.

 Note
You can edit the following details related to an SAP-delivered evaluation:

Parameters values

Filter values

Thresholds

Semantic object and action

KPI: Cash Position

KPI ID: .sfin.cashmgr.cashposition

KPI Description:
With Cash Position, you can check cash positions by location, company, and currency. This KPI allows you to filter and drill down by
various dimensions.

Goal Type: Maximizing

Evaluations

The following evaluations are assigned to this KPI:

Today

Evaluation

Evaluation ID: .sfin.cashmgr.cashpositionvar

Evaluation Description: With Cash Position, you can check cash positions by location, company, and currency. This KPI allows you to lter and drill down by various dimensions.

Targets, Thresholds, and Trend

Parameter Value Example Value

Goal Type Maximizing

Value Type Fixed Value

Critical 10000

Warning 100000

Target 100000

This is custom documentation. For more information, please visit the SAP Help Portal 18
2/24/2024

Parameter Value Example Value

Trend (Not applicable)

This table shows some example values.

Input Parameters and Filters

Input Parameters

Input Parameter Operator Example Value Explanation

P_DisplayCurrency Equal to EUR Choose a currency in which the currency

amounts should be displayed. Ensure that
exchange rates for this currency exist in your
system.

An entry in this eld is required.

P_ExchangeRateType Equal to M Choose an exchange rate type that is used to

convert the currency into the display currency.

An entry in this eld is required.

You can view the available exchange rate types

in customizing in the system under SAP
NetWeaver SAP NetWeaver General
Settings Currencies Check Exchange
Rate Types .

The following tables show the input parameters, lters, and some precon gured example values. Use your own values where required, according to the data in your backend system.

Drill-Down: By Bank Country

View ID: .sfin.cashmgr.cashposition.view1

View Title: By Bank Country

Measure and Dimension:

Parameter Value

Dimension Country

KPI Measure Amount In Display Currency

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Drill-Down: By Bank

View ID: .sfin.cashmgr.cashposition.view2

View Title: By Bank

Measure and Dimension:

Parameter Value

Dimension Bank

KPI Measure Amount in Display Currency

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Drill-Down: By Company

View ID: .sfin.cashmgr.cashposition.view3

This is custom documentation. For more information, please visit the SAP Help Portal 19
2/24/2024
View Title: By Company

Measure and Dimension:

Parameter Value

Dimension Company Code

Parameter Value

KPI Measure Amount in Display Currency

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Drill-Down: By Currency (Table View)

View ID: .sfin.cashmgr.cashposition.view7

View Title: By Currency (Table View)

Measure and Dimension:

Parameter Value

Dimension Currency

KPI Measure Amount in Display Currency

Measure Amount in Balance Transaction Currency

Visualization Type:

Table

Default Colors

Drill-Down: By Bank Group

View ID: .sfin.cashmgr.cashposition.view2

View Title: By Bank

Measure and Dimension:

Parameter Value

Dimension Bank Group

KPI Measure Amount in Display Currency

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Check Cash Flow Items

Use
With this app you can track document line items that are relevant to cash ows, for example, invoices, payments, bank statements, treasury deals, memo records, and so on. You can
also check document details directly from this app.

This app is available for the role Cash Manager and Cash Management Specialist.

Key Features
Overview

List the aggregated cash ows from source applications that are integrated from One Exposure from Operations and Memo Records

Filter cash ow items by various dimensions, such as certainty level, summarization term, grouping and so on

 Note
A particular grouping consists of planning levels, the G/L accounts, and planning groups that are displayed for the cash position and the liquidity forecast. And by
summarization term, you can combine the two lines to lter the data.

This is custom documentation. For more information, please visit the SAP Help Portal 21
2/24/2024

Monitor payment status in the list view for payment batches in Bank Communication Management (BCM).

Navigate from cash position and liquidity forecast to check the line item details.

Details

Check the original document information from source applications.

Navigate to the source applications, such as a bank statement.

Manually adjust the account assignments, such as liquidity item, transaction amount, cost center, and so on.

 Note
This function only works for cash ows from accounting documents (journal entries).

In addition, the app supports the following technical features and options:

Export your search results to a spreadsheet.

Send emails

You can send an email with a URL that enables the recipients to check the app with exactly the same selection criteria as you are currently using.

Save as tile

You can create a tile that uses the current selection criteria as default settings.

Component for Customer Incidents

BankStatement.fragment extBankStatement PaymentDetailTransData FCLM_PAYMENTDETAILFLOW FCLM_CP_S_ENTITY_PAYMENTDETAIL Superclass

Method:
IF_SADL_

This is custom documentation. For more information, please visit the SAP Help Portal 22
2/24/2024

Further Extensibility Entities

Extension Includes

In addition to the extension includes described above, the following extension includes are available:

DDIC Extension Include Use

FCLM_CP_S_ENTITY_PAYMENTITEM FCLM_CP_S_ENTITY_PAY_ITEM_INCL Allows you to add customer elds which can be exposed to the
front-end UI

For more information about extension includes, see section Extensibility in the SAP S/4HANA UI Technology guide.

UI Controller Hooks

To plug in and execute custom code to <business case>, for example, the following hooks are available in the controller code:

Controller Hook Use

This is custom documentation. For more information, please visit the SAP Help Portal 23
2/24/2024

Controller Hook Use

fin.cash.paymentdetail.display.view.S1. extHookonDataReceived Allows you to assign values of the columns you extended in
OData entity PaymentDetailItem to the extended columns
you added for extension point
extColumnsForBankAccountCurrencyView.

fin.cash.paymentdetail.display.view.S1. extHookOnInit Allows you to assign values of the columns you extended in
OData entity PaymentDetailItem to the extended columns
you added for extension point
extColumnsForBankAccountCurrencyView.

If there are additional UI controller hooks available in the controller code, you can extend the UI controller code. For more information about UI controller hooks, see section
Extensibility in the SAP S/4HANA UI Technology guide.

More Information
For a general description of the extensibility options and procedures, see Extensibility in the SAP S/4HANA UI Technology guide.

De cit Cash Pool

Use
With this app you can quickly identify cash pools with de cits and the total de cit amount in cash pools. This allows you to respond quickly to cash pool de cits and to allocate funds
smartly among your cash pools.

This app is available for the role Cash Manager and Cash Management Specialist.

Calculation Logic
The calculation logic is simple. The number on the app tile is the same as that in the top-right corner of the app.

The amount is the de cit amount in display currency based on the bank accounts that you select today. The de cit cash pool is calculated based on the transaction data from memo
records and the One Exposure from Operations hub.

Key Features
Display the de cit amounts by cash pool

Display the de cit amounts by bank account

Switch the display mode between charts and tables

Export your search results to a spreadsheet

In addition, the app supports the following technical features and options:

Send emails

You can send an email with a URL that enables the recipients to check the app with exactly the same selection criteria as you are currently using.

Save as tile

You can create a tile that uses the current selection criteria as default settings.

This app uses the C_DEFICITCASHPOOLANALYTICS CDS view.

Navigation Targets
The app enables users to access other apps directly (for example to display detailed information).

 Note
These linked apps have to be already available in your system landscape or you have to implement them along with this app.

Manage Bank Accounts

Component for Customer Incidents

FIN-FSCM-CLM-COP

Related Information

This is custom documentation. For more information, please visit the SAP Help Portal 24
2/24/2024
App-Speci c Implementation Information in the SAP Fiori apps reference library

Con guration Settings: De cit Cash Pool

This document contains con guration information for this app.

SAP Jam Integration

For information on how to con gure SAP Jam, see http://help.sap.com/sapjam .

SAP Smart Business Modeler

Before you can use this app, you need to con gure it using the SAP Smart Business Modeler. For more information, see SAP Smart Business Modeler Apps.

 Note
You can edit the following details related to an SAP-delivered evaluation:

Parameters values

Filter values

Thresholds

Semantic object and action

KPI: De ct Cash Pool

KPI ID: .SFIN.CASHMGR.DEFICITCASHPOOL

KPI Description: With this app, cash managers can check deficit cash pool of today.

Goal Type: Maximizing

Evaluation

Evaluation ID: .SFIN.CASHMGR.DEFICITCASHPOOLVAR

Evaluation Description: With this app, cash managers can check de cit cash pool of today. This KPI allows you to lter and drill down by various dimensions.

Targets, Thresholds, and Trend

Parameter Value Example Value

Goal Type Maximizing

Value Type Fixed Value

Critical -100000

Warning -50000

Target 0

Trend (Not applicable)

This table shows some example values.

Input Parameters and Filters

Input Parameters

Input Parameter Operator Example Value Explanation

P_DisplayCurrency Equal to EUR Choose a currency in which the currency

amounts should be displayed. Ensure that
exchange rates for this currency exist in your
system.

An entry in this eld is required.

This is custom documentation. For more information, please visit the SAP Help Portal 25
2/24/2024

Input Parameter Operator Example Value Explanation

P_ExchangeRateType Equal to M Choose an exchange rate type that is used to

convert the currency into the display currency.

An entry in this eld is required.

You can view the available exchange rate types

in customizing in the system under SAP
NetWeaver SAP NetWeaver General
Settings Currencies Check Exchange
Rate Types .

The following tables show the input parameters, lters, and some precon gured example values. Use your own values where required, according to the data in your backend system.

Drill-Down: By Cash Pool

View ID: .SFIN.CASHMGR.DEFICITCASHPOOL.VIEW1

View Title: By Cash Pool

Measure and Dimension:

Parameter Value

Dimension Cash Pool ID

KPI Measure Amount in Dspl Crcy

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Drill-Down: By Bank Account

View ID: .SFIN.CASHMGR.DEFICITCASHPOOL.VIEW2

View Title: By Bank Account

Measure and Dimension:

Parameter Value

Dimension Tech. ID

KPI Measure Amount in Dspl Crcy

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Develop Liquidity Plans

Use
With this app, cash managers can regularly trigger the start of a new cycle for a rolling liquidity plan. Cash management specialists then enter and submit liquidity plans in the
relevant planning period for approval by cash managers. The precise estimates of future cash in ows and out ows allow cash managers to ensure that payment obligations are met
and give them the data they need to make investment or funding plans. Rolling process management makes tracing and tracking much easier, enabling continuous improvements.
This app is available for the roles of Cash Manager and Cash Management Specialist.

Key Features
Start a new planning cycle for a rolling liquidity plan. Cash management specialists are reminded by E-mail noti cations to enter liquidity plans.

Enter liquidity plans in planning currencies based on the reference data of last year actual, previous cycle planned, and liquidity forecast data.

Submit liquidity plans for approval by cash managers. Cash managers are noticed by E-mails that plans are ready to be reviewed.

Approve or reject liquidity plans submitted by cash management specialists.

This is custom documentation. For more information, please visit the SAP Help Portal 26
2/24/2024
Display liquidity plans by planning currency or by aggregation currency.

Display the exchange rate and aggregation details in planning currency.

Navigate to the app Liquidity Plans.

Compare the submitted liquidity plans with last year actual data, previous cycle planned data, and liquidity forecast data.

Related App
Liquidity Plans

Component for Customer Incidents

FIN-FSCM-CLM-LM

More Information
App-Speci c Implementation Information in the SAP Fiori apps reference library: https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F0738

Additional Implementation Activities for All Finance Apps

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library

Foreign Bank Account Report

Use
With this app you can identify foreign bank accounts and responsible signatories in your company. You can use the information to le legitimate reports, if required in your country, for
example the Report of Foreign Bank and Financial Accounts (FBAR) required for United States persons. You can also use the information for analytical purposes.

Key Features
Check foreign bank accounts for one or more company codes

Display the maximum account value for each foreign bank account in the speci ed time range

Apply the minimum aggregate value condition to each selected company code so as to calculate whether foreign bank accounts in a certain company code need to be reported

Check employees who have signature authority over the foreign bank accounts

Export foreign bank accounts that match your search into a spreadsheet

In addition, the app supports the following technical features and options:

SAP Jam integration

If your company uses SAP Jam, you can share information with a certain group of people in SAP Jam and receive feedback from them.

Send emails

You can send an email with a URL that enables the recipients to check the app with exactly the same selection criteria as you are currently using.

Save as tile

You can create a tile that uses the current selection criteria as default settings.

Supported Device Types

Desktop

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps

App Extensibility: Foreign Bank Account Report

Use
You can extend this app according to your business needs for diﬀerent aspects. For this purpose, the following extensibility options are available for developers.

Extension Points

This is custom documentation. For more information, please visit the SAP Help Portal 27
2/24/2024
To add additional columns to the report, for example, the following extension points are available:

View Extension Point Use

List.view.xml fin.cash.foreignbankaccount.report.ownerTableExtPointTableColumnEnd Allows you to insert columns at the end

of the table on the list view of the
Company tab.

List.view.xml fin.cash.foreignbankaccount.report.ownerFormExtPointTableColumnEnd Allows you to insert columns at the end

of the table on the form view of the
Company tab.

List.view.xml fin.cash.foreignbankaccount.report.employeeOverviewExtPointTableColumnEnd Allows you to insert columns at the end

of the table on the list view of the
Employee tab.

EmployeeDetail.view.xml fin.cash.foreignbankaccount.report.employeeDetailsExtPointTableColumnEnd Allows you to insert columns at the end

of the table on employee details
screen.

If there are additional elds available in the OData service, you can display these elds on the UI. For more information about extension points, see section Extensibility in the SAP
S/4HANA UI Technology guide.

UI Controller Hooks
The following hooks are available in the controller code:

Controller Hook Use

List.controller.js extHookOnDataReceived Allows you to extend the logic for received data in
List.view.xml.

List.controller.js extHookOnInit Allows you to extend the initiation of controllers in

List.view.xml.

EmployeeDetail.controller.js extHookOnDataReceived Allows you to extend the logic for received data in
EmployeeDetail.view.xml.

EmployeeDetail.controller.js extHookOnInit Allows you to extend the initiation of controllers in

EmployeeDetail.view.xml.

More Information
For a general description of the extensibility options and procedures, see Extensibility in the SAP S/4HANA UI Technology guide.

House Bank

Purpose
You can use this app for the following purposes:

To display an overview of the house bank data, such as:

House bank description

House bank country

House bank city

Key facts relevant in the business context. Key facts are important data prominently displayed in the app. This app shows the following key facts:

Company code

Bank key

Bank number

As a starting point to navigate to additional information relevant in your business context, such as information about related business partners, related master data, or
related documents.

To navigate to apps with additional functions, such as editing or analyzing related business data.

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps
Searching for a House Bank

This is custom documentation. For more information, please visit the SAP Help Portal 28
2/24/2024

Searching for a House Bank

This document shows you how to search for house banks.

Use
To nd a speci c house bank, you can search for various attributes using the search eld. Before you enter any attributes in the search eld, you should select the category House
Banks.

You can, for example, enter a bank country to display all house banks belonging to this country. To narrow down your search results, you can also combine several attributes, such as a
company code and a bank key. The search takes into account the following business data:

Company Code

Country

Bank Country

Bank Key

Bank Name

To further limit your search results to the ones that are relevant to you, you can apply one or more lters, for example a speci c status. You can also sort the search results according
to your needs.

More Information
For general information about how to search for an object page, see Search.

House Bank Account

Purpose
You can use this app for the following purposes:

To display an overview of the house bank account data, such as:

House bank account description

House bank account ID

Key facts relevant in the business context. Key facts are important data prominently displayed in the app. This app shows the following key facts:

Bank account number

IBAN

As a starting point to navigate to additional information relevant in your business context, such as information about related business partners, related master data, or
related documents.

To navigate to apps with additional functions, such as editing or analyzing related business data.

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps
Searching for a House Bank Account

Searching for a House Bank Account

This document shows you how to search for house bank accounts.

Use
To nd a speci c house bank account, you can search for various attributes using the search eld. Before you enter any attributes in the search eld, you should select the category
House Bank Accounts.

You can, for example, enter a company code to display all house bank accounts belonging to this company code. To narrow down your search results, you can also combine several
attributes, such as a company code and an account ID. The search takes into account the following business data:

Company Code

House Bank

Chart of Accounts

This is custom documentation. For more information, please visit the SAP Help Portal 29
2/24/2024
Account ID

Bank Account

To further limit your search results to the ones that are relevant to you, you can apply one or more lters, for example a speci c status. You can also sort the search results according
to your needs.

More Information
For general information about how to search for an object page, see Search.

Initiate Review Process

Use
With this app you can initiate a review process for selected bank accounts to ensure the bank account master data is up to date for each bank account.

Key Features
Search for bank accounts to be reviewed using the following lters:

Company code

Country

Bank

Account number

Contact person

Initiate a review work ow for the selected bank accounts.

The system sends the review request to contact persons of each bank account respectively. Each contact person receives a request that contains all the bank accounts that he
or she is responsible for and selected for review.

 Note
Only bank accounts assigned with a contact person can be reviewed. Make sure you have de ned the contact person for each bank account in the bank account master
data. To do so, on the Bank Relationship tab, under the Internal Contact Persons section, specify the Contact Person eld.

 Note
This app is based on a diﬀerent UI technology, so there are slight diﬀerences from the other SAP Fiori apps.

Supported Device Types

Desktop

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps

Liquidity Forecast

Use
With this app you can forecast the liquidity trend for the following 90 days. You can lter and drill down by various dimensions. This app is available for the roles of Cash Manager and
Cash Management Specialist.

Calculation Logic
The calculation logic is simple. The numbers on the app tile are the same as those in the top-right corner of the app.

The amount is the forecasted amount in bank account currency. The liquidity forecast is calculated based on the transaction data from memo records and the One Exposure from
Operations hub.

Key Features
Display the aggregated forecast cash ows and closing balance

This is custom documentation. For more information, please visit the SAP Help Portal 30
2/24/2024
Display cash ows and closing balances by company code

Display cash ows and closing balances by liquidity item

Filter the data with various dimensions, such as calendar day, planning group, and so on

Navigate to the Check Cash Flow Items application to display the line item details for each cash ow

Switch the display mode between charts and tables

Monitor the daily actual cash ows for the past days

In addition, the app supports the following technical features and options:

This app uses the C_Lfcastanalytics CDS view.

Supported Device Types

Desktop

Relevant Business Catalog

SAP_SFIN_BC_CM_LM

More Information
App-Speci c Implementation Information in the SAP Fiori apps reference library: https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F0512A

Additional Implementation Activities for All Finance Apps

Con guration Settings: Liquidity Forecast

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library

Con guration Settings: Liquidity Forecast

This document contains con guration information for this app.

SAP Jam Integration

For information on how to con gure SAP Jam, see http://help.sap.com/sapjam .

SAP Smart Business Modeler

Before you can use this app, you need to con gure it using the SAP Smart Business Modeler. For more information, see SAP Smart Business Modeler Apps.

 Note
You can edit the following details related to an SAP-delivered evaluation:

Parameters values

Filter values

Thresholds

Semantic object and action

KPI: Liquidity Forecast

KPI ID: SAP.SFIN.CASHMGR.LIQUIDITY90DAYS

KPI Description:

Goal Type: Maximizing

Evaluation

The following evaluations are assigned to this KPI:

This is custom documentation. For more information, please visit the SAP Help Portal 31
2/24/2024
Liquidity Forecast: EUR

Evaluation ID: SAP.SFIN.CASHMGR.LIQUIDITY90DAYS

Evaluation Description: Liquidity Forecast Transaction Currency: Euro

Targets, Thresholds, and Trend

Parameter Value Example Value

Goal Type Maximizing

Value Type Fixed Value

Critical

Warning

Target

Trend (Not applicable)

This table shows some example values.

Input Parameters and Filters

Input Parameters

Input Parameter Operator Example Value Explanation

P_DisplayCurrency Equal to EUR

For ows which have bank accounts,
choose a bank account currency that is
converted from the transaction
currency.

For ows without bank accounts,

choose the transaction currency as
there's no such conversion.

An entry in this eld is required.

P_NumberOfDays Equal to 90 Choose a number of days to de ne the date

range to be displayed in the liquidity forecast.
The date range is from the current date
number to the number of the last day of the
range after the current date.

An entry in this eld is required.

The following tables show the input parameters, lters, and some precon gured example values. Use your own values where required, according to the data in your backend system.

Drill-Down: Forecast Cash Flow and Balance

View ID: V20151028100017.5724150

View Title: Forecast Cash Flow and Balance

Measure and Dimension: Closing Balance = Opening Balance + Forecast Cash Flow

Parameter Value

Dimension Calendar Day

KPI Measure Closing Balance

KPI Measure Cash Flow

Visualization Type:

Columns and Lines

Manual Colors

Drill-Down: Cash Flow by Liquidity Item

View ID: V20151028100017.7019220

View Title: Cash Flow by Liquidity Item

Measure and Dimension:

Parameter Value

This is custom documentation. For more information, please visit the SAP Help Portal 32
2/24/2024

Parameter Value

Dimension
Liquidity Item

Liquidity Item Name

KPI Measure Cash Flow

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Drill-Down: Cash Flow by Company Code

View ID: V20151028100017.7339160

View Title: Cash Flow by Company Code

Measure and Dimension:

Parameter Value

Dimension Company Code

KPI Measure Cash Flow

Visualization Type:

Bar

Single Axis

Absolute Values

Default Colors

Liquidity Forecast Details

Use
With this app, you can display the overview and the details of forecasted amounts of each liquidity item by diﬀerent dimensions.

Key Features
Overview

Display the amounts of opening balance, net cash ows and closing balance

Set transaction currency and date for the overview

Details

Display the amounts of net cash ows in transaction currency and display currency

Set display currency, liquidity item hierarchy and date for the details

Adjust the dimension layout by switching rows and columns

Switch the display mode between charts and tables

In addition, the app supports the following technical features and options:

This app uses the following CDS views:

C_Liquidityforecastdetailsq

C_Liquidityforecast_Overviewq

Supported Device Types

This is custom documentation. For more information, please visit the SAP Help Portal 33
2/24/2024
Desktop

Tablet

Smartphone

Relevant Business Catalog

SAP_SFIN_BC_CM_LM

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library

Liquidity Plans

Use
With this app, you can locate the diﬀerences between actual, planned and forecast data in each liquidity item and planning unit. You can also check the diﬀerence details for a
selected planning cycle. This allows you to get the continuous analysis of actual, planned and forecast data, thus increases the reliability of liquidity plans. This app is available for the
roles of Cash Manager and Cash Management Specialist.

Key Features
Display your liquidity plans

Display the planning data of the last 12 planning cycles by month in a selected planning cycle

Display the plans by planning currency or aggregation currency

View the diﬀerence details

Compare the diﬀerences between the selected planning cycle and the previous planning cycle

Display aggregation details in both planning and aggregation currencies

Check the exchange rates for aggregation

Check the alerts of your liquidity plans

View the diﬀerence in a 12-month rolling trend

Compare the diﬀerences between actual, planned and forecast data in liquidity items and planning units

Related App
Develop Liquidity Plans

Component for Customer Incidents

FIN-FSCM-CLM-LM

More Information
App-Speci c Implementation Information in the SAP Fiori apps reference library: https:// oriappslibrary.hana.ondemand.com/sap/ x/externalViewer/index.html?appId=F0767

Additional Implementation Activities for All Finance Apps

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library

Maintain Signatory

Use
With this app you can maintain a signatory in multiple bank accounts.

Key Features
Replace a signatory in multiple bank accounts.

Add a signatory to multiple bank accounts.

Revoke the authorization of a signatory in multiple bank accounts, by changing the validity period of the signatory.

This is custom documentation. For more information, please visit the SAP Help Portal 34
2/24/2024
Use SAP Business Work ow to control the process of the operations above.

 Note
This app is based on a diﬀerent UI technology, so there are slight diﬀerences from the other SAP Fiori apps.

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps

Make Bank Transfers

Use
With this app you can conduct bank-to-bank transfers of cash. You can view information about the bank account from which or to which you want to make the transfer. You can lter or
search for bank accounts by several dimensions.

This app is available for the role Cash Manager and Cash Management Specialist.

Key Features
Conduct transfers of cash among diﬀerent banks accounts

List bank accounts from which or to which you want to make the transfer

Specify the payment method and date of conducting the transfer

Display details about a bank account

 Note
The system only supports the exchange rate type M (average rate) to convert payments in foreign currency to bank account currency. You must use the exchange rate type
M and also enter the exchange rates for this type.

In addition, the app supports the following technical features and options: In addition, the app supports the following technical features and options:

SAP Jam integration

If your company uses SAP Jam, you can share information with a certain group of people in SAP Jam and receive feedback from them.

Save as tile

You can create a tile that uses the current selection criteria as default settings.

Navigation Targets
The app enables users to access other apps directly (for example to display detailed information).

 Note
These linked apps have to be already available in your system landscape or you have to implement them along with this app.

Track Bank Transfers

Component for Customer Incidents

FIN-FSCM-CLM-COP

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library

App Extensibility: Make Bank Transfers

Use
You can extend this app according to your business needs for diﬀerent aspects. For this purpose, the following extensibility options are available:

Payment Method Descriptions

You can add a description about a payment method to the right of the Payment Method eld.

Filter Options

You can add more options for ltering the bank accounts to the Filter screen.

This is custom documentation. For more information, please visit the SAP Help Portal 35
2/24/2024
Bank Transfer Parameters

You can add other parameters for the bank transfer and create the corresponding elds on the user interface.

Payment Method Descriptions

To add a description about a payment method, the following extensibility entities are available on the diﬀerent software layers. You have to extend each of these entities according to
your speci c business needs:

UI Back End / ABAP

View Extension Point Design Time: Gateway Entity Design Time: Extension Include (in Runtime: Superclass/ Method to Be Rede ned
DDIC Structure)

S1.view.xml extPaymentMethodField FCLM_BANK_TRANSFER_SRV FCLM_S_PAYMENT_METHOD_INCL Superclass: /IWBEP/CL_MGW_PUSH_ABS_DATANTDETA_DPC_EXT

;/IWBEP/CL_MGW_PUSH_ABS_MODEL

Method:
IF_SADL_GW_EXTENSION_CONTROL~SET_EXTENSION_MAPPING

Filter Options
To add new options for ltering the bank accounts, the following extensibility entities are available on the diﬀerent software layers. You have to extend each of these entities
according to your speci c business needs:

UI Back End / ABAP

View Extension Point Design Time: Gateway Design Time: CDS View Design Time: Extension Include (in Runtime: Superclass/ Method
Entity DDIC Structure)

filter.fragment.xml extSrcFilterCols PERP_FCLM_BTBAL_SRV FCLM_BEGINNINGBALANCE_FINAL FCLM_S_SEARCH_VALUE_HELP_INCL Superclass:

/IWBEP/CL_MGW_PUSH_ABS

Method: GET_ENTITYSET DE

Bank Transfer Parameters

To add new parameters for the bank transfer, the following extensibility entities are available on the diﬀerent software layers. You have to extend each of these entities according to
your speci c business needs:

UI Back End / ABAP

View Extension Point Design Time: Gateway Entity Design Time: Extension Include (in Runtime: Superclass/ Method to Be
DDIC Structure) Rede ned

S1.view.xml extTransferField FCLM_BANK_TRANSFER_SRV FCLM_S_BANK_TRANSFER_INCL Superclass:

/IWBEP/CL_MGW_PUSH_ABS_DATA
;/IWBEP/CL_MGW_PUSH_ABS_MODEL

Method: CREATE_ENTITY DEFINE

Further Extensibility Entities

Extension Includes

In addition to the extension includes described above, the following extension includes are available:

DDIC Extension Include Use

FCLM_BT_S_BANK_TRANSFER FCLM_S_BANK_TRANSFER_INCL Allows you to extend the bank transfer

FCLM_BT_S_PAYMENT_METHOD FCLM_S_PAYMENT_METHOD_INCL Allows you to extend the payment method

FCLM_BT_S_SEARCH_VALUE_HELP FCLM_S_SEARCH_VALUE_HELP_INCL Allows you to extend the search help

For more information about extension includes, see section Extensibility in the SAP S/4HANA UI Technology guide.

UI Controller Hooks

To plug in and execute custom code, the following hooks are available in the controller code:

Controller Hook Use

S1 extHookPaymentMethod Allows you to add a description about a payment method

S1 extHookFilterField Allows you to add more lter options

S1 extHookTransferField Allows you to add other bank transfer parameters

This is custom documentation. For more information, please visit the SAP Help Portal 36
2/24/2024
More Information
For a general description of the extensibility options and procedures, see Extensibility in the SAP S/4HANA UI Technology guide.

Manage Banks

Use
With this app you can display, create, and change data about the banks your company, your customers, and your suppliers use to transact business.

Key Features
Forms a central repository for address, risk, and other kinds of general bank data.

Create, display, and edit data for banks and house banks in which your company has one or more accounts.

Create, display, and edit data for banks that your customers and suppliers use to transact business with your company.

Associate house banks, contact persons, and business partners with your banks.

Other Features

In addition, the app supports the following technical features:

Export to Spreadsheet: Exports list data to a spreadsheet.

Share: Allows you to send speci c data to colleagues by email or by using SAP Jam, and which allows you to save a speci c data view as a tile available on your Launchpad.

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps

Manage Bank Accounts

With this app you can create, display, edit, and delete bank accounts according to your business needs.

Key Features
Search for a bank account using key words and lters.

Create new bank accounts.

Open a bank account master record, where you can check bank account details, make changes, copy the bank account to create a new bank account, close the bank account,
and delete the bank account if it is inactive.

Delete inactive bank accounts and bank account drafts en masse.

 Note
Bank accounts that are in work ow processes cannot be deleted.

Create document or URL attachments for bank accounts.

Search for bank account attachments.

Use SAP Business Work ow or dual control to manage and streamline the process of opening, modifying, closing, reopening, and reviewing bank accounts.

In addition, the app supports the following technical features and options:

Send emails

You can use this app to send an email containing a URL to the selected information in this app.

Share in SAP Jam

If your company uses SAP Jam groups, you can post your comments about a task there.

Save as tile

You can create a tile that uses the current selection criteria as default settings.

How-To Videos (English only)

Using Dual Control for Bank Account Management

This is custom documentation. For more information, please visit the SAP Help Portal 37
2/24/2024

Open this video in a new window

Using Work ows for Bank Account Management

Open this video in a new window

 Note
Captions/subtitles are available for multiple languages. Simply click the CC button at the bottom right of the video player to see which languages are supported.

Supported Device Types

Desktop

Tablet

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps

This is custom documentation. For more information, please visit the SAP Help Portal 38
2/24/2024
App Extensibility: Manage Bank Accounts

App Extensibility: Manage Bank Accounts

You can extend theManage Bank Accounts app according to your business needs for diﬀerent aspects. For this purpose, the following extensibility options are available:

For Key Users and Developers

You can add elds to the following UI elements using UI adaptations at runtime:

UI Element Business Context

The General Data section of the bank account master data Manage Bank Accounts

For more information about how to adapt an SAP Fiori UI at runtime, go to http://help.sap.com/s4hana and open the product page for the relevant version. On the product page,
enter Making UI Changes into the search bar, press Enter and open the search result with that title.

You can implement logic for the following enhancement options:

Enhancement Option Business Context

Assign default values to custom elds Bank Account Master Data

For more information about the extensibility app, see http://help.sap.com/s4hana <Your SAP S/4HANA release> SAP NetWeaver for SAP S/4HANA General Functions for Key
Users Extensibility .

Further Extensibility Entities

Business Add-Ins (BAdIs)

The following BAdIs are available for extensibility purposes:

You can nd the BAdIs under Financial Supply Chain Management Cash and Liquidity Management Bank Account Management Business Add-Ins (BAdIs) :

BAdI: Field Statuses and Field Checks (FCLM_BAM_FIELDS_CTRL)

You can use this BAdI to de ne the following:

Field statuses for elds that are used in bank account master data, for example, whether a eld is read-only, changeable, mandatory, or hidden.

To do so, you can either create your own implementation or use the default implementation FCLM_BAM_FIELDS_CTRL.

 Note
In addition to this Business Add-In, you can also use the Customizing activity Manage Field Status Groups to control the elds on the app screens. The settings made
for eld status groups take precedence over the default BAdI implementation FCLM_BAM_FIELDS_CTRL.

Additional checks for bank account master data.

Whether it is mandatory for users to enter a note when they approve or reject a work ow request.

BAdI: Bank Account Number Mapping Between BAM and HBA (FCLM_BAM_HBACCT)

You can use this BAdI to de ne how to map bank account numbers to elds in a house bank account. For example, due to the length limit of a house bank account number, you
can use this BAdI to specify another eld to store the bank account number, for example, Alternative acct no..

BAdI: Payment Approval Pattern Determination (FCLM_BAM_SIGNATORY)

You can use this BAdI to override the payment approval patterns de ned in Customizing activity De ne Settings for Bank Account Master Data with your own logic and
de nition.

More Information
For a general description of the extensibility options and procedures of SAP Fiori apps, see section Extensibility in the SAP S/4HANA UI Technology Guide .

Manage Bank Accounts - Bank Hierarchy View

With this app you can get an overview of your bank accounts in the bank hierarchy view and maintain bank account groups and cash pools.

Key Features
Check your bank accounts in the Bank Hierarchy view and your self-de ned views.

Create, display, edit, and delete bank account groups.

Create, display, edit, and delete cash pools, as well as perform cash concentration.

Supported Device Types

This is custom documentation. For more information, please visit the SAP Help Portal 39
2/24/2024
Desktop

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps

App Extensibility: Manage Bank Accounts

Use
You can extend the Manage Bank Accounts app according to your business needs for diﬀerent aspects. For this purpose, the following extensibility options are available:

Extension Options Use

CDS view VFCLMBAMHNATTR in structure FCLM_BAM_S_HIERNODE_ATT Allows you to add additional columns for displaying bank account attributes

More Information
For a general description of the extensibility options and procedures, see Extensibility in the SAP S/4HANA UI Technology guide.

Manage Work ows - For Bank Accounts

With this app you can check the prede ned work ow for maintaining bank accounts and con gure work ows for bank account management according to your company's
requirements.

Key Features
Check the prede ned work ow for maintaining bank accounts

Check work ow details, such as status, validity period, and preconditions for starting the work ow

Create new work ows by copying existing ones

You can de ne work ow processes for bank account management according to your company's requirements by de ning preconditions, step sequence, and recipients.

If you need a work ow for reviewing bank accounts, you can create one by following the steps in the Test Script document at https://rapid.sap.com/bp/scopeitems/J77 .

Activate and deactivate work ows

De ne an order for activated work ows

The system evaluates the order and the preconditions of each activated work ow to determine which work ow to trigger for diﬀerent bank accounts and scenarios.

Delete an existing but deactivated work ow.

How-to Video (English only)

This is custom documentation. For more information, please visit the SAP Help Portal 40
2/24/2024

Open this video in a new window

 Note
All videos are available in English only. Captions/subtitles are available for multiple languages. Simply click the CC button at the bottom of the video player to see which languages
are supported.

Supported Device Types

Desktop

Tablet

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps

Monitor Review Status

Use
With this app you can monitor the review status of bank accounts selected for account reviews.

Key Features
Search for bank accounts that have been selected for review by the following parameters:

Request title

Review status

Bank

Country

Contact person who is responsible for reviewing the bank account

Account holder of the bank account

Check the review status of a certain bank account

Check the percentage of reviewed bank accounts in all requests and completed requests

Send a reminder to the contact persons who are responsible for account reviews

 Note
This app is based on a diﬀerent UI technology, so there are slight diﬀerences from the other SAP Fiori apps.

Supported Device Types

Desktop

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps

My Bank Account Worklist

Use
With this app you can check and process your bank-account-related work ow requests that are not yet completed before the upgrade to SAP S/4HANA 1709.

Key Features
Check and process the received requests that are to beyou will approve or process for the following activities:

Opening a bank account

Changing a bank account

Maintaining a signatory in multiple bank accounts

This is custom documentation. For more information, please visit the SAP Help Portal 41
2/24/2024
Reviewing bank accounts

Closing a bank account

Forward a request to another colleague, if needed

Monitor all the bank account related change requests in your responsible area

 Note
This app is based on a diﬀerent UI technology, so there are slight diﬀerences from the other SAP Fiori apps.

Supported Device Types

Desktop

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps

App Extensibility: My Bank Account Worklist

Use
You can extend the My Bank Account Worklist app according to your business needs for diﬀerent aspects. For this purpose, the following extensibility options are available:

Extension Options Use

Customizing include CI_AMD_EXT in table FCLM_BAM_AMD Allows you to add additional elds in the bank account master data

Customizing activity Manage Field Status Groups and BAdI: Field Statuses and Field Checks Allow you to do the following:
(FCLM_BAM_FIELDS_CTRL)
De ne eld status for elds used in bank account master data

De ne additional eld checks for bank account master data

More Information
For a general description of the extensibility options and procedures, see Extensibility in the SAP S/4HANA UI Technology guide.

My Inbox - For Bank Accounts

With this app you can check and process your work ow tasks dealing with bank account master data in various scenarios.

Key Features
Process your work ow tasks in the following scenarios:

Opening a bank account

Modifying a bank account

Maintaining a signatory in multiple bank accounts

Reviewing bank accounts

Closing a bank account

Reopening a bank account

Approve, reject, claim, release, suspend, and forward a task

Sort, group, and search for tasks

View task-speci c details

Add attachments and comments

In addition, the app supports the following technical features and options:

Send emails

You can send an email from this app containing a URL to the selected information in this app.

Share in SAP Jam

If your company uses SAP Jam groups, you can post your comments about a task there.

This is custom documentation. For more information, please visit the SAP Help Portal 42
2/24/2024
Supported Device Types
Desktop

Tablet

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps
App Extensibility: My Inbox

App Extensibility: My Inbox - For Bank Accounts

Use
You can extend the My Inbox - For Bank Accounts app according to your business needs for diﬀerent aspects. For this purpose, the following extensibility options are available:

Change the list view (S2)

Extend the application with additional views

Further Extensibility Entities

Business Add-Ins (BAdIs)

To extend this app and add custom code in the Task Gateway Service, you can use the following Business Add-Ins:

BAdIs in the Back-End System

The BAdI below is only relevant if you are implementing the app for your SAP Business Work ow.

Before Update BAdI (/IWWRK/BADI_WF_BEFORE_UPD_IB)

You can use BAdI /IWWRK/BADI_WF_BEFORE_UPD_IB to if you want to execute an action before the work item is updated with the user decision.

For more information, see SAP Help Portal at http://help.sap.com under Technology Platform SAP Gateway SAP Gateway 2.0 Content Information Content Guide
SAP Gateway Content Guide SAP Gateway Supported OData Channel Scenarios Work ow Services Work ow Task Service: Central Hub Deployment with IW_BEP
Backend Installation Work ow User Exits .

BAdI in the Gateway System

Task Gateway: Change subject in query (/IWPGW/BADI_TGW_TASK_QUERY)

You can use this BAdI to change the task title for all items on the list screen.

For more information, see SAP Help Portal at http://help.sap.com under Technology Platform SAP Gateway SAP Gateway 2.0 Content Information Content Guide SAP
Gateway Content Guide SAP Gateway Supported OData Channel Scenarios Work ow Services Work ow Task Service: Central Hub Deployment with IW_BEP Backend
Installation Work ow User Exits .

Extension Points

The following extension points are available:

View Extension Point Use

S2.view.xml CustomerExtensionForObjectListItem Allows you to replace the list item template with your custom
list item template on the list screen. Make sure that the ID of
your custom list template is the same as the ID of the standard
list item template.

ViewSubstitution.view.xml CustomerExtensionForSubstitutionRowHeader Allows you to add columns in the substitution table.

ViewSubstitution.view.xml CustomerExtensionForSubstitutionRowData Allows you to add column list items in the substitution table.

UI Controller Hooks

To plug in and execute custom code to this app, for example, the following hooks are available in the controller code:

Controller Hook Use

S2.controller.js extHookGetCustomFilter Allows you to create custom lters that can be used for ltering
the work ow.

S2.controller.js extHookChangeFilterItems Allows you to replace the standard lters with custom lters
based on the lter key.

This is custom documentation. For more information, please visit the SAP Help Portal 43
2/24/2024

Controller Hook Use

S2.controller.js extHookChangeSortConfig Allows you to change those properties that can be used for
sorting the work ow tasks.

S2.controller.js extHookChangeGroupConfig Allows you to change those properties that can be used for
grouping the work ow tasks.

S2.controller.js extHookChangeMassApprovalButtons Allows you to add, remove, and change the action buttons on
the list screen in mass action mode.

S2.controller.js extHookGetPropertiesToSelect Allows you to retrieve additional attributes for Task entity from
the back-end system.

Forward.controller.js extHookChangeListSizeLimit Allows you to change the number of recipients displayed on the
forward screen.

ViewSubstitution.controller.js extHookAddFooterButtonsForSubs Allows you to add buttons for the substitution screen.

S2_TaskList.controller.js extHookChangeFooterButtonsForExpertMode Allows you to add, modify or delete the footer buttons, which
are displayed once the task is selected in the expert view.

More Information
For a general description of the extensibility options and procedures, see Extensibility in the SAP S/4HANA UI Technology guide.

My Sent Requests
With this app you can track bank-account-related requests that you have sent.

Key Features
Check your requests in terms of request status, action (what has been done in the request), next processor, creation date, and last change date

View change request details, including approval history

Navigate to see bank account details

Filter or search for a sent request

You can search by request ID or request title.

In addition, the app supports the following technical features and options:

Send emails

You can use this app to send an email containing a URL to the selected information in this app.

Share in SAP Jam

If your company uses SAP Jam groups, you can post your comments about a task there.

Save as tile

You can create a tile that uses the current selection criteria as default settings.

Supported Device Types

Desktop

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps

My Sent Requests - To Be Discontinued

Use
With this app you can track the bank-account-related requests that you have sent before the upgrade to SAP S/4HANA 1709.

Key Features
Check your requests in terms of request status, step, history, next processor, date of creation, and last change.

Send a reminder to the current processor.

This is custom documentation. For more information, please visit the SAP Help Portal 44
2/24/2024

 Note
This app is based on a diﬀerent UI technology, so there are slight diﬀerences from the other SAP Fiori apps.

Supported Device Types

Desktop

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps

App Extensibility: My Sent Requests

Use
You can extend the My Sent Requests app according to your business needs for diﬀerent aspects. For this purpose, the following extensibility options are available:

Extension Options Use

Customizing include CI_AMD_EXT in table FCLM_BAM_AMD Allows you to add additional elds in the bank account master data

De ne additional eld checks for bank account master data

More Information
For a general description of the extensibility options and procedures, see Extensibility in the SAP S/4HANA UI Technology guide.

Payment Statistics

Purpose
With this app, you can display the Key Performance Indicator (KPI) Payment Statistics. You can check the amount and number of critical payments made within 90 days through SAP
Bank Communication Management using diﬀerent ltering criteria.

Calculation Logic
For more information about how the numbers on the app tile and the number in the top-right corner of the app are calculated, see Calculation Logic: Payment Statistics.

Key Features
View the number and amount of critical payments. The following types of payments are considered as critical:

New: payments that are newly made in the system, for example, when the payment batch is just created

In Approval Process: payments that are to be approved

Sent to Bank: payments that are successfully sent to relevant banks for actual transfers to take place

Exceptions: payments that have encountered issues, for example, payments that are rejected by approvers, payment batches that are partially processed, payment
medium creation errors, and so on.

Display critical payments by the following dimensions:

By Status

By Company

By House Bank

By Processing Days

By Payment Method

By Currency

If your company uses SAP Jam, you can post comments there and you can also send emails from this app.

 Note
From this app you can access other apps directly.

These linked apps must be already available already in your system. If not, you have to implement them along with this app.

This is custom documentation. For more information, please visit the SAP Help Portal 45
2/24/2024
Check Cash Flow Items

Supported Device Types

Desktop

Tablet

Extensibility

 Note
This app is not extensible.

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library
Additional Implementation Activities for All Finance Apps
Con guration Settings: Payment Statistics
Calculation Logic: Payment Statistics

Con guration Settings: Payment Statistics

Use
This document contains con guration information for the Payment Statistics app.

SAP Jam Integration

For information on how to con gure SAP Jam, see http://help.sap.com/sapjam .

SAP Smart Business Modeler

Before you can use this app, you need to con gure it using the SAP Smart Business Modeler. For more information, see SAP Smart Business Modeler Apps.

 Note
You can edit the following details related to an SAP-delivered evaluation:

Parameters values

Filter values

Thresholds

Semantic object and action

KPI: Payment Statistics

KPI ID: .K.1465363683199

KPI Description:
With Payment Statistics, you can check payment statistics by status, house bank, company, currency, processing days and payment
method. This KPI allows you to filter and drill down by various dimensions.

Goal Type: Range

Evaluation: In the Last 90 Days

Evaluation ID: .E.1465370796428

Evaluation Description:
With Payment Statistics, you can check payment statistics by status, house bank, company, currency, payment method and processing
days. This KPI allows you to filter and drill down by various dimensions.

Targets, Thresholds, and Trend

Parameter Value

Goal Type Range

This is custom documentation. For more information, please visit the SAP Help Portal 46
2/24/2024

Parameter Value

Value Type Fixed Value

Critical (Not applicable)

Warning (Not applicable)

Target (Not applicable)

Trend (Not applicable)

This table shows some example values.

Input Parameters and Filters

Input Parameters

Input Parameter Operator Example Value Explanation

P_DisplayCurrency Equal to EUR Choose a currency in which the currency

amounts are to be displayed. Ensure that
exchange rates for this currency exist in your
SAP S/4HANA system.

An entry in this eld is required.

P_NumberOfProcessingDays Equal to 90 Enter the number of days from the rst day
when payments were created to today. The
app aggregates all the payments that have
been created during this period.

An entry in this eld is required.

The following tables show the input parameters, lters, and some precon gured example values. Use your own values where required, according to the data in your backend system.

Drill-Down: By Status

View ID: .V.1467613184977

View Title: By Status

Measures and Dimensions:

Parameter Value

Dimension Status

Measures
Number of Payments

Payment Amount in Display Currency

Table

Default Colors

Limit Data Records: 200

Calculation Logic: Payment Statistics

On the App Tile

On the app tile, the app displays the top three types of payments with the highest amounts within 90 days in display currency.

The equation below illustrates how the amount for each type is calculated and is followed by an explanation:

The numbers on the app tile are calculated as follows:

This is custom documentation. For more information, please visit the SAP Help Portal 49
2/24/2024

1. 1.The app calculates the total payment amounts of the following four types of payments made within 90 days.

The amount of each type of payments is calculated by subtracting the amount of incoming payments from outgoing payments. If a payment is made in a currency other than
the current display currency, the amount will be converted according to exchange rates.

New

In Approval Process

Sent to Bank

Exceptions

2. The app selects the three types with the highest amounts and displays them on the app tile in descending order.

In the Top-Right Corner of the App

In the top-right corner of the app, the app displays the total amount of critical payments made within 90 days in display currency.

The equation below illustrates how this number is calculated and is followed by an explanation:

The app calculates the total amount of critical payments made within 90 days by adding up the amounts of the four types of critical payments.

The calculation logic of how the amount of an individual type of payments is illustrated in the On the App Tile section.

Track Bank Transfers

Use
With this app you can view information about the bank-to-bank transfers of cash that you have made during the past 3 months. You can lter or sort such information by several
dimensions.

This app is available for the role Cash Manager and Cash Management Specialist.

Key Features
Display the total number of incomplete bank transfers

Categorize bank transfers according to diﬀerent statuses

Filter or sort bank transfers in a given status

Display details about a bank transfer

In addition, the app supports the following technical features and options:

SAP Jam integration

If your company uses SAP Jam, you can share information with a certain group of people in SAP Jam and receive feedback from them.

This is custom documentation. For more information, please visit the SAP Help Portal 50
2/24/2024
Save as tile

You can create a tile that uses the current selection criteria as default settings.

Navigation Targets
The app enables users to access other apps directly (for example to display detailed information).

 Note
These linked apps have to be already available in your system landscape or you have to implement them along with this app.

Make Bank Transfers

Check Cash Flow Items

Component for Customer Incidents

FIN-FSCM-CLM-COP

Related Information
App-Speci c Implementation Information in the SAP Fiori apps reference library

App Extensibility: Track Bank Transfers

Use
You can extend Track Bank Transfers according to your business needs for diﬀerent aspects. For this purpose, the following extensibility options are available for developers:

Bank Transfer Status

You can extend the statuses of bank transfer and add new icon tabs.

Columns of Bank Transfer List

You can extend the columns of bank transfer list and add new columns.

Bank Transfer Details Fields

You can extend the elds that appear on the Bank Transfer Details screen when you click a record of bank transfer.

Filter and Sort Options

You can extend the lter and sort options that appear on the View Setting screen.

Action Buttons

You can extend the action buttons that appear on the footer bar.

Bank Transfer Status

popover.fragment.xml extPopFields FCLM_CP_TRACK_SRV FCLM_S_TRACK_INCL Superclass:

/IWBEP/IF_MGW_APPL_SRV_RUNTIME;/IWBEP/CL_MGW_PUSH_ABS_MODEL

Method: GET_ENTITYSET DEFINE

Further Extensibility Entities

Extension Includes

In addition to the extension includes described above, the following extension includes are available:

DDIC Extension Include Use

FCLM_S_TRACK FCLM_S_TRACK_INCL Allows you to extend the bank transfer tracking

For more information about extension includes, see section Extensibility in the SAP S/4HANA UI Technology guide.

UI Controller Hooks

To plug in and execute custom code, the following hooks are available in the controller code:

Controller Hook Use

TrackTransfer extHookViewAttributes Allows you to extend the initialization of the controller

TrackTransfer extHookMdyColumns Allows you to extend the columns of bank transfer list

TrackTransfer extHookAddStatus1 Allows you to extend the statuses of bank transfer

extHookAddStatus2

TrackTransfer extHookMdyVSItems Allows you to extend the sort and lter options

Display of UI Controls

The following UI controls can be hidden on the app UI:

View Controller ID Use

TrackTransfer.view.xml trackTabExp Allows you to hide icons for the bank transfer status

trackTabIni

trackTabInApp

trackTabApped

trackTabSend

trackTabCmp

This is custom documentation. For more information, please visit the SAP Help Portal 52
2/24/2024

View Controller ID Use

TrackTransfer.view.xml colTitleDate Allows you to hide columns of the bank transfer list

colTitleFrom

colTitleTo

colTitlePayMethod

colTitleDetail

colTitleNote

colTitleAmount

colTitleRunID

colTitleFromCompany

colTitleToCompany

More Information
For a general description of the extensibility options and procedures, see Extensibility in the SAP S/4HANA UI Technology guide.

This is custom documentation. For more information, please visit the SAP Help Portal 53
2/24/2024

Cash and Liquidity Management

 Note
This solution is intended for business use only. You should not use it for personal bank accounts or personal cash operations.

Bank Relationship Management

Cash Operations

Liquidity Management

Related Information
Business Function: Cash and Liquidity Management
Con guration Guide for SAP S/4HANA Finance for Cash Management
Data Setup Guide for SAP S/4HANA Finance for Cash Management

Business Function: Cash and Liquidity Management

Use
The Basic Cash Management Capability

 Note
Before you use the basic cash management capability that is delivered with SAP S/4HANA, you need to switch oﬀ the business function FIN_FSCM_CLM and select Basic Scope in
the Customizing activity De ne Basic Settings.

Features

The basic cash management capability oﬀers the following basic functions:

Manage banks and house banks (only a subset of elds that are needed for enabling the payment process)

De ne bank accounts and house bank accounts (only common attributes are supported)

Display bank accounts in a list view

Import and export bank accounts

Basic Cash Position and Liquidity Forecast ( transactions FF7AN and FF7BN)

Edit and display memo records ( transactions FF63 and FF65)

Cash concentration via payment advices ( transaction FF73)

Integration

The basic cash management capability can integrate with the following data sources:

Memo Records

Financial Operations

Treasury and Risk Management (FIN-FSCM-TRM)

Consumer and Mortgage Loans (FS-CLM)

Contract Accounts Receivable and Payable (FI-CA)

Sales and Distribution (SD)

Materials Management (MM)

SAP S/4HANA Finance for Cash Management

This is custom documentation. For more information, please visit the SAP Help Portal 2
2/24/2024

 Note
To use SAP S/4HANA Finance for cash management, you need to switch on the business function FIN_FSCM_CLM and select Full Scope for Cash Management Scope in the
Customizing activity De ne Basic Settings. Before you switch on this business function, contact your SAP Account Executive about the license for SAP S/4HANA Finance for cash
management.

Technical Name

Technical Name of Business Function FIN-FSCM-CLM

Type of Business Function Enterprise BF

Available From SAP_FIN 700

S4CORE

Technical Usage SAP NetWeaver 7.4 Support Package Stack 05

Application Component FIN_FSCM_CLM

Required Business Function Not relevant

Features

With this business function, you can enable SAP S/4HANA Finance for cash management to gain the full range of functions for this solution. The following new and improved functions
and processes are available to you:

Manage banks and house banks

De ne bank accounts and house bank accounts

De ne payment signatories and overdraft limits for bank accounts

Display bank accounts in the bank hierarchy view, the list view, and user-de ned views based on bank account groups

Create cash pools based on bank account groups and perform cash concentration

Implement work ow or dual control processes for opening, modifying, closing, reopening, and reviewing bank accounts

Initiate bank account reviews and monitor the review status

Keep track of foreign bank accounts and responsible signatories

Perform cash operation tasks such as monitoring cash positions, making bank transfers, and approving payments

Forecast the liquidity trend and analyze the actual cash ows using various dimensions

Develop and analyze liquidity plans to ensure payment obligations and assist funding decisions

Use prede ned local BI Content to extract cash management data for analytical purposes

Integration
This business function is closely integrated with the following components:

Bank Communication Management (FIN-FSCM-BNK)

The component is integrated for functions involving bank statements, bank payments, bank transfers, and so on.

 Note
Business function FIN-FSCM-BNK is required for use of this component.

Memo Records

Financial Operations

Treasury and Risk Management (FIN-FSCM-TRM)

Consumer and Mortgage Loans (FS-CLM)

Contract Accounts Receivable and Payable (FI-CA)

Materials Management (MM)

Sales and Distribution (SD)

Classic Cash Management

Manual Entry of Bank Cash Balances

SAP Liquidity Planner

Flexible Real Estate Management (RE-FX) (FF7BN only)

Prerequisites
You have installed the following components as of the version mentioned:

Type of Component Component

This is custom documentation. For more information, please visit the SAP Help Portal 3
2/24/2024

Type of Component Component

Software Component SAP_FIN 700

S4CORE

SAP NetWeaver SAP NetWeaver 7.4 Support Package Stack 05

Technical Component SAP NetWeaver Business Client 3.5 or 4.0

More Information
Cash and Liquidity Management

Con guration Guide for SAP S/4HANA Finance for Cash Management

Purpose and Target Groups

This guide describes the activities that you need to perform in order to use SAP S/4HANA Finance for cash management.

Release SAP S/4HANA 1709

Application Component FIN-FSCM-CLM

Target Groups (Roles) Application Consultants

 Note
For app-speci c implementation information, such as business catalogs and OData services, search for the app in the SAP Fiori Apps reference library.

Prerequisites
You need to have ful lled the following prerequisites before you can continue with the activities documented in this guide:

You have installed SAP S/4HANA 1709

For more information, see the Installation Guide of SAP S/4HANA 1709 at https://help.sap.com/viewer/p/SAP_S4HANA_ON-PREMISE .

You have nished the migration.

For more information, see the Conversion Guide and Simpli cation List of SAP S/4HANA 1709 at https://help.sap.com/viewer/p/SAP_S4HANA_ON-PREMISE.

You have assigned roles to users.

For more information about security-relevant authorization objects, see the Security Guide of SAP S/4HANA 1709 at https://help.sap.com/viewer/p/SAP_S4HANA_ON-
PREMISE.

You have switched on the business function FIN_FSCM_CLM and selected Full Scope for Cash Management Scope in the Customizing activity De ne Basic Settings.

You can nd this Customizing activity under Financial Supply Chain Management Cash and Liquidity Management General Settings .

Make sure that you have applied all the notes listed in SAP Note 2493348 (SAP S/4HANA 1709: Release Information Note for Finance) appropriate to your product version.

Your user is con gured with the required back-end authorization and front-end authorization.

You have con gured virus scan pro les for le uploads.

For more information, see the chapter “Virus Scanning in File Uploads” in the Security Guide of SAP S/4HANA 1709 at https://help.sap.com/viewer/p/SAP_S4HANA_ON-
PREMISE.

More Information
Con guration for Bank Relationship Management

Con guration for One Exposure from Operations

Con guration for Cash Operations

Con guration for Liquidity Management

Con guration Tips for SAP Liquidity Planner Customers

Con guration for Bank Relationship Management

Use
Bank Relationship Management enables cash managers to centrally manage the bank accounts in a company, for example, creating, modifying, closing bank accounts, as well as
performing bank account reviews.

This is custom documentation. For more information, please visit the SAP Help Portal 4
2/24/2024
Related Information
Bank Account Master Data
Precheck for the Attachment Function
Payment Approval Process
Cash Pools for Cash Concentration
Approval Processes for Bank Account Management
Extensibility Options
ICF Services

Bank Account Master Data

Number Ranges for Bank Account Technical IDs

In bank account master data, each bank account acquires a technical ID upon creation. To de ne the rules for the assignment of technical IDs, perform the following Customizing
activities under Financial Supply Chain Management Cash and Liquidity Management Bank Account Management Basic Settings :

1. In the Customizing activity De ne Number Ranges for Bank Account Technical IDs, de ne number ranges for bank account technical IDs.

2. In the Customizing activity De ne Settings for Bank Account Master Data, on the Bank Account Master Data Setting screen, specify a number range for the Tech. ID No.
Rang eld.

Number Ranges for Change Requests

The system automatically assigns a number to a change request once it is created. To con gure the rules for assigning change request IDs, perform the following Customizing
activities under Financial Supply Chain Management Cash and Liquidity Management Bank Account Management Basic Settings :

1. In the Customizing activity De ne Number Ranges for Work ow Change Requests, de ne number ranges for change requests.

2. In the Customizing activity De ne Settings for Bank Account Master Data, on the Bank Account Master Data Setting screen, specify a number range for the Req. No. Rang
eld.

Bank Account Types

The bank account type is one of the attributes in the bank account master data. You can de ne different types of accounts to suit different business purposes. Account types can be
used as an analysis dimension in reporting and planning. Using bank account types, you can also de ne different approval patterns for bank accounts of different types. For more
information, see Payment Approval Process.

To maintain bank account types, start the Customizing activity De ne Settings for Bank Account Master Data and de ne account types on the Account Type De nition screen. You
can nd this activity under Financial Supply Chain Management Cash and Liquidity Management Bank Account Management Basic Settings .

Bank Statement Import Methods

Bank statements can be imported using diﬀerent methods, for example via SWIFT or by manual import. For each bank account, you can specify one of the de ned methods as the
Import Method for End-of-Day Statements and another as the Import Method for Intra-Day Statements.

To de ne the import methods, start the Customizing activity De ne Settings for Bank Account Master Data and, on the De ne Import Methods for Bank Statements screen, de ne
method IDs and descriptions. You can nd this activity under Financial Supply Chain Management Cash and Liquidity Management Bank Account Management Basic
Settings .

Bank Statement Monitor

For information about the con guration for the Bank Statement Monitor, see Bank Statement Monitor.

Bank Statement Monitor

You can make settings for the Bank Statement Monitor using either of the following options:

De ne settings in the Manage Bank Accounts app.

You can nd the settings in the Bank Statement Data section on the Bank Relationship tab.

De ne settings in the Customizing activity Settings for Bank Statement Monitor (transaction FTE_BSM_CUST).

 Note
When the settings are maintained in both places, the settings de ned in the Manage Bank Accounts app override the settings in transaction FTE_BSM_CUST.

Settings for the Bank Statement Monitor app

To monitor a bank account in the Bank Statement Monitor app, make sure the following settings have been made:

The Processing Status indicator has been set.

When this indicator is set for a bank account, the system determines that the bank statements of this bank account are monitored by the Bank Statement Monitor app.

This is custom documentation. For more information, please visit the SAP Help Portal 5
2/24/2024
The processing status indicates whether the bank statement has been processed correctly.

Make sure there is at least one valid house bank account de ned on the Connectivity Path tab of the Manage Bank Accounts app.

In addition, the following settings are relevant:

Interval and Interval Unit: You can specify how often the bank statements for a bank account are imported to your system.

Factory Calendar ID: You can specify a calendar so that the Bank Statement Monitor ignores the import status of bank statements on non-working days.

Settings for the Bank Statement Monitor SAP GUI Program

The following settings are relevant to the transaction FTE_BSM:

Processing Status: It determines whether the bank statements of a bank account are monitored.

The processing status indicates whether the bank statement has been processed correctly.

Diﬀerence Status: It determines whether this status appears in the Bank Statement Monitor.

The diﬀerence status indicates whether there is a diﬀerence between the internal general ledger account balance and the bank statement balance.

Diﬀerence Amount: You specify a tolerance amount for the diﬀerence status.

Serial Number Status: It determines whether this status appears in the Bank Statement Monitor.

The serial number status indicates whether the sequence of the last ve bank statements is complete.

Reconciliation Status: It determines whether this status appears in the Bank Statement Monitor.

The reconciliation status indicates whether there are open items in the internal account.

Display Item

It determines the position at which the bank statement for this account is displayed in the Bank Statement Monitor.

Interval and Interval Unit: You can specify how often the bank statements for a bank account are imported to your system.

Factory Calendar ID: You can specify a calendar so that the Bank Statement Monitor ignores the import status of bank statements on non-working days.

Precheck for the Attachment Function

Context
You are recommended to perform a precheck on the prede ned attachment document type BAM before you go live. To do so, proceed as follows:

Procedure
1. Run transaction DC10.

2. Check whether the prede ned class has the following attributes:

Class Type: 017

Class: SAP_FCLM_BAM_DOC

If the class does not have the correct attributes assigned to it, continue with the next step, which entails running a report that will x this issue.

3. Start transaction SE38 and then run the report FCLM_BRM_GENERATE_CLASS_CHAR.

The report helps you generate the class and characteristics that are required when the document type BAM is used.

Payment Approval Process

With Bank Relationship Management, you can de ne diﬀerent approval processes for diﬀerent bank accounts by con guring signatory groups and approval patterns. To use this
function, you need to perform the following steps:

Enable Payment Approval Process

To enable the payment approval process with payment signatories, you rst need to perform the following Customizing activities for Bank Communication Management, under
Financial Supply Chain Management Bank Communication Management :

1. In the Customizing activity Payment Grouping Rule Maintenance , create a rule for payment approvals.

In the rule de nition, you can use payment attributes (such as company code, payment method, and currency) to de ne the coverage of the payment approval process. The
payment approval process applies only to payments that are covered by the rule.

2. In the Customizing activity Payment Grouping Additional Criteria for Payment Grouping , de ne a grouping method for the rule you have de ned.

To use the payment approval process with payment signatories in Bank Account Management, you need to group payment batches by house bank account. To do so, specify
the rule ID and enter HKTID as the Grpng. Field 1. You can specify another criterium for payment grouping in Grpng. Field 2, if necessary.

This is custom documentation. For more information, please visit the SAP Help Portal 6
2/24/2024
3. (Optional) If you want to de ne a scenario in which payment approval is not required, for example, for payments with small amounts, you can de ne a rule in the Customizing
activity Release Strategy Marking Rules for Automatic Payment (No Approval) .

4. (Optional) If a signature is required when users approve payments, you can con gure this in the Customizing activity Basic Settings Basic Setting for Approval by
creating an entry and selecting the Signature Required checkbox.

5. (Optional) To de ne the signature method for approving payments, you can con gure this in the Customizing activity Release Strategy Digital Signatures Specify
Signature Method for Approval Using Simple Signature .

Con gure Payment Signatories

After you enable the payment approval process in Bank Communication Management, you can proceed to con gure the signatories and payment approval patterns in Bank Account
Management.

1. Enable the signatory function

To do so, start the Customizing activity Enable Signatory Control under Financial Supply Chain Management Cash and Liquidity Management Bank Account
Management and enable the function by assigning the required function modules.

2. De ne signatory groups, approval patterns, and pattern priorities

To do so, start the Customizing activity De ne Settings for Bank Account Master Data under Financial Supply Chain Management Cash and Liquidity Management
Bank Account Management Basic Settings and con gure the following:

a. De ne signatory groups

You can group signatories into diﬀerent business groups. For example, in your company, payments made on salary accounts need to be approved rst by the HR
department and then by the Finance department. In this case, you can de ne two signatory groups respectively for users in these two departments.

In the bank account master data, you can de ne multiple signatories for each bank account. The system automatically sends the approval request to eligible signatories
according to the signatory group they belong to, the validity of the signatory, and the amount limit the signatory is entitled to.

b. De ne approval patterns

Approval patterns represent diﬀerent approval processes. To de ne an approval pattern, you specify the signatory groups involved and their corresponding approval
sequences.

You can con gure the approval patterns for the following scenarios:

The payment is approved by a single signature

For this, de ne a sequential approval pattern with only one step.

The payment is approved by a joint signature where more than one signature is required and signatories approve the payment in a certain order.

For this, de ne a sequential approval pattern with two to four signatory groups.

The payment is approved by a joint signature where more than one signature is required and signatories approve the payment regardless of the sequential
order.

For this, de ne a non-sequential approval pattern with two or more signatory groups.

c. Assign approval patterns

You assign approval patterns to bank account types and company codes. For information about how the assignment works, see the documentation for the Customizing
activity De ne Settings for Bank Account Master Data.

Cash Pools for Cash Concentration

With Bank Account Management, you can create cash pools based on a bank account group structure and use cash concentration to centrally manage your cash. To enable the cash
concentration function, de ne the following in Customizing activities under Financial Accounting Bank Accounting Business Transactions Payment Transactions :

Under Payment Request, de ne clearing accounts for receiving banks in the Customizing activity De ne Clearing Accts for Receiving Bank for Acct Transfer.

Under Payment Request, de ne clearing accounts for paying banks in the Customizing activity De ne Clearing Accounts for Cross-Country Bank Account Transfers.

Under Payment Handling -> Bank Clearing Account Determination, de ne the bank clearing account determination logic in the Customizing activity De ne Account
Determination.

Approval Processes for Bank Account Management

For risk control reasons, most companies implement approval processes for master data management. For bank account management, you can use SAP Business Work ow or a
simple dual control process to safeguard your bank account master data in the scenarios listed below.

 Note
If you use SAP NetWeaver Business Client (NWBC) as the user interface, dual control is not supported.

Opening a new bank account, including copying a bank account to create a new bank account

Making changes to a bank account, including changing a signatory in multiple bank accounts

Closing a bank account

Reopening a bank account that is already closed

This is custom documentation. For more information, please visit the SAP Help Portal 7
2/24/2024
Reviewing bank accounts

 Note
The approval process for reviewing bank accounts can only be implemented using SAP Business Work ow.

Related Information
Con guration for Work ows
Con guration for Dual Control

Con guration for Work ows

SAP provides prede ned work ow processes for opening, modifying, closing, and reviewing bank accounts. You can use the prede ned work ows or design your own work ows
according to your company's needs.

More Information
SAP Business Work ow/WebFlow

Related Information
Settings for Using Work ows
Extensibility for Prede ned Work ows
Prede ned Work ows

Settings for Using Work ows

Context
To use SAP Business Work ow for bank account management, follow the steps below to make the necessary settings:

Procedure
1. To enable the work ow function for bank account management, start the Customizing activity De ne Basic Settings and set the Activate via Work ow indicator for Bank
Account Revision. You can nd this Customizing activity in Customizing under Financial Supply Chain Management Cash and Liquidity Management General Settings
De ne Basic Settings .

2. To activate a work ow template that you want to use for bank account management, activate the corresponding event type linkage in the Customizing activity Maintain the
Event Type Linkage for Triggering Work ow Processes under Financial Supply Chain Management Cash and Liquidity Management Bank Account Management :

By default, the linkage for the prede ned work ow template WS78500050 is activated. If you choose to use this template, you do not need to do anything.

If you want to use the work ow template WS74300043, deactivate the linkage for WS78500050 and then activate the linkage for WS74300043.

 Note
Make sure there is only one linkage activated for the event Created in BOR object FCLM_CR. If you have activated both the linkages for WS74300043 and
WS78500050, WS74300043 is used.

If you want to use your own work ow template, you can add and activate a new entry and then deactivate the default one.

3. De ne the organization and staﬃng for your company.

To create new organization and staﬃng, use transaction PPOCE.

To change the existing organization and staﬃng, use transaction PPOMW.

For more information, see the documentation in the transaction by choosing Help Application Help .

4. To de ne responsibilities for the work ow rules used in your work ow processes, perform the Customizing activity De ne Responsibilities for Rules Used in Work ow Steps
under Financial Supply Chain Management Cash and Liquidity Management Bank Account Management .

 Note
If the agent assignment does not work in accordance with what you have de ned in the responsibilities, check the agent assignment settings of the work ow tasks.

To do so, proceed as follows:

a. In transaction PFTC, specify the work ow task that you want to check.

b. From the menu bar, choose Additional Data Agent Assignment Maintain .

c. Choose the Attributes button.

d. Select General Task and then choose Transfer.

5. For the purpose of changing a payment signatory for multiple bank accounts simultaneously, the system generates a mass change request when the work ow is enabled. To
con gure this mass change request, go to the Customizing activity De ne Basic Settings and de ne a grouping option for Change Request Grouping. You can nd this
Customizing activity under Financial Supply Chain Management Cash and Liquidity Management General Settings .

6. When you make changes to the bank account master data, only elds that are de ned as sensitive elds can trigger the work ow process. To de ne sensitive elds, specify the
elds in the Customizing activity De ne Settings for Bank Account Master Data under Financial Supply Chain Management Cash and Liquidity Management Bank
Account Management Basic Settings . On the Sensitive Fields for Modi cation Process screen, de ne the elds that trigger a work ow process when modi ed.

This is custom documentation. For more information, please visit the SAP Help Portal 8
2/24/2024

Prede ned Work ows

Context
Business Object Repository Object

SAP prede nes a Business Object Repository (BOR) object FCLM_CR for bank account management. In this object, the following two events are de ned:

CREATED: This method is used to trigger the work ow by creating a change request.

PROCESSED: Dialog step in approval process which was processed.

Rules

74300006 FCLM_CASHMGR

The rule assigns a cash manager as the agent.

Cash managers are authorized to approve or reject a change request of creating, changing, or closing bank accounts.

74300007 FCLM_CASHOPER

The rule assigns a cash specialist as the agent.

Cash specialists work under cash managers’ supervision and is responsible for opening, changing, and closing bank accounts.

74300008 FCLM_CASHSYSCOLL

The rule assigns a key user as the agent.

Key users are responsible for making necessary con guration settings for bank accounts and house bank accounts.

74300013 FCLM_REVWOR

This is a xed rule, therefore you cannot de ne responsibility for this rule.

The rule retrieves the contact persons de ned in the bank account master data from the Contact Person eld (on the Bank Relationship tab, under the Internal Contact
Persons section).

Work ow Templates

The following prede ned work ow templates are available:

Work ow Template 78500050 (default work ow template)

Work ow Template 74300043

Work ow Template 78500050

Use
This work ow template is intended for customers who want to use the simpli ed work ow for bank account management. With this work ow template, you can use the following apps
to manage your work ow requests:

My Inbox - For Bank Accounts

My Sent Requests

Extensibility Options
To extend the work ows that are prede ned with this work ow template, you can use the Manage Work ows - For Bank Accounts app.

Work ow Scenarios
In this work ow template, the following work ows are de ned for the typical business scenarios of opening, modifying, and closing bank accounts:

Work ow for opening a new bank account

Work ow for copying a bank account to create a new one

Work ow for modifying a bank account

Work ow for changing a signatory in multiple accounts

Work ow for closing a bank account

Work ow for reopening a closed bank account

In the above work ow scenarios, the following process is de ned:

1. A cash specialist creates a new bank account or performs an action on an existing bank account in the system.

The system triggers a change request and sends the information to a cash manager for approval.

This is custom documentation. For more information, please visit the SAP Help Portal 9
2/24/2024
2. After evaluating the request, the cash manager can either approve or reject the request.

3. Once the cash manager approves the request, the changes to the bank account become eﬀective and the bank account is set with status Active.

Standard Task 78500044 FCLM_APPR

This information is very technical, therefore you only need to read it if you want to understand the technical details of the standard task or you want to enhance the standard task.

Standard task 78500044

Abbreviation FCLM_APPR

Name Decision task to maintain bank account

Method Referenced, Properties

Object type:DECISION

Method: PROCESS

Properties: Object method with dialog

Agent Assignment
The agent assignment depends on the work ow template in use.

Important Elements
The table below explains the important elements in the task container:

Technical Name Description Properties Information

CHANGE_REQUEST Change Request Import, Export This element stores the general data of change requests in database table FCLM_BAM_REQUEST.

TOTAL_STEP Total Steps Import This element stores the total number of steps.

STEP_NAME Step Name Import This element stores the name of the step

DESP_OTR_ALIAS Step Description Import This element stores the OTR text alias string that contains the description text for the current step.

Standard Task 78500046 FCLM_REVW

This information is very technical, therefore you only need to read it if you want to understand the technical details of the standard task or you want to enhance the standard task.

Standard task 78500046

Abbreviation FCLM_REVW

Name Decision task to review bank account

Method Referenced, Properties

Object type:DECISION

Method: PROCESS

Properties: Object method with dialog

Agent Assignment
The agent assignment depends on the work ow template in use.

Important Elements
The table below explains the important elements in the task container:

Technical Name Description Properties Information

CHANGE_REQUEST Change Request Import, Export This element stores the general data of change requests in database table FCLM_BAM_REQUEST.

TOTAL_STEP Total Steps Import This element stores the total number of steps.

STEP_NAME Step Name Import This element stores the name of the step

DESP_OTR_ALIAS Step Description Import This element stores the OTR text alias string that contains the description text for the current step.

This is custom documentation. For more information, please visit the SAP Help Portal 10
2/24/2024

Work ow Template 74300043

Use
This work ow template is intended for the following customers:

Customers who use SAP NetWeaver Business Client (NWBC) as the user interface for bank account management

Customers who want to use the My Bank Account Worklist app and the My Sent Requests - To Be Discontinued app to manage their work ow requests

Extensibility Options
To extend the work ows de ned by this work ow template, you can use the SAP GUI transaction SWDD.

Work ow Scenarios
In this work ow template, the following sub-work ows are de ned for the typical business scenarios for opening, modifying, and closing, and reviewing bank accounts:

74300047 FCLM_AMD_OP (work ow for opening a new bank account)

The following process is de ned with this template:

1. A cash specialist creates a bank account in the system.

The system triggers a change request and sends the information to a cash manager for approval.

2. After evaluating the request, the cash manager can either approve or reject the request.

3. If the cash manager approves the request, the cash specialist opens the bank account at the bank and maintains the necessary information for the bank account in the
system, for example, the bank account number and the IBAN number.

If the bank account is opened in a bank that does not exist in the system, the cash specialist rst creates the bank in the system.

4. A key user nishes the necessary con guration, for example, by creating house bank accounts and assigning these accounts to the newly created bank account.

If the corresponding general ledger accounts are not yet available, the key user rst creates the general ledger accounts.

74300048 FCLM_AMD_MD (work ow for modifying a bank account)

The following process is de ned with this template:

1. A cash specialist modi es a bank account in the system.

The system triggers a change request and sends the information to a cash manager for approval.

2. After evaluating the change request, the cash managers can either approve or reject the request.

3. If the cash manager approves the request, the cash specialist noti es the bank about making the necessary changes. After the cash specialist con rms that the
changes have taken eﬀect at the bank, he or she con rms the corresponding step in the system.

The changes are updated to the bank account master data.

4. A key user updates the con guration if necessary.

For example, if a new currency has been added, the key user creates a house bank account for the new currency and then assigns the house bank account to the bank
account.

74300049 FCLM_AMD_MM (work ow for changing a signatory in multiple accounts)

The process de ned with this template is the same as that de ned for the work ow template 74300048 FCLM_AMD_MD.

74300050 FCLM_AMD_CL (work ow for closing a bank account)

The following process is de ned with this template:

1. A cash specialist closes a bank account in the bank account master data.

The system triggers a change request and sends the information to a cash manager for approval.

2. After evaluating the change request, the cash manager can either approve or reject the request.

3. If the cash manager approves the request, the cash specialist noti es the bank about closing the bank account. After the account is closed at the bank, the cash
specialist con rms corresponding the step in the system.

4. A key user nishes the necessary con guration.

For example, the key user can mark the related house bank accounts as closed in their descriptions to distinguish them from other house bank accounts that are still in
use.

74300065 FCLM_AMD_RV (work ow for reviewing bank account master data)

The following process is de ned with this template:

1. A cash manager selects the bank accounts to be included in a review process.

The system detects the contact person responsible for each selected bank account and sends out a request to each contact person. Each contact person receives a
request that contains all the bank accounts that he or she is responsible for and that have been selected for review.

This is custom documentation. For more information, please visit the SAP Help Portal 11
2/24/2024
The contact persons who are responsible for bank account review are de ned in the Contact Person eld in the bank account master data (on the Bank Relationship
tab, in the Internal Contact Persons section).

2. After reviewing the bank account master data of their responsible bank accounts, account contact persons can either mark the bank account as reviewed or directly
update the master data if they spot any incorrect information.

Modifying the bank account master data may trigger another work ow, depending on the elds that are changed.

3. The contact person completes the request after all the bank accounts in the request are marked as reviewed.

Work ow template 01800002 FCLM_BAM_RO (work ow for reopening a closed bank account)

The following process is de ned with this template:

1. A cash specialist reopens a closed bank account in the system.

The system triggers a change request and sends the information to a cash manager for approval.

2. After evaluating the request, the cash manager can either approve or reject the request.

3. If the cash manager approves the request, the bank account is set back to status Active in the system.

Standard Task 74300047 FCLM_DEC

This information is very technical, you only need to read it if you want to understand the technical details of the standard task or you want to enhance the standard task.

Standard task 74300047

Abbreviation FCLM_DEC

Name Bank Account Management: Decision

Method Referenced, Properties

Object type:FCLM_CR

Method: PROCESS (Process)

Properties: Object method with dialog

Agent Assignment
The agent assignment depends on the work ow template in use.

Important Elements
The table below explains the important elements in the task container:

Technical Name Description Properties Information

INDICATOR_APPROVE Approve Import, Export This element is used for the decision of the current step. When the step is approved, the element is set to X
Indicator

CHANGE_REQUEST Change Import, Export, This element stores the general data of change requests in database table FCLM_BAM_REQUEST.
Request Mandatory

APPROVE_STATUS Approved Import, Mandatory This element stores the next status when the current step is approved.
Status

REJECT_STATUS Rejected Import, Mandatory This element stores the next status when the current step is rejected
Status

DESP_OTR_ALIAS Step Import This element stores the OTR text alias string that contains the description text for the current step.
Description

AGENTDET_BUKRS Company Import This element stores the company code used for agent determination.
Code

AGENTDET_ACCTYPE Account Type Import This element stores the account type used for agent determination.

NEXT_STEP Next Step Import This element stores the next step, so that the system can adjust the UI display to the next step accordingly, once the current
step is completed.

PREV_STEP Previous Step Import This element stores the previous step so that the system can adjust the UI display to the previous step accordingly, once the
current step is rejected.

Extensibility for Prede ned Work ows

If you want to extend the prede ned work ow templates, you can consider the following options:

De ne Responsibility Rules

This is custom documentation. For more information, please visit the SAP Help Portal 12
2/24/2024
To determine the agent assignment in work ows, de ne rules using the function Maintain Rule (transaction PFAC)

To de ne your own rules, you must include the following elements with the exact technical names:

Company Code (technical name: AGENTDET_BUKRS)

Account Type (technical name: AGENTDET_ACCTYPE)

To work with work ow template 74300049 FCLM_AMD_MM (work ow for changing a signatory in multiple bank accounts), set the above two elements to # so as to include all the
company codes and account types. The work ow is for changing multiple bank accounts at the same time.

Extend Work ow Template 74300043

You can use transaction SWDD to extend this work ow template, such as by adding work ow steps or assigning responsibility rules to work ow steps.

Extend Work ow Template 78500050

You can use the Manage Work ows - For Bank Accounts app to extend this work ow template, such as by adding work ow steps, assigning responsibility rules to work ow steps, or
de ning the start action for triggering the work ow.

Related Information
Manage Work ows - For Bank Accounts

Con guration for Dual Control

To implement dual control for bank account management, make the following settings:

To enable dual control for bank account management, start the Customizing activity De ne Basic Settings and set the Activate via Dual Control indicator for Bank Account
Revision.

 Note
The dual control mode is only available to customers who have implemented the SAP Fiori app Manage Bank Accounts. If you use SAP NetWeaver Business Client (NWBC)
as the user interface and specify Activate via Dual Control as the activation mode, the setting here is ignored and your bank accounts are activated directly.

You can nd this Customizing activity in Customizing under Financial Supply Chain Management Cash and Liquidity Management General Settings De ne Basic
Settings .

When you make changes to the bank account master data, only elds that are de ned as sensitive elds can trigger the dual control process. To de ne sensitive elds, specify
the elds in the Customizing activity De ne Settings for Bank Account Master Data under Financial Supply Chain Management Cash and Liquidity Management Bank
Account Management Basic Settings . On the Sensitive Fields for Modi cation Process screen, specify the elds that trigger a work ow process when modi ed.

Extensibility Options
The following extensibility options are available for you to enhance Bank Relationship Management:

Add customer-de ned elds to the bank account master data

For customers who use SAP Fiori apps:

You can add elds to the following UI element using UI adaptations at runtime:

UI Element Business Context

The General Data section of the bank account master data Manage Bank Accounts

For more information about how to adapt an SAP Fiori UI at runtime, go to http://help.sap.com/s4hana and open the product page for the relevant version. On the
product page, enter Making UI Changes into the search bar, press Enter and open the search result with that title.

For customers who use SAP NetWeaver Business Client (NWBC) as their user interface:

You can add custom elds to the structure FCLM_BAM_AMD. After you activate the elds, you can add the elds to existing tabs of the bank account master data.

For more information, see https://help.sap.com/viewer/p/SAP_NETWEAVER_740 under Application Help UI Technologies in SAP NetWeaver Web Dynpro ABAP
and Floorplan Manager Floorplan Manager for Web Dynpro ABAP Adapting FPM Applications Customizing FPM Applications .

Business Add-Ins (BAdIs)

You can nd the BAdIs for Bank Account Management under Financial Supply Chain Management Cash and Liquidity Management Bank Account Management
Business Add-Ins (BAdIs) :

BAdI: Field Statuses and Field Checks

You can use this BAdI to de ne the following:

Field statuses for elds that are used in bank account master data, such as whether a eld is read-only, modi able, mandatory, or hidden.

To do so, you can either create your own implementation or use the default implementation FCLM_BAM_FIELDS_CTRL.

This is custom documentation. For more information, please visit the SAP Help Portal 13
2/24/2024

 Note
In addition to this Business Add-In, you can also use the Customizing activity Manage Field Status Groups to control the elds on the app screens. The
settings made for eld status groups take precedence over the default BAdI implementation FCLM_BAM_FIELDS_CTRL.

Additional checks for bank account master data.

Whether it is mandatory for users to enter a note when they approve or reject a work ow request.

BAdI: Bank Account Number Mapping Between BAM and HBA

You can use this BAdI to de ne how bank account numbers are mapped to elds in a house bank account. For example, due to the length limit of a house bank account
number, you can use this BAdI to specify another eld in which to store the bank account number, for example, Alternative Acct No..

BAdI: Events After Bank Account Activation

 Note
This BAdI is only intended for customers who use SAP NetWeaver Business Client (NWBC) as the user interface for Bank Relationship Management.

You can use this BAdI to de ne events that you want to trigger after a bank account master record is activated, such as sending a noti cation to inform aﬀected
parties.

BAdI: Bank Account Master Data Fields in Change Requests

 Note
This BAdI is only intended for customers who use SAP NetWeaver Business Client (NWBC) as the user interface for Bank Relationship Management.

You can use this BAdI to de ne which elds in bank account master data are recorded in change requests when their values are changed. Changes made to elds
included in change requests can be tracked by the change history.

BAdI: Payment Approval Pattern Determination

You can use this BAdI to override the payment approval patterns de ned in the Customizing activity De ne Settings for Bank Account Master Data with your own logic
and de nition.

BAdI: Processing Logic for IDoc Message Type HBABAMAST and BAdI: Processing Logic for IDoc Message Type BAMMAST

You can use these BAdIs to enhance the processing logic of the tool for replicating house banks, house bank accounts, and bank accounts.

ICF Services
Before you use the Web Dynpro application for Bank Account Management, you need to activate the following services.

To do so, in Maintain Services (transaction code SICF), search for a service by entering the service name, and then activate it.

To activate a service, right click on the service and then choose Activate Service.

The following services must be activated:

Web Dynpro services

WDA_FCLM_BAM_ACC_MASTER

WDA_FCLM_BAM_ACC_REVIEW

WDA_FCLM_BAM_ADAPT_SIGN

WDA_FCLM_BAM_BANK_DATA

WDA_FCLM_BAM_CHGREQ

WDA_FCLM_BAM_HIERARCHY

WDA_FCLM_BAM_HIER_BP

WDA_FCLM_BAM_HIER_MAINTAIN

WDA_FCLM_BAM_MASS_CHANGE

WDA_FCLM_BAM_REVIEW_REPORT

WDA_FCLM_BAM_REQOVERVIEW

WDA_FCLM_REPORT

WDA_FCLM_UPLOAD_DOWNLOAD

Work ow services

ibo_wda_inbox

swf_formabsenc

swf_workplace

UCT_DISPLAY_DOCUMENT

UCT_DISPLAY_INBOX

This is custom documentation. For more information, please visit the SAP Help Portal 14
2/24/2024
UCT_DISPLAY_SIGNOFF

UCT_DISPLAY_CHANGE

USMD_CREQUEST_PROTOCOL2

USMD_SSW_RULE

USMD_WF_NAVIGATION

POWL services

POWL

POWL_COLLECTOR

powl_composite

POWL_EASY

POWL_ERRORPAGE

POWL_MASTER_QUERY

POWL_PERS_COMP

Data Replication
To replicate house banks, house bank accounts, and bank accounts from a sender system to one or more receiver systems, you can use the Execute Data Replication program
(transaction DRFOUT). With this program, you can carry out the following tasks:

Replicate existing house banks, house bank accounts, and bank accounts to receiver systems en masse

Replicate changes that occurred in the sender system during a speci ed time interval to receiver systems

Manually select and transfer data to receiver systems

SAP has provided the following message types for using the replication program to replicate house banks, house bank accounts, and bank accounts. The table below lists the
supported software component versions for this tool.

System Usage Product Software Component Versions

Sender System SAP S/4HANA

S4CORE 102 SP00 and higher verisons

S4CORE 101 SP00 and higher versions

S4CORE 100 SP03 and higher versions

SAP S/4HANA Finance

SAP_FIN 720 SP05 and higher versions

SAP_FIN 730 SP04 and higher versions

Receiver System SAP ERP

SAP_APPL 618 SP03 and higher versions

SAP_APPL 617 SP12 and higher versions

SAP_APPL 616 SP11 and higher versions

SAP S/4HANA
S4CORE 102 SP00 and higher verisons

S4CORE 101 SP00 and higher versions

S4CORE 100 SP03 and higher versions

SAP S/4HANA Finance

SAP_FIN 720 SP05 and higher versions

SAP_FIN 730 SP04 and higher versions

The use of the message types depends on whether the receiver system is an SAP S/4HANA system. The table below explains the use of the message types in diﬀerent scenarios.

Message Type SAP S/4HANA system Not an SAP S/4HANA system

BAMMAST Replicate bank account master data including bank accounts and house bank accounts Not applicable

HBHBAMAST Replicate house banks Replicate house banks and house bank accounts

For more information about this program, choose the Information button.

Schedule a Job for Automatic Replication

This is custom documentation. For more information, please visit the SAP Help Portal 15
2/24/2024
In additon to the above replication modes, you can schedule a job to automatically replicate house banks, house bank accounts, and bank accounts to receiver systems. To do so, you
can use transaction SM36 to schedule a job for program RBDMIDOC.

Prerequisites
Before con guring the settings for using this program to replicate house banks, house bank accounts, and bank accounts, make sure that you have performed the following steps for
IDoc and Application Link Enabling (ALE) in the sender system and the receiver systems.

1. Create users for ALE transfer.

2. Create logical systems and assign clients to logical systems.

3. Create RFC connections.

For more information, search for the topic IDoc Interface/ALE at https://help.sap.com/.

Con guration in the Sender System

Con guration for the Customizing Activity Distribute ALE Master Data
In the sender system, con gure the following in the Customizing activity Distribute ALE Master Data. You can nd this Customizing activity under Quality Management
Environment Tools .

1. Set Up Model View in Distribution Model (transaction BD64)

a. Choose Edit and then choose Create Model View.

b. Specify BAM_HBANK as the technical name.

c. To add BAPIs to the new model, select the created model view, and then, from the menu bar, choose Edit Add BAPI .

d. Add BAPIs as shown in the table below for each receiver system:

Sender/client Receiver/client Obj. name/interface Method

Sender system Receiver system BUSHBANK BankReplicate

Sender system Receiver system BankAcctReplication BamAmdBnkant

2. Generate Partner Pro les

In the Model View eld, enter BAM_HBANK and then choose Execute.

3. Maintain Partner Pro le

Maintain the partner pro le for each receiver system as follows:

a. In the structure, select Partner Type LS and then select a receiver system.

b. In the Outbound Parameters section, choose Create Outbound Parameter to create two parameters as follows:

Receiver Port Message Basic Type Output Mode IDoc Type

Type

Parameter The port ID of HBHBAMAST HBHBAMAST02 Select the Pass IDoc Select the Cancel
1 the receiver Immediately Processing After Syntax
system  Note checkbox Error checkbox
This type only applies when both the sender and receiver systems are
SAP S/4HANA 1709 or higher versions. Otherwise, please use
HBHBAMAST01.

Parameter The port ID of BAMMAST BAMMAST02 Select the Pass IDoc Select the Cancel
2 the receiver Immediately Processing After Syntax
Note:
system checkbox Error checkbox

 Note
This type only applies when both the sender and receiver systems are
SAP S/4HANA 1709 or higher versions. Otherwise, please use
BAMMAST01.

4. Object with Change Document: Activate Change Indicators (Generally)

Make sure this checkbox is selected.

5. Object with Change Document: Set Up Change Indicators for Table Fields

With this setting, you con gure elds in bank account master data that can trigger synchronization from the sender system to the receiver systems.

To register a eld, enter the message type BAMMAST or HBHBAMAST, and then specify the corresponding object name as shown in the table below and the eld technical name.

You can obtain the technical information about the bank account master data elds from the following table:

This is custom documentation. For more information, please visit the SAP Help Portal 16
2/24/2024

Message Type Object Tables

HBHBAMAST FCLM_HOUSEBANK FCLM_BAM_ACLINK2

FCLM_BAM_AMD_T

T012

T012D

BAMMAST FCLM_BAM3 FCLM_BAM_ACLINK2

FCLM_BAM_AMD

FCLM_BAM_SIG

FCLM_BAM_AMD_CUR

FCLM_BAM_AMD_LIM

FCLM_BAM_AMD_T

6. Object with Change Document: Activate Change Indicators for Message Type

Add message types BAMMAST and HBHBAMAST.

Select the active checkbox for both entries.

7. Object with Change Document: Maintain Additional Data for Message Type

Create two new entries as follows:

Message Type Reference Message Type Format Function Module Reducable Message Type

BAMMAST Leave blank MASTERIDOC_CREATE_SMD_BAMMAST Deselect the checkbox

HBHBAMAST HBHBAMAST MASTERIDOC_CREATE_SMD_HBANK Select the checkbox

Con guration for Transaction DRFIMG

In the sender system, make the following settings using transaction DRFIMG.

1. De ne business systems for receiver systems.

a. Go to De ne Custom Settings for Data Replication De ne Technical Settings De ne Technical Settings for Business Systems .

b. De ne a business system for each receiver system.

To do so, create a new entry and specify the logical system information of the receiver system.

2. De ne replication models.

a. Go to De ne Custom Settings for Data Replication De ne Replication Models .

b. Create a new replication model for message type HBHBAMAST and then do the following:

i. Select the entry created and then double-click Assign Outbound Implementation.

ii. Enter the outbound implementation HBANK_IMP and select Replication via IDoc for the Communication Channel eld.

1. Select the implementation created and double-click Assign Target Systems for Repl. Model/Outb.Impl.

2. Choose New Entries. Enter the business systems and save.

3. Go back to the De ne Replication Model view and choose Activate to activate your settings.

c. Create another replication model for message type BAMMAST.

i. Select the entry created and then double-click Assign Outbound Implementation.

ii. Enter the outbound implementation BAMMAST and select Replication via IDoc for the Communication Channel eld.

1. Select the implementation created and double-click Assign Target Systems for Repl. Model/Outb.Impl.

2. Choose New Entries. Enter the business systems and save.

3. Go back to the De ne Replication Model view and choose Activate to activate your settings.

3. Enable the replication mode in transaction DRFOUT.

1. Go to De ne Custom Settings for Data Replication De ne Business Object Settings .

2. Create the following entries:

Business Object Type Message Type Retention Period

BAMMAST BAMMAST 100

HBHBA_OBJ HBHBAMAST 100

This is custom documentation. For more information, please visit the SAP Help Portal 17
2/24/2024
3. Check settings for the replication mode

a. Go to Business Add-Ins (BAdIs) BAdI: Creation of MDG Change Pointers from ALE Change Pointer .

b. Make sure that the implementation DRF_CP_PROCESSING is active.

Con guration in Receiver Systems

1. Run transaction WE20.

2. Select Partner Type LS and then create a new partner.

3. In the Inbound Parameters section, create two new entries respectively for the two messages types with the following information:

Message Type: HBHBAMAST, BAMMAST

Process Code: BAPI

Select the Cancel Processing After Syntax Error checkbox.

Select the Trigger Immediately option.

Additionally, you can monitor the processing status of dispatched IDocs in the receiving system using ALE Audit. With this feature, you can receive con rmation messages and check
the con rmation log in the source system. For more information about the use and con guration of ALE Audit, search for the topic Monitoring the Status of Inbound IDocs Using ALE
Audit at https://help.sap.com/.

Con guration for One Exposure from Operations

Use
The One Exposure from Operations hub is a central storage location for operational data that is relevant for managing cash and liquidity. The provision of the data in the One
Exposure from Operations hub facilitates funds planning and risk management across multiple companies. Currently, SAP S/4HANA Finance for cash management uses One
Exposure from Operations to acquire both data from the central system and remote systems that serve as subsystems of the central system. The integration is either real-time (one-
system scenario) or periodic (side-by-side scenario with remote systems).

More Information
Integration with Source Applications in the Central System

Integration with Remote Systems

Integration with Source Applications in the Central System

The following source applications can be integrated for real-time update into One Exposure from Operations and the transaction data can be consumed by SAP S/4HANA Finance for
cash management and relevant cash management apps :

Financial Operations

Accounting Documents (FI)

Bank Statements

Promise to Payment (P2P)

Treasury and Risk Management (TRM)

Consumer and Mortgage Loans (FS-CML)

Contract Accounts Receivable and Payable (FI-CA)

Materials Management (MM)

Sales and Distribution (SD)

To set up the real-time integration of source applications, con gure the following Customizing activities under Financial Supply Chain Management Cash and Liquidity
Management Cash Management Data Setup :

1. To activate source applications for company codes, con gure either of the following two Customizing activities:

Activate Individual Source Applications: Activate a single source application for a company code

Activate Multiple Source Applications: Activate several source applications for one or more company codes

2. The upload of existing transaction data from the source applications is optional and can be performed as a mass upload using the Customizing activity Load Trans. Data from
Source Appl. into One Exposure from Operations Hub.

 Note
Note: This step should be executed after you nished the steps in the Con guration for Cash Operations.

This is custom documentation. For more information, please visit the SAP Help Portal 18
2/24/2024
More Information
Alternatively, for sources aplications of FI and MM, you can run the ow builder program to set up the data.

For more information, see Customize the Flow Builder.

Customize the Flow Builder

Customize the settings and tools for Flow Builder.

For sources applications of FI and MM, you can run the Flow Builder program to generate cash-relevant ows, which are then imported to One Exposure from Operations.

To enable the Flow Builder to run automatically, add the job FCLM_FLOWBUILDER_JOB to the Customizing activity Activation of Scope-Dependent Background Job De nitions
(S/4HANA) . You can nd this activity under SAP NetWeaver Application Server System Administration .

To customize the settings and tools for the Flow Builder Program, perform the Customizing activity Customize the Flow Builder under Financial Supply Chain Management Cash
and Liquidity Management Cash Management Data Setup .

For more information, see Build Cash Flows from Operations.

Integration with Remote Systems

Periodic integration of data into the One Exposure from Operations hub can be set up for:

Manual Entry of Bank Cash Balances

Classic Cash Management

SAP Liquidity Planner

Manual Entry of Bank Cash Balances

In the central system, con gure the following:

In the Manage Bank Accounts app, maintain the connectivity path for bank accounts that exist in a remote system by de ning a connectivity path with the ID category of Remote
System: G/L Account.

Classic Cash Management

In both the central system and the remote systems, con gure the following:

Con gure the following Customizing activities for using IDoc under IDoc Interface / Application Link Enabling (ALE) using transaction SALE:

De ne Logical System, under Basic Settings Logical Systems

Create RFC Connections, under Basic Settings Communication

Generate Partner Pro les, under Modelling and Implementing Business Processes Partner Pro le

In the central system, con gure the following:

De ne the distribution model using message types CMSEND and CMREQU and distribute it to all the remote systems in Customizing activity Maintain Distribution Model and
Distribute Views, under IDoc Interface / Application Link Enabling (ALE) Modelling and Implementing Business Partners .

In the Manage Bank Accounts app, maintain the connectivity path for bank accounts that exist in a remote system by de ning a connectivity path with the ID category of
Remote System: G/L Account.

In the SAP GUI application, con gure the following Customizing activities to de ne how to convert company codes, planning groups, planning levels, and business areas from
remote systems for use in the central system, under Financial Supply Chain Management Cash and Liquidity Management Cash Management Data Setup Inbound
Mapping for Integration of Remote Data into One Exposure :

Assign Company Codes

Convert Sender Planning Groups

Convert Sender Planning Levels

Convert Sender Business Areas

Flow types are derived by a default logic, but an additional diﬀerentiation for con rmed cash can be con gured with Customizing activity Assign Flow Types to Planning Levels
under Financial Supply Chain Management Cash and Liquidity Management Cash Management Flow Types .

To de ne the liquidity item derivation rules, con gure queries and query services as described in Liquidity Items and Liquidity Item Hierarchies.

SAP Liquidity Planner

To enable the Web service, the system administrator con gures the following in SOA Management (transaction SOAMANAGER):

In the central system, con gure a Web service based on the service de nition FQM_WS_DISTRIBUTE.

This is custom documentation. For more information, please visit the SAP Help Portal 19
2/24/2024
In the remote systems, de ne a logical port for each remote system based on the consumer proxy CO_FQM_WS_DISTRIBUTE.

To enable the data transfer and conversion, the application consultant con gures the following:

In the central system, con gure the following activities to de ne how to convert company codes and business areas from remote systems for the use in the central system,
under Financial Supply Chain Management Cash and Liquidity Management Cash Management Data Setup Inbound Mapping for Integration of Remote Data into
One Exposure :

Assign Company Codes

Convert Sender Business Areas

In the remote systems, con gure the following:

De ne source applications, company codes, and payment dates (optional) to control data transfers into the One Exposure from Operations hub in Customizing activity
Activate Source Application Liquidity Planner for One Exposure Transfer under Financial Supply Chain Management Cash and Liquidity Management Liquidity
Planner Tools .

If you have additional mapping requirements, you also have the option of using the BAdI BADI_FQM_FLOW_ADJUST_CORE. The BAdI includes a sample implementation.

Make sure you have liquidity items de ned in both the central system and the remote systems. For more information, see Liquidity Items and Liquidity Item Hierarchies.

Con guration for Cash Operations

Use
This activity is to set up transactional data that will be consumed by Cash Management applications. Applications in SAP S/4HANA Finance for cash management consume data from
the following sources:

Memo records (database table FDES)

One Exposure from Operations (database table FQM_FLOW) for data from other components such as Financial Operations, TRM, CML, FI-CA, MM, SD, and integrated data
from remote systems.

To use Cash Operations, make the following con guration settings:

Flow types

With built-in semantics, ow types classify information from diﬀerent source components or diﬀerent steps in the cash ow lifecycle from forecast to actual.

Liquidity items

Liquidity items represent the use and purpose of the cash ow. Typically with liquidity items and the de ned hierarchical structures, cash ows can be classi ed into diﬀerent
categories and sub-categories in a hierarchical view, for example, cash ows for operations, cash ows for nancing, and cash ows for investment.

Planning levels and planning groups

Planning levels and planning groups help customers to lter and categorize cash data for diﬀerent reporting and analytical purposes. The two attributes enable the integration
between Cash Management and other components.

House banks and house bank accounts

House bank accounts specify the bank accounts used or to be used for payments.

Source Applications

Source applications represent the information sources relevant for Cash Management. Only activated source applications will be taken into account. For more information, see
Con guration for One Exposure from Operations.

More Information
Memo Records

Source Applications

Flow Types

Liquidity Items and Liquidity Item Hierarchies

Planning Levels and Planning Groups

Field Status

Memo Records

Use
Incoming and outgoing payments that are not transferred to the sytem of SAP S/4HANA Finance for cash management via actual postings, can be entered manually in the planning.

This is custom documentation. For more information, please visit the SAP Help Portal 20
2/24/2024
Make sure you have properly con gured the following Customizing activities under Financial Supply Chain Management Cash and Liquidity Management Cash Management
Memo Records :

De ne Cash Management Account Name

De ne Planning Types

De ne Number Ranges

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 Cash Management Data Setup :

Activate Individual Source Applications: Activate a single source application for a company code

Activate Multiple Source Applications: Activate several source applications for one or more company codes

Build Cash Flows from Operations: Build ows for source application of FI and MM

You may need to activate the following source applications:

To build key information in accounting documents, activate source application One Exposure.

To use data of a particular category stored in the One Exposure from Operations hub, activate the corresponding source application according to your business needs.

For more information, see Con guration for One Exposure from Operations.

Flow Types

De nition
Flow types classify the lifecycle of cash ows, for example, they distinguish forecasted cash ows from con rmed cash ows. Only transaction data that is assigned with ow type
information can be consumed and used in Cash Management applications.

SAP prede nes a set of ow types. If you do not have special requirements, you can rely on the standard ow types delivered by SAP.

Flow Type Assignment for Accounting Documents

The ow types listed here are uploaded to the Accounting Document Segment (table BSEG) and serve as a trigger for the ow builder. The ow builder then derives cash ows and
stores the ow types to the One Exposure from Operations hub for analytical purposes.

In general, the integration of Financial Operations into One Exposure from Operations covers information on invoices, payments, and bank statements. Within this integration, the
system classi es accounting document line items into the following categories:

Line item posting on a customer or vendor account (Receivables or Payables)

Line item posting on a bank clearing account (Cash in Transit)

Line item posting on a bank account (Cash)

The determination of the category is done by the system in the following way:

Receivable or Payable

Items from invoices having account type K (Vendor) or D (Customer)

Cash in Transit

Items having a G/L account that has one of the following characteristics:

Maintained in account determination of payment program ( T042I ), is a balance sheet account ( SKA1-XBILK ), and is not a reconciliation account ( SKB1-MITKZ )

Maintained in account determination of bank-to-bank transfer ( T042Y ), is a balance sheet account ( SKA1-XBILK ), and is not a reconciliation account ( SKB1-
MITKZ)

Marked as cash relevant ( SKB1-XGKON ) and with open item management (SKB1-XOPVW )

Cash

Items having a G/L account that has one of the following characteristics:

Maintained in house bank accounts ( T012K )

Marked as cash relevant ( SKB1-XGKON ) without open item management ( SKB1-XOPVW )

For these accounting document items, the system derives the following ow types:

Receivable or Payable

600000 - Regular Receivables Increase

This is custom documentation. For more information, please visit the SAP Help Portal 21
2/24/2024
600001 - Regular Payables Increase

600200 - Unallocated Receivables Increase

600201 - Unallocated Payables Increase

Revenue and Expenses

600500 - Delivered Goods/Services Increase

600501 - Received Goods/Services Increase

600510 - Received Goods/Services Decrease

600511 - Delivered Goods/Services Decrease

Tax

300000 - Input Tax Increase

300001 - Output Tax Increase

300010 - Output Tax Decrease

300011 - Input Tax Decrease

Cash in Transit

800006 - Incoming Cash in Transit Increase

800008 - Outgoing Cash in Transit Increase

Cash

900006 - Incoming Bank Con rmed Cash Increase

900008 - Outgoing Bank Con rmed Cash Increase

For items representing payables, receivables, revenues, invoices, tax, or cash in transit, One Exposure from Operations derives cash forecasts. Accounting documents containing
other items than the ones described above are not handled by the integration of Financial Operations into One Exposure from Operations.

Assign Flow Types to G/L Accounts

If you want (as an exception) additional accounting document items to be processed by the integration of Financial Operations into One Exposure from Operations, you have to de ne
them using the Customizing activity Assign Flow Types to G/L Accounts under Financial Supply Chain Management Cash and Liquidity Management Cash Management
Flow Types .

You do this by assigning the corresponding G/L accounts to the following ow types, which are currently available to you. For example:

Cash in Transit

800006 - Incoming Cash in Transit Increase

800008 - Outgoing Cash in Transit Increase

Cash

900006 - Incoming Bank Con rmed Cash Increase

900008 - Outgoing Bank Con rmed Cash Increase

Payment Request Clearing

700000 - Incoming Payment Request

700001 - Outgoing Payment Request

If an item posts to such an account in debit, the system uses the rst ow type; in credit the system uses the second ow type. These ow types are delivered. There is no need to
create additional customer-speci c ow types for this.

 Caution
Do not assign ow types to a G/L account that is characterized as a reconciliation account.

Liquidity Items and Liquidity Item Hierarchies

Liquidity items represent the source and use of cash ows in your company. They serve as an import dimension for nancial planning and reporting in SAP S/4HANA Finance for cash
management. Con gure the following under Financial Supply Chain Management Cash and Liquidity Management Cash Management Liquidity Items .

De ne Liquidity Items and Liquidity Item Hierarchies

To de ne liquidity items, use the Edit Liquidity Items activity.

To group liquidity items into hierarchical structures, de ne hierarchies using the De ne Liquidity Item Hierarchies activity.

The hierarchies de ned here can be used by Cash Management applications to display cash ows in categories and sub-categories in a hierarchical view.

This is custom documentation. For more information, please visit the SAP Help Portal 22
2/24/2024
Derive Liquidity Items for Accounting Documents
For accounting documents (in database table BSEG), if liquidity items can be determined by G/L accounts, you may use the De ne Default Liquidity Items for G/L Accounts
activity to de ne the derivation rules.

If you need more complex logic to derive liquidity items from various elds of the accounting document, then you need to de ne queries and query sequences using the
following activities:

De ne Queries for Liquidity Item Derivation

De ne Query Sequences

Assign Queries to Query Sequences

You should always specify the Origin as D or C when de ning queries and query sequences for accounting documents.

Origin C applies to line items with account type D (customer) or K (supplier).

Origin D applies to line items with account types other than D (customer) or K (supplier).

When deriving liquidity items, the system rst tries to apply the assigned query sequences; if not successful, then it turns to the default liquidity items de ned for G/L
accounts.

Derive Liquidity Items for Source Application Data in One Exposure from Operations
For data integrated into the One Exposure from Operations hub from source applications in the central system, such as TRM, CML, or FI-CA data, there is no default derivation rules
for liquidity items. You need to de ne 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 One Exposure from Operations hub.

For more information on how to con gure the One Exposure from Operations hub to extract data from source applications in the central system, see Integration with Source
Applications in the Central System.

Derive Liquidity Items for Remotely Integrated Data in One Exposure from Operations
Data integrated from remote systems falls into the following types:

Classic Cash Management data from remote systems: De ne queries and query sequences with the Origin as X.

Liquidity Planner actuals: The original liquidity item values in the source data are transferred into the One Exposure from Operations hub. Therefore it has to be assured that
the liquidity items exist in both systems (remote and central). For this purpose you can use the Customizing activity Import and Export Liquidity Items to create liquidity items
massively in diﬀerent systems, under Financial Supply Chain Management Cash and Liquidity Management Cash Management Tools .

For more information on how to con gure the One Exposure from Operations hub to integrate with data from remote systems, see Integration with Remote Systems.

Planning Levels and Planning Groups

The planning level re ects typical nancial transactions, for example, posting to a bank account, posting to a clearing account, con rmed or uncon rmed 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 in ow or out ow, and the type of
business relationship.

Before you use SAP S/4HANA Finance for cash management, con gure planning levels and planning groups under Financial Supply Chain Management Cash and Liquidity
Management 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 accounts, for example bank accounts, bank
clearing accounts, payment request 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.

Field Status
By default, house bank and house bank account are optional elds in payments and bank statements. To ensure the information is recorded for relevant transactions, you may
consider to set the two elds as mandatory for G/L accounts that work as bank clearing accounts and bank accounts by using the Customizing activity De ne Field Status Variants,
under Financial Accounting Accounts Receivable and Accounts Payable Business Transactions Incoming Payments Incoming Payments Global Settings Make and Check
Document Settings .

Con guration for Liquidity Management

Use
This activity is to set up data that will be consumed by Liquidity Management applications.

Prerequisites

This is custom documentation. For more information, please visit the SAP Help Portal 23
2/24/2024
Make sure you have properly con gured the settings mentioned in the Con guration for Cash Operations, for example, One Exposure from Operations, Memo Records and so
on.

Make sure you have properly con gured the settings under Financial Supply Chain Management Cash and Liquidity Management Cash Management

Activities
To use Liquidity Management applications, you need to make the following con guration settings:

BI Content

You activate BI Content Bundle and additional BI content objects. This step is only relevant for the liquidity planning function.

Planning Units and Planning Unit Hierarchy

Planning units are organizational units that need to enter liquidity plan data. Each planning unit corresponds to one company code. You de ne Planning Units and Planning Unit
Hierarchy in the Customizing activity Maintain Planning Unit Settings and Activate Planning Unit Hierarchyunder Financial Supply Chain Management Cash and Liquidity
Management Liquidity Planning . This step is only relevant for the liquidity planning function.

Reference Data Sources

SAP prede nes standard BW modeling. You can also de ne your own reference data sources if extension is needed. You de ne this in the Customizing activity De ne
Reference Data Sources under Financial Supply Chain Management Cash and Liquidity Management Liquidity Planning . This step is only relevant for the liquidity
planning function.

Liquidity Planning Types

SAP prede nes standard BW modeling. You can also de ne your own planning types. You de ne this in the Customizing activity De ne Liquidity Planning Types under
Financial Supply Chain Management Cash and Liquidity Management Liquidity Planning . This step is only relevant for the liquidity planning function.

Liquidity Items and Liquidity Item Hierarchies

Liquidity items represent the source and use of cash ows in your company. It serves as an import dimension for nancial planning and reporting in Cash and Liquidity
Management. Con gure the following under Financial Supply Chain Management Cash and Liquidity Management Cash Management Liquidity Items . This step is
only relevant for the liquidity planning function.

ICF Services

Business Planning and Consolidation (BPC)

The following con guration settings in BPC need to be made :

Enable BPC Embedded Model and Deep HANA Integration

Customize BPC Templates

Con gure the Default Liquidity Item Hierarchy in Template

Customize the BPC Work Status

Specify the BPC Con guration Set

This step is only relevant for the liquidity planning function.

Launchpad Access Con guration

The following front-end con guration settings need to be made in order to enable the navigation from the ori launchpad to BPC:

Create Launchpad

Create Catalog

Create Tile

Create Target Mapping

Assign Role to Catalog

This step is only relevant for the liquidity planning function.

More Information
For more information about app-speci c implementation information, see Apps for Cash Management and the details in the SAP Fiori apps reference library.

Settings in the Back-End Server

BI Content

Activation of BI Content Bundle

BI Content bundles contain BW Queries, Operational Data Providers (ODPs), and other BI Content objects. The concept of BI Content bundles simpli es the activation of all required
objects so there is no need to perform the more cumbersome procedure of collecting and activating objects individually.

Activate the BI Content bundle FIN_CLM_PLANNING (Liquidity Planning) using the BI Content Activation Workbench (transaction BSANLY_BI_ACTIVATION).

This is custom documentation. For more information, please visit the SAP Help Portal 24
2/24/2024
On the activation screen, specify the RFC connection for your BI client (if the BI client is the current client, you can specify RFC destination NONE), set Treatment of Already Active
Content Objects ag to Copy, and activate the ag Install all Collected Objects. Check the activation log to verify there are no errors.

 Note
If the BI bundle cannot be activated successfully, you need to activate all the BI contents collected in the bundle manually using transaction RSOR. To display the BI contents
contained in the bundle, choose the Show Detail button.

 Note
You can activate other options later on even if you have changed the content delivered by SAP by selecting the checkbox. For content objects delivered by SAP, you are asked if you
want to merge the new content version with the active object. Deselect Install all Collected Objects if you only want to activate the new SAP-delivered objects. Automatic choices
between Match and Copy depend on the object type (for more information, see ag MERGEFL in table RSTLOGOPROP). You must activate the BI Content in each system
(development, test, and production) separately. It is part of the system setup, not part of application customizing.

Activation of Additional BI Content Objects

Proceed as follows:

1. In transaction RSOR, choose Object Types on the left panel.

2. On the middle panel, nd an object type of the BI Content objects listed in the table below.

3. Choose Select Objects.

4. In the dialog box, select the objects to be activated.

5. Choose Transfer Selections.

6. On the right panel, select Data ow Before and Afterwards in the Grouping menu.

7. Select all the objects.

8. Choose Install to start the content installation.

Object Type Object Type Technical Name Object Description Object Technical Name

BPC Uni ed Environment ENVM Liquidity Plans Environment 0FCLM_LP_ENV

BPC Model MODL Liquidity Plans Model 0FCLM_LP_ENV

FCLM_LP_MODEL

BPC BPF BBPF Develop Liquidity Plans (Design Studio) 0FCLM_LP_ENVFCLM_LP_PROCESS_AO

BPC Workspace WKSP 0FCLM_LP_ENV/Root

0FCLM_LP_ENV/Public

0FCLM_LP_ENV/Teams

Analysis Oﬃce AAOE Analysis Oﬃce Excel Workbook /ERP/FCLM_LP_AL01_T0001

Analysis Oﬃce AAOE Analysis Oﬃce Excel Workbook /ERP/FCLM_LP_AL01_T0002

Analysis Oﬃce AAOE Analysis Oﬃce Excel Workbook /ERP/FCLM_LP_AL01_T0003

Analysis Oﬃce AAOE Analysis Oﬃce Excel Workbook /ERP/FCLM_LP_MP01_T0001

Analysis Oﬃce AAOE Analysis Oﬃce Excel Workbook /ERP/FCLM_LP_MP01_T0002

Analysis Oﬃce AAOE Analysis Oﬃce Excel Workbook /ERP/FCLM_LP_MP01_T0013

Analysis Oﬃce AAOE Analysis Oﬃce Excel Workbook /ERP/FCLM_LP_MP01_T0004

Analysis Oﬃce AAOE Analysis Oﬃce Excel Workbook /ERP/FCLM_LP_MP01_T0005

BI Content for Liquidity Planning

SAP provides the following local BI Content for liquidity planning:

Queries

Variables

MultiProviders

Key Figures

InfoCubes

Characteristics

Planning Functions

This is custom documentation. For more information, please visit the SAP Help Portal 25
2/24/2024

Liquidity Management

Queries

Monthly Rolling Liquidity Plans

/ERP/FCLM_LP_AL01_Q0001

Use
This is an input query for monthly liquidity plans. The query shows the planning layout for twelve consecutive calendar months, starting with the rst month of the selected planning
cycle, in the planning currency view.

This query is based on the aggregation level Monthly Liquidity Plans (/ERP/LP_AL01).

No navigation option exists for this query.

Switches are not assigned to this query.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Calendar Year/Month 0CALMONTH 0P_FCLM_LP_PLAN_MONTH

0P_FCLM_LP_PLAN_MONTH+1

0P_FCLM_LP_PLAN_MONTH+2

0P_FCLM_LP_PLAN_MONTH+3

0P_FCLM_LP_PLAN_MONTH+4

0P_FCLM_LP_PLAN_MONTH+5

0P_FCLM_LP_PLAN_MONTH+6

0P_FCLM_LP_PLAN_MONTH+7

0P_FCLM_LP_PLAN_MONTH+8

0P_FCLM_LP_PLAN_MONTH+9

0P_FCLM_LP_PLAN_MONTH+10

0P_FCLM_LP_PLAN_MONTH+11

Characteristic Planning Unit /ERP/ORG_UNIT 0P_FCLM_ORG_UNIT

Characteristic Client 0MANDT 0SYMANDT

Characteristic Planning Cycle /ERP/VMONTH 0P_FCLM_LP_PLAN_VERSION

Characteristic Planning Type /ERP/PLANTYPE 0P_FCLM_PLANNING_TYPE

Free Characteristics

Object Type Name Technical Name

Characteristic Calendar Year/Month 0CALMONTH

Characteristic Planning Unit /ERP/ORG_UNIT

Characteristic Client 0MANDT

Characteristic Planning Cycle /ERP/VMONTH

Characteristic Planning Type /ERP/PLANTYPE

Characteristic Planning Currency 0CURRENCY

Characteristic Liquidity Item /ERP/LQITEM

Characteristic Conversion Currency /ERP/TCUR

Characteristic Conversion Partner /ERP/TDP_CC

Characteristic Calendar Year/Month 0CALMONTH

Variables

Object Type Name Technical Name

This is custom documentation. For more information, please visit the SAP Help Portal 26
2/24/2024

Object Type Name Technical Name

Variable Planning Month 0P_FCLM_LP_PLAN_MONTH

Variable Planning Unit 0P_FCLM_ORG_UNIT

Variable System Client 0SYMANDT

Variable Planning Cycle 0P_FCLM_LP_PLAN_VERSION

Variable Planning Type 0P_FCLM_PLANNING_TYPE

Rows

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Planning Currency 0CURRENCY

Characteristic Liquidity Item /ERP/LQITEM

Characteristic Conversion Currency /ERP/TCUR

Characteristic Conversion Partner /ERP/TDP_CC

Columns

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Calendar Year/Month 0CALMONTH Not applicable

Key Figure Liquidity Forecast Key Figure=Suggest

InfoProvider=/ERP/LP_IC01

Suggest Value Source = 002

Key Figure Last Cycle Plan Key Figure=Suggest

InfoProvider=/ERP/LP_IC01

Suggest Value Source = 003

Key Figure Last Year Actual Key Figure=Suggest

InfoProvider=/ERP/LP_IC01

Suggest Value Source = 001

Key Figure Plan Amount Key Figure=Suggest

InfoProvider=/ERP/LP_IC01

Suggest Value Source = #

Report/Report Interfaces

Object Type Name Technical Name

Develop Liquidity Plans-Data Entry 0FCLM_MLP_INPUT

Develop Liquidity Plans-Review 0FCLM_MLP_REVIEW

Develop Liquidity Plans-Display 0FCLM_MLP_DISPLAY

Aggregation Currency View

/ERP/FCLM_LP_AL01_Q0005

Use
This query is used for analyzing liquidity plans by aggregation currency. The query shows the following in aggregation currency:

Planned values for the 12 calendar months of the selected planning cycle

Reference data, such as forecast values (for the 12 calendar months) or plan values for the previous cycle

This query is based on the aggregation level Monthly Liquidity Plans (/ERP/LP_AL01).

No navigation option exists for this query.

Switches are not assigned to this query.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

This is custom documentation. For more information, please visit the SAP Help Portal 27
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Calendar Year/Month 0CALMONTH 0P_FCLM_LP_PLAN_MONTH

0P_FCLM_LP_PLAN_MONTH+1

0P_FCLM_LP_PLAN_MONTH+2

0P_FCLM_LP_PLAN_MONTH+3

0P_FCLM_LP_PLAN_MONTH+4

0P_FCLM_LP_PLAN_MONTH+5

0P_FCLM_LP_PLAN_MONTH+6

0P_FCLM_LP_PLAN_MONTH+7

0P_FCLM_LP_PLAN_MONTH+8

0P_FCLM_LP_PLAN_MONTH+9

0P_FCLM_LP_PLAN_MONTH+10

0P_FCLM_LP_PLAN_MONTH+11

Characteristic Planning Unit /ERP/ORG_UNIT 0P_FCLM_ORG_UNIT

Characteristic Client 0MANDT 0SYMANDT

Characteristic Planning Cycle /ERP/VMONTH 0P_FCLM_LP_PLAN_VERSION

Characteristic Planning type /ERP/PLANTYPE 0P_FCLM_PLANNING_TYPE

Free Characteristics

Object Type Name Technical Name

Characteristic Calendar Year/Month 0CALMONTH

Characteristic Planning Unit /ERP/ORG_UNIT

Characteristic Client 0MANDT

Characteristic Planning Cycle /ERP/VMONTH

Characteristic Planning type /ERP/PLANTYPE

Characteristic Planning Currency 0CURRENCY

Characteristic Liquidity Item /ERP/LQITEM

Characteristic Calendar Year/Month 0CALMONTH

Variables

Object Type Name Technical Name

Variable Planning Month 0P_FCLM_LP_PLAN_MONTH

Variable Planning Unit 0P_FCLM_ORG_UNIT

Variable System Client 0SYMANDT

Variable Planning Cycle 0P_FCLM_LP_PLAN_VERSION

Variable Planning Type 0P_FCLM_PLANNING_TYPE

Variable Key Date 0P_FCLM_KEY_DATE

Variable Exchange Rate Type 0P_FCLM_RTYPE

Variable Target Currency 0P_FCLM_AG_CURRENCY

Rows

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Liquidity Item /ERP/LQITEM Not applicable

Columns

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Calendar Year/Month 0CALMONTH Not applicable

Key Figure Liquidity Forecast Key Figure=Suggest

InfoProvider=/ERP/LP_IC01

Suggest Value Source = 002

Key Figure Last Cycle Plan Key Figure=Suggest

InfoProvider=/ERP/LP_IC01

Suggest Value Source = 003

This is custom documentation. For more information, please visit the SAP Help Portal 28
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Key Figure Last Year Actual Key Figure=Suggest

InfoProvider=/ERP/LP_IC01

Suggest Value Source = 001

Key Figure Plan Amount Key Figure=Suggest

InfoProvider=/ERP/LP_IC01

Suggest Value Source = #

Report/Report Interfaces

Object Type Name Technical Name

Develop Liquidity Plans-Aggregation View 0FCLM_MLP_AGGVIEW

Multiple Rating
/ERP/FCLM_LP_AL01_Q0002

Use
This input query is used for planning multiple rating during currency conversion. The query is based on the aggregation level Monthly Plan (New) (/ERP/LP_AL01).

No navigation option exists.

No switches are assigned to this query.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Calendar Year/Month 0CALMONTH 0P_FCLM_LP_PLAN_MONTH

Characteristic Planning Unit /ERP/ORG_UNIT 0P_FCLM_ORG_UNIT

Characteristic Client 0MANDT 0SYMANDT

Characteristic Planning Cycle /ERP/VMONTH 0P_FCLM_LP_PLAN_VERSION

Characteristic Planning Type /ERP/PLANTYPE 0P_FCLM_LP_PLANNING_TYPE

Characteristic Conversion Partner /ERP/TDP_CC 0P_FCLM_CONVERSIONPARTNER

Characteristic Conversion Currency /ERP/TCUR 0P_CONVERSION_TARGETCURRENCY

Characteristic Liquidity Item /ERP/LIQITEM 0P_FCLM_LIQUIDITYITEM_CC

Characteristic Currency 0CURRENCY 0P_FCLM_CIRRENCY_CC

Characteristic Line Item /ERP/LITEMRAT 1

Free Characteristics

Object Type Name Technical Name

Characteristic Calendar Year/Month 0CALMONTH

Characteristic Planning Unit /ERP/ORG_UNIT

Characteristic Client 0MANDT

Characteristic Planning Cycle /ERP/VMONTH

Characteristic Planning Type /ERP/PLANTYPE

Characteristic Conversion Partner /ERP/TDP_CC

Characteristic Conversion Currency /ERP/TCUR

Characteristic Liquidity Item /ERP/LIQITEM

This is custom documentation. For more information, please visit the SAP Help Portal 29
2/24/2024

Object Type Name Technical Name

Characteristic Currency 0CURRENCY

Characteristic Line Item /ERP/LITEMRAT

Variables

Object Type Name Technical Name

Variable Planning Month 0P_FCLM_LP_PLAN_MONTH

Variable Planning Unit 0P_FCLM_ORG_UNIT

Variable System Client 0SYMANDT

Variable Planning Cycle 0P_FCLM_LP_PLAN_VERSION

Variable Planning Type 0P_FCLM_PLANNING_TYPE

Variable Conversion Partner 0P_FCLM_CONVERSIONPARTNER

Variable Conversion Currency 0P_CONVERSION_TARGETCURRENCY

Variable Liquidity Item 0P_FCLM_LIQUIDITYITEM_CC

Variable Currency 0P_FCLM_CURRENCY_CC

Rows

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Line Item /ERP/LITEMRAT

Columns

Object Type Name Technical Name Value Restriction / Calculation

Key Figure Amount Key Figure=Planning

InfoProvider=/ERP/LP_IC02

Suggest Value Source = #

Key Figure Exchange Rate Key Figure=Multiple Planning Rating

InfoProvider=/ERP/LP_IC02

Suggest Value Source = #

Report/Report Interfaces

Object Type Name Technical Name

Develop Liquidity Plans-Data Entry 0FCLM_MLP_INPUT

Develop Liquidity Plans-Review 0FCLM_MLP_REVIEW

Develop Liquidity Plans-Display 0FCLM_MLP_DISPLAY

Aggregation Details
/ERP/FCLM_LP_AL01_Q0006

Use
This query allows you to check the details of planned values in aggregation currency. Using the liquidity item hierarchy, this query shows plan values for the selected month and for the
selected liquidity item in aggregation currency.

This query is based on the aggregation level Monthly Liquidity Plans (/ERP/LP_AL01).

No navigation option exists for this query.

Switches are not assigned to this query.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

This is custom documentation. For more information, please visit the SAP Help Portal 30
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Calendar Year/Month 0CALMONTH 0P_FCLM_LP_PLAN_MONTH

0P_FCLM_LP_PLAN_MONTH+1

0P_FCLM_LP_PLAN_MONTH+2

0P_FCLM_LP_PLAN_MONTH+3

0P_FCLM_LP_PLAN_MONTH+4

0P_FCLM_LP_PLAN_MONTH+5

0P_FCLM_LP_PLAN_MONTH+6

0P_FCLM_LP_PLAN_MONTH+7

0P_FCLM_LP_PLAN_MONTH+8

0P_FCLM_LP_PLAN_MONTH+9

0P_FCLM_LP_PLAN_MONTH+10

0P_FCLM_LP_PLAN_MONTH+11

Characteristic Planning Unit /ERP/ORG_UNIT 0P_FCLM_ORG_UNIT

Characteristic Client 0MANDT 0SYMANDT

Characteristic Planning Cycle /ERP/VMONTH 0P_FCLM_LP_PLAN_VERSION

Characteristic Planning Type /ERP/PLANTYPE 0P_FCLM_PLANNING_TYPE

Free Characteristics

Object Type Name Technical Name

Characteristic Calendar Year/Month 0CALMONTH

Characteristic Planning Unit /ERP/ORG_UNIT

Characteristic Client 0MANDT

Characteristic Planning Cycle /ERP/VMONTH

Characteristic Planning type /ERP/PLANTYPE

Characteristic Planning Currency 0CURRENCY

Characteristic Liquidity Item /ERP/LQITEM

Characteristic Calendar Year/Month 0CALMONTH

Variables

Object Type Name Technical Name

Variable Planning Month 0P_FCLM_LP_PLAN_MONTH

Variable Planning Unit 0P_FCLM_ORG_UNIT

Variable System Client 0SYMANDT

Variable Planning Cycle 0P_FCLM_LP_PLAN_VERSION

Variable Planning Type 0P_FCLM_PLANNING_TYPE

Variable Key Date 0P_FCLM_KEY_DATE

Variable Exchange Rate Type 0P_FCLM_RTYPE

Variable Target Currency 0P_FCLM_AG_CURRENCY

Rows

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Planning Currency 0CURRENCY Not Applicable

Characteristic Liquidity Item /ERP/LQITEM Not Applicable

Columns

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Calendar Year/Month 0CALMONTH Not Applicable

Key Figure Amount in Planning Currency Key Figure=Planning

InfoProvider=/ERP/LP_IC01

Suggest Value Source = #

Key Figure Exchange Rate Not applicable

This is custom documentation. For more information, please visit the SAP Help Portal 31
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Key Figure Amount in Aggregation Currency Key Figure= Planning

InfoProvider=/ERP/LP_IC01

Suggest Value Source = #

Report/Report Interfaces

Object Type Name Technical Name

Develop Liquidity Plans-Aggregation View 0FCLM_MLP_AGGVIEW

Liquidity Plans by Planning Currency (Graphic View)

/ERP/FCLM_LP_MP01_Q0002

Use
This query allows you to analyze liquidity plans by planning currency in the graphic view. You can compare the plan amounts of the selected liqudity plan with the previous plan version
and view the maximun and minimun plan amounts for each month.

This query is based on the MultiProvider MultiProvider (New Liquidity Plan) (/ERP/LP_MP01).

No navigation option exists for this query.

Switches are not assigned to this query.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Reference Source /ERP/SUGSRC #

Characteristic Version /ERP/VMONTH 0P_FCLM_LP_PLAN_VERSION

0P_FCLM_LP_PLAN_VERSION-1

0P_FCLM_LP_PLAN_VERSION-2

0P_FCLM_LP_PLAN_VERSION-3

0P_FCLM_LP_PLAN_VERSION-4

0P_FCLM_LP_PLAN_VERSION-5

0P_FCLM_LP_PLAN_VERSION-6

0P_FCLM_LP_PLAN_VERSION-7

0P_FCLM_LP_PLAN_VERSION-8

0P_FCLM_LP_PLAN_VERSION-9

0P_FCLM_LP_PLAN_VERSION-10

0P_FCLM_LP_PLAN_VERSION-11

Characteristic Client 0MANDT 0SYMANDT

Characteristic Month in Selected Planning Cycle 0CALMONTH 0P_FCLM_LP_PLAN_MONTH

0P_FCLM_LP_PLAN_MONTH+1

0P_FCLM_LP_PLAN_MONTH+2

0P_FCLM_LP_PLAN_MONTH+3

0P_FCLM_LP_PLAN_MONTH+4

0P_FCLM_LP_PLAN_MONTH+5

0P_FCLM_LP_PLAN_MONTH+6

0P_FCLM_LP_PLAN_MONTH+7

0P_FCLM_LP_PLAN_MONTH+8

0P_FCLM_LP_PLAN_MONTH+9

0P_FCLM_LP_PLAN_MONTH+10

0P_FCLM_LP_PLAN_MONTH+11

Characteristic Planning Unit /ERP/ORG_UNIT 0P_FCLM_ORG_UNIT

Characteristic Currency 0CURRENCY 0N_FCLM_SEVERAL_LQITEM

Characteristic Liquidity Item /ERP/LQITEM 0N_FCLM_SEVERAL_LQITEM

This is custom documentation. For more information, please visit the SAP Help Portal 32
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Planning Type /ERP/PLANTYPE '#', 0P_FCLM_PLANNING_TYPE

Characteristic InfoProvider 0INFOPROV '/ERP/LP_IC01', '/ERP/CFA_VP01'

Variables

Object Type Name Technical Name

Variable Planning Currency 0P_FCLM_LP_PCURR

Variable Node of Planning Unit 0P_FCLM_ORGUNIT_P_C

Variable Planning Cycle 0P_FCLM_LP_PLAN_VERSION

Variable Liquidity Item Hierarchy 0P_LQI_HIER

Variable Liquidity Item Nodes 0N_FCLM_SEVERAL_LQITEM

Variable Planning Type 0P_FLCM_PLANNING_TYPE

Variable First Day of Version Month 0P_FCLM_FIRST_DAY_OF_VERSION

Variable System Client (SY-MANDT) 0SYMANDT

Variable Active Planning Unit Hierarchy 0H_FCLM_PU_HIER

Variable Text Variable for Version 0T_FCLM_LP_VERSION

Variable Planning Month 0P_FCLM_LP_PLAN_MONTH

Rows

Object Type Name Technical Name Value Restriction / Calculation

Key Figure Selected Planning Cycle: 1KYFNM = /ERP/PL_AMT

&0T_FCLM_LP_VERSION&
0INFOPROV = /ERP/LP_IC01

/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION

/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure Previous Planning Cycle: 1KYFNM = /ERP/PL_AMT

&0T_FCLM_LP_VERSION&
0INFOPROV = /ERP/LP_IC01

/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-1

/ERP/SUGSRC = #

/ERP/PLANTYPE = 0P_FLCM_PLANNING
_TYPE

Formula Diﬀerence from Previous Planning Cycle ʻSelected Planning Cycle:

&0T_FCLM_LP_VERSION&’ – ʻPrevious
Planning Cycle: 0T_FCLM_LP_VERSION&’

Key Figure Cash In 1KYFNM = '/ERP/CI_AMT', 0INFOPROV =

'/ERP/CFA_VP01'

Key Figure Cash Out 1KYFNM = /ERP/CO_AMT, 0INFOPROV =

/ERP/CFA_VP01

Formula Actual ʻCash In' + 'Cash Out'

Formula Diﬀerence from Actual ʻActual’ - ʻSelected Planning Cycle:

&0T_FCLM_LP_VERSION&’

Key Figure Version (S-2) 1KYFNM = /ERP/PL_AMT

0INFOPROV = /ERP/LP_IC01

/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-2

/ERP/SUGSRC = #

/ERP/PLANTYPE = 0P_FLCM_PLANNING
_TYPE

Key Figure Version (S-3) 1KYFNM = /ERP/PL_AMT

0INFOPROV = /ERP/LP_IC01

/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-3

&0T_FCLM_LP_VERSION&' == 0 ) *
ʻMinimum_Original’ + ( NOT ( ʻSelected
Planning Cycle: &0T_FCLM_LP_VERSION&’ ==
0) ) * ʻSelected Planning Cycle:
&0T_FCLM_LP_VERSION&’

This is custom documentation. For more information, please visit the SAP Help Portal 34
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Formula Version (S-1) For Max ( ʻPrevious Planning Cycle:

&0T_FCLM_LP_VERSION&’ == 0 ) *
ʻMinimum_Original’ + ( NOT ( ʻPrevious
Planning Cycle: &0T_FCLM_LP_VERSION&’ ==
0) ) * ʻPrevious Planning Cycle:
&0T_FCLM_LP_VERSION&’

Formula Version (S-2) For Max ( ʻVersion (S-2)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-2)’ == 0) ) * ʻVersion (S-2)’

Formula Version (S-3) For Max ( ʻVersion (S-3)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-3)’ == 0) ) * ʻVersion (S-3)’

Formula Version (S-4) For Max ( ʻVersion (S-4)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-4)’ == 0) ) * ʻVersion (S-4)’

Formula Version (S-5) For Max ( ʻVersion (S-5)’ == 0 ) * ʻMinimum_Original’ + (

NOT ( ʻVersion (S-5)’ == 0) ) * ʻVersion (S-5)’

Formula Version (S-6) For Max ( ʻVersion (S-6)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-6)’ == 0) ) * ʻVersion (S-6)’

Formula Version (S-7) For Max ( ʻVersion (S-7)’ == 0 ) * ʻMinimum_Original’ + (

NOT ( ʻVersion (S-7)’ == 0) ) * ʻVersion (S-7)’

Formula Version (S-8) For Max ( ʻVersion (S-8)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-8)’ == 0) ) * ʻVersion (S-8)’

Formula Version (S-9) For Max ( ʻVersion (S-9)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-9)’ == 0) ) * ʻVersion (S-9)’

Formula Version (S-10) For Max ( ʻVersion (S-10)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-10)’ == 0) ) * ʻVersion (S-
10)’

Formula Version (S-11) For Max ( ʻVersion (S-11)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-11)’ == 0) ) * ʻVersion (S-11)’

Formula Version (S) For Min ( ʻSelected Planning Cycle:

&0T_FCLM_LP_VERSION&’ == 0 ) *
ʻMaximum_Original’ + ( NOT ( ʻSelected
Planning Cycle: &0T_FCLM_LP_VERSION&’ ==
0) ) * ʻSelected Planning Cycle:
&0T_FCLM_LP_VERSION&’

Formula Version (S-1) For Min ( ʻPrevious Planning Cycle:

&0T_FCLM_LP_VERSION&’ == 0 ) *
ʻMaximum_Original’ + ( NOT ( ʻPrevious
Planning Cycle: &0T_FCLM_LP_VERSION&’ ==
0) ) * ʻPrevious Planning Cycle:
&0T_FCLM_LP_VERSION&’

Formula Version (S-2) For Min ( ʻVersion (S-2)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-2)’ == 0) ) * ʻVersion (S-2)’

Formula Version (S-3) For Min ( ʻVersion (S-3)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-3)’ == 0) ) * ʻVersion (S-3)’

Formula Version (S-4) For Min ( ʻVersion (S-4)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-4)’ == 0) ) * ʻVersion (S-4)’

Formula Version (S-5) For Min ( ʻVersion (S-5)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-5)’ == 0) ) * ʻVersion (S-5)’

Formula Version (S-6) For Min ( ʻVersion (S-6)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-6)’ == 0) ) * ʻVersion (S-6)’

Formula Version (S-7) For Min ( ʻVersion (S-7)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-7)’ == 0) ) * ʻVersion (S-7)’

Formula Version (S-8) For Min ( ʻVersion (S-8)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-8)’ == 0) ) * ʻVersion (S-8)’

Formula Version (S-9) For Min ( ʻVersion (S-9)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-9)’ == 0) ) * ʻVersion (S-9)’

Formula Version (S-10) For Min ( ʻVersion (S-10)’ == 0 ) * ʻMaximum_Original’

+ ( NOT ( ʻVersion (S-10)’ == 0) ) * ʻVersion (S-
10)’

Formula Version (S-11) For Min ( ʻVersion (S-11)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-11)’ == 0) ) * ʻVersion (S-11)’

Formula Minimum_Original MIN( MIN( MIN( MIN( MIN( MIN( MIN( MIN(
MIN( MIN( MIN( 'Selected Planning Cycle',
'Previous Planning Cycle' ) , 'Version (S-2)' ) ,
'Version (S-3)' ) , 'Version (S-4)' ) , 'Version (S-
5)' ) , 'Version (S-6)' ) , 'Version (S-7)' ) ,
'Version (S-8)' ) , 'Version (S-9)' ) , 'Version (S-
10)' ) , 'Version (S-11)' )

This is custom documentation. For more information, please visit the SAP Help Portal 35
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Formula Maximum_Original MAX( MAX( MAX( MAX( MAX( MAX( MAX(

MAX( MAX( MAX( MAX( 'Selected Planning
Cycle', 'Previous Planning Cycle' ) , 'Version (S-
2)' ) , 'Version (S-3)' ) , 'Version (S-4)' ) ,
'Version (S-5)' ) , 'Version (S-6)' ) , 'Version (S-
7)' ) , 'Version (S-8)' ) , 'Version (S-9)' ) ,
'Version (S-10)' ) , 'Version (S-11)' )

Formula Minimum Plan Amount MIN( MIN( MIN( MIN( MIN( MIN( MIN( MIN(
MIN( MIN( MIN( 'Version (S) For Min', 'Version
(S-1) For Min' ) , 'Version (S-2) For Min' ) ,
'Version (S-3) For Min' ) , 'Version (S-4) For Min'
) , 'Version (S-5) For Min' ) , 'Version (S-6) For
Min' ) , 'Version (S-7) For Min' ) , 'Version (S-8
For Min)' ) , 'Version (S-9) For Min' ) , 'Version
(S-10) For Min' ) , 'Version (S-11) For Min' )

Formula Maximum Plan Amount MAX( MAX( MAX( MAX( MAX( MAX( MAX(
MAX( MAX( MAX( MAX( 'Version (S) For Max',
'Version (S-1) For Max' ) , 'Version (S-2) For
Max' ) , 'Version (S-3) For Max' ) , 'Version (S-
4) For Max' ) , 'Version (S-5) For Max' ) ,
'Version (S-6) For Max' ) , 'Version (S-7) For
Max' ) , 'Version (S-8) For Max' ) , 'Version (S-
9) For Max' ) , 'Version (S-10) For Max' ) ,
'Version (S-11) For Max' )

Columns

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Month in Selected Planning Cycle 0CALMONTH Not applicable

Report/Report Interfaces

Object Type Name Technical Name

Analyze Liquidity Plans by Planning Currency SAP BusinessObjects Design Studio Application:
0FCLM_PV_PCUR

Planning Status
/ERP/FCLM_LP_BPC_Q0011

Use
This is a display query that shows the work status by active planning unit hierarchy and planning cycle.

This query is based on the aggregation level Monthly Liquidity Plans (/ERP/LP_AL01).

No navigation option exists for this query.

No switches are assigned to this query.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Version /ERP/VMONTH 0P_FCLM_LP_PLAN_VERSION

0P_FCLM_LP_PLAN_VERSION +1

0P_FCLM_LP_PLAN_VERSION +2

0P_FCLM_LP_PLAN_VERSION +3

0P_FCLM_LP_PLAN_VERSION +4

0P_FCLM_LP_PLAN_VERSION +5

0P_FCLM_LP_PLAN_VERSION +6

0P_FCLM_LP_PLAN_VERSION +7

0P_FCLM_LP_PLAN_VERSION +8

0P_FCLM_LP_PLAN_VERSION +9

0P_FCLM_LP_PLAN_VERSION +10

0P_FCLM_LP_PLAN_VERSION +11

This is custom documentation. For more information, please visit the SAP Help Portal 36
2/24/2024
Free Characteristics

Object Type Name Technical Name

Characteristic Planning Unit /ERP/ORG_UNIT

Characteristic Planning Cycle /ERP/VMONTH

Variables

Object Type Name Technical Name

Variable Planning Cycle 0P_FCLM_LP_PLAN_VERSION

Variable Hierarchy for Org OH_FCLM_ORG_UNIT

Rows

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Planning Unit 0P_FCLM_ORG_UNIT Not applicable

Columns

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Month /ERP/VMONTH Not applicable

Key Figure Work: Status BPC:WS Order Not applicable

Report/Report Interfaces

Object Type Name Technical Name

Develop Liquidity Plans-Data Entry 0FCLM_MLP_INPUT

Develop Liquidity Plans-Review 0FCLM_MLP_REVIEW

Develop Liquidity Plans-Display 0FCLM_MLP_DISPLAY

Develop Liquidity Plans-Track Work Status 0FCLM_MLP_STATUS

Liquidity Plans by Planning Currency

/ERP/FCLM_LP_MP01_Q0001

Use
This query is used in the table view which is one of modes to analyze liquidity plans by planning currency.

This query shows the actual, forecast and planned data in planning currency for the 12 calendar months in the selected planning cycle. It also shows the planned data of the selected
planning cycle in the last 11 calendar months. You can not only get the liquidity forecast for the future months, but also compare the liquidity data of the selected planning cycle with
that of the previous versions.

This query is based on the MultiProvider Liquidity Planning (/ERP/LP_MP01).

No navigation option exists for this query.

Switches are not assigned to this query.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Reference Source /ERP/SUGSRC #

This is custom documentation. For more information, please visit the SAP Help Portal 37
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Version /ERP/VMONTH #

0P_FCLM_LP_PLAN_VERSION,

0P_FCLM_LP_PLAN_VERSION -1

0P_FCLM_LP_PLAN_VERSION -2

0P_FCLM_LP_PLAN_VERSION -3

0P_FCLM_LP_PLAN_VERSION -4

0P_FCLM_LP_PLAN_VERSION -5

0P_FCLM_LP_PLAN_VERSION -6

0P_FCLM_LP_PLAN_VERSION -7

0P_FCLM_LP_PLAN_VERSION -8

0P_FCLM_LP_PLAN_VERSION -9

0P_FCLM_LP_PLAN_VERSION -10

0P_FCLM_LP_PLAN_VERSION -11

Characteristic Client 0MANDT 0SYMANDT

Characteristic Month in Selected Planning Cycle 0CALMONTH 0P_FCLM_LP_PLAN_VERSION,

0P_FCLM_LP_PLAN_VERSION+1

0P_FCLM_LP_PLAN_VERSION+2

0P_FCLM_LP_PLAN_VERSION+3

0P_FCLM_LP_PLAN_VERSION+4

0P_FCLM_LP_PLAN_VERSION+5

0P_FCLM_LP_PLAN_VERSION+6

0P_FCLM_LP_PLAN_VERSION+7

0P_FCLM_LP_PLAN_VERSION+8

0P_FCLM_LP_PLAN_VERSION+9

0P_FCLM_LP_PLAN_VERSION+10

0P_FCLM_LP_PLAN_VERSION+11

Characteristic Planning Unit /ERP/ORG_UNIT 0P_FCLM_ORG_UNIT

Characteristic Currency 0CURRENCY 0P_FCLM_LP_PCURR

Characteristic Liquidity Item /ERP/LQITEM 0N_FCLM_SEVERAL_LQITEM(0P_LQI_HIER,

0P_FCLM_FIRST_DAY_OF_VERSION)

Characteristic Planning Type /ERP/PLANTYPE #, 0P_FLCM_PLANNING_TYPE

Characteristic InfoProvider 0INFOPROV /ERP/LP_IC01, /ERP/CFA_VP01,

/ERP/LP_VP3

Variables

Object Type Name Technical Name

Variable Planning Currency 0P_FCLM_LP_PCURR

Variable Planning Unit 0P_FCLM_ORG_UNIT

Variable Planning Cycle 0P_FCLM_LP_PLAN_VERSION

Variable Liquidity Item Hierarchy 0P_LQI_HIER

Variable Several Liquidity Item Node 0N_FCLM_SEVERAL_LQITEM

Variable Planning Type 0P_FLCM_PLANNING_TYPE

Variable First Day of Version Month 0P_FCLM_FIRST_DAY_OF_VERSION

Variable System Client (SY-MANDT) 0SYMANDT

Variable Text variable for version 0T_FCLM_LP_VERSION

Rows

Object Type Name Technical Name Value Restriction / Calculation

Key Figure Forecast Cash In 1KYFNM = /ERP/LQF_IN,

0INFOPROV = /ERP/LP_VP3

This is custom documentation. For more information, please visit the SAP Help Portal 38
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Key Figure Forecast Cash Out 1KYFNM = /ERP/ LQF_OUT,

0INFOPROV = /ERP/LP_VP3

Formula Forecast ( ʻForecast Cash In’ – ʻForecast Cash Out’ ) * (

ʻ[0P_REPLACE_INFOOBJECT] Month Object’
>= ʻ[0P_FCLM_CURRENTMONTH] Current
Month(Sap Exist)’ )

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION, /ERP/SUGSRC
= #, /ERP/PLANTYPE = 0P_FLCM_PLANNING
_TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-1,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-2,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-3,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-4,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-5,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-6,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-7,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-8,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-9,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-10,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-11,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Columns

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Month in Selected Planning Cycle 0CALMONTH Not applicable

This is custom documentation. For more information, please visit the SAP Help Portal 39
2/24/2024
Report/Report Interfaces

Object Type Name Technical Name

Analyze Liquidity Plans by Planning Currency SAP BusinessObjects Design Studio Application:
0FCLM_PV_PCUR

Liquidity Plans by Aggregation Currency

/ERP/FCLM_LP_MP01_Q0007

Use
This query is used in the table view, which is one of modes to analyze liquidity plans by aggregation currency.

This query is based on the Liquidity Planning (/ERP/LP_MP01).

No navigation option exists for this query.

No switches are assigned to this query.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Reference Source /ERP/SUGSRC '#'

Version /ERP/VMONTH '#'

0P_FCLM_LP_PLAN_VERSION-1

0P_FCLM_LP_PLAN_VERSION-2

0P_FCLM_LP_PLAN_VERSION-3

0P_FCLM_LP_PLAN_VERSION-4

0P_FCLM_LP_PLAN_VERSION-5

0P_FCLM_LP_PLAN_VERSION-6

0P_FCLM_LP_PLAN_VERSION-7

0P_FCLM_LP_PLAN_VERSION-8

0P_FCLM_LP_PLAN_VERSION-9

0P_FCLM_LP_PLAN_VERSION-10

0P_FCLM_LP_PLAN_VERSION-11

Characteristic Client 0MANDT 0SYMANDT

Characteristic Calendar Year/Month 0CALMONTH 0P_FCLM_LP_PLAN_MONTH

0P_FCLM_LP_PLAN_MONTH+1

0P_FCLM_LP_PLAN_MONTH+2

0P_FCLM_LP_PLAN_MONTH+3

0P_FCLM_LP_PLAN_MONTH+4

0P_FCLM_LP_PLAN_MONTH+5

0P_FCLM_LP_PLAN_MONTH+6

0P_FCLM_LP_PLAN_MONTH+7

0P_FCLM_LP_PLAN_MONTH+8

0P_FCLM_LP_PLAN_MONTH+9

0P_FCLM_LP_PLAN_MONTH+10

0P_FCLM_LP_PLAN_MONTH+11

Characteristic Planning Unit /ERP/ORG_UNIT 0N_FCLM_ORG_UNIT_P_C

(OH_FCLM_PU_HIER)

Characteristic Liquidity Item /ERP/LQITEM 0N_FCLM_SEVERAL_LQITEM

(0P_LQI_HIER,
0P_FCLM_FIRST_DAY_OF_VERSION)

This is custom documentation. For more information, please visit the SAP Help Portal 40
2/24/2024
Variables

Object Type Name Technical Name

Variable Planning Unit 0P_FCLM_ORG_UNIT

Variable Planning Cycle 0P_FCLM_LP_PLAN_VERSION

Variable Liquidity Item Hierarchy 0P_LQI_HIER

Liquidity Item Nodes 0N_FCLM_SEVERAL_LQITEM

Variable Planning Type 0P_FLCM_PLANNING_TYPE

Variable First Day of Version Month 0P_FCLM_FIRST_DAY_OF_VERSION

Variable System Client (SY-MANDT) 0SYMANDT

Variable Text Variable for Version 0T_FCLM_LP_VERSION

Variable Exchange Rate Type 0P_FCLM_RTYPE

Variable 0P_FCLM_AG_CURRENCY 0P_FCLM_AG_CURRENCY

Variable Liquidity Item Hierarchy Key Date 0P_FCLM_KEY_DATE

Rows

Object Type Name Technical Name Value Restriction / Calculation

Key Figure Forecast Cash In 1KYFNM = /ERP/LQF_IN,

0INFOPROV = /ERP/LP_VP3

Key Figure Forecast Cash Out 1KYFNM = /ERP/ LQF_OUT,

0INFOPROV = /ERP/LP_VP3

Formula Forecast ( ʻForecast Cash In’ – ʻForecast Cash Out’ ) * (

ʻ[0P_REPLACE_INFOOBJECT] Month Object’
>= ʻ[0P_FCLM_CURRENTMONTH] Current
Month(Sap Exist)’ )

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION, /ERP/SUGSRC
= #, /ERP/PLANTYPE = 0P_FLCM_PLANNING
_TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-1,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-2,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-3,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-4,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-5,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-6,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-7,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

This is custom documentation. For more information, please visit the SAP Help Portal 41
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-8,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-9,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-10,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Key Figure &0T_FCLM_LP_VERSION& Cycle 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-11,
/ERP/SUGSRC = #, /ERP/PLANTYPE =
0P_FLCM_PLANNING _TYPE

Columns

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Month in Selected Planning Cycle 0CALMONTH

Report/Report Interfaces

Object Type Name Technical Name

Liquidity Plans by Aggregation Currency SAP BusinessObjects Design Studio Application:

0FCLM_ALP_ACUR

Diﬀerence Details by Planning Currency

/ERP/FCLM_LP_MP01_Q0006

Use
This query is used for checking the difference details of planned data by planning currency. It calculates the difference and absolute difference through liquidity item hierarchy and
compares planned data in a selected planning cycle and those in the previous planning cycle in planning currency.

This query is based on the MultiProvider Liquidity Planning (/ERP/LP_MP01).

No navigation option exists for this query.

No switches are assigned to this query.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Reference Source /ERP/SUGSRC '#'

Characteristic Version /ERP/VMONTH '#', 0P_FCLM_LP_PLAN_VERSION

0P_FCLM_LP_PLAN_VERSION-1

Characteristic Client 0MANDT 0SYMANDT

Characteristic Calendar Year/Month 0CALMONTH 0P_FCLM_CALMONTH

Planning Unit /ERP/ORG_UNIT 0P_FCLM_ORG_UNIT

Characteristic Currency 0CURRENCY 0P_FCLM_LP_PCURR

Characteristic Liquidity Item /ERP/LQITEM 0N_FCLM_SEVERAL_LQITEM

Characteristic Planning Type /ERP/PLANTYPE 0P_FLCM_PLANNING_TYPE,'#'

Variables

Object Type Name Technical Name

Variable Planning Currency 0P_FCLM_LP_PCURR

This is custom documentation. For more information, please visit the SAP Help Portal 42
2/24/2024

Object Type Name Technical Name

Variable Planning Unit 0P_FCLM_ORG_UNIT

Variable Planning Cycle 0P_FCLM_LP_PLAN_VERSION

Variable Liquidity Item Hierarchy 0P_LQI_HIER

Variable Liquidity Item Nodes 0N_FCLM_SEVERAL_LQITEM

Variable Planning Type 0P_FLCM_PLANNING_TYPE

Variable First Day of Version Month 0P_FCLM_FIRST_DAY_OF_VERSION

Variable Calendar Month 0P_FCLM_CALMONTH

Variable System Client (SY-MANDT) 0SYMANDT

Variable Text Variable for Version 0T_FCLM_LP_VERSION

Variable Node of Planning Unit 0N_FCLM_ORGUNIT_P_C

Variable Active Planning Unit Hierarchy 0H_FCLM_PU_HIERARCHY

Rows

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Liquidity Item /ERP/LQITEM

Columns

Object Type Name Technical Name Value Restriction / Calculation

Key Figure Selected Cycle - &0T_FCLM_LP_VERSION& 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/SUGSRC = #,
/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION

Key Figure Previous Cycle - &0T_FCLM_LP_VERSION& 1KYFNM = /ERP/PL_AMT, 0INFOPROV =

/ERP/LP_IC01, /ERP/SUGSRC = #,
/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-1

Formula Diﬀerence ʻSelected Cycle - &0T_FCLM_LP_VERSION&’

– ʻPrevious Cycle - &0T_FCLM_LP_VERSION&’

Formula Diﬀerence (Absolute) ABS(( ʻSelected Cycle -

&0T_FCLM_LP_VERSION&’ – ʻPrevious Cycle -
&0T_FCLM_LP_VERSION&’ ))

Report/Report Interfaces

Object Type Name Technical Name

Diﬀerence Details by Planning Currency SAP BusinessObjects Design Studio Application:

0FCLM_ALP_BY_LQITEM_PCUR

Liquidity Plans by Aggregation Currency (Graphic View)

/ERP/FCLM_LP_MP01_Q0008

Use
This query allows you to analyze liquidity plans by aggregation currency in the graphic view.

The query compares the plan amounts of the selected liquidity plan with the previous plan version and view the maximun and minimun plan amounts for each month.

This query is based on the MultiProvider MultiProvider (New Liquidity Plan) (/ERP/LP_MP01).

No navigation option exists for this query.

Switches are not assigned to this query.

This query is used in the graphic view which is one of modes to analyze liquidity plans by aggregation currency.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Reference Source /ERP/SUGSRC '#'

This is custom documentation. For more information, please visit the SAP Help Portal 43
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Version /ERP/VMONTH 0P_FCLM_LP_PLAN_VERSION

0P_FCLM_LP_PLAN_VERSION-1

0P_FCLM_LP_PLAN_VERSION-2

0P_FCLM_LP_PLAN_VERSION-3

0P_FCLM_LP_PLAN_VERSION-4

0P_FCLM_LP_PLAN_VERSION-5

0P_FCLM_LP_PLAN_VERSION-6

0P_FCLM_LP_PLAN_VERSION-7

0P_FCLM_LP_PLAN_VERSION-8

0P_FCLM_LP_PLAN_VERSION-9

0P_FCLM_LP_PLAN_VERSION-10

0P_FCLM_LP_PLAN_VERSION-11

Characteristic Client 0MANDT 0SYMANDT

Characteristic Month in the Selected Planning Cycle 0CALMONTH 0P_FCLM_LP_PLAN_MONTH

0P_FCLM_LP_PLAN_MONTH+1

0P_FCLM_LP_PLAN_MONTH+2

0P_FCLM_LP_PLAN_MONTH+3

0P_FCLM_LP_PLAN_MONTH+4

0P_FCLM_LP_PLAN_MONTH+5

0P_FCLM_LP_PLAN_MONTH+6

0P_FCLM_LP_PLAN_MONTH+7

0P_FCLM_LP_PLAN_MONTH+8

0P_FCLM_LP_PLAN_MONTH+9

0P_FCLM_LP_PLAN_MONTH+10

0P_FCLM_LP_PLAN_MONTH+11

Characteristic Planning Unit /ERP/ORG_UNIT 0P_FCLM_ORG_UNIT

Characteristic Liquidity Item /ERP/LQITEM 0N_FCLM_SEVERAL_LQITEM

Characteristic Planning Type /ERP/PLANTYPE '#', 0P_FCLM_PLANNING_TYPE

Characteristic InfoProvider 0INFOPROV '/ERP/LP_IC01', '/ERP/CFA_VP01'

Variables

Object Type Name Technical Name

Variable Node of Planning Unit 0N_FCLM_ORGUNIT_P_C

Variable Planning Cycle 0P_FCLM_LP_PLAN_VERSION

Variable Liquidity Item Hierarchy 0P_LQI_HIER

Variable Liquidity Item Nodes 0N_FCLM_SEVERAL_LQITEM

Variable Planning Type 0P_FLCM_PLANNING_TYPE

Variable First Day of Version Month 0P_FCLM_FIRST_DAY_OF_VERSION

Variable System Client (SY-MANDT) 0SYMANDT

Variable Active Planning Unit Hierarchy 0H_FCLM_PU_HIER

Variable Text Variable for Version 0H_FCLM_LP_VERSION

Variable Planning Month 0H_FCLM_LP_PLAN_MONTH

Variable Exchange Rate Type 0P_FCLM_RTYPE

Variable 0P_FCLM_AG_CURRENCY 0P_FCLM_AG_CURRENCY

Variable Aggregation Currency for Planning Unit Hierarchy 0P_FCLM_ALERT_AG_CUR

Variable Liquidity Item Hierarchy Key Date 0P_FCLM_KEY_DATE

Rows

Object Type Name Technical Name Value Restriction / Calculation

This is custom documentation. For more information, please visit the SAP Help Portal 44
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Key Figure Selected Planning Cycle: 1KYFNM = '/ERP/PL_AMT'

&0T_FCLM_LP_VERSION&
0INFOPROV = '/ERP/LP_IC01'

/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION

/ERP/SUGSRC = '#'

/ERP/PLANTYPE = 0P_FLCM_PLANNING
_TYPE

*Currency translation with conversion type

0FCLM_TCC

Key Figure Previous Planning Cycle: 1KYFNM = /ERP/PL_AMT

&0T_FCLM_LP_VERSION&
0INFOPROV = /ERP/LP_IC01

/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-1

/ERP/SUGSRC = #

/ERP/PLANTYPE = 0P_FLCM_PLANNING
_TYPE

*Currency translation with conversion type

0FCLM_TCC

Formula Diﬀerence from Previous Planning Cycle ʻSelected Planning Cycle:

&0T_FCLM_LP_VERSION&’ – ʻPrevious
Planning Cycle: &0T_FCLM_LP_VERSION&’

Key Figure Cash In 1KYFNM = '/ERP/CI_AMT'

0INFOPROV = '/ERP/CFA_VP01'

*Currency translation with conversion type

Key Figure Version (S-3) 1KYFNM = /ERP/PL_AMT

0INFOPROV = /ERP/LP_IC01

/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-4

/ERP/SUGSRC = #

/ERP/PLANTYPE = 0P_FLCM_PLANNING
_TYPE

*Currency translation with conversion type

0FCLM_TCC

Key Figure Version (S-4) 1KYFNM = /ERP/PL_AMT

0INFOPROV = /ERP/LP_IC01

/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-4

/ERP/SUGSRC = #

/ERP/PLANTYPE = 0P_FLCM_PLANNING
_TYPE

*Currency translation with conversion type

0FCLM_TCC

This is custom documentation. For more information, please visit the SAP Help Portal 45
2/24/2024

0FCLM_TCC

This is custom documentation. For more information, please visit the SAP Help Portal 46
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Key Figure Version (S-11) 1KYFNM = /ERP/PL_AMT

0INFOPROV = /ERP/LP_IC01

/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-11

/ERP/SUGSRC = #

/ERP/PLANTYPE = 0P_FLCM_PLANNING
_TYPE

*Currency translation with conversion type

0FCLM_TCC

Formula Version (S) For Max ( ʻSelected Planning Cycle:

&0T_FCLM_LP_VERSION&’ == 0 ) *
ʻMinimum_Original’ + ( NOT ( ʻSelected
Planning Cycle: &0T_FCLM_LP_VERSION&’ ==
0) ) * ʻSelected Planning Cycle:
&0T_FCLM_LP_VERSION&’

Formula Version (S-1) For Max ( ʻPrevious Planning Cycle: :

&0T_FCLM_LP_VERSION&’ == 0 ) *
ʻMinimum_Original’ + ( NOT ( ʻPrevious
Planning Cycle: &0T_FCLM_LP_VERSION&’ ==
0) ) * ʻPrevious Planning Cycle:
&0T_FCLM_LP_VERSION&’

Formula Version (S-2) For Max ( ʻVersion (S-2)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-2)’ == 0) ) * ʻVersion (S-2)’

Formula Version (S-3) For Max ( ʻVersion (S-3)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-3)’ == 0) ) * ʻVersion (S-3)’

Formula Version (S-4) For Max ( ʻVersion (S-4)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-4)’ == 0) ) * ʻVersion (S-4)’

Formula Version (S-5) For Max ( ʻVersion (S-5)’ == 0 ) * ʻMinimum_Original’ + (

NOT ( ʻVersion (S-5)’ == 0) ) * ʻVersion (S-5)’

Formula Version (S-6) For Max ( ʻVersion (S-6)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-6)’ == 0) ) * ʻVersion (S-6)’

Formula Version (S-7) For Max ( ʻVersion (S-7)’ == 0 ) * ʻMinimum_Original’ + (

NOT ( ʻVersion (S-7)’ == 0) ) * ʻVersion (S-7)’

Formula Version (S-8) For Max ( ʻVersion (S-8)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-8)’ == 0) ) * ʻVersion (S-8)’

Formula Version (S-9) For Max ( ʻVersion (S-9)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-9)’ == 0) ) * ʻVersion (S-9)’

Formula Version (S-10) For Max ( ʻVersion (S-10)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-10)’ == 0) ) * ʻVersion (S-
10)’

Formula Version (S-11) For Max ( ʻVersion (S-11)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-11)’ == 0) ) * ʻVersion (S-11)’

Formula Version (S) For Min ( ʻSelected Planning Cycle:

&0T_FCLM_LP_VERSION&’ == 0 ) *
ʻMaximum_Original’ + ( NOT ( ʻSelected
Planning Cycle&0T_FCLM_LP_VERSION&’ ==
0) ) * ʻSelected Planning
Cycle&0T_FCLM_LP_VERSION&’

Formula Version (S-1) For Min ( ʻPrevious Planning

Cycle&0T_FCLM_LP_VERSION&’ == 0 ) *
ʻMaximum_Original’ + ( NOT ( ʻPrevious
Planning Cycle&0T_FCLM_LP_VERSION&’ ==
0) ) * ʻPrevious Planning
Cycle&0T_FCLM_LP_VERSION&’

Formula Version (S-2) For Min ( ʻVersion (S-2)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-2)’ == 0) ) * ʻVersion (S-2)’

Formula Version (S-3) For Min ( ʻVersion (S-3)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-3)’ == 0) ) * ʻVersion (S-3)’

Formula Version (S-4) For Min ( ʻVersion (S-4)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-4)’ == 0) ) * ʻVersion (S-4)’

Formula Version (S-5) For Min ( ʻVersion (S-5)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-5)’ == 0) ) * ʻVersion (S-5)’

Formula Version (S-6) For Min ( ʻVersion (S-6)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-6)’ == 0) ) * ʻVersion (S-6)’

This is custom documentation. For more information, please visit the SAP Help Portal 47
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Formula Version (S-7) For Min ( ʻVersion (S-7)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-7)’ == 0) ) * ʻVersion (S-7)’

Formula Version (S-8) For Min ( ʻVersion (S-8)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-8)’ == 0) ) * ʻVersion (S-8)’

Formula Version (S-9) For Min ( ʻVersion (S-9)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-9)’ == 0) ) * ʻVersion (S-9)’

Formula Version (S-10) For Min ( ʻVersion (S-10)’ == 0 ) * ʻMaximum_Original’

+ ( NOT ( ʻVersion (S-10)’ == 0) ) * ʻVersion (S-
10)’

Formula Version (S-11) For Min ( ʻVersion (S-11)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-11)’ == 0) ) * ʻVersion (S-11)’

Formula Minimum_Original MIN( MIN( MIN( MIN( MIN( MIN( MIN( MIN(
MIN( MIN( MIN( 'Selected Planning Cycle:
&0T_FCLM_LP_VERSION&', 'Previous Planning
Cycle: &0T_FCLM_LP_VERSION&' ) , 'Version
(S-2)' ) , 'Version (S-3)' ) , 'Version (S-4)' ) ,
'Version (S-5)' ) , 'Version (S-6)' ) , 'Version (S-
7)' ) , 'Version (S-8)' ) , 'Version (S-9)' ) ,
'Version (S-10)' ) , 'Version (S-11)' )

Formula Maximum_Original MAX( MAX( MAX( MAX( MAX( MAX( MAX(

MAX( MAX( MAX( MAX( 'Selected Planning
Cycle: &0T_FCLM_LP_VERSION&', 'Previous
Planning Cycle: &0T_FCLM_LP_VERSION&' ) ,
'Version (S-2)' ) , 'Version (S-3)' ) , 'Version (S-
4)' ) , 'Version (S-5)' ) , 'Version (S-6)' ) ,
'Version (S-7)' ) , 'Version (S-8)' ) , 'Version (S-
9)' ) , 'Version (S-10)' ) , 'Version (S-11)' )

Key Figure Selected Planning Cycle: 1KYFNM = '/ERP/PL_AMT'

&0T_FCLM_LP_VERSION&
0INFOPROV = '/ERP/LP_IC01'

/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION

/ERP/SUGSRC = '#'

/ERP/PLANTYPE = 0P_FLCM_PLANNING
_TYPE

*Currency translation with conversion type

0FCLM_TAC

Key Figure Previous Planning Cycle: 1KYFNM = /ERP/PL_AMT

&0T_FCLM_LP_VERSION&
0INFOPROV = /ERP/LP_IC01

/ERP/SUGSRC = #,

/ERP/PLANTYPE = 0P_FLCM_PLANNING
_TYPE

*Currency translation with conversion type

0FCLM_TAC

This is custom documentation. For more information, please visit the SAP Help Portal 49
2/24/2024

0FCLM_TAC

Formula Version (S) For Max in HQ Cur ( ʻSelected Planning Cycle:

&0T_FCLM_LP_VERSION&’ == 0 ) *
ʻMinimum_Original’ + ( NOT ( ʻSelected
Planning Cycle: &0T_FCLM_LP_VERSION&’ ==
0) ) * ʻSelected Planning Cycle:
&0T_FCLM_LP_VERSION&’

Formula Version (S-1) For Max in HQ Cur ( ʻPrevious Planning Cycle: :

&0T_FCLM_LP_VERSION&’ == 0 ) *
ʻMinimum_Original’ + ( NOT ( ʻPrevious
Planning Cycle: &0T_FCLM_LP_VERSION&’ ==
0) ) * ʻPrevious Planning Cycle:
&0T_FCLM_LP_VERSION&’

Formula Version (S-2) For Max in HQ Cur ( ʻVersion (S-2)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-2)’ == 0) ) * ʻVersion (S-2)’

Formula Version (S-3) For Max in HQ Cur ( ʻVersion (S-3)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-3)’ == 0) ) * ʻVersion (S-3)’

This is custom documentation. For more information, please visit the SAP Help Portal 50
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Formula Version (S-4) For Max in HQ Cur ( ʻVersion (S-4)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-4)’ == 0) ) * ʻVersion (S-4)’

Formula Version (S-5) For Max in HQ Cur ( ʻVersion (S-5)’ == 0 ) * ʻMinimum_Original’ + (

NOT ( ʻVersion (S-5)’ == 0) ) * ʻVersion (S-5)’

Formula Version (S-6) For Max in HQ Cur ( ʻVersion (S-6)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-6)’ == 0) ) * ʻVersion (S-6)’

Formula Version (S-7) For Max in HQ Cur ( ʻVersion (S-7)’ == 0 ) * ʻMinimum_Original’ + (

NOT ( ʻVersion (S-7)’ == 0) ) * ʻVersion (S-7)’

Formula Version (S-8) For Max in HQ Cur ( ʻVersion (S-8)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-8)’ == 0) ) * ʻVersion (S-8)’

Formula Version (S-9) For Max in HQ Cur ( ʻVersion (S-9)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-9)’ == 0) ) * ʻVersion (S-9)’

Formula Version (S-10) For Max in HQ Cur ( ʻVersion (S-10)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-10)’ == 0) ) * ʻVersion (S-
10)’

Formula Version (S-11) For Max in HQ Cur ( ʻVersion (S-11)’ == 0 ) * ʻMinimum_Original’ +

( NOT ( ʻVersion (S-11)’ == 0) ) * ʻVersion (S-11)’

Formula Version (S) For Min in HQ Cur ( ʻSelected Planning Cycle:

&0T_FCLM_LP_VERSION&’ == 0 ) *
ʻMaximum_Original’ + ( NOT ( ʻSelected
Planning Cycle&0T_FCLM_LP_VERSION&’ ==
0) ) * ʻSelected Planning
Cycle&0T_FCLM_LP_VERSION&’

Formula Version (S-1) For Min in HQ Cur ( ʻPrevious Planning

Cycle&0T_FCLM_LP_VERSION&’ == 0 ) *
ʻMaximum_Original’ + ( NOT ( ʻPrevious
Planning Cycle&0T_FCLM_LP_VERSION&’ ==
0) ) * ʻPrevious Planning
Cycle&0T_FCLM_LP_VERSION&’

Formula Version (S-2) For Min in HQ Cur ( ʻVersion (S-2)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-2)’ == 0) ) * ʻVersion (S-2)’

Formula Version (S-3) For Min in HQ Cur ( ʻVersion (S-3)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-3)’ == 0) ) * ʻVersion (S-3)’

Formula Version (S-4) For Min in HQ Cur ( ʻVersion (S-4)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-4)’ == 0) ) * ʻVersion (S-4)’

Formula Version (S-5) For Min in HQ Cur ( ʻVersion (S-5)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-5)’ == 0) ) * ʻVersion (S-5)’

Formula Version (S-6) For Min in HQ Cur ( ʻVersion (S-6)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-6)’ == 0) ) * ʻVersion (S-6)’

Formula Version (S-7) For Min in HQ Cur ( ʻVersion (S-7)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-7)’ == 0) ) * ʻVersion (S-7)’

Formula Version (S-8) For Min in HQ Cur ( ʻVersion (S-8)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-8)’ == 0) ) * ʻVersion (S-8)’

Formula Version (S-9) For Min in HQ Cur ( ʻVersion (S-9)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-9)’ == 0) ) * ʻVersion (S-9)’

Formula Version (S-10) For Min in HQ Cur ( ʻVersion (S-10)’ == 0 ) * ʻMaximum_Original’

+ ( NOT ( ʻVersion (S-10)’ == 0) ) * ʻVersion (S-
10)’

Formula Version (S-11) For Min in HQ Cur ( ʻVersion (S-11)’ == 0 ) * ʻMaximum_Original’ +

( NOT ( ʻVersion (S-11)’ == 0) ) * ʻVersion (S-11)’

Formula Minimum_Original in HQ Cur MIN( MIN( MIN( MIN( MIN( MIN( MIN( MIN(
MIN( MIN( MIN( 'Selected Planning Cycle:
&0T_FCLM_LP_VERSION&', 'Previous Planning
Cycle: &0T_FCLM_LP_VERSION&' ) , 'Version
(S-2)' ) , 'Version (S-3)' ) , 'Version (S-4)' ) ,
'Version (S-5)' ) , 'Version (S-6)' ) , 'Version (S-
7)' ) , 'Version (S-8)' ) , 'Version (S-9)' ) ,
'Version (S-10)' ) , 'Version (S-11)' )

Formula Maximum_Original in HQ Cur MAX( MAX( MAX( MAX( MAX( MAX( MAX(
MAX( MAX( MAX( MAX( 'Selected Planning
Cycle: &0T_FCLM_LP_VERSION&', 'Previous
Planning Cycle: &0T_FCLM_LP_VERSION&' ) ,
'Version (S-2)' ) , 'Version (S-3)' ) , 'Version (S-
4)' ) , 'Version (S-5)' ) , 'Version (S-6)' ) ,
'Version (S-7)' ) , 'Version (S-8)' ) , 'Version (S-
9)' ) , 'Version (S-10)' ) , 'Version (S-11)' )

This is custom documentation. For more information, please visit the SAP Help Portal 51
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Columns

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Month in Selected Planning Cycle 0CALMONTH

Report/Report Interfaces

Object Type Name Technical Name

Liquidity Plans by Aggregation Currency SAP BusinessObjects Design Studio Application:

0FCLM_PV_ACUR

Diﬀerence Details by Aggregation Currency

/ERP/FCLM_LP_MP01_Q0009

Use
This query is used for checking the diﬀerent details of planned data by aggregation currency.

It calculates the diﬀerence and absolute diﬀerence through liquidity item hierarchy and compares planned data in a selected planning cycle and those in the previous planning cycle in
aggregation currency.

This query is based on the MultiProvider Liquidity Planning (/ERP/LP_MP01).

No navigation option exists for this query.

Switches are not assigned to this query.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Reference Source /ERP/SUGSRC '#'

Characteristic Version /ERP/VMONTH 0P_FCLM_LP_PLAN_VERSION

0P_FCLM_LP_PLAN_VERSION-1

Characteristic Client 0MANDT 0SYMANDT

Characteristic Calendar Year/Month 0CALMONTH 0P_FCLM_CALMONTH

Characteristic Planning Unit /ERP/ORG_UNIT 0P_FCLM_ORG_UNIT

Characteristic Liquidity Item /ERP/LQITEM 0N_FCLM_SEVERAL_LQITEM

Characteristic Planning Type /ERP/PLANTYPE 0P_FLCM_PLANNING_TYPE

Variables

Object Type Name Technical Name

Variable Planning Unit 0P_FCLM_ORG_UNIT

Variable Planning Cycle 0P_FCLM_LP_PLAN_VERSION

Variable Liquidity Item Hierarchy 0P_LQI_HIER

Variable Liquidity Item Nodes 0N_FCLM_SEVERAL_LQITEM

This is custom documentation. For more information, please visit the SAP Help Portal 52
2/24/2024

Object Type Name Technical Name

Variable Planning Type 0P_FLCM_PLANNING_TYPE

Variable First Day of Version Month 0P_FCLM_FIRST_DAY_OF_VERSION

Variable Calendar Month 0P_FCLM_CALMONTH

Variable System Client (SY-MANDT) 0SYMANDT

Variable Text variable for version 0T_FCLM_LP_VERSION

Variable Exchange Rate Type 0P_FCLM_RTYPE

Variable 0P_FCLM_AG_CURRENCY 0P_FCLM_AG_CURRENCY

Variable Liquidity Item Hierarchy Key Date 0P_FCLM_KEY_DATE

Rows

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Liquidity Item /ERP/LQITEM

Columns

Object Type Name Technical Name Value Restriction / Calculation

Key Figure Selected Planning Cycle - 1KYFNM = /ERP/PL_AMT

&0T_FCLM_LP_VERSION&
0INFOPROV = /ERP/LP_IC01

/ERP/SUGSRC = #

/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION

*Currency translation with conversion type

0FCLM_TCC

Key Figure Previous Planning Cycle - 1KYFNM = /ERP/PL_AMT

&0T_FCLM_LP_VERSION&
0INFOPROV = /ERP/LP_IC01

/ERP/SUGSRC = #

/ERP/VMONTH =
0P_FCLM_LP_PLAN_VERSION-1

Formula Diﬀerence Selected Cycle- &0T_FCLM_LP_VERSION& –

Previous Cycle - &0T_FCLM_LP_VERSION&

Formula Diﬀerence Selected Cycle - &0T_FCLM_LP_VERSION& –

Previous Cycle - &0T_FCLM_LP_VERSION&

Report/Report Interfaces

Object Type Name Technical Name

Diﬀerence Details by Aggregation Currency SAP BusinessObjects Design Studio Application:

0FCLM_PV_BY_LQITEM_ACUR

Cash Flow Analysis

FCLM_CFA_VP01_Q0001

Use
This query shows forecast ow details in transaction currencies in a time frame for company codes. Overdue and future amounts are displayed in individual columns respectively. They
are aggregated forecast amounts for the past and future. This query also provides many free characteristics to drill down.

This query is based on VirtualProvider /ERP/CFA_VP01.

No navigation option exists for this query.

Switches are not assigned to this query.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Calendar Day 0CALDAY 0I_FCLM_ACTUAL_DATE

Characteristic Currency 0CURRENCY 0P_FCLM_TRAN_CURRENCY

Characteristic Client 0MANDT 0SYMANDT

This is custom documentation. For more information, please visit the SAP Help Portal 53
2/24/2024

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Company Code /ERP/COMPCODE 0P_FCLM_COMPANY_CODE

Free Characteristics

Object Type Name Technical Name

Company Code /ERP/COSTCNTR_/ERP/COMPCODE

Company Code /ERP/WBSELMT_/ERP/COMPCODE

Company Code /ERP/ORG_UNIT_/ERP/COMPCODE

Company Code /ERP/ACC_ID_/ERP/COMPCODE

Assigned Company Code /ERP/PAYCMPCD

Certainty Level /ERP/CERTLVL

Liquidity Item /ERP/LQITEM

Planning Group /ERP/PLGRP

Planning Level /ERP/PLLEV

Planning Unit /ERP/ORG_UNIT

House Bank Account /ERP/HBACC

House Bank /ERP/HBANK

Bank /ERP/ACC_ID_/ERP/BANK

Bank Account /ERP/ACC_ID_

Bank Acct. Desc /ERP/ACC_ID_/ERP/ACCDES

Bank Acct. Number /ERP/ACC_ID_/ERP/ACC_NUM

Bank Acct. Status /ERP/ACC_ID_/ERP/AC_STUS

Bank Acct. Type /ERP/ACC_ID_/ERP/ACTYPE

Bank Current Account /ERP/ACC_ID_/ERP/CUR_ACC

Business Area /ERP/BUSAREA

Business Partner /ERP/BP

Cash Pool /ERP/ACC_ID_/ERP/CASHP

Cash Pool(Master) /ERP/ACC_ID_/ERP/CASHP2

Controlling Area /ERP/CO_AREA

Controlling Area /ERP/WBSELMT_/ERP/CO_AREA

Controlling Area /ERP/ACC_ID_/ERP/CO_AREA

Cost Center /ERP/COSTCNTR

Country /ERP/ACC_ID_/ERP/COUNTRY

Country /ERP/COMPCODE_/ERP/COUNTRY

Customer /ERP/CUSTOMER

Supplier /ERP/VENDOR

Direction /ERP/LQITEM_/ERP/DIR

Pro t Center /ERP/PROFTCTR

Pro t Center /ERP/ACC_ID_/ERP/PROFTCTR

Responsible Cost Center /ERP/WBSELMT_/ERP/RESPCCTR

Segment /ERP/SEGMENT

Segment /ERP/PROFTCTR_/ERP/SEGMENT

Segment /ERP/ACC_ID_/ERP/SEGMENT

Trading Partner /ERP/TDP

WBS Element /ERP/WBSELMT

Project De nition /ERP/WBSELMT_/ERP/PROJECT

Variables

Object Type Name Technical Name

Variable Calendar Day 0I_FCLM_AACTUAL_DATE

This is custom documentation. For more information, please visit the SAP Help Portal 54
2/24/2024

Object Type Name Technical Name

Variable Currency 0P_FCLM_TRAN_CURRENCY

Variable Company Code 0P_FCLM_COMPANY_CODE

Variable Virtual Time Hierarchy for Calendar Day 0P_FCLM_VIRTUALHIER_DAY

Variable Liquidity Item Hierarchy 0H_FCLM_LF_LI

Rows

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Company Code /ERP/COMPCODE

Characteristic Currency 0CURRENCY

Characteristic Liquidity Item /ERP/LQITEM__/ERP/LQI_CP

Columns

Object Type Name Technical Name Value Restriction / Calculation

Characteristic Calendar Day 0CALDAY Selected Hierarchy

0P_FCLM_VIRTUALHIER_DAY

Key Figure Cash Net Formula ʻCash In’ + ʻCash out’

Key Figure Cash In /ERP/CI_AMT

Key Figure Cash Out /ERP/CO_AMT

Key Figure Cash Net(converted) Formula ʻCash In (converted)’ + ʻCash Out(converted)’

Key Figure Cash In(converted) /ERP/CI_AMT With conversion type 0FCLM_CFA

Key Figure Cash Out(converted) /ERP/CO_AMT With conversion type 0FCLM_CFA

Cash Flow – Detailed Analysis

FCLM_CFA_VP04_Q0001

Use
This query shows forecast ow details in transaction currencies in a time frame and company codes. Overdue and future amounts are displayed in individual columns respectively.
They are aggregated forecast amounts for the past and the future. This query also provides many free characteristics to drill down.

Structure

Filters

Object Type Name Technical Name Value Restriction / Calculation

Calendar Day 0CALDAY 0I_FCLM_ACTUAL_DATE

Currency 0CURRENCY 0P_FCLM_TRAN_CURRENCY

Client 0MANDT 0SYMANDT

Company Code /ERP/COMPCODE 0P_FCLM_COMPANY_CODE

Free Characteristics

Object Type Name Technical Name

Company Code /ERP/COSTCNTR_/ERP/COMPCODE

Company Code /ERP/WBSELMT_/ERP/COMPCODE

Company Code /ERP/ORG_UNIT_/ERP/COMPCODE

Company Code /ERP/ACC_ID_/ERP/COMPCODE

Assigned Company Code /ERP/PAYCMPCD

Certainty Level /ERP/CERTLVL

Liquidity Item /ERP/LQITEM

Planning Group /ERP/PLGRP

Planning Level /ERP/PLLEV

Planning Unit /ERP/ORG_UNIT

House Bank Account /ERP/HBACC

House Bank /ERP/HBANK

This is custom documentation. For more information, please visit the SAP Help Portal 55
2/24/2024

Object Type Name Technical Name

Bank /ERP/ACC_ID

Bank Acct. Desc /ERP/ACC_ID_/ERP/ACCDES

Bank Acct. Number /ERP/ACC_ID_/ERP/ACC_NUM

Bank Acct. Status /ERP/ACC_ID_/ERP/AC_STUS

Bank Acct. Type /ERP/ACC_ID_/ERP/ACTYPE

Bank Current Account /ERP/ACC_ID_/ERP/CUR_ACC

Business Area /ERP/BUSAREA

Business Partner /ERP/BP

Cash Pool /ERP/ACC_ID_/ERP/CASHP

Cash Pool(Master) /ERP/ACC_ID_/ERP/CASHP2

Controlling Area /ERP/CO_AREA

Controlling Area /ERP/WBSELMT_/ERP/CO_AREA

Controlling Area /ERP/ACC_ID_/ERP/CO_AREA

Cost Center /ERP/COSTCNTR

Country /ERP/ACC_ID_/ERP/COUNTRY

Country /ERP/COMPCODE_/ERP/COUNTRY

Customer /ERP/CUSTOMER

Supplier /ERP/VENDOR

Direction /ERP/LQITEM_/ERP/DIR

Pro t Center /ERP/PROFTCTR

Pro t Center /ERP/ACC_ID_/ERP/PROFTCTR

Responsible Cost center /ERP/WBSELMT_/ERP/RESPCCTR

Segment /ERP/SEGMENT

Segment /ERP/PROFTCTR_/ERP/SEGMENT

Segment /ERP/ACC_ID_/ERP/SEGMENT

Trading partner /ERP/TDP

WBS Element /ERP/WBSELMT

Project De nition /ERP/WBSELMT_/ERP/PROJECT

Rows

Object Type Name Technical Name Value Restriction / Calculation

Company Code /ERP/COMPCODE

Currency 0CURRENCY

Liquidity Item /ERP/LQITEM__/ERP/LQI_CP

Columns

Object Type Name Technical Name Value Restriction / Calculation

Calendar Day 0CALDAY Selected Hierarchy

0P_FCLM_VIRTUALHIER_DAY

Cash Net

Cash In

Cash Out

Cash Net(converted)

Cash In(converted)

Cash Out(converted)

Variables

Liquidity Item Hierarchy

This is custom documentation. For more information, please visit the SAP Help Portal 56
2/24/2024
0H_FCLM_LF_LI

Use
The variable is used for characteristic /ERP/LQITEM__/ERP/LQI_CP. It is an optional and ready for input of hierarchy variable.

WBS Hierarchy
0H_FCLM_LF_WBS

Use
The variable is used for characteristic /ERP/WBSELMT. It is an optional and ready for input of hierarchy variable.

Calendar Day
0I_FCLM_ACTUAL_DATE

Use
The variable is used for characteristic 0CALDAY. It is to be lled with the interval between the current day and one of the following days in a year by default by SAP Exit.

Calendar Month Range

0I_FCLM_CALMONTH

Use
The variable is used in characteristic Calendar Year/Month (0CALMONTH). It is required that users enter a value range for this variable.

Calendar Month
0I_FCLM_CAL_MONTH

Use
The variable is used for characteristic 0CALMONTH. It’s mandatory, and can be input as interval. It is to be lled with the interval between the current month and one of the following
months in a year by default by SAP Exit.

Calendar Day
0I_FCLM_CALDAY

Use
The variable is used for characteristic 0CALDAY. It’s input as interval. It is to be lled with the interval between the current day and one of the following days in a year by default by
SAP Exit.

All Liquidity Items in the Hierarchy

0N_FCLM_LQH_ITEMS

Use
This mandatory variable is used in characteristic Liquidity Item (/ERP/LQITEM). Users must enter multiple values for this variable.

Leaf Liquidity Items in the Hier. w/o Balance Liquidity Item

0N_FCLM_LQH_NO_BAL

Use
This optional variable is used in characteristic Liquidity Item (/ERP/LQITEM). It is an SAP exit.

This is custom documentation. For more information, please visit the SAP Help Portal 57
2/24/2024

Multiple Liquidity Item Nodes

0N_FCLM_SEVERAL_LQITEM

Use
This mandatory variable is used in the characteristic Liquidity Item (/ERP/LQITEM). Users must specify multiple values for this variable.

Currency Conversion
0P_CONVERSION_TARGETCURRENCY

Use
This mandatory variable is used in the characteristic Conversion Currency (/ERP/TCUR). Users must specify a single value for this variable.

Calendar Month
0P_FCLM_CALMONTH

Use
This mandatory variable is used in characteristic Calendar Year/Month (0CALMONTH). Users must specify a single value for this variable.

Currency
0P_FCLM_CURRENCY_CC

Use
This optional variable is used in the characteristic Currency Key (0CURRENCY). Users can specify a single value for this variable.

Liquidity Item
0P_FCLM_EMPTYNODE_LQ

Use
The variable is used for characteristic /ERP/LQITEM__/ERP/LQI_CP. It is to be lled with all the nodes from the selected liquidity item hierarchy by SAP Exit.

First Date for Selected Time Range

0P_FCLM_FIRST_DAY

Use
The variable is used for characteristic 0CALDAY. It is optional, and is not ready for input.

First Day of Version Month

0P_FCLM_FIRST_DAY_OF_VERSION

Use
This optional variable is used in the characteristic 0DATE. The variable is a replacement variable.

First Date for Selected Days

0P_FCLM_FIRSTD_DAYS

Use
The variable is used for characteristic 0CALDAY. It is a date variable for the selected liquidity item hierarchy.

This is custom documentation. For more information, please visit the SAP Help Portal 58
2/24/2024

Liquidity Item Hierarchy Key Date

0P_FCLM_KEY_DATE

Use
The variable is used in characteristic Date (0DATE). It derives the date from the rst day of the selected planning cycle. For example, if the selected planning cycle is 201403, the
value of the exit variable is 20140301. The exit supports only deriving a date from one planning cycle variable with a single value. The variable is an SAP Exit that refers to the function
module RSVAREXIT_0P_FCLM_KEY_DATE. The variable is optional.

Last Date for Selected Time Range

0P_FCLM_LAST_DAY

Use
The variable is used for characteristic 0CALDAY. It is optional, and is not ready for input.

Last Date for Selected Days

0P_FCLM_LASTD_DAYS

Use
The variable is used for characteristic 0CALDAY. It is optional, and is not ready for input.

Day for Current Member

0P_FCLM_LF_CM_DAY

Use
The variable is used for characteristic 0CALDAY. It is optional, and is not ready for input.

First Date for Selected Months

0P_FCLM_LF_FIRSTDAY

Use
The variable is used for characteristic 0CALDAY. It is optional, and is not ready for input.

First Month for Selected Months

0P_FCLM_LF_FIRSTMON

Use
The variable is used for characteristic 0CALMONTH. It is optional, and is not ready for input.

First Month for Future Period

0P_FCLM_LF_FURS_MON

Use
The variable is used for characteristic 0CALMONTH. It is optional, and is not ready for input.

Last Day for Selected Months

0P_FCLM_LF_LASTDAY

Use
The variable is used for characteristic 0CALDAY. It is optional, and is not ready for input.

This is custom documentation. For more information, please visit the SAP Help Portal 59
2/24/2024

Last Date for Overdue Period

0P_FCLM_LF_PASTE_DAY

Use
The variable is used for characteristic 0CALDAY. It is optional, and is not ready for input.

First Date for Overdue Period

0P_FCLM_LF_PASTS_DAY

Use
The variable is used for characteristic 0CALDAY. It is optional, and is not ready for input.

Last Month for Overdue Period

0P_FCLM_LF_PASTS_MON

Use
The variable is used for characteristic 0CALMONTH. It is optional, and is not ready for input.

Planning Month
0P_FCLM_LP_PLAN_MONTH

Use
This optional variable is used in characteristic Calendar Year/Month (0CALMONTH). It derives a value for a single month from the key value of the selected planning cycle variable
0P_FCLM_LP_PLAN_VERSION.

Planning Cycle
0P_FCLM_LP_PLAN_VERSION

Use
The variable is used in characteristic Version (/ERP/VMONTH). It is required that users specify a single value for this variable.

Liquidity Item
0P_FCLM_LQITEM_EXIT

Use
The variable is used in characteristic Liquidity Item (/ERP/LQITEM). The variable is mandatory, and it is an SAP exit variable.

Planning Unit
0P_FCLM_ORG_UNIT

Use
This mandatory variable is used in the characteristic Planning Unit (/ERP/ORG_UNIT). Users must specify a single value for this variable.

Previous Version
0P_FCLM_PRE_VERSION

Use
This mandatory variable is used in the characteristic Version (/ERP/VMONTH). Users must specify a single value for this variable.

This is custom documentation. For more information, please visit the SAP Help Portal 60
2/24/2024

Virtual Time Hierarchy for Calendar Day

0P_FCLM_VIRTUALHIER_DAY

Use
The variable is used for characteristic 0CALDAY. It is optional, and can be input as single value.

Liquidity Item Hierarchy

0P_LQI_HIER

Use
This mandatory variable is used in the characteristic Liquidity Item (/ERP/LQITEM). It is a hierarchy variable.

Hierarchy for Org

OH_FCLM_ORG_UNIT

Use
This mandatory variable is used in the characteristic Planning Unit (/ERP/ORG_UNIT). It is a hierarchy variable.

Company Code
0S_FCLM_COMPANYCODE

Use
This variable is used for company code. It is mandatory and ready for input.

MultiProviders

Liquidity Forecast
/ERP/LF_MP01

Use
This MultiProvider contains 3 VirtualProviders: forecast ows from One Exposure, forecast ows from Memo Records and cash position opening balance. Liquidity forecast analysis
can be performed by BW queries built on this MultiProvider.

Liquidity Planning
/ERP/LP_MP01

Use
This Multiprovider combines planned data and forecast data for liquidity planning, so that you can de ne queries for all the relevant data as you need.

Key Figures

Cash In
/ERP/CI_AMT

Use
This key gure is used for in ow of actual.

Technical Data

This is custom documentation. For more information, please visit the SAP Help Portal 61
2/24/2024
Exchange Available as of Release

Aggregation Summation

Exception Aggregation Summation

Planning
/ERP/PL_AMT

Use
This key gure contains the plan amounts entered by users in liquidity plans. The values can either be positive (with a + sign) or negative (with a - sign).

Technical Data

Exchange Available as of Release

Aggregation Summation

Exception Aggregation Summation

Calculation No

Value Restriction / Calculation No

This is custom documentation. For more information, please visit the SAP Help Portal 63
2/24/2024

Reference Data
/ERP/SUG_AMT

Use
This key gure contains the reference data suggested by the system for plan amounts. The values can either be positive (with a + sign) or negative (with a - sign).

Technical Data

Exchange Available as of Release

Aggregation Summation

Exception Aggregation Summation

Calculation No

Value Restriction / Calculation No

InfoCubes

BPC Work Status

/ERP/LP_VPWS

Use
This InfoCube retrieves work status information from SAP Business Planning and Consolidation.

Liquidity Plans
/ERP/LP_IC01

Use
This real-time InfoCube retrieves the planning data and enables you to keep and read the data.

Planning Cube (Exchange Rate for Currency Conversion)

/ERP/LP_IC02

Use
This real-time InfoCube retrieves the planning amount and enables you to keep and read the planning amount for currency conversion.

Bank Balance
/ERP/LP_VP01

Use
This InfoCube is used to analyze the opening balance for company codes.

Actual Cash Flow

/ERP/CFA_VP01

Use
This virtual provider retrieves the actual cash in ow, cash out ow and net cash ow data from One Exposure from Operations.

Liquidity Forecast
/ERP/LF_VP06

This is custom documentation. For more information, please visit the SAP Help Portal 64
2/24/2024
Use
This virtual provider retrieves liquidity forecast data from One Exposure from Operations.

Deposit Balance
/ERP/LP_VP05

Use
This virtual provider retrieves the deposit balance data.

Characteristics

Certainty Level
/ERP/CERTLVL

Use
This characteristic is used to indicate the reliability and therefore the likelihood of a ow in One Exposure from Operations.

Technical Data

Exchange Available as of Release

External Hierarchy

Liquidity Item
/ERP/LQITEM

Use
This characteristic is used as a key to identify a Liquidity Item.

Technical Data

Exchange Available as of Release

External Hierarchy

Aggregation Currency
/ERP/AGG_CUR

Use
This characteristic is used to indicate the aggregation currency con gured for each organizational unit. It is modeled as an attribute of characteristic Organizational Unit
(/ERP/ORG_UNIT).

Technical Data

Exchange Available as of Release

External Hierarchy

External Hierarchy

External Hierarchy

Planning Functions

Balance Calculation
Technical name: /ERP/LP_AL01_PS10

The planning sequence is used to calculate closing balance and opening balance for the whole planning cycle, except the opening balance of the rst month.

Technical Data

Planning Function Name Planning Function (Description)

/ERP/LP_AL01_PF30 Get the actual cash ow data

Filling in Cash Flow Data with Liquidity Forecast

Technical name: /ERP/LP_AL01_PS26

The planning sequence is used to copy data from forecast to planning under required lter condition.

Technical Data

Planning Function Name Planning Function (Description)

/ERP/LP_AL01_PF17 Fill planning amount with liquidity forecast data

/ERP/LP_AL01_PF02 Revaluate planning amount with multiplier

/ERP/LP_AL01_PF21 Fill planning amount with opening balance data

Loading Cash Flow Data from Liquidity Forecast

Technical Name: /ERP/LP_AL01_PS27

The planning sequence is used to get the forecast data under required lter condition.

This is custom documentation. For more information, please visit the SAP Help Portal 68
2/24/2024
Technical Data

Planning Function Name Planning Function (Description)

/ERP/LP_AL01_PF14 Get cash ow data from liquidity forecast

/ERP/LP_AL01_PF22 Get opening balance data for the rst month

Loading Planning Amount from Previous Planning Cycle

Technical name: /ERP/LP_AL01_PS28

The planning sequence is used to get the planned data from previous cycle under required lter condition.

Technical Data

Planning Function Name Planning Function (Description)

/ERP/LP_AL01_PF15 Load planning amount from previous planning cycle

Loading Cash Flow Data from Actual Cash Flow

1. Create planning units

In Customizing activity Maintain Planning Unit Settings, do the following:

Create planning units to be used in liquidity planning. Planning units are organizational units that need to enter liquidity plan data. Each planning unit corresponds to
one company code.

This is custom documentation. For more information, please visit the SAP Help Portal 69
2/24/2024
De ne planning currencies for planning units

You can de ne one or more planning currencies for each planning unit.

2. Maintain the planning unit hierarchy

a. Start BW modeling using transaction code RSA1.

b. Locate the info object /ERP/ORG_UNIT under Modeling InfoObjects Financial Management & Controlling Cash & Liquidity Management Characteristics ,
and then double click it.

c. On the Hierarchy tab, choose the Maintain Hierarchy button.

d. Create a new hierarchy by specifying the name and description.

e. Add nodes to the hierarchy by using the Planning Unit button.

f. De ne a leaf planning unit named as Headquarter with key 1.

It will be used for currency conversion. Please note that all the subsidiary planning units can only do currency exchange with the headquarter.

g. Choose the Hierarchy Attributes button and then select the Do Not Display Leaves for Inner-Nodes in the Query and Suppress ʻUnassigned’ Node checkbox.

h. Check planners and reviewers of planning units

In Customizing activity Maintain Planning Unit Settings, do the following:

After the Planning Unit Hierarchy has been de ned in previous step, the Planner and Reviewer of Planning Unit need to be checked to make sure that the Reviewer of
the subsidiary Planning Unit is consistent with the Planner of the parent Planning Unit. Otherwise, the status of BPC cannot be modi ed as expected.

i. Activate planning unit hierarchy

In Customizing activity Activate Planning Unit Hierarchy, do the following:

Activate a planning unit hierarchy to be used for all liquidity planning activities.

Reference Data Sources

To de ne reference data sources that can be used to classify the source of suggested values, use the Customizing activity De ne Reference Data Sources, under Financial Supply
Chain Management Cash and Liquidity Management Cash Management Liquidity Planning .

Key 001 to 004 are from SAP standard delivery. You can de ne your own reference data sources if extension is needed.

Liquidity Planning Types

Planning type is used to classify the diﬀerent kind of planning data. SAP provides two prede ned planning type, monthly rolling plan and non-rolling plan. You can de ne your own
planning types if necessary, using the Customizing activity De ne Liquidity Planning Types, under Financial Supply Chain Management Cash and Liquidity Management
Liquidity Planning .

With SAP standard solution, users can only develop monthly rolling plans. For non-rolling plans or other kinds of plans, users can develop extensions as needed.

Liquidity Items and Liquidity Item Hierarchies

Liquidity Items
When creating liquidity items using the activity Edit Liquidity Items, under Financial Supply Chain Management Cash and Liquidity Management Cash Management
Liquidity Items , note the following:

If you want to integrate with cash position to get bank balance data, de ne a liquidity item with the key as LP_CASHOP.

If you want to integrate with Treasury and Risk Management (TRM) to identify the opening balance for deposits, such as xed-term deposits, deposits at notice, de ne a
liquidity item with the key as LP_DPOP.

If you want to use the currency exchange function, de ne the following two liquidity items:

LP_EXF: Cash planned to be converted from another currency

LP_EXI: Cash planned to be converted to another currency

Liquidity items can be de ned to represent cash ows or balance values. In liquidity planning, only the liquidity items representing cash ows are taken into calculation.
To exclude liquidity items that represent balance values from liquidity planning calculation, you must diﬀerentiate balance-related liquidity items from other ow-
related liquidity items. To do so, use the Customizing activity Exclude Liquidity Items Representing Balance Values, under Financial Supply Chain Management Cash
and Liquidity Management Liquidity Planning , to register all the liquidity items de ned in the system that representing balance values. Otherwise, the plan data
may be miscalculated.

Closing Balance Calculation

The closing balance is calculated using the logic below:

LP_AROPEN + LP_ARFA = LP_ARCL

LP_LBOPEN - LP_LBFA = LP_LBCL

This is custom documentation. For more information, please visit the SAP Help Portal 70
2/24/2024
LP_ARCPOP + LP_ARCPFA = LP_ARCPCL

LP_LBCPOP - LP_LBCPFA = LP_LBCPCL

LP_DPOP + LP_DEPOSITFA = LP_DPCL

LP_LOOP - LP_LOANODFA = LP_LOCL

LP_CASHOP + LP_CASHFA = LP_CASHCL

LP_AR3RDDOP + LP_AR3RDFA = LP_AR3RDCL

LP_LB3RDOP - LP_LB3RDFA = LP_LB3RDCL

Liquidity Item Hierarchy

With the Customizing activity De ne Liquidity Item Hierarchies, under Financial Supply Chain Management Cash and Liquidity Management Cash Management Liquidity
Items , you can maintain the liquidity item hierarchies to be used in liquidity planning.

The current closing balance calculation logic is based on the sample liquidity item hierarchy, therefore if you would like to customize the liquidity item and liquidity item hierarchy, you
need to customize the closing balance calculation backend logic as well. The way to do the backend calculation customizing follows the standard BW logic.

Derivation Rules for Liquidity Items

To de ne how liquidity items can be derived for forecasted cash ows and actual cash ows, con gure the rules for liquidity derivation using the following Customizing activities under
Financial Supply Chain Management Cash and Liquidity Management Cash Management Liquidity Items Derivation Rules for Liquidity Items :

Create a query sequence for the new origin (transaction code FLQC15)

Create queries to be linked to the query sequence (transaction code FLQQA1)

Assign the queries to the query sequence (transaction code FLQQA5)

De ne default liquidity item derivation for Company Code (transaction code FLQC0)

De ne default liquidity items for G/L accounts (transaction code FLQINFACC)

 Note
If you set the indicator Further to one G/L account, you get the account assignment information from the account line item information of the assigned G/L account. If this
indicator is not set in the assigned G/L accounts, the account assignment information is inherited from the oﬀsetting items in the source (original document).

ICF Services
Activate the ICF services listed in the table below as follows:

1. In transaction SICG, enter a service path and then choose Execute.

2. Right click on the service and choose Activate Service.

ICF Service Description Service Path

BPC Universal Web Client /sap/bc/ui5_ui5/sap/bpcwebclient

Client Service (Persistence, User Preference, etc.) /sap/bw/cs

BW: Get Response /sap/bw/ina/GetResponse

Before you use the Web Dynpro applications for Liquidity Management, you need to activate the following services using transaction SICF:

App Name Technical Name

Cash Flow-Detail Analysis WD_FCLM_FPM_OVP_CFA

Liquidity Forecast Detail

WD_FCLM_FPM_OVP_FD

WD_FCLM_FPM_OVP_FO

Business Planning and Consolidation

Prerequisites
Before you activate the BPC-related objects below, make sure you have installed SAP Business Planning and Consolidation, version for SAP NetWeaver (BPC).

For more information about installation and upgrade, see the guides that are listed under Installation and Upgrade at
https://help.sap.com/viewer/p/SAP_BUSINESS_PLANNING_AND_CONSOLIDATION,_VERSION_FOR_SAP_NETWEAVER.

For more information about authorization, see the Security Guide under Security at
https://help.sap.com/viewer/p/SAP_BUSINESS_PLANNING_AND_CONSOLIDATION,_VERSION_FOR_SAP_NETWEAVER.

This is custom documentation. For more information, please visit the SAP Help Portal 71
2/24/2024
In the BPC, you can use SAP BusinessObjects Analysis for Microsoft Office (Analysis for Office) as the interface. Analysis for Office makes activity list directly available in Excel
interface, which reduces the need to login or switch between web and Excel interface.

Make sure you have set up and made con guration settings for Analysis for Oﬃce.

For more information on how to install, con gure, manage, maintain, and optimize Analysis for Oﬃce, see Administrator Guide at
https://help.sap.com/viewer/p/SAP_BUSINESSOBJECTS_ANALYSIS_OFFICE.

For more information on how to use SAP BusinessObjects Analysis plug-ins to accomplish your business tasks, see Analysis Plug-in User Guide under Application Help
at https://help.sap.com/viewer/p/SAP_BUSINESSOBJECTS_ANALYSIS_OFFICE.

Procedure
Enable BPC Embedded Model and Deep HANA Integration

Proceed as follows:

1. Run transaction SM30.

2. Specify the RSPLS_HDB_ACT table view.

3. Add and activate the parameter BPC Embedded Model (BPC_ACT) and Deep HANA Integration (HANA_ACT) .

Customize BPC Templates

If you want to enhance or modify the prede ned BPF templates, proceed as follows:

1. Start BPC Workcenter with the following URL pattern by replacing the parameters between the braces: https://[host]:
[port]/sap/bc/ui5_ui5/sap/bpcwebclient/index.html?sap-language=[language]&sap-client=[client]#cm=0FCLM_LP_ENV;connType=pak.

2. On the ADMINISTRATION tab, choose Process Templates.

3. Select the prede ned BPF template FCLM_LP_PROCESS_AO, and then choose the New Version button.

4. Specify at least a valid user for Process Monitors.

5. On the Activities tab, under the section Driving Dimension, select All Members for the Selected Hierarchy for the Members eld.

6. Select the planning unit hierarchy that you want to use, and then choose the Save and then the Back button.

The hierarchy must be an active one. For more information on how to activate a planning unit hierarchy, see Planning Units and Planning Unit Hierarchy.

7. To activate the modi ed template, choose the Deploy button to activate the modi ed template.

Con gure the Default Liquidity Item Hierarchy in Template

2. On the ADMINISTRATION tab, choose Process Templates. Select the BPF template FCLM_LP_PROCESS_AO, and then choose the New Version button.

3. Select the model FCLM_LP_MODEL.

4. On the Activities panel, under the Activity Performer and Activity Reviewer section, choose the Edit for the Workspace eld.

5. For liquidity item hierarchy parameter, select the member maintained in Customizing activity De ne Liquidity Item Hierarchies which refers to the template liquidity item
hierarchy. For more information about liquidity item hierarchy template, see SAP Note2145500 . For Planning Cycle and Planning Unit parameter, select Use Workspace
Context.

Customize the BPC Work Status

2. On the ADMINISTRATION tab, choose Work Status Con guration.

3. Select the model FCLM_LP_MODEL.

4. In the Locking Dimensions, specify the planning unit hierarchy you have activated in the Customizing activity Activate Planning Unit Hierarchy.

5. Select the Enable Work Status checkbox and save the settings.

Specify the BPC Con guration Set

To activate a BPC con guration set, you can do so in Customizing activity Specify a BPC Con guration Set, under Financial Supply Chain Management Cash and Liquidity
Management Liquidity Planning .

By default, the standard BPC con guration set provided by SAP is activated for Liquidity Planning. If you want to use your own con guration set, add the con guration set and make
sure only one con guration set is activated for Liquidity Planning.

Settings in the Front-End Server

Launchpad Access Con guration

This is custom documentation. For more information, please visit the SAP Help Portal 72
2/24/2024
Use
In order to use the liquidity planning function, you need to make additional con guration steps to enable the navigation from the ori launchpad to BPC:

Create Launchpad

Create Catalog

Create Tile

Create Target Mapping

Assign Role to Catalog

Depending on your needs, you can create one or more launchpad and tile according to the details in the following tables.

When you create two tiles, you can take the following tile names as a reference:

Start New Planning Cycle (binding target mapping BankAccount-createCycle)

Enter and Review Liquidity Plans (binding target mapping BankAccount-inbox)

In the case where you only create one tile, you can also start a new planning cycle in the Process Instances under the Administration tab, or enter and review liquidity plans
under the My Activities tab

For more technical details, see the parameters in the following table:

Con guration of Launchpads

Role Instance Application Application URL

Alias Type

FCLM_BPC FCLM_BPC_CI BPC_CI URL https://[host]:[port]/sap/bc/ui5_ui5/sap/bpcwebclient/index.html?sap-language=[language]&sap-

client=[client]#cm=0FCLM_LP_ENV;connType=pak; VIEW_ID=admin-composite-container/admin-bpf-
process_instances

 Note
Replace the [host], [port], [client] and [language] with your own system parameters.

FCLM_BPC FCLM_BPC_INBOX BPC_INBOX URL https://[host]:[port]/sap/bc/ui5_ui5/sap/bpcwebclient/index.html?sap-language=[language]&sap-

client=[client]#cm=0FCLM_LP_ENV;connType=pak

Con guration of Tiles

Title Subtitle Semantic Object Action

BPC BPC WorkCenter BankAccount OpenBPC

Con guration of Target Mappings

Semantic Object Action Navigation Type Launchpad Role Launchpad Instance Application Alias Desktop

BankAccount createCycle SAP Fiori App using FCLM_BPC FCLM_BPC_CI BPC_CI Yes
LPD_CUST

BankAccount inbox SAP Fiori App using FCLM_BPC FCLM_BPC_INBOX BPC_INBOX Yes
LPD_CUST

Activities
You can follow the con guration steps below to set up the ori launchpad and enable access in the front end.

Con guration Steps

1. Create Launchpad

a. Go to transaction LPD_CUST.

b. Choose the New Launchpad button and specify the Role and Instance in the dialog box as listed in the table of Con guration of Launchpad. These two elds will be used
when you create the target mapping. The description can be maintained up to customers.

c. Click the New Application.

d. Fill the following content according to the table of Con guration of Launchpads:

Link Text (You can de ne the text by yourself)

Application Type

URL

Application Alias

e. Save the settings.

2. Create Catalog

This is custom documentation. For more information, please visit the SAP Help Portal 73
2/24/2024
a. Open the Fiori Launchpad Designer

b. Create a standard customizing catalog and ll the Title and the ID. The customizing catalog is to contain the customizing target mappings.

c. Save the settings.

3. Create Tile

a. Choose the customizing catalog that you create.

b. Click the Add tile tile and enter the details of the tile, such as Title, Semantic Object, Action, and so on.

c. Save the settings.

4. Create Target Mapping

a. In the customizing catalog, go to the Target Mapping panel and choose Create Target Mapping.

b. Con gure the target mapping as listed in table of Con guration of Target Mappings. Launchpad Role, Launchpad Instance and Application Alias are bound to the target
mapping. When you open the tile, BPC will be launched.

 Note
The Semantic Object and Action must be the same as those in the tile.

c. Save the settings.

5. Assign Role to Catalog

a. Create a customizing role or opening an existing role via transaction PFCG.

b. Add Transaction SAP Fiori Tile Catalog.

c. Bind the customizing Catalog to the role. Catalog Provider should be X-SAP-UI2-CATALOGPAGE.

d. Assign the customizing role to users.

Con guration Tips for SAP Liquidity Planner Customers

The following should be considered if you migrate from the classic SAP Liquidity Planner to the new SAP S/4HANA Finance for cash management:

From actual/info accounts to ow types

The classic SAP Liquidity Planner distinguishes actual accounts from info accounts. Actual accounts are G/L accounts that re ect actual incoming or outgoing payments.

In the new SAP S/4HANA Finance for cash management, the concept of ow types was introduced. The ow types classify the lifecycle of cash ows and only data assigned
with ow type information can be consumed and used in Cash Management applications. To use the new SAP S/4HANA Finance for cash management, it is important to
understand the new ow type concept and available con guration options before you adapt your original account settings to ow type assignment. For more information, see
Flow Types.

Liquidity items and Liquidity Item Hierarchies

In the new SAP S/4HANA Finance for cash management, the Customizing activity Edit Liquidity Items has been enhanced with a new attribute Cash Flow Direction.
After the migration, you must specify a cash ow direction for each of the liquidity items.

For more information, see Liquidity Items and Liquidity Item Hierarchies.

Liquidity Item Hierarchy

The Customizing activity Liquidity Item Hierarchies is a mandatory customizing activity in the new SAP S/4HANA Finance for cash management. It allows you to group
liquidity items into diﬀerent hierarchical structures for various business uses.

You must set up this Customizing activity if you haven’t done so in classic SAP Liquidity Planner.

Liquidity item de nition for Liquidity Management

If you want use the Liquidity Management functions in the new SAP S/4HANA Finance for cash management, note that SAP has provided prede ned liquidity items and
sample liquidity item hierarchy. For more information about the required con guration, see Liquidity Items and Liquidity Item Hierarchies.

Liquidity item derivation

In the classic SAP Liquidity Planner, the transaction FLQINFACC is used to de ne liquidity items for info accounts. In the new SAP S/4HANA Finance for cash
management, the transaction can still be used to de ne default liquidity items for G/L accounts. It can also be accessed via the Customizing activity De ne Default
Liquidity Items for G/L Accounts. Liquidity items are rst derived according to the customer-con gured query sequences. If the query sequence fails to determine a
liquidity item, default liquidity item de ned here is used and recorded in accounting document line items table.

 Note
The Customizing activity De ne Default Liquidity Items for G/L Accounts is not cross-client.

Queries and query sequences

Queries and query sequences are still used to derive liquidity items. To reuse your con guration settings, note the following:

Query origins except C (other types of accounting documents) and D (invoices) are no longer supported.

Queries that are de ned with origin C or D are supported with the new SAP S/4HANA Finance for cash management.

This is custom documentation. For more information, please visit the SAP Help Portal 74
2/24/2024
You are recommended to evaluate and test the queries before you go live with SAP S/4HANA Finance for cash management, just to ensure that they work as
expected with the new SAP S/4HANA Finance for cash management.

For more information, see Derive Liquidity Items for Accounting Documents in Liquidity Items and Liquidity Item Hierarchies.

In the new SAP S/4HANA Finance for cash management, the concept One Exposure from Operations was introduced. The One Exposure from Operations hub
works as a central storage location of operation data that is relevant for cash management. Source applications, for example bank statements (origin B in the
classic SAP Liquidity Planner), can be set up for the One Exposure from Operations hub. You can use query origins C and D to derive liquidity item for Financial
Operations, and query origin X to derive liquidity items for all other source applications integrated into the One Exposure from Operations hub.

For more information, see Con guration for One Exposure from Operations.

Exit function and other extensions

If you have used exit functions in the classic SAP Liquidity Planner, you need to review the logic and adapt the code to the new exit function template
FCLM_LQF_DERIVE_LQITEM_SAMPL.

If you have implemented other extensions, they may not be supported any more. For example, you have added custom elds to the liquidity planner tables (FLQ*
tables) in the classic SAP Liquidity Planner. However, the elds are no longer supported as the new SAP S/4HANA Finance for cash management consumes data only
from the BSEG table and the FQM_FLOW table.

You are recommended to evaluate if the extensions are still needed with the new SAP S/4HANA Finance for cash management, as with the new document chain
derivation mechanism, most of the important analysis dimensions are available for analyzing the source and use of cash, for example, liquidity item, house bank
account, WBS element, pro t center, and so on.

Data Setup Guide for SAP S/4HANA Finance for Cash Management

Use
The classic SAP Cash and Liquidity Management (FIN-FSCM-CM and FIN-FSCM-LP) is not available in SAP S/4HANA. Instead, you can use the new SAP S/4HANA Finance for cash
management (FIN-FSCM-CLM) with SAP S/4HANA. If you currently use the classic SAP Cash and Liquidity Management, you can migrate relevant master data and transactional
data to the new SAP S/4HANA Finance for cash management.

 Note
SAP S/4HANA Finance for cash management requires a separate license. Please contact your SAP Account Executive about the license for SAP S/4HANA Finance for cash
management before you perform the migration.

This chapter introduces the activities that you need to perform to migrate and set up data before you go live with SAP S/4HANA Finance for cash management.

This chapter 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
S/4HANA Finance for cash management.

Customers who want to transfer information relevant to cash management that is stored in remote systems (either SAP systems or third-party systems) to the SAP
S/4HANA Finance for cash management system.

Prerequisites
You need to have ful lled the following prerequisites before you can continue with the migration activities:

You have installed SAP S/4HANA 1709

For more information, see the Installation Guide of SAP S/4HANA 1709 at http://help.sap.com/s4hana_op1709.

You have nished the migration for Accounting.

For more information, see the Conversion Guide and the Simpli cation List of SAP S/4HANA 1709 at http://help.sap.com/s4hana_op1709.

You have assigned roles to users.

For more information about security-relevant authorization objects, see the Security Guide of SAP S/4HANA 1709 at http://help.sap.com/s4hana_op1709.

You have switched on the business function FIN_FSCM_CLM and selected Full Scope for Cash Management Scope in the Customizing activity De ne Basic Settings under
Financial Supply Chain Management Cash and Liquidity Management General Settings .

Make sure that you have applied all the notes listed in SAP Note 2493348 (SAP S/4HANA 1709: Release Information Note for Finance) appropriate to your product version.

Your user is con gured with the required back-end authorization and front-end authorization.

Create Bank Account Master Data

Before you start to use SAP S/4HANA Finance for cash management, 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.

This is custom documentation. For more information, please visit the SAP Help Portal 75
2/24/2024
Below are the two migration tools available for migrating bank account master data.

Migrate House Bank Accounts (mandatory)

Import and Export Bank Accounts (optional)

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.

Prerequisites
Before you work with bank account master data, make sure you have properly con gured the following settings:

Number ranges for bank account technical IDs

Banks and house banks

Business partners for banks

Business partners for external contacts (optional)

Number Ranges for Bank Account Technical IDs

In bank account master data, each bank account is assigned with a technical ID when created. To de ne the technical ID assignment rules, con gure the following Customizing
activities under Financial Supply Chain Management Cash and Liquidity Management Bank Account Management Basic Settings :

1. In the Customizing activity De ne Number Ranges for Bank Account Technical IDs, de ne number ranges for bank account technical IDs.

2. In the Customizing activity De ne Settings for Bank Account Master Data, on the Bank Account Master Data Setting tab, specify a number range for the Tech. ID No. Rang
eld.

Banks and House Banks

Before you migrate bank account master data, you need to maintain banks in your cash management system.

You can create banks manually using the Manage Banks app or the transaction FI01. To upload bank accounts en masse, you can use an upload tool, which can be found under
SAP Customizing Implementation Guide Cross-Application Components Bank Directory Bank Directory Data Transfer .

For bank accounts used by payments, bank statements, or bank transfers in your central cash management system, their corresponding house bank and house bank accounts
must be con gured.

You can use the Manage Banks app or the transaction FI12_HBANK to maintain the house banks.

Business Partners for Banks

Context
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 de ne the business partners for banks, we recommend that you de ne the bank hierarchy rst. After you de ne the position of a bank in the bank
hierarchy, the system automatically assigns or creates a business partner, and establish the linkage between the business partner and the bank.

1. Open the Manage Bank Account app. In the bank hierarchy view, choose the Edit button.

2. In the bank hierarchy view, choose the Edit button.

3. From the list, select a node under which you want to add the bank.

4. Choose the Add Existing Bank button and specify the Bank Country and Bank Key of the bank to be added.

5. After the bank is added to the hierarchy, the system checks whether the bank has a corresponding business partner instance with role TR0703:

If yes, the system assigns the business partner instance to the bank.

If the bank has a corresponding business partner without role TR0703, the system adds the role TR0703 to the existing business partner

If the bank does not have any corresponding business partners, the system creates a business partner instance for the bank, with role TR0703 assigned.

6. To check the created business partners and the established linkages, check the entries in transaction FCLM_BAM_BNKA_BP .

This is custom documentation. For more information, please visit the SAP Help Portal 76
2/24/2024

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 le, you may maintain the Contact at Bank and Bank Relationship Manager elds. After the le is imported, the speci ed 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 elds for external contacts, you must create business partner for external contacts and con gure the relationship between contact business partners and bank
business partners. To do so, choose either of the following two methods:

 Note
Note down the IDs of business partners for external contacts. Later when you specify the Contact at Bank and the Bank Relationship Manager eld in the Excel, make sure you
use the ID of business partners.

Import business partners and con gure business partner relationship using a Microsoft Excel le.

For more information on how to use the tool, see SAP Library at http://help.sap.com , under Financial Management SAP Strategic Enterprise Management SAP SEM
6.0 SEM - 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, nd 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.

Import and Export Bank Accounts

Use
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 S/4HANA Finance for cash management is installed.

With this tool, you can download a template XML le in spreadsheet format, with which you may prepare the bank account master data and attributes from your remote systems.
Once you have nished preparing the le, you may import it to SAP S/4HANA Finance for cash management.

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 SAP S/4HANA Finance for cash management system
or other remote systems.

Additional data

Prerequisites
You use Microsoft Oﬃce 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.

Procedure
For information on how to use this tool, see the application help for SAP S/4HANA Finance for cash management.

1. In the Manage Bank Accounts app, switch to the Account List view.

2. Choose Import and Export Bank Accounts.

3. To prepare bank account data to be migrated, download the template by choosing Download XML Spreadsheet Template.

4. Save and open the le 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 elds, enter the corresponding business partner IDs.

This is custom documentation. For more information, please visit the SAP Help Portal 77
2/24/2024
Contact at Bank

Bank Relationship Manager

Payment Signatories

Overdraft Limits

Additional Data

Connectivity Path

6. On the Developer tab, choose Export to export the data as an XML le.

7. To import the bank accounts, specify the import path of the XML source data le generated in the previous step and then choose Import to upload the le.

You can choose either of the following two modes for the import:

Overwrite mode: By selecting the Overwrite option, if you leave a eld blank in the source le, the respective eld in the bank account master data will be erased after
the import.

Update mode: By deselecting the Overwrite option, empty elds in the source le will be ignored during the import. Only elds with values will be updated after the
import.

 Note

Before you export data Microsoft Excel, check the data and make sure the following:

All the bank account entries you want to import are inside the blue frame.

The application does not import data outside of the frame.

There are no empty rows between bank account entries.

The application treats empty rows as incorrect entries.

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

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

Replicate House Banks, House Bank Accounts, and Bank Accounts

To replicate house banks, house bank accounts, and bank accounts from a sender system to one or more receiver systems, you can use the Execute Data Replication program
(transaction DRFOUT). With this program, you can carry out the following tasks:

Replicate existing house banks, house bank accounts, and bank accounts to receiver systems en masse

Replicate changes that occurred in the sender system during a speci ed time interval to receiver systems

Manually select and transfer data to receiver systems

For more information on the con guration settings for using this program, see Data Replication.

Set Up Cash Management Data

This activity is to set up transactional data that will be used by Cash Management applications.

SAP S/4HANA Finance for cash management consumes data from the following applications:

Memo records (database table FDES)

One Exposure from Operations (database table FQM_FLOW) for data from other components like accounting, end-of-day bank statements, TRM, CML, FI-CA, and integrated
data from remote systems.

To use SAP S/4HANA Finance for cash management, perform the following data setup activities:

Build Key Information in Accounting Documents (database table BSEG)

Load Data into One Exposure from Operations Hub

Load data from Treasury and Risk Management (TRM), Loans Management (FS-CML), Contract Accounts Receivable and Payable (FI-CA), and integrated remote systems,
into the One Exposure from Operations hub.

Prerequisites
You have con gured the following:

Memo records

One Exposure from Operations

Flow types

This is custom documentation. For more information, please visit the SAP Help Portal 78
2/24/2024
Liquidity items and liquidity item hierarchies

Planning levels and planning groups

Field status

For more information, see Con guration Guide for SAP S/4HANA Finance for Cash Management

Build Key Information in Accounting Documents

Context
Data such as liquidity items, ow types, house banks, and house bank accounts are key to the calculation of Cash Management. To build key information in accounting documents that
are already posted to ledgers, perform the following Customizing activities under Financial Supply Chain Management Cash and Liquidity Management Cash Management
Data Setup :

Rebuild Planning Levels, Groups, Dates in Accounting Documents

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 elds 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 ll in the updated planning level and planning group information into the existing BSEG records.

Rebuild Flow Types in Accounting Documents

This activity is to derive ow types for accounting document line items that have already been posted. Typically, ow types are automatically derived as postings are made.
However, you must run this Customizing activity to derive ow types for accounting document line items that have already been posted but for which the ow types are
missing.

The way the system derives ow types for accounting document line items is described in the documentation of the Customizing activity Assign Flow Types to G/L Accounts
under Financial Supply Chain Management Cash and Liquidity Management Cash Management Flow Type . For more information, see Flow Types.

Rebuild Liquidity Items in Accounting Documents

This activity is to derive liquidity items for line items that are already posted to ledgers. Typically, liquidity items are automatically derived as postings are made. However, you
must run this Customizing activity to generate liquidity items data for line items that are already posted but are missing liquidity items. When building liquidity items data, the
system reads required data from the BSEG table, which stores line items that are posted on accounting documents. Then it populates the derived liquidity items data back to
the BSEG table so that other application features can consume the liquidity information directly.

Insert House Bank and House Bank Account Data to Accounting Documents

This activity is to insert house bank ( eld HBKID) and house bank account ( eld HKTID) data into table BSEG before you use the applications that use historical cash
management data.

Load Data into One Exposure from Operations Hub

The One Exposure from Operations hub is a central storage location for operational data that is relevant for managing cash and liquidity. The provision of the data in the One
Exposure from Operations hub facilitates funds planning and risk management across multiple companies. Currently, SAP S/4HANA Finance for cash management uses One
Exposure from Operations to acquire the following data:

Transaction data from source applications in the central system of SAP S/4HANA Finance for cash management:

Financial Operations

Accounting Documents (FI)

Bank Statements

Promise to Payment (P2P)

Treasury and Risk Management (TRM)

Consumer and Mortgage Loans (FS-CML)

Contract Accounts Receivable and Payable (FI-CA)

Materials Management (MM)

Sales and Distribution (SD)

To upload existing data from these source applications, perform the Customizing activity Load Transaction Data from Source Applications into One Exposure from Operations
Hub under Financial Supply Chain Management Cash and Liquidity Management Cash Management Data Setup .

For more information, see Integration with Source Applications in the Central System in Con guration for One Exposure from Operations

Data from integrated remote systems:

Manual Entry of Bank Cash Balances

To upload bank account balances (derived from external sources), in the central system, perform the activity Import Bank Cash Balances, in the SAP menu under
Accounting Financial Supply Chain Management Cash and Liquidity Management Tools One Exposure from Operations .

Classic Cash Management

To transfer classic cash management data to the One Exposure from Operations hub, in the remote systems, perform the activity Send TR-CM Data, in the SAP menu
under Accounting Financial Supply Chain Management Cash and Liquidity Management Tools Distribution TR-CM Subsystems .

This is custom documentation. For more information, please visit the SAP Help Portal 79
2/24/2024
The transfer of the classic cash management data is triggered by a request of the central system. To do this, in the central system, perform the activity Retrieve CM
Data, in the SAP menu under Accounting Financial Supply Chain Management Cash and Liquidity Management Tools Distribution .

SAP Liquidity Planner

To transfer data from SAP Liquidity Planner into the One Exposure from Operations hub, in the remote systems, perform the activityInitial and Periodic Update, in the
SAP menu under Accounting Financial Supply Chain Management Cash and Liquidity Management Liquidity Planner One Exposure Update .

For more information, see Integration with Remote Systems in Con guration for One Exposure from Operations

More Information
For sources applications of FI and MM, you can run the ow builder program to set up the data.

For more information, see Build Cash Flows from Operations.

Build Cash Flows from Operations

Build ows for FI and MM documents.

For sources aplications of FI and MM, you can run the Flow Builder program to generate cash-relevant ows, which are then imported to One Exposure from Operations.

To do so, perform the Customizing activity Build Cash Flows from Operations under Financial Supply Chain Management Cash and Liquidity Management Cash Management
Data Setup .

For more information, see Customize the Flow Builder in the Con guration Guide for SAP S/4HANA Finance for Cash Management.

Bank Relationship Management

Use
With Bank Relationship Management, cash managers and cash specialists are able to centralize the management of bank accounts and perform the following tasks:

De ne banks, house banks, house bank accounts, and bank accounts

Display bank accounts in standard views including the Bank Hierarchy view and the Account List view

De ne custom views using bank account groups

Manage cash pools and perform cash concentration

Use signatory control for payment approval process

Use dual control or work ow processes for opening, modifying, closing, reopening, and reviewing bank accounts

Import or export bank accounts

Replicate house banks, house bank accounts, and bank accounts

Check foreign bank accounts and responsible payment signatories in your company

Related Information
Bank
House Bank
House Bank Account
Manage Banks
Manage Bank Accounts
Manage Bank Accounts - Bank Hierarchy View
My Inbox - For Bank Accounts
My Sent Requests
Maintain Signatory
Initiate Review Process
Monitor Review Status
Manage Work ows - For Bank Accounts
Foreign Bank Account Report

De ning Banks, House Banks, Bank Accounts, House Bank Accounts

With Bank Relationship Management, you can de ne the following master data:

De ning banks and house banks using the Manage Banks app.

Alternatively, you can use SAP GUI transaction FI01 to de ne banks and FI12_HBANK to de ne house banks.

De ning house bank accounts and bank accounts using the Manage Bank Accounts app.

This is custom documentation. For more information, please visit the SAP Help Portal 80
2/24/2024
Alternatively, you can use SAP NetWeaver Business Client (NWBC) as the user interface to de ne bank accounts and house bank accounts.

De ning Banks
To de ne a bank, you can use the Manage Banks app.

Alternatively, you can use SAP GUI transaction FI01 to de ne banks.

De ning House Banks

Use
The house banks of your company are the banks that your company has an account with. You can use them to process payment transactions.

In the SAP system, house banks have the following characteristics:

They are assigned to company codes.

Each company code can have multiple house banks.

Each house bank of a company code is represented by a bank ID.

Every account at a house bank is represented by an account ID.

In the SAP system, you use the bank ID and the account ID to specify bank details. Bank ID and account ID are used, for example, for automatic payment transactions to determine
the bank details for payment.

To create a house bank, you use this transaction. To create the house bank accounts, you use an SAP Business Client application. The account IDs are generated in the process. For
more information, see Bank Account Management.

 Note
If you have already performed the IMG activity Transfer Bank Directory Data under SAP Customizing Implementation Guide Cross-Application Components Bank Directory
and then Transfer Bank Directory Data - International or Transfer Bank Directory Data - Country-Speci c, you have already created house banks in the system or have updated
existing house bank data. If this is the case, you only have to create the missing house banks in this step. You can add also missing information for the existing house banks.

Create a House Bank

To de ne your house banks, proceed as follows:

1. Enter transaction code FI12_HBANK or, in the SAP Menu, go to Accounting Financial Accounting Banks Master Data House Banks Create / Change .

2. In the Determine Work Area: Entry dialog, do the following:

Bank relationship data that enables you to maintain bank-related information such as internal and bank contact persons, and bank statement data.

Connectivity paths that enable you to con gure the integration from a bank account to the corresponding house bank accounts or other account records, in either the central
system or other remote systems.

Payment signatories that enable you to de ne payment approval processes for payments that are made through a bank account.

Overdraft limits that enable you to manage the overdraft limits of a bank account.

Cash pools that enable you to maintain cash pools and perform cash concentration activities.

Multi-language descriptions that allow you to de ne account descriptions in diﬀerent languages.

File or hyperlink attachments as reference documents.

Alternatively, you can use SAP NetWeaver Business Client (NWBC) as the user interface to de ne bank account master data.

Related Information
Maintaining a Signatory in Multiple Bank Accounts
Maintaining Overdraft Limits for Bank Accounts
Maintaining Connectivity Path
Managing Attachments

Maintaining a Signatory in Multiple Bank Accounts

Replacing a Signatory in Multiple Bank Accounts

In a company, if a signatory who is responsible for multiple bank accounts leaves the company, you have to replace the signatory with a new one. To do so, proceed as follows:

1. In the Maintain Signatory application, search for the signatory that you want to replace.

The system displays the bank accounts that list this user as one of the signatories.

2. Select the bank accounts that you want to change, and choose Change Signatory.

3. Specify a new signatory.

Adding a Signatory to Multiple Bank Accounts

You have de ned a signatory for several bank accounts. Now you want to add another signatory to the identical set of accounts or part of the accounts. To do so, proceed as follows:

1. In the Maintain Signatory application, select the bank accounts that you want to add the new signatory to, and then choose Add Signatory.

2. Specify a new signatory.

The system adds the new signatory to the bank accounts that you have speci ed.

Revoking Authorization of a Signatory in Multiple Bank Accounts

To revoke the authorization of a signatory in multiple accounts, proceed as follows:

1. In the Maintain Signatory application, search for the signatory that you want to revoke authorization or just change the validity period.

The system displays the bank accounts that list this user as one of the signatories.

2. Select the bank accounts that you want to change, and choose Revoke Signatory.

3. Change the validity period as you need.

This is custom documentation. For more information, please visit the SAP Help Portal 82
2/24/2024

Maintaining Overdraft Limits for Bank Accounts

You can maintain one for more overdraft limits for a bank account. The overdraft limits are time dependent, therefore the total overdraft limit of the bank account may vary with time
if you maintain multiple overdraft limits for diﬀerent periods of time.

 Example
The bank grants your company an overdraft limit of 100000 EUR for year 2013. Your company requests an additional overdraft limit of 50000 EUR for the end of the rst quarter.

You de ne the overdraft limits in the system as below:

EUR, 100000, Valid from January 1, 2013 to December 31, 2013

EUR, 50000, Valid from March 25, 2013 to March 31, 2013

The total overdraft limit of Euro for this bank account in year 2013 is:

From January 1, 2013 to March 24, 2013: 100000 EUR

From March 25, 2013 to March 31, 2013: 150000 EUR

From April 1, 2013 to December 31, 2013: 100000 EUR

Maintaining Connectivity Path

Connectivity path enables you to link a bank account to its corresponding house bank account in the central system where SAP S/4HANA Finance for cash management is installed,
or to account records in remote SAP or non-SAP systems.

You can de ne the following types of linkages according to your business needs:

Link the bank account to one or more house bank accounts that exist in the central system

 Note
You can link a house bank account to only one active bank account.

Specify the Category ID as Central System: House Bank Account and then specify the following:

Company code

House bank ID

To create a new house bank, choose the Manage House Bank button. For more information, see De ning House Banks.

House bank account ID

To create a new house bank account, enter a unique account ID and other necessary elds. For more information, see De ning House Bank Accounts.

Validity period

Link the bank account to a G/L account when there is no relevant house bank account available

Specify the Category ID as Central System: G/L Account and then specify the G/L account number on the House Bank Account Data tab.

Link the bank account to a house bank account that exists in a remote SAP Business Suite system

Specify the Category ID as Remote System: House Bank Account and then specify the following:

Remote system ID

Company code

House bank ID

House bank account ID

Validity period

Link the bank account to a G/L account that exists in a remote SAP Business Suite system

Specify the Category ID as Remote System: G/L Account and then specify the following:

Remote system ID

Company code

Additional ID: Enter the G/L account number

Validity period

Link the bank account to an account record in a third-party system

Specify the Category ID as Others and then specify the following:

Remove system: Specify the third-party system

Additional ID: Enter an identi er that points to the target account in the non-SAP system

This is custom documentation. For more information, please visit the SAP Help Portal 83
2/24/2024
Validity period

Managing Attachments
With the SAP Document Management System, you can upload documents or URLs as attachments to bank accounts. In the Manage Bank Accounts app, you can manage your
attachments as follows:

Uploading Attachments
Upload an attachment for a certain bank account.

To do so, open the bank account entry, and then in the top right corner, choose Manage Attachments to upload attachments for this bank account.

Upload an attachment for multiple bank accounts en masse

To do so, in the Account List view, proceed as follows:

1. Choose Create Document.

2. Specify a document type and leave the other elds blank.

You can use the prede ned document type BAM or a document type that is de ned by your company.

3. Press Enter .

4. Enter a description for the attachment.

5. Choose the Create Original button and then in the popup window, specify the following values:

Application: The format of the attachment.

Original: Specify the menu path of the le from a virtual drive or enter a URL.

6. Choose Save and then in the popup window, specify DMS_C1_ST as the storage category.

7. Go to the Additional Data tab, and then specify the bank accounts to which you want to upload the attachment.

8. Save your changes.

The system assigns a document number to the upload attachment.

Searching for Attachments

To search for an attachment, you can do either of the following:

Searching for attachments of a speci c bank account

To do so, open the bank account entry, and then in the top right corner, choose Manage Attachments to check the attachments for this bank account.

Searching for attachments without specifying a bank account

To do so, in the Account List view, choose Find Document.

You can search for attachments using various attributes, such as document description, document type, and attributes for bank accounts.

Alternatively, you can use SAP NetWeaver Business Client (NWBC) as the user interface to manage attachments of bank accounts.

De ning House Bank Accounts

The house bank accounts of your company are the bank accounts that your company owns. You can use them to process payment transactions. Each house bank account is linked to a
bank account in bank account master data via a connectivity path. To create a house bank account, proceed as follows:

1. In the Manage Bank Accounts app, open a bank account.

2. On the Connectivity Path tab, create an entry with the following values:

ID Category: specify Central System: House Bank Account

House Bank

Valid From and Valid To

3. Below the table, on the House Bank Account Data tab, specify a unique ID for this house bank account.

The account ID can be alphanumeric. The length limit is 5 digits.

4. Specify the G/L Account to which payment transactions should be posted to.

Deleting Bank Accounts

You can only delete inactive bank accounts and bank account drafts. You cannot delete an active bank account that has been oﬃcially approved and opened, nor set it back to inactive.
If you are no longer using an active bank account, you can close the bank account.

This is custom documentation. For more information, please visit the SAP Help Portal 84
2/24/2024

 Note
If work ows are implemented for bank account management, you cannot delete bank accounts that are already involved in a work ow process.

To delete inactive bank accounts or bank account drafts, do either of the following in the Manage Bank Accounts app:

Open a bank account entry, and then on the account details page, choose the Delete button to delete the account.

From the bank account list, select one or more account entries, and then choose the Delete button to delete the selected account entries en masse.

Alternatively, you can use SAP NetWeaver Business Client (NWBC) as the user interface to delete bank accounts.

Related Information
Manage Bank Accounts

Editing the Bank Hierarchy

Adding Banks to Bank Hierarchy

The bank hierarchy view displays banks in a hierarchical structure. The hierarchical relationship is constructed by business partners that represent banks or bank groups. By default,
only organization business partners assigned with the role Bank (TR0703) are displayed in the structure. If you have banks that are assigned to an organization business partner
without the role Bank (TR0703), or not assigned to any business partner, they are not displayed in the bank hierarchy. To add them into the bank hierarchy, follow the procedure
below.

1. Choose Bank Hierarchy and then choose the Edit button.

The left pane displays all the available banks in your system. If the In Hierarchy checkbox is not selected for a bank, it means that the bank is not yet added to the hierarchy
displayed on the right pane.

2. To add a bank into the bank hierarchy, on the left pane, select the bank.

3. On the right pane, select a business partner under which you want to add the bank.

4. Do either of the following:

To add the bank directly under the business partner on the right pane, choose the Add Bank button.

To assign the bank to a business partner before adding it under the business partner on the right pane, choose the Add Bank with BP button.

You can either use an existing business partner that is not yet in the bank hierarchy, or create a new business partner for this bank.

Modifying Hierarchical Relationship

To make changes to the hierarchical order of the bank hierarchy, you can adjust the business partner nodes by using drag and drop.

Removing a Bank from the Bank Hierarchy

Banks and their corresponding business partners are displayed in the bank hierarchy in either of the following ways:

If a business partner corresponds with multiple banks, the banks are displayed as subnodes under the business partner.

To remove one of the banks from the bank hierarchy, select the bank and then choose Remove Bank.

If a business partner corresponds with only one bank, the bank information is displayed together with the business partner name.

To remove the bank from the bank hierarchy, select the business partner entry and then choose Remove Bank.

The bank information is removed from the entry while the business partner stays in the hierarchy. If you want to remove the business partner also from the bank hierarchy, in
the SAP GUI transaction BP, remove the role Bank (TR0703) from the business partner.

Creating Bank Account Groups

Context
In addition to the standard views including the Bank Hierarchy view and the Account List view, you can also de ne your own views for displaying bank accounts in hierarchical
structures, by using the bank account groups. It enables you to de ne diﬀerent views for diﬀerent management purposes. You can also create cash pools using the bank account
group function. For more information, see Working with Cash Pools

Procedure
1. To create a new bank account group, choose the Create button in the Bank Account Group Views line.

2. Enter a name for the bank account group.

3. To de ne the visibility of the bank account group, do either of the following:

To make the bank account group a private view that is only visible to yourself, select the Visible Only to Creator radio button.

This is custom documentation. For more information, please visit the SAP Help Portal 85
2/24/2024
To make the bank account group a view that can be used by other people, select the Visible to De ned Users radio button, and then specify the authorized users by
choosing the Manage Visibility button.

 Note
If you select the Visible to De ned Users radio button but do not specify any user in Manage Visibility, the bank account group is visible to all users.

4. To create the rst-level node for your structure, choose the Create Node button to add a node.

5. You can create subnodes as you needed.

6. From the left pane, select the bank accounts that you want to add to the structure, and then choose Add to Bank Account Group.

7. Save the bank account group.

8. In the Manage Bank Accounts window, choose the Refresh button.

You can see and access the bank account group view by choosing the bank account group name.

Working with Cash Pools

Use
With Bank Account Management, you can create cash pools based on a bank account group structure and use cash concentration to centrally manage your cash.

Procedure
Creating Bank Account Groups for Cash Pooling

To create a cash pool, you must rst de ne a bank account group for the cash pool. It enables you to view the cash pool accounts in a hierarchical structure and do cash concentration
in Bank Account Management.

 Note
For bank account groups to be used for cash pooling, note the following:

De ne only one rst-level node for the bank account group

For bank accounts placed under a sub-node, all accounts under this sub-node must be of the same company code.

For more information about how to create a bank account group, see Creating Bank Account Groups.

De ning Cash Pools

1. In the Manage Bank Accounts app, select a bank account group that you have de ned for cash pooling, then from the Cash Pool dropdown list, choose the Create Cash Pool
option.

2. In the Cash Pool Data section, specify the cash pool ID, name, and usage.

3. In the Target Account section, specify the account information for the superior bank account.

4. In the Source Accounts section, specify the following for the subordinate bank accounts.

Account information

Payment method

Planned balance: The system evaluates the planned balance and the current balance of a source account so as to generate payment request proposals.

Minimum amount: When you make a transfer from a source account, the minimum amount is considered.

 Example
The table below shows how transfers can be conducted.

Current Account Balance Planned Balance Cash Concentration Proposal

(EUR) (EUR)

8000 5000 The system proposes that you transfer 3000 EUR, the amount that exceeds the planned balance, to the superior bank account.

3000 5000 The system proposes that you transfer 2000 EUR from the superior account to the source account so that the planned balance of the
source account can be reached.

Performing Cash Concentration

1. To perform cash concentration, in the Manage Bank Accounts window, select the bank account group that represents the cash pool you want to work with.

2. From the Cash Pool dropdown list, select Cash Concentration.

3. Specify a planning date.

4. Check the payment request proposals generated by the system.

This is custom documentation. For more information, please visit the SAP Help Portal 86
2/24/2024
5. To create a bank account transfer, choose the Create Payment Requests.

Using Signatory Control for Payment Approvals

Use
With Bank Relationship Management, users that are de ned as payment signatories are able to approve or reject payment documents.

Prerequisites
1. The signatory function has been enabled in Customizing under Financial Supply Chain Management Cash and Liquidity Management Bank Account Management
Enable Signatory Control .

2. The signatory groups, approval patterns, and pattern priorities have been properly con gured in Customizing under Financial Supply Chain Management Cash and
Liquidity Management Bank Account Management Basic Settings De ne Settings for Bank Account Master Data .

Activities
The system determines an approval pattern for each bank account according to the settings in Customizing activity De ne Settings for Bank Account Master Data. An approval
pattern speci es the following:

Signatory groups eligible for the approval process

Approval sequence

For sequential approval patterns, each signatory group is assigned with a step sequence. Any of the eligible signatories under this group can approve the payment and
nish the step.

For non-sequential signatory patterns, the signatory groups approve payments regardless of sequential order. All the signatory groups receive the approval request at
the same time. Any two of the signatory groups can approve the payment and complete the approval process.

An eligible signatory must meet the following requirements:

The signatory belongs to a signatory group de ned in the approval pattern.

The payment amount does not exceed either the de ned limit per document nor the limit for batch payment.

The signatory is active.

 Note
In the following exceptional cases, the system may fail to nd any eligible signatory for a payment request and reports an error message. You can contact your administrator to
reassign the request.

The payment amount exceeds the maximum amount de ned with the signatories

Signatories are inactive

Payment approval pattern cannot be determined

Using Approval Processes for Bank Account Management

 Note
The dual control mode is not supported if you use SAP NetWeaver Business Client (NWBC) as the user interface.

Related Information
Using SAP Business Work ow for Bank Account Management
Using Dual Control for Bank Account Management

Using SAP Business Work ow for Bank Account Management

Use
SAP provides prede ned work ow processes for the following scenarios:

Opening a new bank account

Copying an existing bank account to create a new one

Making changes to a bank account

This is custom documentation. For more information, please visit the SAP Help Portal 87
2/24/2024
Changing a signatory in multiple bank accounts

Closing a bank account

Reopening a bank account that is already closed

Reviewing bank accounts

For more information on the prede ned work ows and the technical implementation of work ows, see Con guration for Work ows.

How-To Video (English only)

Using Work ows for Bank Account Management

Video thumbnail

Open this video in a new window

 Note
Captions/subtitles are available for multiple languages. Simply click the CC button at the bottom right of the video player to see which languages are supported.

Using Dual Control for Bank Account Management

In addition to SAP Business Work ow, you can choose to implement dual control for bank account management. With dual control, revisions are saved when users create or edit bank
accounts in the following scenarios. The revisions have to be activated by another authorized user before they become eﬀective.

Opening a new bank account

Copying an existing bank account to create a new one

Modifying a bank account

Changing a signatory in multiple bank accounts

Closing a bank account

Reopening a bank account that is already closed

For information on the settings required for using dual control, see Con guration for Dual Control .

How-To Video (English only)

Using Dual Control for Bank Account Management

Video thumbnail

This is custom documentation. For more information, please visit the SAP Help Portal 88
2/24/2024

Open this video in a new window

 Note
Captions/subtitles are available for multiple languages. Simply click the CC button at the bottom right of the video player to see which languages are supported.

Importing and Exporting Bank Accounts

With the tool Import and Export Bank Accounts, you can do the following:

Import bank accounts from a source le

For more information, see Importing Bank Accounts.

Export bank accounts to an XML le for batch editing

You can edit bank accounts in either XML or spreadsheet format. For more information, see Exporting Bank Accounts.

Enhance the template and validation schema for customer-de ned elds

For more information, see Enhancing Template and Validation Schema for Custom Fields.

Importing Bank Accounts

Prerequisites
You use Microsoft Oﬃce 2010 or higher that contains Microsoft Excel.

You have enabled the Developer tab in Microsoft Excel.

To do so, in the Microsoft Excel, go to File Options Customize Ribbon , and then add the Developer tab.

In the SAP GUI application, you have properly con gured the number ranges for bank account technical IDs as follows:

1. De ne number ranges for bank account technical IDs in the Customizing activity De ne Number Ranges for Bank Account Technical IDs, under Financial Supply
Chain Management Cash and Liquidity Management Bank Account Management Basic Settings .

2. Specify a number range for bank account technical IDs in the Customizing activity De ne Settings for Bank Account Master Data, under Financial Supply Chain
Management Cash and Liquidity Management Bank Account Management Basic Settings , on the Bank Account Master Data Setting tab.

You can de ned banks for the bank accounts to be imported in the target system.

Procedure
1. From the Manage Bank Accounts app, choose the Import and Export Bank Accounts button.

2. To prepare bank account data to be migrated, download the template by choosing Download XML Spreadsheet Template.

3. Save and open the le XML_SpreadSheet_Template.xml.

4. In the XML le, ll in information that is essential to your business operations either by manual entering data or by copying and pasting data to the corresponding sheets.

5. On the Developer tab, choose Export to export the data as an XML le.

6. To import the bank accounts, specify the import path of the XML source data le and then choose Import to upload the le.

This is custom documentation. For more information, please visit the SAP Help Portal 89
2/24/2024
You can choose either of the following two modes for the import:

Overwrite mode: By selecting the Overwrite option, if you leave a eld blank in the source le, the respective eld in the bank account master data will be erased after
the import.

Update mode: By deselecting the Overwrite option, empty elds in the source le will be ignored during the import. Only elds with values will be updated after the
import.

 Note

Before you export data Microsoft Excel, check the data and make sure the following:

All the bank account entries you want to import are inside the blue frame.

The application does not import data outside of the frame.

There are no empty rows between bank account entries.

The application treats empty rows as incorrect entries.

We recommend that you rst 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.

Next Steps
Exporting Bank Accounts

Exporting Bank Accounts

Prerequisites
You use Microsoft Oﬃce 2010 or higher that contains Microsoft Excel.

You have enabled the Developer tab in Microsoft Excel

To do so, in your Microsoft Excel, go to File Options Customize Ribbon Customize the Ribbon , select the Developer checkbox and choose OK.

Procedure
1. In the Manage Bank Accounts app, choose Import and Export Bank Accounts.

2. To export the bank accounts, choose Export Bank Accounts to an XML File.

3. Save the le Bank_Accounts.xml.

The le contains all the existing bank account master data in your system in XML format. If you like, you can directly make changes to the XML le.

4. To edit your le in spreadsheet format, choose Download XML Spreadsheet Template.

5. Save and open the le XML_SpreadSheet_Template.xml.

6. On the Developer tab, choose Import and then select the le Bank_Accounts.xml.

You can now view and make changes to your bank account in spreadsheet format.

Next Steps
Importing Bank Accounts

Enhancing Template and Validation Schema for Custom Fields

You are able to add additional elds according to your business needs by appending structure CI_AMD_EXT to database table FCLM_BAM_AMD. To enhance the template for
importing and exporting bank accounts and assign checks for custom elds, proceed as follows:

1. To enhance the XML schema for validation, choose Download XML Schema File for Import Validation.

2. Edit the downloaded le XML_Schema_Import.xml with the Notepad or other XML editing tools.

The XML le already contains the custom elds you have de ned.

3. For each customer eld, add an attribute type as appropriate.

The value of the type attribute can be one of the simple types de ned. If the simple types are not suﬃcient, you can add your own type de nitions.

4. Download the XML template by choosing Download XML Spreadsheet Template.

5. Open the template le XML_SpreadSheet_Template.xml. On the Developer tab, choose Source, the prede ned validation structure is displayed.

6. Choose the XML Maps button, and then delete the default mapping dataroot_Map.

 Note
The rst two lines are the descriptions and technical types of the elds. Do not delete them.

This is custom documentation. For more information, please visit the SAP Help Portal 90
2/24/2024
7. To add the new validation schema that contains the check for customer elds, choose the Add button to import the changed schema le XML_Schema_Import.xml, and
select dataroot.

8. Map the new validation le to the corresponding cell of each sheet by using drag and drop.

9. To activate the validation, on the Developer tab, choose Map Properties and select the checkbox Validate data against schema for import and export.

10. Save the le as your new template.

Cash Operations

Use
With the functions of cash operations, cash managers can review short-term cash forecast based on imported bank statements, check the cash ows by navigating to the line items
and manage bank transfers and outgoing payment by approval process. Other daily operations tasks include memo records, cash concentration, de cit cash pools and so on. Cash
operations helps you monitor the liquidity status of your company and lets you make liquidity plans to mitigate nancial risks and maximize nancial bene ts.

Prerequisites
Make sure you have activated SAP S/4HANA Finance for cash management.

The calculation is based on the transaction data from memo records and One Exposure from Operations. Make sure you have con gured the settings of One Exposure from
Operations. For more information, see Con guration for One Exposure from Operations in the Con guration Guide for SAP S/4HANA Finance for Cash Management

You have made the following settings for Cash Operations.

Customizing activities for Liquidity Management under Financial Supply Chain Management Cash and Liquidity Management Cash Management

Con guration for Cash Operations in the Con guration Guide for SAP S/4HANA Finance for Cash Management

Set Up Cash Management Data in the Data Setup Guide for SAP S/4HANA Finance for Cash Management

Features
Cash Position and Short Term Cash Forecast

You can use the cash position KPI or drill down to the details and the cash ow items. Based on the imported bank statements, you can again an overview of cash position and short-
term cash forecast. This provides you with information on the current nancial situation in your bank accounts and bank clearing accounts.

The following apps are related to this feature:

Bank Statement Monitor

Cash Position

Cash Flow Analyzer

Check Cash Flow Items

Bank Transfers

You can make inter-bank transfers and track the details of your transfers, with an enhanced outgoing payment by approval process.

The following apps are related to this feature:

Make Bank Transfers

Track Bank Transfers

Cash Concentrations

You can concentrate the balances of various accounts in one target bank account, for example the account oﬀering the best conditions. All accounts you plan to concentrate are
linked together in a grouping structure. You can de ne various groupings for diﬀerent cash concentrating procedures accordingly.

For more information, see Working with Cash Pools.

Memo Records

You diﬀerentiate between the payment advices relevant for the cash position and the planned items relevant for the liquidity forecast. You can create memo record manually and
select memo records in a list to transfer them afterwards into an archive.

The following apps are related to this feature:

Edit Memo Record

Display Memo Records

Others

You can also review the KPIs of bank risk and de cit cash pools. Reviewing banks of low ratings and cash pools with de cits facilitates your bank transfer decisions.

This is custom documentation. For more information, please visit the SAP Help Portal 91
2/24/2024
The following apps are related to this feature:

Bank Risk

De cit Cash Pool

Liquidity Management

Use
With the functions of liquidity management, cash managers can analyze actual cash in ows and out ows, forecast medium-term liquidity trends, and perform a rolling planning so
that they can understand what payment obligations are to be ful lled and whether they need to make investment or funding plans.

Prerequisites
You have activated SAP S/4HANA Finance for cash management.

The calculation is based on the transaction data from memo records and One Exposure from Operations. Make sure you have con gured the settings of One Exposure form
Operations. For more information, see Con guration for One Exposure from Operations in the Con guration Guide for SAP S/4HANA Finance for Cash Management.

You have made the following settings for Liquidity Management.

Customizing activities for Liquidity Management under Financial Supply Chain Management Cash and Liquidity Management Liquidity Planning

Con guration for Liquidity Management in the Con guration Guide for SAP S/4HANA Finance for Cash Management

Set Up Cash Management Data in the Data Setup Guide for SAP S/4HANA Finance for Cash Management

Features
Liquidity Forecast Analysis

You can forecast the medium and long term liquidity trend, get an overview of the liquidity and view the details of forecasted amounts of each liquidity item.

The following apps are related to this feature:

Cash Flow Analyzer

Liquidity Forecast

Liquidity Forecast Details

Actual Cash Flow Analysis

You can get an overview of the daily cash in ows and out ows, and analyze the details for the last weeks or months for all subsidiaries and liquidity items. You can then identify
the extraordinary and abnormal cash ows, and ensure that they are accurate and compliant.

The following apps are related to this feature:

Cash Flow Analyzer

Actual Cash Flow

Cash Flow - Detailed Analysis

Rolling Liquidity Planning

You can analyze the liquidity based on the actual, plan and forecast data, and the alerts of diﬀerence between current plans and previous ones. You can also develop a liquidity
plan for a new planning cycle with an approval process.

The following apps are related to this feature:

Liquidity Plans

Develop Liquidity Plans

One Exposure from Operations

De nition
The One Exposure from Operations 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 One Exposure from Operations hub facilitates funds planning and risk management across multiple companies.

Use
The One Exposure from Operations hub can receive operational data from sources within the system in which it runs itself, as well as from external sources. Currently it can receive
data from the following sources:

Sources Within the Same System (one-system scenario)

Source Name Source ID Default Flow Types Flow Types Available for Con guration

This is custom documentation. For more information, please visit the SAP Help Portal 92
2/24/2024

Source Name Source ID Default Flow Types Flow Types Available for Con guration

Financial Operations BKPF 900900 – Incoming Cash from Invoices Not applicable

P2P 900901 – Outgoing Cash from Invoices

900902 – Incoming Cash from Payments

900903 – Outgoing Cash from Payments

900910 – Incoming Cash from Bank

Statements

900911 – Outgoing Cash from Bank

Statements

900900 - Incoming Forecast Cash (P2P)

Treasury and Risk Management TRM 900100 – Incoming Bank Cash (TRM) Not applicable

900101 – Outgoing Bank Cash (TRM)

Consumer and Mortgage Loans CML 900104 – Incoming Bank Cash (CML) Not applicable

900105 – Outgoing Bank Cash (CML)

Contract Accounts Receivable and Payable FICA 900106 – Incoming Cash (FI-CA) Not applicable

900107 – Outgoing Cash (FI-CA)

Materials Management MM 900000 – Incoming Bank Cash Not applicable

900001 – Outgoing Bank Cash

Sales and Distribution SDCM 900000 – Incoming Bank Cash Not applicable

900001 – Outgoing Bank Cash

900018 – Incoming Bank Cash (Tax)

900019 – Outgoing Bank Cash (Tax)

External Sources (side-by-side scenario)

Source Name Source ID Default Flow Types Flow Types Available for Con guration

Classic Cash Management CMSND, CMDSR 900110 – Incoming Cash (IDoc) 900108 – Cash Balance Increase (IDoc)

900111 – Outgoing Cash (IDoc) 900109 – Cash Balance Decrease (IDoc)

Manual Entry of Bank Cash Balances MEBAC 900102 – Bank Cash Balance Increase Not applicable

900103 – Bank Cash Balance Decrease

SAP Liquidity Planner LPA 900112 – Incoming Cash (LP) Not applicable

900113 – Outgoing Cash (LP)

The source application One Exposure is a prerequisite for all other source applications. You must activate this source application for a company code rst to enable the One Exposure
from Operations hub to receive data. Then you can activate additional source applications for that company code.

You activate source applications in the Customizing activities under Financial Supply Chain Management Cash and Liquidity Management Cash Management Data Setup .

To give users access to the data stored in the One Exposure from Operations hub, you use the following authorization object: FQM_FLOW.

 Note
Original System is a key information to diﬀerentiate ows that are stored in One Exposure. If the original system is changed, it will probably cause severe data issue in One
Exposure. The ows in the old original system cannot be updated automatically in the new original system.

In the case when the original system is changed, you are suggested to delete ows with the old original system using the FQM_DELETE program and rebuild ows with the new
original system using the FQM_INITIALIZE and the FCLM_FLOW_BUILDER programs, in order to avoid the issue. For S/4HANA Cloud customers, please raise customer incident
for further support.

Financial Operations in One Exposure from Operations

Use
You can integrate invoices, payments, and bank statements from Accounts Receivable/Accounts Payable (AR/AP) into One Exposure from Operations. In this integration scenario,
the source application Financial Operations and One Exposure from Operations run in the same system (one-system scenario).

Prerequisites
You have activated the source application Financial Operations for a company code using the following Customizing activity: Financial Supply Chain Management Cash and
Liquidity Management Cash Management Data Setup Activate Individual Source Applications .

This is custom documentation. For more information, please visit the SAP Help Portal 93
2/24/2024
Activities
The information is then consumed by cash management apps, such as:

Cash Flow Analyzer

Check Cash Flow Items

More Information
Integration of Accounting Documents

Integration of Bank Statements

One Exposure from Operations

Integration of Accounting Documents

Use
The system classi es accounting document (journal entry) line items into the following categories:

Posting on a customer or vendor account (Receivables or Payables)

Posting on a bank clearing account (Cash in Transit)

Posting on a bank account (Cash)

The system distinguishes the diﬀerent categories as follows:

Receivable or Payable

Items with account type D (Customer) or K (Vendor)

Cash in Transit

Items with a G/L account that is:

Either

Maintained in account determination of payment program (T042I)

A balance sheet account (SKA1-XBILK)

Not a reconciliation account (SKB1-MITKZ)

Maintained in account determination of bank-to-bank transfer (T042Y)

A balance sheet account (SKA1-XBILK)

Not a reconciliation account (SKB1-MITKZ)

Marked as cash relevant (SKB1-XGKON) and

With open item management (SKB1-XOPVW)

Cash

Items with a G/L account that is:

Either

Maintained in house bank accounts (T012K)

Marked as cash relevant (SKB1-XGKON) and

Without open item management (SKB1-XOPVW)

For these accounting document items, the system derives the following ow types:

 Note
The system only recognizes “positions”, examples of which are Regular Receivables, Unallocated Receivables, or Incoming Bank Con rmed Cash. Every position is considered
separately and thus, rst added to then subtracted from One Exposure. For further information, see the examples in Integration of Bank Statements.

Accounting Document Item Default Flow Types

This is custom documentation. For more information, please visit the SAP Help Portal 94
2/24/2024

Accounting Document Item Default Flow Types

Receivable or Payable 600000 - Regular Receivables Increase

600001 - Regular Payables Increase

600200 - Unallocated Receivables Increase

600201 - Unallocated Payables Increase

Revenue and Expenses 600500 - Delivered Goods/Services Increase

600501 - Received Goods/Services Increase

600510 - Received Goods/Services Decrease

600511 - Delivered Goods/Services Decrease

Tax 300000 - Input Tax Increase

300001 - Output Tax Increase

300010 - Output Tax Decrease

300011 - Input Tax Decrease

Cash in Transit 800006 - Incoming Cash in Transit Increase

800008 - Outgoing Cash in Transit Increase

Cash 900006 - Incoming Bank Con rmed Cash Increase

900008 - Outgoing Bank Con rmed Cash Increase

Date and Amount

The transaction date and amount are determined based on the billing date and the invoiced amount together with the payment terms.

For these accounting document items, the system oﬀers the following options to derive liquidity items:

Based on G/L accounts

Use the following Customizing activity: Financial Supply Chain Management Cash and Liquidity Management Cash Management Liquidity Items Derivation Rules for
Liquidity Items De ne Default Liquidity Items for G/L Accounts .

Based on queries of origin C (for Receivables or Payable) or D (Cash in Transit or Cash)

Based on a derivation function (exit)

For these accounting document items, the system oﬀers the following options to derive planning levels:

From the G/L account, where it is de ned in the master record for company code-speci c data.

For customer or vendor postings, it is derived from the planning group.

Use the following Customizing activity: Financial Supply Chain Management Cash and Liquidity Management Cash Management Planning Levels and Planning Groups
De ne Planning Groups .

For special G/L transactions, such as down payment requests, you can derive speci c planning levels.

Use the following Customizing activities: Financial Supply Chain Management Cash and Liquidity Management Cash Management Planning Levels and Planning
Groups Special G/L Transaction Levels .

Customers upgrading from the classic cash management can use the existing settings for the planning level when integrating Accounting Documents into One Exposure.

One Exposure derives cash forecasts for items representing receivables, payables, or cash in transit, and it stores actual cash from items representing cash. It stores this information
with the following certainty levels.

Certainty Level Description Meaning

ACTUAL Actual Accounting document line items from bank statements or accounting document line items with G/L accounts representing cash

SI_CIT Self-Initiated Cash in Transit Cash forecast from a self-initiated payment

REC_N Regular Receivable Cash forecast from an open item of a receivable

PAY_N Regular Payable Cash forecast from an open item of a payable

These forecasts and actuals contain information inherited from the offsetting accounting document line items of the corresponding receivable or payable. They are split based on this
inherited information. The inheritance uses the linkage between the affected accounting document items to analyze these accounting document chains. By doing so, the following
information from the offsetting accounting document line items of the receivable or payable is available in the forecasts and actuals:

Accounting Assignments:

Business Area

This is custom documentation. For more information, please visit the SAP Help Portal 95
2/24/2024
Pro t Center

Cost Center

WBS Element or a Project

Segment

Company

Material

Liquidity Item

 Example
The following example illustrates the inheritance and split logic for both forecasts and actuals:

1. A company receives a vendor invoice. The company purchased materials for two diﬀerent cost centers, CC01 and CC02. This information is passed on to the cash forecast
of the payable and thus this cash forecast is split into two ows according to the expense line items.

Vendor Invoice Cash

Forecast

Expense 01: 60 EUR for CC01 Forecast

from
Expense 02: 40 EUR for CC02
Payable
Account Payable: 100 EUR for
CC01:
60 EUR

Forecast
from
Payable
for
CC02:
40 EUR

2. The company then pays this vendor invoice. The cost center information is passed on to the cash forecast from cash in transit and thus this cash forecast is split into two
ows according to the expense line items.

Vendor Payment Cash Forecast

Account Payable: 100 EUR Forecast from Cash in Transit for CC01: 60 EUR

Bank Clearing Account: 100 EUR Forecast from Cash in Transit for CC02: 40 EUR

3. This payment is then con rmed by a bank statement. The cost center information is passed on to the actual cash from the bank statement and thus this actual cash is split
into two ows according to the expense line items.

Bank Statement Actual Cash

Bank Account: 100 EUR Actual Cash for CC01: 60 EUR

Bank Clearing Account: 100 EUR Actual Cash for CC02: 40 EUR

The following ow types are generated for forecasts and actuals in One Exposure:

Forecasts and Actuals Default Flow Types

Cash Forecasts from Receivables or Payables 900900 - Incoming Cash from Invoices

900901 - Outgoing Cash from Invoices

Cash Forecasts from Cash in Transit 900902 - Incoming Cash from Payments

900903 - Outgoing Cash from Payments

Actuals from Cash 900910 - Incoming Allocated Cash Increase

900911 - Outgoing Allocated Cash Increase

Central Finance

If Central Finance is deployed, all accounting documents that were created based on the accounting documents from your local systems can also be integrated into One Exposure.
Accounting document line items in a Central Finance system are, then categorized in the same way as described above and integrated into One Exposure accordingly. With Central
Finance, therefore, a side-by-side scenario for integrating accounting documents into One Exposure is also possible.

Activities
Customizing Activities

This is custom documentation. For more information, please visit the SAP Help Portal 96
2/24/2024
Assign Flow Types to G/L Accounts

If you want additional accounting document items to be processed by One Exposure from Operations, you have to de ne them using this Customizing activity. You do this by
assigning the corresponding G/L accounts to the following ow types, which are currently available to you. For example:

Category of Accounting Document Item Default Flow Types

Cash in Transit 800006 - Incoming Cash in Transit Increase

800008 - Outgoing Cash in Transit Increase

Cash 900006 - Incoming Bank Con rmed Cash Increase

900008 - Outgoing Bank Con rmed Cash Increase

If an item debits an account of this type, the system uses the rst ow type; if an item credits the account, the system uses the second ow type. These ow types are provided
as standard. There is no need to create additional customer-speci c ow types in this case.

 Caution
Do not assign ow types to a G/L account that is characterized as a reconciliation account.

 Note
You repeat the following Customizing activities each time an additional company code is activated for the source application Financial Operations.

Rebuild Flow Types in Accounting Documents

If you want to process existing accounting document line items, you use this activity to derive and rebuild ow types for those line items.

Rebuild Liquidity Items in Accounting Documents

If you want to process existing accounting document line items, you use this activity to derive and rebuild liquidity items for those line items. This Customizing activity oﬀers
two modes to derive liquidity items:

Initial Load for initial runs

Rebuild for rebuilding liquidity items subsequent to an initial run

Rebuild Planning Levels, Groups, Dates in Accounting Documents

If you want to process existing accounting document line items, you use this activity to derive and rebuild planning levels, planning groups, and planning dates for those line
items.

Load Transaction Data from Source Applications into One Exposure from Operations Hub

If you want to integrate transaction data that had already been created before the source application Financial Operations was activated, you use this Customizing activity.

Alternatively, you can also use the Customizing activity Build Cash Flows from Operations to load transaction data from the source application Financial Operations into One
Exposure.

Customize the Flow Builder

If you want the system to trigger regular updates of accounting documents into One Exposure, you use this activity to schedule automatic background jobs.

For more information, see Flow Builder.

Delete Data from One Exposure from Operations Hub

If you want to use a new starting point within an implementation project, you can use this Customizing activity to delete all existing data or the source application Financial
Operations from One Exposure. You do this for each company code and source application.

For more information, see Flow Builder.

More Information
Integration of Bank Statements

One Exposure from Operations

Flow Builder

Use
Overview

The Flow Builder generates cash ows detailing current amounts and dates of liquidity items by:

Tracing the original document line items from the related Financial Accounting (FI) and Materials Management (MM) tables.

Analyzing the document ow back to the source (original) document. The analysis is based on virtually clearing the open items in the preceding and subsequent documents,
which results in precise amount, date, and account assignment. Items in the preceding documents are called base items, while items in the subsequent documents are called
oﬀsetting items.

This is custom documentation. For more information, please visit the SAP Help Portal 97
2/24/2024
Generating cash ows, according to the remaining offsetting items that are not cleared in the source (original) document. Each cash ow is split according to the offsetting
items in the subsequent documents and the account assignment as inherited from the offsetting items in the source (original) document.

Importing the cash ows with the split amounts, dates, and liquidity items over into the One Exposure from Operations hub. Cash ows are then categorized into diﬀerent
certainty levels in One Exposure from Operations for further calculation and consumption.

Process

The following gure shows how the Flow Builder works. Based on the original transactional data from the related FI and MM tables, the Flow Builder generates cash-relevant ows,
re ecting amount, date, ow level, liquidity item and other account assignments, which are then imported to One Exposure from Operations.

Figure 1. How Flow Builder works

Example

The following example is based on a vendor invoice. The incoming invoice (1a) is cleared via an outgoing payment (2a). Posting on the vendor account is categorized as payables with
certainty level PAY_N, cash forecast from an open item of a payable. After that, the amount can be found in a bank clearing account for outgoing payments. Posting on the bank
clearing account is categorized as cash in transit with certainty level SI_CIT, cash forecast from a self-initiated payment. Then the bank clearing account is debited and the
transaction is posted at which point the bank clearing account is cleared (3a). This posting is categorized as cash with certainty level ACTUAL, accounting document line items from
bank statements.

Based on ow types, the Flow Builder traces the document chain back to its source. In the example below, this is the expense account, which shows a cash out ow of 100 EUR in
liquidity item E01. The expense account shows other account assignment information, such as cost center, company code, and so on.

This is custom documentation. For more information, please visit the SAP Help Portal 98
2/24/2024

Figure 2. An Example of Document Chain Analysis

Prerequisites
IMG Customizing Activities

To use the Flow Builder, make the required settings in Customizing under Financial Supply Chain Management Cash and Liquidity Management Cash Management :

Flow Types

Flow types classify the lifecycle of cash ows. Each ow type is assigned to an SAP-de ned ow category. Flow type and ow level are used to diﬀerentiate document line items.

For FI documents, ow types must be de ned and uploaded to line items in table BSEG.

For MM documents, ow types are generated in One Exposure from Operations.

For more information, see Flow Types.

Liquidity Items

Liquidity items is a customer-de ned attribute for categorizing the source and use of cash ows. It serves as an analytical dimension in cash ow statements and forecast reports.

For FI documents, liquidity items are uploaded to line items in table BSEG.

For MM documents, currently only the query sequence for liquidity item is supported in Flow Builder for MM, which is used in the generation of MM loading class. However,
when you de ne query sequence, only limited elds are supported. For more information, see SAP Note 2354048 .

For more information, see Liquidity Items and Liquidity Item Hierarchies.

Activate Individual Source Applications and Activate Multiple Source Applications under Data Setup

You can activate the source applications for Financial Operations (FI and BKPF) and Materials Management (MM) for cash ows corresponding to speci c company codes.

For more information, see Integration with Source Applications in the Central System.

Activities
The Flow Builder program uses the accounting interface (RWIN) to trace back to the original documents, which are stored in delta tables. The Setting and Tools feature controls the
background jobs based on the delta tables. Flows are then built automatically or manually.

Flow Builder (FCLM_FLOW_BUILDER)

You can run this transaction in two ways, either by running the Flow Builder or by using the Customizing activity Build Cash Flows from Operations. Flows are built either in the Delta
Run mode, or in the Mass Run mode:

In the Delta Run mode, ows are built automatically as the back-end job of the program is triggered after online posting of FI documents.

This is custom documentation. For more information, please visit the SAP Help Portal 99
2/24/2024
In the Mass Run mode, however, ows are built manually with certain search criteria, such as company code, scal year, document number, and line item. As an example, in the
case of an initialization and ow rebuild, you would want to use the Mass Run mode instead of the Delta Run mode.

 Note
For MM documents, the selection criteria diﬀers according to diﬀerent data sources:

For purchase orders (PO) and scheduling agreements, you can select company code, scal year, document number and line Item.

For purchase requisitions (PR), you can select from several criteria, such as purchase requisitions, item of requisitions, document type, and so on.

Flow Builder also allows you to perform the following activities:

Maximum Steps of Chain Tracing

You can de ne the maximum steps in a document chain trace. For example, if you choose one step of chain tracing, you nd the document ow with one preceding document
and one subsequent document.

Merge Tax Items

If you choose to merge tax items, the tax line item, which was previously split as a line item, is merged with other line items. This means that there is no separate line item for
tax. For more information, see SAP Note 2221748 .

Settings and Tools (FCLM_FB_UTIL )

You can run this transaction in two ways, either by running the Settings and Tools or by using the customizing activity Customize the Flow Builder.

With this transaction, you can perform the following activities:

Schedule Background Job

You use this setting to change the pre-de ned back-end job parameters, such as: Job Delay in Seconds, Variant for Flow Builder (Delta Run only), or
Background User for authorization check. The variants for Flow Builder (FCLM_FLOW_BUILDER ) are de ned in Transaction SE38. The background job name is in the
format of FLOW_FLOW_BUILDER_{CLIENT}*.

Check Background Job Logs

You use this setting to check the status of the back-end jobs. This activity is automatically triggered by online posting. By de ning the User Name and Job Name, you can
check the job status released, ready, active, nished, and canceled) within a time frame that you de ne.

Delete Flows

This tool allows you to de ne speci c search criteria to search for and delete ows from target tables.

Change Default Loading Classes

For FI documents, the default loading class is CL_FCLM_BSEGFLOW_SAMPLE. For MM documents, you must use this tool to generate a loading class. You can then designate
the query sequence to be used to derive liquidity items from MM transactions.

Generate Loading Classes

You use this tool to generate loading classes, by specifying Package, Exit Class and Loading Class Name.

FI documents require a Date. By default, the date is determined by the planning date for forecasting cash ows from invoices. For more information, see SAP
Note 2273656 .

MM documents requires Query Sequence in order to generate loading class. If you change the liquidity item derivation rules, you need to regenerate and assign
your loading class. Please note that only limited elds are supported when you de ne query sequence. For more information, see SAP Note 2354048 .

Assign Loading Classes

You use this tool to assign loading classes to the Flow Builder. Changes in the loading class is updated to the Flow Builder program.

Extensibility

Extension is supported. By taking the default exit class as an example, you can de ne your own exit class for use as the loading class in the Flow Builder. You can choose from the
following exit classes:

For FI documents, you can use the example exit class CL_FCLM_APAR_HADI_SAMPLE. The standard ABAP interface is IF_FCLM_HADI_APAR.

For MM documents, such as Purchase Order (PO) Filter, Purchase Requisition (PR) Filter and ow adjustment, you can use the example exit class
CL_FCLM_MM_HADI_SAMPLE. The standard ABAP interface is IF_FCLM_HADI_MM.

You will have to regenerate the loading class after implementing ow adjustments using your own exit class.

More Information
One Exposure from Operations

Integration of Accounting Documents

Integration of Bank Statements

 Note

This is custom documentation. For more information, please visit the SAP Help Portal 100
2/24/2024
One Exposure from Operations generates actual cash ows for bank statements that are imported with no posting. If bank statements are imported with FI document
posting, the Flow Builder generates actual cash ows based on the FI document and also clears the ows in One Exposure from Operations.

Materials Management in One Exposure from Operations

Integration of Promise to Pay

Promise to Pay integrates into One Exposure from Operations.

Use
With the Promise to Pay (from Collections Management) integration, you can now get an updated forecasted cash ows whenever there's the creation of promise to pay document
against customer invoice and the updates of its follow-up activity.

In this integration scenario, the source application Promise to Pay and One Exposure from Operations run in the same system (one-system scenario). Forecasted cash contains the
following information from Promise to Pay:

Account Assignments

Account assignments are inherited from customer invoice against which the promise to pay document is created.

Certainty Level

One Exposure from Operations derives cash forecasts for items representing promise to pay. It stores this information with the certainty level FIP2P.

Flow Type

The system uses the following ow type for forecast cash in One Exposure from Operations:

Default Flow Types

900900 - Incoming Forecast Cash (P2P)

Planning Group

The system uses the planning group that is de ned in the customer master data.

If errors occur during data upload, the system collects these errors in an application log. You can access it with transaction code FQM_APPLICATION_LOG.

Activities
To enable the integration, make the required data initialization that are located in the Customizing activities under Financial Supply Chain Management Cash and Liquidity
Management Cash Management :

Load Transaction Data from Source Applications into One Exposure from Operations

You use this Customizing activity to load transaction data into One Exposure from Operations. You choose the BKPF source application to load transaction data from accounting
documents (journal entries), where the corresponding customer invoice of promise to pay document is stored.

Build Cash Flows from Operations

Alternatively, you use the Flow Builder program to build ows from the existing transaction data into One Exposure from Operations. You choose the Financial Accounting source
application to build ows from accounting documents (journal entries), where the corresponding customer invoice of promise to pay document is stored.

Load Promise to Pay (from Collections Management) to One Exposure from Operations

You use the program FCLM_P2P_MIGRATE to directly integrate transaction data of promise to pay into One Exposure from Operations. You can use this program to load data that
have been created but not integrated during the initial load of One Exposure from Operations.

More Information
For more information, see Flow Builder about how the ows are built and One Exposure from Operations.

Integration of Bank Statements

Use
To help the cash manager to get an overview of the cash ow in the company, bank statements are also integrated into One Exposure when:

They are imported with the status “do not post” because they are operationally relevant to another system.

They are imported, but no posting is carried out due to problems in account determination.

They are not imported in chronological order. It is then not suﬃcient to consider only the accounting documents to determine the bank account balance.

Date and Amount

This is custom documentation. For more information, please visit the SAP Help Portal 101
2/24/2024
The transaction date and amount are determined based on the bank statement item and bank statement value date.

 Example
The following examples illustrate how information from bank statements is recorded in One Exposure:

1. A bank statement with date 24.02.2016 is imported with opening balance 1000 and closing balance 1100. The bank statement lists one item with the value date 23.02.2016.
In One Exposure the system now creates one ow with transaction date 23.02.2016, which represents the incoming bank cash of the item, and two ows with transaction
date 24.02.2016, which represent the transition from incoming bank cash to incoming con rmed bank cash.

Bank Statement

Opening Balance: 1000

Closing Balance: 1100

Date: 24.02.2016

Items:

Value Date Amount

23.02.2016 100

One Exposure

Date Flow Type Amount

23.02.2016 900014 - Incoming Bank Cash Increase +100

24.02.2016 900015 - Incoming Bank Cash Decrease -100

24.02.2016 900006 - Incoming Bank Con rmed Cash Increase +100

If errors occur during data upload, the system collects these errors in an application log. You can access it with transaction code FQM_APPLICATION_LOG .

Activities
Customizing Activities

Assign Planning Levels to Flow Types

The system lls the planning level, if the planning level is assigned to the ow types the system uses.

Bank Statement Information Default Flow Types

Bank Statement 900006 - Incoming Bank Con rmed Cash Increase

900008 - Outgoing Bank Con rmed Cash Increase

900014 - Incoming Bank Cash Increase

900015 - Incoming Bank Cash Decrease

900016 - Outgoing Bank Cash Increase

900017 - Outgoing Bank Cash Decrease

Delete Data from One Exposure from Operations Hub

More Information
Integration of Accounting Documents

One Exposure from Operations

Treasury and Risk Management in One Exposure from Operations

Use
You can integrate forecasted cash from nancial instruments into One Exposure from Operations. In this integration scenario, the source application Treasury and Risk Management
and One Exposure run in the same system (one-system scenario).

Forecasted cash contains the following information from the nancial instrument:

Reference to the business transaction and the ow in TRM

This is custom documentation. For more information, please visit the SAP Help Portal 102
2/24/2024
Company

Business Partner ( lled with the counterparty of the transaction from transaction management and with the issuer for business transactions from security account positions,
such as interests of bonds)

Speci c TRM parameters:

Product Type

Transaction Type

Transaction Activity Category

Security ID Number

Securities Account

Portfolio

Internal Reference

Characteristics

Assignment

House bank account and bank account

Date and Amount

The forecast transaction date is determined based on the transaction payment date.

The forecast transaction date is determined based on the transaction payment amount.

Certainty Level

One Exposure derives cash forecasts for items representing nancial instruments. It stores this information with the following certainty levels:

Certainty Level Description Meaning

TRM_O Optional Financial Instrument Cash forecast from an option in TRM

TRM_D Financial Instrument Cash forecast from all other TRM instruments

 Example
For example, you enter an option with an underlying foreign exchange transaction. The forecasted cash ows for the foreign exchange transaction have certainty level TRM_O.
After the option is exercised, the forecasted cash of the foreign exchange transaction has certainty level TRM_D.

Flow Type

The system uses the following ow types for forecasts in One Exposure:

Default Flow Types

900100 - Incoming Bank Cash (TRM)

900101 - Outgoing Bank Cash (TRM)

Planning Group

If the cash ow from TRM has no house bank account, the system tries to determine a planning group instead. To do so, it takes the business partner (for example the counterparty in
a money market transaction), reads the corresponding customer (from database table CVI_CUST_LINK), and takes the planning group from the corresponding company-code-
dependent data (database table KNB1). If no customer exists for this business partner, or if the customer has no planning group assigned to the given company code, the cash ow is
updated with an empty planning group. The planning group is then also empty in cash management.

Activities
Customizing Activities

Activate Individual Source Applications and Activate Multiple Source Applications

You can activate the source application TRM - Treasury and Risk Management in this Customizing activity. Data coming from TRM is only updated in One Exposure if the
application is activated and successfully initialized.

De ne Queries for Liquidity Item Derivation

This oﬀers the possibility to enter derivation rules for data coming from Treasury and Risk Management. The liquidity item derivation is based on a subset of information
available in One Exposure (origin X).

For Foreign Exchange Transactions (product category 600), Foreign Exchange Options (product category 760), and Money Market Transactions (product categories 510 - 550),
you can use the following ow types to derive separate liquidity items for purchase side, sale side, investment, repayment, interests, and fees.

You use the following ow types for product categories 600 and 760:

200200 - Increase FX Forward Purchase

This is custom documentation. For more information, please visit the SAP Help Portal 103
2/24/2024
200201 - Increase FX Forward Sale

200010 - Fee Receivable

200011 - Fee Payable

You use the following ow types for product categories 510 - 550:

201000 - Fin. Instrument Receivable

201001 - Fin. Instrument Payable

200100 - Increase Investment

200101 - Increase Borrowing

200020 - Interest Receivable Increase

200021 - Interest Payable Increase

200010 - Fee Receivable

200011 - Fee Payable

For all other product categories you use the ow types 900100 and 900101 to de ne queries for liquidity item derivation.

If no liquidity item can be determined, the system updates the ow with an empty liquidity item.

BAdI: TRM Integration into One Exposure

You can use this BAdI to derive a liquidity item based on additional TRM-speci c parameters if the source elds are not suﬃcient for a thorough liquidity item derivation. You
can also use this BAdI to overwrite ow types in One Exposure that originate from the source application TRM.

Assign Planning Levels

You can de ne the planning level for TRM by using this Customizing activity: Treasury and Risk Management Transaction Manager General Settings Link to Cash
Management Assign Planning Levels

Customers upgrading from the classic cash management can use the existing settings for the planning level when integrating TRM into One Exposure.

Load Transaction Data from Source Applications into One Exposure from Operations Hub

If you want to integrate transaction data that had already been created before the source application Treasury and Risk Management was activated, you use this Customizing
activity.

Delete Data from One Exposure from Operations Hub

If you want to use a new starting point within an implementation project, you can use this Customizing activity to delete all existing data or the source application TRM from
One Exposure. You do this for each company code and source application.

More Information
The information is then consumed by cash management apps, such as:

Cash Flow Analyzer

Check Cash Flow Items

For further information, see One Exposure from Operations

Consumer and Mortgage Loans in One Exposure from Operations

Use
You can integrate forecasted cash from consumer and mortgage loans into One Exposure from Operations. In this integration scenario, the source application Consumer and
Mortgage Loans and One Exposure from Operations run in the same system (one-system scenario).

Forecasted cash contains the following information from CML:

Reference to the contract and ow in CML

Account Assignments:

Business Area

Company

Business Partner ( lled with main loan partner if the partner also exists in the role customer)

Product Type

House bank account and bank account

Certainty Level

One Exposure derives cash forecasts for items representing CML. It stores this information with the certainty level TRM_D.

This is custom documentation. For more information, please visit the SAP Help Portal 104
2/24/2024
Flow Type

The system uses the following ow types for forecasts in One Exposure:

Default Flow Types

900104 - Incoming Bank Cash (CML)

900105 - Outgoing Bank Cash (CML)

Planning Group

The system determines the planning group from the loan partner if the partner also exists in the role customer

Activities
Customizing Activities

Activate Individual Source Applications and Activate Multiple Source Applications

You can activate the source application CML - Consumer and Mortgage Loans in this Customizing activity. Data coming from CML is only updated in One Exposure if the
application is activated and initialized successfully.

De ne Queries for Liquidity Item Derivation

This oﬀers you the possibility to enter derivation rules for data coming from Consumer and Mortgage Loans. The liquidity item can be determined, the system updates the
ow with an empty liquidity item.

The liquidity item derivation is based on a subset of information available in One Exposure (origin X).

Assign Planning Levels

You can de ne the planning level for CML in the customizing activity SAP Banking Loans Management Transaction Management Assign Planning Levels

Customers upgrading from the classic cash management can use the existing settings for the planning level when integrating CML into One Exposure.

Load Transaction Data from Source Applications into One Exposure from Operations Hub

If you want to integrate transaction data that had already been created before the source application Consumer and Mortgage Loans was activated, you use this Customizing
activity.

Delete Data from One Exposure from Operations Hub

If you want to use a new starting point within an implementation project, you can use this Customizing activity to delete all existing data or the source application CML from
One Exposure. You do this for each company code and source application.

More Information
The information is then consumed by cash management apps, such as:

Cash Flow Analyzer

Check Cash Flow Items

For further information, see One Exposure from Operations

Contract Accounts Receivable and Payable (FI-CA) in One Exposure

Use
You can integrate forecasted cash from contract accounts receivable and payable into One Exposure from Operations. In this integration scenario, the source application Contract
Accounts Receivable and Payable and One Exposure run in the same system (one-system scenario).

Forecasted cash contains the following information from FI-CA:

Account Assignments:

Business Area

Company

 Note
Compared to other source applications, One Exposure does not contain any reference to the documents in FI-CA. The upload to One Exposure is done on a summary level (for each
company code, transaction currency, transaction date, planning level, planning group, or G/L account)

Certainty Level

One Exposure derives cash forecasts for items representing contract accounts receivable and payable. It stores this information with the certainty level FICA.

Flow Type

This is custom documentation. For more information, please visit the SAP Help Portal 105
2/24/2024
The system uses the following ow types for forecast in One Exposure:

Default Flow Types

900106 - Incoming Bank Cash (FI-CA)

900107 - Outgoing Bank Cash (FI-CA)

Planning Group

The system uses the planning group that is de ned in the section general data of the contract account.

If errors occur during data upload, the system collects these errors in an application log. You can access it with transaction code FQM_APPLICATION_LOG .

Activities
Customizing Activities

Activate Individual Source Applications and Activate Multiple Source Applications

You can activate the source application FICA - Contract Accounts Receivable and Payable in this Customizing activity. Data coming from FICA is only updated in One
Exposure if the application is activated and initialized successfully.

 Note
The source application FICA - Contract Accounts Receivable and Payable is only available for activation if the software component FI-CA is installed.

De ne Queries for Liquidity Item Derivation

It oﬀers the possibility to enter derivation rules for data coming from Contract Accounts Receivable and Payable. The liquidity item derivation is based on a subset of
information available in One Exposure (origin X).

If no liquidity item can be determined, the system updates the ow with an empty liquidity item.

 Note
As mentioned above, please keep in mind that the data coming from FICA is uploaded to One Exposure on a summary level.

De ne Alternative Planning Levels for Locks and De ne Alternative Planning Levels for Transactions

Planning Levels are determined either on the basis of the planning group ( Financial Supply Chain Management Cash and Liquidity Management Cash Management
Planning Levels and Planning Groups De ne Planning Groups ) or on the basis of the company-code-dependent data of the G/L account (SKB1-FDLEV). With these two
Customizing activities, however, you can determine a planning level on a more detailed basis (both are available in Financial Accounting (New) Contract Accounts
Receivable and Payable Integration Cash Management ).

Customers upgrading from the classic cash management can use the existing settings for the planning level when integrating FI-CA into One Exposure.

Load Transaction Data from Source Applications into One Exposure from Operations Hub

If you want to integrate transaction data that had already been created before the source application Contract Accounts Receivable and Payable was activated, you use this
Customizing activity.

Delete Data from One Exposure from Operations Hub

If you want to use a new starting point within an implementation project, you can use this Customizing activity to delete all existing data or the source application FI-CA from
One Exposure. You do this for each company code and source application.

More Information
The information is then consumed by cash management apps, such as:

Cash Flow Analyzer

Check Cash Flow Items

For further information, see One Exposure from Operations

Sales and Distribution in One Exposure from Operations

Use
You can integrate forecasted cash from sales order items and scheduling agreement items into One Exposure from Operations. Creating sales orders or scheduling agreements leads
to forecasted cash that is adjusted by subsequent billing processes. In this integration scenario, the source application Sales and Distribution and One Exposure run in the same
system (one-system scenario).

The following business processes in Sales and Distribution can be integrated into One Exposure:

Sales Orders and Scheduling Agreements with the following:

Price and quantity changes

Billing plans (periodic and milestone billing) including

This is custom documentation. For more information, please visit the SAP Help Portal 106
2/24/2024
Invoice and down payment items

Down payment requests and down payments

Consignment-, third party-, rush- and cross-company sales orders

Billing with the following:

Order-related invoice

Delivery-related invoice

Invoice splits

Separate invoices

Collective invoices

Invoices according to an invoice calendar

Credit/debit memo

Complaints with the following:

Returns

Credit/debit memo requests

Invoice correction requests

 Note
Scheduling agreements with release are not incorporated.

Forecasted cash contains the following information from the sales document:

Reference to Sales Document and item of the Sales Document

Account Assignments:

Business Area

Pro t Center

Cost Center

WBS Element or a Project

Segment

Company

Material

Business Partner ( lled with the payer of the sales order or scheduling agreement)

Date and Amount

The transaction date is determined based on the expected billing date or dates of the item of the sales order or scheduling agreement, and considers the payment terms of the sales
order or scheduling agreement. Regarding cash discount, the system uses the latest possible date to get the maximum possible cash discount (independent of anything else, for
example, payment history of the customer).

The system creates two separate ows; one for the forecasted cash from the net amount of an item, and one for the forecasted cash of the tax amount of an item.

Other condition types such as cash discount, freight, or other discounts are not shown separately. They are merged in the forecasted cash for the net amount. Regarding cash
discount, the system calculates the cash forecast amount with the maximum possible cash discount (on the corresponding date from the payment terms).

Certainty Level

One Exposure derives cash forecasts for items representing sales orders and scheduling agreements. It stores this information with the following certainty levels:

Certainty Level Description Meaning

SDSO Sales Order Cash forecast from sales orders

SDSA Sales Scheduling Agreement Cash forecast from scheduling agreements

Flow Type

The system uses the following ow types for forecasts in One Exposure:

Cash Default Flow Types

Cash forecast of a net amount 900000 - Incoming Bank Cash

900001 - Outgoing Bank Cash

This is custom documentation. For more information, please visit the SAP Help Portal 107
2/24/2024

Cash Default Flow Types

Cash forecast of a tax amount 900018 - Incoming Bank Cash (Tax)

900019 - Outgoing Bank Cash (Tax)

If errors occur during data upload, the system collects these errors in an application log. You can access it with transaction code FQM_APPLICATION_LOG .

Planning Group

The system uses the planning group that is de ned in the company code section of the master data of the payer of the sales order or scheduling agreement. If the master data of the
payer does not contain the company code section, the system uses the planning group from the Customizing activity De ne Planning Levels for Logistics.

Activities
Customizing Activities

Activate Individual Source Applications and Activate Multiple Source Applications

You can activate the source application SDCM - Sales and Distribution (CM) in this Customizing activity. Data coming from SD is only updated in One Exposure, if the
application is activated and successfully initialized.

De ne Queries for Liquidity Item Derivation

This oﬀers the possibility to enter derivation rules for data coming from Sales and Distribution. The liquidity item derivation is based on a subset of information available in
One Exposure (origin X).

 Note
It is possible to derive separate liquidity items for forecasted cash from net amount and forecasted cash from tax amount based on the ow type.

If no liquidity item can be determined, the system updates the ow with an empty liquidity item.

De ne Planning Levels for Logistics

You can de ne the planning level for Sales and Distribution with this Customizing activity. The system takes the planning level that is assigned to the internal ID 101 - Order

Customers upgrading from the classic cash management can use the existing settings for the planning level when integrating SD into One Exposure.

Load Transaction Data from Source Applications into One Exposure from Operations Hub

If you want to integrate transaction data that was already created before the source application Sales and Distribution (SDCM) was activated, you use this Customizing
activity.

Delete Data from One Exposure from Operations Hub

If you want to use a new starting point within an implementation project, you can use this Customizing activity to delete all existing data or the source application SDCM from
One Exposure. You do this for each company code and source application.

Eﬀects on Data Transfer

If cash forecasts from the obsolete source application SDSO - Sales Orders exist in One Exposure, users have to delete this data by using the report
FQM_DELETE_OBSOLETE_SO_ENTRIES.

More Information
The information is then consumed by cash management apps, such as:

Cash Flow Analyzer

Check Cash Flow Items

For further information, see One Exposure from Operations

Materials Management in One Exposure from Operations

Use
You can integrate forecasted cash from materials management into One Exposure from Operations. Creating purchase requisition, purchase orders or scheduling agreements leads
to forecasted cash that is adjusted by subsequent invoicing processes. In this integration scenario, the source application Materials Management and One Exposure from Operations
run in the same system (one-system scenario).

The following business processes in Materials Management can be integrated into One Exposure:

Purchase requisition, purchase orders and scheduling agreements with the following:

Purchase requisition release

Price and quantity changes

Invoicing plans

This is custom documentation. For more information, please visit the SAP Help Portal 108
2/24/2024
Down payment requests and down payments

Multiple account assignment and delivery schedule

Consignment-, third party-, rush- and cross-company purchase orders

Service purchase order and its follow-up activities

Follow-up activities with the following:

Goods receipt

Invoice receipt

Purchase order with returned goods

Cross-company code purchase order

Forecasted cash contains the following information from the materials management document:

Reference to Materials Management and the items of Materials Management

Account Assignments:

Currency

Transaction Date

Business Area

Liquidity Item

Pro t Center

Cost Center

WBS Element or a Project

Segment

G/L Account

Date and Amount

The forecasted payment date is determined based on the following:

Statistical delivery date that is de ned in delivery schedule

Invoicing date that is de ned in invoicing plan

Posting date of goods receipt if it is complete delivery, but the delivery quantity is over or under order quantity

Payment terms of the purchase order or scheduling agreement, and vendor master data of purchase requisition

Cash discount

The system creates two separate ows; one for the forecasted cash from the net amount of an item, and one for the forecasted cash of the tax amount of an item.

Net amount of purchase requisition, purchase order and scheduling agreement

Invoice amount that is de ned in invoicing plan

Condition in payment terms

Amount of invoice veri cation is deducted from forecasted amount of purchase order

Down payment and down payment request is deducted from forecasted amount of purchase order

For scheduling agreement, only amount de ned in delivery schedule is taken into account.

Other condition types, such as non-deductible input tax, are also considered.

Certainty Level

One Exposure derives cash forecasts for items representing purchase requisition and purchase orders and scheduling agreements. It stores this information with the following
certainty levels:

Certainty Level Description Meaning

MMPR Purchase Requisition Cash forecast from purchase requisition

MMPO Purchase Orders or Scheduling Agreement Cash forecast from purchase orders or scheduling agreements

Flow Type

The system uses the following ow types for forecasts in One Exposure:

Cash Default Flow Types

This is custom documentation. For more information, please visit the SAP Help Portal 109
2/24/2024

Cash Default Flow Types

Cash forecast of a net amount 900000 - Incoming Bank Cash

900001 - Outgoing Bank Cash

For more information, see Flow Types.

Planning Group

The system uses the planning group that is de ned in the company code section of the master data of the supplier:

If planning group is not de ned, the system uses the planning group from the Customizing activity De ne Planning Levels for Logistics.

Planning Level

The system uses the planning level from the Customizing activity De ne Planning Levels for Logistics. For more information, see Planning Levels and Planning Groups.

Liquidity Item

The liquidity item derivation is based on query sequence (origin X), which is determined in the Customizing activity Customize the Flow Builder. For more information, see Liquidity
Items and Liquidity Item Hierarchies and Flow Builder.

Activities
IMG Customizing Activities

Activate Individual Source Applications and Activate Multiple Source Applications

You can activate the source application Materials Management (MM) in this Customizing activity. Data coming from MM is only updated in One Exposure, if the application is
activated and successfully initialized.

Build Cash Flows from Operations

You can derive cash ows in this Customizing activity. Data coming from MM is only updated in One Exposure, if the application is activated and successfully initialized.

For more information, see Flow Builder.

Customize the Flow Builder

This oﬀers you the possibility to enter derivation rules for data coming from Materials Management.

For more information, see Flow Builder.

More Information
The information is then consumed by cash management apps, such as:

Cash Flow Analyzer

Check Cash Flow Items

For further information, see One Exposure from Operations

Flow Builder

Use
Overview

The Flow Builder generates cash ows detailing current amounts and dates of liquidity items by:

Tracing the original document line items from the related Financial Accounting (FI) and Materials Management (MM) tables.

Generating cash ows, according to the remaining offsetting items that are not cleared in the source (original) document. Each cash ow is split according to the offsetting
items in the subsequent documents and the account assignment as inherited from the offsetting items in the source (original) document.

Process

This is custom documentation. For more information, please visit the SAP Help Portal 110
2/24/2024

Figure 1. How Flow Builder works

Example

Figure 2. An Example of Document Chain Analysis

This is custom documentation. For more information, please visit the SAP Help Portal 111
2/24/2024
Prerequisites
IMG Customizing Activities

To use the Flow Builder, make the required settings in Customizing under Financial Supply Chain Management Cash and Liquidity Management Cash Management :

Flow Types

Flow types classify the lifecycle of cash ows. Each ow type is assigned to an SAP-de ned ow category. Flow type and ow level are used to diﬀerentiate document line items.

For FI documents, ow types must be de ned and uploaded to line items in table BSEG.

For MM documents, ow types are generated in One Exposure from Operations.

For more information, see Flow Types.

Liquidity Items

Liquidity items is a customer-de ned attribute for categorizing the source and use of cash ows. It serves as an analytical dimension in cash ow statements and forecast reports.

For FI documents, liquidity items are uploaded to line items in table BSEG.

For more information, see Liquidity Items and Liquidity Item Hierarchies.

Activate Individual Source Applications and Activate Multiple Source Applications under Data Setup

You can activate the source applications for Financial Operations (FI and BKPF) and Materials Management (MM) for cash ows corresponding to speci c company codes.

For more information, see Integration with Source Applications in the Central System.

Flow Builder (FCLM_FLOW_BUILDER)

In the Delta Run mode, ows are built automatically as the back-end job of the program is triggered after online posting of FI documents.

In the Mass Run mode, however, ows are built manually with certain search criteria, such as company code, scal year, document number, and line item. As an example, in the
case of an initialization and ow rebuild, you would want to use the Mass Run mode instead of the Delta Run mode.

 Note
For MM documents, the selection criteria diﬀers according to diﬀerent data sources:

For purchase orders (PO) and scheduling agreements, you can select company code, scal year, document number and line Item.

For purchase requisitions (PR), you can select from several criteria, such as purchase requisitions, item of requisitions, document type, and so on.

Flow Builder also allows you to perform the following activities:

Maximum Steps of Chain Tracing

You can de ne the maximum steps in a document chain trace. For example, if you choose one step of chain tracing, you nd the document ow with one preceding document
and one subsequent document.

Merge Tax Items

Settings and Tools (FCLM_FB_UTIL )

You can run this transaction in two ways, either by running the Settings and Tools or by using the customizing activity Customize the Flow Builder.

With this transaction, you can perform the following activities:

Schedule Background Job

Check Background Job Logs

This is custom documentation. For more information, please visit the SAP Help Portal 112
2/24/2024
You use this setting to check the status of the back-end jobs. This activity is automatically triggered by online posting. By de ning the User Name and Job Name, you can
check the job status released, ready, active, nished, and canceled) within a time frame that you de ne.

Delete Flows

This tool allows you to de ne speci c search criteria to search for and delete ows from target tables.

Change Default Loading Classes

Generate Loading Classes

You use this tool to generate loading classes, by specifying Package, Exit Class and Loading Class Name.

FI documents require a Date. By default, the date is determined by the planning date for forecasting cash ows from invoices. For more information, see SAP
Note 2273656 .

Assign Loading Classes

You use this tool to assign loading classes to the Flow Builder. Changes in the loading class is updated to the Flow Builder program.

Extensibility

For FI documents, you can use the example exit class CL_FCLM_APAR_HADI_SAMPLE. The standard ABAP interface is IF_FCLM_HADI_APAR.

You will have to regenerate the loading class after implementing ow adjustments using your own exit class.

More Information
One Exposure from Operations

Integration of Accounting Documents

Integration of Bank Statements

 Note
One Exposure from Operations generates actual cash ows for bank statements that are imported with no posting. If bank statements are imported with FI document
posting, the Flow Builder generates actual cash ows based on the FI document and also clears the ows in One Exposure from Operations.

Materials Management in One Exposure from Operations

Classic Cash Management in One Exposure from Operations

Use
You can integrate forecasted cash from classic cash management into One Exposure from Operations. In this integration scenario, classic cash management and One Exposure from
Operations run in diﬀerent systems (side-by-side scenario).

Forecasted cash contains the following information from classic cash management:

Reference to the IDoc and the segment of the IDoc

Account Assignment:

Company

Business Area

Planning Level and Planning Group

Certainty Level

One Exposure derives cash forecasts for items representing distributed cash. It stores this information with the certainty levels ACTUAL and CMIDOC.

If the ow types 900108 – Cash Balance Increase (IDoc) or 900109 – Cash Balance Decrease (IDoc) are assigned to dedicated planning levels in the Customizing activity Assign
Flow Types to Planning Levels, the system derives certainty level ACTUAL for these ows.

Flow Type

The system uses the following ow types for forecasts in One Exposure:

This is custom documentation. For more information, please visit the SAP Help Portal 113
2/24/2024

Default Flow Types Flow Types Available for Con guration

900110 – Incoming Cash (IDoc) 900108 – Cash Balance Increase (IDoc)

900111 – Outgoing Cash (IDoc) 900109 – Cash Balance Decrease (IDoc)

If errors occur during data upload, you can analyze the messages in the central system using transaction FF$S – Transmission Status.

Prerequisites
You need to con gure the usage of IDocs in the central and the remote system. In addition, you de ne the distribution model in the central system using message types CMSENDand
CMREQU. For more details see Integration with Remote Systems.

To derive a Bank account, you must maintain connectivity path information for remote bank accounts in the bank account master data of the activity Manage Bank Accounts in the
central system. There, you need to ll the ID category eld with Remote System: G/L Account, and enter the company code and G/L account from the remote system.

Activities
Customizing Activities

You perform the following Customizing activities in the central system.

Reassign Company Codes

You use this Customizing activity to convert the company codes coming from the remote system into company codes in the central system.

Convert Sender Business Areas

You use this Customizing activity to convert the business areas coming from the remote system into business areas in the central system.

Convert Sender Planning Levels

You use this Customizing activity to convert the planning levels coming from the remote system into planning levels in the central system.

Convert Sender Planning Groups

You use this Customizing activity to convert planning groups coming from the remote system into planning groups in the central system.

Assign Flow Types to Planning Levels

If you assign the ow types 900108 – Cash Balance Increase (IDoc) or 900109 – Cash Balance Decrease (IDoc) to the dedicated planning levels in this Customizing activity,
the system derives certainty level ACTUAL for these ows.

De ne Queries for Liquidity Item Derivation

This oﬀers you the possibility to enter derivation rules for data coming from classic cash management. The liquidity item derivation is based on a subset of information
available in One Exposure (origin X).

If no liquidity item can be determined, the system updates the ow with an empty liquidity item.

Delete Data from One Exposure from Operations Hub

If you want to use a new starting point within an implementation project, you can use this Customizing activity in the central system to delete all existing data or the source
application Distributed Cash from One Exposure. You do this for each company code and source application.

More Information
The information is then consumed by cash management apps, such as:

Cash Flow Analyzer

Check Cash Flow Items

For further information, see One Exposure from Operations

Manual Entry of Bank Cash Balances in One Exposure from Operations

Use
You can integrate forecasted cash from bank cash balances into One Exposure from Operations. In this integration scenario, you enter the cash balances in a Microsoft Excel sheet
and load them into One Exposure. Since you have to upload the balances manually to One Exposure (central system), this integration scenario is also a side-by-side scenario.

Cash in ows and out ows contain the following information from bank cash balance uploads:

Company

Business Partner ( lled with the bank of the bank account)

Bank Account

Certainty Level

This is custom documentation. For more information, please visit the SAP Help Portal 114
2/24/2024
One Exposure derives cash in ows and out ows for the given bank account balances. It stores this information with the certainty level ACTUAL.

Flow Type

The system uses the following ow types for the cash ows from bank cash balances in One Exposure:

Default Flow Types

900102 – Bank Cash Balance Increase

900103 – Bank Cash Balance Decrease

If errors occur during data upload, they are directly displayed in a log after executing transaction FQM21.

Prerequisites
You have to maintain connectivity path information for remote bank accounts in the bank account master data of the activity Manage Bank Accounts. There, you need to ll the ID
category eld with Remote System: House Bank Account or Remote System: G/L Account.

Activities
Customizing Activities

Assign Planning Levels to Flow Types

The system lls the planning level, if the planning level is assigned to the ow types the system uses.

De ne Queries for Liquidity Item Derivation

This oﬀers you the possibility to enter derivation rules for data coming from bank cash balances. The liquidity item derivation is based on a subset of information available in
One Exposure (origin X).

If no liquidity item can be determined, the system updates the ow with an empty liquidity item.

Load Transaction Data from Source Applications into One Exposure from Operations Hub

If you want to integrate transaction data that had already been created before the source application Bank Account Balances was activated, you use this Customizing activity.

Delete Data from One Exposure from Operations Hub

If you want to use a new starting point within an implementation project, you can use this Customizing activity to delete all existing data or the source application Bank
Account Balances from One Exposure. You do this for each company code and source application.

More Information
For further information on the import of bank cash balances, see the report documentation available in transaction FQM21.

The information are then consumed by cash management apps, such as:

Cash Flow Analyzer

Check Cash Flow Items

For further information, see One Exposure from Operations

Apps for Cash Management

This is custom documentation. For more information, please visit the SAP Help Portal 115

S4F51 - Customizations in TRM
100% (1)
S4F51 - Customizations in TRM
806 pages
SAP Enterprise Structure Concept and Configuration Guide: A Case Study
From Everand
SAP Enterprise Structure Concept and Configuration Guide: A Case Study
Ahmad Rizki
5/5 (3)
S4C30: SAP S/4HANA Cloud For Finance
0% (2)
S4C30: SAP S/4HANA Cloud For Finance
3 pages
SAP - FI Dictionary
From Everand
SAP - FI Dictionary
Shyamala Nemana
4.5/5 (5)
Key Components: 1. Bank Account Management
No ratings yet
Key Components: 1. Bank Account Management
5 pages
Cash Management With Sap S4hana
No ratings yet
Cash Management With Sap S4hana
45 pages
Learn SAP BI in 24 Hours
From Everand
Learn SAP BI in 24 Hours
Alex Nordeen
3/5 (1)
Microsoft Dynamics GP 2013 Implementation
From Everand
Microsoft Dynamics GP 2013 Implementation
Victoria Yudin
No ratings yet
SAP Cash Management On SAP S/4HANA Finance
No ratings yet
SAP Cash Management On SAP S/4HANA Finance
37 pages
Mysap Fi Fieldbook: Fi Fieldbuch Auf Der Systeme Anwendungen Und Produkte in Der Datenverarbeitung
From Everand
Mysap Fi Fieldbook: Fi Fieldbuch Auf Der Systeme Anwendungen Und Produkte in Der Datenverarbeitung
Thomas Spitters
4/5 (1)
Cash and Liquidity Management
No ratings yet
Cash and Liquidity Management
195 pages
SFIN Cash Management
100% (1)
SFIN Cash Management
20 pages
CONV_CASH_MGMT
No ratings yet
CONV_CASH_MGMT
8 pages
FI_S4HANA 1610 - Customizing for Cash Operation Management
No ratings yet
FI_S4HANA 1610 - Customizing for Cash Operation Management
29 pages
Draft 5
No ratings yet
Draft 5
5 pages
Customizing for Cash Operations 20160510
No ratings yet
Customizing for Cash Operations 20160510
28 pages
pdfdownload04
No ratings yet
pdfdownload04
240 pages
SAP ECC FI Transaction Codes: Unofficial Certification and Review Guide
From Everand
SAP ECC FI Transaction Codes: Unofficial Certification and Review Guide
Equity Press
5/5 (2)
S4 HANA Finance Content
No ratings yet
S4 HANA Finance Content
10 pages
Customizing in Cash Management in SAP S/4HANA
0% (1)
Customizing in Cash Management in SAP S/4HANA
20 pages
SAP - CashManagement-Cash Flow Analyzer
100% (1)
SAP - CashManagement-Cash Flow Analyzer
3 pages
SAP Cash Management
100% (2)
SAP Cash Management
13 pages
Copy of CPF - Cash Management Configuration Rationale
No ratings yet
Copy of CPF - Cash Management Configuration Rationale
19 pages
S Fin Int Prep
No ratings yet
S Fin Int Prep
8 pages
LC Config
No ratings yet
LC Config
22 pages
Customizing SHANA Treasury
100% (1)
Customizing SHANA Treasury
850 pages
C_S4CFI_1911.v2020-02-19.q20
No ratings yet
C_S4CFI_1911.v2020-02-19.q20
7 pages
pdfdownload03
No ratings yet
pdfdownload03
248 pages
Cash Management
No ratings yet
Cash Management
43 pages
Release Info Note Automatic Account Determ S4 Hana 1908
No ratings yet
Release Info Note Automatic Account Determ S4 Hana 1908
5 pages
SAP HANA 1909 Blog
No ratings yet
SAP HANA 1909 Blog
3 pages
2.- DATOS MAESTROS
No ratings yet
2.- DATOS MAESTROS
17 pages
S4F50 EN Col06 ILT FV CO A4
No ratings yet
S4F50 EN Col06 ILT FV CO A4
23 pages
Accounting and Financial Close: Roadmap SAP S/4HANA
No ratings yet
Accounting and Financial Close: Roadmap SAP S/4HANA
55 pages
Sap Education: Sample Questions: P - S4Fin - 1610
No ratings yet
Sap Education: Sample Questions: P - S4Fin - 1610
6 pages
SAP Introduction To Treasury Applications
100% (1)
SAP Introduction To Treasury Applications
28 pages
Sap In-House Cash Help Ecc6 Ehp8 Sp13 Part 1
33% (3)
Sap In-House Cash Help Ecc6 Ehp8 Sp13 Part 1
85 pages
Sample 1709 Questions
100% (1)
Sample 1709 Questions
4 pages
Make Bank Transfers
No ratings yet
Make Bank Transfers
4 pages
SAP SF Cash Management
No ratings yet
SAP SF Cash Management
25 pages
Real Time Treasury Episode2
No ratings yet
Real Time Treasury Episode2
21 pages
Business Processes in Treasury and Risk Management in SAP S/4HANA
No ratings yet
Business Processes in Treasury and Risk Management in SAP S/4HANA
20 pages
Accounting
No ratings yet
Accounting
242 pages
SAP S4HANA FICO
No ratings yet
SAP S4HANA FICO
24 pages
SAP.HELP_Part1
No ratings yet
SAP.HELP_Part1
230 pages
TF in SAP
No ratings yet
TF in SAP
21 pages
Intelligent Treasury For A Connected World
100% (1)
Intelligent Treasury For A Connected World
13 pages
1S2_S4CLD2308_BPD_EN_US
No ratings yet
1S2_S4CLD2308_BPD_EN_US
24 pages
Help Sap in House Cash
No ratings yet
Help Sap in House Cash
269 pages
Business Visibility with Enterprise Resource Planning
From Everand
Business Visibility with Enterprise Resource Planning
Anupama Sakhare
No ratings yet
Bank Account Management in SAP S - 4 HANA - A Master Data Perspective - SAP Blogs
No ratings yet
Bank Account Management in SAP S - 4 HANA - A Master Data Perspective - SAP Blogs
22 pages
SAP Basis Configuration Frequently Asked Questions
From Everand
SAP Basis Configuration Frequently Asked Questions
Equity Press
3.5/5 (4)
TRM, New Instruments, Accounting Enhancements, Reporting
No ratings yet
TRM, New Instruments, Accounting Enhancements, Reporting
8 pages
01
No ratings yet
01
30 pages
Classic Cash and Liquidity Management Offers Functionality To Do Cash Concentration As Followings
No ratings yet
Classic Cash and Liquidity Management Offers Functionality To Do Cash Concentration As Followings
6 pages
SAP APO Interview Questions, Answers, and Explanations: SAP APO Certification Review
From Everand
SAP APO Interview Questions, Answers, and Explanations: SAP APO Certification Review
Equity Press
2/5 (9)
Cobase_The_ultimate_guide_for_efficient_and_safe_cash_visibility
No ratings yet
Cobase_The_ultimate_guide_for_efficient_and_safe_cash_visibility
11 pages
brochure-b4b-simple-secure-global-bank-payments
No ratings yet
brochure-b4b-simple-secure-global-bank-payments
4 pages
Adv - SAP Cash and Liquidity Management A Comprehensive Guide
No ratings yet
Adv - SAP Cash and Liquidity Management A Comprehensive Guide
10 pages
TS4F01_2 Financial Accounting in SAP S/4HANA Academy Part I
No ratings yet
TS4F01_2 Financial Accounting in SAP S/4HANA Academy Part I
20 pages
IA1 CCE Part 3
No ratings yet
IA1 CCE Part 3
4 pages
Bank Statement: Lawrence Customer 10234 Anywhere Dr. Small Town, MO 12345-6789
No ratings yet
Bank Statement: Lawrence Customer 10234 Anywhere Dr. Small Town, MO 12345-6789
1 page
AP Quiz 1 (B48)
No ratings yet
AP Quiz 1 (B48)
21 pages
B1 90 BSP Processes
No ratings yet
B1 90 BSP Processes
42 pages
'ACT1204 Audit of Cash and Cash Equivalents Quiz No. 4
No ratings yet
'ACT1204 Audit of Cash and Cash Equivalents Quiz No. 4
4 pages
Fabm2 Q2 M3 - 4
No ratings yet
Fabm2 Q2 M3 - 4
9 pages
Bank Reconciliation Template
No ratings yet
Bank Reconciliation Template
4 pages
1eg S4hana2023 BPD en Sa
No ratings yet
1eg S4hana2023 BPD en Sa
32 pages
Bank Reco Paper (Recovered)
No ratings yet
Bank Reco Paper (Recovered)
4 pages
Bank Reconciliation Notes 2023
No ratings yet
Bank Reconciliation Notes 2023
7 pages
Bank Reconciliation Statement Previous Year Question
No ratings yet
Bank Reconciliation Statement Previous Year Question
6 pages
New Sea 1
No ratings yet
New Sea 1
9 pages
Chapter-3 Homework Cash
No ratings yet
Chapter-3 Homework Cash
5 pages
FAQ's of RFE Claims
No ratings yet
FAQ's of RFE Claims
9 pages
Top 70 F1 Visa Interview Questions And Answers (1)
No ratings yet
Top 70 F1 Visa Interview Questions And Answers (1)
13 pages
FIN-I-042 - FS - Prior Day Electronic Bank Statements - Interface
No ratings yet
FIN-I-042 - FS - Prior Day Electronic Bank Statements - Interface
17 pages
Chapter 5 Cash Management Cycle 2024 Part 1
No ratings yet
Chapter 5 Cash Management Cycle 2024 Part 1
44 pages
Manual 3 Federal Accounting System Chapter 11. Monthly Reports
No ratings yet
Manual 3 Federal Accounting System Chapter 11. Monthly Reports
38 pages
Aditya Birla Enach Form
No ratings yet
Aditya Birla Enach Form
2 pages
PROOF OF CASH QUIZ
No ratings yet
PROOF OF CASH QUIZ
2 pages
NEW
No ratings yet
NEW
5 pages
In The Court of The Principal City Civil & Sessions Judge at Bangalore
100% (1)
In The Court of The Principal City Civil & Sessions Judge at Bangalore
15 pages
Financial Requirements For Tier 4 May 21 28713
No ratings yet
Financial Requirements For Tier 4 May 21 28713
9 pages
A Study of The Customer - Docx Shreya - Docx 1
No ratings yet
A Study of The Customer - Docx Shreya - Docx 1
49 pages
Bank Reconciliation Sample
No ratings yet
Bank Reconciliation Sample
5 pages
FAR.2917 Bank-Reconciliation
No ratings yet
FAR.2917 Bank-Reconciliation
4 pages
DS Fusion CE _ Cash Manager Dashboards and Infolets
No ratings yet
DS Fusion CE _ Cash Manager Dashboards and Infolets
20 pages
fabm 2 lesson 9
No ratings yet
fabm 2 lesson 9
10 pages
The Cash Transactions and Cash Balances of Dodge Inc For
No ratings yet
The Cash Transactions and Cash Balances of Dodge Inc For
1 page
Engagement Letter - Bookkeeping and Tax Filing - NON VAT
100% (2)
Engagement Letter - Bookkeeping and Tax Filing - NON VAT
6 pages

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.