Wednesday, September 9, 2015

Oracle Cash Management Standard Features Differences between 11i and R12

Business Process - Standard Features
These are tables which hold the bank details irrespective of supplier or internal banks.
• ap_bank_branches
• ap_bank_accounts_all
These changes make easier and more reliable by
• Single access point
• Single Legal Entity ownership
• Usage rights granted to one or more Organizations
o Reconciliation option defined at Bank Account level
o  More flexibility and control
Comparing the 11i Vs R12
We can notice the bank was utilized into three different places , finance ,payroll and treasury, which requires altogether a different setup.
 It was one of the big issues with integration aspect, as significant problem was recognized once the Expense management and payroll uses same bank for the respective person.
These issues has been resolved in R12 release.
International Bank Account Number (IBAN)
Does not exist in 11i.
International Bank Account Number (IBAN) is an international standard for identifying bank accounts across national borders in a way that would minimize the risk of propagating transaction errors. Cash Management now validates IBAN at the time of recording bank account details.
Bank Identifier Code (BIC)
Does not exist in 11i.
Bank Identifier Code (BIC) is a unique identification for bank branches. This code can be 8 or 11 characters in length. Cash Management now validates the length of BIC when recording bank branch details.
Payment Group based Bank Statement Reconciliation
Does not exist in 11i.
Oracle Cash Management now utilizes the new Payment Group Number attribute as an optional matching criterion for manual and automated reconciliation of bank statements.
Option to Override Country-Specific Validation for Bank Accounts
Does not exist in 11i.
Sometimes legacy bank account numbers do not conform to modern country-specific validation rules. Users can now disable the default country-specific bank validations to migrate legacy bank account information.
EDIFACT Bank Statement Format Update
Does not exist in 11i.
The bank statement loader program supports EDIFACT statements. With this release, the following additional data processing features are addressed:
• Support for non-numeric characters in bank balances. The opening and closing balance amounts sent in the EDIFACT statements contain non-numeric characters. The bank statement loader and import program is enhanced to convert the non-numeric characters into numeric values.
• Support loading and importing the Record 05. The current seeded loader is enhanced to handle the record type 05. This additional record is defined as part of the EDIFACT standard and contains the contextual information of Record 04.
Copy Bank Transaction Codes
Does not exist in 11i.
Bank transaction codes are used by banks to identify the types of transactions on bank statements. The codes are set up for each bank account for reconciliation purposes. For organizations having several bank accounts, it can be a cumbersome process to manually setup these transaction codes since most bank accounts for a specific bank use the same transaction codes.
A new concurrent program has been provided to copy the bank transaction codes from one bank account to another bank account(s).
Load Bank Statements for the Current Day
Does not exist in 11i.
In previous releases, users could only import bank statements and perform bank balance maintenance for past dates. Users can now enter or import bank statements and perform bank balance maintenance for the current date.
Manual Entry in Cash Position
Does not exist in 11i.
The cash position functionality has been enhanced to allow cash managers the ability to manually enter cash flows into their cash positions allowing for greater flexibility in their decision making process.

No comments:

Post a Comment

Best Blogger TipsGet Flower Effect