R12 Upgrade ProjectR12.1.3 Cash Management analysis

Functional Design Workshop:Cash Management (CE)

2

Agenda

• Introduction

• Purpose of the workshop

• Changed functionality overview Banks Other Setup Changes

• Interactive discussion on requirements

• Action Plan/Next Steps

3

Introduction

Alicia WingTelephone: 780-508-4810E-Mail: Alicia.Wing@atcoitek.comUpgrade applications: AP, IBY, CE, iExp

Payables (AP)Payments (IBY)

Cash Management (CE)Internet Expenses (iExp)

4

Purpose of the Workshop

• Interactive two way discovery session Discuss changing functionality resulting from

upgrade Discuss related challenges Gather information on:

– Business requirements – Gaps

5

Changing Functionality Upgrading 11i to R12

• Banks

6

Internal Versus External Banks

• Internal bank accounts are centralized in Cash Management

Legal entities own bank accounts – think Taxpayer ID Number

• External bank accounts are centralized in Payments

Supplier and customer Centralization gives a single point of control

for encryption and masking

7

New Bank Account Model

• Single point of access for managing internal banks for AP, AR, Payroll, Cash Management and Treasury

• Each Bank Account is associated with a Bank and Bank Branch defined in TCA

• Is now an OA Framework/HTML form

8

TCA Definition – Why do I care?

• Trading Community Architecture (TCA)

• New terminology

• Data model

• Manages suppliers, customers, banks Any party with which you do business, except

HR related entities, such as employees

9

TCA and Banks

• Bank, bank branch, account attributes,contact persons

• Bank sites & locations• Change history & additional

attributes• Contact details & methods• Contact titles• Contact purpose or role

10

Bank Queries

• Some 11i queries will need moderate attention

• Data moved to TCA will require query rewrites

11

CE Banks and Setup and Table Change

• Setup in Cash Management (CE) Bank, bank account setup Shared with Payables, Receivables, Treasury, &

Payroll Banks & bank branches now represented as TCA

parties• Three key CE tables

CE_BANK_ACCOUNTS for bank accounts CE_BANK_ACCT_USES_ALL for account uses by

Operating Units & Legal Entities CE_GL_ACCOUNTS_CCID for bank account use

accounting data

12

Banks are Merged if:• Banks are merged during the upgrade if the

following attributes are the same: Bank number Institution type Country (w/default country setting for null) Bank administrator’s email Bank name Alternative bank name Taxpayer identifier Tax reference Description Active date End date

13

Internal Bank Account Security

• In Release 11i, bank accounts were used by a single operating unit

Operating unit security was used to control the maintenance of these accounts

• In R12, bank accounts can be accessed by multiple operating units, but are owned by a single legal entity

The bank account maintenance security was moved to the legal entity level

Security Wizard grants each responsibility access to create and modify bank accounts owned by one or more legal entities

14

Bank Account Security During Upgrade

• During the upgrade: Cash Management sets the Bank Account

Maintenance security for each responsibility that had access to the bank account forms in Release 11i

For each of these responsibilities, a legal entity is derived from the organization that the responsibility had access to in Release 11i

The responsibility is then granted bank account maintenance security for this legal entity

15

Other CE Setup Change

• System Parameters In order to provide more flexibility and control over the

reconciliation process, many of the options that used to be defined as system parameters at the system level (operating unit) have been moved to the bank account level

By placing these controls at the bank account level, both the manual and automatic reconciliation processes can be configured depending on the bank account and its uses

In addition, the remaining system parameter options and controls from Release 11i are defined at the legal entity level in R12

16

Transaction Codes and Tolerances

• Bank Transaction Codes can be linked to multiple Sources

• Reconciliation Tolerances are Defined at bank account level Available as separate tolerances for

Manual and Auto reconciliation Broken down by source for Auto

reconciliation • Reconciliation can be done across

operating units

17

Requirements /GAPs

• What are the requirements?

• What are the GAPs?

18

• Draft Functional design (RD.030) Document requirements Document GAPs (as identified)

• Possible follow up requirements session

• Review and Approval of RD.030

• Document tasks to be undertaken by POS

Action Plan/Next Steps

19© 2012 ATCO Group of Companies. All Rights Reserved 19

Questions and Answers

April 18, 2012