J78 - S4CLD2308 - BPD - EN - DE - Advance Cash Operations

Test Script
SAP S/4HANA Cloud - 06-07-23
Advanced Cash Operations (J78_DE)
PUBLIC
Table of Contents
1 Purpose
2 Prerequisites
2.1 System Access
2.2 Roles
2.3 Master Data, Organizational Data, and Other Data
2.4 Business Conditions
2.5 Additional Manual Configuration
2.6 Preliminary Steps
2.6.1 Maintain Full Scope for Cash Management
2.6.2 Enable Snapshot (Optional)
2.6.3 Liquidity Items
2.6.3.1 Define Source Application Accounting
2.6.3.2 Define Basic Settings for Liquidity Analysis
2.6.3.3 Alternative 1: Define Derivation Rules – BRF Plus
2.6.3.4 Alternative 2: Define Derivation Rules – Query Sequence
2.6.3.4.1 Define Query Sequences
2.6.3.4.2 Define Queries for Liquidity Item Derivation
2.6.3.4.3 Assign Queries to Query Sequences
2.6.3.4.4 Assign Sequence to Company Codes
2.6.3.5 Alternative 3: Define Default Liquidity Items for G/L Accounts
2.6.3.5.1 Schedule Job for Rebuild Tool for Liquidity Item
2.6.3.6 Define Liquidity Item Derivation Mode for Flow Builder
2.6.3.7 Flow Builder: Stop Condition (Optional)
2.6.3.7.1 Define Profile for Stop Condition
2.6.3.7.2 Assign Flow Builder Profile to Company Code
2.6.3.8 Manage Liquidity Items Hierarchies
2.6.3.9 Blocking Date Range for Actual Flows in Liquidity Analysis (Optional)
2.6.4 Payment Approval
2.6.4.1 Maintain Payment Approver for Bank Accounts
2.6.4.2 Specify Optional User Authentication (Optional)
2.6.4.3 Define Automatic Approval/Rejection for Bank Account Master Data
2.6.5 Define Cash Position Profile
2.6.6 Reconcile Cash Flows – Intraday Memo Records
2.6.6.1 Enable New Reconciliation Model (Optional)
2.6.6.2 Define Planning Level for Residual Forecast (Optional)
2.6.6.3 Define Memo Record Type for Residual Forecast (Optional)
2.6.6.4 Define Profiles for Cash Flow Reconciliation (Optional)
2.6.6.5 Define Tolerance Groups for Cash Flow Reconciliation
2.6.6.6 Activate Intraday Reconciliation for Bank Account
2.6.7 Cash Trade Request
2.6.7.1 Enable Cash Trade Requests
2.6.7.2 Define Planning Level for Cash Request
2.6.7.3 Assign Planning Level to Cash Request
2.6.8 Manage Reason Codes
2.6.8.1 Create Internal Reason Codes
2.6.8.2 Map External Reason Codes to Internal Reason Codes
2.6.9 Automatically Reversing Rejected Payments
2.6.9.1 Define Rules for Reversing Rejected Payments
2.6.9.2 Create Team for Reversing Rejected Payments
2.6.10 Situation Handling
2.6.10.1 Situation Handling for Cash and Liquidity Management
2.6.10.1.1 Manage Teams and Responsibilities
2.6.10.1.2 Create Situation Types: Date Difference Warning for FI Flows
2.6.10.2 Situation Handling for Bank Communication Management
2.6.10.2.1 Define Function
2.6.10.2.2 Define Function Profiles
2.6.10.2.3 Assign Function Profiles to Standard Team Category
2.6.10.2.4 Define Team Types
2.6.10.2.6 Create Situation Types: Payment Batch Partially Rejected
2.6.10.2.7 Create Situation Types: Payment Batch Was Rejected
2.6.10.2.8 Create Situation Types: Payment Batch Status Check
3 Overview Table
4 Test Procedures
4.1 Outgoing Payment with BCM Approval Process
4.1.1 Approval and Bank Integration

Appendix PUBLIC 2
4.1.1.1 BCM Batch Creation
4.1.1.2 Monitor Payments
4.1.1.3 Check Cash Flow Items (Before Approval)
4.1.1.4 Approval of Bank Transfer
4.1.1.4.1 Approval by First Approver
4.1.1.4.2 Reject by First Approver (Option)
4.1.1.4.3 Process Rejected Payments (Option)
4.1.1.4.4 Approval by Second Approver
4.1.1.5 Bank Integration with SAP Multi-Bank Connectivity (16R) (Outgoing)
4.1.1.6 Monitor Payments with SWIFT GPI Reason Codes
4.1.1.7 Situation Handling for Payment Batch
4.1.1.7.1 Situation Handling: Payment Batch Partially Rejected
4.1.1.7.2 Situation Handling: Payment Batch Was Rejected
4.1.1.7.3 Situation Handling: Payment Batch Status Check
4.1.1.8 Bank Integration with File Interface (1EG) (Outgoing)
4.1.1.9 Check Cash Flow Items (Check Status)
4.2 Bank Transfer Actions
4.2.1 Initiate Bank Transfer
4.2.1.1 Option 1: Create, Release and Clear Payment Request in One Single Action
4.2.1.2 Option 2: Create, Release, and Clear Payment Request in Separate Steps
4.2.1.2.1 Create Bank Transfer
4.2.1.2.2 Release Payment Request
4.2.1.2.3 Pay Payment Request
4.2.1.3 Option 3: Make Bank Transfer with Templates
4.2.1.3.1 Define Bank Transfer Templates
4.2.1.3.2 Create Bank Transfers with Templates
4.2.2 Approve and Bank Integration
4.2.3 Check Cash Position (Smart Business)
4.3 Cash Trade Request
4.3.1 Create and Submit Cash Trade Request for FX
4.3.2 Create and Submit Cash Trade Request for Money Market
4.3.3 Release Cash Trade Request
4.3.4 Reject Cash Trade Request (Optional)
4.3.5 Treasury Management Integration for Trading Platform
4.3.6 Fulfill Cash Trade Request as Deal Done
4.3.7 Cancel Cash Trade Request as Deal Cancel
4.3.8 Check Partial Fulfill or Partial Decline Cash Trade Request Status
4.4 Reconcile Cash Flows - Intraday Memo Records (Old Reconciliation Model)
4.4.1 Schedule Intraday Memo Records Reconciliation
4.4.2 Check Automatic Reconciliation Result
4.4.3 Perform Manual Reconciliation
4.4.4 Undo Reconciliation

Appendix PUBLIC 3
4.5 Reconcile Cash Flows - Intraday (New Reconciliation Model)
4.6 Manage Bank Account Balances
4.6.1 Create Bank Account Balances
4.6.2 Import Bank Account Balances
4.6.3 Edit Bank Account Balances
4.6.4 Check Bank Account Balances
4.7 Manage Liquidity Item Transfer
4.8 Situation Handling: Date Difference Warning for FI Flows
4.8.1 Monitor Situations
4.8.2 Check Notification
4.9 Cash Reports
4.9.2 Check Liquidity Items on G/L Accounts
4.9.3 Check Cash Flow Items
4.9.4 Schedule Jobs for Bank Statement Monitor
4.9.5 Bank Statement Monitor
4.9.6 Intraday Bank Statement Monitor
4.9.6.1 Define Monitoring Rules for Intraday Bank Statement Monitor
4.9.6.2 Assign Monitoring Rule to Bank (Optional)
4.9.6.3 Define Bank Account to Monitor
4.9.6.4 Monitor Intraday Bank Statement
4.9.7 Monitor Bank Account Balances
4.9.8 Schedule Jobs for Bank Account Balance Initialization
4.9.9 Short Term Cash Positioning
4.9.10 Cash Flow Analyzer
4.9.11 Cash Flow Comparison – By Date Range
4.9.12 Cash Flow Comparison – By Timestamp
4.10 Display Status of Payment Documents
5 Appendix
5.1 Process Chains

Appendix PUBLIC 4
1 Purpose
Overview
With Advanced Cash Operations you can get a consistent view for the actual cash position as well as the short/mid-term cash forecast. Drill-down features are provided for the detailed transactions
and rich dimensions are provided for the analysis. A comparison view between the actual and forecasted cash flow is also available.
This scope item also allows you to make bank transfer and track its status, and to approve the bank payments and monitor the payment processing status.
Caution All of the procedures are only required if you have adopted Cash Management Full, which requires an additional license for SAP Cash Management powered by SAP HANA. If you use
Basic Cash Management, skip all steps in this document.
This document provides a detailed procedure for testing this scope item after solution activation, reflecting the predefined scope of the solution. Each process step, report, or item is covered in its
own section, providing the system interactions (test steps) in a table view. Steps that are not in scope of the process but are needed for testing are marked accordingly. Project-specific steps must be
added.
Note Values in this test script (decimal notation, date formats, and so on) are presented in U.S. standard notation. If your test system is set up to use a different notation, enter values as appropri-
ate.

Appendix PUBLIC 5
2 Prerequisites
This section summarizes all the prerequisites for conducting the test in terms of systems, users, master data, organizational data, other test data and business conditions.
Caution Testing in a 3-System Landscape

In a 3-system landscape (with SAP Central Business Configuration as your configuration environment), changes to software and business configuration are applied to your systems indepen-
dently of one another. It is therefore your responsibility to manage the active business configuration in your systems and synchronize configuration data in your SAP S/4HANA Cloud system
landscape. A synchronization is required, for example, after you've enhanced the scope, extended configuration, or adopted new or changed content from content updates or upgrades. For more
information, refer to the product assistance in the SAP Help Portal.
Before testing, if you want to use all software features described for the process steps, reports, or items in this document, we recommend the Business Process Configuration Expert in your or-
ganization has upgraded the configuration content and deployed the configuration data to your system landscape.
If the decision is not to upgrade the configuration content in your test or production system, you can run regression tests of software changes using the procedures in the previous test script ver-
sion (see the following link ).
2.1 System Access
System Details
System Accessible via SAP Fiori launchpad. Your system administrator provides you with the URL to access the various apps assigned to your role.
2.2 Roles
Create business roles using the following business role templates delivered by SAP and assign them to your individual test users.
Alternatively, if available, you can use the following spaces delivered by SAP. You create a space with pages containing predefined essential apps and assign it to the business role. You then assign
this business role to your individual users.
For more information, refer to How to Create a Business Role from a Template in the product assistance for SAP S/4HANA Cloud.
Name (Role ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log on
Template)
Cash Man- SAP_BR_CASH_MAN- Cash Manager SAP_BR_CASH_MANAGER Suggested sample user

ager AGER CASH_MANAGER repre-
senting the business role
Cash Manager.

Appendix PUBLIC 6
Name (Role ID (Role Template) Name (Launchpad Space) ID (Launchpad Space) Log on
Template)
Cash Man- SAP_BR_CASH_SPE- Cash Management Specialist SAP_BR_CASH_SPECIALIST Suggested sample user
agement Spe- CIALIST CASH_SPECIALIST repre-
cialist senting the business role
Cash Management Special-
ist.
Accounts SAP_BR_AP_AC- Accounts Payable Accountant / Central Invoice Management - Sup- SAP_BR_AP_ACCOUNTANT / SAP_MM_SPT_CIM_INV_PC / Suggested sample user
Payable Ac- COUNTANT plier Invoices / Central Invoicing - Supplier Invoice SAP_MM_SPT_CNTRL_INVOICING_PC AP_ACCOUNTANT repre-
countant senting the business role Ac-
count Payable Accountant.
Accounts Re- SAP_BR_AR_AC- Accounts Receivable Accountant SAP_BR_AR_ACCOUNTANT Suggested sample user
ceivable Ac- COUNTANT AR_ACCOUNTANT repre-
countant senting the business role Ac-
counts Receivable Accoun-
tant.
Accounts SAP_BR_AP_MAN- Accounts Payable Manager SAP_BR_AP_MANAGER Suggested sample user

Payable AGER AP_MANAGER represent-
Manager ing the business role Ac-
counts Payable Manager.
Configura- SAP_BR_BPC_EX- Configuration Expert - Business Process Configuration / Business SAP_BR_BPC_EXPERT / SAP_CA_SPT_BPC_FM_PC / Suggested sample user
tion Expert - PERT Configuration - Feature Management / BPC Expert Workflow Space SAP_CA_SPT_BPC_WORKFLOW_PC / BPC_EXPERT representing
Business / Business Process Configuration – Manage your Solution / Business SAP_CA_SPT_IC_LND_BASE_PC / SAP_EI_SPT_BPC_EXT_PC / the business role Configura-
Process Con- Process Configuration - Extensibility Explorer / Business Process SAP_FIN_SPT_BPC_EXPERT_PC / tion Expert - Business
figuration Configuration – Finance / Materials Management - Business Process SAP_MM_SPT_BIZ_PROC_CONFIGN_PC / Process Configuration.
Configuration / Transportation Business Process Configuration SAP_TM_SPT_TRANSPCFG_PC
Note During testing, Cash Manager and Accounts Payables Manager should be separate user IDs, they are used as different approvers in payment approval, for details see sections Maintain
Payment Approver for Bank Accounts and Approval of Bank Transfer.
2.3 Master Data, Organizational Data, and Other Data

Default Values
The organizational structure and master data of your company have been created in your system during activation. The organizational structure reflects the structure of your company. Depending on
the operational focus of your company, the master data represents materials, customers, and vendors.
Use your own master data or the following sample data to go through the test procedure.
The business process is enabled with this organization-specific master data, examples are provided in the next section.
Operational Focus

Appendix PUBLIC 7
SAP Best Practices deliver standard values for more than one operational focus area, such as Services, Manufacturing, or Trade. This means that you may find more than one master data table. Use
the master data that matches the operational focus of your company (Services, Manufacturing, or Trade).
Note Additional Default Values

You can test the scope item with other SAP Best Practices default values that have the same characteristics.
Check your SAP ECC system to find out which other material master data exists.
Note Using Your Own Master Data

You can also use customized values for any material or organizational data for which you have created master data. For more information on how to create master data, see the Master Data Pro-
cedures documentation.
Use the following master data in the process steps described in this document:
Data Sample Value Details Comments
Bank Key 50070010 ,82080000 Bank key
Country DE Country of bank key
Company Code 1010 Company code
G/L Account 11001000, 11001020,11001080, and so on G/L account for bank accounts
Chart of Accounts YCOA Chart of accounts
House Bank DEBK1 House bank

DEBK2
House Bank Account DEAC1 House bank account is integrated in Bank account master data (BAM)
DEAC2
For more information on creating these master data objects, see the following Master Data Scripts (MDS) Scripts (MDS):
Table 1: Master Data Script Reference
Master Data Script ID Description
BNG Create G/L Account and Cost Element
2.4 Business Conditions

Before this test script can be tested, the following business conditions must be met.

Appendix PUBLIC 8
Scope Item Business Condition
J60 - Accounts Perform the relevant steps of payment run to vendors in the Accounts Payable (J60) test script. This is the prerequisite for the Outgoing Payment with BCM Approval Process section in this test
Payable script.
2.5 Additional Manual Configuration

You have the option to enable two-factor authentication for the Approve Bank Payments app. If you enable two-factor authentication in the preliminary step Specify Optional User Authentication,
you should completed the additional configuration steps that are described in the Set-Up Instructions for this scope item. These configuration steps are specific for your implementation and include
mandatory settings that are not delivered by SAP and must be created by you.
For more information, follow the link to the document:
Link to Set-Up Instructions
2.6 Preliminary Steps
2.6.1 Maintain Full Scope for Cash Management
Use
In this activity, you maintain Full Scope for cash management.
Procedure
Depending on your configuration environment for SAP S/4HANA Cloud, choose one of the following options:
Configure Your Solution:
Test Step Test Step Name Instruction Expected Result Pass / Fail / Com-
# ment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configura-
tion.

Appendix PUBLIC 9
# ment
2 Access the SAP Fiori Open Manage Your Solution (F1241).

App
3 Configure Choose Configure Your Solution. The Configure Your Solution: Realize Phase view displays.
4 Filter List Make the following entries: A list of Configuration Items display with the filter criteria.
Application Area: Finance
Sub Application Area: Cash and Liquidity Management
5 Select General Settings Select the following row: The Configure Your Solution - General Settings view displays.
Item Name: General Settings
6 Define Basic Settings From the Configuration Steps area, on the Define Basic Settings step, choose Configure. The Change View "Define Basic Settings": Details view dis-
plays.
7 Select Full Scope Make the following entries and choose Save.
Cash Scope: Full Scope
SAP Central Business Configuration:
Test Test Step Name Instruction Expected Result Pass / Fail /

Step # Comment
1 Log on Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launch-
pad displays.
2 Open General Settings for In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree view,
Cash Management search for the following activity: General Settings for Cash Management.
Choose Open Documentation for the found line item to see more details about this configuration activity.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configuration Ex-
pert - Business Process Configuration.
3 Select Full Scope Make the following entries and choose Save.
Cash Scope: Full Scope

Appendix PUBLIC 10
Remember Basic Settings must be reviewed following any system upgrade or improvement before continuing any business operation in the system. When differences are found from previous ac-
tivations, you must correct them in the SSCUI Define Basic Settings.
2.6.2 Enable Snapshot (Optional)
Use
In this activity, you enable the snapshot feature. The snapshot feature allows the cash manager to see a past date cash position or forecast when testing the Check Cash Flow Items and Cash Flow An-
alyzer procedures. The difference between historical view and actual view can be analyzed and the cash flow forecast can be improved.
Caution If Basic Scope is adopted, enabling Snapshot produces an error.
Caution If you enable Snapshot, it will consume quite a big database space. Please enable Snapshot only if it’s really needed. You can use the app Delete Data from One Exposure and choose
Snapshot Cleanup to remove the old snapshot records.
Procedure
# ment
tion.

App
5 Select General Settings Select the following row: The Configure Your Solution - General Settings view displays.

Appendix PUBLIC 11
# ment
6 Define Basic Settings From the Configuration Steps area, on the Define Basic Settings step, choose Configure. The Change View "Define Basic Settings": Details view dis-
plays.
7 Enable Snapshot Select the Enable Snapshot checkbox and choose Save.

Step # Comment
pad displays.
3 Enable Snapshot Select the Enable Snapshot checkbox and choose Save.
Remember Define Basic Settings must be reviewed following any system upgrade or improvement before continuing any business operation in the system. When differences are found from pre-
vious activations, you must correct them in the SSCUI Define Basic Settings.
2.6.3 Liquidity Items
2.6.3.1 Define Source Application Accounting
Test Administration
Customer project: Fill in the project-specific parts.

Appendix PUBLIC 12
Test Case ID <X.XX> Testing Date:
Tester Name: Duration:
Business Role(s): Responsibility: <State the Service Provider, Customer or Joint Service Provider and Customer>
Purpose
In this activity, you can make additional configuration for Financial Accounting (FI) in One Exposure.

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration. The SAP Fiori launchpad is displayed.
2 Access the SAP Fiori App Open Manage Your Solution(F1241).
3 Filter List Choose Configure Your Solution. The Change View “Source Application Accounting”:
Make the following entries: Overview screen is displayed.

Item Name: Cash Operations
4 Configuration From the Configuration Steps area, on the Define Source Application Accounting step, choose Configure.
5 Define Source Applica- Change the following entries for a specific company code per your requirement and choose Save: The source application accounting is defined for your
tion Accounting Company Code: 1010 company code.
AcctgScope: for example， Cash Position & Liquidity Analysis
Note
● Advanced Cash: Cash Position & Liquidity Analysis
This scope is treated as level 2 data and level 3 data. The chain step configured in
FCLM_FB_CHN_STP will influence Flow Builder in the delta run.
● Advanced Cash: Liquidity Analysis Only
This scope is treated as level 3 data only. The chain step configured in FCLM_FB_CHN_STP will
influence Flow Builder in the delta run.

Appendix PUBLIC 13
Step # Comment
UpdateMode: for example, Close to Real Time

Step # Comment
1 Log on Log on to the project experience in SAP Central Business Configuration. The SAP Fiori launchpad displays.
2 Open Define Source Ap- In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the The Change View “Source Application Ac-
plication Accounting tree view, search for the following activity: Define Source Application Accounting. counting”: Overview screen is displayed.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a
Configuration Expert - Business Process Configuration.
3 Define Source Applica- Change the following entries for a specific company code per your requirement and choose Save: The source application accounting is defined for
tion Accounting Company Code: 1010 your company code.
AcctgScope: for example, Cash Position & Liquidity Analysis
Note
● Advanced Cash: Cash Position & Liquidity Analysis
This scope is treated as level 2 data and level 3 data. The chain step configured in FCLM_FB_CHN_STP will
influence Flow Builder in the delta run.
● Advanced Cash: Liquidity Analysis Only
This scope is treated as level 3 data only. The chain step configured in FCLM_FB_CHN_STP will influence
Flow Builder in the delta run.
UpdateMode: for example, Close to Real Time

Appendix PUBLIC 14
2.6.3.2 Define Basic Settings for Liquidity Analysis
Use
In this activity, you define basic settings for liquidity analysis, such as default liquidity Items & derivation tool for liquidity analysis.
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configu-
ration.
5 Choose Configuration Items Select the following row: The Configure Your Solution – Cash Operations view dis-
Item Name: Cash Operations plays.
6 Define Basic Settings for Liquidity From the Configuration Steps area, on the Define Basic Settings for Liquidity Analysis The "General Settings for Liquidity Analysis" Details: De-
Analysis step, choose Configure. tails view displays.
7 Default Liquidity item Change the default liquidity item as needed.
8 Select Derivation Tool Select the Derivation Tool as your needed and choose Save.
For example: Q – Query Sequence.

Appendix PUBLIC 15
# ment
Note - Undefined
P - BRF Plus (alternative 1)
If you choose BRF Plus, please go to step Alternative 1: Define Derivation Rules –
BRF Plus
Q – Query Sequence
If you choose Query Sequence, please go to step Alternative 2: Define Derivation
Rules – Query Sequence

Step # Comment
2 Open Define Basic Settings In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in The "General Settings for Liquidity Analy-
for Liquidity Analysis the tree view, search for the following activity: Define Basic Settings for Liquidity Analysis. sis" Details: Details view displays.
3 Default Liquidity item Change the default liquidity item as needed.
4 Select Derivation Tool Select the Derivation Tool as your needed and choose Save.
For example: Q – Query Sequence.
Note - Undefined
P - BRF Plus (alternative 1)
If you choose BRF Plus, please go to step Alternative 1: Define Derivation Rules – BRF Plus
Q – Query Sequence
If you choose Query Sequence, please go to step Alternative 2: Define Derivation Rules – Query Sequence

Appendix PUBLIC 16
2.6.3.3 Alternative 1: Define Derivation Rules – BRF Plus
Test Administration
Purpose
In this activity, you can define Derivation Rules of Liquidity item via BRF plus.
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Cash Management Specialist. The SAP Fiori launchpad displays.
2 Access the SAP Fiori Open Liquidity Item Hierarchy (F1088). The Liquidity Item Hierarchy List view displays
App
3 Define Derivation Choose Define Derivation Rules. The Define Derivation Rules view displays.
Rules
4 Select Decision Table Make the following entries: The Define Derivation Rules displays.
Select Decision Table: Extended Liquidity Item Table
5 Change Table Setting Choose Edit, on the Decision Table: LQI_TABLE, Liquidity Item table section, choose Table Settings in the The relevant condition columns are selected.
top right.
In the Table Setting dialog box, you can choose/change Condition Columns attribution per your needs and
choose OK.

Appendix PUBLIC 17
# ment
6 Edit Derivation Rules In the Table Contents section, maintain the value for the relevant condition columns to derivate the specific The conditions and result have been maintained per
result (liquidity item). your needs.
For example:
(Condition column 1) Company code: choose the dropdown menu on this column.
Choose Direct Value Input, maintain the value as Company Code is equal to1010, then choose OK.
Maintain other Condition columns and Result column (Liquidity Item) per your need.
7 Activate Derivation Choose Activate. Choose Yes to confirm the message Do you really want to activate Liq- The Derivation Rules is saved and activated.
Rules uidity Item table?
2.6.3.4 Alternative 2: Define Derivation Rules – Query Sequence
2.6.3.4.1 Define Query Sequences
Use
In this activity, you can define query sequences.
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configuration.
2 Access the SAP Fiori Open Manage Your Solution(F1241).

App

Appendix PUBLIC 18
# ment
3 Configure Choose Configure Your Solution. The Configure Your Solution: Realize Phase view dis-
plays.
4 Filter List Make the following entries: A list of Configuration Items display with the filter crite-
Application Area: Finance ria.
5 Choose Configuration Select the following row: The Configure Your Solution – Cash Operations view
Items Item Name: Cash Operations displays.
6 Define Query Sequences From the Configuration Steps area, on the Define Query Sequences step, choose Configure.
7 Choose Origin On the Determine Work Area:Entry popup screen, make the following entries and choose Contin- The "Define Query Sequences" Change view displays.
ues(Enter).
Origin: <as needed>
8 Create Query Sequence Choose New Entries, make the following entries and choose Save. The new query sequence is created.
Query Sequence: <Query Sequence ID>
Name: <Query Sequence Name>
Description: <Query Sequence description>

Step # Comment
2 Define Query Se- In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree view,
quences search for the following activity: Define Query Sequences.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configuration
Expert - Business Process Configuration.
3 Choose Origin On the Determine Work Area:Entry popup screen, make the following entries and choose Continues(Enter). The "Define Query Sequences" Change
view displays.

Appendix PUBLIC 19
Step # Comment
Origin: <as needed>
4 Create Query Se- Choose New Entries, make the following entries and choose Save. The new query sequence is created.
quence Query Sequence: <Query Sequence ID>
Name: <Query Sequence Name>
Description: <Query Sequence description>
2.6.3.4.2 Define Queries for Liquidity Item Derivation
Test Administration
Purpose
In this step, you define queries for liquidity item derivation.
Procedure
Test Step # Test Step Name Instruction Expected Result Pass / Fail / Comment
1 Log On Log on to the SAP Fiori launchpad as a Cash Management Specialist.
2 Access the SAP Fiori App Open Define Queries for Liquidity Item Derivation (FLQQA1). The Edit Query view displays.

Appendix PUBLIC 20
3 Define Query Make the following entries:

Query ID: <Query ID>
Name: <Query name>
Description: <Query description>
Liquidity Item: liquidity item
4 Maintain Conditions Choose Conditions, make the conditions as needed. The query is defined
2.6.3.4.3 Assign Queries to Query Sequences
Test Administration
Purpose
In this step, you assign queries to query sequences.
Procedure
2 Access the SAP Fiori App Open Assign Queries to Query Sequence(FLQQA5). The “Sequences”:Display view displays.

Appendix PUBLIC 21
3 Choose Origin Make the following entries:

Origin: <C or D>
4 Select Sequence Select a query sequence from sequence list, choose Queries under the left- side Dialog Structure. The “Queries”:Change view displays.
5 Assign Query Choose New Entries, make the following entries and Choose Save. The query is assigned to sequence.
No.: entry number
Query ID: query ID
Liquidity Item: liquidity item
2.6.3.4.4 Assign Sequence to Company Codes
Use
In this activity, you can define the default derivation logic for liquidity items for company codes that have Cash Management activated. Each entry assigns a query sequence and a derivation function
to a company code, which the system uses to derive liquidity items for that company code. For example, liquidity items can be determined based
on the accounts referenced by the line items in documents posted to ledgers (G/L, accounts receivable, or accounts payable).
Procedure
# ment
tion.
2 Access the SAP Fiori App Open Manage Your Solution (F1241).
plays.

Appendix PUBLIC 22
# ment
5 Choose Configuration Items Select the following row: The Configure Your Solution – Cash Operations view
Item Name: Cash Operations displays.
6 Assign Sequence to Company From the Configuration Steps area, on the Assign Sequence to Company Codes step, choose The "Assign Sequence to Company Codes" Change view
Codes Configure. displays.
7 Create New Entry Choose New Entries, make the following entries and choose Save. The query sequence is assigned to a company code.
CoCd: 1010
Origin: <as needed>
Query Sequence: Query Sequence created in previous step

Step # Comment
2 Assign Sequence to In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree The "Assign Sequence to Company
Company Codes view, search for the following activity: Assign Sequence to Company Codes. Codes" Change view displays.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Config-
uration Expert - Business Process Configuration.
3 Create New Entry Choose New Entries, make the following entries and choose Save. The query sequence is assigned to a com-
CoCd: 1010 pany code.
Origin: <as needed>

Query Sequence: Query Sequence created in previous step

Appendix PUBLIC 23
2.6.3.5 Alternative 3: Define Default Liquidity Items for G/L Accounts
Test Administration
Purpose
In this step, you define default liquidity Items for G/L Accounts.
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Cash Management Special-

ist.
2 Access the SAP Fiori App Open Define Default Liquidity Items - For G/L Accounts (FLQIN- The Liquidity Calculation – Account s with Assig..”Change view
FACC). displays.
3 Define Default Liquidity Items for G/L Ac- Choose New Entries,make the following entries and choose Save: The default liquidity items for G/L accounts is defined.
counts Chart of Accounts: YCOA
Company Code: <your company code or empty>
Account from: <account from>
Account to: <account to>
Incl/excl: <Inclusive or Exclusive>
Further: < Liquidity Calculation: Further Evaluation >
Default Value: <default liquidity item>

Appendix PUBLIC 24
2.6.3.5.1 Schedule Job for Rebuild Tool for Liquidity Item
Test Administration
Purpose
In this step, you rebuild liquidity item in accounting document .
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Cash Management Specialist .
2 Access the SAP Fiori Open Schedule Job for Rebuild Tool for Liquidity Item (F6770). The Application Jobs view displays.
App
3 Create a New Applica- On the current view, choose Create to create an application job. The New Job: Schedule Health Check for Cash Management – With Free
tion Job Selection view displays.
4 Choose Job Template In the Template Selection section, make following entries:
Job Template: Rebuild Liquidity Items in Accounting Documents
Job Name: for example：Rebuild liquidity item in accounting docu-
ment
5 Maintain Scheduling Choose Step 2. In the Scheduling Options section, make the following entries If you would like to run this job immediately, the check-box of Start Im-
Options Start Immediately: <Selected or deselected> mediately should be selected.
If you schedule this job at some time in the future, the Start and Time

Appendix PUBLIC 25
Step # Comment
If you choose star immediately, other parameter do not need to maintain. Zone should be defined.
Start: <current time or any future time as needed>
Time Zone: <time zone>
For Recurrence Pattern, choose Define Recurrence Pattern.
In the Scheduling Information dialog box, the additional scheduling options are available.
Recurrence Pattern: for example, Weekly
Every: for example, 1
On: for example, Monday
End: Optional
On Non-Working Day: Optional
Calendar: for example, Germany(Standard)
Choose OK.
6 Maintain Parameter Choose Step 3. In Parameter section and make the following entries: Parameters are maintained.
Accounting Documents:
Company code: For example: 1010
Fiscal Year: For example: <current fiscal year>
Posting Date: as needed
Document Type: as needed
Document Number: as needed
Accounting Assignment:
G/L Account: as needed
Supplier: as needed
Customer: as needed
Note: If you keep parameters empty, that means all cases will be included in the job.
Technical Settings:
Test Run: as needed
7 Check Choose Check.
8 Run this Application Choose Schedule to run this application job.

Job
9 Check Application Choose Go to update the job status. When your job’s status change to Finished, you Job log displays.
Jobs Log choose Log navigate to the Job Log.

Appendix PUBLIC 26
2.6.3.6 Define Liquidity Item Derivation Mode for Flow Builder
Use
In this activity, you can define the liquidity item derivation mode for liquidity analysis flows for Flow Builder.
When Flow Builder is executed with the run type Liquidity Analysis: Delta Run from Staging or Liquidity Analysis: Mass Run for Financial Accounting, the program will read Liquidity Item Deriva-
tion Mode from this configuration guide. Flow builder will derive liquidity item during the document chain analysis according to the Liquidity Item Derivation Mode.
Liquidity Analysis Update Mode in Define Run Type for Flow Builder Liquidity Item Derivation Mode
Source Application Accounting
Close to Real Time Liquidity Analysis: Delta Run It will only fetch liquidity item information from Table BSEG Field LQITEM
from Staging
Deferred Liquidity Analysis: Delta Run It will derive liquidity item according to the Liquidity Item Derivation Mode as following:
from Staging The program read Liquidity Item Derivation Mode for a given company code from this configuration guide
If not found, the program will read one default entry of which the company code equals space.
If still not found, the program will fetch liquidity item information from Table BSEG Field LQITEM
all Liquidity Analysis: Mass Run for It will always derive liquidity item according to the Liquidity Item Derivation Mode as following:
Financial Accounting The program read Liquidity Item Derivation Mode for a given company code from this configuration guide
If not found, the program will read one default entry of which the company code equals space.
In this step, you can define the liquidity item derivation mode for liquidity analysis.
Note
1. This configuration guide provides you with another option to define the liquidity items for Flow Builder. If you don't want to fetch
liquidity items from the BSEG table, you need to configure it in this configuration guide.
2. When Liquidity Analysis Update Mode is set as Close to Real Time in the configuration Define Source Application Accounting,
Flow Builder will only fetch liquidity item information from Table BSEG Field LQITEM.
Procedure

Appendix PUBLIC 27
Step # Comment
plays.
5 Choose Configuration Items Select the following row: The Configure Your Solution – Cash Operations view
Item Name: Cash Operations displays.
6 Define Liquidity Item Derivation From the Configuration Steps area, on the Define Liquidity Item Derivation Mode for Flow The "Define Liquidity Item Derivation Mode for F.."
Mode for Flow Builder Builder step, choose Configure. Change view displays.
7 Create New Entry Choose New Entries, make the following entries and choose Save. The liquidity item derivation mode for liquidity analysis
For example: flows for Flow Builder is defined.
Entry 1)
CoCd: <empty>
LA: Liquidity Item Derivation Mode: for example: Fetch Liquidity Item from ta-
ble BSEG
Entry 2)
CoCd: 1010
LA: Liquidity Item Derivation Mode: for example, O Derive Liquidity Item On-
line
The derivation mode is set as such as Derive Liquidity Item Online , It means
derivation tool BRF plus or Query Sequence will be fetched.

Appendix PUBLIC 28
Step # Comment
2 Define Liquidity Item Deriva- In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity The "Define Liquidity Item Derivation Mode for
tion Mode for Flow Builder in the tree view, search for the following activity: Define Liquidity Item Derivation Mode for Flow Builder. F.." Change view displays.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as
a Configuration Expert - Business Process Configuration.
3 Create New Entry Choose New Entries, make the following entries and choose Save. The liquidity item derivation mode for liquidity
For example: analysis flows for Flow Builder is defined.
Entry 1)
CoCd: <empty>
LA: Liquidity Item Derivation Mode: for example: Fetch Liquidity Item from table BSEG
Entry 2)
CoCd: 1010
LA: Liquidity Item Derivation Mode: for example, O Derive Liquidity Item Online
Note:
The derivation mode is set as such as Derive Liquidity Item Online. It means derivation tool BRF
plus or Query Sequence will be fetched.
2.6.3.7 Flow Builder: Stop Condition (Optional)

Purpose
In Flow Builder, the technical concept for chain step is removed, now you can use stop condition to shorten/stop the chain on business purpose.
Note The flow builder’s profile for stop condition is used for Accounting Scope “Cash Position & Liquidity Analysis” or “Liquidity Analysis Only”.
2.6.3.7.1 Define Profile for Stop Condition
Test Administration

Appendix PUBLIC 29
Purpose
In this activity, you define a profile for stop condition.
Procedure
# ment
2 Access the SAP Fiori app Open Flow Builder: Stop Condition (S_ER9_11002333). The Change View “Flow Builder: Stop Condition”: Overview
screen displays
3 Create New Profile Choose New Entries. Make the following entries and choose Save. The New Entries: Overview of Added Entries screen displays.
Profile: <Profile Name>
Profile Description: <Profile Description>
4 Define Filter Conditions Select the created profile and choose Define Filter Conditions. The Maintain Stop Conditions For Flow Builder screen displays.
5 Maintain Stop Conditions For Flow Make the following entries per your business requirement and choose Save Stop The stop condition is maintained.
Builder Conditions.
G/L Account: <per your requirement>
Account Type: <per your requirement>
Planning Level: <per your requirement>
Supplier: <per your requirement>
Customer: <per your requirement>
Posting Key: <per your requirement>
Choose Continue to confirm the Information popup screen.

Appendix PUBLIC 30
2.6.3.7.2 Assign Flow Builder Profile to Company Code
Test Administration
Purpose
In this activity, you define the association between the company code and profile of stop conditions.
Procedure
# ment
1 Log on Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Configu-
ration.
3 Search Choose Configure Your Solution.
4 Application and Subapplica- Make the following entries: Selected application area items are displayed in the Configuration
tion Area Application Area: Finance Items view.
5 Select Configuration Item Choose the following row: Configuration steps are displayed for the selected row.
Item Name:
Cash Operations
6 Select Configuration Steps Choose Configure to configure the following row: The "Define Profile for Flow Builder:Stop Condi..": Change dis-
Step Name: Define Profile for Flow Builder:Stop Conditions plays.
7 Assign Profile to Company Choose a company code and make the following entries and choose Save: The profile for flow builder’s stop condition is assigned for a spe-
Code For example:

Appendix PUBLIC 31
# ment
Cocd: 1010 cific company code.

Profile: <the profile for flow builder’s stop condition created
in previous step>

Step # Comment
2 Open Define Profile for Flow In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity The "Define Profile for Flow Builder:Stop
Builder: Stop Conditions in the tree view, search for the following activity: Define Profile for Flow Builder:Stop Conditions. Condi..": Change displays.
3 Assign Profile to Company Choose a company code and make the following entries and choose Save: The profile for flow builder’s stop condition is
Code For example: assigned for a specific company code.
Cocd: 1010
Profile: <the profile for flow builder’s stop condition created in previous
step>
2.6.3.8 Manage Liquidity Items Hierarchies
Test Administration

Appendix PUBLIC 32
Purpose
In this step, you create Liquidity Item Hierarchies.
Procedure

Step # Comment
2 Access the SAP Fiori App Open Manage Liquidity Item Hierarchies (F4966). The Manage Liquidity Item Hierarchies view displays.
3 Import Legacy Liquidity In the Hierarchy List, choose the Import Hierarchy button. A legacy Liquidity item hierarchy is imported to the Global Hierar-
Item Hierarchy (Option 1) In the Import Hierarchy dialog box, make the following entries and choose OK: chy and activate successfully.
Source: Liquidity Item Hierarchy

Liquidity Item Hierarchy: <a legacy liquidity item hierarchy> Note If you have legacy liquidity item hierarchies, you can use
In the Create a Hierarchy Based On dialog box, make the following entries and choose Create: this step to migrate them one by one.
Hierarchy ID: For example, LQH_HIE
Note You can use the same ID or new ID.
Hierarchy Description: For example, Liquidity Item Hierarchy

Valid From: For example, <01/01/1900>
Note Use the same validity period as the legacy hierarchy.
Valid To: For example, <keep default>

Note: <any value>
4 Create a New Hierarchy Choose Create, make the following entries and choose Create in the New Hierarchy dialog box: Create a new liquidity item hierarchy.
(Option 2) Type: Liquidity Item Hierarchy
Hierarchy ID: <your hierarchy ID>
Hierarchy Description: <description for hierarchy>
Valid From: <valid from date>
Valid To: <default value>

Appendix PUBLIC 33
Step # Comment
Note: <your note>
5 Navigate to Timeframe Click your hierarchy to navigate to right pane.

pane
6 Add New Subnode Choose Edit. In the Nodes section of right pane, choose the highest node and choose +(Add) at The liquidity items are assigned as nodes of liquidity item hierarchy.
the right side of the row. Make the following entries in the Add Node dialog box and choose
OK.
Subnode: Selected
Node:<select nodes(liquidity items) via search help F4>
Note You can also choose Fast Entry (beside Add +) to assign liquidity items as subnode.
7 Assign Liquidity Item to a Choose the new subnode created in the previous step and choose +(Add) at the right side of the The liquidity items are assigned to a node of liquidity hierarchy.
Node row. Make the following entries in the Add Node dialog box and choose OK.
Liquidity Item: Selected
Liquidity Item:<select liquidity items via search help F4>
Note You can also choose More (beside Add +), from the dropdown menu, choose Fast En-
try to assign liquidity items.
8 Save Choose Save. The liquidity item hierarchy is well structured and maintained.
9 Activate Choose Activate. The liquidity item hierarchy newly maintained is successfully acti-
vated. Its status has been converted into Active.
10 Export Liquidity Item Hier- Choose Export/Import and choose Export to Spreadsheet from the dropdown menu. A new excel spreadsheet containing the liquidity item hierarchy
archy to Spreadsheet structure and contents is exported and generated in the specified
folder path.
Open the spreadsheet to go through the liquidity item hierarchy de-
tails.

Appendix PUBLIC 34
2.6.3.9 Blocking Date Range for Actual Flows in Liquidity Analysis (Optional)
Test Administration
Purpose
In this activity, you can define blocking date range for actual flows in Liquidity Analysis.
The Blocked Date program determines whether FI documents with value or posting dates are blocked from generating into One Exposure. FI documents with dates prior to or equal to the blocking
dates are blocked from generating level 3 actual flows in One Exposure.
Note Since the blocking date application only applies to level 3 cash flows in Liquidity Analysis, the account scope should be set as Cash Position & Liquidity Analysis or Liquidity Analysis
Only via SSCUI (105487) Define Source Application Accounting.
If you do not want to block level 3 actual flows generation in One Exposure, skip this procedure.
Procedure
1 Log On Log on to the SAP Fiori launchpad as a Cash Management Specialist. The SAP Fiori launchpad displays.
2 Set Block Date for Actual Cash- Open Set block date for actual cashflows (S_ER9_11002196). The "Flow Builder:Blocked Date": Change view displays
flows .
3 New Entry Choose New Entries The New Entries: Overview of Added Entries view displays.
4 Maintain Block Date Range Make the following entries The block date range for actual flows in liquidity analysis is maintained.
CoCd: 1010

Appendix PUBLIC 35
Trans Date: <Transaction date>

Posting Date: <Posting date>
5 Save Choose Save.
2.6.4 Payment Approval
2.6.4.1 Maintain Payment Approver for Bank Accounts
Context
This activity describes how to maintain the payment approver for existing bank accounts as a prerequisite. Payment signatories work as approvers in the Approval and Bank Integration section of the
scope item J78 Advanced Cash Operations.
Procedure
Finish the Maintain Payment Approver for Multiple Bank Accounts procedure of the scope item J77 Advanced Bank Account Management for the following two existing bank accounts:
● Bank account 1133698, bank key 50070010, country/region DE
● Bank account 2580061, bank key 82080000, country/region DE
Note
● If the Unlimited Approval field is selected for the payment approvers, it won’t take the amount setting of this approver into consideration during BCM approval process.
● Please make sure you have assigned all payment approver groups of the approval pattern that you want to use in the payment approval process. If not, the payment approval pattern will be
invalid, no payment approvers can be found during the BCM approval process, and the payment approval process will also fail. After you maintain the payment approver for the bank ac-
counts, you can check if there are valid payment approval steps. To do so, open the Manage Bank Accounts (F1366A) app, choose the Payment Approvers tab, and choose Show Approval
Steps.

Appendix PUBLIC 36
2.6.4.2 Specify Optional User Authentication (Optional)
Purpose
In this step, you have the option to enable two-factor authentication for the Approve Bank Payments app. If you enable two-factor authentication, the business user submitting payment batches for
processing by the bank will be asked to authenticate their identity using SAP Cloud Platform Identity Authentication (IAS).
Note this functionality is only for approving outgoing payments using the Approve Bank Payments Fiori app.
Note that SAP Cloud Platform Identity Authentication are separate products. You must have an active account in SAP Cloud Platform Identity Authentication to use two-factor authentication as de-
scribed in the Set-Up Instructions for this scope item.
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process
Configuration.
4 Application and Sub-application Make the following entries: Selected application area items are displayed in the Configuration
area Application Area: Finance Items view.
Sub Application Area: Bank Communication Management
Item Name:
Approve Bank Payments
6 Select Configuration Steps Choose Configure to configure the following row: The Change View “Specify Optional User Authentication”: Over-
Step Name: Specify Optional User Authentication view displays.
7 Add New Entry Choose New Entries and make the following entries and choose Save: Two-factor authentication for the Approve Bank Payments app is

Appendix PUBLIC 37
# ment
Authentication Type: for example, <Authentication by IAS is on> enabled.

Step # Comment
1 Log on Log on to the project experience in SAP Central Business Configuration.
2 Open Specify Optional In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in The Change View “Specify Optional User Au-
User Authentication the tree view, search for the following activity: Specify Optional User Authentication. thentication”: Overview screen displays.
3 Add New Entry Choose New Entries and make the following entries and choose Save: Two-factor authentication for the Approve Bank
Authentication Type: for example, <Authentication by IAS is on> Payments app is enabled.
2.6.4.3 Define Automatic Approval/Rejection for Bank Account Master Data
Purpose
In this step, you can set what should be done in case of missing approvals. You will have 3 possible actions as following:
01: Auto-Rejection when Approval Pattern not Found or List Empty
02: Auto-Rejection when Approval List Empty
03: Auto-Approve when Approval List Empty
Note If no value is maintained for this customizing , default value 03 will be used for all payment batches. This means the payment batches are auto-approved in case the approval list for House
Bank Account is empty.
If your payment batch is automatically rejected, you might also reverse all payment documents related to this payment batch to be able to collect them as open items in another payment batch.

Appendix PUBLIC 38
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Con-
figuration.
4 Application and Subapplica- Make the following entries: Selected application area items are displayed in the Configuration
tion area Application Area: Finance Items view.
Item Name:
Bank Account Management
6 Select Configuration Steps Choose Configure to configure the following row:

Step Name: Define Settings for Bank Account Master Data
7 Define Automatic Approval/ Double-click Define Automatic Approval/Rejection in the Dialog Structure of left side. The Define Automatic Approval/Rejection displays.
Rejection
8 Add New Entry Choose New Entries and make the following entries and choose Save: The Automatic Approval/Rejection setting for Bank account mas-
For example: ter data is defined.
CoCd: 1010
Appr/Rjct: eg: <01 Auto Rejection when Approval Pattern not
Found or List Empty>

Appendix PUBLIC 39
Step # Comment
2 Define Settings for Bank Ac- In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in
count Master Data the tree view, search for the following activity: Define Settings for Bank Account Master Data.
3 Define Automatic Double-click Define Automatic Approval/Rejection in the Dialog Structure of left side. The Define Automatic Approval/Rejection view
Approval/Rejection displays.
4 Add New Entry Choose New Entries and make the following entries and choose Save: The Automatic Approval/Rejection setting for
For example: Bank account master data is defined.
CoCd: 1010
Appr/Rejection: eg: <01 Auto Rejection when Approval Pattern not Found or List
Empty>
2.6.5 Define Cash Position Profile
Test Administration
Purpose
In this step, you can define profiles for any desired reporting structure to be used in short-term cash position. You can define the cash position hierarchy, balance period, the logic how bank account
balance is shown and so forth in a specific profile based on your business scenario and requirement. You can also define filters and assign filters to your profile. With the predefined view, you can go
through the balance data in the Short-Term Cash Positioning (F5380) app accordingly.

Appendix PUBLIC 40
Procedure

Step # Comment
2 Access the SAP Open Define Cash Position Profiles (F5399). The Change View “Define Cash
Fiori App Position Profile’: Overview screen
displays.
3 Create New Entry Choose New Entries. The New Entries: Details of Added
Entries screen displays.
4 Define Cash Posi- Make the following entries and choose Save: An new Cash Position Profile is de-
tion Profile Cash Pos. Profile: for example, CPP_01 fined.
Description: For example, CP Profile for short term CP

Hierarchy Src.: For example, Derived from Cash Pool and Bank Account Master Data
Note If you want to show the cash pool hierarchy in the Short Term Cash Position app, choose Hierarchy Src: Derived from Cash Pool
and Bank Account Master Data. And you can not enable Root Node and maintain Hier. Level.
Enable Root Node: No

Root Node Name: <empty>
Hier. Level 1: <default>
Hier. Level 2: <default>
Hier. Level 3: <empty>
Note Only if Derived by Bank Account Master Data is chosen for hierarchy source, you need to fill in Hier. Level 1 & 2
& 3, and at least Hier. Level 1 shall be given. There's no bank account dimension because system always takes bank account as the
lowest node in the hierarchy.
Hierarchy ID: <choose a bank account hierarchy via Value Help>
Note Only if Derived from Bank Account Hierarchy is chosen for hierarchy source, you need to fill in Hierarchy ID. The
hierarchies were created in App Manage Bank Account Hierarchies (F4973), you can refer to the Manage Bank Account Hierar-
chies procedure of the scope item J77 Advanced Bank Account Management.

Appendix PUBLIC 41
Step # Comment
View Category: Balance View or Delta View

Balance Type: Value Date Balance or Available Balance
Note The value date balance is the interest-bearing balance for a particular day. It is calculated based on the ledger balance.
The available balance indicates the funds available to the account holder for immediate use.
Some banks, especially US banks, provide this balance in bank statements. For bank statements that do not provide it, the system cre-
ates a data entry for the available balance by copying the amount of the value date balance.
Bal.Category: Opening Balance or Closing Balance

Increment: For example, 7
Period Unit: For example, Days
Natural End: For example, No
Show Overdue: For example, Yes
Note:
If selected Show Overdue checkbox, a separate overdue column will appear in short-term cash positioning for showing overdue amount.
Incl. Overdue: Yes
If selected Incl. Overdue checkbox, overdue amount will be added into the closing balance of the first period.
Show Future: For example, Yes
Shift Option: For example, Non-Working Day -> Next Working Day
Factory Cal. ID: For example, 01
Enable Smart Crcy: For example, Yes
Note:
With the Enable Smart Currency function, you can switch between different currency types to get an aggregated balance. There are three
currency types, company code currency, bank account currency, and display currency.
Display Crcy: For example, EUR
If display currency is defined, all currencies will be converted into display currency based on exchange rate type and shown in short-term
cash positioning, or bank account currencies will be taken.
Exch.Rate Type: For example, M
Display Pos.Details: For example, Yes
Scaling Factor: For example, No Scaling
5 Define Filter (Op- Steps from 5 to 11 are optional. You can define them as needed. The Change View “Define Filter”:
tion) Choose Define Filter in the left-side Dialog Structure. Overview screen displays.
6 Maintain Filter Choose New Entries. Make following entries and choose Save: Filter is created.

Appendix PUBLIC 42
Step # Comment
Name Filter: CP_A

Filter Description: Filter for cash position profile CCP_01
7 Define Filter Con- Select your filter, then choose Define Filter Conditions. The Maintain Filter Conditions
ditions screen displays.
8 Maintain Parameter Maintain the following entries as needed and choose Save Filter Conditions. Choose Continue to confirm the Information popup screen. Filter condition is created.
for Filter Condition Bank Accounts:
Company Code: 1010

Bank Country/Region Key: DE
Bank Key: <as needed>
Currency: <as needed>
Technical ID: <as needed>
Account Number: <as needed>
Account Type: <as needed>
Co Code Country/Region Key: <as needed>
Contract Type: <as needed>
Flows:
Forecast Planning Level: <as needed>
Overdue Planning Level: <as needed>
9 Back Choose Back.
10 Assign Filter to Choose Assign Filter to Cash Position Profile in the left-side dialog structure. Make the following entries in the popup screen and choose The Change View “Assign Filter to
Cash Position Pro- Enter. Cash Position Profile”: Overview
file Cash Position Profile: CPP_01 screen displays.
11 Choose Filter to Choose New Entries. Enter your filter CP_A and choose Save. Filter is assigned to the cash posi-
Assign tion profile.

Appendix PUBLIC 43
2.6.6 Reconcile Cash Flows – Intraday Memo Records
2.6.6.1 Enable New Reconciliation Model (Optional)
Use
In this activity, you enable new reconciliation model feature.
Caution Switch-off (default):

● Everything is the same as before.
● New reconciliation app Reconcile Cash Flows - Intraday (F3418A) does not work.
● Residual flows are invisible in Apps: Cash Flow Analyzer (F2332) & Check Cash Flow Items (F0735) & Short-Term Cash Positioning (F5380).
Switch-on:
● Old reconciliation app Reconcile Cash Flows - Intraday Memo Records (F3418) does not work.
● Reconciliation status in Cash Flow Analyzer (F2332) is deactivated. Residual flows are invisible in Cash Flow Analyzer (F2332).
● Existing reconciliation status in Check Cash Flow Items (F0735) is deactivated and the new one should be activated. Residual flows are visible in Check Cash Flow Items (F0735).
● The data displayed in Short-Term Cash Positioning (F5380) replies on the cash position profile setting.
Note If you do not enable new reconciliation model feature, you should skip following steps:
● Enable New Reconciliation Model (option)
● Define Planning Level for Residual Forecast (option)
● Define Memo Record Types for Residual Forecast (option)
● Define Profiles for Cash Flow Reconciliation (option)
● Reconcile Cash Flows (New Reconciliation Model)

Appendix PUBLIC 44
# ment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business Process Config-
uration.
5 Select General Settings Select the following row: The Configure Your Solution - General Settings view dis-
Item Name: General Settings plays.
6 Define Basic Settings From the Configuration Steps area, on the Define Basic Settings step, choose Configure. The Change View "Define Basic Settings": Details view
displays.
7 Enable New Reconciliation Select the Enable New Reconciliation Model checkbox and choose Save.
Model

Step # Comment
pad displays.
3 Enable New Reconciliation Select the Enable New Reconciliation Model checkbox and choose Save.
Model

Appendix PUBLIC 45
2.6.6.2 Define Planning Level for Residual Forecast (Optional)
Purpose
In this activity, you define planning level for residual forecast.
Procedure
# ment
Configuration.
4 Application and Subapplication Make the following entries: Selected application area items are displayed in the Configuration
Item Name: Cash Operations.
6 Select Configuration Steps Choose Configure to configure the following row: The “Define Planning Levels”: Change view displays.
Step Name: Define Planning Levels.
7 New Entries Choose New Entries.
8 Define Planning Level Make the following entries and choose Save: The planning level is defined.
Level : For example, RF
SC : For example, <blank>
Source: For example, BNK

Appendix PUBLIC 46
# ment
Short Text : For example, Res.Fore.

Planning Level Long Text: For example, Residual Forecast

Step # Comment
2 Open Define Plan- In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree view, The “Define Planning Levels”:
ning Levels search for the following activity: Define Planning Levels. Change view displays.
4 Define Planning Make the following entries and choose Save: The planning level is defined.
Level Level: For example, RF
SC: For example, <blank>
Source: For example, BNK
Short Text: For example, Res.Fore.
Planning Level Long Text: For example, Residual Forecast
2.6.6.3 Define Memo Record Type for Residual Forecast (Optional)
Purpose
In this activity, you define memo record type for residual forecast.

Appendix PUBLIC 47
Procedure
# ment
Configuration.
6 Select Configuration Steps Choose Configure to configure the following row: The Change View “Define Memo Record Types”: Overview view
Step Name: Define Memo Record Types. displays.
8 Define memo record types Make the following entries and choose Save: The planning typs is defined.
Plg Type: For example, RF
Plan.Lvl: For example, RF
memo record type Text: For example, Residual Forecast
Memo Record Category: For example, Residual Forecast

Appendix PUBLIC 48
Step # Comment
2 Open Define Memo In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the The Change View “Define Memo Record
Record Types tree view, search for the following activity: Define Memo Record Types . Types”: Overview screen displays.
4 Define memo record Make the following entries and choose Save: The planning typs is defined.
types Plg Type: For example, RF
Plan.Lvl: For example, RF
memo record type Text: For example, Residual Forecast
Memo Record Category: For example, Residual Forecast
2.6.6.4 Define Profiles for Cash Flow Reconciliation (Optional)
Purpose
In this activity, you define profiles for cash flow reconciliation that are necessary for the new app Reconcile Cash Flows - Intraday (F3418A) test procedure.
Procedure
# ment

Appendix PUBLIC 49
# ment
Configuration.
4 Application and Subapplication area Make the following entries: Selected application area items are displayed in the Configura-
Application Area: Finance tion Items view.
6 Select Configuration Steps Choose Configure to configure the following row: The “Define Profiles for Cash Flow Reconciliation ”: Change
Step Name: Define Profiles for Cash Flow Reconciliation. view displays.
8 Define Reconciliation Profile Make the following entries and choose Save: The reconciliation profile is defined.
Reconciliation Profile: For example, ZRP_01
Reconciliation Profile Description : <description>
Planning Type: RF
Note Only the planning type for residual flows can be used.
9 Assign Planning Levels for Bank State- Choose the profile, choose Assign Planning Levels for Bank Statement Flows in
ment Flows left dialog structure.
10 New Entry Choose New Entry. Assign all relevant planning levels as needed. For example:
AB
Note The planning level is used in intraday memo record.
11 Assign Planning Levels for Forecasted Choose Assign Planning Levels for Forecasted Flows in left dialog structure.
Flows
12 New Entry Choose New Entry. Assign all relevant planning levels as needed. For example:
B2, B3, B5, B9, F1

Appendix PUBLIC 50
# ment
13 Save Choose Save

Step # Comment
2 Open Define Profiles for In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activ- The Change View “Tolerance Groups for Cash Flow
Cash Flow Reconciliation ity in the tree view, search for the following activity: Define Profiles for Cash Flow Reconciliation. Reconciliation”: Overview screen displays.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad
as a Configuration Expert - Business Process Configuration.
4 Define Reconciliation Pro- Make the following entries and choose Save: The reconciliation profile is defined.
file Reconciliation Profile: For example, ZRP_01
Reconciliation Profile Description : <description>
Planning Type: RF
Note Only the planning type for residual flows can be used.
5 Assign Planning Levels for Choose the profile, choose Assign Planning Levels for Bank Statement Flows in left dialog structure.
Bank Statement Flows
6 New Entry Choose New Entry. Assign all relevant planning levels as needed. For example: AB
Note The planning level is used in intraday memo record.
7 Assign Planning Levels for Choose Assign Planning Levels for Forecasted Flows in left dialog structure.
Forecasted Flows
8 New Entry Choose New Entry. Assign all relevant planning levels as needed. For example: B2, B3, B5, B9,F1

Appendix PUBLIC 51
Step # Comment
9 Save Choose Save
2.6.6.5 Define Tolerance Groups for Cash Flow Reconciliation
Purpose
In this activity, you create tolerance groups for Cash Flow Reconciliation that are necessary for the following Reconcile Cash Flows – Intraday Memo Records test procedure.
Note When you reconcile intraday memo records with forecasted cash flows, there might be a difference in the amount. The system then checks whether the bank account has a tolerance group
defined. If the bank account has no tolerance group assigned, or the difference exceeds the defined limit of the tolerance group, the system prompts a warning message to warn you about the no-
table difference.
Procedure

Step # Comment

App
4 Application and Subap- Make the following entries: Selected application area items are displayed in the Con-
plication area Application Area: Finance figuration Items view.

Appendix PUBLIC 52
Step # Comment
5 Select Configuration Choose the following row: Configuration steps are displayed for the selected row.
Item Item Name: Cash Operations.
6 Select Configuration Choose Configure to configure the following row: The Change View “Tolerance Groups for Cash Flow
Steps Step Name: Define Tolerance Groups for Cash Flow Reconciliation. Reconciliation”: Overview view displays.
8 Create Default Toler- Make the following entries and choose Save: The empty tolerance group created is the default for the
ance Group Currency: For example, EUR bank account of the same currency.
Tolerance Group: For example, <blank> for EUR bank accounts
Note Enter the tolerance group and a tolerance group description.
Amount: For example, 100.00

Percentage: For example, 5.0%
Exchange Rate Type: For example, M
Note You can create other tolerance groups with different tolerance amounts, percentages, or currency
per your business needs and then assign it to the relevant bank account.

Step # Comment
2 Open Define Tolerance Groups In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activ- The Change View “Tolerance Groups for Cash
for Cash Flow Reconciliation ity in the tree view, search for the following activity: Define Tolerance Groups for Cash Flow Reconciliation. Flow Reconciliation”: Overview screen displays.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad
as a Configuration Expert - Business Process Configuration.
4 Create Default Tolerance Group Make the following entries and choose Save: The empty tolerance group created is the default
Currency: For example, EUR for the bank account of the same currency.

Appendix PUBLIC 53
Step # Comment
Tolerance Group: For example, <blank> for EUR bank accounts
Note Enter the tolerance group and a tolerance group description.
Amount: For example, 100.00

Percentage: For example, 5.0%
Exchange Rate Type: For example, M
Note You can create other tolerance groups with different tolerance amounts, percentages, or currency
per your business needs and then assign it to the relevant bank account.
2.6.6.6 Activate Intraday Reconciliation for Bank Account
Purpose
In this step, you activate Intraday Reconciliation for Bank Accounts. This activation is necessary for the following Reconcile Cash Flows - Intraday Memo Records test procedure.
Procedure

Step # Comment
2 Access the SAP Fiori Open Manage Bank Accounts (F1366A).

App
3 Enter Selection Criteria Make the following entries and choose Go:
Account Number: For example, 2580061
Bank Key: For example, 82080000
Bank Country/Region: For example, DE
4 Select Bank Account Choose > for the Intraday Reconciliation activation. The Bank Account view is displayed.

Appendix PUBLIC 54
Step # Comment
5 Edit Choose Edit.
6 Activate Intraday Rec- Choose the Bank Relationship tab, enter the following data and choose Save: Note When this change is relevant to dual control, the button is
onciliation Tolerance Group for Reconciliation: For example, <blank> Submit for Activation. When this change is relevant to workflow,
the button is Submit for Approval.
Reconcile Intraday Memo Records: Selected
Note If no tolerance group is maintained in the bank account master data, the default (empty)
tolerance group for the bank account of the same currency is used. When you have created other
tolerance groups, maintain the relevant data.
Caution If no tolerance group is available for certain currency, then a system text format notifi-
cation appears for reconciliation.
Pmnt Tran Type Group: <your transaction type group>
7 Activate Bank Account Note If Full Cash Management and Dual Control Revision Activate is applied in the basic set-
Change Request (Op- tings, follow the Activate Bank Account Change Request procedure in the Advanced Bank Ac-
tional) count Management(J77) test script.
8 Approve Bank Account Note If Full Cash Management and Workflow Revision Activate is applied in the basic settings,
Change Request (Op- follow the Approve Bank Account Change Request procedure in the Advanced Bank Account
tional) Management (J77) test script.
2.6.7 Cash Trade Request
2.6.7.1 Enable Cash Trade Requests
Test Administration

Appendix PUBLIC 55
Purpose
You can enable the cash request functionality in the full scope of cash management. This functionality is integrated with Treasury and Risk Management (TRM).
Procedure
# ment
Configuration.
Area Application Area: Finance Items view.
6 Select Configuration Steps Choose Configure to configure the following row: The Change View “Basic Settings”: Details view displays.
Step Name: Define Basic Settings
7 Enable Cash Trade Requests Make the following entries and choose Save: The cash request functionality in the full scope of cash management
Enable Cash Trade Requests: <selected> is enabled.

Appendix PUBLIC 56

Step # Comment
2 Open Define Basic In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in The Change View “Basic Settings”: Details screen
Settings the tree view, search for the following activity: Define Basic Settings. displays.
3 Enable Cash Trade Make the following entries and choose Save: The cash request functionality in the full scope of
Requests Enable Cash Trade Requests: <selected> cash management is enabled.
2.6.7.2 Define Planning Level for Cash Request
Test Administration
Purpose
In this step, you create the planning levels which are used for cash requests created, submitted and released.
Procedure

Appendix PUBLIC 57
# ment
Configuration.
Item Name:
Cash Operations
6 Select Configuration Steps Choose Configure to configure the following row: The "Define Planning Levels": Change view displays.
Step Name: Define Planning Levels
7 Create Planning Levels for Cash Choose New Entries and make the following entries and choose Save: The planning levels for cash request are defined.
Requests For example:
Planning level for cash request created:
Level: C1
Source: BNK
Short Text: Created CR
Planning Level Long Text: Created Cash Request
Planning level for cash request submitted:
Level: C2
Short Text: Submit. CR
Source: BNK
Planning Level Long Text: Submitted Cash Request
Planning level for cash request Released:
Level: C3
Source: BNK
Short Text: Releas. CR

Appendix PUBLIC 58
# ment
Planning Level Long Text: Released Cash Request

Step # Comment
2 Open Define Planning Lev- In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree The "Define Planning Levels":
els view, search for the following activity: Define Planning Levels. Change screen displays.
3 Create Planning Levels for Choose New Entries and make the following entries and choose Save: The planning levels for cash request
Cash Requests For example: are defined.
Planning level for cash request created:

Level: C1
Source: BNK
Short Text: Created CR
Planning Level Long Text: Created Cash Request
Planning level for cash request submitted:
Level: C2
Short Text: Submit. CR
Source: BNK
Planning Level Long Text: Submitted Cash Request
Planning level for cash request Released:
Level: C3
Source: BNK
Short Text: Releas. CR
Planning Level Long Text: Released Cash Request

Appendix PUBLIC 59
2.6.7.3 Assign Planning Level to Cash Request
Test Administration
Purpose
In this step, you assign the planning levels to cash requests with the status of created, submitted and released. You can see cash trade requests in different statuses by planning level.
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert - Business

Process Configuration.

Appendix PUBLIC 60
# ment
Item Name:
Cash Operations
6 Select Configuration Steps Choose Configure to configure the following row: The Change View “Assign Planning Levels to Cash Requests”:
Step Name: Assign Planning Levels to Cash Trade Requests Overview displays.
7 Define Planning Levels for Cash Choose New Entries and make the following entries and choose Save: The planning levels for cash request are defined.
Requests For example:
Item 1:
Original: <blank>
Created: C1
Submitted: C2
Released: C3
Item 2:
Original: F0
Created: C1
Submitted: C2
Released: C3

Step # Comment
2 Open Assign Planning Levels In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity The Change View “Assign Planning Levels to
to Cash Trade Requests in the tree view, search for the following activity: Assign Planning Levels to Cash Trade Requests. Cash Requests”: Overview screen displays.
3 Define Planning Levels for Choose New Entries and make the following entries and choose Save: The planning levels for cash request are defined.
Cash Requests For example:
Item 1:

Appendix PUBLIC 61
Step # Comment
Original: <blank>
Created: C1
Submitted: C2
Released: C3
Item 2:
Original: F0
Created: C1
Submitted: C2
Released: C3
2.6.8 Manage Reason Codes
2.6.8.1 Create Internal Reason Codes
Purpose
In this activity, you can create internal reason codes and descriptions. You can later use the values to map them to external reason codes you receive from external entities, such as banks.
This step is relevant to the following Monitor Payments for GPI Tracker test procedure.
Procedure
# ment
Configuration.

Appendix PUBLIC 62
# ment
Item Name:
Manage Reason Codes
6 Select Configuration Steps Choose Configure to configure the following row: The Change View “Internal Reason Codes”: Overview displays.
Step Name: Create Internal Reason Codes
7 Create Internal Reason Codes Choose New Entries and make the following entries and choose Save: The Internal Reason Codes are defined.
For example:
Reason: SGLT
Reason Description: Has left gpi

Step # Comment
2 Open Create Internal In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the The Change View “Internal Reason Codes”:
Reason Codes tree view, search for the following activity: Create Internal Reason Codes. Overview screen displays.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Con-
figuration Expert - Business Process Configuration.
3 Create Internal Reason Choose New Entries and make the following entries and choose Save: The Internal Reason Codes are defined.
Codes For example:
Reason: SGLT

Appendix PUBLIC 63
Step # Comment
Reason Description: Has left gpi
2.6.8.2 Map External Reason Codes to Internal Reason Codes
Purpose
In this activity, you can interpret the reason codes you receive from external entities, such as banks. These mappings will be displayed in the batch and payment monitor with an external reason code
and internal description to interpret the codes for your system.
This step is relevant to the following Monitor Payments for GPI Tracker test procedure.
Procedure
# ment

Application Area: Finance tion Items view.
Item Name:

Appendix PUBLIC 64
# ment
Manage Reason Codes
6 Select Configuration Steps Choose Configure to configure the following row: The Change View "Map internal to external reason codes":
Step Name: Map External Reason Codes to Internal Rea- Overview displays.
son Codes
7 Map External Reason Codes to Internal Choose New Entries and make the following entries and choose Save: Mapping of internal to external reason codes has been main-
Reason Codes For example: tained.
Status Reason Code: G001

Reason: SGLT

Step # Comment
2 Open Map External Reason In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity The Change View "Map internal to external
Codes to Internal Reason Codes in the tree view, search for the following activity: Map External Reason Codes to Internal Reason Codes. reason codes": Overview screen displays.
7 Map External Reason Codes to Choose New Entries and make the following entries and choose Save: Mapping of internal to external reason codes
Internal Reason Codes For example: has been maintained.
Status Reason Code: G001

Reason: SGLT

Appendix PUBLIC 65
2.6.9 Automatically Reversing Rejected Payments
2.6.9.1 Define Rules for Reversing Rejected Payments
Purpose
In this step, you define rules that determine which reason should be automatically specified for reversing a rejected payment document and which payment block option should be automatically spec-
ified for blocking the reopened items.
Procedure
# ment

4 Application and Subapplica- Make the following entries: Selected application area items are displayed in the Configuration Items
tion area Application Area: Finance view.
Item Name:
Approve Bank Payments
6 Select Configuration Steps Choose Configure to configure the following row: The Change View "Define Rules for Reversing Rejected Payments":
Step Name: Define Rules for Reversing Rejected Payments Overview displays.

Appendix PUBLIC 66
# ment
7 Specify Rule Choose New Entries and make the following entries and choose Save: The rule for Automatically Reversing Rejected Payments is defined.
For example:
Sequence Number: 1
Paying Company Code: 1010
Payment Method: <blank>
House Bank: DEBK1
Account ID: DEAC1
Reversal Reason: 01
Payment Block: A

Step # Comment
2 Open Define Rules for Re- In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the The Change View “Define Rules for Automatically Re-
versing Rejected Payments activity in the tree view, search for the following activity: Define Rules for Reversing Rejected Payments. versing Rejected Payments”: Overview screen displays.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launch-
pad as a Configuration Expert - Business Process Configuration.
7 Specify Rule Choose New Entries and make the following entries and choose Save: The rule for Automatically Reversing Rejected Payments
For example: is defined.
Sequence Number: 1
Payment Method: <blank>
House Bank: DEBK1
Account ID: DEAC1
Reversal Reason: 01
Payment Block: A

Appendix PUBLIC 67
2.6.9.2 Create Team for Reversing Rejected Payments
Purpose
In this activity, you create a team to specify responsibilities for reversing rejected payments.
Procedure
Execute the Create Team steps in the Responsibility Management (1NJ) test script with the following information:
Team Information tab
Team Name: Team for Reversing Payments
Description: Team for automatically reversing rejected payments
Global ID: PAYMENT_REVERSE
Status: Enabled
Type: SFSCM_BCMR (Category FSCM_BCM)
Responsibility Definition tab
Company Code: 1010
Note If fields are empty, the team is responsible for all company codes.
Team Members tab

Business Partner: <user ID>, for example, AP_Accountant
Functions: SFSCM_BCMR
Note To display the connection between the business partner, AP accountant, and user ID, see the search help. Generic users are described in the Last Name field.

Appendix PUBLIC 68
2.6.10 Situation Handling
2.6.10.1 Situation Handling for Cash and Liquidity Management
Purpose
In this activity, you create a team to specify responsibilities for the review process.
Procedure
Execute the Create Team steps in the Responsibility Management 1NJ test script with the following information:
Team Information tab:
Team Name: Team for Cash Management
Global ID: SFCLM1_A
Description: Situation team for cash and liquidity Management
Team Status: Enabled
Type: SFCLM1
Responsibility Definition tab:
Company Code: 1010
Note If fields are empty, the team is responsible for all company codes.
Team Members tab:

Business Partner: <user ID>, for example, Cash Manager
Functions: SFCLM_TD
Note To display the connection between the business partner, cash manager, and user ID, see the search help. Generic users are described in the Last Name field.

Appendix PUBLIC 69
2.6.10.1.2 Create Situation Types: Date Difference Warning for FI Flows
Test Administration
Purpose
In this activity, you can use the situation template FIN_FQM_FIDATE_DIFFERENCE to create a situation type. The situation type is used to inform specific users when the system detects an FI
cash flow for which the difference between the posting date and the value date does not meet the defined condition.
Prerequisite
If you want to trigger notification and check it. Please make sure you have posted a FI cash flow for which the difference between the posting date and the value date has exceeded the defined toler-
ance.
For example, in our testing case, tolerance is greater than or equal to 30 days under your company code.
Procedure

Step # Comment

2 Access the SAP Open Manage Situation Types (F2947).

Fiori app
3 Copy Situation Select the checkbox for standard template FIN_FQM_FIDATE_DIF- The Situation Type view is displayed.

Appendix PUBLIC 70
Step # Comment
Types template FERENCE and choose Copy. This standard template is used to inform specific users when the system detects an FI cash flow for
which the difference between the posting date and the value date has exceeded the defined tolerance.
4 Define Condition Make the following entries: The ZFIN_FQM_FIDATE_DIFFERENCE view displays.
Admin Information tab:
ID: ZFIN_FQM_FIDATE_DIFFERENCE
Conditions tab:
Company Code: 1010
Date Difference (Days): greater than or equal to 30
Fiscal Year: <current fiscal year>
5 Batch Job Sched- In Batch Job Scheduling Tab, make the following entries:
uling Time Zone: for example UTC
Start Batch Job At: for example <your time>
6 Add Team Cate- In the Recipients area, choose Add Team Category. On the dialog box,
gory select FCLM1 - Cash and Liquidity Management and choose Select.
7 Maintain Respon- For team category FCLM1 - Cash and Liquidity Management, make the
sibility by Teams following entries:
Filter by Responsibility Definition: Company Code
Filter by Member Function: Check Transaction Data in One
Exposure
8 Situation Monitor- In the Situation Monitoring area, select checkbox for Monitor Instances.
ing
9 Create Choose Create. Choose Yes to confirm the message Enable Situation The situation type is created and enabled.
Type.
10 Trigger Now Choose Trigger Now at the upper-right corner. The notification is triggered immediately. Situation Instances is shown.

Appendix PUBLIC 71
2.6.10.2 Situation Handling for Bank Communication Management
2.6.10.2.1 Define Function
Procedure
4 Application and Subapplication area Application Area: Application Platform and Infrastructure
Sub Application Area: Responsibility Management
5 Select Configuration Item Item Name:

Functions
6 Select Configuration Steps Choose Configure to configure the following row: The "Define Functions": Change displays.
Step Name: Define Functions
7 Create Function Choose New Entries and make the following entries and choose Save:
Function: for example, <BCM_FUNC>
Function Description: for example, <Function for BCM batch>

Appendix PUBLIC 72
Step # Comment
2 Open Define In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree view, The "Define Functions": Change
Functions search for the following activity: Define Functions. screen displays.
3 Create Function Choose New Entries and make the following entries and choose Save:
Function Description: for example, <Function for BCM batch>
2.6.10.2.2 Define Function Profiles
Purpose
In this step, you can create function profiles and assign functions to a function profile. You can group similar functions for a business process in a function profile.
Procedure
# ment
tion.

Appendix PUBLIC 73
# ment
4 Application and Subapplica- Make the following entries: Selected application area items are displayed in the Configu-
tion area Application Area: Application Platform and Infrastructure ration Items view.
Item Name:
Functions
6 Select Configuration Steps Choose Configure to configure the following row: The Change View “Function Profile”: Overview displays.
Step Name: Define Function Profiles
7 Create Function Profile Choose New Entries and make the following entries and choose Save: The function Profile is created for BCM Batch.
For example:
Profile: <BCM_PROF>
Function Profile Description: for example, <Function Profile for BCM batch>
8 Assign Function to Function Choose Function Profile to Function Mapping in the left-side Dialog Structure. Enter follow- The function is assigned to the function profile.
Profile ing entries and Choose Save.

Step # Comment
2 Open Define Function In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree The Change View “Function Profile”:
Profiles view, search for the following activity: Define Function Profiles. Overview screen displays.
3 Create Function Profile Choose New Entries and make the following entries and choose Save: The function Profile is created for BCM
For example: Batch.
Profile: for example, <BCM_PROF>

Appendix PUBLIC 74
Step # Comment
Function Profile Description: for example, <Function Profile for BCM batch>
4 Assign Function to Choose Function Profile to Function Mapping in the left-side Dialog Structure. Enter following entries and Choose Save. The function is assigned to the function
Function Profile Function: <BCM_FUNC> profile.
2.6.10.2.3 Assign Function Profiles to Standard Team Category
Purpose
In this step, you can assign a function profile to a standard team category.
Procedure
# ment

Application Area: Application Platform and Infrastructure tion Items view.
Item Name:

Appendix PUBLIC 75
# ment
Teams
6 Select Configuration Steps Choose Configure to configure the following row: The "Assign Function Profiles to Team Category": Change dis-
Step Name: Assign Function Profiles to Standard Team plays.
Category
7 Map Function Profiles to Standard Team Choose New Entries and make the following entries and choose Save: The function profile is mapped to standard Team Category.
Category For example:
Team Category: BCM

Step # Comment
2 Open Assign Function Profiles In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in The "Assign Function Profiles to Team
to Standard Team Category the tree view, search for the following activity: Assign Function Profiles to Standard Team Category. Category": Change screen displays.
3 Map Function Profiles to Stan- Choose New Entries and make the following entries and choose Save: The function profile is mapped to standard
dard Team Category For example: Team Category.
Team Category: BCM


Appendix PUBLIC 76
2.6.10.2.4 Define Team Types
Purpose
In this step, you can assign a function profile to a standard team category.
Procedure
# ment
Configuration.
area Application Area: Application Platform and Infrastructure Items view.
Item Name:
Teams
6 Select Configuration Steps Choose Configure to configure the following row: The Change View “Team Type”: Overview displays.
Step Name: Define Team Types
7 Define Team Types Choose New Entries and make the following entries and choose Save: The team type is defined.
For example:
Team Type: for example, <BCM_TEAM>
Team Category: BCM

Appendix PUBLIC 77
# ment
Team Type Description: <Team Type for Bank Communication Man-

agement>

Step # Comment
2 Open Define In the Product-Specific Configuration phase, navigate to the Configuration Activities tab. To locate the activity in the tree The Change View “Team Type”: Over-
Team Types view, search for the following activity: Define Team Types. view screen displays.
Choose the link to navigate directly to the SAP S/4HANA Cloud system. Log on to the SAP Fiori launchpad as a Configura-
tion Expert - Business Process Configuration.
3 Define Team Choose New Entries and make the following entries and choose Save: The team type is defined.
Types For example:
Team Type: for example, <BCM_TEAM>
Team Category: BCM
Team Type Description: <Team Type for Bank Communication Management>
Purpose
In this activity, you create a team to specify responsibilities for the review process.
Procedure
Execute the Manage Teams and Responsibilities steps in the Responsibility Management 1NJ test script with the following information:

Appendix PUBLIC 78
Team Information tab:
Team Name: Team for Bank Communication Management
Global ID: BCM_TEAM
Description: Situation team for Bank Communication Management
Team Status: Enabled
Type: SBCM
Responsibility Definition Tab:
Company Code: 1010
If fields are empty, the team is responsible for all company codes.
Team Members tab:
Business Partner: <user ID>, for example, AP Accountant
Functions: S_BCMMON_F
To display the connection between the business partner, cash manager, and user ID, see the search help. Generic users are described in the Last Name field.
2.6.10.2.6 Create Situation Types: Payment Batch Partially Rejected
Test Administration
Purpose
In this activity, you can use the situation template FIN_BCM_BATCH_PARTIALLY_REJECTED to create a situation type. The situation type is used for Situation Handling that informs specific
members of your team about payment batches that were partially rejected.
Note This situation template is available for payment batches and navigates to the SAP Fiori app Monitor Payments.

Appendix PUBLIC 79
Procedure

Step # Comment

2 Access the SAP Open Manage Situation Types(F2947). The Situation Type view displays.
Fiori app
3 Copy Situation Select the checkbox for standard template FIN_BCM_BATCH_PAR- The situation type FIN_BCM_BATCH_PARTIALLY_REJECTED is used to inform specific users
Types template TIALLY_REJECTED and choose Copy. when the system detects the BCM batch is partially rejected by bank.
4 Define Condition Make the following entries:

ID: Z_FIN_BCM_BATCH_PART_REJECTED
Name: Payment Batch Partially Rejected
Display Sequence: Medium
Conditions tab:
You can maintain other filters per your requirement
5 Maintain Responsi- For Team Category BCM Bank Communication Management, make the
bility by Teams following entries:
Filter by Responsibility Definition: Paying Company Code
Filter by Member Function: Bank Communication Monitoring
（S_BCMMON_F)
6 Situation Monitor- In Situation Monitoring, select the checkbox for Monitor Instances.
ing
7 Create Choose Create. Choose Yes to confirm the message Enable Situation The situation type is created and enabled.
Type.

Appendix PUBLIC 80
2.6.10.2.7 Create Situation Types: Payment Batch Was Rejected
Test Administration
Purpose
In this activity, you can use the situation template FIN_BCM_BATCH_REJECTED to create a situation type. The situation type is used for Situation Handling that informs specific members of your
team about payment batches that were rejected.
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert -

Business Process Configuration.
2 Access the SAP Fiori Open Manage Situation Types(F2947).

app
3 Copy Situation Types Select the checkbox for standard template FIN_BCM_BATCH_RE- The situation type FIN_BCM_BATCH_REJECTED is used to inform specific users when the sys-
template JECTED and choose Copy. tem detects the BCM batch is fully rejected by bank.

ID: Z_FIN_BCM_BATCH_REJECTED

Appendix PUBLIC 81
Step # Comment
Name: Payment Batch Was Rejected

Conditions tab:
You can maintain other filters according to your requirement.
5 Maintain Responsibil- For team category BCM Bank Communication Management, make
ity by Teams the following entries:
Filter by Member Function: Bank Communication Moni-
toring（S_BCMMON_F)
7 Situation Monitoring In the Situation Monitoring tab, choose the Monitor Instances
checkbox.
8 Create Choose Create. Choose Yes to confirm the message in the Enable The situation type is created and enabled.
Situation Type dialog box.
2.6.10.2.8 Create Situation Types: Payment Batch Status Check
Test Administration

Appendix PUBLIC 82
Purpose
In this activity, you can use the situation template FIN_BCM_BATCH_STATUS_CHECK to create a situation type. The situation type is used for Situation Handling that informs specific members
of your team about payment batches that are stuck in a defined status. The status check is triggered daily. It’s possible to define the statuses for which the notification is triggered and also for how
many days the payment batch must be stuck in the defined status for a notification to be sent.
Prerequisite
Please make sure the BCM batch is created with the relevant status, such as Payment Batch Created, Payment Medium Created… which is defined in your situation type.
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Configuration Expert -

Business Process Configuration.
2 Access the SAP Open Manage Situation Types(F2947).

Fiori app
3 Copy Situation Select the checkbox for standard template The situation type is used to inform specific users when the system detects the specific BCM batch status
Types template FIN_BCM_BATCH_STATUS_CHECK and choose Copy. which is defined in the situation type Z_FIN_BCM_BATCH_STATUS_CHECK.

ID: Z_FIN_BCM_BATCH_STATUS_CHECK
Name: Payment Batch Status Check
Conditions tab:
Status: for example, IBC01 (Payment batch created), IBC15
(Payment medium created)
Batch Job Scheduling section:
Time Zone: for example UTC

Appendix PUBLIC 83
Step # Comment
Start Batch Job At: for example <your time>
5 Maintain Responsi- For team category Bank Communication Management, make the
bility by Teams following entries:
Filter by Member Function: Bank Communication Moni-
toring（S_BCMMON_F)
7 Situation Monitor- In Situation Monitoring, select checkbox for Monitor Instances.

ing
8 Create Choose Create. Choose Yes to confirm the message Enable Situ- The situation type is created and enabled.
ation Type.
9 Trigger Now Choose Trigger Now at the upper-right corner. The notification is triggered immediately. Situation Instances is shown.
Note For batch/job situation, you can choose Trigger Now to

trigger the notification immediately.

Appendix PUBLIC 84
3 Overview Table
This scope item consists of several procedures provided in the tables below.
Note If your system administrator has enabled spaces and pages on the SAP Fiori launchpad, the homepage will only contain the essential apps for performing the typical tasks of a business
role.
You can find all other (searchable) apps not included on the homepage using the search bar (2434549).
If you want to personalize the homepage and include the hidden apps, navigate to your user profile and choose App Finder.
Outgoing Payment With BCM Approval

Table 2: Approval and Bank Integration
Process Step, Report or Item Business Role Transaction/App Expected Results
BCM Batch Creation [page ] 93 This step is done automatically
Monitor Payments [page ] 93 Accounts Payable Accountant Monitor Payments (F2388) Check status of payments.
Check Cash Flow Items (Before Approval) [page ] 95 Cash Manager Check Cash Flow Items (F0735) Review detailed information of payment documents.
Approval of Bank Transfer [page ] 96 Accounts Payable Manager & Cash A Bank Communication Management (BCM) batch is approved, the payment
Manager medium is created automatically.
Approval by First Approver [page ] 97 Accounts Payable Manager Approve Bank Payments The batch status is In Approval. The next approvers is displayed.
(F0673A)
Reject by First Approver (Option) [page ] 98 Accounts Payable Manager Approve Bank Payments A Bank Communication Management (BCM) batch is rejected during bank pay-
(F0673A) ment approval process by kind of reasons.
Process Rejected Payments (Option) [page ] 100 Accounts Payable Accountant My Inbox - Process Rejected Pay- The rejected payment is reversed.
ments (F4546)
Approval by Second Approver [page ] 101 Cash Manager Approve Bank Payments The batch status is Payment Medium Created. The Reference Number is generated.
(F0673A)
Bank Integration with SAP Multi-Bank Connectivity Role dependent upon procedure Transaction/App dependent upon Results dependent upon procedure
(16R) (Outgoing) [page ] 103 procedure
Monitor Payments with SWIFT GPI Reason Codes Accounts Payable Accountant Monitor Payments (F2388) The Monitor Payments app incorporates SWIFT gpi reason codes to indicate the
[page ] 103 status of payments.
Situation Handling for Payments Batch

Appendix PUBLIC 85
Process Step, Report or Item Business Role Transaction/App Expected Results
Situation Handling : Payment Batch Partially Rejected
Monitor Situations [page ] 104 Configuration Expert - Business Monitor Situations (F3264) You can monitor situations and check instance details.
Process Configuration
Check Notification [page ] 106 a recipient (for example, AP Accoun- The detailed payment information is checked.
tant)
Situation Handling : Payment Batch Was Rejected
Check Notification [page ] 108 a recipient (for example, AP Accoun- The notification is checked by the recipient who is assigned to team members in the
tant) preliminary step.
Situation Handling : Payment Batch Status Check
Check Notification [page ] 110 a recipient (for example, AP Accoun- The notification is checked by the recipient who is assigned to team members in the
tant) preliminary step.
Bank Integration with File Interface (1EG) (Outgoing) Role dependent upon procedure Transaction/App dependent upon Results dependent upon procedure
[page ] 111 procedure
Monitor Payments with SWIFT GPI Reason Codes Accounts Payable Accountant Monitor Payments (F2388)
[page ] 103
Check Cash Flow Items (Check Status) [page ] 112 Cash Manager Check Cash Flow Items (F0735) Review detailed information of payment documents
Bank Transfer Actions
Process Step Business Role Transaction/App Expected Results
Initiate Bank Transfer
Option 1: Create, Release and Clear Payment Request in One Single Cash Management Special- Make Bank Transfers (F0691) A payment request for bank transfer is created,released and paid in

Appendix PUBLIC 86
Action [page ] 115 ist one step.
Option 2: Create, Release, and Clear Payment Request in Separate Cash Management Special- Make Bank Transfers (F0691) A payment request for bank transfer is created,released and paid in
Steps [page ] 118 ist individual steps.
Option 2: Create Bank Transfer [page ] 118 Cash Management Special- Make Bank Transfers (F0691) A payment request via bank transfer is created.
ist
Option 2: Release Payment Request [page ] 120 Cash Management Special- Make Bank Transfers (F0691) The payment request is released.
ist
Option 2: Pay Payment Request [page ] 121 Cash Management Special- Make Bank Transfers (F0691) The payment request is paid.
ist
Option 3: Make Bank Transfer with Templates
Option 3: Define Bank Transfer Templates [page ] 123 Cash Management Special- Define Bank Transfer Templates (F3759) Bank transfer templates is created
ist
Option 3: Create Bank Transfers with Templates [page ] 125 Cash Management Special- Make Bank Transfers - Create with Templates A payment request for bank transfer is created with Templates.
ist (F3760)
Option 3: Release Payment Request [page ] 127 Cash Management Special- Make Bank Transfers (F0691) The payment request is released.
ist
Option 3: Pay Payment Request [page ] 127 Cash Management Special- Make Bank Transfers (F0691) The payment request is paid.
ist
Approve and Bank Integration [page ] 128 Role dependent upon pro- Transaction/App dependent upon procedure Results dependent upon procedure
cedure
Check Cash Position (Smart Business) [page ] 128 Cash Manager Cash Position - Today (F1737) Check the cash position by country, currency, company code or bank.
Cash Trade Request
Create and Submit Cash Trade Request for FX [page ] 130 Cash Management Special- Reconcile Cash Flows - Intraday Memo Records (F3418) Cash trade request for FX is created and sub-
ist mitted

Appendix PUBLIC 87
Create and Submit Cash Trade Request for Money Market Cash Management Special- Reconcile Cash Flows - Intraday Memo Records (F3418) Cash trade request for MM is created and
[page ] 132 ist submitted
Release Cash Trade Request [page ] 133 Cash Manager Manage Memo Records (F2986) Release Cash Trade Request
Reject Cash Trade Request (Optional) [page ] 134 Cash Manager Manage Memo Records (F2986) Reject Cash Trade Request
Treasury Management Integration for Trading Platform [page ] Role dependent upon proce- Follow the relevant procedure in the Treasury Trading via Trading Plat- Send cash trade request
135 dure forms test script.
Fulfill Cash Trade Request as Deal Done [page ] 136 Cash Manager Manage Memo Records (F2986) Cash trade request fulfilled.
Cancel Cash Trade Request as Deal Cancel [page ] 137 Cash Manager Manage Memo Records (F2986) Cash trade request canceled.
Check Partial Fulfill or Partial Decline Cash Trade Request Sta- Cash Manager Manage Memo Records (F2986) Cash trade request is in process or completed.
tus [page ] 138
Reconcile Cash Flows - Intraday Memo Records (Old Reconciliation Model)
Schedule Intraday Memo Records Reconciliation Cash Management Spe- Schedule Intraday Memo Records Reconciliation Reconcile Cash Flows and Intraday Memo Records
[page ] 141 cialist (F5284)
Check Automatic Reconciliation Result [page ] 143 Cash Management Spe- Reconcile Cash Flows - Intraday Memo Records You can view automatically reconciled intraday memo records and forecasted
cialist (F3418) cash flows.
Perform Manual Reconciliation [page ] 144 Cash Management Spe- Reconcile Cash Flows - Intraday Memo Records You can manually reconcile intraday memo records with any forecasted cash
cialist (F3418) flows.
Undo Reconciliation [page ] 146 Cash Management Spe- Reconcile Cash Flows - Intraday Memo Records You can undo reconciliations for selected items and reset them to the open sta-
cialist (F3418) tus.

Appendix PUBLIC 88
Reconcile Cash Flows - Intraday (New Reconciliation Model)
Perform Manual Reconciliation [page ] Cash Management Specialist Reconcile Cash Flows - Intraday Memo Records Reconcile Cash Flows and Intraday Memo Records
148 (F3418)
Undo Reconciliation [page ] 150 Cash Management Specialist Reconcile Cash Flows - Intraday (F3418A) You can undo reconciliations for selected items and reset them to the open status.
Manage Bank Account Balances
Create Bank Account Balances [page ] 152 Cash Management Specialist Manage Bank Account Balances (F5175) Enter or upload the balances for bank accounts. You can also edit it.
Import Bank Account Balances [page ] 153 Cash Management Specialist Manage Bank Account Balances (F5175) The Balance of relevant Bank Accounts is updated massively.
Edit Bank Account Balances [page ] 154 Cash Management Specialist Manage Bank Account Balances (F5175) Bank Account Balances is edited.
Check Bank Account Balances [page ] 155 Cash Management Specialist Manage Bank Account Balances (F5175) The difference between ledger balance and value date balance is showed.
Manage Liquidity Item Transfer [page ] 156 Cash Management Specialist Manage Cash Pools (Version 2) (F3266A) A cash pool hierarchy is created.
Situation Handling: Date Difference Warning for FI Flows
Monitor Situations [page ] 158 Configuration Expert - Business Process Configura- Monitor Situations (F3264) You can monitor situations and check instance details.
tion
Check Notification [page ] Cash Manager The notification is checked by the recipient who is assigned to team members in preliminary step.
159

Appendix PUBLIC 89
Cash Reports
Check Cash Position (Smart Business) [page ] Cash Manager Cash Position - Today (F1737) Check the forecast cash positions for the current date by location, company, and currency.
160
Check Liquidity Items on G/L Accounts Cash Manager Check Liquidity Items on G/L Accounts You can check liquidity items on G/L Accounts.
[page ] 161 (F6459)
Check Cash Flow Items [page ] 162 Cash Manager Check Cash Flow Items (F0735) Track and trace all the cash flow items from different source applications. Also check line item
detailed of the original documents.
Schedule Jobs for Bank Statement Monitor Accounts Receivable Schedule Jobs for Bank Statement Monitor You can execute schedule jobs for bank statement monitor.
[page ] 164 Accountant (F6866)
Bank Statement Monitor [page ] 167 Cash Manager Bank Statement Monitor - End of Day Monitor the import status of end-of-day bank statements for all the bank accounts selected for
monitoring.
Intraday Bank Statement Monitor [page ] 168
Define Monitoring Rules for Intraday Bank Cash Management Define Monitoring Rules - Intraday Statements The monitoring rules with frequency for the intraday bank statement is defined.
Statement Monitor [page ] 169 Specialist (FCLM_BRM_RULE)
Assign Monitoring Rule to Bank (Optional) Cash Management Manage Banks - Basic (F1574) Monitoring rule is assigned to bank.
[page ] 170 Specialist
Define Bank Account to Monitor [page ] 171 Cash Management Manage Bank Accounts (F1366A) The bank account is set to be monitored by the Bank Statement Monitor - Intraday (F3671)
Specialist App with monitoring rule
Monitor Intraday Bank Statement [page ] 172 Cash Management Bank Statement Monitor - Intraday (F3671) Monitor the intraday bank statement.
Specialist
Monitor Bank Account Balances [page ] 174 Cash Manager Monitor Bank Account Balances (F5176) You can monitor whether bank account balances have been imported or entered in time for bank
accounts.
Schedule Jobs for Bank Account Balance Ini- Cash Management Schedule Jobs for Bank Account Balance Initial- You can schedule jobs to identify these bank accounts and replicate bank account balances from
tialization [page ] 175 Specialist ization (F7146) their latest end-of-day bank statements to cash management.
Short Term Cash Positioning [page ] 178 Cash Manager Short-Term Cash Positioning (F5380) The short-term cash position information per your predefined cash position profile can be
checked.
Cash Flow Analyzer [page ] 180 Cash Manager Cash Flow Analyzer (F2332) View the aggregated amounts and line item details of cash position, medium-and-long term liq-
uidity forecast and actual cash flows.

Appendix PUBLIC 90
Cash Flow Comparison – By Date Range Cash Manager Cash Flow Comparison - By Date Range Compare actual cash flows with your forecasts.
[page ] 184 (F3274)
Cash Flow Comparison – By Timestamp [page Cash Manager Cash Flow Comparison - By Timestamp Compare actual cash flows with your forecasts.
] 185 (W0137)
Display Status of Payment Docu- Accounts Payable Display Status of Payment Docu- You can see the payment item’s status of payment batches and/or payment run documents at a glance without the need to
ments [page ] 186 Accountant ments (F7084) do a drill down from batch level to single item level.

Appendix PUBLIC 91
4 Test Procedures
This section describes test procedures for each process step that belongs to this scope item.
4.1 Outgoing Payment with BCM Approval Process
4.1.1 Approval and Bank Integration
Prerequisite
Before testing the steps under Approval and Bank Integration, ensure that at least one of the following procedures has been completed:
1. Maintain Payment Approver for Bank Accounts before Batch creation (refer to Maintain Payment Approver for Bank Accounts [page ] 36)
2. Batch is created successfully. Batch can be automatically generated via one of the following procedures:
• Bank transfer (refer to the Bank Transfer Actions section).
• Payment run using the Manage Automatic Payments (F0770), as described in Accounts Payable J60 test script.
• Free form payment is described in Accounts Payable (J60) test script.
• Others.
Purpose
This section provides procedures for how the outgoing payment of a bank transfer is approved, whether it comes from a payment run for vendor or an initiated bank transfer.
After payment approval, the payment medium file is created. If PMW Format’s Alternative Format Type is marked with 90 SAP Multi-Bank Connectivity, the payment medium files are automati-
cally sent the house bank via SAP Multi-Bank Connectivity for further processing (as described in the Bank Integration with SAP Multi-Bank Connectivity (16R) test script.)
Outgoing payments always updates the cash position, so the cash manager can review detailed cash position information, analyze the payment details or even verify the FI document.
After Approval and Bank Integration is processed, in the Cash Operations -Common Steps section (as described in the Basic Cash Operations (BFB) test script), the Bank Statement, Memo Record,
and Cash Reports procedures can be tested.
Note You must create the BCM batch with the payment method using the Payment Medium Workbench (PMW) format, then approvals are possible for the BCM batch.
When the payment methods for file downloading use the Classic Payment Medium Program in SAP S/4HANA Enterprise Management, use the Schedule Automatic Payments Periodically SAP
Fiori app for payment runs. However no BCM batch can be created or approved for the Classic Payment Medium Program.

Appendix PUBLIC 92
Note Grouping of different bank accounts into one payment file is not possible. KBA 3257630 - Group different bank accounts into one payment file not possible created.
4.1.1.1 BCM Batch Creation
Context
The creation of the cross-payment run in bank communication management (BCM Batch) is done automatically after the payment is initiated.
Note If the batch is not created successfully. You can use the App: Manage Automatic Payments (F0770) or Automatic Payment Transactions for Payment Requests (F111) to check applica-
tion log for your payment run ID.
Note If the approval list in the bank master data is empty, all payment will be rejected or approved depending on the value customized in preliminary step Define Automatic Approval/Rejection
for Bank Account Master data.
Note Please make sure the Basic Settings is set as Full Scope, you can check it via SSCUI 101025. If not, the batch can not be created.
Procedure
This step is done automatically.
4.1.1.2 Monitor Payments
Test Administration

Appendix PUBLIC 93
Context
In the Monitor Payments (F2388) app, you can display an overview of your payment batches. You can view the statuses of batches and individual payments at different processing stages.
In different stages of a BCM batch's lifecycle, the app displays different batch/batch item status.
● Payment Batch Created: Batch is created and waits for first approval.
● In Approval: Batch is approved at least once, though not final approval.
● Payment Medium Created: Batch successfully completes approval process and the payment medium is created.
● Accepted by Bank: The payment medium has been sent to the bank and the bank sends responds with a payment status message accepting the payment instruction. This can also be fulfilled
through Multi-Bank Connectivity (MBC).
● Stmt. Received: Batch is reconciled by a bank statement.
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as an Accounts Payable

Accountant.
2 Access the SAP Open Monitor Payments (F2388).

Fiori App
3 Find the Newly Maintain your filter and choose Go. Choose the New tab. All newly created batches are displayed on the New tab. You can find the batch you created earlier in the process.
Created Batch
4 Verify the Verify the batch status in the Bank Status Text column. The Note If the approval list in bank master data is empty, all payment will be rejected or approved depending on the
Batch Status status should be Payment Batch Created. value customized in the Define Automatic Approval/Rejection for Bank Account Master Data preliminary step in
the Advanced Cash Operations (J78) test script.
5 Check Details Select your cash flow item, and choose > (Details). Detailed information for this batch is displayed.
6 Check Ap- In the header section, choose Approvers to check who are All approvers used in the first approver step are shown (for example: Accounts Payable Manager).
prover the first approvers for the batch. Close the dialog box when
you are done.

Appendix PUBLIC 94
4.1.1.3 Check Cash Flow Items (Before Approval)
Test Administration
Context
In this activity, the Cash Manager or Bank Accountant reviews the detailed information of payment documents before approval.
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Cash Manager.
2 Access the SAP Fiori app Open Check Cash Flow Items (F0735). The Check Cash Flow Item view displays.
3 Enter Selection Criteria Choose Adapt Filters if selection fields are hidden. The list is filtered to show fewer entries.
Make the following entries and choose Go.
Exchange Rate Type: <M>
Snapshot Time: <default value>
Value Date: <Today>
Company Code: 1010
Certainty Level: <choose all certainty levels>
Account Number: 1133698
Cash Flow View for Accounting: 2(Cash Position) or 3(Liquidity
Analysis)

Appendix PUBLIC 95
# ment
4 Display Additional Payment Infor- Select your cash flow item, and choose > (Details) to check details information. More payment information is displayed.
mation
Note Different source applications display different payment in-

formation.
4.1.1.4 Approval of Bank Transfer
Context
In the SAP S/4HANA system, a Bank Communication Management (BCM) batch should be approved by approvers according to the approval pattern in preconfiguration.
After the approval process is done, the payment medium is created automatically.
No matter the source of a BCM batch, payment run of vendors/customers,or payment run of bank transfer, the BCM batch should go through the approval process.
Note
● The 5 payment method IDs (E, Q, R, &, @) are marked as automatic payment (No Approval). No approval process is required.
● The approver for a payment cannot be its creator. Payments created by the approver do not appear in the app Approve Bank Payments (F0673A)
● If the payment or batch amount is greater than the Maximum amount maintained in the Bank Account Master, no payment approver can be found for the batch. The payments also do not ap-
pear in the app Approve Bank Payments (F0673A)
Note You have the option to enable two-factor authentication using SAP Cloud Platform Identity Authentication (IAS) for the Approve Bank Payments app. See preliminary step Specify Op-
tional User Authentication. If you enable two-factor authentication, the business user submitting payment batches for processing by the bank will be asked to authenticate their identity before
the batches can be submitted.
Prerequisites
Payment approver is maintained for bank accounts. BCM batches are created successfully.

Appendix PUBLIC 96
4.1.1.4.1 Approval by First Approver
Test Administration
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as an Accounts Payable Manager.
Note The user assigned to Signatory Group G001 in the Prerequisites section, Maintain Payment Ap-
prover for Bank Accounts.
2 Access the SAP Fiori Open Approve Bank Payments (F0673A).

app
3 Maintain Filters Make the following entries and choose Go.

4 Review Payment Batch Choose the For Review tab, review to ensure that the batches are correct. All items are correct and the batches can be approved.
and Items
5 Select Batch to be Ap- Select the payment batch for approval.

proved If more than one batch must be approved, select the checkbox for the batches to approve.
6 Approve Choose Approve. Enter the note and choose OK to confirm the dialog box. The payment is approved and appears on the Reviewed
tab.
7 (Optional) Undo Ap- Choose the Reviewed tab and select the payments to be discarded. The payment is discarded. it displays on the For Re-

Appendix PUBLIC 97
Step # Comment
proval Choose Discard Changes from the top right of the view. view tab.
To confirm the dialog box, choose Discard Changes.
Note This optional step is only necessary when you want to undo the approval.
8 Submit Reviewed Batch Choose the Reviewed tab and select the payments to be submitted. Choose the Approve and Submit button. The batch is submitted.
To confirm the dialog box, choose Submit.
(Op- Submit Verification To- On the dialog box Confirm Submission of Reviewed Batches, make the following entry and choose Submit.
The payment is sent to the Second Approver and no
tional) ken (Optional) VerificationToken: < Insert the Passcode from App SAP Authenticator on your mo- longer appears on the Reviewed tab.
bile phone and insert it here>
Note This step is only required when you enable two-factor authentication using SAP Cloud Platform
Identity Authentication (IAS) for the Approve Bank Payments (F0673A) app.
9 Check Batch Status and Check the batch status and next approvers via App Monitor Payments (F2388), see step Monitor Payments. The batch status is In Approval. The next approvers is
Next Approver displayed. For example: Cash Manager.
4.1.1.4.2 Reject by First Approver (Option)
Test Administration
Purpose
A Bank Communication Management (BCM) batch is rejected during bank payment approval process by kind of reasons.

Appendix PUBLIC 98
Note If the Bank Communication Management (BCM) batch is rejected in this step, you can skip the next following step Approval by Second Approver.
Procedure
Test Test Step Instruction Expected Result Pass /

Step # Name Fail /
Comment
1 Log On Log on to the SAP Fiori launchpad as an Accounts Payable

Manager.
Note The user assigned to Signatory Group G001 in the

Prerequisites section, Maintain Payment Approver for
Bank Accounts [page ] 36.
2 Access the Open Approve Bank Payments (F0673A).

SAP Fiori
app
3 Maintain Fil- Make the following entries and choose Go.

ters Paying Company Code: 1010
4 Select Batch Choose the For Review tab, select the payment batch for re-
to be Re- jection.
jected If more than one batch must be rejected, select the check-
box for the batches to reject.
5 Reject Choose Reject. In the Confirm Reject dialog box, enter The payment is rejected and appears on the Reviewed tab.
some reason in Note, and choose OK.
6 Submit Re- Choose the Reviewed tab, choose the batch to reject, then The batch is submitted.
viewed Batch choose Submit. To confirm the Submission of Reviewed
Batches dialog box, choose Submit.
7 Check Batch Check the batch status and next approvers via App Monitor The batch status is change to Automatic Rejection. The payment status is also change to Rejected by Approver.
Status Payments (F2388), see step Monitor Payments.
Note If the reversal reasons and payment block for the rejected payments is defined in SSCUI mentioned in the Pre-
liminary Step Define Rules for Reversing Rejected Payments. the AP Accountant receives the rejected payment doc-
uments workflow in his My inbox app. You go on the next step Process Rejected Payments (Option).

Appendix PUBLIC 99
Test Test Step Instruction Expected Result Pass /
Step # Name Fail /
Comment
If not, skip next step and reverse it manually in the Reset Cleared Items app.
4.1.1.4.3 Process Rejected Payments (Option)
Test Administration
Purpose
In this activity, the AP Accountant receive the rejected payment documents workflow in his My inbox app, he could review the items and select all and click the button Confirm, then all the selected
payment documents to be reversed with reason defined in SSCUI mentioned in the Preliminary Steps Define Rules for Reversing Rejected Payments [page ] 66. He will be also notified by the sys-
tem notification as well.
Prerequisite
The reversal reasons and payment block for the rejected payments is defined in the SSCUI mentioned in the Preliminary Step Define Rules for Reversing Rejected Payments [page ] 66.
A Bank Communication Management (BCM) batch is rejected during the bank payment approval process by kind of reasons in the previous step.

Appendix PUBLIC 100
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as an Accounts Payable Accountant.
Note The user assigned to the team for Reversing Rejected Payments which is defined in the Preliminary step.
2 Access the SAP Open My Inbox - Process Rejected Payments (F4546).

Fiori app
3 Process Re- Double click your rejected payment batch in left side panel and choose Reverse. To confirm the dialog box, enter a note and choose Submit. Task successfully processed.
jected Pay- The rejected payment is re-
ments versed.
Note
● This payment was rejected in the bank payment approval process. You can choose Reverse or Keep Rejected.
● If you keep the payment rejected, the payment will not be sent to the bank. If you later want to reverse the payment, you need to manu-
ally reverse it in the Reset Cleared Items app.
● The payment will be reversed using the automatically specified reason for the reversal. The cleared items in the payment will be re-
opened. If the automatically specified payment block option confirms a block, the reopened items will be blocked and cannot be paid in
other payment runs.
● Whichever action you choose, the payment will then disappear from the list of rejected payments on the left.
4.1.1.4.4 Approval by Second Approver
Test Administration

Appendix PUBLIC 101
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Cash Manager. The SAP Fiori launchpad displays.
Note The user assigned to Signatory Group G002 in the Prerequisites section, Maintain Payment Approver for
Bank Accounts.
2 Access the SAP Fiori Open Approve Bank Payments (F0673A). The Approve Bank Payments app displays.
app
3 Maintain Filters Make the following entries and choose Go.

4 Review Payment Choose the For Review tab to ensure if the batches are correct. All items are correct and the batches can be ap-
Batch and Items proved.
5 Select Batch to be Ap- Select the payment batch for approval.

proved If more than one batch must be approved, select the checkbox for the batches to approve.
6 Approve Choose Approve. The global payment is approved and appears on

Choose OK to confirm the dialog box. the Reviewed tab.
7 Submit Reviewed Choose the Reviewed tab and select the payments to be submitted, choose Submit. The payment is submitted.
Batch On the dialog box, choose Submit.
(Op- Submit Verification On the Confirm Submission of Reviewed Batches dialog box, make the following entries and choose Submit: The payment is finally approved and no longer
tional) Token (Optional) VerificationToken: < Insert the Passcode from App SAP Authenticator on your mobile appears on the Reviewed tab.
phone and insert it here>, make the following entry and choose
Note This step is only required when you enable two-factor authentication using SAP Cloud Platform Identity
Authentication (IAS) for the Approve Bank Payments app.
8 Check Batch Status Check the batch status and next approvers via App Monitor Payments (F2388), see step Monitor Payments. The batch status is Payment Medium Created.
The Reference Number is generated.

Appendix PUBLIC 102
4.1.1.5 Bank Integration with SAP Multi-Bank Connectivity (16R) (Outgoing)
Purpose
If PMW Format’s Alternative Format Type is marked with 90 SAP Multi-Bank Connectivity, the payment medium files are automatically sent the house bank via SAP Multi-Bank Connectivity for
bank payment processing.
Procedure
Follow the steps in the Outgoing Integration test procedure of the Bank Integration with SAP Multi-Bank Connectivity (16R) test script.
Note As part of the Bank Statement Monitor section in this test script, perform the procedures in the Incoming Integration section of the Bank Integration with SAP Multi-Bank Connectivity
(16R) test script.
4.1.1.6 Monitor Payments with SWIFT GPI Reason Codes
Test Administration
Purpose
In this step, you can check the payment status with SWIFT gpi reason codes. The Monitor Payments app incorporates SWIFT gpi reason codes to indicate the status of payments. External entities,
such as banks, use reason codes to communicate the status of SWIFT gpi payments. Your entity receives these external Status Reason Codes and translates them into internal reason codes. One inter-
nal reason code may be mapped to many external reason codes.

Appendix PUBLIC 103
Prerequisite
You can follow the steps in the Preliminary Steps section to define your own internal reason codes and map external reason codes to them.
Also make sure Payment Medium Created and pain.002 format payment status with SWIFT gpi reason codes has been uploaded.
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as an Accounts Payable Accountant.
2 Access the SAP Fiori Open Monitor Payments (F2388). The Monitor Payments screen displays.
App
3 Batch Monitor Make the following entries and choose Go: All batches are displayed in the All Batches tab.
4 Choose Batch In Tab Sent to Bank, choose the Batch Status Text Accepted by Bank or
other status.
5 Check Status Reason In the header section, choose Status Reason Codes. The popup screen Status Reason Codes is shown with field Reason and Reason Status
Codes Reason Code.
4.1.1.7 Situation Handling for Payment Batch
4.1.1.7.1 Situation Handling: Payment Batch Partially Rejected
4.1.1.7.1.1 Monitor Situations
Test Administration

Appendix PUBLIC 104
Purpose
In this step, you can monitor situations and check instance details.
Prerequisite
You have performed the procedure Situation Handling for Bank Communication Management in Preliminary Step.
In order to trigger notification and check it, please make sure you have created the relevant transaction data.
For Situation Template FIN_BCM_BATCH_PARTIALLY_REJECTED, please make sure the BCM batch is partially rejected by bank.
For example, the payment is partially rejected via pain.002 file. You can refer to the step Pull Status Message from MBC of Test Script Bank Integration with SAP Multi-Bank Connectivity (16R) .
Procedure
2 Access the SAP Fiori app Open Monitor Situations (F3264).
3 Check Situation type for Payment Batch Partially Rejected Make the following entries:
Situation Type ID: Z_FIN_BCM_BATCH_PART_REJECTED
Year: <current year>
4 Check Instance Details In the Instance Details section, check detailed information for your situation type.

Appendix PUBLIC 105
4.1.1.7.1.2 Check Notification
Test Administration
Purpose
In this step, the notification is checked by the recipient who is assigned to team members in preliminary step.
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a recipient (for example, AP Accountant).
2 Check Notification for Situation Template On home page, choose Notifications on the upper right corner.
FIN_BCM_BATCH_PARTIALLY_REJECTED Choose By Type, under type Situation Payment Batch Partially Rejected has be…,
choose Expand Group.
3 Check Details Choose one item with Payment batch was partially rejected and navigate to App The detailed payment information
Monitor Payments (F2388). is checked.

Appendix PUBLIC 106
4.1.1.7.2 Situation Handling: Payment Batch Was Rejected
Test Administration
Purpose
Prerequisite
You have performed the procedure Situation Handling for Bank Communication Management in the Preliminary Step.
For Situation Template FIN_BCM_BATCH_REJECTED, please make sure the BCM batch is fully rejected by the bank.
For example, the payment is fully rejected via pain.002 file. You can refer to the step Pull Status Message from MBC of Test Script Bank Integration with SAP Multi-Bank Connectivity (16R).
Procedure

Appendix PUBLIC 107
3 Check Situation type for Payment Batch Fully Rejected Make the following entries:
Situation Type ID: Z_FIN_BCM_BATCH_REJECTED
4 Check Instance Details In Instance Details section, check detailed information for your situation type.
Test Administration
Purpose
In this step, the notification is checked by the recipient who is assigned to team members in the preliminary step.
Procedure
# ment
FIN_BCM_BATCH_REJECTED Choose By Type, under type Situation Payment Batch Was Rejected has be…,

Appendix PUBLIC 108
# ment
3 Check Details Choose one item with Payment batch was rejected and navigate to App Monitor Pay- The detailed payment information is
ments (F2388). checked.
4.1.1.7.3 Situation Handling: Payment Batch Status Check
Test Administration
Purpose
Prerequisite
You have performed the procedure Situation Handling for Bank Communication Management in the Preliminary Step.

Appendix PUBLIC 109
For Situation Template FIN_BCM__BATCH_STATUS_CHECK, please make sure the BCM batch is created with the relevant status, such as ‘Payment Batch Created, Payment Medium Created…’
which is defined in your situation type.
Procedure
3 Check Situation type for Payment Batch Status Check Make the following entries:
Situation Type ID: Z_FIN_BCM_BATCH_STATUS_CHECK
4 Check Instance Details In Instance Details section, check detailed information for your situation type.
Test Administration
Purpose
In this step, the notification is checked by the recipient who is assigned to team members in the preliminary step.

Appendix PUBLIC 110
Procedure
# ment
FIN_BCM_BATCH_STATUS_CHECK Choose By Type, under type Situation Payment Batch Status Check has be…,
3 Check Details Choose one item with Payment batch is stuck and navigate to App Monitor Pay- The detailed payment information is
ments (F2388). checked.
4.1.1.8 Bank Integration with File Interface (1EG) (Outgoing)
Context
The BCM batch is approved, the payment medium file is created and it can be downloaded manually in the App Manage Payment Media (F1868) as an Accounts Payable Accountant.
Procedure
Run steps in the Outgoing Integration section of the Bank Integration with File Interface (1EG) test script.
Note As part of the process flow for the Bank Statement Monitor procedure, in this test script, perform the procedures in the Incoming Integration section of the Bank Integration with File Inter-
face (1EG) test script.

Appendix PUBLIC 111
4.1.1.9 Check Cash Flow Items (Check Status)
Test Administration
Purpose
Within the Check Cash Flow Items app, the cash manager, bank accountant or AR/AP accountants can check the status of each single outgoing payment that is merged in a BCM batch.
In different stages of a BCM batch's lifecycle, different batch/batch item status is displayed in the Check Cash Flow Items app.
● Payment Batch Created: Batch is created and waits for first approval.
● In Approval: Batch is approved at least once, though not in final approval.
● Payment Medium Created: Batch successfully completes the approval process and the payment medium is created.
● Accepted by Bank: The payment medium has been sent to the bank and the bank responds with a payment status message accepting the payment instruction. This can also be fulfilled through
Multi-Bank Connectivity (MBC).
● Stmt. Received: Batch is confirmed by a bank statement.
Procedure

Step # Comment
1 Log on Log onto the SAP Fiori launchpad as a Cash Manager. The SAP Fiori launchpad displays.
2 Access the SAP Open Check Cash Flow Items (F0735). The Check Cash Flow Item screen displays.
Fiori app
3 Search Criteria Choose Adapt Filters if selection fields are hidden. The list is filtered to show fewer entries.
Make the following entries and choose Go.

Appendix PUBLIC 112
Step # Comment
Snapshot Time: <default value>

Exchange Rate Type: <M>
Value Date: <Today>
Company Code: 1010
Note Other fields keep default value, change it as needed.
4 Check Batch and Choose either the Batch Item Status Code or the Batch Status Code col- For the payment document with MBC payment medium format, after the steps in chapter Outgoing Inte-
Batch Item Sta- umns (scroll right to last columns) and check their status. gration of test script 16R - Bank Integration with SAP Multi-Bank Connectivity are executed success-
tus If you cannot find the Batch Item Status Code and the Batch Status Code fully, its status should be Accepted by Bank.
column, please change the layout. For the Payment document with a payment medium format for file download, after the steps in the chap-
ter Outgoing Integration of test script 1EG - Bank Integration with File Interface are executed success-
fully, its status should be Payment Medium Created.
5 Take Action The cash manager should take action for those batches or batch items
with inappropriate status (such as a batch created 10 days ago that has
not been approved or rejected).
4.2 Bank Transfer Actions
Purpose
This section describes the steps to make a bank transfer between two house bank accounts. For example, there is a deficit of a current bank account; the cash manager makes a decision to make a
bank transfer from another bank account.
Example Data:
There are two sample bank accounts provided:
Item Bank Account Bank Key House Bank / Account ID
Account 1 1133698 50070010 DEBK1/DEAC1
Account 2 2580061 82080000 DEBK2/DEAC2
You may make a bank transfer from bank account 1133698 to bank account 2580061, or from bank account 2580061 to bank account 1133698.

Appendix PUBLIC 113
Note
● Cross-company code bank transfer is not supported in preconfigured content. You need to define a clearing account between company codes via SSCUI: 100297.
● Also cross countries with different withholding tax is not supported.
Prerequisite
Make sure the relevant clearing accounts are maintained for your bank account. You can define the relevant clearing accounts via SSCUI:102803, 102802.
4.2.1 Initiate Bank Transfer
Context
You can make transfers between bank accounts in your company. For each transfer, the system creates a payment request. Depending on your company's process, you can either create and clear the
payment request in one single action, or create, release, and clear the payment request in separate steps.
You can also navigate from the Make Bank Transfers (F0691) app to the Make Bank Transfers - Create with Templates (F3760) app, to use repetitive codes to speed up internal work, create
payment requests in batches, and proceed with payment program for payment requests. To do this, you must have already created master data and relevant customizing settings for repetitive codes.
The app can be used with the Define Bank Transfer Templates (F3759) and Make Bank Transfers - Create with Templates (F3760) apps. As a result, bank-to-bank transfer and payment pro-
cesses become more transparent, structured and flexible, and cash management related functionalities become more comprehensive.
You are allowed to designate an instruction key for the payment requests while using app Make Bank Transfer - Create with Template and app Make Bank Transfer. An instruction key for data
medium exchange controls which statements are given to the participating banks when carrying out the payment. It is used in countries such as Germany, Austria, the Netherlands, Spain, Norway,
Finland, and Japan as well as for the international SWIFT formats.
You have three options for bank transfer:
1. Create, release, and clear the payment request in one single action by selecting the Release and Pay checkbox. See Option 1: Create, Release and Clear Payment Request in One Single Action
[page ] 115 task.
2. Create, release, and clear the payment request in separate steps by deselecting the Release and Pay checkbox. See Option 2: Create, Release, and Clear Payment Request in Separate Steps
[page ] 118 task.
3. Create a bank transfer with a template. For more information see the Option 3: Make Bank Transfer with Templates [page ] 123 task.

Appendix PUBLIC 114
4.2.1.1 Option 1: Create, Release and Clear Payment Request in One Single Action
Test Administration
Purpose
In this activity, you create, release and clear the payment request in one single action.
Prerequisite
The sample bank accounts exist, with payment signatories assigned to them. For more information, see the Maintain Payment Approver for Bank Accounts [page ] 36 section.
Procedure
Test Test Step Name Instruction Expected Result Pass /

Step # Fail /
Comment
1 Log on Log onto the SAP Fiori launchpad as a Cash Management Specialist. The SAP Fiori launchpad displays.
2 Access the SAP Fiori Open Make Bank Transfers (F0691).

app
3 Create, Release and To trigger a new bank transfer, choose Create. Make the following entries and choose The Make Bank Transfer screen displays, and the relevant payment request is created.
Pay Bank Transfer in Create: If the system does not find any configuration or input errors and the payment run is
one step (Option 1) successfully triggered for the payment request, the new bank transfer payment request
is successfully created and cleared.
Note Make a note of the payment request number: __________ (when you have

Appendix PUBLIC 115
Step # Fail /
Comment
done so, choose Close). Otherwise, the payment request stays in Released status.
Payer Information:
Paying Bank Account: 1133698
Paying House Bank: for example, DEBK1
Paying House Bank Account: for example, DEAC1
Payee Information:
Receiving Bank Account: for example, 2580061
Receiving Company Code: 1010
Receiving House Bank: for example, DEBK2
Receiving House Bank Account: for example, DEAC2
Note The descriptions for the two bank account fields are populated in display mode
after determination.
Transaction Information:
Transfer Date: <current date>
Payment Method: Choose an existing payment method for credit transfer.
Note Only payment methods that are applicable to the paying bank account are
listed.
Amount: for example, 1000EUR

Release and Pay: Selected
Note Select Release and Pay checkbox, the system automatically releases the pay-
ment re-quest and starts the payment run.
Payment Data: (option)

Single Payment: <select per your request>
Note If you want to designate instruction key for the payment re quests, enter fol-

Appendix PUBLIC 116
Step # Fail /
Comment
lowing instruction key & instruction fields.
Instruction Key: <via Value Help>

Instruction 1: <via Value Help>
Note The key is used as part of an argument when reading the information stored for
an instruction key (incl. instructions, cost allocation key and payment method for
DME, for example). Maintenance is done in SSCUI / Customizing.
Note Instructions can be defined 1) in document; 2) in master data record using an

instruction key; 3) in the house bank DME data using an instruction key; The in-
structions from the document are used with higher priority, provided that one of the
four fields has been filled out.
4 Search Bank Trans- Make the following entries and choose Go: The specified bank transfer entry with Cleared status is displayed in the Bank Transfer
fer Payment Request: <payment request number> worklist.
Note Choose Adapt Filters to show the Payment Request field.
5 Open Bank Transfer Choose the bank transfer entry. The bank transfer payment request is presented in the right side of the screen with
Cleared status. The Clearing Document No. field displays the clearing document num-
ber automatically.
6 Check Application In Application Log section, choose Search. The payment request info is presented in log details.
Log
Note
● If the payment request is not cleared and stays in Released status or the batch
is not created, you can read the message and also use the App: Automatic Pay-
ment Transactions for Payment Requests (F111) to check application log for
your payment run ID.
● You can check your payment status via App: Monitor Payments (F2388).

Appendix PUBLIC 117
4.2.1.2 Option 2: Create, Release, and Clear Payment Request in Separate Steps
Test Administration
Purpose
In this activity, you create, release and clear the payment request in separate steps.
Prerequisite
4.2.1.2.1 Create Bank Transfer
Test Administration

Appendix PUBLIC 118
Purpose
In this activity, you create a payment request via bank transfer.
Procedure
Test Test Step Instruction Expected Result Pass / Fail /

Step # Name Comment
1 Log on Log onto the SAP Fiori launchpad as a Cash Management Special- The SAP Fiori launchpad displays.
ist.
2 Access the Open Make Bank Transfers (F0691).

SAP Fiori app
3 Create New To trigger a new bank transfer, choose Create. Make the following If the system does not encounter validation errors, the new bank transfer payment request is successfully cre-
Bank Transfer entries and choose Create: ated. The system displays a message indicating that a payment request is created with the payment request
ID.
Note Make a note of the payment request number: __________

(when you have done so, choose Close).
Payer Information:
Paying Bank Account: 1133698
Payee Information:
Receiving Bank Account: for example, 2580061
Receiving Company Code: 1010
Receiving House Bank Account: for example, DEAC2
Transaction Information:
Payment Method: Choose an existing payment method for credit
transfer.
Amount: for example, 1000EUR
Release and Pay: Deselected

Appendix PUBLIC 119
Step # Name Comment
Payment Data: (option)

Note If you want to designate instruction key for the payment

request, enter following instruction key & instruction fields.

4 Check Appli- In Application Log section, choose Search. The payment request creation info is presented in log details.
cation Log
Test Administration
Purpose
In this activity, you release a payment request.

Appendix PUBLIC 120
Procedure

Step # Comment
1 Log on Log onto the SAP Fiori launchpad as a The SAP Fiori launchpad displays.
Cash Management Specialist.
2 Access the SAP Fiori app Open Make Bank Transfers (F0691).
3 Search Bank Transfer Make the following entries and choose The specified bank transfer entry with Created status is displayed in the Bank Transfer worklist.
Go:
Payment Request: <payment re-
quest number>
Note Choose Adapt Filters to show the

Payment Request field.
4 Release Bank Transfer At the right of the screen, choose Release. The bank transfer payment request is presented in the right side of the screen with 'Released' status. The Pay and
To confirm, on the dialog box, choose Re- Reverse buttons are shown for you to proceed with the next payment transactions.
lease.
5 Check Application Log In Application Log section, choose The payment request release info is presented in log details.
Search.
6 Reverse Bank Transfer after be- At the right of the screen, choose Reverse. The bank transfer payment request status change to Reversed.
ing released(option) To confirm, on the dialog box, choose Re- If you reverse the payment request, go back to the prior step to create a bank transfer.
verse.
Test Administration

Appendix PUBLIC 121
Purpose
In this activity, you pay a payment request.
Procedure

Step # Comment
1 Log on Log onto the SAP Fiori launchpad as a The SAP Fiori launchpad displays.
Cash Management Specialist.
2 Access the SAP Open Make Bank Transfers (F0691).

Fiori app
3 Search Bank Make the following entries and choose The specified bank transfer entry with Released status is displayed in the Bank Transfer worklist.
Transfer Go:
Payment Request: <payment re-
quest number>
Note Choose Adapt Filters to show

the Payment Request field.
4 Pay Bank Trans- At the right of the screen, choose Pay. The payment request is cleared.
fer To confirm, on the dialog box, choose
Pay.
5 Check Applica- In Application Log section, choose The payment request cleared info is presented in the log details.
tion Log Search.
6 Search and Open To find your new payment request, run The bank transfer payment request is presented in the right side of the screen with Cleared status. The Clearing Document No. field
Bank Transfer steps 3-4 above. Open the request. shows the clearing document number.
Note If the payment request is not cleared and stays in Released status or the batch is not created, you can read the message and
also use the App: Automatic Payment Transactions for Payment Requests (F111) to check the application log for your pay-
ment run ID.

Appendix PUBLIC 122
4.2.1.3 Option 3: Make Bank Transfer with Templates
Purpose
This section describes the process to make bank transfers with templates.
Prerequisite
4.2.1.3.1 Define Bank Transfer Templates
Test Administration
Purpose
In this activity, you maintain bank transfer templates.

Appendix PUBLIC 123
Procedure

Step # Comment
1 Log on Log onto the SAP Fiori launchpad as a Cash Management Specialist.
2 Access the SAP Fiori app Open Define Bank Transfer Templates (F3759).
3 Create Bank Transfer Tem- To create a template, choose Create. Make the following entries and choose Create: The Bank Transfer Template is successfully saved. The template is
plates Payer Information: shown in display mode with all information filled.
Repetitive Code: for example, RC001

Paying Bank Account: for example, 1133698 Note The system performs checks when saving the template,
Paying Company Code: 1010 such as:
● bank account validation in current period
● bank account with valid house bank and house bank ac-
count ID
Payee Information:
● payment method properly configured for the paying com-
Receiving Bank Account: for example, 2580061 pany code's country
Receiving Company Code: 1010 ● payment method configured for the selected currency
Receiving House Bank Account: for example, DEAC2 If an error message occurs, read the message and take any required
Transaction Information: actions.
Payment Method: <existing payment method for credit transfer>
Note Only payment methods that are applicable to the paying bank account are listed.
Currency: for example, EUR
4 Close Bank Transfer Tem- To close the right panel, choose Close. The Define Bank Transfer Templates screen displays.
plates
5 Edit a Bank Transfer Tem- Choose Edit on the top right corner. Make some changes and choose Save. The Bank Transfer Template is successfully saved.
plate Note:
Some fields cannot be changed, such as
- Repetitive Code
- Paying Bank Account
- Paying Bank Account ID

Appendix PUBLIC 124
Step # Comment
6 Delete a Bank Transfer Tem- Choose Delete on the top right corner. On the dialog box, choose Delete to confirm the interac- The bank transfer template is deleted.
plate(option1) tion.
Note If you delete the bank transfer template, go back to the

previous step to create a new bank transfer template.
7 Delete Multiple Bank Trans- Execute steps 3 - 5 to create multiple bank transfer templates. Search for the templates, select The selected bank transfer templates are deleted.
fer Templates (option2) them, and choose Delete. On the dialog box, choose Delete to confirm the interaction.
Note If you delete the bank transfer template, go back to the

previous step to create a new bank transfer template.
4.2.1.3.2 Create Bank Transfers with Templates
Test Administration
Purpose
In this activity, you make bank transfer with templates.
Prerequisite
The relevant bank transfer templates have been created.

Appendix PUBLIC 125
Procedure

Step # Comment
1 Log on Log onto the SAP Fiori launchpad as a Cash Management Specialist.
2 Access the SAP Fiori app Open Make Bank Transfers - Create with Templates (F3760). The Make Bank Transfers – Create with Templates view
displays.
Note Alternatively, you can open Make Bank Transfers (F0691), then choose Create with
Templates to get into the Make Bank Transfers - Create with Templates (F3760) app.
3 Search Bank Transfer Templates All available bank transfer templates are listed. Search for the specific bank transfer template cre- All the bank transfer template records matching the search
ated previously (searching for its repetitive code, paying company code or paying bank account). criteria are listed.
4 Create a Payment Request - New Select a bank transfer template. The Bank Transfers are created. Also a new payment re-
Bank Transfers（Option 1） Choose Show More per Row at the right corner and make the following entries: quest with Created status is created for the repetitive code.
Note choose Settings to open more fields.

Amount: <transfer amount>
Currency: EUR (change if required)
Reference Text: <description>
Release and Pay: <deselected>
Note If you choose Release and Pay, you can skip further steps Release Payment Request and
Pay Payment Request.
Note If you want to designate instruction key for the payment re quests, enter following in-
struction key & instruction fields.

Choose Create.
Make a note of the payment request number: __________
5 Create Multiple Payment Requests Execute step 3-4, but choose several templates to maintain and Create. The payment requests are listed.

Appendix PUBLIC 126
Step # Comment
- New Bank Transfers(Option 2) Choose Close to confirm the message"
Note The Message pop up telling that payment request

is created or not created for the repetitive codes.
Purpose
In this activity, you release a payment request..
Procedure
Please refer to step Release Payment Request [page ] 120 in this document.
Purpose
In this activity, you pay a payment request.
Procedure
Please refer to step Pay Payment Request [page ] 121 in this document.

Appendix PUBLIC 127
4.2.2 Approve and Bank Integration
Purpose
After the bank transfer is executed, a Bank Communication Management (BCM) batch or several BCM batches are created automatically. The BCM batches are approved as described in this proce-
dure.
After approval, if a MBC credit transfer payment medium format was used in bank transfer, the payment medium format file can be sent to Multi-Bank Connectivity (MBC) for bank payment pro-
cessing, as described in Bank Integration with SAP Multi-Bank Connectivity (16R). If in the SAP S/4HANA Enterprise Management system the payment medium format for the file download was
used in cash concentration, the payment medium format file can be downloaded manually, as described in Bank Integration with File Interface (1EG).
Procedure
Run the steps in the previous Approve and Bank Integration procedure for payment triggered by using the Make Bank Transfer app.
Test Administration
Context
After a bank transfer is made, the positions of the paying bank and receiving bank are updated. The head of cash manager can analyze the cash position by country, currency, company code or bank.

Appendix PUBLIC 128
Procedure

Step # Comment
1 Log on Log onto the SAP Fiori launchpad as a Cash Manager.
2 Access the SAP Fiori app Open Cash Position - Today (F1737). The Cash Position screen displays.
3 Check the Cash Position The screen displays a bar chart classified by bank country. The bar for each country represents the The total cash position amount is displayed at the top right of
Classified by Bank Country cash position in banks for this country. screen. The bar chart displays at the bottom of the screen.
4 Display by other Drill You can use the drill down list (By Bank Country is chosen by default) to change to another option.
Down Option For example, if you choose By Company, the bar chart is classified by company code name.
5 Drill Down by Clicking on If you click the blue bar, you can choose an option from the context menu. For example, if you The positions of these two banks involved in bank transfer in
a Bar choose By Bank, the bars are reclassified by bank name. the previous step are updated.
6 Shift to Form Display Choose the Tabular View button. The cash position data is shown in a list/form format.
4.3 Cash Trade Request
Test Administration
Purpose
In this activity, you can create, edit, and delete cash trade requests, which will then be submitted for approval. As a result of your submission, your requests can be released or rejected. The released
cash trade requests will then automatically trigger the creation of trade requests in the Treasury and Risk Management (TRM).

Appendix PUBLIC 129
Prerequisite
You need to manually enable the cash trade request functionality in the full scope of cash management. This functionality is integrated with Treasury and Risk Management (TRM). You also need to
define planning levels for cash trade requests. You can follow the steps in Preliminary Steps section.
1. Enable Cash Request Integration
2. Define Planning Level for Cash Request
3. Assign Planning Level to Cash Request
4.3.1 Create and Submit Cash Trade Request for FX
Test Administration
Purpose
Cash Specialist create and submit Cash Trade Request for FX.
Procedure

Step # Comment
2 Access the SAP Fiori App Open Manage Memo Records (F2986).
3 Create Cash Trade Request (FX) Choose Create Memo Record/... > Create Cash Trade Request (FX) . The Memo Record view displays.

Appendix PUBLIC 130
Step # Comment
Note The certainty level for the new memo record is

Cash Trade Request.
4 Enter Cash Trade Request Data In the Cash Trade Request Data section, make following mandatory fields and choose En-
ter:
Instrument Category: for example, FXFW (FX Forward)
Value Date: <current date+3 months>
Buy / Sell: Buy
Company Code: 1010
Requested Amount: for example, 1000,000USD
Requested Opposite Amount(Forecasted): <in the second field, enter the
opposite currency, for exampleEUR>
Choose Enter, Opposite Amount is activated for input. Enter the Opposite Amount if
needed.
Note Use Adapt Filters to view any missing fields in the view.
5 Create Cash Trade Request Choose Create. The cash trade request is created with status Created.
Note Before submitting, you can edit or delete the cash trade request via choose Edit
or Delete.
6 Submit Cash Trade Request Choose Submit. The cash trade request is submitted for approval and its sta-
After Submitted, you can not edit or delete the cash trade request. tus is also updated as Submitted.
7 Save and Submit Cash Trade Request Note You can also save and submit cash trade request in one step as following: The cash trade request is saved and submitted in one step.
in One Step (Optional) Repeat steps 1-5, then choose Save and Submit.

Appendix PUBLIC 131
4.3.2 Create and Submit Cash Trade Request for Money Market
Test Administration
Purpose
Cash Specialist create and submit Cash Trade Request for Money Market.
Procedure
# ment
3 Create Money Market Request Choose Create Memo Record/... and choose Create Cash Trade Request (MM) The Memo Record view displays.
(MM) from dropdown list. The certainty level for the new memo record is Cash Trade Request.
4 Enter Cash Trade Request Data On the Cash Trade Request Data section, make following mandatory fields and
choose Enter:
Instrument Category: MM (Money Market Undefined)
Invest / Borrow: <Invest or Borrow>
Term Start Date: <current date>
Term End Date: <current date+1 year>
Company Code: 1010
Requested Amount: for example, 1000,000EUR

Appendix PUBLIC 132
# ment
5 Cash Trade Request Choose Create. The Cash Trade Request is created with status Created.
Before submitting, you can edit or delete the cash trade request via choose Edit
or Delete.
6 Cash Trade Request Choose Submit. The cash trade request is submitted for approval and its status is also up-
After submitting, you can not edit or delete the cash trade request. dated as Submitted.
7 Cash Trade Request in One Step You can also save and submit Cash Trade request in one step as following: The Cash Trade request is saved and submitted in one step.
(Optional) Repeat steps 1-5, then choose Save and Submit.
4.3.3 Release Cash Trade Request
Test Administration
Purpose
Cash Manager release the Cash Trade Request.
Note The other user is used to approve and release the cash trade request.

Appendix PUBLIC 133
Procedure

Step # Comment
2 Access the SAP Open Manage Memo Records (F2986).

Fiori App
3 Search Cash Make the following entries and choose Go. The cash trade requests are displayed.
Trade Request Company Code: 1010
Certainty Level: Cash Trade Request
Cash Trade Request Status:S(Submitted)
Note Choose Adapt Filters to add the fields as filter if needed.
4 Release Cash Select a cash trade request and choose Release. The cash trade request is released, then automatically trigger the creation
Trade Request of trade requests in the Treasury and Risk Management (TRM).
After the deal is performed in trading platform, cash trade request gets re-
Note Follow the relevant procedure in the Treasury Trading via Trading Platforms (2F5) test sponse from Trade Request and update the status.
script to send the trade request to trading platforms through SAP Cloud Platform.
5 Check Trade Re- In the General Information section, choose the highlighted number of trade request. The relevant
quest trade request displays.
4.3.4 Reject Cash Trade Request (Optional)
Test Administration

Appendix PUBLIC 134
Purpose
Cash Manager rejects a Cash Trade Request
Note The other user is used to reject the cash trade request.
Procedure
3 Search Cash Trade Request Make the following entries and choose Go. The cash trade requests are displayed.
Company Code: 1010
Cash Trade Request Status:S(Submitted)
4 Reject Cash Trade Request Select a cash trade request and choose Reject. The cash trade request is rejected, and its status is updated as Created.
Note The creator can adjust the cash trade request and submit again.
4.3.5 Treasury Management Integration for Trading Platform
Test Administration

Appendix PUBLIC 135
Purpose
In this step, you send the cash trade request to trading platforms through SAP Cloud Platform.
After a deal is performed in a trading platform, the cash trade request gets a response from the Trade Request and the status is updated accordingly.
● If the whole deal is fulfilled in the trading platform, the cash trade request is updated as Completed
● If the whole deal is canceled in the trading platform, the cash trade request status is updated as Canceled.
● If the deal is split and partial fulfilled(or partial declined) in the trading platform, the cash trade request status is updated as In Process. Then the remaining part is partial fulfilled (or partial de-
clined) in the trading platform, the cash trade request status is finally updated as Completed.
Prerequisite
The cash trade request has been released.
Procedure
Follow the relevant procedure in the Treasury Trading via Trading Platforms (2F5) test script.
4.3.6 Fulfill Cash Trade Request as Deal Done
Test Administration

Appendix PUBLIC 136
Purpose
Follow the relevant procedure in the Treasury Trading via Trading Platforms (2F5) test script to send the cash trade request to a trading platform through SAP Cloud Platform.
After the deal is done in the trading platform and the TR transaction was created, a cash trade request gets a response from the Trade Request and updates the status to Completed.
Procedure
Company Code: 1010
Cash Trade Request Status:F(Completed)
4 Check Trade Cash Trade Request Select a cash request to check. The cash request status is updated as Completed.
4 Check Trade Request Click Trade Request number which is highlighted with Blue. Trade Request detailed information is displayed.
4.3.7 Cancel Cash Trade Request as Deal Cancel
Test Administration

Appendix PUBLIC 137
Purpose
Follow the relevant procedure in the Treasury Trading via Trading Platforms (2F5) test script to send the trade request to trading platforms through SAP Cloud Platform.
If deal is canceled in trading platform, cash trade request status is updated as Canceled.
Procedure
3 Search Cash Trade Request Make the following entries and choose Go. The change requests are displayed.
Company Code: 1010
Cash Trade Request Status:X(Canceled)
4 Check Cash Trade Request Select a cash trade request to check. The cash trade request status is updated as Canceled.
4.3.8 Check Partial Fulfill or Partial Decline Cash Trade Request Status
Test Administration

Appendix PUBLIC 138
Purpose
Follow the relevant procedure in the Treasury Trading via Trading Platforms (2F5) test script to send the cash trade request to trading platforms through SAP Cloud Platform.
If a deal is split and partial fulfilled(or partial declined) in a trading platform, the cash trade request status is updated as In Process. Then the remaining part is partial fulfilled (or partial declined) in a
trading platform, the cash trade request status is finally updated as Completed.
Note For current release, this step is only for Cash Trade Request for FX.
Procedure
Company Code: 1010
Cash Trade Request Status: T(In Process)/ F(Completed)
4 Check Cash Trade Request Select a cash trade request to check. The cash trade request status is updated as In Process or Completed.
4.4 Reconcile Cash Flows - Intraday Memo Records (Old Reconciliation Model)
Note If you enable New Reconciliation Model in preliminary step Enable New Reconciliation Model, the old reconciliation app Reconcile Cash Flows - Intraday Memo Records (F3418) does
not work. you should skip this step and go to the next step Reconcile Cash Flows (new Reconciliation Model).

Appendix PUBLIC 139
Purpose
With the app Reconcile Cash Flows - Intraday Memo Records (F3418), you can manually reconcile intraday memo records that were generated automatically from intraday bank statements with
forecasted cash flows. This feature enables you to compare your intraday bank statements with your forecasts before the end of the business. You can easily identify unfinished and unknown pay-
ments in time, as well as help you remove duplicated items in forecasts to gain a more accurate account of your cash positions.
The reconciliation result is also reflected in the Cash Flow Analyzer (F2332), where you can filter intraday bank statements and forecasted cash flows according to their reconciliation status. By
combining different filter options, you can analyze your cash flows and bank account balances from various dimensions.
The four reconciliations status under Cash Flow Analyzer are as follows:
1. Reconciled Intraday Bank Statements
2. Unreconciled Intraday Bank Statements
3. Reconciled Forecasted Cash Flows
4. Unreconciled Forecasted Cash Flows
Prerequisite
Before testing this step, ensure that the following customizing, master data and procedures have been defined, maintained and completed. Some steps that must be completed as prerequisites are de-
scribed in other test scripts.
1. Define Tolerance Groups for Cash Flow Reconciliation
You have completed the steps in the Define Tolerance Groups for Cash Flow Reconciliation [page ] 52 procedure in the Preliminary Steps section of the Prerequisites.
2. Activate Intraday Reconciliation for Bank Account
You have completed the steps in the Activate Intraday Reconciliation for Bank Account [page ] 54 for Bank Account procedure in the Preliminary Steps section of the Prerequisites.
3. Create Forecast Cash Flows (optional)
Open forecast cash flows exist. One Exposure derives cash forecasts for items representing receivables, payables, or cash in transit, and so on.
4. Intraday bank statement with memo record is generated.
The relevant intraday memo records are automatically generated after importing intraday bank statements.
You can follow the Upload Intraday Bank Statement procedure in the Bank Integration with File Interface (1EG).
Note
1. If you want to generate memo records from imported bank statements, you have to define the following settings:
1. via SSCUI (101024): Make Global Settings for Electronic Bank Statement
1. Assign a memo record type to the specific transaction type (optional).
2. via SSCUI (105440): Define Memo Record Settings for Bank Statements
1. Disable generating memo records via batch input for end-of-day bank statements.
2. Activate and define the memo record type derivation logic for intraday memo records.
2. After a new intraday bank statement is imported for a certain bank account, the system generates an intraday memo record. If there is already an active intraday memo record that was gener-
ated before the current date under this bank account, the system automatically deactivates the old intraday memo record into the inactive status to eliminate duplicate data.

Appendix PUBLIC 140
3. When an end of day bank statement is imported for a certain bank account, any active intraday memo record under this bank account before the current date, the system automatically will
deactivate the old intraday memo record into the inactive status to eliminate duplicate data.
4.4.1 Schedule Intraday Memo Records Reconciliation
Test Administration
Purpose
In addition, a specific reconciliation report Schedule Intraday Memo Records Reconciliation (F5284) is offered to support you to automatically and periodically reconcile intraday memo records
with not only three type open forecasted cash flows (Regular Receivable, Regular Payable, Self-Initiated Cash in Transit), but also general memo records.
Procedure

Step # Comment
2 Access the SAP Open Schedule Intraday Memo Records Reconciliation (F5284).
Fiori App
3 Create a New Ap- On the current view, choose Create to create an application job. The New Job: Schedule Intraday Memo
plication Job Records Reconciliation view displays.
4 Choose Job Tem- In the Template Selection section, make following entries:
plate Job Template: Schedule Intraday Memo Records Reconciliation

Appendix PUBLIC 141
Step # Comment
Job Name: Schedule Intraday Memo Records Reconciliation
5 Maintain Schedul- Choose Step 2. In the Scheduling Options section, make the following entries
ing Options Start Immediately: <Selected or deselected>
Note If you choose star immediately, other parameter do not need to maintain.

End: Optional
Choose OK.
Note If you would like to run this job immediately, the check-box of Start Immediately should be selected.
If you schedule this job at some time in the future, the Start and Time Zone should be defined.
6 Maintain Parame- Choose Step 3. In Parameter section and make the following entries: Parameters are maintained.
ter Control Parameters
Run Type: For example: Reconcile with Bank Statement Info and Match by Amount
Selection Criteria
Bank Account: For example: <Technical ID for your bank account>
Company Code: For example: 1010
Import Date: Import date
Planning Level For Memo Record: Planning level is used to reconcile with Intraday memo record
Note If you keep parameters empty, that means all cases will be included in the job.

Appendix PUBLIC 142
Step # Comment
8 Run this Applica- Choose Schedule to run this application job.

tion Job
9 Check Application Choose Go to update the job status. When your job’s status changes to Finished, you choose > navigate to the job details. In Log The job log displays.
Jobs Log and Results section, choose the Log status (Error, Information or Success…) to check the Log Details.
4.4.2 Check Automatic Reconciliation Result
Test Administration
Purpose
You can view automatically reconciled intraday memo records and forecasted cash flows.
Once an intraday bank statement is imported into the system, the system automatically generates an intraday memo record for each bank account. The system then automatically reconciles open in-
traday memo records with three type open forecasted cash flows (Regular Receivable, Regular Payable, Self-Initiated Cash in Transit). Not All forecast flows are supported by automatic reconcilia-
tion.
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Cash Man-

Appendix PUBLIC 143
Step # Comment
agement Specialist.
2 Access the SAP Open Reconcile Cash Flows - Intraday Memo The Reconcile Cash Flows - Intraday Memo Records view displays.
Fiori App Records (F3418).
3 Selection Criteria Choose Adapt Filters if selection fields are hidden. Bank accounts in reconciliation are listed.
Make the following entries and choose Go:
Value date: <current date>
Company code: 1010
Bank Account: For example, 2580061
4 Verify Reconcilia- Choose the Reconciled Items tab to verify the rec- Note If the items are changed after reconciliation, the column Changed After Reconciliation is marked as Yes.
tion onciled pairs. You can Undo Reconciliations per your request.
Test Administration
Purpose
You can manually reconcile intraday memo records with any forecasted cash flows.

Appendix PUBLIC 144
Procedure

Step # Comment
2 Access the SAP Open Reconcile Cash Flows - Intraday Memo Records (F3418). The Reconcile Cash Flows - Intraday Memo Records view
Fiori App displays.
3 Selection Criteria Choose Adapt Filters if selection fields are hidden. Intraday Memo Records, Forecasted Cash Flows, Reconciled
Make the following entries and choose Go: Items of the same bank account (with the same currency)
display.
Value Date: <current date>
Company Code: 1010
4 Select Intraday In the Bank Accounts in Reconciliation area, choose a bank account you wish to view by choosing the > to the
Memo Records right of the row.
Select one or more Intraday memo records with same currency under the Intraday Memo Records tab.
5 Select Forecasted In the Forecasted Cash Flows tab, choose the relevant forecast cash flows of the same bank account (with the
Cash Flows same currency).
Note To reconcile with forecasted cash flow of other bank accounts, choose To Company Code View to view
all the open cash flows of the same company code, and then select the desired forecasted cash flow items
from that list.
To reconcile between different currencies, you choose the intraday memo records of the currency and then
choose the forecasted cash flows of the other currency.
A tolerance group is available for the bank account where the exchange rate type is configured. If exchange
rates or exchange rate types are not properly defined, you cannot reconcile those items.
6 Perform Recon- Choose either Reconcile with Cash Flow from above the Intraday Memo Record section, or Reconcile with Intra- .
ciliation day in the Forecasted Cash Flows section.
Note
● If the difference exceeds the limit defined in the relevant tolerance group for the bank account, the system
notifies you with an alert.
● For reconciliation between different currencies, if the difference after currency exchange is higher than
the tolerance, a dialog box notification warning displays.
7 Verify Reconcili- Choose the Reconciled Items tab to verify the reconciled pairs. The intraday memo records and the forecasted cash flows are

Appendix PUBLIC 145
Step # Comment
ation reconciled.
Test Administration
Purpose
You can undo reconciliations for selected items and reset them to the open status.
Procedure

Step # Name Comment
2 Access the Open Reconcile Cash Flows - Intraday Memo Records (F3418). The Reconcile Cash Flows - Intraday Memo Records view displays.
SAP Fiori
App
3 Selection Cri- Choose Adapt Filters if selection fields are hidden. Bank accounts with status reconciled are listed.
teria Make the following entries and choose Go:

Appendix PUBLIC 146
Step # Name Comment

Company Code: 1010
4 Verify Recon- In the Bank Accounts in Reconciliation area, choose a bank account you wish to view by choosing the Note If the items are changed after reconciliation, the column Changed
ciliation > to the right of the row. After Reconciliation is marked as Yes.
Choose the Reconciliations tab to verify the reconciled pairs.
4 Undo Recon- Choose the Reconciliations tab, select any items that are not matched together and choose Undo Recon- The reconciliation chains are broken and any of those items of this recon-
ciliation Item ciliation at up-right corner of the section. Choose OK to confirm the notification that displays in the di- ciliation group are reset to open, making them available for further match-
alog box. ing.
5 Verify Recon- Choose the Reconciliations tab to verify if the reconciled pairs are broken.
ciliation
4.5 Reconcile Cash Flows - Intraday (New Reconciliation Model)
Purpose
You can now enable the new model for cash flow reconciliaiton and use the new app Reconcile Cash Flows - Intraday (F3418A) to perform cash flow reconciliations between intraday bank state-
ment flows and forecasted cash flows before end of business. It helps you easily identify unfinished and unknown payments before end of business. Compared to the old app, the new app enables
you to reconcile cash flows at bank account level and create residual flows for carrying forward unreconciled forecated flows to the next round of reconciliation.
Prerequisite
Before testing this step, ensure that the following customizing, master data and procedures have been defined, maintained and completed. Some steps that must be completed as prerequisites are de-
scribed in other test scripts.
1. Enable New Reconciliation Model
You have completed the steps in the Enable New Reconciliation Model (Optional) [page ] 44 procedure in the Preliminary Steps section of the Prerequisites.
2. Define Profiles for Cash Flow Reconciliation
You have completed the steps in the Define Profiles for Cash Flow Reconciliation (Optional) [page ] 49 procedure in the Preliminary Steps section of the Prerequisites.
3. Define Tolerance Groups for Cash Flow Reconciliation
You have completed the steps in the Define Tolerance Groups for Cash Flow Reconciliation [page ] 52 procedure in the Preliminary Steps section of the Prerequisites.

Appendix PUBLIC 147
4. Activate Intraday Reconciliation for Bank Account
You have completed the steps in the Activate Intraday Reconciliation for Bank Account [page ] 54 procedure in the Preliminary Steps section of the Prerequisites.
5. Create Forecast Cash Flows (optional)
Open forecast cash flows exist. One Exposure derives cash forecasts for items representing receivables, payables, or cash in transit, and so on.
6. Intraday bank statement with memo record is generated or upload bank statement.
The relevant intraday memo records are automatically generated after importing intraday bank statements.
You can follow the Upload Intraday Bank Statement or Upload Bank Statement procedure in the Bank Integration with File Interface (1EG).
Note
1. If you want to generate memo records from imported bank statements, you have to define the following settings:
1. via SSCUI (101024): Make Global Settings for Electronic Bank Statement
Assign a memo record type to the specific transaction type (optional).
2. via SSCUI (105440): Define Memo Record Settings for Bank Statements
Disable generating memo records via batch input for end-of-day bank statements.
Activate and define the memo record type derivation logic for intraday memo records.
2. After a new intraday bank statement is imported for a certain bank account, the system generates an intraday memo record. If there is already an active intraday memo record that was gener-
ated before the current date under this bank account, the system automatically deactivates the old intraday memo record into the inactive status to eliminate duplicate data.
3. When an end of day bank statement is imported for a certain bank account, any active intraday memo record under this bank account before the current date, the system automatically will
deactivate the old intraday memo record into the inactive status to eliminate duplicate data.
Test Administration

Appendix PUBLIC 148
Purpose
You can perform cash flow reconciliations between intraday bank statement flows and forecasted cash flows before end of business.
Procedure

Step # Comment
2 Access the SAP Fiori Open Reconcile Cash Flows - Intraday (F3418A). The Reconcile Cash Flows - Intraday view displays.
App
3 Selection Criteria Choose Adapt Filters if selection fields are hidden. Reconciliation status, Reconciled/Unreconciled BS flows, Reconciled/Unreconciled Fore-
Make the following entries and choose Go: casts, Unreconciled Residual, Proposal Amount of the same bank account (with the same
currency) display.
Exchange Rate Type: M
Reconciliation Profile: ZRP_01 Note If no BS flows exist, the reconciliation status will set as Not Applicable.
Company Code: 1010

Reconciliataion Status: For example, Unreconciled
4 Choose Details Choose > (Details). All Cash Flows tab, Unreconciled Cash Flows tab and Reconciliation Bundles tab display.
5 Select Bank State- Choose Unreconciled Cash Flows tab, in the Unreconciled Bank Statement
ment Flows Flows area, select one or more items.
6 Select Forecasted In the Unreconciled Forecasted Flows area, choose the relevant forecast cash
Flows flows.
7 Perform Reconcilia- Choose Reconcile. In the Reconcile popup screen Proposed Amount is calcu-
tion with Residual lated and displayed. You can manually change it or add text. Then choose
(option1) Confirm.
Note The Proposed amount is generated as residual cash flow which is

considered in next reconciliation exection.

Appendix PUBLIC 149
Step # Comment
8 Perform Reconcilia- Or choose Reconcile Without Residual. In the Reconcile Without Residual
tion without Residual popup screen, no Proposed Amount is calculated. Then choose Confirm.
(option 2)
9 Verify Reconciliation Choose the Reconciliation Bundles tab to verify the reconciled pairs. The Bank statement flows and the forecasted cash flows are reconciled.
Test Administration
Purpose
You can undo reconciliations for selected items and reset them to the open status.
Procedure

Step # Comment
2 Access the SAP Open Reconcile Cash Flows - Intraday (F3418A). The Reconcile Cash Flows - Intraday view displays.
Fiori App

Appendix PUBLIC 150
Step # Comment
3 Selection Crite- Choose Adapt Filters if selection fields are hidden. Bank accounts with status reconciled are listed.
ria Make the following entries and choose Go:
Exchange Rate Type: M
Reconciliation Profile: ZRP_01
Company Code: 1010
Reconciliataion Status: For example, Reconciled
4 Choose Details Choose > (Details).
5 Unreconcile In the Reconciliation Bundles tab, select any items that are not matched together The reconciliation chains are broken and any of those items of this reconciliation group are
and choose Undo Reconciliation at up-right corner. reset to open, making them available for further matching.
Note If it is relevant to residual cash flow, residuals also are updated.
6 Verify Unrecon- Choose the Unreconciled Cash Flows tab to verify the items are reset to open to Unreconciled bank statement flows and unreconciled forecasted flows display.
ciliation reconcile.
4.6 Manage Bank Account Balances

Purpose
You can manually enter or import balances for bank accounts and monitor the balance changes of these accounts.
The Manage Bank Account Balances app is able to receive bank account balance data from imported end-of-day bank statements. In addition to bank accounts managed in remote systems, now you
can also use this app to manage bank account balances for bank accounts that are managed in your central system.
Note Bank account balances received from imported bank statements are displayed with the Update Method of Electronic Bank Statements. The balances are stored by the bank statement dates
contained in the bank statements. For each date, if there is already a balance entry updated by electronic bank statements, the balance is not allowed to be updated via spreadsheet import or man-
ual entry.
Prerequisite:
To display bank account balances from imported bank statements, the bank accounts must be defined with one of the following transfer modes:
● Balance Only
● Balance and Bank Statement Items

Appendix PUBLIC 151
If you want to manually enter bank account balances or import bank account balances via a spreadsheet, in the next steps, you need to enable Balance from Manual Entry and Balance from spread-
sheet Import.
For more information about this setting, see step Define Bank Account Settings – Bank Statements or Integrate with End-of-Day Bank Statements in the Basic Bank Account Management (BFA) test
script.
4.6.1 Create Bank Account Balances
Test Administration
Purpose
You can manually enter balances for bank accounts.
Procedure
# ment
2 Access the SAP Fiori app Open Manage Bank Account Balances (F5175). The Manage Bank Account Balance view dis-
plays.
3 Create Bank Account Balance Choose Create. In the Enter Balance for Bank Account dialog box, make the following entries and The balance of bank account is created.
choose Create:
Technical ID: <choose a house bank via value help>
Statement Date: <current date>

Appendix PUBLIC 152
# ment
Balance Amount: 3500.00
4 Check in Cash Flow Analyzer Use your bank account and refer to procedure Cash Flow Analyzer.
5 Check in Short Term Cash Po- Use your bank account and refer to procedure Short Term Cash Position. The balance of your bank account displays.
sition
4.6.2 Import Bank Account Balances
Test Administration
Purpose
You can upload Excel file for Balance of Bank Accounts, so that the Balance of relevant Bank Accounts can be updated massively.
Procedure
Test Step Test Step Name Instruction Expected Result Pass / Fail / Comment
#
2 Access the SAP Fiori app Open Manage Bank Account Balances (F5175). The Manage Bank Account Balances view dis-

Appendix PUBLIC 153
Test Step Test Step Name Instruction Expected Result Pass / Fail / Comment
#
plays.
3 Navigate to Import Bank Account Bal- Choose Import. The Import Bank Account Balances view displays.
ances
4 Download Template Choose Download Template. The template is download in your local PC.
5 Edit Template file Open the template file in your local PC and maintain the value per your bank account.
6 Import Bank Account Balances Choose Browse to select your template, then choose Import. The balance of bank account imported
7 Check in Cash Flow Analyzer Refer to procedure Cash Flow Analyzer.
8 Check in Short Term Cash Position Refer to procedure Short Term Cash Position. The balance of your bank account displays.
4.6.3 Edit Bank Account Balances
Test Administration
Purpose
You can edit bank account balances for a bank account.

Appendix PUBLIC 154
Procedure
2 Access the SAP Fiori app Open Manage Bank Account Balances (F5175). The Manage Bank Account Balance view displays.
3 Check Bank Account Balance list Make the following entries and choose Go: The balance of bank account list displays.
Account Number: <choose a bank account via value help>
Company Code: <your company code>
4 Check Bank Account Choose > to navigate to check balance history.
5 Edit Bank Account Balance Choose Edit. Change Closing Balance as needed and choose Save. The balance of your bank account edited.
4.6.4 Check Bank Account Balances
Test Administration
Purpose
You can show the difference between ledger balance and value date balance.
There are three kinds of balance types supported in the Manage Bank Account Balance app: Ledger balance, value date balance, available balance.
If the bank account balance is imported from a bank statement, then the value date balance is calculated based on the ledger balance from the bank statement. For a bank statement item whose value
date is greater than the bank statement date, the amount will not be considered. It means the formula is: value date balance + predated flow = ledger balance. However, if there is no future date item,
then value date balance = ledger balance. Therefore, the display predated flows will help the customer better understand how the value date balance is calculated.
If the bank account balance is manually entered via Manage Bank Account Balance, then only the value date balance and the available balance will be created, and the amount will be the same.

Appendix PUBLIC 155
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Cash Manage-

ment Specialist.
2 Access the SAP Fiori app Open Manage Bank Account Balances (F5175). The Manage Bank Account Balance view displays.
3 Check Bank Account Bal- Make the following entries and choose Go: The balance of bank account list displays.
ance list Account Number: <choose a bank account
via value help>
Company Code: <your company code>
4 Check Balance History Choose > to check balance history.
5 Check Balance History Select one balance item, choose > to check balance his- Three balance types displays. The ledger balance and value date balance, and the difference between
Details tory details. ledger balance and value date balance may display.
6 Check Details for Value Choose value date balance, chose choose > to check The value date balance details displays.
Date Balance value date balance details.
Note Detailed information is available for value date

balances only.
4.7 Manage Liquidity Item Transfer
Test Administration

Appendix PUBLIC 156
Purpose
You can process lifecycles of liquidity item transfer documents like Create, Change, Copy, and Delete.
Procedure

Step # Comment
2 Access the SAP Fiori Open Manage Liquidity Item Transfer. The Manage Liquidity Item Transfer screen displays.
app
3 Enter Company Code Choose Create, make the following entries in the Create dialog box The Liquidity Item Transfer screen displays.
and Currency and choose Continue:
Company Code: 1010
Transfer Currency: <for example EUR>
4 Maintain Description in Make the following entries:

header level Description: <your description>
5 Maintain Liquidity item In the Line Items section, choose Create to add a new items, and
transfer items – item 1 make the following entries:
1) Transfer Item ID: for example the original liquidity item you
want to tranfer
Transfer Item Desc: <your description>
Liquidity Item: <for example, the oringal liquid-
ity item which you want to tranfer>
Amount: <transfer amount, for example -
1000.00>
Value Date: <Value Date>
Posting Date: <Posting Date>
Note Choose Setting to select more field to enter.
6 Maintain Liquidity item In the Line Items section, choose Create to add another item, and
transfer items – item 2 make the following entries:
2) Transfer Item ID: for example the target liquidity item you want

Appendix PUBLIC 157
Step # Comment
to tranfer.
Transfer Item Desc: <your description>
Liquidity Item: <for example, the target li-quid-
ity item you want to tranfer>
Amount: <transfer amount, for example 1000.00>
Value Date: <Value Date>
Posting Date: <Posting Date>
Note Please ensure the total amount for Credit and Debit
should be 0. You can also create more items for Credit or
Debit amount.
7 Save At the bottom of the view, choose Create. All the items will generate actual One Exposure flows. During the liquidity item transfer, the original
liquidity items will not necessarily be changed, and the shifts between liquidity items will be docu-
mented.
Note You can check the tranfer liquidity items with App Check Cash Flow Items (F0735),
Short-Term Cash Positioning (F5380) or Cash Flow Analyzer (F2332).
4.8 Situation Handling: Date Difference Warning for FI Flows
4.8.1 Monitor Situations
Test Administration

Appendix PUBLIC 158
Purpose
Prerequisite
You have performed the procedure Situation Handling for Cash and Liquidity Management in the Preliminary Step.
Procedure
3 Maintain Filter Make the following entries:

Situation Type ID: ZFIN_FQM_FIDATE_DIFFERENCE
4 Check Instance Details In Instance Details section, check detailed information for your situation type. The batch job is executed per one hour.
4.8.2 Check Notification
Test Administration

Appendix PUBLIC 159
Purpose
In this step, the notification is checked by the recipient who is assigned to team members in preliminary step.
Procedure
1 Log On Log on to the SAP Fiori launchpad as a recipient (for example, Cash Manager).
2 Check Notification On home page, choose Notifications on the upper right corner.
Choose By Type, under type Situation Date Difference Warning for FI Flows has been identified, choose Expand Group.
3 Check Details Choose one item with Date difference in FI flow is too large and navigate to App Display Line Item Entry (F2218).
4.9 Cash Reports

Purpose
This section describes all of the frequently used reports for cash daily operation.
Test Administration

Appendix PUBLIC 160
Context
The Cash Manager or bank accountant can use this app to check the forecasted cash positions for the current date by location, company, and currency. Cash position data is calculated based on
memo records and various data sources from the One Exposure from Operations hub.
Procedure

Step # Comment
2 Access the SAP Open Cash Position - Today (F1737).

Fiori app
3 Review Cash Po- A bar chart displays the cash position information classified by bank For each country, the blue bar represents the cash position in the banks of this country. The cash
sition country. position amount is displayed in the top left of the view.
4 Display by other From the drilldown list, By Bank Country is chosen by default, select an- The bar charts are classified by the company code names.
Options other option, for example, By Company.
5 Drill Down Us- Choose the blue bar, choose an option from the list (for example, By The bar charts are reclassified by bank names.
ing Bar Bank).
6 Shift to Form Choose the Tabular View button. The cash position data is displayed in a form format.
Display
4.9.2 Check Liquidity Items on G/L Accounts
Test Administration

Appendix PUBLIC 161
Purpose
In this step, you can check liquidity items on G/L Accounts.
Procedure
2 Access the SAP Fiori app Open Check Liquidity Items on G/L Accounts (F6459). The Check Liquidity Items on G/L Accounts view displays.
3 Enter Selection Criteria Choose Adapt Filters if selection fields are hidden. The liquidity item on G/L accounts list displays.
Company Code: 1010
G/L Account: <empty>
Chart of Accounts: <empty>
Account Group: <empty>
4.9.3 Check Cash Flow Items
Test Administration

Appendix PUBLIC 162
Purpose
The Cash Manager, Bank Accountant, Accounts Receivable Accountant, or Accounts Payable Accountant can use this app to track and trace all the cash flow items from different source applications
that are integrated with cash management. You can also see line item details of the original documents, such as journal entries, banks, and account assignments. This provides a comprehensive over-
view of the cash flow and liquidity status in your company.
Note After completing the reconciliation described in the Reconciliation Cash Flows – Intraday Memo Records procedure, use the Check Cash Flow Items (F0735) SAP Fiori app and filter
by Reconciliation Status to view the detail line item information from each intraday bank statement and all forecast cash flows.
Procedure

Step # Fail /
Comment
2 Access the SAP Fiori app Open Check Cash Flow Items (F0735). The Check Cash Flow Items view displays.
3 Enter Selection Criteria Choose Adapt Filters if selection fields are hidden. The Payment Documents list is displayed.
Exchange Rate Type: <M> Note If Snapshot is enabled and the period of (Valid From to Valid To) includes
Snapshot Time: <default value> cash flow time stamp, the data flow should be detected under the current se-
Value Date: <Today> lected timeslot. You can change default Snapshot Time.
If Snapshot is not enabled and the period of (Valid From to Valid To) excludes
Company Code: 1010
cash flow time stamp, the data flow should not be detected under the current se-
Certainty Level: <choose all certainty levels> lected timeslot.
ReconciliationDspStatus: <select per your request>
Account Number: 1133698
Cash Flow View for Accounting: 2 Cash Position or 3 (Liquidity
Analysis)
4 Display Additional Pay- Select your cash flow item, and choose > (Details) to check details information. More payment information is displayed on the screen, such as:
ment Information ● General Information
● Journal Entry Information
● Bank Information
● Bank Communication Management Information
Note Different source applications display different payment information.

Appendix PUBLIC 163
Step # Fail /
Comment
5 Display FI Document Choose the blue link for a journal entry number, and navigate to Manage Journal En- The Manage Journal Entries screen displays.
tries.
Note Choose a line with Source Application such as Accounts Receivable, Ac-
counts Payable, or Payment.
6 Go Back Choose Back. The Check Cash Flow Items view displays.
7 Make Manual Adjust- Choose Edit. In Account Assignments section, manually adjust the account assign- The account assignments of the cash flow items is manually adjusted.
ment of the Cash Flow ments (such as liquidity item, transaction amount, cost center, and so on).
Items (Optional)
Note
● This function only works for cash flows from accounting documents (jour-
nal entries).
● You can also choose Add to add one or more new items to split the Transac-
tion Amount of the original item into different dimensions (such as liquidity
item, transaction amount, cost center, and so on).
● The Transaction Amount of all items must equal the Transaction Amount of
the original item.
4.9.4 Schedule Jobs for Bank Statement Monitor
Test Administration

Appendix PUBLIC 164
Purpose
In this step, you execute schedule jobs for bank statement monitor.
Prerequisite
Ensure that fields related to the bank statement monitor are fully populated under the Bank Relationship tab in bank account master data. For more information, see the Advanced Bank Account
Management (J77) test script.
Fields related to the bank statement monitor:
Processing Status: Yes
Interval: for example, 10
Interval Unit: for example, Calendar Days
Factory Calendar ID: for example, 01
Difference Status: Yes
Serial Number Status: Yes
Reconciliation Status: Yes
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Accounts Receivable Accountant .
2 Access the SAP Open Schedule Jobs for Bank Statement Monitor (F6866).
Fiori App
3 Create a New On the current view, choose Create to create an application job. The Application Jobs view displays.
Application Job
4 Choose Job In the Template Selection section, make following entries:

Template Job Template: Determine Status of End-of-Day Bank Statements
Job Name: Determine Status of End-of-Day Bank Statements
5 Maintain Sched- Choose Step 2. In the Scheduling Options section, make the following entries If you would like to run this job immediately, the check-box of Start Im-
uling Options Start Immediately: <Selected or deselected> mediately should be selected.

Appendix PUBLIC 165
Step # Comment
If you schedule this job at some time in the future, the Start and Time
Zone should be defined.
Note If you choose star immediately, other parameter do not need to maintain.

End: Optional
Choose OK.
6 Maintain Pa- Choose Step 3. In Parameter section and make the following entries: Parameters are maintained.
rameter General Parameters:
Key Date (Job Start Date +/- X Days): 7
House Bank: <empty>
House Bank Account : <empty>
Other Parameters:
Send Email for Jobs with Status Failed and Canceled: <deselected>
Email Recipients (Separated by Semicolon): <empty>
Email Language: <empty>
8 Run this Appli- Choose Schedule to run this application job. Choose Yes to confirm the dialog box.
cation Job
9 Check Applica- Choose Go to update the job status. When your job’s status change to Finished, you choose Details to Job log displays.
tion Jobs Log navigate to the job details. In Log and Results section, choose Log status (Error, Information or Suc-
cess…) to check Job Log.
Note After application job is executed or Success messages display,
check the Error message and correct your customizing or house bank

Appendix PUBLIC 166
Step # Comment
master data accordingly.
4.9.5 Bank Statement Monitor
Test Administration
Purpose
The Bank Accountant or Cash Manager can use this app to monitor the status of end-of-day bank statements from individual bank accounts. In addition to checking the status of end-of-day bank
statements for a specific date, you also get an overview of the records over the last 14 days starting from the date you specified. Based on your bank account settings, you can efficiently identify
problematic bank statements for your bank accounts and track if there is any missing statement page, any difference between the bank statement balance and the G/L account balance, any items that
are not posted.
Prerequisite
Ensure that fields related to the bank statement monitor are fully populated under the Bank Relationship tab in bank account master data. For more information, see the Advanced Bank Account
Management (J77) test script.
Fields related to the bank statement monitor:
Processing Status: Yes
Interval: for example, 10
Interval Unit: for example, Calendar Days
Factory Calendar ID: for example, 01
Difference Status: Yes

Appendix PUBLIC 167
Serial Number Status: Yes
Reconciliation Status: Yes
Procedure

Step # Comment
1 Log on Log onto the SAP Fiori launchpad as a Cash Manager.
2 Access the SAP Fiori app Open Bank Statement Monitor (F6388).
3 Edit Header Data Make the following entries and choose Go: Processing Status,Difference Status,Serial Number Status and Recon-
Key Date: Today ciliation Status are listed for monitored bank accounts.
Company Code: 1010

House Bank: <empty>
House Bank Account :<empty>
4 Check Details In the End of Day – Single Day tab, choose one item and choose >. All status in detailed information display.
5 Back Choose Back.
6 Check Status for End of Choose End of Day – Last 14 Days tab, choose an option from the list (for example, Process- End of Day bank statement status for last 14 days display.
Day – Last 14 Days ing Status,Difference Status,Serial Number Status or Reconciliation Status).
4.9.6 Intraday Bank Statement Monitor
Purpose
The Cash Management Specialist or Cash Manager can monitor the import status of intraday bank statements for the bank accounts selected for monitoring. They can compare the expected number
of imports with the actual number, and view the import schedule and status for bank accounts in a timeline that can be zoomed in or out.

Appendix PUBLIC 168
4.9.6.1 Define Monitoring Rules for Intraday Bank Statement Monitor
Test Administration
Use
In this activity, you define the monitoring rules with frequency for the intraday bank statement.
Procedure
# ment
2 Access the SAP Fiori App Open Define Monitoring Rules - Intraday Statements The Define Monitoring Rules for Intraday Bank Statements screen dis-
(FCLM_BRM_RULE). plays.
3 Edit Rule Choose Edit. The Define Monitoring Rules for Intraday Bank Statements view displays.
4 Generate Rule with Fre- Choose Create Rule with Frequency. The Generate Rule with Frequency screen displays.
quency
5 Enter Rule Data Make the following entries and choose Generate Rule and Save:
Rule ID: for example, R01
Description: Rule for intraday bank statement monitor
Time Zone: <your time zone>
Import Frequency (In Minutes): 60

Appendix PUBLIC 169
# ment
6 Continue Choose Continue to confirm the dialog box. Rule generated and saved.
4.9.6.2 Assign Monitoring Rule to Bank (Optional)
Test Administration
Use
At the bank level, you can use this process to assign a monitoring rule that applies to all the bank accounts in this bank, if there are no other rules specified for individual bank accounts.
Procedure
1 Log on Log on to the SAP Fiori launchpad as a Cash Management Specialist.
2 Access the SAP Fiori app Open Manage Banks - Basic (F1574).
3 Set Up Bank for Intraday Bank Statement Make the following entry and choose Go:
Bank Number: for example, 50070010
4 Choose Bank Choose > for Bank Number50070010. The Display Bank view displays.

Appendix PUBLIC 170
5 Edit Bank Choose Edit.
6 Enter Data Make the following entries and choose Save: The bank is updated with the rule.
Intraday Statements Rule (Bank Level): for example, R01
4.9.6.3 Define Bank Account to Monitor
Test Administration
Use
In this section, you define the bank accounts to be monitored. Only bank accounts that are set to be monitored appear in this App Bank Statement Monitor - Intraday (F3671) app.
Note Bank accounts can be linked to multiple house bank accounts by using the House Bank Account Connectivity setting. However, only bank accounts that are linked to one house bank ac-
count can currently be monitored by the Bank Statement Monitor - Intraday (F3671) app.
Procedure

Step # Comment
2 Access the SAP Fiori app Open Manage Bank Accounts (F1366A). The Manage Bank Ac-

Appendix PUBLIC 171
Step # Comment
counts screen displays.
3 Set Up Bank Account for Make the following entry and choose Go:
Intraday Bank Statement Account Number: for example, 1133698
4 Account Detail Choose > for the Account Number 1133698. The Bank Account view
displays.
5 Set Up Bank Account for Choose Edit.

Intraday Bank Statement
6 Enter Data Choose the Bank Relationship tab.

Make the following entries and choose Save:
Upload of Intraday Statements: Selected
Intraday Statements Rule (Account Level): for example, R01
Note If you maintained the rule at bank level in the prior step, you can keep the Intraday Statements Rule (Account Level) field
blank. To use a specific rule, maintain it at the bank account level.
Ensure that the house bank account exists in the selected bank account.
7 Save If the general setting for cash management is Activate Directly, the button displays as Save. For Activate via Dual Control, the button dis-
plays as Submit for Activation. For Activate via Workflow, the button displays as Submit for Approval.
Note The changes for the bank account have to be approved if the general setting for cash management is Activate via Dual Control
or Activate via Workflow. For bank account approval process, see the Advanced Bank Account Management (J77) test script.
4.9.6.4 Monitor Intraday Bank Statement
Test Administration

Appendix PUBLIC 172
Use
In this activity, you monitor the intraday bank statement.
Note The appointment of importing intraday bank statements can be generated automatically once a day via technical job SAP_FIN_FCLM_BAM_GEN_APPTS. You must wait at least one
day to monitor the bank account maintained in the previous steps.
Prerequisite
The bank account is added into the intraday bank statement monitoring hierarchy. Intraday bank statements for this specific bank account are uploaded.
Procedure

Step # Name Comment
2 Access the Open Bank Statement Monitor - Intraday (F3671). The Bank Statement Monitor - Intraday screen displays.
SAP Fiori app
3 Enter User Choose your user icon in the upper right corner, then select User Settings.
Settings Make the following entries on the Alert Setting dialog box and choose OK.
Number of Warnings: for example 4
Note this number is used to show an alert for consecutive warnings in

this App.
4 Enter Criteria Make the following entry and choose Go: For the bank accounts added into the intraday bank statement monitor hierarchy, the status shows as
Key Date: <today> Error/Warning/Success in the hierarchy according to the imported number of the intraday bank state-
ment.
Bank Country/Region: for example, DE

Appendix PUBLIC 173
Step # Name Comment
Bank Key: for example, 50070010

Import Status of Bank Account: for example, <blank>
5 Check Status Choose > (Expand Node) to check Status, Expected, Imported for the Bank For the bank accounts added into the intraday bank statement monitor hierarchy, the status shows as
Account. Alert/Warning/Success in the hierarchy according to the imported number of the intraday bank state-
ment.
4.9.7 Monitor Bank Account Balances
Test Administration
Purpose
You can monitor whether bank account balances have been imported or entered in time for bank accounts.
Note Before you monitor Bank Account Balances, make sure you have defined the following attributes for the bank accounts you want to monitor in the Bank Relationship tab of the Manage
Bank Accounts app:
Interval and Interval Unit: Together, the two attributes define the frequency of the expected bank account balance update, for example, one day or two weeks.
Factory Calendar ID (optional): You can specify a factory calendar if you want to take it into consideration.
You can refer to the step Create Bank Account in test script Advanced Bank Account Management (J77).

Appendix PUBLIC 174
Prerequisite
You have entered or imported balances for bank accounts in remote systems in the previous step Manage Bank Account Balances [page ] 151.
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Cash

Manager.
2 Access the SAP Fiori app Open Monitor Bank Account Balances
(F5176).
3 Monitor Bank Account Bal- Maintain selection criteria and choose Go. Bank account balances is displayed under different status.
ances Statement Date: <current date>
Technical ID: <blank> Note Note for Status:
Status: <blank> 1) Not Applicable:
Company Code: 1010 Bank account opening date is later than selected date.
Bank account closing date is earlier than selected date
Interval is not maintained
Interval is maintained and calculated next import date is later than selected date but it's never up-
loaded before
2) Missing
Calculated next import date is earlier than selected date
3) Uploaded
Calculated next import date is later than selected date
4.9.8 Schedule Jobs for Bank Account Balance Initialization
Test Administration

Appendix PUBLIC 175
Purpose
Some bank account balances may not show up in cash management, for example the Short-Term Cash Positioning (F5380) app, even though bank statements have been imported. With this app,
you can schedule jobs to identify these bank accounts and replicate bank account balances from their latest end-of-day bank statements to cash management. You are recommended to use this app to
initialize bank account balances for bank accounts to ensure the accuracy of short-term cash positions.
Procedure
Balance initialization can only be performed for bank accounts for which the transfer mode is defined as Balance Only or Balance and Bank Statement Items. For more information about this setting,
see step Define Bank Account Settings – Bank Statements in the Basic Bank Account Management (BFA).

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Cash Management Specialist .
2 Access the SAP Open Schedule Jobs for Bank Account Balance Initialization (F7146).
Fiori App
3 Create a New Ap- On the current view, choose Create to create an application job. The Application Jobs view displays.
plication Job
4 Choose Job Tem- In the Template Selection section, make following entries:
plate Job Template: Bank Account Balance Initialization
Job Name: Bank Account Balance Initialization
5 Maintain Schedul- Choose Step 2. In the Scheduling Options section, make the following entries: If you would like to run this job immediately, the check-box of Start Immediately should
ing Options Start Immediately: <Selected or deselected> be selected.
If you schedule this job at some time in the future, the Start and Time Zone should be
defined.
Note If you choose star immediately, other parameter do not need to main-
tain.

Appendix PUBLIC 176
Step # Comment

In the Scheduling Information dialog box, the additional scheduling options are
available.
End: Optional
Choose OK.
6 Maintain Parameter Choose Step 3. In Parameter section and make the following entries: Parameters are maintained.
Selection Parameters section:
Free Selection: <Selected>
Account Type: <empty>
Note You can select Free Selection or Cash Position Profile.
Date section:
Last Bank Statement Before: current date
Adjust Balance for Past: for example, 14
Processing Option section:
Test Run : <deselected>
8 Run this Applica- Choose Schedule to run this application job.

tion Job
9 Check Application Choose Go to update the job status. When your job’s status change to Finished, The log details display.
Jobs Log you choose Log icon to navigate to the job details.
Note After application job is executed , check the Warning/Error message and cor-

Appendix PUBLIC 177
Step # Comment
rect your customizing or house bank master data accordingly.
10 Check Jobs Result Choose Result to navigate to the job results. The job result displays.
11 Check Balance Open Manage Bank Account Balances (F5175) to check balances generatedby The balance channel of these balance is marked as Initial Load from EBS.
this report.
4.9.9 Short Term Cash Positioning
Test Administration
Purpose
In this activity, you can view the cash positions by location, company, and currency. Cash position data is calculated based on the cash position profiles that are defined in the Define Cash Position
Profiles (F5399) app.
Note If the smart currency is enabled in the cash position profile, you can switch between different currency types to get an aggregated balance.
● For the hierarchy source Bank Account Master Data, the following rules are applied:
• If the selection rule of the node is bank accounts with the same account currency, the bank account currency will be used for displaying cash position.
• If the selection rule of the node is bank accounts with the same company code, the company code currency will be used for displaying cash position.
• In other cases, the display currency defined in the cash position profile will be used for displaying cash position.
● For the hierarchy source Bank Account Hierarchy, the following rules are applied:
• If a display currency is defined in the cash position profile, the bank account currency will be used.

Appendix PUBLIC 178
• You can define the hierarchy level in the Manage Bank Account Hierarchies app.
• For bank accounts, the bank account currency will be used. For other nodes, the display currency will be used.
● For the hierarchy source Cash Pool and Bank Account Master Data
• The root node is not supported, and the hierarchy levels are fixed. The first level is company code, and the second level is currency.
• For the company code node, the company code currency will be displayed.
• For the currency node, the bank account currency of the currency will be displayed.
• For the bank account node, the bank account currency of the bank account will be used.
Prerequisites
Make sure you have defined the cash position profiles that will be used to calculate cash position data in the Short-Term Cash Positioning app.
Make sure you have defined the bank account settings in the Define Bank Account Settings - Bank Statements app.
If needed, perform bank account balance initialization to ensure all bank accounts that have balances are shown in this app.
If you want to display the cash pool hierarchy in the Short-Term Cash Positioning(F5380) app, you should choose Hierarchy Src: Derived from Cash Pool and Bank Account Master Data when
defining cash position profile in the preliminary steps. Also you need to create the relevant cash pool in the Manage Cash Pools (Version2) procedure of scope item Intercompany Process for Cash
Concentration (2U8).
Procedure

Step # Comment
2 Access the SAP Fiori Open Short-Term Cash Positioning (F5380). The Short-Term Cash Positioning view is displayed.
app
3 Maintain User Setting On the upper right corner, choose your user, choose User Settings. On the
(Optional) dialog box, maintain your user setting and choose OK.
4 Set Cash Position Pro- Make the following entries and choose Go: In the display area, data is displayed in a structure per cash position profile which is defined in
file Cash Position Profile: <CPP_01, defined in preliminary the preliminary steps.
steps>
5 Review Details of Hi- On the left navigation panel of Bank Account Hierarchy, expand and Cash Position Overview data is shown on the right side.
erarchy Level 1 choose > (Details) against one of the hierarchy level 1 node. For example: If you choose Display Position Details in the cash position profile, the Cash Position Over-
Company code level view tab page also can display.

Appendix PUBLIC 179
Step # Comment
6 Review More Details On the right side screen, in the Cash Position Overview section, choose > The cash position details is displayed.
(Details) to further check details at the hierarchy level.
7 Back Choose Back.
8 Review Details of On the left navigation panel of bank account hierarchy, expand and choose Cash Position overview data is shown on the right side.
Other Hierarchy level > (Details) against a hierarchy Node Value. For example:
If you define the hierarchy source as Cash Pool and Bank Account Master Data. The root
node is not supported, and the hierarchy levels are fixed as Company Code node ->Currency
node-> Bank Account node.
In the header Bank Account node, cash pool structure can display in the right-side screen.
9 Review Bank Account On the left navigation panel of bank account hierarchy, expand and choose General information displays.
Node > (Details) the bottom node for the Bank Account.
On the right side screen, choose the General Information tab.
10 Check Bank Account Choose the blue date under Opening Balance for Date section. Bank Account Openning Balance Details displays.
Opening Balance De-
tails
11 Export to Spreadsheet Choose the Export to Spreadsheet icon. All of the current table contents are exported to a spreadsheet.
Note Export of Spreadsheet (Ctrl + Shift + E).
4.9.10 Cash Flow Analyzer
Test Administration

Appendix PUBLIC 180
Purpose
With this app, the cash manager or bank accountant can view the aggregated amounts and line item details of cash position, medium-and-long term liquidity forecast, and actual cash flows. You can
analyze cashflows 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 flow status to the management.
Note After completing the reconciliation described in the Reconciliation Cash Flows – Intraday Memo Records procedure, use this app and filter by Reconciliation Status to view the detail line
item information from each intraday bank statement and all forecast cash flows. The cash position report is more accurate.
For example:
● Reconciled Intraday Bank Statements
● Unreconciled Intraday Bank Statements
● Unreconciled Forecasted Cash Flows
Prerequisites
Before checking the report at the Hierarchy level, you need to define the relevant hierarchies. You can define or check the hierarchies via the following Apps:
● Bank Account Group Hierarchy: Execute the Manage Bank Account Hierarchies (F4973) procedure in Advanced Bank Account Management (J77) to define/check bank account hierarchy.
● Bank Hierarchy: Use the Manage Bank Accounts - Bank Hierarchy View (WDA_FCLM_BAM_HIERARCHY) app to check the bank hierarchy.
● Cash Pool Hierarchy: Execute the procedure in Intercompany Process for Cash Concentration (2U8) test script to define/check a cash pool hierarchy by assigning a header account and subac-
counts to the cash pool.
● Liquidity Item Hierarchy: Execute the Manage Liquidity Item Hierarchies (F4966) procedure in Preliminary Steps to create your liquidity item hierarchies.
Procedure
Test Test Step Name Instruction Expected Result Pass / Fail

Step # / Com-
ment
1 Log On Log on to the SAP Fiori launchpad as a Cash Manager. The SAP Fiori launchpad displays.
2 Access the SAP Open Cash Flow Analyzer (F2332). The Cash Flow Analyzer (F2332) view displays.
Fiori app
Maintain User Set- On the upper right corner, choose your user, choose User Settings. On the dialog box, maintain your user setting
ting (Optional) and choose OK.
3 Selection Criteria Choose Adapt Filters if the filter selection fields are hidden. The list is filtered and shows all related entries within the time

Appendix PUBLIC 181
Step # / Com-
ment
Maintain selection criteria and choose Go. period.

Company Code: 1010
Note The time period settings are by Unit: D (Day), W
Currency: <leave blank> (Week), or M (Month).
Time Period: D7
Date: <current date> Note If Snapshot is enabled and the period of (Valid From to
Valid To) includes cash flow time stamp, the data flow should
Reconciliation Status: <Reconciled Intraday Bank Statements,Unreconciled Intraday
be detected under the current selected timeslot.
Bank Statements,Unreconciled Forecasted Cash Flows>
Note If Snapshot is not enabled--the period of Valid From to

Note You can choose Filters to display and save additional filter criteria. You can choose the user account at Valid To will exclude the cash flow time stamp. The data
the up right corner of the current view, then choose User Settings to designate defaults settings as needed, flow should not be detected under the current selected times-
such as: lot.
● Derive Currency
● Calendar
• No Shift: The day is not taken into account if it is a working day or non-working day.
• Shift to Working Days: The working days must be considered. The non-working day flow is au-
tomatically accumulated to the next working day or previous working day. If you select this op-
tion, choose one calendar to be mandatory, and choose Shift to Next Day or Shift to Previous
Day as needed.
● Scaling
4 Expand Hierarchy Expand the hierarchy Currency > Company Code > Bank Account. Rows for opening balance, inflow, outflow and closing balance
display for a specific bank account when they exist. The
amount of bank transfer is reflected in outflow/inflow.
5 Navigate to Dis- Select a Inflow or Outflow Item, select an amount highlighted in blue, in the dialog box for that item, choose Dis- The Cash Flow Items view displays.
play Cash Flow play Cash Flow Items. Then you can also navigate to Display Cash Flow Items by choosing any entry and choos-
Items ing Display Cash Flow Items in the respective dialog box.
Note In Balance View, only In/Out Flows can do Display Cash Flow Items navigation; Balance flows can’t
navigate.
6 Switch Views Select View pulldown menu to display the My Views dialog box and select either Balance View or Delta View Balance View displays opening balance, outflows/inflows, and
and choose Save As. closing balance.
Delta View displays outflows/inflows.
7 Adjust Layout Select Settings to change the layout and include more fields, such as Liquidity Item.

Appendix PUBLIC 182
Step # / Com-
ment
8 Export to Spread- Choose the Export to Spreadsheet button.

sheet
9 Display Bank Ac- Back arrow to the Cash Flow Analyzer view, and choose Display Hierarchy and on the Select Hierarchy dialog The Bank Account Group view displays.
count Hierarchy box, select Bank Account Hierarchy.
View Enter a Bank Account Hierarchy ID and choose OK.
Note You can display the report in the bank accounts hier-
archy. You can also display the report in cash pools.
Note If there is no Bank Account Hierarchy display here, you have not yet created the Bank Account Hierar-
chy. Cash pools can be selected from the bank account groups list.
Note If large amounts of data and the multilevel hierarchy cause slow performance, use the Expand Level for
Hierarchy in the Users Settings to limit the hierarchy to your current situation. For example, if you input 1 in
the Expand Level for Hierarchy, the result is only the first level of hierarchy is expanded.
10 Display Liquidity Choose the back arrow, then choose Display Hierarchy again. On the Select Hierarchy dialog box, select Liquid- The Liquidity Item Hierarchy view displays.
Item Hierarchy ity Item Hierarchy and enter the following data and choose OK:
View Liquidity Item Hierarchy ID: For example, LIQ_HIE
Display Currency for Liquidity Item Hierarchy: For example, EUR
Note You can choose Display Currency for Liquidity Item Hierarchy in User Settings.
11 Display Cash Con- Choose the < (Back) button and choose Display Hierarchy. In the Select Hierarchy dialog box, choose Cash Con- The Cash Concentration Simulation view displays.
centration Simula- centration Simulation and make the following entries and choose OK:
tion View Cash Pool Name: CP00A
Display Currency for Cash Pool: EUR
Note When you display cash concentration simulation view, please ensure you have performed the relevant
steps in the Intercompany Process for Cash Concentration (2U8) test script.

Appendix PUBLIC 183
4.9.11 Cash Flow Comparison – By Date Range
Test Administration
Context
You can compare actual cash flows with your forecasts in the past as well as compare different forecast records that were made on different snapshot dates. It helps you understand the accuracy of
your past forecast records and assists you in improving your cash flow forecasts continuously.
Note To view the forecast values in the past, make sure that you executed the Enable Snapshot (Optional) [page ] 11 step in the Preliminary Steps.
Procedure
# ment
1 Log On Log on to the SAP Fiori launchpad as a Cash Manager. The SAP Fiori launchpad is displayed.
2 Access the SAP Open Cash Flow Comparison - By Date Range (F3274). The Cash Flow Comparison – Actual/Forecast view is displayed.
Fiori App
3 Selection Criteria Choose Adapt Filter Bar, if the filter selection fields are hidden. Acutal-to-forecast and forecast-to-forecast comparison for cash flows of the specified time range
Maintain the following selection criteria and choose Go: is displayed.
Value Date From: For example, <the first date of cur-

rent month>
Note The Actual Flows line displays the actual cash flow. The line with a specific date, dis-
Value Date To: For example, <the last date of current plays the forecast cash flow data.
month>
Snapshot Date From: For example, <the first date of
current month>

Appendix PUBLIC 184
# ment
Snapshot Date To: For example, <the last date of cur-

rent month>
Snapshot Time: For example, 23:59:59
Display Currency: for example, EUR
Exchange Rate Type: for example, M
4.9.12 Cash Flow Comparison – By Timestamp
Test Administration
Context
You can select any two snapshot timestamps in the past and compare the forecasted cash flows as well as compare the forecasted flows with the actual flows. It helps you understand the accuracy of
your past forecast records and assists you in improving your cash flow forecasts continuously.
Note
● To view the forecast values in the past, make sure that you executed the Enable Snapshot (Optional) [page ] 11 step in the Preliminary Steps.

Appendix PUBLIC 185
Procedure

Step # Comment
1 Log On Log on to the SAP Fiori launchpad as a Cash Manager. The SAP Fiori launchpad is displayed.
2 Access the SAP Open Cash Flow Comparison - By Timestamp (W0137). The Cash Flow Comparison - By Timestamp view is displayed.
Fiori App
3 Selection Criteria Choose Adapt Filters, if the filter selection fields are hidden. Forecast records that were made on different snapshot timestamps is compared. The forecast records is
Maintain the following selection criteria and choose Go: compared with the actual cash flows.
Value Date From: For example, <the first date of

current month)
Value Date To: For example, <the last date of
current month)
Snapshot Date A: For example, <the first date of
current month)
Snapshot Date B: For example, <the last date of
current month)
Snapshot time A: For example, 23:59:59
Snapshot time B: For example, 23:59:59
Display Currency: for example, EUR
Exchange Rate Type: for example, M
4.10 Display Status of Payment Documents
Test Administration

Appendix PUBLIC 186
Purpose
In this step, you can see the payment item’s status of payment batches and/or payment run documents at a glance without the need to do a drill down from batch level to single item level. Based on
this report you can immediately and easily be able to identify if there are exceptions (payment rejected by bank, payment file not in file etc.) in this huge number of payment run documents.
Procedure
1 Log On Log on to the SAP Fiori launchpad as an Accounts Payable Accountant. The SAP Fiori launchpad displays.
2 Access the SAP Fiori app Open Display Status of Payment Documents (F7084). The Display Payment Documents app displays.
3 Maintain Filters Make the one or all following entries and choose Go. Payment item status for batching process display.
Run Date: <run date for payment run> ● Payment Item not in batch
Payment Run ID: <ID for payment run> ● Payment Item reversed
Paying Company Code: 1010 ● Payment Item not in file
● Other Exception Status

Appendix PUBLIC 187
5 Appendix
5.1 Process Chains

The process to be tested in this test case is part of a chain of integrated processes.

Appendix PUBLIC 188
Typographic Conventions
Type Style Description
Example Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names,
menu paths, and menu options.
Textual cross-references to other documents.
Example Emphasized words or expressions. www.sap.com/contactsap
EXAMPLE Technical names of system objects. These include report names, program names, transaction codes, table names, and
key concepts of a programming language when they are surrounded by body text, for example, SELECT and IN-
CLUDE.
Example Output on the screen. This includes file and directory names and their paths, messages, names of variables and parame-
ters, source text, and names of installation, upgrade and database tools.
Example Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documenta-
tion.
<Example> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to
make entries in the system.
EXAMPLE Keys on the keyboard, for example, F 2 or E N T E R .
© 2023 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or
for any purpose without the express permission of SAP SE or an SAP affili-
ate company. The information contained herein may be changed without
prior notice.
Some software products marketed by SAP SE and its distributors contain
proprietary software components of other software vendors. National product
specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for in-
formational purposes only, without representation or warranty of any kind,
and SAP or its affiliated companies shall not be liable for errors or omissions
with respect to the materials. The only warranties for SAP or SAP affiliate
company products and services are those that are set forth in the express war-
ranty statements accompanying such products and services, if any. Nothing
herein should be construed as constituting an additional warranty.
SAP and other SAP products and services mentioned herein as well as their
respective logos are trademarks or registered trademarks of SAP SE (or an
SAP affiliate company) in Germany and other countries. All other product
and service names mentioned are the trademarks of their respective compa-
nies.
See www.sap.com/copyright for additional trademark informa-

Advanced Cash Operations (J78_DE) tion and notices.
Appendix PUBLIC 189

J78 - S4CLD2308 - BPD - EN - DE - Advance Cash Operations

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

J78 - S4CLD2308 - BPD - EN - DE - Advance Cash Operations

Uploaded by

Copyright:

Available Formats

Test Script

SAP S/4HANA Cloud - 06-07-23

Advanced Cash Operations (J78_DE)

Advanced Cash Operations (J78_DE)

Advanced Cash Operations (J78_DE)

Advanced Cash Operations (J78_DE)

Advanced Cash Operations (J78_DE)

Caution Testing in a 3-System Landscape

2.1 System Access

Cash Man- SAP_BR_CASH_MAN- Cash Manager SAP_BR_CASH_MANAGER Suggested sample user

Advanced Cash Operations (J78_DE)

Accounts SAP_BR_AP_MAN- Accounts Payable Manager SAP_BR_AP_MANAGER Suggested sample user

2.3 Master Data, Organizational Data, and Other Data

Advanced Cash Operations (J78_DE)

Note Additional Default Values

Note Using Your Own Master Data

Data Sample Value Details Comments

Bank Key 50070010 ,82080000 Bank key

Country DE Country of bank key

Company Code 1010 Company code

Chart of Accounts YCOA Chart of accounts

House Bank DEBK1 House bank

BNG Create G/L Account and Cost Element

2.4 Business Conditions

Advanced Cash Operations (J78_DE)

2.5 Additional Manual Configuration

2.6 Preliminary Steps

2.6.1 Maintain Full Scope for Cash Management

In this activity, you maintain Full Scope for cash management.

Advanced Cash Operations (J78_DE)

2 Access the SAP Fiori Open Manage Your Solution (F1241).

SAP Central Business Configuration:

Test Test Step Name Instruction Expected Result Pass / Fail /

Advanced Cash Operations (J78_DE)

2.6.2 Enable Snapshot (Optional)

Caution If Basic Scope is adopted, enabling Snapshot produces an error.

2 Access the SAP Fiori Open Manage Your Solution (F1241).

Advanced Cash Operations (J78_DE)

Item Name: General Settings

SAP Central Business Configuration:

Test Test Step Name Instruction Expected Result Pass / Fail /

2.6.3 Liquidity Items

2.6.3.1 Define Source Application Accounting

Customer project: Fill in the project-specific parts.

Advanced Cash Operations (J78_DE)

Tester Name: Duration:

Test Test Step Name Instruction Expected Result Pass / Fail /

2 Access the SAP Fiori App Open Manage Your Solution(F1241).

Application Area: Finance

AcctgScope: for example， Cash Position & Liquidity Analysis

Advanced Cash Operations (J78_DE)

UpdateMode: for example, Close to Real Time

SAP Central Business Configuration:

Test Test Step Name Instruction Expected Result Pass / Fail /

AcctgScope: for example, Cash Position & Liquidity Analysis

UpdateMode: for example, Close to Real Time

Advanced Cash Operations (J78_DE)

2 Access the SAP Fiori App Open Manage Your Solution(F1241).

7 Default Liquidity item Change the default liquidity item as needed.

Advanced Cash Operations (J78_DE)

SAP Central Business Configuration:

Test Test Step Name Instruction Expected Result Pass / Fail /

3 Default Liquidity item Change the default liquidity item as needed.