Oracle OM R12 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).

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.

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.

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. . It also can now pickup lines that are in Entered status - both converted and manually entered orders.

Exception Management Enhancements Improved visibility to workflow errors

and eases the process of retrying workflows that have experienced processing
errors

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

Cascading Attributes Cascading means that if the Order header attributes

change, the corresponding line attributes change

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.

Blanket Sales Agreements terminology which was used in 11i is now

renamed to Sales Agreements. There is no functional impact for this.

Deferred COGS-Accounting Standards stipulate that COGS and Revenue are

recognized in the same accounting period. In R12 a new feature was provided to
invoke deferred COGS instead of COGS at shipment. When revenue is
recognized upon customer acceptance or a deferral reason, then an accounting
transaction is created to hit the COGS account. COGS will be recognized to the
same percentage as the revenue.

Credit Card Enhancement - An additional field has been added to the order
entry screen to capture the security code typically located on the back of a credit
card. Additionally, the credit card number is encrypted at the database level and
stored within the Payments (formally iPayments) module.

Reoccurring Charges - Recurring charges feature accurately display totals,

taxes and discounts of recurring and one-time prices when telecommunications
services are ordered. Functionality has been added to the TSO
(Telecommunications Service Ordering) module which allows reoccurring billings.
This is perfect for subscriptions and other like services.

Customer Acceptance Process - Oracle R12 now provides the ability to

introduce a customer acceptance step prior to invoicing. By setting up a deferral
reason in AR, invoicing can be deferred until acceptance has been captured.
Revenue Contingency which can be used for pre-billing or post-billing customer
acceptance.

In Pre-Billing acceptance, the line gets invoiced, closed and revenue

recognized after the acceptance. Invoice Pending Acceptance supports
when acceptance, installation, or other requirements must be meet prior
to invoicing.

In Post-Billing acceptance, the line gets closed and revenue recognized

after the acceptance.

Partial Period Revenue Recognition - A joint OM and AR enhancement, partial

period revenue recognition is a set of new revenue recognition rules in AR which
allow for revenue recognition on a daily basis. Previously in 11i revenue
recognition could only be done on a monthly basis.

Pay Now or Pay Later - Upfront billing in Order Management can now be done
and can be configured based on pricing charges, taxes, deposits, installment
billing, and prepayments.

The Contact Center form - Has been modified to host new OM tab pages to
create and edit orders. The Contact Center is also enhanced to support a
streamlined flow to order changes to telecommunications services using the new
OM tab pages and an enhanced Installed Base tab page.

Assemble to Order (ATO) - At present assemble to order (ATO) items require a

Bill of Material in either the shipping or the Item Master validation organization to
perform scheduling actions on them in OM. This functionality has been enhanced
to provide the option of not requiring a BOM to schedule an ATO item when ATP
is based on collected data (ODS mode). A BOM is not required for these items if
ATP is based on planning output (PDS mode).

Tax Updates - Additional tax fields have been added to the order entry screens
that provide more flexibility with 3rd party tax software.

Architectural Changes to Inventory (Inventory Convergence) - in 11i,

Discrete and Process Inventory modules were entirely separate entities. Oracle
has converged these modules into one data structure, where functionalities from
both modules have combined to be available to both. This doesnt mean much
from an OM perspective, but technical changes have been performed to the Pick
Release and Ship Confirmation processes to work with the new combined
inventory model.

Architectural Changes to OM, Install Base, and Service Contracts

Integration - there is no functionality changes, but from a technical standpoint
Oracle has implemented a best practice approach to OM to Install Base and OM
to Service Contracts touch points to ensure API calls are used rather than direct
queries.

Shipping directly from Inventory without a Sales Order

Using XML Publisher can configure custom Bill of Lading(BOL)