R12 Feature Analysis 4.0

Page 1
Document Title
Version Control Version No. Version Date Changes Owner / Author Review / Expiry Date
Notice: The information contained in this document is not to be used for any purpose other than the purposes for which this document is furnished by Genpact, nor is this document (in whole or in part) to be reproduced or furnished to third parties or made public without the prior express written permission of Genpact.
Classification:Genpact Internal
Module Common
Feature Multi-Org Access Control
Subledger Accounting
Subledger Accounting (New Module)
General Ledger
Simultaneous Accounting for Multiple Reporting Requirements
General Ledger
Centralized Accounting Setup
General Ledger
Enhanced Reporting Currency Functionality
General Ledger
Simultaneous Data Access to Multiple Legal Entities and Ledgers
General Ledger
Simultaneous Opening and Closing of Periods for Multiple Ledgers Cross-Ledger and Foreign Currency Allocations
General Ledger
General Ledger
Simultaneous Currency Translation of Multiple Ledgers Financial Reporting Across Ledgers
General Ledger
General Ledger
Streamline Automatic Posting ; Auto Reversal Criteria Setup; Consolidation Mappings
General Ledger
Replacement for Disabled Accounts GL Standard Reports Integration With XML Publisher
General Ledger
General Ledger
Data Security across Legal Entities and Ledgers Management Reporting and Security
General Ledger
General Ledger
General Ledger
Prevent Reversal of Journals with Frozen Sources, Reversal of Unposted Journals Accounting and Reporting Sequencing
General Ledger
Foreign Currency Recurring Journals Journal Line Reconciliation
General Ledger
General Ledger
Account Analysis and Drilldown
General Ledger
Enhanced Intercompany Functionality (AGIS)
Payables
Supplier related enhancements
Payables
Enhanced Invoice Work bench
Payables
Enhanced Asset Tracking Enhancements to Payment Banks, Branches, and Accounts
Payables
Payables
Payment Process Enhancements
Payables
Accounts Receivable / Accounts Payable Netting
Payments
Central Payment Engine (New Module)
Receivables
Revenue Management Enhancements
Receivables
Line Level Cash Applications
Receivables
Refunds Enhancements
Receivables
Credit Card Error Handling during payment authorization & capture
Receivables
Deduction Management
Receivables
Balance Forward Billing
Receivables
Enhanced Late Charges functionality
Receivables
Receivables Reconciliation Enhancements
Receivables
Obsolete Collections work bench
Receivables
Bill Presentment Architecture
Cash Management
Bank Account Model
Cash Management
Bank Account Balances & Interest Calculation
Cash Management
Bank Account Transfers
Cash Management
Bank Statement Reconciliation
Cash Management
Cash pooling
Advanced Collections
Simplified Setups
Advanced Collections Advanced Collections
Collections Workbench Multi-Org Access Control Credit Management Integration
Dunning Letter
Limitation in 11i 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. For example, 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. This was control via MO: Operating Unit. It gives user or responsibility to access only one OU.
In 11i, accounting information and the tie back to the underlying transaction is maintained differently for each module. Different sub ledgers/modules have their own model as to how and what they capture in terms of accounting data. Some allow capturing more details and some link between the journals and the underlying transactions. Some do not have the same flexibility or detail. This causes difficulty and inconsistency in reporting for auditing, reconciliation or whichever purpose across modules. 1) Separate process to post in primary, MRC and secondary GLs 2) MRC only for primary ledgers . 3) Different account derivation rules across modules 4) Accounting rules defined for each operating unit 5) No track of change in application accounting rules 6)Cannot verify correctness of account derived prior to posting to GL 7) Require technical / DBA support for SQLs / Workflow account generator
In 11i, a set of books is defined by three components - chart of accounts, functional currency, and accounting calendar. To add a Accounting Method directly to the set of books was not available. Hence, it resulted in more setups to get different accounting methods for multiple countries. The default accounting method was "Standard Accrual". For reporting ledger requirements, in 11i, Multiple Reporting Currencies (MRC) were used to maintain sub ledger transactions and General Ledger journals in a different reporting currency. Moreover, it has lots of different setups to configure reporting ledgers. In 11i, there is no central location called as "Accounting Setup Manager". The Set of Books creation and accounting-related setup were done in GL module. Legal entities were created as Organization from HRMS or Inventory module. Then, setup of books were linked to LE from HRMS or Inventory modules. This resulted in more complex setup and dependency on other modules.
Only Journals were being converted from Primary to Reporting currencies - In 11i, Multiple Reporting Currencies (MRC) were used to maintain sub ledger transactions and General Ledger journals in a different reporting currency. However, users were required to do complete new setups for Reporting ledgers. 11i lacked in below currency representations at different levels: 1.) Balance Level - Maintains translated balances 2.) Journal Level - Balance Journal level is a currency representation of only General Ledger journals and balances 3.) Sub ledgers Level - Sub ledger level is a complete currency representation of sub ledger transactions, General Ledger journals entries and balances. In 11i user had to have one responsibility per set of books and could not restrict read or write access. There were two main configurations of legal entities: 1.) The single legal entity - single set of books model which had excelled in data security, 2.) The multiple legal entity - single set of books model excelled in information sharing and processing efficiency. Major drawback of above model is that both worked in mutually exclusive environment. Hence, it did not provide both benefits to both the model at the same time. In 11i, user cannot group the Set of Books which share same Charts of Accounts and Calendar/Period type combination. Hence, user was not able to Open or Close periods for multiple Set of Books simultaneously. User had to Open or Close periods separately for each Set of Books. This functionality is provided by "Ledger Sets" in R12. In 11i, users cannot access multiple ledgers via single responsibility. They can only access ledger/Set of Books which is assigned to GL: Set of Books profile option. In R12, Cross-Ledger and Foreign Currency Allocations is possible because a single responsibility can now access data for multiple ledgers. This is possible via Ledger Sets/Data Access Sets functionalities. Group of ledger is assigned to responsibility via GL: Data Access Set. In 11i, user cannot create a single allocation definition that can be executed for multiple ledgers. User had to create a different allocations for each ledger individually.
In 11i, user cannot group the Set of Books which share same Charts of Accounts and Calendar/Period type combination. Because of above limitation, user cannot run Translation Program for multiple Set of Books simultaneously. This functionality is provided by "Ledger Sets" in R12. Grouping of ledgers is required to run FSG for multiple ledgers simultaneously. However, in 11i, user cannot group the Ledgers which share same Charts of Accounts and Calendar/Period type combination. In 11i, user cannot instantly summarize data across multiple ledgers in a single FSG report. This results in poor control and visibility into global operations because user cannot easily spot check the performance of all entities by running one report. This functionality is provided by "Ledger Sets" in R12.
In 11i, user has to define a different Auto Post or Auto Reversal Criteria Set for each Set of Books. User cannot reuse or share one Auto post Criteria and Auto Reversal Criteria across other Set of Books In 11i, Consolidation Mapping feature was available. Consolidation is limited to only Source and Target SOBs. It allowed mapping of Set of Books and not mapping of Charts of Accounts. This resulted in major drawback as it cannot be shared across multiple Set of Books In 11i, this feature is not available. Due to this, user has to manually correct journal or imported journal errors caused by disabled accounts. This results in decrease in processing efficiency. This feature is available in 11i. However, user has to separately implement XML publisher to get GL standard reports via XML publisher. With R12, XML publisher is default for reports.
In 11i, data cannot be secured by legal entity or balancing segments values. In 11i, with the help of "Security Rules" and "Cross Validation Rules", data can be secured for Accounting segments and Responsibilities respectively. In 11i, this feature is not available.Due to this, it gives major drawback to give read only or read and write access to specific management segment values to prevent certain managers from viewing and updating data. In 11i, this feature is not available.
In 11i, document sequencing sequentially numbered documents upon creation. Due to this, it sometimes becomes tough to meet legal requirements for audit purposes in various countries. In 11i, user can only define recurring journals using the functional currency or STAT currency. User was unable to create Recurring journals to create foreign currency journals. In 11i, this feature is available by name of General Ledger Entry Reconciliation feature.Though Reconciliation flag is available at the segment qualifier level, the functionality is not available.
In 11i, Drilldown feature is available. However, it is not in single page. Line drilldown is limited only to view the transaction.
In 11i, Global Intercompany System and Intercompany Balancing features were available. Using the GIS, the data is sent only to the respective SOBs and no back-feed to the Subledgers (like AP or AR).
1. Suppliers defined in AP Supplier contacts replicated for each supplier site. No TCA Architecture
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
In 11i Asset Tracking is limited with one single check box to Track Asset. No option of providing Book Name and Category 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
Payment process is limited to only one OU
Manually driven process with a work-around to off-set the AP/AR balances.
No such feature in 11i
Revenue cannot be recognized for a partial period (with prorated amount).When Revenue is deferred or split up for different accounting periods and thus partially recognized for a particular period, user wants only the proportionate amount of COGS to be recognized for that period. In R11i, Oracle Costing records COGS when an inventory item is shipped. This recognition is independent of what happens to revenue in Receivables. Revenue were booked even though the COGS was not booked .e.g long term project billing. This caused issues with revenue matching. Recognition of revenue and COGS should occur in the same accounting period. If revenue is deferred, the equivalent percentage of COGS should also be deferred. In R11i, there is no functionality to allow COGS to defer. There is also no communication between Receivables and Costing to indicate when and how much revenue is being recognized. Similarly, there is no communication to indicate when revenue is deferred, so that COGS could also be deferred. User wants to recognize revenue only upon customer acceptance User wants to recognize revenue 10 days after Shipping Date User wants to recognize revenue (in case collection is doubtful for any customer) only when payment is received.
Receipts can be applied at invoice level and not at line level. If any existing lines, which are tax exempt are returned and remaining lines are paid by customer, the application leaves both line and tax amount opening . User wants to apply the Receipt amount to the Line amount of the transaction only or to the tax amount of the transaction only or to the freight amount of the transaction only. In 11i, there was no seamless integration of creating refunds for the customer. Infact, it was a workaround which involved lot many steps in order to generate refund and correct accounting entries.
Any refunds to customer needs to be handled through entering debit memo and entering a AP invoice & make payment. This process is very cumbersome For specific error codes received from third party credit card processor or financial institution, user wants an automated action viz. Change instrument or clear payment information or retry or reverse receipt. In 11i, there is a functionality for the vendor to issue a Credit Card chargeback directly to the customer. However, 11i does not support the vendor to also be able to register and process a chargeback that a card issuer has already issued to the customer. In 11i, the functionality of credit card errors during payment does not exist. Hence any exceptions needs to be handled manually 1. While applying receipt, User wants to view a list of open receipts to net the receipt. 2. User wants to record Underpayments/ deductions or Overpayments in the receipt application form.(Such application of receipt to Claim investigation should be shared with Trade Management where the investigation will be taken up) . 3. In 'Search & Apply' tab claim was not available to search and apply. 4. Also receipt cannot be applied against another receipt which open claim investigation application
1. The consolidated invoices can be printed on monthly basis only. When the defined AR Period is a calender month, User wants to generate daily / weekly etc billing cycles. User wants to bill on specific day of a week.Eg; Every Monday. 2. In the scenarios of customers frequent orders & billing, managing numerous invoices become very cumbersome. 3. User wants flexibility regarding Account level billing or site level billing or Account level billing excluding a particular site or excluding a particular invoice. More so, if the customer follows the centralized payment policy i.e. for different Ship-To locations payment from one/few Bill-To locations.....In 11i, user had to choose between consolidating all invoices for a customer into one monthly bill, or printing all invoices separately. Plus, if customer needed different billing formats that meant customizing print layouts. In 11i Consolidated Billing, the payment term assigned to the transaction was ignored if consolidated billing was enabled. This meant that the due date on an individual invoice may be different then on the consolidated bill if the payment term assigned to the invoice was different than the default payment term assigned to the customer. Aging is based on due date of the individual invoice, while payment due date was based on the payment term assigned to the customer. This caused aging to be out of sync with bills due date. User wants to assign a flexible late charges policy to an Account or Site. In 11i, Late charges func was not directly available as R12. Series of setups were required which were hard to manage.
Finance charges does not have flexibility like exclusion of any specific set of transactions, charges only if balance exceed threshold limit, etc. User wants to match transactional data to accounting data.
User wants additional features to Collections Workbench such as scoring, collections strategies, enhanced payment and promise processing, automated promise tracking, and automated collector work assignment. In 11i, Collections Workbench was present in Receivables. Moreover, Advanced Collections was more used to do follow up with customers to generate receivables.
Users want BPA to support online and printed presentment of consolidated bills. Users want to include legal entity specific attributes on BPA template. The invoices can be generated based on details on AR transactions and does not drill down to other applications for more details In 11i, Oracle Accounts Payable owned banks, bank branches and bank accounts. Such bank accounts could also be used by Accounts Receivable. Payroll and Treasury, however, had their own bank account models. In 11i, Bank Account Model was not centralized. In 11i, Bank Accounts cannot be granted to multiple operating units. This increased the redundant duplicate bank account setup under different operating units in case these operating units share the same bank account. Moreover, it resulted in complex the reconciliation process if money than one bank account is the system corresponds to one bank account at the bank.
In 11i, bank account balances were only available as a part of the bank account statement. The bank account interest calculation was only available for bank accounts set up in Treasury.
In 11i, Bank account transfers could not be created in Treasury module.
In 11i, simultaneously bank statement reconciliation across operating units is not available. User has to do individually for respective OU for which responsibility is assigned. In 11i, Reconciliation tolerance level were at system level and not at Bank account level. This resulted in one set of tolerance level for all the bank accounts across OUs. So, no flexibility was available. In 11i, tolerances were same for manual and auto reconciliation. Donot have robust functionality
In 11i, there were more complex setups to do setup. Moreover, it involved lot many modules to complete the setup.
In 11i, Collections Workbench was part of AR responsibility. In 11i, Collections Agent can only view data for customer in that Operation Unit only. He cannot view data across operating Units. In 11i, much of the details are not available.
In 11i, it requires extra implementation of XML publisher to get more accurate dunning letters.
Enhanced / new features in Release 12 Allows users access to multiple operating units from a single responsibility. Allows users to limit the number of operating units based on their work environment. Allows reports to be run across multiple operating units The MO Security Profile controls the list of operating units that a responsibility or user can access. If you set the security profile at the responsibility level, then all users using that responsibility will have access to only the operating units available in the security profile. If you set the security profile at the user level, then the user will have access to only those operating units, irrespective of application responsibility that they log into.
Complexity Medium
Type of Change New Feature
Its an engine which drives the Accounting process for all the High subledger modules.A single transaction can be represented in multiple accounting methods. The Accounting entries can be customized easily with the help of rules and definitions to meet any kind of reporting. Draft accounting is possible. 1) Single process to post in primary, reporting (MRC in 11i) and secondary GLs 2) Reporting currencies can be assigned to primary and secondary ledgers 3) Uniform account derivation rules across modules 4) Accounting rules defined for the Chart of Accounts / GL 5) Date tracked application accounting definitions 6) Draft accounting to verify correctness of account derived 7) DBA support not required for change in account derivation rules
New Feature
Performing accounting in accordance with accounting principles and High standards of multiple countries and in different currencies, charts of accounts, and/or calendars. The reporting requirements can also be statutory in nature, and one subsidiary may even need to satisfy multiple sets of statutory requirements
New Feature
The Accounting Setup Manager is a central location to define accounting-related setup across all financial applications. Define legal entities and their accounting context, which includes the ledgers that contain the accounting data for each legal entity
Medium
New Feature
Multiple Reporting Currencies functionality is enhanced to support all journal sources. Every journal that is posted in the primary currency of a ledger can be automatically converted into one or more reporting currencies
Medium
Enhancement
Access multiple legal entities and ledgers using a single responsibility. This improves processing efficiency by reducing the need to switch between responsibilities when trying to access data for different ledgers or legal entities.
Medium
New Feature
The Open and Close Periods Programs has multiple Medium enhancements. Can open or close periods for multiple ledgers simultaneously. Keep the status of periods across multiple ledgers in synch with new programs that ensure a specific period is Open or Closed for all of the ledgers you manage. Allocate financial data from one or more ledgers to a different target Medium ledger.This is possible even if the target ledger is in a different currency than the source ledgers). We can create allocations in foreign currencies. Foreign currency allocations are also useful within a single ledger for allocating amounts to a currency that is different from the primary currency of a ledger.
Enhancement
Enhancement
We can run the Translation program for multiple ledgers simultaneously.
Low
Enhancement
We can run Financial Statement Generator (FSG) reports for Low multiple ledgers simultaneously. This is useful for reports such as consolidating financial statements that display data for each subsidiary in separate columns as well as aggregated data in a total column
Enhancement
1. Auto Post Criteria can be shared across ledgers that have the Medium same chart of accounts and calendar. This dramatically reduces the number of Auto Post Criteria sets we define. 2. Auto Reversal Criteria can be shared across ledgers. This reduces the number of Auto Reversal Criteria sets we define. 3. Define Chart of Accounts Mappings (formerly known as Consolidation Mappings) between two charts of accounts. This significantly reduces the number of mappings we define if Consolidation Definitions involve the same pair of charts of accounts and the mapping rules are the same. We can prevent transactions that include the account from erroring Low during journal import by defining a replacement account for the disabled account General Ledgers Account Analysis, General Journals and Trial Medium Balance standard reports are now integrated with XML Publisher. Leverage the formatting features of a word processing application to design the layout of report. Personalize report by changing fonts, adding images, inserting headers and footers, creating borders, changing column widths, and reordering/adding/deleting columns. We can create professional-quality reports directly from the general ledger, which ensures the integrity and auditability of the information. Secure data by legal entity, ledger, or even balancing segment Medium values or management segment values. We can 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. Designate any segment (except the natural account segment) of Medium chart of accounts to be management segment and use General Ledgers security model to secure the management segment for reporting and entry of management adjustments Journals with frozen journal sources are prevented from being reversed to streamline the reconciliation of data from Subledger Accounting sources. Users are no longer allowed to reverse Unposted journals. Low
New Feature
New Feature
Enhancement
New Feature
New Feature
Enhancement
Assign sequence numbers to journals during the posting process to Low ensure that finalized journal entries are properly sequenced. We can also assign a sequence number to journals when a period is closed to sequence journals for reporting purposes. Recurring Journals to create foreign currency journals. Low
Enhancement
Enhancement
Reconcile journal lines that should net to zero. This is often done to Low reconcile suspense accounts or to verify the open balances of specific accounts at the end of the period.
Enhancement
view the balances of multiple detail or summary accounts in a single Low page and drill down to supporting journal entries and sub ledger transactions all within a browser window control the display of data by choosing from various layouts, specifying sort criteria, or defining filters to only retrieve balances that meet specific conditions 1. Intercompany Balancing - the Balancing Process automatically High generates the correct intracompany or intercompany accounting entries, depending on whether the balancing segments are in the same legal entity or in different legal entities. 2. Intercompany Invoicing - New in this release is the automatic creation of payables and receivables invoices for intercompany transactions. Where local statutory compliance requires an Intercompany-Organization to produce physical invoices for intercompany transactions. Oracle AGIS then synchronizes the automatic creation of payables and receivable invoices for the initiator and recipient organizations whenever an intercompany transaction is processed. 3. Intercompany Reconciliation - Users can perform reconciliation between Legal Entity Relationships belonging to the same or different ledgers. The users are able to run the reconciliation process any time for open or closed periods, and can choose how much detail they want to work with. Supplier becomes TCA Party. Supplier Site is a TCA Party Site. Medium Single supplier address and contact can be leveraged by multiple sites, for each OU 2. Other enhancements- Data Librarian Function & Processes, Integrated Enrichment Capabilities including D&B, Address Validation, Data Consistency, and Ease of Data Maintenance. Incorporates Invoice Lines into the invoice model. Now the invoice Medium is having three levels, viz, header, lines and distributions. 2. Invoice Lines supports the representation of the goods or services as well as tax, freight, and other charges as lines with distributions tied to each line. Additional fields record attributes such as serial numbers and item descriptions. 3. It facilitates the capture and transfer of additional, pertinent information to and from Projects and Assets. 4. With the introduction of Invoice Lines, users are able to further extend their approval policy granularity in Approvals Management for individual lines of an invoice. The newly introduced invoice lines and the distribution is having fields to capture some asset details like Book name, category, etc. Low
New Feature
New Feature
Enhancement
Enhancement
Navigation
Banks and Bank Branches are represented in s Trading Community Medium Architecture and shared by other E-Business Suite applications. The Bank Account is centrally defined, managed and secured and includes the legal ownership and operating unit access for each bank account.
Navigation
1. Manage fewer pay runs by choosing selection criteria with multiple currencies, operating units, and pay groups. 2. Save pay run invoice selection criteria and processing requirements in a template to be reused and/or scheduled. 3. A Payment Dashboard is introduced which empowers your payment manager with the ability to monitor all current pay run processing and payment processes that require attention. 1. The new AP/AR Netting feature will find out the outstanding receivables and payables and automatically create corresponding supporting documents in both AP and AR. 2. With the help of Netting Agreement, we can link any supplier to any customer, which means that it is not necessary to have the customer's and supplier's name as same. 3.Discounts, late fees, and withholding taxes are considered prior to determining the final netting amount. 4. A review process and trading partner approval caters to further verification to support the netting event. Highly configurable and robust engine to disburse and receive payments. Processes invoice payments from Payables, bank account transfers from Cash Management, and settlements against credit cards and bank accounts from Receivables. 3. The product supports features designed specifically for its two payment process activities, viz, funds disbursement and funds capture. 4. iPayments is being replaced by payments with some additional features. 1. Partial Period Revenue Recognition 2. Revenue Deferral Reasons 3. COGS and Revenue Matching 4. Enhanced Payment-Based Revenue Recognition
Medium
Enhancement
Medium
New Feature
High
New Feature
Medium
Enhancement
The Line Level Cash Applications solution allows the application of receipts to specific transaction items such as individual lines, groups of lines, or tax or freight buckets. From the receipt workbench, We can choose whether to allocate cash to the entire transaction or to apply amounts against specific items according to the customer remittance.
Low
Navigation
Receivables is fully integrated with Payables to deliver a seamless, Medium automated process to generate check and bank account transfer refunds for eligible receipts and credit memos. To maintain strict security over refunds, users may choose to leverage the approval workflow process available in Payables.
Enhancement
For a merchant, who wants to secure timely payment, it is vital to respond promptly to credit card errors. The new Credit Card Error Handling feature in Receivables provides a quick and efficient method to handle credit card errors that occur during payment authorization and capture.
Medium
New Feature
1. The ability to choose whether we want to view open receipts by default in the receipt applications apply to list of values and the search &apply window or choose to keep them hidden. 2. Additional Claim information will be available in the Receipt Applications and Search and Apply application windows, giving Receivables Clerks key information to perform receipt-to-receipt applications of open claims.
Low
Navigation
1. Balance Forward Billing is an enhanced version of the existing Medium consolidated billing functionality for industries where customers are billed for all their account activity on a regular, cyclical basis. 2. Balance Forward Billing provides the ability to setup cycle-based billing at the account or account site levels, enable event based billing, and leverage user configurable billing formats provided by Bill Presentment Architecture.
Enhancement
Receivables delivers enhanced Late Charges functionality enabling Medium the creation of standard late charge policies that can be assigned to customer accounts or account sites. Flexible policy configurations include multiple interest calculation formulas, transaction and account balance thresholds, and currency-level rate setups. Additionally, charges may be modeled as different document types such as adjustments, debit memos, or interest invoices depending on the business need.
Enhancement
Quickly match transactional data to your accounting data. Highlight the possibility of incorrect set up with newly added exception reporting that suggests potential reconciling items. Reconcile Receivables to the General Ledger using one flexible report that automatically compares account activity by GL account. Audit balance sheet accounts in Receivables with a cumulative balance report that lists details making up the account balance.
Low
Enhancement
The Collections Workbench module in Receivables is obsolete in NA this release. Like functionality is provided by Advanced Collections, including customer collections interactions and correspondences, transaction processing, and dunning activities as well as additional features.
NA
1. Bill Presentment Architecture (BPA) allows you to retrieve billing High data from multiple data sources for presentment on a bill. 2. BPA supports the presentment of a balance forward bill. 3. BPA supports the use of source product specific attributes as assignment criteria in template assignment rules. 4. BPA allows printing of PDF attachments with the printed bill. Bank Account is owned by Legal Entity. One Bank Account Medium definition can be assigned to many Legal Entities and its Operating Units. Different Roles and Responsibilities can created and assigned to users for restricting the creation / modification of bank accounts. New Bank account type 'Netting' is being introduced to support AP/AR netting.
Enhancement
Enhancement
Many new bank account balance types are supported for all internal Medium bank accounts including ledger, available, value dated, 1-day float, 2-day float, and projected balances. Can create and calculate interest based on the interest schedules. Centrally stored balance history is available for trend analysis, etc. Bank account transfers are supported directly in Low Cash Management. This feature allows users to create these types of cash transfers between internal bank accounts manually or automatically through physical cash pools. 1. Mapping rules are available with enables user to automatically Low create and reconcile the transactions like bank fees, interest, etc. 2. Users are able to define flexible matching rules based on bank accounts, transaction codes, and text search strings
New Feature
New Feature
Enhancement
Cash Management supports common cash pooling techniques by allowing users to group bank accounts into different types of pooling structures and by managing the associated activity for either centralized or decentralized business environments. In R12, Setup for collections is very simplified. It is in Questions and Answers Type Setup. Moreover, Configuration shows "Checklist" to make setup. So, users knows which setup is done and which left. In R12, Collections Workbench is replaced totally. Its functionalities are incorporated in Advanced Collections module. In R12, Collections Agent has ability to view data for a customer across operating Units. It is controlled by MO:Security Profile. R12, offers seamless integration with Oracle Credit Management module. It displays all details related to Credit Management in Profile tab of Advanced Collections
Medium
Enhancement
High
New Feature
Medium High
Enhancement New Feature
High
New Feature
In R12, Oracle Advanced Collections has more robust and automated dunning process that takes advantage of the XML reporting capabilities.
High
New Feature
Target audience for training Super User
Super User
Super User
Super User
Super User
Super User
RTS User
Super User
End User
End User
Super User
End User
RTS User
Super User
Super User
End User
End User
End User
End User
End User
Super User
End User
End User
End User
End User
End User
End User
Super User
End User
End User
End User
RTS User
End User
End User
End User
End User
NA
Super User
End User
Super User
End User
End User
Super User
RTS User
RTS User RTS User
RTS User
RTS User
Complexity
High
Medium
Low
NA
Type of Change
Target audience for training
Navigation
Super User
New Feature
End User
Enhancement
RTS User
NA
Consultants
NA
Assets
Legacy Conversions with enhanced Mass Additions
Assets
Automatic preparation of Mass Additions
Assets
Automatic Depreciation Roll back
Assets
Enhanced Logging for Asset transactions and Programs
Additional attributes are available in the Mass Additions Low interface to ease legacy data conversions. Attributes such as asset life, depreciation method, prorate convention; bonus rule ceiling name, depreciation limit, and others can now be directly imported from legacy system instead of being derived from asset category setups. A set of extensible public APIs is available to Low automatically prepare a mass addition line for all required attributes such as depreciation expense account, asset category, location etc. with the goal of minimizing manual intervention by the user in the mass additions workbench. The intermediate manual step of rolling back depreciation Low for the entire book in order to process further adjustments on selected assets is no longer necessary. Assets automatically rolls back the depreciation on just the selected assets (instead of the whole book) and allows the transactions to be processed normally. The assets for which depreciation was rolled back is automatically picked up during the next depreciation run or at the time that the depreciation period is finally closed. Through the common logging architecture, Assets Low ensures a common repository for all log messages within and outside the product. This reduces resource usage on the file system for excessively large log files.
Enhance ment
RTS User
Enhance ment
RTS User
Enhance ment
End User
Enhance ment
RTS User
Genpact Software - OLM Community > Documents > Training Material from Leasing Practice > Oracle Financials - Orac
ng Practice > Oracle Financials - Oracle training material

R12 Feature Analysis 4.0

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

R12 Feature Analysis 4.0

Uploaded by

Copyright:

Available Formats

Page 1

Feature Multi-Org Access Control

Subledger Accounting (New Module)

Simultaneous Accounting for Multiple Reporting Requirements

Centralized Accounting Setup

Enhanced Reporting Currency Functionality

Simultaneous Data Access to Multiple Legal Entities and Ledgers

Simultaneous Currency Translation of Multiple Ledgers Financial Reporting Across Ledgers

Streamline Automatic Posting ; Auto Reversal Criteria Setup; Consolidation Mappings

Foreign Currency Recurring Journals Journal Line Reconciliation

Account Analysis and Drilldown

Enhanced Intercompany Functionality (AGIS)

Supplier related enhancements

Enhanced Invoice Work bench

Enhanced Asset Tracking Enhancements to Payment Banks, Branches, and Accounts

Payment Process Enhancements

Accounts Receivable / Accounts Payable Netting

Central Payment Engine (New Module)

Revenue Management Enhancements

Line Level Cash Applications

Credit Card Error Handling during payment authorization & capture

Balance Forward Billing

Enhanced Late Charges functionality

Receivables Reconciliation Enhancements

Obsolete Collections work bench

Bill Presentment Architecture

Bank Account Model

Bank Account Balances & Interest Calculation

Bank Account Transfers

Bank Statement Reconciliation

Advanced Collections Advanced Collections

Collections Workbench Multi-Org Access Control Credit Management Integration

Payment process is limited to only one OU

Manually driven process with a work-around to off-set the AP/AR balances.

No such feature in 11i

In 11i, Bank account transfers could not be created in Treasury module.

Type of Change New Feature

We can run the Translation program for multiple ledgers simultaneously.

Enhancement New Feature

Target audience for training Super User

RTS User RTS User

Target audience for training

Legacy Conversions with enhanced Mass Additions

Automatic preparation of Mass Additions

Automatic Depreciation Roll back

Enhanced Logging for Asset transactions and Programs

ng Practice > Oracle Financials - Oracle training material

You might also like