Cash Management

Status Analysis and Cash

Concentration
Overview

Purpose and Benefits:

Purpose
 The cash position overview provides information on the current financial state of the bank
accounts.
 It is the starting point for cash concentration in which the balances from various bank accounts
are concentrated in one target account, taking minimum balances and payment optimization
into consideration.
 Understanding posting processes that affects liquidity (invoice and incoming payment).
 It presents the main functions for retrieving information about the liquidity status.

Benefits
Cash Management in IFMIS provides basic functions such as:
 Quickly and reliably transfer all cash-relevant information from internal and external sources
into the cash management system (inbound data)
 Performs analysis and reporting of current and future cash flows to help you make cash
management decisions (analysis and decision)
 Communicates with banks and other business partners based on the results of the decision
process (outbound data).

Key process flows covered

 Cash Management Status Analysis and
 Cash Concentration.
Requirements:

Required
 Oracle E-Business Suite R12

Company roles involved in process flows

 Treasurer
 Accounts Payable Accountant
 Bank Accountant
Detailed Process Description:
 Posting of a vendor invoice in local and foreign currency.
 Posting of a customer invoice in local currency (from a sales order).
 Posting of planning items and memo records.
 Execution of the report showing cash position and the liquidity forecast. All
posted documents will be displayed on the value date basis.
 After posting the manual bank statement, the flow between the planning
levels will be demonstrated.
 Due to the actual postings of the bank statement, the memo records will be
archived automatically (by using a special report).
 The function of cash concentration will illustrate how to identify the relevant
amounts and transfer them from one account to another.
Process Flow Diagram
Cash Management Status Analysis and Cash Concentration
 Legend

Symbol Description Usage Symbol Description Usage Comments

Comments

Band: Identifies a user role, such as Accounts Role band To next / From last Diagram: Leads Flow chart continues on the next /
to the next / previous page of the previous page
Payable Clerk or Sales Representative. This band contains tasks Diagram
<Function>

can also identify an organization unit or group, common to that Diagram

rather than a specific role. role. Connection
The other process flow symbols in this table go into
these rows. You have as many rows as required to
cover all of the roles in the scenario. Hardcopy / Document: Identifies a Does not correspond to a task
printed document, report, or form step in a document; instead, it is
Hardcopy / used to reflect a document
External Events: Contains events that start or end the Document generated by a task step; this
External

scenario, or influence the course of events in the shape does not have any outgoing
to SAP

scenario. flow lines

Financial Actuals: Indicates a Does not correspond to a task

Flow line (solid): Line indicates the normal sequence Connects two financial posting document step in a document; instead, it is
tasks in a Financial used to reflect a document
of steps and direction of flow in the scenario. scenario generated by a task step; this
Flow line (dashed): Line indicates flow to infrequently-
Actuals
process or a shape does not have any outgoing
used or conditional tasks in a scenario. Line can non-step event flow lines
also lead to documents involved in the process flow.

Business Activity / Event: Identifies an action that Does not Budget Planning: Indicates a Does not correspond to a task
either leads into or out of the scenario, or an outside correspond to a budget planning document step in a document; instead, it is
Business Process that happens during the scenario task step in the used to reflect a document
Budget generated by a task step; this
Activity / document
Planning shape does not have any outgoing
Event flow lines

Unit Process: Identifies a task that is covered in a Corresponds to

step-by-step manner in the scenario a task step in Manual Process: Covers a task Does not generally correspond to
the document that is manually done a task step in a document;
Unit Process Manual instead, it is used to reflect a task
Proces that is manually performed, such
s as unloading a truck in the
warehouse, which affects the
process flow.
Process Reference: If the scenario references another Corresponds to
scenario in total, put the scenario number and name a task step in
Process here. the document
Existing Version / Data: This block Does not generally correspond to
Reference covers data that feeds in from an a task step in a document;
Existing external process instead, this shape reflects data
Version / coming from an external source;
Data this step does not have any
Sub-Process Reference: If the scenario references Corresponds to incoming flow lines
another scenario in part, put the scenario number, a task step in
Sub- name, and the step numbers from that scenario here the document
Process
Reference System Pass / Fail Decision: This Does not generally correspond to
System block covers an automatic a task step in the document;
Pass/F decision made by the software instead it is used to reflect an
Process Decision: Identifies a decision / branching Does not
ail automatic decision by the system
Decisio that is made after a step has been
point, signifying a choice to be made by the end usually executed.
user. Lines represent different choices emerging correspond to a n
Proces
from different parts of the diamond. task step in the
s document;
Decisio Reflects a
n choice to be
made after step
execution