FSFI005 Cash Management

7/28/2019 FSFI005 Cash Management

1/7

SAP SYSTEM

Functional Specification Finance - Cash Management

Doc. Ref.: FSFI005 version 01

Core Functional Specification

FinanceCash Management

Written By:

Joanna Wasilewska

FICO Consultant

Signature Date

Approved By:Carmen E Brown

Finance Solution Architect (Core Team)

Signature Date

Global Process Owner Signature DateGudjon Gustafsson

Process Champion Signature Date

Mark Keatley

EVPSignature Date

Controlled Document DO NOT COPY without permission Page 1 of 7


2/7

SAP SYSTEM




REVISION DETAILS

Issue No. Issue Date Amendment Details

01 18-July 2011 Initial Release


3/7

SAP SYSTEM



TABLE OF CONTENT

1 PURPOSE......................................................................................................................42 SCOPE.......................................................................................................................... 4

3 OVERVIEW.....................................................................................................................4

4 DETAILED FUNCTIONAL SPECIFICATIONS................................................................................4

4.1 Cash Position............................................................................................................44.2 Liquidity Analysis .......................................................................................................44.3 Source Symbols .........................................................................................................44.4 Planning Groups ........................................................................................................54.5 Planning Levels..........................................................................................................54.6 House Banks and Bank Accounts .....................................................................................54.7 Manual Bank Statement ...............................................................................................54.8 Variants for Manual Bank Statement ................................................................................5

4.9 Electronic Bank Statement ...........................................................................................6

5 ROLES AND RESPONSIBILITIES.............................................................................................6

6 DEFINITIONS AND ACRONYMS.............................................................................................6

7 DOCUMENT REFERENCES...................................................................................................6



4/7

SAP SYSTEM



1 PURPOSE

The purpose of this document is to define what the SAP system should do and what functions and facilities areto be provided to fulfill the requirements of the User Requirements Specification. It describes design objectivesfor the SAP system from a functional perspective.

2 SCOPE

The scope of this Functional Specification covers the Cash Management Process.

3 OVERVIEW

This document contains an outline of all of the configuration and customisation in SAP required for the CashManagement process, which is detailed in the following scenarios:

SC24 Cash Management

4 DETAILED FUNCTIONAL SPECIFICATIONS

4.1 Cash Position

The cash position report provides short-term liquidity information on the daily cash inflow and outflow of thebank accounts. To enable the use of the Cash Position report the G/L accounts relevant for the status analysishave been assigned a cash management level in the company code segment.

The cash position provides the current overview of the bank accounts by value date and, on account of the

integration with payment advices, a complete overview of the short-term movements in liquidity.

4.2 Liquidity Analysis

The liquidity forecast comprises the medium-term the incoming and outgoing cash flows, as well as the planneditems in the sub-ledger accounts for a long period. The increments can be changed from daily for the firstweek, to weekly for the next two months, and then monthly for the next six months.

4.3 Source Symbols

The source symbols group the planning levels according to the sources that provide them with data. They canthen be assigned to either the liquidity forecast or the cash position.

For details of the Source Symbols, please refer to Appendix 1.


Financial AccountingFinancial Accounting


5/7

SAP SYSTEM



4.4 Planning Groups

Customers and vendors are assigned to a planning group by making an entry in the master record. A planninggroup represents particular characteristics, behaviors, or risks of a customer or vendor group. It enables analysisof incoming and outgoing payments according to the probability of the cash inflow or outflow, the amount, andthe type of business relationship.

For details of the Planning Groups, please refer to Appendix 2.

4.5 Planning Levels

Typical financial transactions in Cash Management are displayed using planning levels, which explain theopening and closing balances.

General Ledger and sub-ledger-accounts can be assigned to a planning level to analyse the cash position orliquidity forecast by using the source symbol.

For details of the Planning Levels for G/L Accounts, please refer to Appendix 3, and for Planning Levels for Subledger Accounts see Appendix 4.

4.6 House Banks and Bank Accounts

To enable the use of automatic payment run programs or the posting of bank statements automatically HouseBanks must be created within SAP. These House Banks will correspond to the Companies Banks. Furthermore,each Bank Account that is maintained with these Banks will be created in SAP as a Bank Account that is linkedto the House Bank.

4.7 Manual Bank Statement

To be able to post a Manual Bank Statement within SAP the main settings are as follows:

Create account symbols the G/L accounts (such as banks, cash receipts and outgoing payments) whose

postings have to be made from account statement. Each G/L account is assigned to an account symbolto the G/L account numbers. For details of the Account symbols please refer to Appendix 5.

Assign accounts to account symbols - Define which postings are to be triggered by transactions in the

account statement (such as bank transfer, incoming payment. For details of the Assignment of theAccount symbols please refer to Appendix 5.

Create keys for posting rules - posting rules are assigned to possible transactions in the account

statement file. A list of assignments where one external transaction code is assigned to one posting ruleis called transaction type. For details of the Posting Rules please refer to Appendix 6, and Appendix 7for Posting Specifications.

Create a transaction type - bank details are assigned for the account statements that have to be

imported, to a transaction type. All the house bank accounts at a particular bank are usually assigned tothe same transaction type.

4.8 Variants for Manual Bank Statement

The default layout Manual Bank Statement can be changed and new layouts or Variants can be created to ifrequired, to adapt the assignment and/or selection of the account assignment fields. These will be created asnecessary during the design phase of the project.



6/7

SAP SYSTEM



4.9 Electronic Bank Statement

If possible Actavis would prefer to import the bank statement electronically; this will depend on the specifiedbank producing a bank statement in an SAP readable electronic format. When this is the case SAP functionalityto will be used to import the statement, with a similar posting logic as that defined for use with the ManualBank Statement.

Certain Banks have an electronic statement format that initially requires the use of a conversion program, thisfunctionality will used when required as a precursor to posting the Bank Statement.

5 ROLES AND RESPONSIBILITIES

Roles Responsibilities

SAP Functional

Consultant

Authors this Functional Specification document

Ensures this document accurately reflects its intendedPurpose and Scope

SAP Solution Architect Ensures this document accurately reflects its intended

Purpose and Scope

Review and approval of this document

Global Process Owner Ensures this document accurately reflects its intended

Purpose and Scope


Process Champion Ensures this document accurately reflects its intended

Purpose and Scope


EVP Ensures this document accurately reflects its intended

Purpose and Scope


6 DEFINITIONS AND ACRONYMS

Term Description

SAP Glossary All terms and descriptions of SAP across all modules.

Location: Core Team on SharepointFI Financial Accounting module in SAP system (External) Reporting

CO Controlling module in SAP system (Internal) Management Accounting

7 DOCUMENT REFERENCES

Doc Ref Document Title

1. BBR2R Core Business Blueprint Record to Report (R2R)

2. CSFI005 Core Configuration Specification Cash Management



7/7

SAP SYSTEM




FSFI005 Cash Management

Documents

Transcript of FSFI005 Cash Management