Inventory New Features:

Electronic Records and Electronic Signatures (ERES) Support for 21 CFR Part 11
Compliance
With this release, Oracle Inventory has extended the support for Electronic Records and
Electronic Signatures to miscellaneous transactions. Based on user defined setup
parameters, the system may prompt a user for an electronic signature while performing
Account Alias Receipts and Issues and Miscellaneous Receipt and Issue transactions in
Oracle Inventory. When viewing transactional history in the lot or serial genealogy forms,
Oracle Inventory can display the Electronic Record generated for those transactions.
Enhanced Inter-company Transactions
With this release, Oracle Inventory has enhanced its inter-company invoicing to support
these global fulfillment and procurement business flows. This new functionality supports:
Shared Procurement Services: If a PO is placed by an operating unit (OU) that is
different from the material destination OU, then the procurement OU can invoice
that receiving OU. The invoice can be done at either the PO price or the transfer
price, and accounting is done to represent a transfer of ownership between the
OU's.
Ownership Transfer during sales order shipments: When doing a sales order
shipment from an OU that is different from the OU on the sales order, users can
now generate accounting which represents a transfer of ownership from the
shipping OU and the selling OU, rather then just a pure invoice. In this case, the
inter-company invoice is always done at transfer price.
Drop Ship Across Sets of Books: On a drop ship sales order, you must specify the
warehouse (Org) that owns the fulfillment of the order. In this release, this Org
can be in a different set of books, and the purchasing can be done through a
shared procurement center. Invoicing and accounting are done as described above.
Chains of inter-company relationships: In all of the above cases, users can define
a chain of OU's through which ownership must pass when transacting between a
selling and shipping OU, or between a procuring and receiving OU. Intercompany invoices are generated between all OU's, and accounting is done to
represent and ownership transfer between all OU's in the chain.

Outbound Flow Sequence

The Pull Sequences setup definition for Kanban cards has been enhanced to support
outbound flow sequencing. For more information on this feature, please refer to the
Oracle Flow Manufacturing section of this document.

PAR Replenishment Counts

PAR (Periodic Automated Replenishment) Level Counting addresses the needs of

facilities which do not store perpetual inventory levels, but still require locator level
replenishment to specific stock level targets. This practice is common in the
replenishment of supplies stores within hospitals and health care organizations.
This feature extends existing Replenishment Count capabilities to allow users to perform
locator level stock counting in non quantity tracked subinventories and for the system to
generate the appropriate replenishment document (Internal Requisition, Purchase Order
Requisition or Move Order) based on the item's sourcing for that subinventory if the
stock level has fallen below the target on hand for the locator.
Aging Based Consumption
In some consigned from supplier relationships, contractual agreements require that you
purchase consigned stocks that have not been consumed within a stipulated time period.
In this release, you can specify this time period in Oracle Purchasings Approved Supplier
List form. You will then be able to monitor consigned stocks that are past due in Oracle
Inventorys Consigned Inventory Aging self service page.
Consigned Inventory Diagnostics
In Consigned Inventory from Supplier flow, errors may occur during consumption or
billing. Possible sources of error include missing set up or invalid blanket agreements. In
this release, the Pending Transaction window has been enhanced to display errors that
occurred during ownership transfer. The Material Transaction window has been enhanced
to
display
errors
that
occur
during
consumption
advice
creation a preventive tool, the Consigned Inventory Diagnostics concurrent program
allows the user to monitor potential errors that may interfere with consumption or billing.
When the concurrent program detects an error, an Oracle Workflow notification will be
sent to the buyer for remedial actions. A new self service page is also provided for the
Inventory Manager to monitor these potential errors.
Changed Features
Manufacturing Component Picking Enhancements
Attributes of the job, such as assembly quantity increase, or component deletion, may
change after an associated component pick task was created. These changes may impact
the pick task. This project addresses many types of job changes, and synchronizes these
to the associated inventory allocation or task. In addition, overpicking for components
can now be supported.

Item Master Changes

The following new attributes have been added to the inventory item definition. For more
information regarding each of these attributes.

Catch Weight enabledAuto created Configuration

Created Configured Item, Bom
Match Configuration
Activity Source
Vendor Managed Inventory
Replenishment Point Minimum Quantity
Replenishment Point Minimum Days of Supply
Order Quantity Maximum Quantity
Order Quantity Maximum Days of Supply
Order Quantity Fixed Quantity
Release Authorization Required
Consigned Item
Auto Expire ASN
Average Daily Demand Calculation Forecast Type
Average Daily Demand Calculation Window Days
Exclude From Budget
Critical Component
Incremental Supply Pattern
Continuous Inter-Org Transfers
Convergence Pattern
Divergence Pattern
Distribution Planning
DRP Planning
Maximum Inventory
Days of Supply
Window
Target Inventory
Days of Supply
Window
Recovered Part Disposition
Service Duration (removed)
Subscription Dependency Enabled (removed)
Service Importance Level (removed)

New Features

Allocation Delete at Move Order Cancel

Currently, when move order lines are canceled due to source order cancellation, move
order line allocations are not automatically deleted. A new parameter has been
introduced for inventory organizations, which enables automatic deletion of move order
line allocations when move order line status is set to Canceled. This behavior is
applicable for all the move order types - Pick wave, Component Pick release,
Replenishment and Requisition move order types.

Cross
Organization
Serial
Genealogy
Inquiry
Users can now inquire on a Serial's transaction history and genealogy without first
knowing the Organization in which it currently resides. In addition, the display will show
all transaction history and genealogy data across all Organizations.

Purchasing New Features:

Model Complex Pricing with Oracle Advanced Pricing
Oracle Advanced Pricing is now integrated with Oracle Purchasing and Oracle
iProcurement. Oracle Advanced Pricing is a flexible pricing engine capable of addressing
complex pricing needs of customers. Using Oracle Advanced Pricing, purchasing
professionals can setup complex pricing structures in the form of price lists, price
formulas and modifiers. Price lists contain the basic information that associates price and
currency with an item, service, group of products or services, or sub-component. Pricing
formulas let you model mathematical relationships for product pricing using certain order
attributes. Price modifiers allow you to setup discounts or surcharges that can be applied
on top of base prices.
To price requisitions and purchase orders based on pricing rules setup in Oracle
Advanced Pricing, the requisition or purchase order line need simply reference a contract
purchase agreement.
Requisition Approval Management using Oracle Approvals Management
Oracle Purchasing now provides the option to use Oracle Approvals Management as the
approval engine for requisitions. Some of the benefits include:
Single approval engine with consistent and uniform approval policies across
multiple Oracle Applications modules including Oracle iExpenses.
Approval policies can be defined once and be leveraged across multiple products;
hence less maintenance is required.
Approval policies can easily be extended using the standard features of Oracle
Approvals Management eliminating the need to customize individual applications
or the workflow.

Purchase Order Printing and Communication in PDF

Oracle Purchasing includes a powerful and flexible solution for creating and formatting
purchase orders in Adobe Portable Document Format (PDF). In Oracle Purchasing, the
buyer can view a draft version of the PDF purchase order. After approval, generated PDF
documents can be sent using email, fax, or print and are viewable online in Oracle
Purchasing, Oracle iSupplier Portal, and Oracle Sourcing. You can set up layout
templates that define how your purchase orders should be formatted, including the
company logo, headers, footers, and watermarking.
This feature is extended for use by Oracle Procurement Contracts and therefore described
in the context of contract management in a dedicated document for that new product.
Suggested Document:258526.1.
Buyer Driven Logistics Management
Some companies choose to manage inbound shipments from their supply base. Oracle
Purchasing is now integrated with Oracle Transportation Management to provide
transportation execution personnel and planners visibility into open purchase orders,
shipments available for pickup at supplier sites, and in-transit shipments. Based on this
information, planners can create an optimal route for their logistics fleet. This route can
include a combination of supplier locations for goods pickup (inbound shipments) and
customer locations for shipment drop-off (outbound shipments). This feature allows
companies to greatly reduce freight costs by optimizing their transportation plans.
FDA CFR 21 Compliance
Oracle Purchasing now aids compliance with the FDA Code of Federal Regulations 21
Part 11 requirements governing the technical aspects of computer and software systems
that are used by manufacturers. Specifically, Oracle Purchasing now satisfies the two
primary requirements of CFR Part 11: electronic records (e-records) and electronic
signatures (e-signatures).
The new functionality is manifest in two areas: the approved supplier list (ASL) and
receiving inspections with Oracle Quality. Changes to an ASL attribute are now recorded
through an e-record to an evidence store. Likewise, an e-record snapshot is also stored for
receiving inspections using Oracle Quality. Additionally, receiving inspections using
Oracle Quality capture an e-signature through a self-service browser window. Please refer
to the About Oracle Quality document for additional information;

Integration with Procurement Contracts

Oracle Procurement Contracts provides robust contract management capabilities for
procurement professionals, including a sophisticated contract terms library, robust

deliverables tracking and formal change management. Organizations can use these
capabilities to minimize exposure to contractual risks, maximize their buying power, and
eliminate erroneous payments from sourcing through contract award, order execution
through termination or renewals. Oracle Purchasing allows you to leverage these new
capabilities in various aspects of the procurement flow; contract authoring with
sophisticated terms, deliverables definition and tracking, contract binding and document
signatures, document communication in PDF format, contract attachments with revision
tracking, and more. Please refer to the About Oracle Procurement Contracts document for
more information;
Integration with Services Procurement
Oracle Services Procurement enables a streamlined process for sourcing, procuring and
managing of services, such as contingent labor, facilities management, marketing,
information technology, consulting services, and more. These commodity areas usually
account for a large percentage of an organizations spend. Oracle Purchasing enables key
business functions in the services procurement flow, including preferred supplier
identification and management, long term agreements for fixed price and rate based
services, purchase order management, time card management and auto invoice generation
and payment. Please refer to the About Oracle Services Procurement document for
additional information;
Gapless Self-Bill Invoice Numbering
Self-bill Invoices (SBI) is an automated invoicing process where the buying company
creates an invoice on behalf of the supplier. This process lowers the invoicing costs,
errors and cycle time for both buyers and suppliers. SBIs include evaluated receipt
settlements, debit memos, and purchase price adjustment invoices. Certain countries
require that invoice numbers on SBIs be gapless.
Oracle Purchasing now supports gapless invoice numbering for all self-billing invoices.
The buying organization has the flexibility to turn on or off gapless SBI numbering by
supplier site or by operating unit.

Changed Features
Retroactive Price Changes

Prices for items on blanket agreements can change over the effective period of an
agreement as a result of ongoing negotiations between the buyer and the supplier. In fact,
it is common practice in certain industries to initiate and execute against an agreement
with an interim price. A firm price may get finalized several months into the life of the
agreement. In these scenarios it is possible that the updated price is applicable
retroactively. Oracle Purchasing allows buyers to make price changes on global blanket
agreements and on blanket agreements. With 11.5.9, Oracle Purchasing allowed
automatic updates to orders (standard purchase orders and blanket releases) referencing
the modified agreements with the latest pricing as long as there was no receiving or
invoicing activity against these orders. With this release Oracle Purchasing can optionally
update prices on orders to reflect the latest agreement price, even if there has been
receiving and invoicing activities against them. Additionally, for orders that have been
received against, Oracle Purchasing automatically adjusts the accrued liability to reflect
the latest pricing. Finally, for orders that have been invoiced, Oracle Purchasing
automatically generates price adjustment invoices in Oracle Payables. Depending on the
nature of the change, the Payables department can then process either a payment or a
debit memo request against the price adjustment invoice.
Receiving Open Interface Enhancements
Most companies managing receiving docks in a high volume environment use barcodes
and radio frequency (RF) scanning devices to record shipment and receipt information.
Such capabilities are readily available when receiving using the Oracle Mobile Supply
Chain (Oracle MSCA) or Oracle Warehouse Management (Oracle WMS) applications.
Should a company have some other form of barcode/RF support then the receiving open
interface provides a mechanism to process the generated transactions. Substantial
improvements to the receiving open interface include:
Support for most receiving transactions, including advanced shipment notices
(ASN), advanced shipment billing notices (ASBN), receipts, deliveries,
inspections, and transfers.
Multistage
transaction
processing:
For example, you may import related receive, transfer and deliver transactions as
and when they occur.
Receiving transactions against advanced shipment notices (ASN), advanced
shipment billing notices (ASBN), return material authorizations (RMA), internal
orders, and inter-organizational transfers.
The import of transactions in Batch, Immediate, and Online modes.

These enhancements are intended to significantly improve the productivity of personnel

working on receiving docks by minimizing manual data entry requirements. For technical
details see the Updates to the Receiving Open Interface topic in the New and Changed
Setup Steps section of this document.
Drop Shipment Enhancements

The integrated business flow between Oracle Order Management and Oracle Purchasing
facilitating drop shipments has been streamlined. Enhancements include:
Improved Purchase Order Communication: Drop ship purchase order information
communicated to suppliers includes all relevant details about the end customer
(customer name, ship-to contact, etc.).
Automatic Document Synchronization: Customer requested changes to sales
orders (for example, order cancellation, quantity increase, or date changes) in
Oracle Order Management would now automatically flow down to the
corresponding purchasing documents. This ensures that the sales order and the
corresponding purchase order are always in sync, eliminating the need for manual
data synchronization. Changes to the sales order are automatically captured as
revisions to the corresponding purchase order. These changes can be
automatically communicated to the supplier as a purchase order change.
ASN Auto-generation of Receipt: Suppliers send an advanced shipment notice
(ASN) to notify the purchasing organization that goods have been shipped.
Buying organizations can now choose to automatically record receipt transactions
against the supplier ASN. This receipt enables buying organizations to recognize
liability and to optionally automatically generate the invoice as soon as the goods
are shipped to the end customer. The receipt can also be used to automatically
generate an invoice for the end customer in Oracle Accounts Receivable.

Encumbrance Enhancements
Many organizations negotiate long-term agreements with suppliers and commit to a
certain level of spending during the life of the agreement. These minimum spending
commitments need to be captured and budgeted. Buyers now are able to capture these
commitments and encumber funds on blanket and global blanket agreements to
accurately reflect existing commitment levels. These funds are encumbered against a
summary budget account as called out by the buyer on the agreement. The encumbrance
on an agreement is gradually relieved as purchase orders or releases are created against
the agreement. Requisition lines referencing encumbered agreements are not
encumbered, as funds committed on the backing agreement have already been reserved.
You can now relieve encumbrance at any level (header, line, shipment, or distribution) of
the purchasing document from the entry windows (View Purchase Orders, View Releases,
or View Requisitions).

Nested License Plate Number (LPN) and Lot/Serial

Suppliers can include lot/serial and LPN information in an Advance Shipment Notice
(ASN). This information is automatically captured in subsequent receipt transactions,
thus greatly reducing manual data entry at time of receipt.
All LPN actions pack, unpack, nesting, transfer can be performed on receiving
transactions through the Oracle Purchasing receiving open interface. LPN information is
never mandatory, but once assigned to a material in a receiving transaction it will remain
associated with it unless you change it.
For lot/serial controlled items, you can define lot and serial information on all receiving
transactions imported through the receiving open interface. These include receipts,
transfers, inspections, deliveries, returns and corrections. The lot/serial information is
optional throughout receiving and is mandatory only at delivery into inventory. This
functionality takes advantage of the Oracle Warehouse Management LPN open interface
table (WMS_LPN_INTERFACE). Suggested Document 258449.1
Receiving Locator Support
Sub inventory and locator functionality has been extended to the receiving dock allowing
for an added level of granularity to receiving locations. It is now possible to specify
receiving subinventories and locators on receiving transactions in addition to the
receiving location, when importing these transactions through the open interface. This
makes it easier to accurately track material on the receiving dock.
Integration with Oracle Inventory provides receiving personnel access to the Inventory
Material Workbench with a view of all the material contained in receiving sub-inventories
and locators.
Timestamps for Improved Logistics Management
You can now specify a time associated with need by and promised dates on requisitions
and purchase orders. This enables you to be more specific in communicating your
requirements to suppliers. Oracle Purchasing also allows capture of timestamps for
receiving transactions.
Some organizations may find the additional time component useful to more effectively
plan resource requirements, receiving activity and downstream material usage, especially
in low lead-time, JIT environments.

Category Based Account Defaulting in Oracle Purchasing

Account generation workflow logic has been enhanced to add category specificity to the
default expense charge account on purchase orders or releases. Companies can call out
segments that will carry category specific values in the multi-segment charge account
structure. The account generator workflow has been enhanced to construct the expense
account based on a combination of the employee default expense account and the
category specific rules. Equivalent functionality for expense account defaulting has been
available from Release11.5.9 onwards.
Center-Led Procurement Features
With 11.5.10, Oracle Purchasing includes a powerful solution for automating the
purchase order execution, receipt and invoice where the requesting business unit differs
from the organization that issues the purchase order. With the intercompany transaction
flows established, the system can issue the purchase order from the appropriate buying
center and handle the required accounting charges. This solution can be especially useful
for companies that use shared service centers or when purchase orders need to be issued
sby specific subsidiary organizations.

Enable
Purchase
Order
Execution
in
Any
Organization
Buyers were able to centrally negotiate pricing and contract terms on behalf of
multiple organizations using Oracle Sourcing in 11.5.9. The finalized agreement
was captured as a global blanket agreement in Oracle Purchasing. Enabled
organizations were able to leverage the centrally negotiated pricing but forced to
generate purchase orders in the organization where demand originated. Now,
buyers can define purchase order execution organizations for each of the demandgenerating and enabled organizations on a global blanket agreement. For example,
a European-based company can create and enable a global agreement with a
supplier based in China and specify that all purchase orders issued against the
global agreement will be issued from an international subsidiary organization in
China. Furthermore, buyers can also specify the supplier location (supplier site)
from which demand will be satisfied for each of the enabled organizations.
Global
Contract
Purchase
Agreements
Oracle Purchasing introduces the new global contract purchase agreements
document with 11.5.10. Global contract purchase agreements, like global blanket
agreements, enable companies to centralize supplier relationship management and
to standardize terms and conditions across all enabled organizations when doing
business with a given supplier. Buying organizations may find global contract
purchase agreements especially helpful when considering how best to use Oracle
Advanced Pricing capabilities with a central procurement organization. In
addition, global contract purchase agreements may be helpful in some situations
when extending a single negotiated supplier catalog across many organizations.

Procurement
Execution
in
Shared
Services
Environments
Buyers in center-led procurement organizations are typically responsible for
procuring on behalf of multiple demand raising organizations within a company.
With this release, Oracle Purchasing provides a powerful framework from which
an organizations complex procurement environment can be mapped directly to
system execution. For example, enterprises can:
Map purchase order generating organizations (shared service centers) to
demand raising organizations via global blanket agreements or global
contract purchase agreements.
Continue to rely on automatic document creation to preserve automated
generation of purchase orders where possible, even when the purchase
order will be created in a different organization than where demand
originated.
Extend buyer productivity through access to center-led procurement
functions from the AutoCreate workbench when manual intervention or
manual purchase order creation is required.
Receipt
Accounting
&
Drop
Shipments
Regardless of which organization issued the purchase order, receipts continue to
be processed in the demand raising organizations. To reconcile accounting
between organizations, companies model their financial relationships and the
system initiates and executes appropriate cost transfer/invoicing accounting
transactions, especially if these flows cross legal entities and sets of books.
Business transactions like receipts, invoice matches and payments automatically
initiate the appropriate cost transfer or inter-company invoicing accounting
transactions based on the rules defined in the financial relationship between the
purchase order creation and receiving organizations. Please refer to the About
Oracle Inventory in Oracle Supply Chain Management document for details on
Enhanced
Inter-company
Transactions;SuggestedDocument258455.1.
The drop shipment process has also been modified to go across traditional
organization boundaries. Companies can have local or central order capture
organizations that interface with a center-led procurement shared services
organization. In fact, the order capture organization and purchasing organization
can even belong to different sets of books. The appropriate accounting and intercompany invoicing transactions are automatically initiated based on the rules
defined in the financial relationship between the sales order and purchase order
creation organizations.

Auto Create Grouping Rules Enhancement

In 11.5.9, with the introduction of time-phased pricing, you are able to setup price breaks
based on when the item is needed. The AutoCreate grouping rules were modified to
include need-by date as one of the grouping criteria. This means, multiple requisition
lines for the same item, ship-to location with different need-by dates were grouped into
different purchase order lines. In 11i10, Oracle Purchasing has introduced two new
profile options to give you complete control over the grouping criteria related to need-by
date and ship-to location.

Custom Pricing APIs

The Custom Pricing APIs can be used to complement the integration with Oracle
Advanced Pricing and can also be used with the Retroactive Price Changes feature. There
are three new pricing APIs supported in Oracle Purchasing.

Custom
Pricing
Date
API
Prices of products in catalogs may not be static and can vary with time due to
various factors: supply/demand variations, buying volume, and component price
variations. The variation of the price of a product with time is actually captured in
terms of price and effective periods in the form of price breaks on blanket
purchase agreements, and catalog quotations. Price list lines in Oracle Advanced
Pricing
can
also
have
effective
periods
defined.
Based on the supplier agreement, the price of the product being ordered or
requested from the catalog may be determined based on the price that is effective
on the pricing date. The pricing date can be the date that the order is placed, the
day that the order is shipped, or the date that the material is expected to arrive.
Rules determining the pricing date widely vary from one business to another and
even
within
a
business
from
one
commodity
to
another.
Businesses can add PL/SQL code to a new custom hook that accommodates their
own special rules to determine the pricing date. Subsequent pricing calls return
the unit price from the source blanket or quotation that is effective on the pricing
date.

Custom
Requisition
Pricing
API
Often times the price maintained on supplier catalogs are purely list prices and
does not factor in adjustments like discounts and surcharges as negotiated
between a specific buyer-supplier pair. Businesses can add PL/SQL code to a new
custom price adjustment hook in the standard Requisition Pricing API to adjust
the price as determined from a source document (blanket or quote). This provides
a mechanism to factor in negotiated discounts, surcharges, or other adjustments on
top of the catalog prices.
Custom
PO/Release
Pricing
API
Businesses can add PL/SQL code to a new custom price adjustment hook in the
standard PO/Release Pricing API that can adjust the unit price as determined from
a source document (blanket or quote). This would provides a mechanism to factor
in negotiated discounts, surcharges, or other adjustments on top of the catalog
prices.

Price Update Flexibility on Orders, Releases

You can now manually change prices on purchase orders or releases even if there have
been receiving and invoicing activities against them. This greatly simplifies the
procurement process for goods or services where pricing is volatile and changes often
need to be made after the purchase order has been created and possibly even after a
purchase order has been received or invoiced.
Control Action Enhancements
Oracle Purchasing supports cancel actions from the Tools menu in the Enter Purchase
Order and Enter Release windows. This allows multiple cancel actions on a single
document to be performed within a single revision from the entry windows. Cancel
actions from Purchase Order Summary, Enter Purchase Order/Release, and the Cancel
API support all communication modes (print, fax, e-mail, XML, EDI).
PDOI Enhancements
The Oracle Purchasing Documents Open Interface (PDOI) has been enhanched as
follows:
Add Standard Purchase Order Lines and Shipments: You can add a new line to an
existing standard purchase order, based on certain conditions such as document
status through the purchasing documents open interface. This will enable new
purchase order lines to be imported from a legacy system or another Oracle
Applications instance, allowing for seamless processing of receipts and invoice
matching. When a new line is added to an existing standard purchase order all the
applicable actions like re-approval, archival, reservation will be performed on
these lines based on the status of the purchase order.
Import Grant Information: Companies can now import award information related
to purchase order distributions using the PDOI. This eliminates the need for
manual data entry when importing purchase order information from an external
source.

UI Enhancements
UI Improvements have been made to some of the purchasing windows to allow buyers to
perform their daily tasks more efficiently.

Increased the size of the Enter Purchase Order window and the AutoCreate
window Increased the number of requisition lines displayed in the AutoCreate
window Increased the number of lines displayed in the Enter Purchase Order
window Reduce unnecessary pop up windows in the enter Purchase Order
window and the AutoCreate window Provide Reassign Buyer option in the
AutoCreate window secured by a menu function Improvements to the Enter
Releases window to function more like the Enter Purchase Order window
Multiple tabs in the Approval window of the Enter Purchase Order window for
easier navigation

Oracle Procurement Contracts

In SCM FP.J RUP1, Oracle Procurement Contracts introduces a number of new features.
These features expand choice for both buyer and approver through the contract lifecycle.
If you have implemented Oracle Procurement Contracts, then these features are available
to you when you upgrade to SCM FP.J RUP1. Microsoft Word Integration: View and
update contract terms in Microsoft Word.
Contract Deviations Report: Tracks changes made to the standard terms and
conditions relative to the pre-approved template.
Contract Expert: A rule-based contract creation wizard that assists in authoring
complex contracts.
Enhanced Electronic Signature Support: Validate approvers' signatures using
digital certificates issued by a certification authority.
Automatic Application of Contract Templates: Default contract templates can be
automatically added to a new standard purchase order, blanket purchase
agreement, or contract purchase agreement.

New Features in Pricing:

Changed Features
Creating Modifiers
Guided flows to create modifiers are now available in the HTML User Interface (UI). In the
HTML interface, you can create the following modifier list types:

Deal
Discount List
Promotion List
Surcharge List

You can create the following modifier line types:

Discount
Price Break
Promotional Goods
Surcharge

This feature is only available in Oracle Advanced Pricing.

Creating Price Lists

Guided flows to create price lists and price list lines are now available in the HTML User
Interface (UI). This feature is only available in Oracle Advanced Pricing.
Creating Qualifiers
Guided flows to create qualifiers for price lists and modifiers are now available in the HTML
User Interface (UI). This feature is only available in Oracle Advanced Pricing. Note: Qualifier
groups can only be created in the forms-based windows but, once created, can be used in the
HTML UI.
Updating Price lists and Modifiers created from Blanket Sales Agreement (Oracle Order
Management)
Price lists and modifiers created from Blanket Agreements cannot be updated (regardless of any
other QP security rules) from outside of Blanket Agreements. Therefore, they are view-only if
they are opened through the Pricing Manager Responsibility. Price lists and modifiers created for
blankets are NON- SHAREABLE (the lists created for one BSA can not be shared by other
BSA).
Attribute Manager Loader
In previous releases, multiple .ldts per product consisting of same entity
affected performance of the database driver. The same data or overlapping data
for the same entity could be uploaded multiple times.
In this release, two attribute manager loaders are provided for loading attributes:
QPXATTRS.ldt: Is owned and managed by QP (pricing). Contains Contexts, Attributes

and PTE-Attributes links. The Control File is QPXATTRS.lct.

xxxATMAP.ldt (where xxx = AMS, QPX, ASO, OKC, INV, etc): Is owned by individual
integrating teams. Contains Attribute Mapping rules owned by the team. The Control File
is QPXATMAP.lct.
New Features
Net Amount Calculation field ( New list of value item added: "For Matching Products")
The Net Amount Calculation feature enables you to set up a modifier to calculate the selling price
based on the net amount (bucketed amount). A new value "For matching products" has been
added to the Net Amount Calculation field (the existing value is "For all matching attributes.")
You can select net amount calculation options from the Net Amount Calculation field when
setting up a price break modifier line in the HTML or Forms-based user interface.
When a modifier with "For matching products" is applied to an order, the following actions
occur:
1. The order lines that match the Product criteria defined in the price break modifier are
selected and grouped. The Product could be defined by criteria such as Item Number or
Item Category (additional Product criteria are available). Note: For calculating the net

amount calculations, the order lines are selected regardless if the order line meets all of
the other modifiers qualifications.
2. The calculation engine takes the sum of the amounts from the order lines selected from
the preceding step.
3. The sum of amounts is used as the group amount for the net amount calculations.
Example
Suppose you create a price break modifier line with the following setup (this is a simplified
example):
Product: Item Number AS54888
Net Amount Calculation: "For matching products" selected
Pricing Attribute: Red

If this modifier is applied against the following order (this is a simplified order example: item
number, unit prices and other information is omitted), then all order lines that match the Product
(in this case, Item Number: AS54888) specified by the price break modifier line are grouped
together for the net amount calculations (regardless of other qualifying criteria).
Line

Product

Pricing Attribute

Item Number: AS54888

Red

Item Number: AS54888

Blue

Item Number: AS54888

Red

Lines that contribute to Net Amount Calculations: All order lines with Product "Item

Number: AS54888" are grouped together.

Lines that get discount: The modifier adjustment (such as a discount) will only be

applied to Lines 1 and 3 because they meet the remaining qualifying criteria that the
modifier specified (pricing attribute = Red)
You must select the following criteria to use the "For matching products" option for net amount
calculations:
Modifier Type for the modifier line must be Price Break (or Price Break Header in the

Forms-based UI) and related price breaks must be set up.

Modifier Level (for modifier lines) must be Group of Lines level. Note: If the Modifier

Line level is Line, then only "For all matching attributes" can be selected in the Net
Amount Calculation field.
Automatic check box for the modifier line must be selected.
Volume Based on must be Item Amount.
Product attribute must be defined in the setup (this is important to the special grouping by
attribute that is performed).

Promotional Goods and Net Amount Calculation: Promotional good amounts will not be
included in the net amount calculation. For example, if an order line gets a promotional good
(buy A, get B free/discounted), the new line will not contribute to any net amount calculation of
any modifier in the order.
Changed Features
Price Lists: Create Price List Line and Create Price Break Line flows (HTML UI)
Two separate flows--one for creating price list lines and the other for creating price break lines-have been added to the Update Price List: Price List Lines page in the HTML UI. From this page,
click either the Create Price List Line or Create Price List Break Line button to create a new price
list line or price break line.
Price List Maintenance page (HTML UI)
When you enter criteria to change existing price list/price list line information in the Maintenance
Criteria region of the Bulk Change: Make Changes page, you can click either the Continue or
Refresh Data button to process the changes. If you click Continue, the Bulk Change: Review
Changes page ds the processed changes.
In prior releases, if you entered change criteria and clicked Continue (without clicking Refresh
Data), then the changes were not processed.
Navigating between Fields
The navigation between fields has been changed for the following pages: Price Lists, Modifier
Lists, and Price List Maintenance pages (HTML UI). Now pressing the Tab key navigates you to
the field below rather than the field to the right.
Integration Enhancements with Oracle Service Contracts (OKS)
The following enhancements have been introduced to support Oracle Service Contracts (OKS)
requirements for price locking and prorated billing requirements for Advanced Pricing customers:
Price List Locking
In prior releases, the user was responsible for creating a locked price list and price list line from
the user interface (UI). However, in the current release, an API is called programmatically from
the OKS code to lock the price list and price list line without user intervention. Locking an
already locked price list and line is also supported now. A new naming convention (shown below)
automatically assigns a new name to the locked price list:
<Source System Code> || ' LOCKED ' || <Source Price List Name>
However, if the Source Price List name already has already been assigned a "locked" name, for
example, <Source System Code> || ' LOCKED ' prefix, then the new name will be <Source
System Code> || ' LOCKED' || <version no> || ' ' || <Original Source Price List Name> where the
version number starts from 2.

For example, if the source price list is named Corporate, then the locked price list will be named
QP LOCKED Corporate. However, if the source price list name is QP LOCKED Corporate, then
the locked price list name will be QP LOCKED2 Corporate.
Price Line Locking
The ability to lock an already locked price list line is now being supported in this release. Price
line locking describes the process where the price list line of the source price list is copied (now
the locked price list line) as a child of the locked price list.
For example, suppose Oracle Service Contracts (OKS) wants to lock the locked price list line
with list_line_id = 201 on the OKS LOCKED Corporate price list. Since it is an already locked
list line, it will have a pricing attribute with context = 'QP Internal' , attribute = 'List Line Id' and
value = 201. Then the following steps occur:
1. The locked price list will be created with the name OKS LOCKED Corporat price list.
2. The new locked price list line will be a copy of the price list line with list_line_id = 201
and created under the locked price list OKS LOCKED2 Corporate. The new locked line
with, for example, list_line_id = 301, will have a new pricing attribute with context = 'QP
Internal', attribute = 'List Line Id' and value = 301 attached to it (in addition to the other
pricing attributes copied over from the source list line with list_line_id 201). However,
the pricing attribute with context = 'QP Internal', attribute = 'List Line Id' and value = 201
that is attached to the source list line with list_line_id = 201 is not copied over from the
source to the newly locked list line having list_line_id = 301.
Note: The Locked price list is created only once for a given source price list and source system
code. For subsequent lock requests, the new locked price list lines are created under the already
existing locked price list.
Effective Dates for Copied Price List
No effective dates are copied to the locked price list and price list lines--instead the effective
dates can be controlled by OKS using the effectivity dates on the associated Service Contract.

New Features in Shipping

New Features
Quick Ship User Interface
The Quick Ship user interface enables users with basic shipping processes to process and record
shipments without exposing them to some of the more advanced features in Oracle Shipping
Execution. The window provides a user interface with minimum navigational requirements along
with utmost configurability. You can, for example, ship confirm a delivery with minimal
keystrokes.

Global Shipping Parameters

To better suit several organization wide parameters that previously extended across organizations,
the Global Shipping Parameters window now holds parameters that previously resided on the
Shipping Parameters window within the Shipping Transaction tab. The Global Shipping
Parameters window represents parameters that impact the features of Oracle Shipping Execution
and Oracle Transportation Execution across all organizations of an instance. The window consists
of two tabs: General and Transportation.
Consolidate at Backorder
A delivery detail can be split into multiple details as a result of pick release, packing, ship
confirm, cycle-count, or as a result of manual splits. These multiple delivery details that are
associated to the same sales order line might get backordered and be available for pick release
again. A Global Parameter entitled Consolidate Backordered Lines enables you to restore the
delivery details to their original single line state, at the time of pick release, cycle count, or ship
confirm, when this parameter is enabled.
Delivery and Trip Consolidation
With this new feature, Oracle Shipping Execution provides a method to optimize the
consolidation of deliveries and trips for freight cost savings. At pick release, instead of grouping
delivery lines into new deliveries, the system can automatically add lines to an existing open
delivery. Trip consolidation can also be performed to group deliveries into trips. Additionally, you
can perform Delivery or Trip consolidation through a new concurrent program, Process
Deliveries.
Process Deliveries SRS
This new process enables you to append deliveries and/or autocreate deliveries with unassigned
delivery lines. It also enables the autocreation of trips with delivery groups according to your
grouping
parameters
and
compatibility
constraints.

Changed Features
International Trade Management (ITM) Partner Integration Enhancements
Oracle Shipping Execution has enhanced the existing integration capability to 3rd Party
International Trade Management Partners' applications. Having pre-built integration can greatly
decrease the cost to build custom integration and to maintain it. The integration allows for the
following:
Sales orders can be submitted for export compliance screening by embedding the seeded

workflow activity within the order flow.

Deliveries can be screened at multiple points during the shipment process, including pick

release and ship confirm. Those deliveries failing screening raise a shipment exception.

 Item and Customer synchronization: The integration allows pertinent attributes of the

item and customer to be automatically synchronized to the International Trade

Management Partner application.
The new integration uses the Oracle International Trade Management (ITM) Adapter and
provides asynchronous messaging support using XML. The integration also provides
concurrent programs with flexible parameters for the item and customer synchronization.
Interlocation Transit Times Enhancements
Inter-location transit times are used by Oracle Advanced Supply Chain Planning to ensure the
timely delivery of goods. The inter-location transit time feature has been enhanced to include
more combination possibilities for Ship From and Ship To locations. For drop ship movements,
you can now set up estimated transit times between supplier locations and your customers. For
inbound movements, you can now set up estimated transit times between your suppliers and your
warehouses. Additionally, regions and zones are now supported as Ship From locations. For
example, you can set up transit times from a region to a customer. Providing specific ship
methods and the transportation time between suppliers and customers is critical to the planning
and execution of drop shipments.
Release Rules Enhancements
The criteria available in the Release Rules window has been expanded to enable greater flexibility
for pick release. It is now possible to run pick release from an item category, a destination zone,
region, or a specific subinventory. The existing shipping parameter Autocreate Delivery Criteria
(within or across orders) has been added to the Release Rules window to enable you with the
flexibility to determine how you want deliveries to be created for a particular batch. A new
subinventory field (used as a selection criteria) has been added to the Release Rules window
making it possible to pick release lines for a specific subinventory.
Also, the Release Rules criteria now includes a feature for setting up a rolling pick release
window when used in conjunction with the concurrent manager. When defining Release Rules,
you enter a release window in offset days rather than static days. The offset days defined in the
Release Rules are converted into actual dates at the time of pick release.
Pick Release Enhancements
The criteria available in the Release Sales Orders window has been expanded to give you greater
flexibility for pick release. It is now possible to define release rules and to run pick release for an
item category, a destination zone, region, or a specific subinventory.
The existing shipping parameter Autocreate Delivery Criteria (within or across orders) has been
added to the Release Sales Orders window and the Release Sales Order window to enable you
with the flexibility to determine how you want deliveries to be created for a particular batch.
A new subinventory field (used as selection criteria) has been added to the Release Sales Order
window making it possible to pick release lines for a specific subinventory.
Also, a new warning message in the Release Sales Orders window that helps to prevent
unintended releases when an unusually large number of lines will be released due to minimal
selection criteria.

Shipping Exceptions Enhancements

Shipping Exceptions functionality has been enhanced in the areas of definition, reporting,
logging, and resolving. These enhancements enable you to better manage if and when an
exception is logged, and to control whether a response is needed.
Shipping Parameters Enhancements
The existing Shipping Parameters window has been reorganized to regroup the parameters into
logical sets according to the process or entity that they impact. Another reason for the
reorganization is to distinguish between parameters that are organization-specific versus those
that are global (or across all organizations). Additionally, new parameters are also available that
enable you to define a Global Units of Measure for weight, volume, distance, dimension,
currency and, time.
Shipping Transactions Form Enhancements
The key objective of this feature is to introduce user configurability in various windows thereby
improving the usability. The enhancements enable you to work in a customizable user interface
that is intuitive and flexible, enabling a more efficient process flow. Additionally, the
enhancements also improve navigational efficiencies and performance for the various flows
within the Shipping Transactions form. Ultimately, the enhancements simplify the existing
processes while continuing to allow you to work with trips and stops.
Weight and Volume Calculation Enhancements
The behavior of the Calculate Weight and Volume functionality within Oracle Shipping Execution
has been enhanced to provide more flexibility for weight and volume calculation across all of the
Oracle Shipping Execution entities: Stops, Deliveries, LPNs, and Delivery Lines.
Interface Trip Stop - SRS
Interface Trip Stop - SRS has been modified to accept Organization code as a parameter and
process the trip stops for the specified organization. Interface Trip Stop - SRS has also been
enhanced to spawn multiple child processes to process trip stops in parallel. Two new parameters
have been added to support spawn multiple child processes. The parameter Number of Child
Processes is used to specify the number of child processes to be spawned by Interface Trip Stop SRS. The parameter Stops per Batch is used to specify the number of stops to be processed by
each thread of the Interface Trip Stop - SRS. Interface Trip Stop - SRS has also been enhanced to
defer the Inventory Interface processes. A new profile option Defer Inventory Process Online has
been added to support this feature. If this profile is set to Yes, then Inventory Interface
transactions are processed in the background by the Inventory transaction manager.

New Features in Order management :

Advanced Item Search
The intent is to provide the Oracle Order Management user with an additional, expanded
item search capability from the Sales Orders window and the Quick Sales Orders
window. The user can search for items using criteria supported by PLM Item Workbench
such as item description, category, catalog information, etc.
Approval Enhancements
A workflow process for Approvals has been created to leverage in any business process
where Approvals may be required. The Approver list can be setup in Oracle Order
Management and tied to a specific transaction type. You can create an Approval sub-flow
using the seeded approval related activities and extend your workflows and add the
approval sub-flow in it. Workflow notifications provide users the details of the approval
or rejection. In addition, an Approver list form is created that can be setup in Oracle
Order Management and tied to a specific transaction type. For the new Negotiation
feature, an approval process has been seeded using the above approval related workflow
activities. The seeded new flow is called Negotiation Flow-Generic with Approval.
Authoring and Negotiating Contract Terms
Oracle Order Management together with Oracle Sales Contracts introduces the ability to
create a long term agreement or one-time sale including terms and conditions for use by
Sales Managers, Sales Representatives, Contract Negotiators, Contract Administrators as
well as Legal Representatives. The enhanced functionality leverages seamless integration
to Oracles contract management system and includes formal negotiation complete with
internal approval and customer acceptance.
Automatic Fulfillment Set and Line Set Assignment
Oracle Order Management enhances Line Set (Ship/Arrival) and Fulfillment Set
functionality with seeded defaulting rules. Ship, Arrival, and Fulfillment sets sets can be
defaulted from transaction types. Order lines can be automatically added to fulfillment
set.
Catch Weight Support for Discrete Inventory
Catch weight support allows the user to set up an item as catch weight enabled, specify a
secondary quantity and secondary UOM at the time of shipping and to reprice and
invoice the order based on that quantity. Catch weight support in Oracle Order
Management has been available only for Inventory Organizations which are enabled for
Process Manufacturing. In this release, this functionality has been expanded to WMS
inventory organizations.

Customer Location
Oracle Order Management is being enhanced to enter Customer Locations that can be
used as a mailing address to which the quote can be sent. Customer Location can be used
during the Negotiation phase or Fulfillment phase on all Sales Transactions which
includes Quotes, Orders, and Blankets.
Decimal Quantities for Options of ATO Configurations
We now provide the ability to specify decimal quantities when selecting options for ATO
models, both in the Configuration and in the Options Window.
End Customer
This feature enables you to specify the End Customer information on a sales order.
International Trade Management Generic Export Screening
Oracle Order Management introduces Generic Export Compliance Screening through the
partner ITM application for all the export related compliance checks. These include
Restricted Party Screening, Embargo Country Screening, License Determination, and
other partner supported screening like Document Generation etc.
Key Transaction Dates for DBI
Order Management now allows customers to track order firmed date and actual
fulfillment date. Order firmed date can be defaulted. It is not available for update via the
User Interface or Order Import in this release. It can be updated via public APIs.
The Actual fulfillment date is populated by system when the actual fulfillment event
takes place, for example when a line is shipped or line is fulfilled for a
non-shippableitem.
These dates are used in Daily Business Intelligence (DBI) Reports.
Open Interface Tracking
Oracle Order Management has introduced the Open Interface Tracking form to allow
users to view the current status of the various XML and EDI electronic messages, as well
as Order Import. This feature also allows the user to drill down to relevant Workflow,
XML and Corrections information.

Order Import Key Change

This feature allows the customer to be included in the key that order import uses to
determine a unique order. It can be controlled via the profile option "OM: Unique Order

Source, Orig Sys Document Ref Combination For Each Customer" and allows orders
with the same reference information to be distinguished based on the Sold To customer.
Preview and Print Sales Documents
Oracle Order Management provides a flexible Preview and Print feature that allows users
to preview the sales agreement as it would appear for customer signing, and to print the
document. The document may or may not contain textual terms and conditions as part of
the agreement. The print and preview feature is available for blankets as well as sales
orders/quotes.
Publishing Plan Results to Oracle Order Management
In this release, Advance Supply Chain Planning can recommend and release warehouse,
date, and ship method changes for sales orders. Users can firm the warehouse on the sales
order to have planning system to honor the warehouse specified on the sales order. Order
Management
provides
three
ways
to
firm
the
sales
orders:
1. Based on an event. Users could choose to firm the line at scheduling, or when the line
is
interfaced
to
shipping,
or
not
at
all.
2. Through a seeded workflow process. A new workflow subprocess will hold the lines
until they are progressed. Once the lines are progressed, they are firmed. A new
concurrent program is provided for progressing lines waiting at this subprocess.
3. Using the Firm flag on the sales order line. Users can set the flag manually, or unfirm
the line.
Retroactive Billing
Order Management provides the Retrobilling Organizer form to identify order lines that
have previously been invoiced that may be subject to retroactive billing
due to price changes, a simple approval mechanism, and then the automatic generation of
credit memos (and occasionally invoices).
Simple Negotiation in Oracle Order Management
Sales orders and Blanket Sales Agreements can now include a workflow phase to support
the activities that typically occur within a negotiation process, such as an internal
approval and customer acceptance. A sales order in the negotiation phase will be referred
to as a Quote. This enables users to create and manage quotes during the negotiation
phase and transition the quote to a sales order, which will begin its fulfillment flow, after
completion of the negotiation.
Oracle Order Management has also introduced the Expiration Date for negotiated sales
orders. A Quote is an offer to do business and the validity of that offer is often limited to
a specific period. If the customer does not complete the negotiation by a specific point in
time, then the offer is liable for closure.

Scheduling Flexibility
The following scheduling parameters are offered to users, allowing users to control
various scheduling activities. Users can maintain current functionality without changing
the default values.
Whether a change in Request Date should reschedule the lines.
Whether a change in Ship Method should reschedule the lines.
How the Promise Date is used. A Promise Date can be defined as a static field, either the
first Request Date or the first Schedule Date. Other choices are making the Promise Date
dependent on the Request Date or the Ship Date. A fifth choice is setting the Promise
Date manually, i.e. by defaulting or manual entry.
Partial manual reservations. When reserving manually on the Sales Orders window or
using the Reservation Time Fence, you can choose whether or not to allow partial
reservations.
Control the behavior of the Latest Acceptable Date (LAD) for manual scheduling.
(System scheduling always honors the LAD.) For manual scheduling, you can choose to
ignore the LAD, and display a warning message but allow the scheduling process to go
through.
Versioning
Oracle Order Management has introduced Versioning to capture changes and updates
made to any transaction, which includes Sales Orders, Quotes, and Blanket Sales
Agreements. Creating and managing versions can be of great assistance during the
negotiation phase of any transaction and helpful when maintaining history throughout the
life of a Sales Order, Quote, and Blanket Sales Agreement.
XML Transactions
Change Sales Order
Oracle Order Management is able to generate and send an outbound OAG Change Sales
Order XML document in the following scenarios:
A change in status of XML sales orders from Pending to Accept. A change in ordered
quantity, unit selling price, or schedule ship date on booked XML sales orders, and
optionally putting the order line on hold to wait for a response from the buyer via Change
Purchase Order ..
Change Purchase Order
Order Management is able to consume the Change Purchase Order XML document from
the buyer to change a sales order in Order Management. Changes can include

cancellation, attribute updates, and line creation. Change Purchase Order can be sent
standalone or as a response to a Change Sales Order XML document.
Changed Features
Blanket Sales Agreements Enhancements
Oracle Order Management continues to enhance Blanket Sales Agreements (BSA) to
leverage common functionality including workflow, approvals, versioning, and
processing constraints as well as include BSA-specific functionality such as inline
pricing.
Configuration Date Effectivity Enhancements
As part of the increased flexibility provided to customers in handling the many dates used
in processing orders with configurations, customers can specify either the creation date of
the model line or the system date until booking for validation of item effectivity in new or
existing configurations. This feature is available for product configurator as well as the
Options window.
Credit Checking Enhancements
Order Management Payment Type definition can determine the inclusion or exclusion of
order lines when executing credit checking. Pre-payment amounts associated to the sales
order are now considered when validating customer credit limits.
Return lines can be included or excluded during credit checking execution based on your
credit check rule definition.
Enhanced Credit Exposure report to provide exposure information at any level in a party
hierarchy.
Display Choices for Freight Rating
When you choose the action Choose Ship Method from the Order tab or Lines tab, the
Display Freight Choices form opens. At the time of opening, Order Management calls
Transportation Execution by passing all the order lines to get shipment summary
information.Shipment Summary contains the number of shipments and Ship From, Ship
To, Weight, and Volume for each of the shipments.To view all the available ship methods,
cost, transit time, and charge, you must select a particular shipment and click Open.
When you click Open, Order Management calls Transportation Execution to get the
different ship methods, cost, and transit time.
Once Order Management gets the ship methods, cost, and transit time, the Pricing Engine
is called to convert the costs to charges for each of the ship method.

When you select the ship method click Apply, the OE_ORDER_LINES_ALL table is
updated with ship method and the freight charges are inserted into
OE_PRICE_ADJUSTMENTS table.
Drop Ship Across Sets of Books
Currently, drop ship lines can only be sourced from warehouses (suppliers) defined in the
same Operating Unit or Set of Books as the Operating Unit in which the customer sales
order is taken. Now we are providing the ability to drop-ship goods across Operating
Units, Legal Entities, and Sets of Books.
Drop Ship Change Management
Oracle Order Management has enhanced the drop shipment process by communicating
additional data elements from Oracle Order Management to Oracle Purchasing and then
to the end supplier, and automatically sending sales order changes to the purchase order
and then the supplier.
EDI Transactions Processing
To improve performance of EDI inbound Orders, the EDI acknowledgment API now only
writes column ids to the acknowledgment tables. The column values which are sent back
on the outbound EDI message are generated at a later stage via a deferred workflow
process. The workflow status can be verified by querying up the order in the new
Tracking window.
Fulfillment with Wait
Oracle Order Management has enhanced the Fulfillment Workflow activity to provide a
new seeded workflow sub-process Wait to Fulfill Line. Customers can add this subprocess before the existing defer_fulfillment and/or fulfill_line. The sub-process is
especially useful to hold non shippable order lines from getting fulfilled immediately
after order booking. Thus, user can change such order lines without facing system
constraints enabled at line fulfillment e.g. order line can now be canceled until the line is
progressed beyond Wait to Fulfill Line and fulfill line sub-processes. This sub-process
can also be used for shippable order lines.

Global Order Promising for ATO Configurations

Scheduling for ATO models is enhanced so that sourcing rules can be used to select a
warehouse for an ATO model. With this functionality, users will no longer need to specify
a warehouse for the ATO model.

High Volume Pricing

High Volume Order Processing (HVOP) functionality is enhanced to improve the
performance of pricing high volumes of order lines. HVOP pricing supports many
features, e.g. discounts, surcharges, freight and special charges, static or dynamic
formulas, and GSA pricing.
High Volume Shipping Interface
High Volume Order Processing (HVOP) functionality is enhanced to improve the
performance of the interface from Oracle Order Management to Oracle Shipping
Execution. Shipping to Order Management Interface after ship confirmation is also
enhanced to improve the performance of complete shipments. Complete shipments
include all order lines with shipped quantity same as ordered quantity in case of standard
items, In case of models and sets it means that shipped quantity should be same as
ordered quantity on all the lines in that model or set. This enhancement is useful for
orders taken with or without HVOP functionality.
Line Level Ship/Arrival Sets
Oracle Order Management has increased the choice to their customers of header level
Ship/Arrival Set functionality. The profile, OM: Assign new set for each line, provides
two alternatives:
Many businesses do not wish to create multiple shipments for a single order. The default
will be set to N thus creating ONE Ship/Arrival Set per order. As an example, if the
header level choice is Ship, then all successfully scheduled lines, will automatically go
into one Ship Set when created.
It is important for other businesses that a single line ship complete and multiple
shipments are allowed per order. By setting the profile to Y, the system will create a
unique Ship/Arrival Set for EACH line in an order as long as the line can be scheduled.
Multiple and Partial Payments
Oracle Order Management is enhanced to allow additional types of payment vehicles and
to allow specification of a payment at the line level. Also multiple prepayments can be
processed at the order header level, to provide support for down payments.

Order Management Parameters

The Oracle Order Management Parameters window is enhanced for greater flexibility.
Parameters can be functionally grouped, and users can define controls there as easily as
with profile options.
Override List Price
Oracle Order Management is enhanced to allow overriding of list price. This is controlled
by a system profile option "OM: List Price Override Privilege."
Order Import Enhancements
You can now specify whether a single-line queuing method should be used when
importing orders using multiple instances. This functionality is controlled by a concurrent
program parameter that is not displayed and the default behavior is to utilize the singleline queue. You also can now trim trailing blanks from the attributes they import. This
functionality is also controlled by a concurrent program parameter (displayed) and the
default behavior is to not do any trimming.
Pricing and Availability Enhancements
The Pricing & Availability window, that allows users to quickly check the price and/or
availability of an item without entering an order, is being enhanced to support the
following features:
Ability to take the item being priced and convert it into a quote or a sales order.
Additional search criteria, including demand class, line type as well as the ability to enter
ask for promotions and coupons.
Ability to do Pricing and Availability checks of ATO items.
Enhanced defaulting of attributes that can affect Pricing and Availability, including
demand class, item identifier type, order type, warehouse, and price list.
A new results tab to display Related Items, such as up-sell, cross-sell or substitute items,
and their price and availability. This tab allows the user to select the Up-Sell or CrossSell items from the Related Items region.
New sub-tab of Pricing results tab displays Additional Benefits. These are modifiers that
are applicable but that do not affect the selling price of the item that is being priced,
including terms substitution, promotional goods, other item discounts, item upgrade,
coupons, and accruals.

Display of modifier Price Breaks in addition to existing price list Price Breaks.
Ability to apply Manual Discounts to items whose price is being checked.
Ability to store a selected group of items being checked, so that they can all be quoted or
ordered at once.
Several new attributes, Item, Item Weight, Item Size, and Default Source type have been
added to the Item Information tab.
The Creation of an Order and Quote from this form can be secured through Function
Security.
Ability to Add Customer & Find Customer from Pricing/Availability.
Project Task Changes for Booked Orders
This enhancement benefits users of Oracle Project Manufacturing. Prior to this, once an
order line was booked, the user could not make any adjustments to the Project or Task
attached to the line. This restriction is lifted; allowing the user to make changes to the
Project or Task number further along in the order's life cycle.
Reservation Enhancements
The Reserve Order Program has been enhanced to support three reservation modes,
which are "Fair Share," "Percentage," and "Partial." In addition to this the program has
been enhanced to simulate the results so that you can view the results and make
corrections to the output before placing the actual reservation.
Service Termination
Order Management has enhanced the return flows to identify if prorated, full, or no credit
should be issued when extended warranties are terminated in service contracts on return
of a product. The RMA line corresponding to the product item is stamped with a value
that determines the credit behavior for the extended warranty lines based on a new
workflow
activity
added
in
Order
Management.
Also, if an RMA line doesn't qualify the credit behavior for service lines, Service
Contracts determine the credit behavior based on the Global Contracts Defaults setup.
The Credit Option Rule in Global Contracts Defaults will determine if service lines
qualifies for credit and what percentage of credit (prorated vs. full vs. none) is issued. If
the Credit option rule is not specified in Global Contracts Defaults, then Service
Contracts will honor the existing "OKS: Raise Credit Memo for IB Instance Termination"
profile and prorates the credit based on the return date.

Purge
Oracle Order Management has enhanced the purge criteria to include negotiated orders
that are no longer needed within the operational requirements of the order taken and order
administration.
Copy
Oracle Order Management has enhanced the copy function to allow the creation of quotes
based on an existing quote or sales order using the Copy Orders feature.
XML Transactions
Process Purchase Order (RosettaNet 3A4)
The Process Purchase Order (RosettaNet 3A4) xml message now supports the Pending
status. The pending status can be assigned at the Order level or at the Order Line level.
Updates in SCM FP.J RUP1
New Features
Exception Management
Changes have been made to the Order Management Messaging feature to enable you to
view messages logged when a workflow activity fails due to an exception. Each message
logged has an associated status (seeded values are Open or Closed).
The Sales Orders, Blanket Sales Agreement, and Open Interface Tracking windows
provide direct navigation to Open errors, and enable you to retry a workflow activity that
failed. If the retry is successful, Open messages are automatically closed.
A new workflow error handling process generates an Order Management-specific
notification that uses standard workflow functionality to enable the recipient to retry an
activity
in
error.
By going through successive iterations of fixing errors and retries, you can identify and
fix all the issues that are causing an activity to error out. This feature also provides a
record of errors and corresponding diagnostic information for Oracle Support in case you
are unable to fix the problem.

Changed Features
End Customers
The following features enhance End Customer functionality:
Automatic Account Creation for End Customer
You can automatically create an account for the End Customer.
Closed Order Import is supported for End Customer.
You can import Closed Orders with End Customer attributes.
Mass Change for End Customer Attributes
You can use mass change for End Customer attributes.
HVOP Support for End Customer Attributes
You can import end customer attributes using HVOP, which is bulk-enabled for high
volume users. There is EDI support for End Customer attributes with HVOP.
Install Base fields: IB Location, IB Current Location, and Owner Were Added
You can import Open and Closed Orders with these fields.
Earlier IB Owner, IB Installed Location, and IB Current Location fields were working as
code fields, for example you must supply the values like SOLD_TO, END_CUSTOMER,
SHIP_To_LOCATION etc. Now these fields are working as values columns and new
code fields have been added like IB Owner Code etc.
Print Preview Feature for End Customer Attributes.
End Customer attributes are available in Print Preview feature.
Reporting End Customer Information
The Comprehensive Order Detail report displays the End Customer, Address, and Contact
at the line level.
OIP Displays the Name and Address of the End Customer
Within Order Information Portal (OIP) you can view the name and address of the End
Customer, as captured at the time of processing the order, at both at the header and line
levels.
OIP Displays the Contact for the End Customer
You can view the contact for the End Customer, when captured at the time of processing
the order, at both the header and line level.
OIP Displays End Customer Attributes for the Installed Base
You can view the Owner, Installed at Location, and Current Location in OIP - at both the
header and line level.

OIP Displays Individual DFF Segments

Within OIP you can view the contents of Descriptive Flexfields (DFF) fields, with userdefined labels.
Sort by End Customer
Using OIP, you can sort query results by End Customer.
Electronic Messaging Support for End Customer
The inbound Process Purchase Order (RosettaNet 3A4) and Change Purchase Order
(RosettaNet 3A8) XML messages support end customer attributes.
The 850 Purchase Order Inbound and 860 Purchase Order Change Inbound as well as the
outbound 855 Purchase Order Acknowledgment and 865 Purchase Order Change
Acknowledgment EDI transactions also support end customer attributes.
EDI and XML Support
With standard order import, you can import End Customer attributes using EDI or XML.
Order Management is supporting End Customer functionality in this release. This feature
enables you to specify the End Customer information on a sales order. If you are using
EDI transactions (850/855/860/865/875) and want to use End Customer functionality
through these EDI transactions, please apply patch 4147509.
After applying the patch 4147509, you should perform seed data reconciliation.
Additional details are available in the README of the patch 4147509.
Enhancements around Authoring and Negotiating Contract Terms
Microsoft Word Integration
If the Oracle Sales Contracts option is licensed, Oracle Order Management users can
download contract terms from a blanket sales agreement, quote, or sales order into a
Microsoft Word document. In addition to redlining, users can take advantage of other
word processor features such as text formatting and spell checking. After changes are
made, the document can be uploaded and stored as either an attachment or used as a basis
to update the structured terms. If the attachment is marked as the source of contract
terms, the Preview and Print functionality merges in content from the attached document
and the business document in PDF.
Contact Deviations Report
With the Sales Contracts option, Order Management users have the option to attach the
system generated deviations report or their own document to the approval notification
when a blanket sales agreement or quote is submitted for approval.