Thursday, January 22, 2015

Oracle GL, AP, AR, FA and CASH Standard Features Differences between 11i and R12

Oracle General Ledger Standard Features Differences between 11i and R12
Standard Features
In 11i, when users had to enter or process data for multiple operating units, they had
to login to different responsibilities because each responsibility could only access
one operating unit. So if there were a centralized payment processing center where
users processed payments for multiple organizations, they would have to keep
logging in and out of different responsibilities to process payments for a different
organization or operating unit.
Now in Release 12, Multi-Org Access Control enables companies that have
implemented a Shared Services operating model to efficiently process business
transactions by allowing users to access, process, and report on data for an
unlimited number of operating units within a single application’s responsibility.
• This increases the productivity of Shared Service Centers as users no longer
have to switch application responsibilities when processing transactions for
multiple operating units. Data security and access privileges are still maintained
using security profiles that will now support multiple operating units.
• Enhanced Multi-Org reporting is not the same as cross-organization reports that
allow you to run a report at the ledger level to obtain results for all operating units
assigned to that ledger or obtain results for all the operating units for a GRE/LE.
• Multi-Org Reporting allows a user to select any operating unit from a list of
accessible operating units. This allows users to report on data for multiple
operating units from a single application responsibility. The benefit of this
1) Reduced reporting time
2) Improved efficiency
Accounting Setup Manager
Exist with the name “Set of Books”. The ledger replaces the 11i concept of a set of Books.
Set of books is defined by 3 C’s,
1. chart of accounts
2. functional currency
3. accounting calendar,
The ledger is a basic concept in Release 12.
Now, legal Entities can be mapped to entire Ledgers or if you account for more than one legal entity within a ledger, you can map a legal entity to balancing segments within a ledger
While a set of books is defined by 3 C’s,
1. chart of accounts
2. functional currency
3. accounting calendar,
The addition in this list the ledger is defined by a 4th C: the accounting method,
This 4th C allows you to assign and manage a specific accounting method for each ledger. Therefore, when a legal entity is subject to multiple reporting requirements, separate ledgers can be used to record the accounting information.
Accounting Setup Manager is a new feature that allows you to set up your common financial setup components from a central location.
What is Accounting Setup Manager?
Accounting Setup Manager is a new feature that streamlines the setup and implementation of Oracle Financial Applications. The Accounting Setup Manager will facilitate the setup required for simultaneous accounting for multiple reporting requirements.
Sub Ledger Accounting (SLA)
GL was not integrated with SLA.
GL is integrated with SLA to enable a unified process to account for subledger transactions and post data to GL, and to provide a consistent view when drilling down from GL to subledger transactions
Enhanced Foreign Currency Processing by Reporting Made easy
Features mentioned in R12 were either not available or available with a limited extent in 11i.                                                                                                                                   In Release 11i, I can review the 500 GBP and the 1200 USD that results from converting the 500 GBP, and the total 2200 USD which is the USD balance in the Cash Account. The $2200 is the sum of the $1000 entered in USD and the $1200 converted from the 500 British Pounds. However, I view that a 1000 USD were entered directly in USD.
GL has added new features and enhanced existing features to support foreign currency processing. They are mainly as:

1) In R12, MRC feature is enhanced with a feature call Reporting Currencies. That mean it will now support multiple currency representations of data from any source, including external systems, Oracle or non-Oracle subledgers, and Oracle General Ledger journals and balances.

2) The second one is in reporting to view balances that were entered in your ledger currency separate from those balances that were entered and converted to the ledger currency. The change in R12 is that balances entered in the ledger currency are maintained separately from balances converted to the ledger currency for use in Reporting and Analysis. Here is an example. Assume we have a ledger and the ledger currency is USD.
I enter and post two journals; one in 1,000 US Dollars, and another in 500 British Pounds that gets converted to 1200 US Dollars.                                                                                                                                                                             In Release 12, I can view the 1000 USD by performing an account inquiry on the Cash account for balances entered only in the ledger currency. The amounts entered in foreign currencies that were converted to the ledger currency will not be included in the balance. Of course, if I want to retrieve all balances in USD, both the entered as well and the converted, I can still do that in Release 12.
Creating foreign currency recurring journals
In Release 11i, you could define recurring journals using the functional currency or STAT currency
In Release 12, you can create recurring journals using foreign currencies. This is particularly useful if you need to create foreign currency journals that are recurring in nature. For example, assume a subsidiary that uses a different currency from its parent borrows money from the parent. The subsidiary can now generate a recurring entry to record monthly interest payable to the parent company in the parent's currency
Data Access to Multiple Legal Entities and Ledgers
This feature was not available in Release 11i.
You no longer have to constantly switch responsibilities in order to access the data in a different ledger. You can access multiple ledgers from a single responsibility as long as all ledgers share the same chart of accounts and calendar
Simultaneous Opening and Closing of Periods for Multiple Ledgers
This feature was not available in Release 11i.
You no longer have to open and close periods for each ledger separately. You can now open and close periods across multiple ledgers simultaneously by submitting Open and Close Periods programs from the Submit Request form
Simultaneous Currency Translation of Multiple Ledgers
This feature was not available in Release 11i.
You can run the Translation program for multiple ledgers simultaneously, if you are managing multiple ledgers
Financial Reporting for Multiple Ledgers
This feature was not available in Release 11i
Now with this feature you can run Financial Statement Generator (FSG) reports for multiple ledgers simultaneously. This is useful if you manage multiple ledgers and want to run a balance sheet or income statement report for all of your ledgers at the same time
Cross-Ledger and Foreign Currency Allocations
This feature was not available in Release 11i
You are able to allocate financial data from one or more ledgers to a different target ledger. This enables you to perform cross-ledger allocations, which is useful for purposes such as allocating corporate or regional expenses to local subsidiaries when each entity has its own ledger
Streamlined Automatic Posting
This feature was not available in Release 11i
You can now share AutoPost Criteria sets across multiple ledgers that share the same chart of accounts and calendar and use the AutoPost Criteria sets to post journals across multiple ledgers simultaneously
Streamlined AutoReversal Criteria Setup Integrated Web-based
Integrated Web-based Spreadsheet Interface was not available in Release 11i
AutoReversal Criteria Sets can also be shared across ledgers to reverse journals across multiple ledgers. This is enhanced by integrated Web-based Spreadsheet Interface.
Journal Copy
This feature was not available in Release 11i
Now we can copy entire journal batches. You can copy journal batches with any status. The system will create a new journal batch containing the same journal entries. You may also change the batch name, period, and/or effective date while copying the journal batch. After copying the journal batch, you may modify the unposted journals in the same manner as any manually created journals.
Replacement for Disabled Accounts
This feature was not available in Release 11i.
Normally when an account is disabled, you can prevent transactions that include the account from erroring during journal import by defining a replacement account for the disabled account. Journal import replaces the disabled account with the replacement account and continue the journal import process if the replacement account is valid. This improves processing efficiency by preventing the journal import process from erroring and enabling the successful creation of the journal with minimal user intervention when an account has been disabled.
Data Access Security for Legal Entities and Ledgers
This feature was not available in Release 11i.
In R12, since you can access multiple legal entities and ledgers when you log into Oracle General Ledger using a single responsibility, Oracle General Ledger provides you with flexible ways to secure your data by legal entity, ledger, or even balancing segment values or management segment values. You are able to control whether a user can only view data, or whether they can also enter and modify data for a legal entity, ledger, balancing segment value or management segment value.
Prevent Reversal of Journals with Frozen Sources
This feature was not available in Release 11i.
You can no longer reverse journals from frozen sources defined in the journal sources form. If the journal is created from a frozen source, the journal cannot be modified even if the source is subsequently unfrozen in the future. This provides streamlined data reconciliation with subsystems. Not being able to reverse journals that originated in subledgers will ensure that the account balances will always tie out with General Ledger. If you need to reverse a subledgers journal, then you should do so in Sub ledger Accounting or the sub ledger application.
Prevent Reversal of Unposted Journals
This feature was not available in Release 11i.
You also can no longer reverse unposted journals. This ensures data integrity and better audit ability. In the past when we allowed you to reverse unposted journals, there was a risk that the original journal could be deleted so you could end up reversing something that didn't exist. Now, all reversals can be tied back to the original posted journal
Control Accounts
This feature was not available in Release 11i.
You are able to control data entry to an account by ensuring it only contains data from a specified journal source and to prevent users from entering data for the account either in other journal sources or manually within general ledger.
Enhanced Financial Statement Generator Reporting to Display Content Set Values
This feature was not available in Release 11i.
Users can now publish a Financial Statement Generator (FSG) report with a content set. When the Page Expand option is selected, each value in the content set becomes visible as an individual tab in the Microsoft Excel workbook.
Enhanced Financial Statement Generator Reporting to Support Drill-down for Non-Contiguous Account Ranges
This feature was not available in Release 11i.
General Ledger provides a streamlined drill path from the monetary amounts in financial statements to the underlying detail balances. After running a FSG report, users can drill from any summarized financial balance in the report directly to the detail account balances that comprise the summary amount, even if the summary amount represents multiple non-contiguous account ranges.
This process allows users to perform the drill down efficiently in one step and eliminates the need to perform multiple searches by selecting one account range at a time. It also improves usability by enabling the user to see all the information on a single page.
Streamlined Excel-based Financial Statement Publishing
This feature was not available in Release 11i.
Users can now publish FSG reports natively as Excel files. Users can create presentation templates using Excel, and then run reports using BI Publisher’s Excel publishing capabilities to generate an Excel file that opens directly in Excel. Users can then drill to the underlying details, leveraging General Ledger’s Account Analysis and Drilldown capability.
Synchronize Reversing Journals between Primary and Secondary Ledgers
This feature was not available in Release 11i.
Oracle General Ledger now streamlines the propagation of journal reversals from the primary ledger to the associated secondary ledgers. The manual reversal of primary ledger journal entries now automatically reverses the corresponding journal entries in the secondary ledger.
Limit Accounts in Budget Wizard
This feature was not available in Release 11i.
In prior releases, users could only use specific account code combinations ranges in the Oracle General Ledger Budget Wizard to limit accounts for the budget entry process.
The Budget Wizard now allows users to use low and high values for one or more segments in the account range.
Oracle Payable Standard Features Differences between 11i and R12
Standard Features
Few Features like invoice Lines, Line level approvals, Matching to a PO shipment or receipt, Suppliers in TCA makes a complete new look.
• Suppliers defined in AP.
• Supplier contacts replicated for each supplier site.
• Supplier becomes as TCA Party.
• Suppliers Sites as TCA Party Site for each distinct address.
• Contacts for each supplier/address , it means Single supplier address and contact can be leveraged by multiple sites, for each OU
o A single change to an address can be seen instantly by all OUs
o No longer need to manually 'push' updates across OUs.This can be best understood by the figure below
• Had only distributions line.
• Allocation of freight and special charges are captured at the distribution level only
• Tax and payment and Project accounting Payment was captured through global Descriptive Flexfields.
Invoice Lines as a new additional line accommodated in Invoice data model
Because of introduction of invoice line there is significant improvement of data flow with n other oracle modules like
• Fixed Asset - Asset Tracking
• Business Tax - Tax line
• Payment - Payment
• SubLedger Accounting - Accounting
Allocate freight and special charges are captured to the lines on the invoice
Invoice distributions created at the maximum level of detail similar to 11i.
Core functionality
Internal Bank Accounts
In 11i we have seen internal Banks defined in AP and that is shared by AP/AR/CE, Payroll and Treasury and they are bank accounts often replicated in multiple Ous
Where as in R12,
• Bank and Branch become part of TCA Parties.
Internal Bank Account in Cash Management which is owned by a Legal Entity. Here the Operating units have granted usage rights
Suppliers Bank Accounts
• Banks/Branches defined in AP
• Bank accounts often replicated in multiple OUs Before
• Suppliers, Banks and Branches are defined as Parties in TCA
• Supplier (party's) payment information and all payment instruments (Bank Accounts, Credit Cards) moved into Oracle Payments.
Integration with Oracle E-Business Tax
• Oracle standard functionality was based out of User which determines tax by assigning Tax Codes at line level of invoice and Tax rules was controlled at underline code.
• There was global descriptive flex fields were captured for country-specific tax attributes.
• More important most of the setup performed at OU level
• A new module eBusinessTax determines tax based on facts about each transaction, this is reason why Oracle has introduced additional line information at invoice level.
• The module "ebusiness Tax" set and configure Tax rules which can be viewed
• Tax attributes collected in fields on key entities
• Configure tax rules once per regime and share with your legal entities
Replace Supplier Bank Accounts on Invoices

In today’s business environment, it is a common practice to change bank accounts. If suppliers change their bank accounts, Oracle Payables can now automatically update all unpaid and partially paid invoices with the new bank account information. When users end date an existing supplier bank account and provide a new active bank account, Oracle Payables will automatically update the remit-to bank account information on unpaid and partially paid invoices. This streamlines transaction processing and prevents the need to update each invoice manually.
Business Intelligence Publisher Support for Selected Payables Reports

The following Oracle Payables reports have been re-written utilizing the Business Intelligence Publisher (BIP) tool. BIP based reports offer greater flexibility to end users in changing report layouts and formats:
• Withholding Tax by Invoice Report
• Bills Payable Maturity Date Report
• Discounts Available Report
• Payment Audit by Voucher Number
• Prepayments Status Report
Third Party Payments

Suppliers can specify a related trading partner to be paid on their behalf. The payments made on behalf of suppliers to other trading partners are termed as third party payments.
Oracle Payables has been enhanced to record third party relationships and to process third party payments. Withholding and 1099 processing continue to occur for invoicing suppliers.
Supplier Dispute Processing

Supplier invoices may be short paid to expedite dispute settlements. The Payables Invoice Workbench has been enhanced to capture the invoice amount originally claimed by the supplier and the reason for short payment.
Discount Calculation Enhancements

Suppliers offer discounts for early payment. Early payment discounts can be fixed monetary amounts or calculated on a percentage basis.
In prior releases, discounts could be defined in percentage terms only. Oracle Payables now allows discounts to be specified in monetary amounts. When a percentage as well as an amount is available, the higher or lower of the two can be specified for application.
Oracle Receivable Standard Features Differences between 11i and R12
Standard Features
Revenue Recognition
Only Rule based Revenue Recognition exists in 11i.
In R12 revenue recognition is based on Rules and Events, and they are:
Time-Based Revenue Recognition
o Ratably Over Time
o Upon Expiration of Contingencies
• Event-Based Revenue Recognition
o Payment
o Customer Acceptance
Rule-Based Revenue Recognition
o Payment Term Thresholds
o Refund Policy Thresholds
o Customer Credit worthiness
Daily Revenue Recognition
o Revenue distribution over full as well as partial accounting periods.
o Fulfills stringent accounting standards
o Accuracy to the number of days in the accounting period.
• Enhanced Revenue Contingencies
o Fully Supports US GAAP and IAS
o User definable contingencies
o User definable defaulting rules for contingencies assignment
o Supports parent-child (e.g. Product and Service) relationship
o Integration with Order Management and Service Contracts
o User Interface as well as Programming Interface (API) support
o Access control through seeded Revenue Managers Responsibility
Deferred Revenue Management
In Release 12, revenue contingencies for customer acceptance that are applied to goods sold in Order Management are now applied to services sold to cover those goods. Revenue is deferred for service ordered in both Order Management and Service Contracts. Acceptance contingencies associated with an item instance are automatically applied to service revenue associated with the item instance when it is covered in a Service Contract as a Covered Product.
Global Architecture
Limited integration of E-Business Tax module with Oracle Receivables.
• EBusiness Tax - Oracle E-Business Tax is a new product that uniformly delivers tax services to all Oracle EBusiness Suite business flows. In Release 12, Receivables is enhanced to support
integration with the E-Business Tax product.
• Intercompany - This is enhanced by automatic balancing
Enhanced Customer Screen
We have seen 11i Customer standard forms makes easier by simple navigation. This times there is clearer separation of the party and account layers, which makes a consist ant look and feel. More over full backward compatibility with 11i UI Bill Presentment Architecture has been provided.
The AR Create Customer page in R12 has eliminated the navigation to separate windows. Now, users can specify the following on a single page:
• Customer Information
• Account Details
• Address
• Account Site Details
• Business Purpose
Limited integration with Oracle Payables.
Oracle Receivables is fully integrated with Oracle Payables to deliver a seamless, automated process to generate check and bank account transfer refunds for eligible receipts and credit memos.
Late Charges
Does not exist.
With new changes these are the enhanced functionality:
• Expanded assessment and calculation capabilities
• Tiered charge schedules
• Penalty charge calculation
• Integration with Balance Forward Billing
• Centralized setup and maintenance of late charge policies
• Calculation performed independent of Dunning and Statement processing.
AP AR Netting
Contra Charges functions available in the 11i.
R12 Netting solution replaces 3 solutions(FV,JE,IGI) in 11i.

In R12 the Contra Charge functionality has been optimized and therefore changed into the AP/AR Netting functionality. In the Payables module as well as the Receivables module, there is a Netting submenu.

    Payables: Payments -> Entry -> Netting
    Receivables: Receipts -> Netting
Oracle Asset Standard Features Differences between 11i and R12
Standard Features
Fixed Assets tied with SLA(Sub Ledger accounting)
Limited integration.

• Oracle Assets is fully integrated with SLA, which is a common accounting platform for Sub Ledgers.
• Customers can use the seeded Account Derivation definitions or modify them as required.
• Continue to support Account Generator functionality for existing Asset Books.
New SLA Accounting report and online account inquiry.

What you will notice create Journal Entries (FAPOST) process feeding into the GL_INTERFACE table is no more exist
This is replaced with the Create Accounting รข€“ Assets process (FAACCPB).
Enhancements In FA_MASS_ADDITIONS Table.
Does Not exist.
As a result of new enhanced feature, we can populate the values for the new attributes directly in the FA Mass Additions interface table rather than accepting default values from the asset category. Legacy conversion can be completely automated.
Following are the new adds-on:
• Asset Life
• Depreciation Method
• Prorate Convention
• Bonus Rule Ceiling Name
• Depreciation Limit
New Automatic Preparation of Mass Additions
Does not exist.
• This new feature consists of default rules and Public APIs that can be used by customers to complete the preparation of mass addition lines automatically.
o Auto populate required fields such as Expense Account, Asset Category etc.
o Avoid manual intervention during the Mass Additions prepare process
o Avoid customization and use public APIs to effect custom business logic.
• Assets now uses Flexible Reporting using XML publisher
o Major Asset Transaction reports have been modified to support XML publisher.
o Users can modify or use new templates to view report output
Flexible Reporting into XML Publisher
Does not exist.
These asset reports have been converted in XML Publisher based reports:
• Create Accounting Assets
• Transfer Journal Entries to GL Assets
• Journal Entry Reserve ledger Report
• Asset Additions Report
• Asset Transfer Report
• Asset Retirement Report
• Transaction History Report
• Asset Reclassification Report
• Mass Additions Create Report
• Mass Additions Posting Report
• Cost Adjustment Report
• Cost Detail report
• Cost Summary Report
• Reserve summary Report
• Reserve Details Report
• Mass Revaluation Preview Report
• Revaluation Reserve Details Report
• Revaluation Reserve Summary Report
• CIP Capitalization report
• CIP Detail Report
• CIP Summary Report
Automatic Depreciation Rollback
Since release 11i, users have been able to run depreciation for an asset book without closing the period. If additional adjustments are required in the current period, then the user submits a process to roll back depreciation for the entire book, performs the necessary adjustment(s) and then resubmits the depreciation program.
Depreciation is rolled back automatically by the system when any transaction is performed on an asset if the following conditions are met:
• Depreciation has been processed in that period
• The period is not closed
In Release 12 the intermediate manual step of rolling back depreciation for the entire book in order to process further adjustments on selected assets is no longer necessary
Cash Management Standard Features Differences between 11i and R12
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