Cash Management on HANA

FUNCTIONAL/TECHNICAL SPECIFICATIONS

DOCUMENT SUMMARY

Project CASH MANAGEMENT ON HANA

Code HTTPS://JIRA.BOOKING.COM/JIRA/BROWSE/SAP-22238
Title CASH POSITION
Version DRAFT
Business Team TREASURY TEAM
Business Process BANK ACCOUNT MANAGEMENT (INCLUDING CASH POOLING)
 Cash Management on HANA

1 DOCUMENT SCOPE ..................................................................................................................................................... 3

2 CHANGES TO THE DOCUMENT ............................................................................................................................... 3

2.1 CHANGES SUMMARY .................................................................................................................................................. 3
3 INTRODUCTION ........................................................................................................................................................... 3
3.1 APPROACH DESCRIPTION ............................................................................................................................................ 3
4 GENERAL REQUIREMENTS ...................................................................................................................................... 4
4.1 USER REQUIREMENTS ................................................................................................................................................. 4
4.2 DETAILED FUNCTIONAL SPECIFICATIONS ................................................................................................................... 7
4.3 DETAILED TECHNICAL SPECIFICATIONS ................................................................................................................... 13
5 DATA PROCESSING ................................................................................................................................................... 14
5.1 SAP TRANSACTIONS/FIORI APPLICATIONS INVOLVED .............................................................................................. 14
5.2 PROCESSING DETAILS ............................................................................................................................................... 14
5.3 AUTHORISATION ....................................................................................................................................................... 14
5.4 PERFORMANCE CONSIDERATIONS ............................................................................................................................. 14
6 OPEN ISSUES ............................................................................................................................................................... 15

7 TABLES ......................................................................................................................................................................... 15
7.1 ADDITIONAL DETAILS ............................................................................................................................................... 15

2
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

1 Document scope
This Document describes business processes related to Bank Account Management, which includes:
1. Basic BAM configuration
2. Workflows for maintaining bank account: Open, Change, Close, Review bank accounts.
3. Cash Pooling functionality (except automatic cash pooling custom development, that is described in document
“Auto Cash Pooling.doc”)
4. “Activated” and “to be activated” fiori apps
5. Corresponding custom developments (Except auto cash pooling)

2 Changes to the document

2.1 Changes Summary

Change Id Date Author Comments

1 28.07.2016 Denis Grinko Document created

...

3 Introduction

3.1 Approach description

For booking.com purposes activated all available standard workflows in BAM. They were copied
into custom workflows and modified according to user’s requirements.
Field statuses (visible/changeable/mandatory) were modified for each workflow, for each status.
“Account type” field’s dictionary was filled with custom description “Account used for … ”. This
field was opened for changing. And can be used as a filter in “Cash Position Details (booking.com)”
fiori app.

3
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

4 General Requirements

4.1 User requirements

Was requested to realize workflow processes, that are listed below, to transport bank management
process from (mail + phone + direct contacting) to SAP system.
Standard steps are presented in grey color; differences (where steps were modified/replaced) are
marked with orange color.

Was realized workflows:

4
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

5
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

Workflow should be triggered when one of the listed fields is changed:

Bank Account’s Tab Field Comment
General Data Account Holder
Currency
IBAN
Account Number
Control Key
Connectivity Path House Bank
House Bank Account ID
Alternative Bank Account
General Ledger Account
Additional Data Exchange Rate Type For Bank Statement Custom field

6
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

4.2 Detailed Functional Specifications

Description of all functional steps (with screen samples) performed to cover the following tasks:

 Basic configuration
All basic configuration was done in tcode spro => Financial Supply Chain Management = >
Cash and Liquidity Management => Bank Account Management:

1. Number ranges were preconfigured before BAM implementation (According to BAM

Lite implementation)
2. Basic Settings:
a. Bank Account Master Data Setting – attached number ranges for Bank Accounts
and Change Requests (Change requests are used in workflow processes)

7
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

b. Account Type Definition dictionary was extended for cash position with
descriptions: “Account is used for …” (according to user’s excel with account
descriptions). All account here were determined as “Inflow and Outflow” and
have no attribute “Operational”/”Functional” since it is not needed for current
purposes.

c. Sensitive Fields for Modification Process were filled according to user’s

requirement:

8
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

No other options from “Basic Setting” were touched.

3. Maintain the Event Type Linkage for Triggering Workflow Processes:

Deactivate standard one, Activate custom 1:

1
WS74300043 is the main workflow that distributes change requests between other sub-workflows (open, change, close
etc.) according to current operation. It should be replaced with custom one that will use custom sub-workflows.
9
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

4. Define responsibilities should be determined in target system according to user roles in

workflows. The rules to use here are: 74300006, 74300007, 74300008.
 Workflows (tcode swdd):
0. In each workflow first approval step was changed: removed restriction, that initiator can
be 1-st approver. Deleted “Excluded” = &WF_INITIATOR&

1. Open bank account workflow is WS90100001. It is a copy of 74300047 with:

a. Exchanged order of 1st and 2 nd steps.
b. Changed binding for task TS74300047 for both levels. In binding values of
“reject_status”, “approve_status”, “next_step” and “prev_step” should be
exchanged between 1st and 2 nd step. To save the approval route.
c. Exchanged “Cash Oper. Approval” and “Cash Mgr Approval” in every condition
and every loop. Exchanged names of those steps (loops, conditions)

10
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

11
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

2. Change bank account workflow is WS90100003. It is a copy of WS74300048 with the

same changes that are mentioned in points 1.a-1.c
3. Close bank account workflow is WS90100004. It is a copy of WS74300050 with the
same changes that are mentioned in points 1.a-1.c
4. Mass change (change signatories) bank accounts workflow is WS90100005. It is a copy
of WS74300049 with the same changes that are mentioned in points 1.a-1.c
5. Review bank accounts workflow is WS90100007. It is a copy of WS74300065 with next
changes:
a. AC rule 74300013 (rule that reads field “bank contact person” in bank account
master data) were replaced by 74300007 (bank accountant) 2.
b. Enhanced class for reviewing bank account to remove checks about “Bank
Contact Person field is empty”. Details in point 4.3.
 Task TS74300047 (Bank Account Management: Decision) was set to “General”. It should be
configured in target system. If it will not be configured – no users will receive workitems
from BAM.

2
That’s why review’s change requests are split if different contact persons are entered in “bank contact person” field.
12
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

 Cash Pooling
1. For cash pooling authorities for infotype 6000-6010 were added to role
Z_SFIN_CASH_MANAGER_MAINT:

2. Note 2246035 was implemented (adds “refresh” button to cash concentration screen,
payment requests list)
3. Added enhancement to trigger “refresh” button after PR are created. Details in point 4.3

4.3 Detailed Technical Specifications

Description of all technical steps (with screen samples) performed to cover the following tasks:

Full list of involved technical objects:

Object type Object name Description

Badi ZFCLM_BAM_FIELDS_CTRL_IMPL Changes fields control for workflows and “edit” mode of bank
Implementation account screen.
For each workflow was replaced code between methods:
OPEN_REQUEST_STEP_ONE TWO
MODIFY_REQUEST_STEP_ONE TWO
CLOSE_REQUEST_STEP_ONE TWO
CHANGE_SIG_REQUEST_STEP_ONE  TWO

For methods with step_one, OPEN and MODIFY was added

code for table gt_hba from method THREE to allow user to
work with connectivity path at first step (key users still can
work with connectivity path too)
Class ZCL_FCLM_BAM_FLD_CTRL_BADI_IMP
Enhancement ZCL_BAM_DEFAULT_TAB_FOR_CLOSE Changes default tab for close bank account workflow. Now
default tab will be for
1st step: “additional data”
2nd step: “general data”

Because Cash Manager step was exchanged with Banking

Specialist (Bank Accountant).
Enhancement ZCASHPOOL_REREAD_PAYRQ_TAB Launches button “refresh” on cash concentration screen after
payment requests are created. So, after PR are created, PR’s list
is updated.
Enhancement ZCL_FCLM_BAM_CURR_USER_ENHA Allows user with corresponding role to approve any review
requests. Even, when they are not bank account’s contact

13
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

person. It is needed, because AC rule for review process was

changed from.
Enhancement ZDO_REVIEW Copy of method
CL_FCLM_BAM_ACC_REVIEW_FEEDER=>DO_REVIEW
with excluded check that “Contact Person” field is filled. After
that enhancement operator “exit” is executed, so, standard code
will not be processed.

5 Data Processing

5.1 SAP transactions/Fiori Applications involved

List of functionalities.
All BAM transactions can be reached from Fiori Launchpad Catalog “Booking.com Cash Manager”
or through nwbc, role SAP_SFIN_CASH_MANAGER.
Transactions for cash pooling are listed in “Auto Cash Pooling.doc”.

5.2 Processing details

Specify for each functionality listed in the previous point the input parameters and sample screens.

5.3 Authorisation
Roles needed.
Backend:
Z_SFIN_CASH_MANAGER_MAINT – maintain bank accounts

Frontend:
SAP_UI2_FIORI_CATALOGS_READ
SAP_UI2_USER_700
ZBOOK_TCR_CASHMANAGER
ZTRUSTED_SYSTEM
Z_SAP_SFIN_BCR_CASHMANAGER
Z_SAP_UI2_FIORI_CATALOGS_READ
Z_SAP_UI2_USER_700

5.4 Performance considerations

If applicable.

14
FUNCTIONAL SPECIFICATIONS CM_Cash Position
 Cash Management on HANA

6 Open Issues

7 Tables

7.1 Additional details

15
FUNCTIONAL SPECIFICATIONS CM_Cash Position