what are the major difference between oracle 11i and R12 ?

o
o
o
o
o
o

o
o
o
o
o
o
o
o

Que: what are the major difference between oracle 11i and R12 ?
Ans :
11i only forms basis application but R12 is now forms and HTML pages.
11i is particularly in responsibility and operating unit basis but R12 is multi operating unit basis.
11i is particularly in set of books using and R12 using in ledgers.
11i in MRC Reporting level set of books called reporting set of books but in R12 reporting ledgers called as reporting
currency. Banks are using at single operating unit level in 11i and ledgers level using in R12.
Differences between R12 & 11i.5.10 New R12 Upgrade to R12 Pros and Cons Pros:
Sub-ledger Accounting The new Oracle Sub-ledger Accounting (SLA) architecture allows users to customize the standard
Oracle accounting entries. As a result of Cost Management's uptake of this new architecture, users can customize their
accounting for Receiving, Inventory and Manufacturing transactions.
Enhanced Reporting Currency (MRC) Functionality Multiple Reporting Currencies functionality is enhanced to support all
journal sources. Reporting sets of books in R12 are now simply reporting currencies. Every journal that is posted in the
primary currency of a ledger can be automatically converted into one or more reporting currencies.
Deferred COGS and Revenue Matching R12 provides the ability to automatically maintain the same recognition rules for
COGS and revenue for each sales order line for each period. Deferred COGS and Deferred Revenue are thus kept in synch.
Cons:
Resources Availability of knowledgeable resources
Maturity Though R12 is around since 2007, not all the modules are mature enough meaning modules like E-B Tax have
many bugs being fixed by Oracle development.
Integration with customized applications In a customized environment, all the extensions & interfaces need to be analyzed
because of the architectural changes in R12
R12 Features and differences with 11.5.10 Inventory / Cost Management
Multi-Organization Access Control (MOAC) - Multi-Org Access Control enables uses to access multiple operating units data
from single responsibility. Users can access reports , Concurrent programs , all setup screens of multiple operating units
from single responsibility without switching responsibilities.
Unified Inventory - R12 merges Oracle Process Manufacturing OPM Inventory and Oracle Inventory applications into a
single version . So OPM users can leverage the functionalities such as consigned & VMI and center led procurement which
were available only to discrete inventory in 11i.5.10.
Inventory valuation Reports -There are a significant number of reports which have been enhanced in the area of Inventory
Value Reporting
Inventory Genealogy - Enhanced genealogy tracking with simplified, complete access at the component level to critical lot
and serial information for material throughout production.
Fixed Component Usage Materials Enhancement Enhanced BOM setup screen and WIP Material Requirement screen
that support materials having a fixed usage irrespective of the job size for WIP Jobs, OSFM lot-based jobs, or Flow
Manufacturing
Component Yield Enhancements - New functionality that provides flexibility to control the value of component yield factors at
WIP job level. This feature allows the user to include or exclude yield factor while calculating back flush transactions.
Periodic Average Cost Absorption Enhancements Enhanced functionality for WIP Final Completion, WIP Scrap Absorption,
PAC WIP Value Report, Material Overhead Absorption Rule, EAM work order, and PAC EAM Work Order Cost Estimate
Processor Report.
Component Yield benefits - Component yield functionality user have the flexibility to control the value of component yield
factors and use those factors for back flush transactions. Of course if the yield factor is not used, yield losses can be
accounted for using the manual component issue transaction.

New Features:
R12 Features and differences with 11.5.10 Advanced Procurement Suite
o Professional Buyers Work Center To speed up buyers daily purchasing tasks view & act upon requisition demand,
create & manage orders and agreements, run negotiation events, manage supplier information.
o Freight and Miscellaneous Charges New page for viewing acquisition cost to track freight & miscellaneous delivery cost
components while receiving. Actual delivery costs are tracked during invoice matching.
o Complex Contract Payments Support for payments for services related procurement including progress payments,
recoupment of advances, and retainage.
o Unified Inventory Support for the converged inventory between Oracle Process Manufacturing OPM Inventory & Oracle
Inventory.
o Document Publishing Enhancements Support for RTF & PDF layouts and publish contracts using user specified layouts
o Support for Contractor Purchasing Users Support for contingent workers to create & maintain requisitions, conduct
negotiations, and purchase orders.
New Features:

R12 Features and differences with 11.5.10 Order Management

Multi-Organization Access Control (MOAC) - Multi-Org Access Control enables uses to access multiple operating units data
from single responsibility. Users can access reports , Concurrent programs , all setup screens of multiple operating units
from single responsibility without switching responsibilities. They can also use Order Import to bring in orders for different
Operating Units from within a single responsibility. The same applies to the Oracle Order Management Public Application
Program Interfaces (APIs).
o Post Booking Item Substitution - Item Substitution functionality support has been extended to post-Booking through
Scheduling/re-scheduling in Sales Order, Quick Sales Order, and Scheduling Order Organizer forms. Item Substitution
functionality is also supported from Planners Workbench (loop-back functionality) till the line is pick-released.
o Item Orderability - Businesses need the ability to define which customers are allowed to order which products, and the ability
to apply the business logic when the order is created.
o Mass Scheduling Enhancements Mass Scheduling can now schedule lines that never been scheduled or those that have
failed manual scheduling. Mass Scheduling also supports unscheduling and rescheduling
o Exception Management Enhancements Improved visibility to workflow errors and eases the process of retrying workflows
that have experienced processing errors
o Sales Order Reservation for Lot-Based Jobs Lot-Based Jobs as a Source of Supply to Reserve Against Sales Order(s).
OSFM Displays Sales Order Information on Reserved Jobs
o Cascading Attributes Cascading means that if the Order header attributes change, the corresponding line attributes
change
o Customer Credit Check Hold Source Support across Operating Units - Order Management honors credit holds placed on
customers from AR across operating Units. When Receivables places a customer on credit hold a hold source will be
created in all operating units which have:

A site defined for that customer

An order placed against that customer.

o

New Features:
R12 Features and differences with 11.5.10 Shipping
o Pick Release/Confirm Features

Pick Release enhancements - Enhancements will be made to the Release Sales Order Form and the Release Rules Form
to support planned crossdocking and task priority for Oracle Warehouse Management (WMS) organizations. Pick release
will allow a user to specify location methods and if crossdocking is required, a cross-dock rule. The task priority will be able
to be set for each task in a sales order picking wave when that wave is pick released. The priority indicated at pick release
will be defaulted to every Oracle WMS task created

Parallel Pick Release Submission - This new feature will allow users to run multiple pick release processes in parallel to
improve overall performance. By distributing the workload across multiple processors, users can reduce the overall time
required for a single pick release run.
o Workflow Shipping Transaction Enhancement Oracle has enabled Workflow in the Shipping process for: workflow, process
workflow, activity and notification workflow, and business event
o Support for Miscellaneous Shipping Transactions - Oracle Shipping Execution users will now be able to create a delivery for
a shipment that is not tied to a sales order via XML (XML-equivalent of EDI 940 IN). Once this delivery has been created,
users will be able to print shipping documents, plan, rate, tender, audit and record the issuance out of inventory. Additionally,
an XML Shipment Advice (XML- equivalent of EDI 945 OUT) will be supported to record the outbound transactions.
o Flexible Documents: With this new feature ,Shipping Execution users will be able to create template-based, easy-to-use
formats to quickly produce and easily maintain shipping documents unique to their business. Additional attributes will be
added to the XML templates for each report for added flexibility
o Enhanced LPN Support - Oracle Shipping Execution users will now have improved visibility to the Oracle WMS packing
hierarchy at Pick Confirmation. The packing hierarchy, including the License Plate Number (LPN), will be visible in the
Shipping Transactions form as well as in the Quick Ship user interface.

New Features:
R12 Features and differences with 11.5.10 Warehouse Management
o Crossdock Execution WMS allow you to determine final staging lane, merge with existing delivery or create a new delivery,
synchronize inbound operation plan with outbound consolidation plan, enhance outbound consolidation plans and manage
crossdock tasks.
o Labor Management WMS provides labor analysis. It gives the warehouse manager increased visibility to resource
requirements. Detailed information for the productivity of individual employees and warehouses is provided
o Warehouse Control Board Additions - Additional Task selection criteria
o User Extensible Label Fields WMS, users are now able to add their own variables without customizing the application, by
simply defining in SQL the way to get to that data element
o Material Consolidation across deliveries WMS allows you to consolidate material across deliveries in a staging lane

New Features:
R12 Features and differences with 11.5.10 OSFM
o Lot and Serial Controlled Assembly Lot controlled job can now be associated with serial numbers to track and trace
serialized lot/item during shop floor transactions as well as post manufacturing and beyond
o Fixed Component Usage Support for Lot Based Jobs OSFM now supports fixed component usage defined in the Bill of
Material of an end it.
o Support for Partial Move Transactions Users are able to execute movement of a partial job quantity interoperation
o Enhanced BOM to Capture Inverse Usage Users can now capture the inverse component usage through the new inverse
usage field in BOM UI
o Support for Rosetta Net Transaction - comprising of 7B1 (work in process) and 7B5 (manufacturing work order).
New Features:
R12 Further Info
o The latest RCD (Release Content Documents) can be accessed from the metalink note 404152.1 (requires user name &
password).
o The TOI (Transfer Of Information) sessions released by Oracle Learning can be accessed from its portal at http://
www.oracle.com/education/oukc/ebs.html
o Oracle White papers Extending the value of Your Oracle E-Business Suite 11i.10 Investment & Application Upgrades and
Service Oriented Architecture

**********

DIFFERENCE BETWEEN 11I

AND R12 MODULE WISE
Posted by Raju ERP

Difference between 11i and R12 module wise:

Recently our business users have upgrade from 11.5.10 to R12.1.3.

After upgrade I have seen a lot of changes happened in R12.1.3. I
have faced a lot of problems while upgrade. Finally it went very
smoothly.

Now i am going to tell you what is difference between 11i and R12
module wise

General Ledger: (GL)

1. Ledgers:

The ledger is a basic concept in Release 12. The ledger replaces the
11i concept of a set of books. It represents an accounting
representation for one or more legal entities or for a business need
such as consolidation or management reporting. Companies can
now clearly and efficiently model its legal entities and their
accounting representations in Release 12. This seems to be a major
area in getting success of the shared service center and single
instance initiatives where many or all legal entities of an enterprise
are accounted for in a single instance, and data, setup, and
processing must be effectively secured but also possibly shared.
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 3Cs

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.

2. Definition Access Set:

Definition Access Sets are an optional security feature that allows

you to secure shared
General Ledger definitions such as MassAllocations, Recurring
Journal Formulas, and
Financial Statement Generator (FSG) components.

Definition Access Sets allow you to:

Assign a user or group of users access to specific definitions.

 Specify what actions can be performed on secured definitions for a

user or group of

users.

For example, you can secure FSG reports to allow some users to
modify the report

definition, other users to only view the report definition, while other
users can modify,

view, and submit the report.

For more information please go trough below link

http://orafinappssetups.blogspot.in/2012/12/definition-accesssets.html

3. Data Access Set:

As we discussed earlier, Release 12 allows one to assign multiple

ledgers to a responsibility. Alongside, one would also be able to
choose the level of privileges that one could provide for each of
these ledgers. For example, I may want my user to have complete

Read Write privileges for Ledger A, but he should be able to only

View the data that exists in Ledger B. Data Access Set also makes
this kind of a combination possible.

The General Ledger Accounting Setup Program automatically

creates a data access set for each ledger and reporting currency
(journal level or subledger level) assigned to a completed
accounting setup. The system-generated data access sets created
for each ledger and reporting currency provide full read and write
access to the ledger and all of its balancing segment values and
management segment values.

4. Accounting Setup Manager:

Accounting Setup Manager is a new feature that streamlines the

setup and implementation of Oracle Financial Applications.With the
Accounting Setup Manager; one can perform and maintain the
following common setup components from a central location:

Legal Entities

Ledgers, primary and secondary

Operating Units, which are assigned to primary ledgers

Reporting Currencies

Subledger Accounting Options. This is where you define the

accounting methods for each submodule and associate them to
the ledger where the accounting is stored.

Intercompany Accounts and Balancing Rules

Accounting and Reporting Sequencing

5. Ledger Sets:

A ledger set is a group of ledgers that share the same chart of

accounts and calendar/period type combination. Ledger sets allow
you to run processes and reports for multiple ledgers
simultaneously.

For example, you can open/close periods for multiple ledgers at

once, run recurring journals that update balances for multiple
ledgers, or run consolidated financial reports that summarize
balances across multiple ledgers in a ledger set. You can group all
types of ledgers in a ledger set, such as primary ledger, secondary

ledgers, and reporting currencies (journal and subledger levels), as

long as they share the same chart of accounts and calendar/period
type combination. The same ledger can belong to multiple ledger
sets, and ledger sets can contain other ledger sets.

6. Sequencing:

In Release 12, in order to cater to the need for Legal compliance for
countries like Europe and Latin America, two more sequencing
options have been introduced as a part of standard application apart
from existing Document Sequences. These Sequences can be
assigned not only to journals in General Ledger module but also to
those created in SLA:
Accounting Sequence:

Accounting Sequences are assigned to GL journals when they are

posted and to Subledger Journals once they complete accounting.
Reporting Sequence:
Reporting Sequences are assigned to journals in GL and Subledger
journals upon GL period closure. Once a period is closed, the close
period program fires a Create Reporting Sequences program as a
shoot off. This program assigns reporting sequences to journals.

7. Line Level Reconciliation

General Ledger Reconciliation allows users to reconcile transactions
in General Ledger and ensure that the sum of these set of
transactions is zero. An example where this functionality would be
required is the VAT control account.
One can enable reconciliation either for Natural Account Values for
specific code combinations. Using this new functionality, one can
selective cross reference transactions by entering a "Reconciliation
Reference" at the Journals Line level. One can perform account
reconciliation either automatically with the General Ledger
Automatic Reconciliation report, or manually in the Reconciliation
Lines window.
Use automatic reconciliation to reconcile journal lines that have
matching balancing segments, account segments, and reconciliation
references, or optionally where the reconciliation reference is blank.
Use manual reconciliation to reconcile journal lines with different
code combinations (including different balancing segments or
account segments) or different reconciliation references.
For both automatic and manual reconciliation, the balance for the
journal lines that you Want to reconcile must be zero. Reconciliations
can be performed between transactions entered in the same or
different currencies.

Payables:

Suppliers are defined as Parties within the Oracle Trading

Community Architecture (TCA).
Invoice Lines are introduced as an entity between the
Invoice Header and Invoice Distributions to better match the
structure of invoice documents and to improve the flow of
information such as manufacturer, model and serial number from
Purchasing through to Assets.
Banks, bank branches, and internal bank accounts are
defined centrally and are managed in Oracle Cash Management.
Document sequencing of payments has moved to the Cash
Management bank account setup.
A new module called Oracle Payments now handles
payments and all funds disbursement activities.
Payment features controlled by Global Descriptive Flexfields
(GDF) in prior releases have been consolidated and migrated into
the data models of Oracle Payables, Oracle Payments, and Oracle
Cash Management. The architecture of this solution moves
attributes from the GDFs, which are now obsolete, to regular fields
on the appropriate entity, including the invoice, payment format
and document, supplier site, and bank account. Having a single
code base as opposed to GDFs implemented per country
simplifies global implementations and streamlines transaction
processing.
Oracle Subledger Accounting, a new module in Release 12,
handles accounting definitions and all accounting setup
associated with a Ledger. In Release 12, Oracle General Ledger
has replaced the term Sets of Books with Ledgers. As part of this
change, centralized accounting reports are available to all
applications. Additionally, Oracle Payables introduces a new Trial
Balance report.

Oracle E-Business Tax, a new module in Release 12, manages

transaction tax setup associated with trading partners and tax

authorities, as well as transaction tax processing and reporting

across the Oracle E-Business Suite. Part of the architecture of this
solution moves tax attributes from Global Descriptive Flexfields
(GDFs), which are obsolete in Release 12, to regular fields on the
appropriate entities.

A responsibility can be associated with multiple Operating

Units using Multiple Organization Access Control (MOAC). Due to
this change, all processing and some reporting in Oracle Payables
are available across Operating Units from a single applications
responsibility. Hence you can isolate your transaction data by
operating unit for security and local level compliance while still
enabling shared service center processing.

Receivables:

Integration with E-Business Tax Release 12 introduces

Oracle E-Business Tax to manage tax across the E-Business Suite.
During the upgrade, system and customer options used to control
tax calculation and tax code defaulting are migrated from Oracle
Receivables into Oracle E-Business Tax entities.

Integration with Subledger Accounting Release 12 introduces

Subledger Accounting for managing accounting across Subledger
transactions. Receivables no longer create any accounting entries.
Existing Receivables accounting options and setups remain, and
they affect the generation of accounting distributions in the
Receivables data model.

Centralized Banks and Bank Accounts Definitions In Release

12, all internal banks and bank accounts you previously defined
for your operations are migrated to central Cash Management
entities. Remittance bank accounts are owned by a legal entity
rather than by an operating unit. However, bank accounts you
defined for your customers are migrated from the Payables
entities to the centralized Payments entities. Oracle Payments
centralizes and secures all payment instrument data, including
external bank accounts, credit cards, and debit cards.

Integration with Payments for Funds Capture Release 12

introduces Oracle Payments, which is used by Oracle Receivables
for processing funds capture.