EBS 122 Cum RCD OM

ORACLE E-BUSINESS SUITE
RELEASE CONTENT DOCUMENT
Order Management and Contracts

Releases 12.1 and 12.2 (inclusive of 12.0.2 – 12.2.8)
Prepared by Oracle E-Business Suite Product Development
Last Updated: April 20, 2018
Copyright © 2011, 2018, Oracle and/or its affiliates. All rights reserved.
Table of Contents
1. Disclaimer 1
2. Introduction 2
2.1. Purpose of Document 2
3. New and Changed Features in Order Management 3
3.1. Oracle Advanced Pricing 3
3.1.1. Release 12.1.1 3
3.1.1.1. Formula for Price Break Lines Based on Unit Price Application Method 3
3.1.2. Release 12.1.2 3
3.1.2.1. Pricing Engine Performance Enhancements 3
3.1.2.2. Purchasing Order Pricing Enhancements 3
3.1.3. Release 12.2 3
3.1.3.1. Service Item Support in Promotional Modifiers 3
3.1.3.2. Support of Non-Continuous Price Breaks 4
3.2. Oracle Configurator 4
3.2.1. Release 12.1.1 4
Overview: Fusion Configurator Engine 4
3.2.1.1. Numeric Handling 4
3.2.1.2. Improved Defaulting 5
3.2.1.3. Auto-instantiation 5
3.2.1.4. Auto-completion 5
3.2.2. Release 12.2.5 5
3.2.2.1. Query-based Rules 5
3.3. Oracle Order Management 5
3.3.1. Release 12.1.1 5
3.3.1.1. Item Orderability 5
3.3.1.2. Credit Over-shipped Quantity for Referenced RMA 6
3.3.1.3. Support Decimal Quantity in BSA UI 6
3.3.1.4. Improved Install Base Search While Ordering Services 6
3.3.1.5. Delayed Scheduling 6
3.3.1.6. Enhanced Workflow Activity Hold 7
3.3.1.7. Customer PO-based Search in Scheduling Organizer 7
3.3.1.8. Visibility to Latest Configuration Till Picking 7
3.3.1.9. Line Level Credit Check Enhancement 7
3.3.1.10. Post Booking Item Substitution 7
3.3.1.11. Defer Split for Configurations 7
3.3.1.12. Internal Requisitions/Internal Sales Order Change Management 7
3.3.1.13. Order Management Productivity Enhancements 8
3.3.1.14. Sales Agreements Enhancements 9
3.3.1.15. Seeded Return Line Workflows 9
3.3.2. Release 12.1.2 9
3.3.2.1. AIA Order To Cash 2.5 Enhancements 9
3.3.2.2. Workflow Performance Enhancements 10
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document ii
3.3.2.3. Supply Chain Web Services – Order Management 10
3.3.3. Release 12.1.3 10
3.3.3.1. International Trade Management Adapter Enhancements for Global Trade Management (GTM) 10
3.3.4. Release 12.2 11
3.3.4.1. Support for Assemble-To-Order (ATO) Items in Pick-To-Order (PTO) Models and Kits 11
3.3.4.2. Order Information Portal (OIP) Enhancements 11
3.3.4.3. Tax Calculation on Freight Charges 12
3.3.4.4. Credit Tolerance for Honoring Manually Released Credit Check Holds 12
3.3.4.5. Support for Credit Hold Based on Bill To Customer 12
3.3.4.6. Selling Services Enhancements 12
3.3.4.7. Support for Service as Promotional Goods 13
3.3.4.8. User Defined Attributes (UDA) 14
3.3.4.9. Scheduling Enhancements 14
3.3.4.10. Support for Advanced Catch Weight 15
3.3.4.11. Integration with Oracle Approvals Management (AME) 16
3.3.4.12. Credit Card Authorization Reversal 16
3.3.4.13. Additional Business Events 16
3.3.5. Release 12.2.3 19
3.3.5.1. Support for “Online” Mode for Line Level Credit Checking 19
3.3.5.2. Consider “Assemble To Order” Flag at Warehouse Level 19
3.3.5.3. Scheduling Enhancements 20
3.3.6. Release 12.2.4 22
3.3.6.1. HTML User Interface for Order Management 22
3.3.6.2. Item Substitution on Internal Sales Orders 22
3.3.6.3. Enabling Configurator for Return Orders (RMA) 22
3.3.6.4. Order Management Support for Yard Management System 23
3.3.6.5. Performance Improvements - Bulk Processing 23
3.3.7. Release 12.2.5 24
3.3.7.1. Enhanced Gross Margin Calculations 24
3.3.7.2. Subscription Ordering Enhancements 24
3.3.7.3. Order Management Support for Serial Tagging at Sales Order Pick 25
3.3.7.4. Performance Improvements in Scheduling Process and Schedule Order Program 25
3.3.8. Release 12.2.6 27
3.3.8.1. Recurring Billing 27
3.3.8.2. Synchronization of Promise Date changes on Purchase Order with Drop Ship Sales Order 27
3.3.8.3. Performance Improvements in Process Order API 28
3.3.8.4. Performance Improvements in Scheduling Process and Schedule Order Program 28
3.3.8.5. Performance Improvements in Order Import Program 28
3.3.9. Release 12.2.7 29
3.3.9.1. Milestone Billing 29
3.3.9.2. Schedule Orders Enhancements 29
3.3.9.3. Manual Item Substitution Post Booking 30
3.3.9.4. REST Web Services Enhancements 30
3.3.10. Release 12.2.8 31
3.3.10.1. Enhancements to Integration with Oracle Approvals Management (AME) 31
3.3.10.2. Item Orderability Enhancements 31
3.4. Oracle Order Management Information Discovery 34
3.4.1. Release V4 34
3.4.2.1. Customer Explorer 34
3.4.3.1. Order 360 View 35
3.4.3.2. Customer Explorer 35
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iii
3.4.4.1. Advanced Search Capabilities 35
3.4.4.2. Performance improvement of Graphs 36
3.5. Oracle Mobile Sales Orders for Oracle E-Business Suite 36
3.5.1. Mobile Release 1.0 36
3.5.1.1. Accessibility Improvements 36
3.5.1.2. Mobile Application Foundation Updates 36
3.5.2.1. Android Support 37
3.5.2.1. Mobile Foundation Release 3.0 Updates 37
3.5.3.1. Enhanced Line Details Page Layout 37
3.5.3.2. Added Adjustments Details Pages for Order Header and Line Adjustments 37
3.5.3.3. Added Default Content in Emails 37
3.5.3.4. Translation Support 37
3.5.4.1. View Invoice for the selected Order 38
3.6. Oracle iStore 38
3.6.1. Overview 38
3.6.2. Release 12.1.2 38
3.6.2.1. Product Comparison 38
3.6.2.2. Automated Password Generation for Secondary Users 39
3.6.2.3. Automated Assignment of Roles and Permissions 39
3.6.2.4. Check for Duplicate Contacts 39
3.6.2.5. Payment Book Enhancements 39
3.6.2.6. Copy Product Content Components 40
3.6.3. Release 12.1.3 40
3.6.3.1. One-Click Shopping List Management 40
3.6.3.2. Product Detail Pop-up 40
3.6.3.3. Add To Cart Navigation 40
3.6.4. Release 12.1.3+ 41
3.6.4.1. Multi-customer Access 41
3.6.4.2. Direct Item Entry Enhancement 41
3.6.4.3. Mandatory Purchase Order Number 41
3.6.4.4. Shopping Cart Purge 42
3.6.5. Release 12.2 42
3.6.5.1. Carousel Views for Related Products 42
3.6.6. Release 12.2.4 42
3.6.6.1. Shopping Cart Purge 42
3.6.7. Release 12.2.5 42
3.6.7.1. Address Search Enhancement 42
3.6.7.2. Line Level Promotions 42
3.6.8. Release 12.2.7 42
3.6.8.1. Order Type for a Specialty Site 42
3.6.8.2. Email Notification Style 43
3.6.9. Release 12.2.8 43
3.6.9.1. Promotion Code Enhancement 43
3.6.9.2. Copy Prior Order Items 43
3.7. Oracle iStore Information Discovery 43
3.7.1. Overview 43
3.7.2. V6 44
3.7.2.1. Enhanced iStore Search 44
3.7.2.2. Customer and Cross Reference Part Number Search 44
3.7.2.3. Price and Price Range Filter 44
3.7.2.4. Multiple Search Result Views 44
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iv
3.7.2.5. Product Comparisons 44
3.7.3. V8 45
3.7.3.1. Enhanced Product Catalog Search Capabilities 45
3.8. Oracle Shipping 45
3.8.1. Release 12.1.1 45
3.8.1.1. Defer Planned Shipment Interface 45
3.8.1.2. Allow Incremental Shipments for Over-shipment and Under-shipment Tolerances 45
3.8.2. Release 12.1.3 45
3.8.2.1. Fulfillment Batches for Distributed Warehouse Management System 45
3.8.3. Release 12.2 46
3.8.3.1. Integration to 3PLs or 3rd Party Distributed Warehouse Management System 46
3.9. Oracle Supply Chain Event Management 46
3.9.1. Release 12.1.3 46
3.9.1.1. Order Fulfillment and Spare Parts Order Templates 46
3.9.2. Release 12.2.5 46
3.9.2.1. Back to Back and Procure to Pay Templates 46
3.10. Oracle Installed Base 47
3.10.1. Overview 47
3.10.2. Release 12.2.4 47
3.10.2.1. Option to track only Customer-owned products using Oracle Installed Base 47
3.10.3. Release 12.2.5 47
3.10.3.1. Tracking of Customer Install Base items 47
3.10.3.2. Install Base Transaction performance improvements 48
3.10.3.3. Serial Tagging at Sales Order Pick support 48
3.11. Oracle Installed Base Information Discovery 48
3.11.1. Overview 48
3.11.2. Release V4 48
3.11.2.1. Search by Extended Product Attributes 48
3.11.2.2. Execute ‘Related Products’ Search 48
3.11.2.3. Improved Drill-down to Product Configuration 49
3.11.2.4. Identify Installed Base by Geography 49
3.11.2.5. Track Customer Product Metrics 49
3.11.3. Release V5 49
3.11.3.1. User-Definable DFF Search 49
4. New and Changed Features in Contracts 50
4.1. Oracle Sales Contracts 50
4.1.1. Release 12.1.1 50
4.1.1.1. Secure Enterprise Search 50
4.1.1.2. Structured Terms Authoring for Repository Contracts 50
4.1.2. Release 12.1.2 50
4.1.2.1. Author Individual Clauses in Microsoft Word 50
4.1.3. Release 12.1.3+ 51
4.1.3.1. Templates, Rules, Questions and Constants APIs 51
4.1.3.2. Contract Terms and Conditions Migration API 51
4.1.3.3. Contract Expert Enhancements 51
4.1.3.4. Enhancements MS Word Synchronization 52
4.1.3.5. Apply Multiple Templates to a Sales Document 52
4.1.3.6. Multi Row Variables 52
4.1.3.7. Deviation Report for Repository Contracts 52
4.1.3.8. Clause Analysis for Repository Contracts 52
4.1.3.9. Contract Usability Enhancements 53
4.1.3.10. Contract Expert Performance Improvements 53
4.1.3.11. Contract Expert History 53
4.1.3.12. Delete Multiple Clauses, Sections and Deliverables 53
4.1.3.13. Purge Process for Repository Contracts 53
4.1.4. Release 12.2 54
4.1.4.1. Repository Contracts Enhancements 54
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document v
4.1.4.2. UDA support for Deliverables 54
4.1.4.3. MS Word 2010 Certification 54
4.1.5. Release 12.2.4 54
4.1.5.1. Repository Contracts Printing Enhancement 54
4.1.6. Release 12.2.5 54
4.1.6.1. Updating UDA on Approved Contracts 54
4.2. Oracle Service Contracts 54
4.2.1. Release 12.1.1 54
4.2.1.1. Service Contract Import Program 54
4.2.2. Release 12.1.3+ 55
4.2.2.1. Service Contract Renewal Performance Enhancements 55
4.2.2.2. Performance Enhancements to Main Billing Program for Usage Contracts 55
4.2.2.3. Mass Update Tool 55
4.2.2.4. Prevent Deletion of Line/Sub line during Contracts Renewal 56
4.2.2.5. Carry Over Self-Service Decline Code onto Service Contract Cancellation Reason 56
4.2.2.6. Revalue Contract during Change in Currency 56
4.2.2.7. Specify Cc E-mail Addresses during Quote and Reminders 56
4.2.2.8. Selective Update of Warranty Contracts upon IB Transfer of Ownership 56
4.2.2.9. Re-price on Renewal Consolidation 56
4.2.2.10. Flexible Invoice Text Defaulting 56
4.2.2.11. Service Contracts Usability Enhancements 56
4.2.2.12. Merge Assets across Contracts 57
4.2.2.13. Drive Contract Coverage by Severity 58
4.2.2.14. Control Generation of Invoice 58
4.2.2.15. Calculate Estimated Tax with Higher Accuracy 58
4.2.2.16. Close Request for Assistance 58
4.2.2.17. Withdrawal of Published Quotes 59
4.2.2.18. Manage Cancellation Risk and Forecast Amount 59
4.2.2.19. Cancellation Code 59
4.2.3. Release 12.2 59
4.2.3.1. Solution Ordering 59
4.2.4. Release 12.2.4 60
4.2.4.1. Service Contracts Public APIs 60
4.2.5. Release 12.2.5 60
4.2.5.1. Enhanced User Interfaces 60
4.2.5.2. Enhancements to Subscription Contracts 60
4.2.6. Release 12.2.7 61
4.2.6.1. Enhancements to Usage Billing 61
4.3. Contract Renewal Command Center 61
4.3.1. Overview 61
4.3.2. V5 61
4.3.2.1. Identify Renewal Exceptions and Manage Renewals Work Queue 62
4.3.2.2. Monitor Renewal Performance Metrics 62
4.3.2.3. Continuously Monitor and Improve Customer Service Experience 62
4.3.2.4. Identify Early Signs of Risks and Strategize Their Remediation 62
4.3.2.5. Monitor Service Revenue Leakage and Strategize Their Mitigation 62
4.3.3. V6 62
4.3.3.1. Customer Management 63
4.3.3.2. Portfolio Management 63
4.3.3.3. Vendor Management 63
4.3.3.4. Contracts (Finance and Service) 63
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document vi
1. Disclaimer
This Release Content Document (RCD) describes product features that are proposed for
the specified releases of the Oracle E-Business Suite. This document describes new or
changed functionality only. Existing functionality from prior releases is not described. It
is intended solely to help you assess the business benefits of upgrading to the specified
release of the Oracle E-Business Suite.
This document in any form, software or printed matter, contains proprietary information
that is the exclusive property of Oracle. Your access to and use of this confidential
material is subject to the terms and conditions of your Oracle Software License and
Service Agreement, which has been executed and with which you agree to comply. This
document and information contained herein may not be disclosed, copied, reproduced or
distributed to anyone outside Oracle without prior written consent of Oracle. This
document is not part of your license agreement nor can it be incorporated into any
contractual agreement with Oracle or its subsidiaries or affiliates.
This document is for informational purposes only and is intended solely to assist you in
planning for the implementation and upgrade of the product features described. It is not a
commitment to deliver any material, code, or functionality, and should not be relied upon
in making purchasing decisions. The development, release, and timing of any features or
functionality described in this document remains at the sole discretion of Oracle.
Due to the nature of the product architecture, it may not be possible to safely include all
features described in this document without risking significant destabilization of the code.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Purpose of Document 1
2. Introduction
2.1. Purpose of Document

This Release Content Document (RCD) communicates information about new or changed
functionality introduced in Oracle E-Business Suite Releases 12.1 and 12.2, and in
subsequent Release Update Packs (RUPs) and off-cycle patches. For your convenience,
it also includes new or changed functionality introduced in the RUPs for Release 12,
including 12.0.2 through 12.2.8.
The features and enhancements described in this document are grouped by product, and
then by the release in which they first became available, for example, “Release 12.1.1”.
Features released in an off-cycle patch have a special designation – for example, a feature
released after 12.1.1, but before 12.1.2, is designated as “Release 12.1.1+”.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Purpose of Document 2
3. New and Changed Features in Order Management
3.1. Oracle Advanced Pricing

3.1.1. Release 12.1.1
3.1.1.1. Formula for Price Break Lines Based on Unit Price Application Method
Currently, a dynamic pricing formula is not supported for Price Break Lines in Price
Lists. As part of the 12.1.1 release, the formula will be supported for Price Break Lines
with Application method as ‘Unit Price’. Users can now have dynamic pricing
calculations for the break lines. However this would not be supported for the Application
method ‘Block Price.’
3.1.2. Release 12.1.2
3.1.2.1. Pricing Engine Performance Enhancements

In this release, the performance of Advanced Pricing Engine has been enhanced by using
a pattern-based search algorithm which normalizes all setup combinations in to a single
hashkey. This feature is optional and enabled through a profile called QP: Pattern Search.
In order to enable this feature, after turning on the profile, users will need to run a one-
time pattern upgrade concurrent program called QP Pattern Upgrade to upgrade all
existing setups to the new pattern format. All subsequent work in the Advanced Pricing
product will leverage this new and faster approach to price determination.
3.1.2.2. Purchasing Order Pricing Enhancements

Oracle Purchasing has extended its integration with Advanced Pricing to provide greater
granularity and flexibility in pricing orders and agreements. The extended integration
also provides greater transparency to the means by which a price has been determined for
orders and agreements.
Oracle Purchasing users can now:
• View the pricing modifier information for a Purchase Order and/or Global Blanket
Purchase Agreement line and view the pre-calculated price adjustments applied by
the pricing engine
• Manually enter a price modifier, change a modifier rate, and recalculate the price
• Query existing manual modifiers and apply them to a Purchase Order and/or Global
Blanket Purchase Agreement unit price
• Change the modifier rate and apply changes to PO or Global Blanket Purchase
Agreement Line.
These new features provide an accurate view of pricing information to the buyer,
increased flexibility for buyers to price an order and streamlined supplier communication
on prices.
3.1.3. Release 12.2
3.1.3.1. Service Item Support in Promotional Modifiers

In this release, service items can be used as the “get” item in promotional modifiers. It
has become a general business practice to give the service free of cost or at a discounted
price to consumers when they buy a high-end-consumer good. Users can now setup
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Advanced Pricing 3
promotional modifiers where a service item gets added automatically when a certain
finished good is added to the order. This helps in cutting down order creation time, adds
efficiency and accuracy of order creator, and enables companies to implement service
item pricing/ordering promotional strategies.
To achieve this, users need to provide the service item as a get product in the promotional
modifier setup.
3.1.3.2. Support of Non-Continuous Price Breaks

Advanced Pricing has added this enhancement to allow gaps in the setup of price breaks.
Businesses sometimes want to provide discounts for only certain tiers and want to keep
gaps in the tiers. This is common where manufacturers keep readymade packages for
certain quantities and if users order anything other than that, it’s an overhead for
manufacturers to package based on user’s order. For these orders, manufacturers don’t
give any discount. For example, users can now create price breaks to have tiers from10
to 20 and then 30 to 40 with the gap of between 20 to 30. Users can now enter the tiers
for what they are interested in discounting, without worrying about entering the 0
discounted tiers.
This enhancement also allows the tier value to start from any positive value other
than 0.
3.2. Oracle Configurator

3.2.1. Release 12.1.1
Overview: Fusion Configurator Engine
Enterprises want to leverage constraint-based technology within their product
configuration deployments to reduce the cost of ownership and increase user adoption.
With the release of an enhanced constraint-based engine, Oracle Configurator meets this
need and continues to be strategically placed to lead in the configuration marketplace.
Various aspects of constraint-based technology provide particular business benefits
which are highlighted in the new Fusion Configurator Engine in this first release. The
robust constraint-based technology reduces time and cost for development and
maintenance of configuration solutions through an easier to maintain architecture that
inherently eliminates current engine limitations.
This release includes a superior ownership experience as a result of improved and
expanded features. The model developer can leverage improved numeric handling and
defaulting, as well as the new auto-instantiation, which automatically creates product
structure. More feedback is provided to the end user during a configuration session and
the end user can even choose to have a configuration completed based on previously
defined preferences.
3.2.1.1. Numeric Handling

The improvements in numeric handling create a configuration session that is easier to use
and provides more feedback. The allowable range for numeric inputs is now dynamically
displayed, resulting in fewer contradictions for the end user and an improved
configuration experience. Since constraint technology employs the propagation of
domains, in which constraints are inherently bidirectional, rules now propagate the most
information possible during selection and Auto-completion.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Configurator 4
3.2.1.2. Improved Defaulting
Defaults are more flexible than ever before since any constraint can now be defined as a
default. Additionally, modelers can define strategies about how to explore a specific
domain by default. For example, when the weight of a configured product is evaluated
during a configuration session, a default can be incorporated so that the strategy used
attempts to find a solution that has the lowest weight. Defaults can also be prioritized or
ordered so they are executed in a sequence defined by the modeler. For example, a
model with a weight and a size may have two defaults, one to find the lowest weight and
another to find the lowest size. Inherently the sequence of this strategy will affect the
outcome. However, the modeler can order the defaults so the strategy may be set to
evaluate size before weight.
3.2.1.3. Auto-instantiation
The new Auto-instantiation feature provides the ability for component structure to be
automatically created by constraints when required for a solution. In previous releases
instantiation was initiated through a click from the end user or accomplished through a
Configurator Extension. Now instantiation can be automatic and based on constraints, as
part of the model, without Configurator Extensions, making it much easier to model
complex system configurations.
3.2.1.4. Auto-completion
With the new Fusion Configurator Engine, partially completed configurations can be
completed automatically for the end user. The Auto-completion is based not only on end
user inputs but on modeler-defined defaults and search strategies as well. The modeler
has the option to define search strategies that are used in the Auto-completion to refine
the solution. However, even with no predefined strategies from the modeler and little
input from the end user, the Fusion Configurator Engine can efficiently find a solution
using engine implicit strategies.
3.2.2. Release 12.2.5
3.2.2.1. Query-based Rules

Customers with very large option classes need a way to more efficiently model and
update these option classes when used in an Oracle Configurator model. With this
release, a new rule type, called Query-based Rules, is introduced to meet this need. With
Query-based Rules parameters established during runtime are used to query an external
data source. The result of the query is returned and used to create the valid configuration.
Oracle Configurator customers with very large option classes composed of frequently
changing items, for example, can leverage Query-based Rules to include a specific item
in the configuration that had not been previously defined in the model. This new rule
type can provide customers with increased flexibility in model design, reduce model size,
and improve overall performance
3.3. Oracle Order Management

3.3.1. Release 12.1.1
3.3.1.1. 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. For
example, Customer A may purchase all items except for repair parts and promotional
items. Alternately, Customer B buys only repair parts from you.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 5
This new feature from Order Management provides users with an easy way to define
orderable products, based on exceptions defined in the Item Orderability rules. It would
be possible to apply Orderable Products business rules to items or Item Categories
defined for an organization. Based on the rules defined in the Orderability UI, the user
would be able to restrict the Items that can be ordered from the Sales Order and Quick
Sales Order form. Flexibility is provided to the users for defining Orderability rules either
at the Customer Class level or at the “Sold-to” Customer level.
3.3.1.2. Credit Over-shipped Quantity for Referenced RMA

With the existing functionality in Order Management, users can book an RMA for a
quantity based on the ordered Quantity. Businesses have requirements to book RMA’s
based on shipped quantities, especially in the case of over-shipments, in addition to the
current provision based on ordered quantities. In Release 12.1.1, users are provided with
an additional option of raising RMAs based on the shipped quantity, if the Invoicing
basis is set to ship quantity. For scenarios where the Profile option is based on Ordered
Quantity, the existing behavior for RMA will continue.
Additionally, two more seeded line level return workflow types have been provided to
cater to business scenarios of “Return with Receipt with No Credit” and “Return with
Receipt and Approval with No Credit”.
3.3.1.3. Support Decimal Quantity in BSA UI

This feature provides the flexibility to enter decimal quantities in Blanket Sales
Agreements. This flexibility will be at par with the capability currently provided in Sales
Order and Quick Sales order screens.
3.3.1.4. Improved Install Base Search While Ordering Services

With the existing functionality in Order Management, users can choose instances in
"Customer Product reference" LOV on Sales Order Form only for the “Sold to”
customers at the Header Level. With this new enhancement in Release 12.1.1, users can
choose instances of products stored in the Installed Base repository in "Customer Product
reference" LOV for related customers also in addition to the "Sold to"
customer. Similarly, you can refer to sales orders of related customers, while entering a
service line on an order.
3.3.1.5. Delayed Scheduling

In the existing “Auto Schedule” functionality in Order Management for Standard lines,
there are scenarios that might lead to data discrepancy between OM and GOP Demand.
The Delayed Scheduling feature in Release 12.1.1 refers to enhancing the “Auto
Schedule” feature in Order Management by introducing an additional option to users
when they choose to Auto Schedule. A new profile option, called, “OM: Delay
Scheduling”, has been introduced for this feature. This new profile option is dependent
on the value of the profile “OM: Autoschedule” being set to value “Yes”. You set the
value of the profile option, “OM: Delay Scheduling” and “OM: Autoschedule” to “Yes”
to enable this feature. Enabling this feature will ensure that GOP calls will be made only
when user actually saves the changes and eliminates the data discrepancy between OM
and GOP Demand.
This will also enhance the overall performance of the Sales Order, as we will make only
one GOP call at the time of saving rather than individual GOP calls for each Line. This
will bring a lot of performance improvement especially if Planning is on a different
server.
3.3.1.6. Enhanced Workflow Activity Hold
With the existing functionality of Holds in Order Management, the workflow activity
hold gets applied to all open records, irrespective of the current workflow status. For
instance, a ‘picking activity hold’ gets applied on the record even if it has already passed
the ‘picking activity’. With Release 12.1.1, the hold gets applied only on valid records,
which have either not reached that specific workflow activity or not in the completed
status.
3.3.1.7. Customer PO-based Search in Scheduling Organizer

The Customer PO field which was not previously available on the Scheduling Order
Organizer form is now available in Release 12.1.1. Additionally, partial value search
capability is provided for the Customer PO number field in both Order/Scheduling
Organizer forms. When executing a search with the partial Customer PO value, all
orders/lines that match the search criteria will be displayed.
3.3.1.8. Visibility to Latest Configuration Till Picking

In most business scenarios, there is time lag between Booking and Picking/Shipping of
configurations. In some cases during this time lag, the BOM definition itself gets changed
due to some business reasons, and therefore the Model on the sales order needs to be re-
configured. In such scenarios, a user expects that the latest/current BOM definition be
visible to them in the Configurator Window at the time of re-configuration. With the
current functionality, if the BOM definition of Model items gets changed after Booking,
users were not able to view latest definition of BOM in Configurator window from Sales
Order. In Release 12.1.1, 'OM: Configuration Effective Dates' profile under the OM
system parameters are enhanced by providing a new value of 'System Date Till Pick
Release' in addition to the existing List of Values. This will help users get visibility of the
latest/current components of Model Items in Configurator Window even after Booking of
Sales Order (but before Picking/Shipping) so that Users can re-configure their Model
Items.
3.3.1.9. Line Level Credit Check Enhancement

In Release 12.1.1, the line level credit checking has been enhanced to pick the order lines
within an order such that the credit exposure of the picked lines is within the credit limit.
3.3.1.10. Post Booking Item Substitution

In Release 12.1.1, 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
ASCP Planner’s Workbench (loop-back functionality) till the line is pick-released.
3.3.1.11. Defer Split for Configurations

In Release 12.1.1, order line split for models can be done in concurrent mode so that
users don’t have to wait for the split action to complete. While splitting an order line for a
configuration, users will have an option to select a checkbox if it’s needed to defer the
split process. If this option is selected, then system will submit a concurrent request to
split the order line and in the mean time users can continue with other activities on the
sales order.
3.3.1.12. Internal Requisitions/Internal Sales Order Change Management

In Release 12.1.1, internal order processing has been enhanced to offer additional and
better-coordinated change management capabilities. Internal requisition and internal sales
order change management allows the requester or the shipping organization to change the
date, change the quantity, or cancel internal transfer requests. All of these changes will
now be visible throughout planning, purchasing and order fulfillment. After an internal
requisition has been approved and before the internal sales order line status disallows any
more changes, the requester can ask to change the internal requisition, which will initiate
a reapproval workflow and log the change history. Once the change request has been
approved, affected users will be notified. Planners will also be able to change the need-
by date or cancel internal requisitions in the Planner's Workbench. When the shipping
organization cancels or makes changes to the scheduled ship date or quantity on an
internal sales order, those changes will be automatically cascaded to the internal
requisition and visible to planning as well.
• Quantity and Schedule Ship/Arrival Date changes on the Internal Sales Order
line will be automatically propagated to the Internal Requisition and vice versa.
Cascading of date is optionally controlled through a profile “POR: Sync up
Need by date on IR with OM”
• Cancellation of an Internal Sales Order/Line will automatically cancel the
corresponding Internal Requisition/Line and vice versa.
• You will be able to view intercompany invoices for a sales order, from the quick
sales order form.
• You’ll also be able to create internal sales orders with different order types.
Defaulting rules in order management can be used to default appropriate internal
order types.
• The urgent flag on the internal requisition line will flow onto the internal sales
order line as the shipment priority, based on the profile option “POR: Urgent
Flag on Int Req maps to Shipping Priority”
Additionally, please refer to the RCD of Purchasing/iProcurement for more information
on this capability.
3.3.1.13. Order Management Productivity Enhancements

In Release 12.1.1, the following new capabilities offer the ability to increase productivity
while entering and managing sales orders:
• The functionality of the quick sales order form has been matched with the regular
sales order form. Mass change and scheduling organizer capabilities are now
available with the Quick Sales Order.
• Mass Change capability in Order Management is also enhanced to support
cascading of order header attribute changes to the order lines.
• Copy capability is enhanced to support copying of orders across operating units,
creating multiple copies of an order in one operation, copying ship sets and
fulfillment sets to new orders. The copy capability automatically populates the
current order number value, in the “Get Header Level info from” field, on the
copy form. There is also a new option, in the copy form, to directly navigate to
the newly created order after the copy operation.
• New attributes for hold source criteria have been introduced. They are Project,
Task, Order type, Line type, Price List, Creation Date, Created By, Sales
Channel, Payment Type, Shipping Method, Deliver to location, Source Type,
Top Model, Option Item, Payment Term and Order Currency. Also, a single hold
source can be used to apply holds across multiple operating units.
• Order header/line workflows, on hold, will automatically restart, when the hold is
released, eliminating the need to manually progress the workflows. This
enhancement is implemented as an option in holds setup.
• High volume order processing (HVOP) capability is enhanced to support import
of orders with taxes and configurations.
• Additional support for Try & Buy scenarios. You can, optionally, update the
Customer PO Number on an Order Line even after it has been ship confirmed,
but not invoiced. The updated Customer PO Number will be printed on the
customer Invoice document, making the reconciliation process for the end
customer smooth and error free. This feature is achieved through the relaxation
of the seeded processing constraint.
• A public API has been provided for re-pricing an order.
• A new concurrent program for batch re-pricing is introduced with parameters,
which could be submitted and scheduled for repricing multiple orders/lines.
3.3.1.14. Sales Agreements Enhancements

In Release 12.1.1, a public API to create sales agreements (a.k.a BSA or blanket sales
agreements) is being introduced. Support for related customers on a sales agreement is
also being introduced. Users can now specify 'Ship to' and 'Bill to' related customers on a
sales agreement.
3.3.1.15. Seeded Return Line Workflows

In Release 12.1.1, two additional order line workflows are seeded for addressing business
requirement of returns without credit:
• Return with Receipt – No Credit: Return process which requires only goods
receipt and no receivables credit, can be setup by attaching this new workflow to
the return line type.
• Return with Receipt and Approval – No Credit: Return process, which also
requires approvals before goods receipt and no receivables credit, can be setup by
attaching this new workflow to the return line type.
3.3.2. Release 12.1.2
3.3.2.1. AIA Order To Cash 2.5 Enhancements

Order Management has enhanced its integration with Siebel Customer Relationship
Management (CRM) or any third party order capture solution via Oracle’s Applications
Integration Architecture (AIA). This solution will enable orders from different channels
(web storefronts, partners, call centers etc.) to be captured via a third party order capture
solution and passed to Oracle E-Business Suite for order fulfillment and billing.
Customer service representatives will be able to enter new orders, monitor order progress
and fulfillment and update orders through Siebel CRM.
This AIA Process Integration Pack (PIP) is responsible for synchronization of orders
between Siebel CRM and Oracle EBS. New features in version 2.5 of the PIP include:
1) Synchronization of updates made in Siebel to the corresponding order in Order
Management
2) Synchronization of scheduling changes driven within Order Management (such as
schedule date, ship-from warehouse and shipping method) to the corresponding Siebel
order.
3) Configurable synchronization of sales order/line workflow status updates from Order
Management to Siebel
3.3.2.2. Workflow Performance Enhancements
In this release, two new enhancements have been added to Order Management to better
support application performance in high volume environments.
3.3.2.2.1. Workflow Purge concurrent program
Often, users choose to defer the closure of the Order at the header level until the end
of the month. Consequently, the Sales Order Header workflow will remain open
throughout the month even though that order has been fulfilled in its entirety. Thus
even though corresponding line workflows can and will close, they will not be
eligible for purging until the header completes as well. This could potentially
increase the load on the ‘Purge Obsolete Workflow Runtime Data’ concurrent
program during month end. Additionally, the workflow tables remain unnecessarily
loaded throughout the month, largely with closed lines waiting for headers to get
closed.
A new concurrent program, “Purge Order Management Workflow,” has been created
to facilitate faster and more thorough purging of Order Management workflows.
This program will first attempt to close stuck order headers and orphaned errored
workflow. The program can then purge child workflows, if they are closed, without
waiting for the parent workflow to complete.
3.3.2.2.2. Support of Workflow bulk APIs to High Volume Order Processing
program
New workflow API’s have been integrated in the High Volume Order Processing
program in order to increase its performance.
3.3.2.3. Supply Chain Web Services – Order Management

As part of this enhancement, web services are provided by exposing business logic
contained within Oracle forms through Java APIs. These web services are cataloged in
the Oracle Integration Repository and can be browsed though Oracle Integration
Repository Browser Interface under respective product family node. By Clicking on the
Business Entity in Integration repository, you can view full description, list of web
services for that business entity along with the description of the web service, whereas
description of parameters can be seen from the XSD definition of the service available
via the generated WSDL.
The following web service is provided for Order Management:
• Sales Order: Create Sales Order, Delete Sales Order, Query Sales Order, Update
Sales Order.
3.3.3. Release 12.1.3
3.3.3.1. International Trade Management Adapter Enhancements for Global Trade

Management (GTM)
The International Trade Management adapter has been enhanced for Global Trade
Management to:
• Support master data synchronization of items
• Support master data synchronization of parties (i.e. organization, person, etc.)
• Send an expanded number of party types
• Deliver additional messages/information
• New option available in the ITM adapter administration that specifically enables
the use of Oracle Global Trade Management
There is a new parameter ’Integrated with Global Trade Management’. If this
parameter is enabled, EBS will send XML messages to GTM for party
synchronization, order export compliance, delivery export compliance screening
and item synchronization. EBS will also be able to receive the responses for the
order and delivery export compliances.
3.3.4. Release 12.2
3.3.4.1. Support for Assemble-To-Order (ATO) Items in Pick-To-Order (PTO)

Models and Kits
Currently, while ATO items are supported as optional/non-mandatory items in PTO
models, they are not supported as included/mandatory items in PTO Models or Kits. In
Release 12.2, ATO items are supported as included/mandatory items in PTO Models as
well as Kits. Thus, ATO items that are identified as included/mandatory items in the Bill
of Materials of the PTO Model or Kit will have the ATO flag selected and corresponding
ATO attributes populated at the time of sales order line creation.
To enable this functionality, the value selected in the profile options “OM: Allow
Standard ATO Items as PTO/Kit Included Components” and “BOM: Allow ATO item in
a KIT or as mandatory in a PTO Model” should be “Yes” at the site level.
3.3.4.2. Order Information Portal (OIP) Enhancements

In Release 12.2, OIP has been enhanced in the following areas:
• Currently, only contacts associated with the Sold To Customer on the sales order
can view and track sales orders through OIP. OIP has been enhanced to allow
contacts associated with the Bill To Customer on the sales order to view and
track sales orders through OIP.
To enable this functionality, the value selected in the profile option “OM: Order
View for External Users based on” should be “Bill to Customer” at the site level.
• External users can subscribe to receive notifications based on key business events
such as Scheduling, Schedule Date Changes and Shipping. In addition, external
users can choose to receive notifications individually for each sales order or
consolidated across sales orders by setting up preferences in Workflow mailer.
• OIP has been integrated with FND Security to enable rules-based access to the
summary and detail views of sales orders and deliveries.
• Several search parameters have been added. “Customer Number” has been
added to Simple Search. “Customer Number”, “Invoice Number”, “Orders On
Hold (Yes/No)”, “Ship To Customer”, “Bill To Customer” and “Deliver To
Customer” have been added to Advanced Search.
• Several display fields have been added to the summary and detail views of the
sales order and delivery.
Fields added to the summary view of the sales order are “Hold Status” and
“Active Holds”.
Fields added to the detail view of the sales order header as well as line are
“Request Date”, “Hold Status”, “Active Holds”, “Ship To Customer”, “Ship To
Contact”, “Bill To Customer”, “Bill To Contact”, “Deliver To Customer” and
Deliver To Contact”. In addition, “Install Base System Names” has been added
to the detail view of the sales order line.
Fields added to the detail view of the delivery line are “Ship To Customer”,
“Ship To Contact”, “Deliver To Customer”, “Deliver To Contact”, “Schedule
Ship Date”, Schedule Arrival Date” and “Serial Number”.
3.3.4.3. Tax Calculation on Freight Charges

Currently, in Order Management, estimated tax is not calculated on freight charges
associated with the sales order header and lines. Taxes on freight charges are
subsequently calculated in Account Receivables if the value of the system parameter
"Invoice Freight as Revenue" is set to “Yes”.
In Release 12.2, estimated taxes on freight charges will also be calculated and displayed
in Order Management if the value of the system parameter "Invoice Freight as Revenue"
is set to “Yes”. In addition to the sales order creation screens, calculation of estimated
taxes on freight charges will be supported in the Process Order API, Order Import and
High Volume Order Processing (HVOP).
In addition, the profile option “OM: Delay Tax Calculation” has been added to allow
deferral of tax calculation from the time of the user entering the sales order line to the
time of the user saving the sales order line.
3.3.4.4. Credit Tolerance for Honoring Manually Released Credit Check Holds
Currently, orders that have been manually released from credit check hold may
potentially have a credit check hold reapplied if changes are made to the order.
In Release 12.2, customers can prevent credit check holds from being reapplied on orders
that were previously released from credit check hold. Reapplication of credit check hold
is prevented if the change in the order amount is within a specified tolerance limit. The
tolerance limit can be specified as an absolute amount or a percentage of the order
amount released from credit check hold. Tolerance amount and percentage can also be
specified together and the lesser of the two will be considered as the tolerance limit. The
tolerance limit applies only to increases in the order amount. Decreases in the order
amount are always considered to be within tolerance limits.
However, changes to certain attributes that impact the credit exposure calculation will
retrigger credit checking regardless of whether changes to the order amount are within
the specified tolerance limit e.g. Bill To Customer is changed. In this event, the order
could potentially have a credit check hold being reapplied.
To enable this functionality, customers should specify values in the Tolerance
“Currency”, “Amount” and/or “Percentage” fields in Credit Check Rules.
3.3.4.5. Support for Credit Hold Based on Bill To Customer

Currently, orders are placed on credit hold if the Sold To Customer is on credit hold. In
Release 12.2, customers have the option to place orders on credit hold if the Bill To
Customer is on credit hold. Additionally, customers can decide to place the order on
credit hold based on the header level Bill To Customer or place the order lines on credit
hold based on the line level Bill To Customer.
A new system parameter “Apply Credit Hold Based On” has been added. Options are
“Sold To Customer”, “Header Level Bill To Customer” and “Line Level Bill To
Customer”. The “Sold To Customer” option is the default option and retains current
functionality.
3.3.4.6. Selling Services Enhancements

In Release 12.2, there are several enhancements related to ordering service items.
3.3.4.6.1. Support for Subscription Contracts
Currently, only service contracts of type “Extended Warranty” can be ordered
through Order Management.
In Release 12.2, service contracts of type “Subscription Contract” can be ordered as
well. Service related attributes such as Start Date, Period and Duration can be
specified for “Subscription Contract”. In addition, an “Extended Warranty” can be
attached to a “Subscription Contract”.
A new system parameter “Default Behavior for Subscription Item on Order Line” has
been added. Set the value to “Subscription Service Line” to enable this feature.
3.3.4.6.2. Billing Options for Extended Warranties & Subscription Contracts
Currently, when an “Extended Warranty” is invoiced through Order Management,
the invoice amount is for the entire duration of the “Extended Warranty”. However,
in several cases, customers need the ability to specify that the invoice amount be
billed in multiple installments during the duration of the “Extended Warranty”.
In Release 12.2, additional billing options have been introduced for “Extended
Warranty” and “Subscription Contract”. The options are as follows:
• Retain the existing behavior of generating an invoice for the entire duration.
• Generate the invoice for the first installment from Order Management and
subsequent installments from Service Contracts.
• Generate invoices for all installments from Service Contracts. In this
scenario, Order Management does not generate any invoices.
A new field “Service Billing Option” has been added to the order line to identify the
appropriate billing option. The value in this field can be defaulted by Order
Management and can be changed by the user.
In addition, a new field “Billing Profile” has been added to the order line to
determine the billing frequency and amount. The “Billing Profiles” available for
selection are maintained in Oracle Service Contracts.
3.3.4.6.3. Additional Attributes for Extended Warranties & Subscription
Contracts
A new field “Service Coverage Template” has been added to the order line. Values
can be specified in this field for “Extended Warranty”.
A new field “Subscription Template” has been added to the order line. Values can be
specified in this field for “Subscription Contract”.
The values in these fields can be defaulted by Order Management and can be
changed by the user.
3.3.4.6.4. Related Order Information Portal (OIP) Enhancements
A new region “Service Details” has been added in Order Information Portal (OIP) to
display service related attributes.
The following fields are available in this region: Service Start Date, Service End
Date, Service Duration, Service Period, Coverage Template, Subscription Template,
Billing Option, Billing Profile, First Period Bill Amount and First Period Bill To
Date.
The new region and fields are hidden by default and need to be enabled for display.
3.3.4.7. Support for Service as Promotional Goods

Currently, only standard items can be defined as promotional goods in Advanced Pricing.
In Release 12.2, service contracts of type “Extended Warranty” can be defined as
promotional goods as well. With this new feature, an “Extended Warranty” can be
automatically added as a discounted order line that is attached to an eligible product.
3.3.4.8. User Defined Attributes (UDA)

In Release 12.2, “User Defined Attributes” have been added in Order Management.
Customers can add several additional fields to the order header and line.
The “User Defined Attributes” framework is in addition to the existing “Descriptive
Flexfields” framework.
In addition, new interface tables and a new concurrent program "Import User Defined
Attributes” have been added to import these attributes.
3.3.4.9. Scheduling Enhancements

In Release 12.2, there are several enhancements related to scheduling.
3.3.4.9.1. Scheduling of Partially Available Quantity
Currently, during scheduling, if the entire quantity is not available on the requested
date, the order line is automatically scheduled with a schedule ship date on which the
entire order quantity is available.
In Release 12.2, during scheduling, if only a partial quantity is available on the
requested date, Order Management will split the order line to schedule the available
quantity on the requested date and schedule the remaining quantity on the available
date.
A new system parameter “Scheduling Auto Split Criteria” has been added. Select a
value other than “None” to enable this feature.
Please note that this feature is only available for standard items that are ATP-enabled
and not part of a Ship Set, Arrival Set, Kit or Model.
This feature is supported in Order Import but not in High Volume Order Processing
(HVOP).
3.3.4.9.2. Substitution of Partially Available Quantity
Currently, during scheduling, if the entire quantity for the ordered item is not
available on the requested date but is available for a substitute item, the entire order
line is scheduled with the substitute item.
In Release 12.2, Order Management will split the line to schedule the ordered item
for the available quantity and schedule the substitute item for the remaining quantity.
To enable this feature, set the value to “With Partial Substitution” in the new system
parameter “Scheduling Auto Split Criteria”. Set the value to “None” or “With Full
Substitution” to retain the existing functionality.
Please note that this feature is only available for standard items that are ATP-enabled
and not part of Ship Set, Arrival Set, Kit or Model.
This feature is supported in Order Import but not in High Volume Order Processing
(HVOP).
3.3.4.9.3. Additional Controls for the Availability Window
Currently, when the profile "OM: Auto Schedule" is set to Yes, the “Availability
Window” is automatically displayed when the user navigates to the “Lines” tab of the
Sales Order form.
In Release 12.2, it is possible to disable the automatic display of the “Availability
Window” when the profile "OM: Auto Schedule" is set to Yes.
A new profile option “OM: Pop Up Availability Window” has been added. Set the
value to “No” to disable the automatic display. Set the value to “Yes” or leave as
blank to retain the existing functionality.
3.3.4.10. Support for Advanced Catch Weight

In 12.2, there are several enhancements related to Dual UOM-enabled items in
Warehouse-enabled (WMS) organizations. These enhancements are across several
Supply Chain products: Order Management, Inventory, Shipping and Warehouse
Management.
Please refer to the RCDs of these products for additional information on related
enhancements.
Enhancements specific to Order Management are:
3.3.4.10.1. Order Fulfillment based on the Secondary UOM
Currently, on a sales order line, when the Ordered UOM is different from the Primary
UOM of the item, an equivalent quantity in the Primary UOM is considered for order
fulfillment.
In Release 12.2, there is a new option to fulfill the order based on the equivalent
quantity in the Secondary UOM. To enable this functionality, the value populated in
a new field “Fulfillment Base” on the order line should be “Secondary”.
A new profile option “OM: Default Fulfillment Base” has been added. Set the value
to “Yes” to enable dynamic fulfillment base selection capability.
Order Management defaults the value of the “Fulfillment Base” field based on the
Ordered UOM, Primary UOM and Secondary UOM of the ordered item. This value
is defaulted on the basis of seeded conditions that determine whether the value in the
“Fulfillment Base” field should be "Primary" or “Secondary". In addition, there is a
“custom hook” to allow customers to define their own conditions to determine the
“Fulfillment Base”.
3.3.4.10.2. Related Pricing Enhancements
Currently, pricing of Dual UOM-enabled items is always calculated on the Shipped
Quantity in the Secondary UOM if specified as such in the item definition.
In Release 12.2, two new pricing options have been introduced to determine if
pricing should be calculated on the Shipped Quantity in the Ordered UOM or
Primary UOM.
3.3.4.10.3. Related Returns (RMA) Enhancements
If the original sales order line is referenced in a return/RMA line, the value of the
“Fulfillment Base” field will be inherited from original sales order line.
If the original sales order line is not referenced, the “Fulfillment Base” on the
return/RMA line will be determined independently using the same logic as specified
for outbound sales order lines.
3.3.4.10.4. Related Availability Window Enhancements
Several fields have been added to the “Availability Window” in the “Ordered Item”
and “Substitute Item” tabs.
The new fields are: Primary UOM, On Hand Ordered Quantity and Ordered Quantity
Reservable. The On Hand Ordered Quantity and Ordered Quantity Reservable fields
display results in the Ordered UOM by converting from the available Primary UOM
or Secondary UOM quantity depending on the value in the “Fulfillment Base” field.
3.3.4.11. Integration with Oracle Approvals Management (AME)

Currently, the list of approvers for the transactions requiring approval is a pre-determined
list.
In Release 12.2, Order Management has been integrated with Oracle Approval
Management to leverage the robust capabilities of the approval rules engine to
dynamically determine the list of approvers for Quotes, Sales Agreements and Returns
(RMA).
A new option “Use Approvals Management Engine” has been added to the “Transaction
Types” form. Select this option to use this feature for specific transaction types.
For the transaction types with the “Use Approvals Management Engine” option selected
and appropriate workflow processes assigned, the list of approvers will be determined by
Approval Management based on the rules defined for the specific entity (Quotes, Sales
Agreements and Returns (RMA). The seeded workflows that support this functionality
are “Order Flow - Mixed or Return with Approval” (for RMAs) and “Negotiation Flow -
Generic with Approval” for Quotes and Sales Agreements.
With AME, the list of approvers is dynamically generated based on attribute values,
conditions, approval types and approval groups. Several attributes have been seeded in
Approval Management for defining rules for these entities (Quotes, Sales Agreements
and Returns (RMA). In addition to the seeded attributes, customers can define additional
attributes for use in rule definition.
3.3.4.12. Credit Card Authorization Reversal

Currently, for an order/ line with credit card payments, Order Management authorizes the
credit for the order/line amount and re-validates the availability of a valid authorization
on the order/line during the order/line lifecycle.
In Release 12.2, an option to reverse the prior authorization and execute a new
authorization when there are changes to the order/line has been added.
In addition, customers can choose various options related to credit card authorization
reversal and re-authorization based on changes to the order/line. The options are:
• Reverse the authorization and re-authorize immediately.
• Defer the reversal of the authorization and re-authorization to specific events
such as picking, shipping and fulfillment.
• Place the order/line on hold.
For orders/lines on hold, reversal of the authorization and re-authorization can be

initiated by the “Process Payments” action or running the “Process Pending Payments”
concurrent program.
A new system parameter "Reversal of Credit Card Authorization and Re-authorization"

and a new option “Reversal of Credit Card Authorization and Re-authorization" in the
“Transaction Types” form have been added.
3.3.4.13. Additional Business Events

In Release 12.2, several business events have been added.
The “oracle.apps.ont.oip.statuschange.update” business event is invoked during the
following changes in the order/line: Booking, Scheduling, Schedule Ship Date Change,
Shipping, Fulfillment, Invoicing, Customer Acceptance and Closing.
The “oracle.apps.ont.hold.action” business event is invoked when a hold on an order/line
is placed and released.
The “oracle.apps.ont.oip.processfailure.update” business event is invoked when order
booking fails.
A new profile option “OM: Raise Status Change Business Event” has been added. Set
the value to “Yes” to enable this feature.
Please note that the new business events are available in Release 12.1.3 as well.

In Release 12.2, the following new capabilities offer the ability to increase productivity
3.3.4.14.1. Additional Hold Source Attributes
In Release 12.2, “Customer Number” has been added as an additional hold source for
creating order header level holds. “Item Category”, “End Customer” and “End
Customer Number” have been added as additional hold sources for creating order
line level holds.
3.3.4.14.2. Specify Recipient/Role for Credit Check Hold Notifications
Currently, if credit check hold notifications are enabled, notifications for sales orders
placed on credit check hold are sent to the user who created that particular sales
order. However, this user may not necessarily be authorized to release the sales order
from credit check hold. A new profile option, “OM: Credit Check Notification
Recipient”, allows customers to specify the user or role assigned to users who will
receive notifications when sales orders are placed on credit check hold.
3.3.4.14.3. Allow Users with View-Only Access to Apply/Release Order Holds
Currently, only users with the ability to edit the sales order can apply/release an order
hold. Users with view-only access to sales orders cannot apply/release order holds
even if they are authorized to do so. In Release 12.2, users with view-only access can
also apply/release order holds assuming that they are authorized to do so.
3.3.4.14.4. Allow Users with Ability to Apply Holds to Search by Hold Name
Currently, only users with the ability to release holds can search for sales orders by
hold name. In Release 12.2, users with the ability to apply but not release holds can
also search for sales orders by hold name.
3.3.4.14.5. Consistency in Display of Credit Hold Flag after Customer Merge
Currently, when customers are merged, the target customer inherits credit holds from
merged customers at the Account and Bill-To site levels. Although Order
Management continues to apply holds for the target customer that are inherited from
the merged customers, the credit hold flag for inherited credit holds is not displayed
as selected when viewed in customer detail. In Release 12.2., this inconsistency has
been addressed and inherited credit holds will be displayed as selected in the
customer detail screen.
3.3.4.14.6. Additional Defaulting Attribute for Intermediate Ship To Org
In Release 12.2, “Intermediate Ship to Org” at the order line level has been added as
an additional attribute for defaulting in the defaulting rules framework. Customers
can setup defaulting rules for “Intermediate Ship to Org” based on defaulting source
type of "Constant "or "PL/SQL".
3.3.4.14.7. Ability to Search Orders by PO Release Number
Currently, drop-ship orders can be searched by "Related PO Number" in Order
Organizer and Quick Order Organizer. In the case of Blanket Purchase Orders, there
could potentially be several Blanket Releases. In Release 12.2, a new search
parameter “PO Release Number” has been added.
If a value is specified in the “Related PO Number” parameter, the “PO Release
Number” parameter will list all related Blanket Releases and these two parameters
can be used together to search drop-ship orders.
3.3.4.14.8. Automatic Creation of Ship Sets Based on Warehouse
Currently, if the profile option “OM: Assign New Set For Each Line” is set to "No"
and the “Line Set” value in the order header is “Ship”, Order Management ensures
that all lines in a ship set are shipped from the same warehouse.
In Release 12.2, this functionality is extended by giving customers the option to
automatically create new ship sets for each warehouse in an order.
To enable this functionality, a new system parameter “Assign New Ship Set for Each
Warehouse” has been added and the value should be set to “Yes”.
3.3.4.14.9. Reassignment of Drop-Ship Orders Created by Inactive Users
In Release 12.2, a new system parameter "Requestor For Drop Ship Orders Created
By Inactive Users” has been added. For drop-ship orders, in the event that the user
who created the original sales order is no longer an active user, the user specified in
this system parameter will be passed to Purchasing when the Purchase Release
process is initiated.
3.3.4.14.10. Copy Automatic Attachments When User Splits Line
Currently, when the user splits a line, manual attachments are copied to the newly
created line but automatic attachments are not copied to the newly created line.
In Release 12.2, if there is no change in the Ship To Address during the split,
automatic attachments, along with any modifications, will be copied over to the
newly created line. If there is a change in the Ship To Address, automatic
attachments will be reapplied to the newly created line based on automatic
attachment rules.
To enable this feature, the value in the existing profile option "OM: Apply Automatic
Attachments" should be set to “Yes”. There is no change in the existing behavior
when the value in this profile option is set to “No”.
Please note that there is no change to the behavior of manual attachments when the
user splits the line or the behavior of manual and automatic attachments when the
system splits the line.
3.3.4.14.11. Ability to View Shippable Lines Only in a Configuration
Currently, in the sales order form, when the "Show Line Details" option is selected in
the Tools menu, details of the configuration such as options, classes and included
items are displayed in the line “Summary” tab.
In Release12.2, there is an additional option to display only the shippable lines of a
configuration when the "Show Line Details" option is selected. To enable this new
feature, a new option "Show Shippable Lines Only" has been added to the Tools
menu.
3.3.4.14.12. Option for Cost of Goods Sold (COGS) Account derivation in Returns
(RMA)
Currently, when advanced accounting is not used for an intercompany sales order, the
COGS account for a return/RMA line that references the original sales order line is
derived from the referenced order line.
In Release 12.2, customers have the option to derive the COGS account from the
attributes of the return/RMA line rather than the referenced sales order line.
A new system parameter “Source Line for deriving COGS account on referenced
RMA" has been added. Set the value to "Return Line to be used as Source" to enable
this feature. Set the value to "Referenced Sales Line to be used as Source" to retain
the existing functionality.
3.3.4.14.13. Serial Item Support in Workflow "Bill Only with Inventory Interface"
In Release 12.2, in addition to current support for lot and revision Items, serial
controlled items are also supported by the “Bill Only with Inventory Interface”
workflow. As a prerequisite, users have to create reservations against serial
number(s) in the Reservation Details form.
3.3.4.14.14. Performance Improvement in Order Organizer
In Release 12.2, performance of order and order line search in Order Organizer and
Quick Order Organizer has been improved by populating the matching orders in a
Global Temporary Table.
3.3.4.14.15. Performance Improvement in Schedule Orders Concurrent Program
Currently, at the time of scheduling orders through the “Schedule Orders” concurrent
program with scheduling mode "Lines at Eligible Activity", two records are inserted
in the workflow activity status history table for each line that meets the criteria
defined by the program parameters but is also on “Line Scheduling” workflow
activity hold.
In Release 12.2, performance is improved by filtering out lines on a “Line
Scheduling” activity hold and thereby reducing the number of records inserted into
the workflow activity status history table.
3.3.4.14.16. Audit History Purge Enhancement
In Release 12.2, the existing "Order Purge" concurrent program has been enhanced to
include the related data from the audit history table when purging sales orders. In
addition, a SQL Script is available to purge records present in the audit history table
for previously purged orders.
3.3.4.14.17. Increase in Size of Freight Carrier Name Field
In Release 12.2, the maximum length of the Freight Carrier field in the Additional
Line Information window has been increased from 30 to 360 characters.
3.3.5. Release 12.2.3
3.3.5.1. Support for “Online” Mode for Line Level Credit Checking
In Release 12.2.3, line level credit checking has been enhanced to support “online” mode
in addition to “pre-calculated” mode. In addition, party/party hierarchy level credit
checking is supported in “online” mode for line level credit checking.
3.3.5.2. Consider “Assemble To Order” Flag at Warehouse Level

Currently, Order Management considers an item as an ATO item if the “Assemble To
Order” flag is selected in the item master of the item validation organization.
In Release 12.2.3, Order Management will consider the “Assemble To Order” flag from
the shipping warehouse instead of the item validation organization if the value in the new
system parameter “Honor ATO Item setup at warehouse level” is “Yes”.
Please note that this feature is only available for ATO items (standalone, part of a
Kit/PTO Model or part of a ship set/arrival set) and not for ATO Models.
3.3.5.3. Scheduling Enhancements

In Release 12.2.3, there are several enhancements related to scheduling.
3.3.5.3.1. Enhanced Support for Line Sets in the “Schedule Orders” Concurrent
Program
In Release 12.2.3:
• When the system parameter "OM: Auto Schedule Sets" is set to "No"
• Sales order lines in a Ship/Arrival set are at the "Schedule Eligible"
activity
When scheduled through the “Schedule Orders” concurrent program, all the lines in a
Ship/Arrival set will be progressed together beyond the “Scheduling” activity if
scheduling is successful.
3.3.5.3.2. Enhancements in the “Reserve Orders” Concurrent Program
In Release 12.2.3, the “Reserve Orders” concurrent program has been enhanced to
allow users to specify “Subinventory”, “Lot Number” and “Revision Number” as
additional parameters.
When the concurrent program is executed with a specified “Subinventory”,
reservations will be created for qualifying sales order lines (those without a prior
reservation and a subinventory specified on the order line) against the specified
“Subinventory”.
If “Item” and “Subinventory” are specified in the program parameters, “Lot Number”
can also be specified in the program parameters to create reservations against a
specific “Subinventory” and “Lot Number”.
If “Item” and “Warehouse” are specified in the program parameters, “Revision
Number” can also be specified in the program parameters to create reservations
against a specific “Revision Number”.
In addition, if the “Reserve Orders” concurrent program is executed by specifying an
"Order By" parameter, the program will consider that parameter irrespective of the
subinventory on the order line.
If multiple lines have the same precedence based on the “Order By” parameter, lines
with earlier creation date will be given precedence.
3.3.5.3.3. Prevent “Bill Only” Lines in Ship /Arrival Set
In Release 12.2.3, there is a new option to prevent adding sales order lines with “Bill
Only” workflows to a Ship/Arrival set. To enable this functionality, a new option
“Bill Only Flow” has been added to the “Transaction Types” form to identify lines
with a “Bill Only” workflow.

3.3.5.4.1. Automatic Creation of Modifiers for a Referenced Return/RMA Line
In Release 12.2.3:
• When a referenced return/RMA line is created with pricing option "At
Original Selling Price"
• There is a difference between the list price and selling price on the
source order line
• There is no modifier on the source order line to account for the
difference between the list and selling price
Order Management will automatically create a modifier on the referenced

return/RMA line to account for the difference between the list and selling price.
To enable this functionality, specify a value in the new profile option “OM: Price
Adjustment Modifier for reference RMA”. The modifier specified in this profile
option should be a line level, manual, over-rideable, amount-based
discount/surcharge modifier that is globally applicable and not associated with a
specific currency.
If there is no value specified in this profile option, there is no change in the existing
behavior where the selling price on the RMA line will be calculated by the pricing
engine as of the current date.
3.3.5.4.2. “Override ATP” Flag in “Mass Change” Form
In Release 12.2.3, the “Override ATP” flag has been added to the “Shipping” tab of
the “Mass Change” form to allow users to select multiple lines and “Override ATP”
by entering a Schedule/Arrival Date for the selected lines.
The new flag is a folder enabled field and is available on the “Mass Change” form
when invoked from Sales Order, Order Organizer and Scheduling Organizer.
3.3.5.4.3. Additional Details in RMA Approval Notification and Order Information
Portal (OIP)
In Release 12.2.3, the notification that is sent to approvers of an RMA will display
order details. The following details for the first five open return/RMA lines will be
displayed in the notification:
• Header Level: Order Number, Order Date, Customer and Currency
• Line Level: Line Number, Item Number, Return Item UOM, Return Item
Quantity, Return Item Unit Price, Return Reason, Order Reference and Invoice
Reference
In addition, there will be a new link “Additional Order Details” in the notification.
This link will allow the user to view additional information in Order Information
Portal (OIP) for the approver to view more details of the order.
The Line Details page in OIP has been enhanced to display addition information for
return lines. The new fields are: Return Reason, Return Order Reference, Return
Order Line Reference, Return Invoice Reference and Return Invoice Line Reference.
The new fields are hidden by default and need to be enabled for display.
3.3.5.4.4. Response Notes in Approval Rejection Notification for Quotes
In Release 12.2.3, the notification that is generated when a quote is rejected by an
approver will include the “Response Notes” entered by the approver.
3.3.5.4.5. “Booked Date” Field in Sales Orders Forms
In Release 12.2.3, a new folder enabled field “Booked Date” is available as a display-
only field in order entry forms (Standard and Quick Sales Order) and search results
(Order and Quick Order Organizer).
In addition, “Book Date From” and “Book Date To” have been added as search
parameters in Order and Quick Order Organizer.
3.3.6. Release 12.2.4
3.3.6.1. HTML User Interface for Order Management

In Release 12.2.4, Order Management will have an HTML user interface for creating,
updating and managing orders. The new HTML user interface is in addition to and co-
exists with the existing sales order screens and Order Information Portal (OIP).
The new HTML user interface is an additional option for customers who desire a modern,
easily configurable, tablet friendly user interface.
The HTML user interface offers functional parity with Sales Orders, Order Organizer and
Scheduling Organizer.
The HTML user interface shares a common foundation with the existing sales order
screens, Process Order API and Order Import.
3.3.6.2. Item Substitution on Internal Sales Orders

Currently, while item substitution is supported for external sales orders, it is not
supported for internal sales orders.
In Release 12.2.4, item substitution is supported for internal sales orders as well. To
enable this functionality, the value selected in the newly added system parameter “Item
Substitution on Internal Order” should be other than “None”. “None” is the default
option and retains current functionality.
The other options in the system parameter “Item Substitution on Internal Order” are:
• Manual – only manual substitution is allowed (via Related Items window)
• Automatic – only automatic substitution is allowed (via ATP)
• Manual and Automatic – both manual and automatic substitutions are allowed
In addition, there is a new profile option “OM: Send Notifications of Internal Order
Change” to enable users to opt in or out of sending notifications when there are changes
to internal sales orders. This profile can be setup at site/responsibility/user level.
The options are:
• Null – default option to retain current behavior. Send notifications when there are
any changes to “ordered quantity” or “schedule arrival date”
• No – do not send any notifications
• Yes – send notifications when there are any changes to “ordered quantity”, “schedule
arrival date” or “ordered item”
3.3.6.3. Enabling Configurator for Return Orders (RMA)

Currently, when creating non-referenced RMAs for PTO Models or Kits, Order
Management always treats such lines as standard lines and they cannot be configured.
In Release 12.2.4, customers have the option to configure PTO Models or Kits in non-
referenced RMAs. To enable this functionality, the value in the new profile option “OM:
Enable Configuration UI for RMA" should be set to “Yes”. When the value in this profile
option is set to “Yes”:
• Configurator can be invoked for PTO Models to select required options for returns
and the selected options/option classes will be populated on the order. In addition,
included items will be populated when Bill of Materials is exploded based on the
value in the "OM: Included Item Freeze Method" profile option
• Kits will explode and included items will be populated based on the value in the
"OM: Included Item Freeze Method" profile option
Please note that as soon as the configuration lines are created, they will be marked as
“remnant” and be treated as standard lines. This is consistent with the existing treatment
of Models and Kits in referenced RMAs.
In addition, re-configuration and/or deletion of any line is not allowed if any line in the
same configuration is either received, fulfilled, closed, cancelled or split.
3.3.6.4. Order Management Support for Yard Management System

The new product Yard Management System (YMS) developed for managing the
resources/inventory flow within the Yard of a Warehouse uses the RMA feature of Order
Management to process returns of materials in YMS-enabled organizations.
Order Management has been enhanced to provide support for:
• Storing trailer details on line level while creating/updating the return lines in Order
Management, and
• Automatically creating/updating trailer details on the return lines for the changes
initiated in Yard Management System during Yard check-in activity
Three new fields "Equipment Number", "SCAC" and "Container Number" have been
added in the “Returns” tab of the Sales Order and Quick Sales Order forms. The new
fields will be available in Order Organizer and Quick Order Organizer as well.
In addition to the sales order creation screens, entry/update of trailer details will be
supported in the Process Order API and Order Import. Please note that once the RMA is
received, further updates to "Equipment Number" and "SCAC" fields on the sales order
line are not allowed.
3.3.6.5. Performance Improvements - Bulk Processing

In Release 12.2.4, bulk processing is enabled for workflow item creation and order purge
processes.
With these enhancements, when adding new lines to an order, corresponding workflow
items will be created simultaneously in a single call to the workflow engine. This
performance enhancement applies to orders created through sales order creation screens,
Process Order API and Order Import.
In addition, the performance of the order purge program has been significantly improved
by adding bulk deletion.

3.3.6.6.1. Public API for Item Orderability
Currently, Item Orderability rules setups in Order Management are used within Order
Management forms and processes.
In Release 12.2.4, External applications can use Order Management Item

Orderability rules through Public API and pass the input parameters to validate
whether an item can be ordered in Order Management.
The new Public API is OE_ORDER_PUB.VALIDATE_ITEM_ORDERABILITY.
3.3.6.6.2. Display of Reserved Quantity Information
In cases, where ordered UOM is other than the item's primary UOM and inventory
reservations are done in the primary UOM, the quantity reserved field (in the ordered
UOM) does not match the ordered quantity due to rounding at the time of conversion
from primary to ordered UOM.
In Release 12.2.4, the reserved quantity will match the ordered quantity if the entire
ordered quantity is reserved and the ordered quantity in primary UOM matches with
the actual reserved quantity up to a precision of five decimals.
Please note that the current enhancement is related solely to the display of reserved
quantity in the sales order form.
3.3.7. Release 12.2.5
3.3.7.1. Enhanced Gross Margin Calculations
In Release 12.2.5, gross margin accuracy has been enhanced by incorporating customer
rebates, vendor rebates and cost modifiers. The “accrual” Offers created in Oracle
Channel Revenue Management are applied as customer rebate or vendor rebate on a sales
order line. Cost modifiers are a mechanism for customers to increase/decrease the unit
cost of the item for purposes of gross margin calculation.
To enable this functionality, the following new values have been added to the existing
system parameter “Margin Calculation”:
• Cost Based, Cost Modifiers Only
• Cost Based, Cost Modifiers and Rebates
• Price Based, Cost Modifiers Only
• Price Based, Cost Modifiers and Rebates
Based on the selected value, cost modifiers and/or rebates will be included in gross
margin calculations of a sales order line. The new calculations are:
Adjusted Unit Cost = Unit Cost + Cost Modifier + Customer Rebate – Supplier Rebate
Margin Amount = Unit Selling Price - Adjusted Unit Cost
“Adjusted Unit Cost” is a newly added field on the sales order line.
A new line level action “View Cost Adjustments” has been added to launch a new
window/page that will display the following cost adjustments details:
• Summary: Unit List Price, Unit Selling Price, Unit Cost, Adjusted Unit Cost, Margin
and Margin%
• Details:
o Cost Adders: Name, Description, Amount
o Customer Rebate: Level, Number, Name, Type, Rate, Amount
o Supplier Rebate: Level, Number, Name, Type, Rate, Amount
Other Margin related enhancements in the Order Management HTML UI
The existing fields “Margin” and “Margin % will now be editable in the HTML UI.
In addition, a new field “Margin %” has been added in the Mass Change page to allow
users to apply the given margin % on eligible order lines.
3.3.7.2. Subscription Ordering Enhancements

The subscription ordering feature introduced in Release 12.2 has been further enhanced
to provide the following new capabilities:
3.3.7.2.1. Subscription Contracts as Promotional Goods
In Release 12.2.5, customers will have the ability to setup subscriptions contracts as
free or discounted services that are automatically added to the sales order based on
adding a qualifying item to the sales order. .
Please refer to the Advanced Pricing section of the RCD for additional information
on related enhancements done in Advanced Pricing.
3.3.7.2.2. Import Models/Kits with Included Items as Pre-Exploded
Currently, imported Models/Kits are exploded by Order Management to add included
items as child lines on the order.
In Release 12.2.5, customers can import pre-exploded included items from external
system with additional details like start and end dates on the included items of
Models/Kits.
3.3.7.3. Order Management Support for Serial Tagging at Sales Order Pick
In Release 12.2.5, Oracle Logistics has enhanced the serial tagging functionality to “Sales
Order Pick” transactions where items with serial control as “none” and “at sales order
issue” can be assigned serial numbers in upstream process “sales order picking”.
Order Management has added following support for items with serial control as “none”
and “serial tagging” enabled at “sales order picking”:
• Extended the existing RMA functionality to enable the user to enter serial numbers
for such items
• Drop Ship orders for such items will be considered as serial controlled and the
appropriate serial number will be interfaced to Inventory from Order Management
Please note that for items with serial control as “none” or “at sales order issue” but
having “serial tagging” enabled at “sales order picking”, order lines with “Bill Only with
Inventory Interface” line type are not supported.
3.3.7.4. Performance Improvements in Scheduling Process and Schedule Order

Program
In Release 12.2.5, bulk processing of order lines in ATP process and parallel processing
in schedule orders program has been enabled resulting in significant performance
improvements in Scheduling in Order Management.
Two new parameters have been added to the Schedule Orders program:
• Bulk Processing - Set the value to “Yes” to enable bulk processing
• Workers - Optionally set a value greater than one to enable parallel processing if
Bulk processing is already enabled
Please note that the new enhancement is applicable for all scheduling Modes except
"Progress Lines at Schedule-Eligible Activity".

3.3.7.5.1. Manual Line Splits in Internal Sales Orders
Currently, internal sales order lines can be split by the system during interface trip
stop when a delivery has been partially shipped.
In Release 12.2.5, the seeded (and enabled) processing constraint that prevents
internal sales order lines from being split manually has been modified to be a “non-
System” constraint thereby giving customers the option to disable this constraint in
their implementation.
Now, for shipping the material most optimally e.g. users can split the internal sales
order line to choose more effective scheduling or different ship methods.
3.3.7.5.2. Extend Defaulting of Contingency / Acceptance Name until Fulfillment

Currently, initial defaulting of revenue contingency attributes (Acceptance Name and
Revenue Recognition Expiration Days) is done based on seeded attributes in Order
Management and on changing any of these attributes re-defaulting occurs until the
order line is booked.
In Release 12.2.5, two new attributes “Ship Method” and “FOB” has been added as
seeded attributes based on which revenue contingency attributes can be defaulted/re-
defaulted.
In addition, re-defaulting of revenue contingency attributes is extended until the line
is fulfilled. Further, Acceptance Name and Revenue Recognition Expiration Days
can be updated manually as well until the line is fulfilled.
3.3.7.5.3. Assign the Ship/Arrival Sets to Split Lines and Enable Set Operations on
Remnant Lines
Currently, the Ship/Arrival set is assigned to the order lines only when the new line is
created if profile option “OM: Assign New Set For Each Line” is set to ‘Yes’ and
Line Set is defined on the order.
In Release 12.2.5, Order Management has extended the existing functionality to new
lines created during "split of existing line” and system will automatically assign
ship/arrival set to such new lines as well.
In addition, set operations like create set, assign set, delete set have been enabled on
shippable remnant lines of PTO Model/ Hybrid Model/Kit.
3.3.7.5.4. Group Drop Ship Requisition Lines by Sales Order

Currently, Oracle Purchasing creates a single purchase requisition for eligible drop
ship lines from the sales orders available in Purchasing Interface.
In Release 12.2.5, Order Management will populate an additional identifier (Order
Header ID) while inserting data into Purchasing Interface tables for Purchasing to
create a purchase requisition for drop ship lines of a single sales order only.
To enable this functionality, the value selected in the new system parameter “Group
Requisitions By Sales Order” should be “Yes”. Value “None” is the default option
and retains current functionality.
3.3.7.5.5. Related Items support for BSA associated Order Lines

In Release 12.2.5, Order Management has extended the related item functionality (to
up-sell/cross-sell etc.) for sales order lines associated with Sales Agreements.
3.3.8. Release 12.2.6
3.3.8.1. Recurring Billing
Currently, recurring billing is supported in the Order Management and Service Contracts
flow for services i.e. Extended Warranties and Subscription Contracts (Tangible &
Intangible).
In this release, recurring billing for standard items has been added to Order Management.
This gives customers the option to model rental equipment contracts as standard,
shippable items and intangible, subscription contracts as standard, non-shippable items.
Recurring billing for rental and subscription contracts can be processed directly through
Order Management.
For recurring billing, a “Billing Plan” can be attached to each sales order line. For each
“Billing Plan”, there is an option to bill indefinitely until termination or generate a
fixed/pre-defined number of bills. Additional parameters such as frequency, start date,
amount, etc. can be specified on the “Billing Plan”.
A new attribute, “Billing Validation” has been added to the sales order line. This
determines whether or not the sum of the bill amounts on the “Billing Plan” should equal
the sales order line amount.
Any change in the sales order line amount/quantity since the “Billing Plan” was last
updated will flag the sales order line for review at the time of invoicing/closing and
prevent the sales order line from progressing. Any mismatch between the sales order line
amount and the billing amount has to be resolved and confirmed by the user before the
sales order line can progress.
There is an option to generate the first bill with the source order line to which the “Billing
Plan” is attached. For all other bills, once the source sales order line is fulfilled/closed, a
new concurrent program “Create Billing Lines” generates bill-only sales order lines on
the due date of each bill as specified on the “Billing Plan”. The bill-only sales order
lines are created in the same sales order as that of the source order line to which the
“Billing Plan” is attached.
After billing has commenced, the “Billing Plan” can be updated and the changes will be
applied to future bills. In the case of a “Billing Plan” with a fixed/pre-defined number of
bills, the number of bills can be increased to extend/renew the “Billing Plan”.
After billing has commenced, billing can be manually terminated by the user. After
billing has commenced, a referenced RMA for the full quantity on the source order line
will automatically terminate further billing. After billing has commenced, a referenced
RMA for part of the quantity on the source order line will automatically place the
“Billing Plan” on hold. The future billing amount should be adjusted to account for the
partial quantity return and confirmed by the user before billing can be recommenced.
To enable this functionality, a new system parameter “Enable Recurring Billing” has
been added.
In addition to the sales order creation screens, this feature is supported in the Process
Order API and Order Import but not in High Volume Order Processing (HVOP).
3.3.8.2. Synchronization of Promise Date changes on Purchase Order with Drop

Ship Sales Order
In Release 12.2.6, drop ship order processing has been enhanced to offer additional and
better-coordinated change management capabilities. Changes to the earlier promised date
can be initiated by Suppliers directly or through Buyer on communication from
Suppliers. Once such changes are accepted and approved in Oracle Purchasing, they are
communicated to Order Management on real time basis and are visible as "Schedule Ship
Date" on drop ship sales order line.
Additionally, please refer to the RCD of Purchasing/iSupplier for more information on
this capability
3.3.8.3. Performance Improvements in Process Order API

Currently, for internal processing of creating/updating multiple order lines of a Sales
Order in the same database session, the lookup values and few other attributes are fetched
over and again from the database for each line.
In Release 12.2.6, the values retrieved during the first time search/call will be persisted
throughout the same database session.
Caching these values and reusing them if the same value is passed again by other lines,
will significantly improve the performance of creating, updating or validating the large
orders or a large number of order lines from multiple orders in the same database session.
3.3.8.4. Performance Improvements in Scheduling Process and Schedule Order

Program
In Release 12.2.6, existing functionality of bulk processing of order lines in ATP process
and parallel processing in schedule orders program has been further extended to
following Scheduling Modes:
• "Progress Lines at Schedule-Eligible Activity"
• Null value. That is, no parameter is passed to Scheduling Mode
Please refer to Order Management 12.2.5 RCD for more details on this feature.
3.3.8.5. Performance Improvements in Order Import Program

Currently, Order Import processes all the lines of a sales order as single entity.
In Release 12.2.6, Order Import program has been enhanced to process large orders by
multi-threading the order lines of a sales order to do parallel processing for improved
performance.
To enable this functionality the profile "OM: Order Lines Threshold For Large Order
Processing in Order Import" should be set to a number value to indicate the minimum
number of lines required in a sales order in order to qualify for a "Large Order".
In addition, Order Import concurrent request parameter "Enable Single Line Queue for
Instances" should be set to "Yes" on concurrent program definition window.
Please note that the new feature is applicable for:
• Standard Orders in "Entered" status only, and
• All Lines in the Order are Standard Lines only

3.3.8.6.1. Line-Level Search by PO Number in Order Organizer
In Release 12.2.6, Order Organizer's Find Window has been enhanced to enable
query on "Related PO Number" field on Line Information tab. Now, search result for
drop ship orders will honor the value on this field while displaying the related orders
and order Lines on Summary and Lines tab respectively.
3.3.9. Release 12.2.7

3.3.9.1. Milestone Billing
In 12.2.6, the Recurring Billing framework was added to Order Management.
In this release, Milestone Billing has been added as an additional flavor to the Recurring
Billing.
This feature is for customers who have long lead times for custom designed equipment
and bill at typical milestones like Booking, Fulfillment and Customer Acceptance.
This feature provides the capability to select milestones in the billing plan and specify the
amount/percentage that should be billed for each milestone.
Here, milestones may be:
• Predefined and natively recognized milestones such as Booking, Fulfillment and
Customer Acceptance. Order Management will recognize and generate bills on
completion of natively recognized milestones.
• Custom defined milestones. The framework will allow customers to define additional
milestones that are not natively recognized by Order Management e.g. Delivery,
Installation, etc. Customers could update the billing plan/schedule with the
completion date of these milestones at which point Order Management will generate
bills.
In addition to the sales order creation screens, this new flavor of Milestone Based Billing
in the Recurring Billing framework is also supported in the Process Order API and Order
Import but not in High Volume Order Processing (HVOP).
3.3.9.2. Schedule Orders Enhancements

In Release 12.2.7, Schedule Orders Concurrent Program has been enhanced to offer
following additional capabilities
3.3.9.2.1. Improved Bulk Rescheduling
In Release 12.2.6, in the limited supply conditions, rescheduling the lines using
Scheduling Mode as “Reschedule Using Request Date” and First Order By as
“Request Date” may not always give earlier schedule ship date to lines having earlier
request date which are currently being scheduled for some later date.
In Release 12.2.7, system now un-schedules all selected lines in one go and then
schedules the lines one by one as per the Order By criteria specified.
In this process demand consumed by all the selected lines is released at once. This
helps to achieve better schedule ship dates within the set of selected lines as per
Order By criteria.
For example: with parameter "Request Date", system will assign early schedule ship
dates to order lines having early request dates as freed up supply was made available
to lines having earlier request date in that sequence.
In addition to bulk mode, this solution is also available in “parallel option” (workers
> 1). However, the Order By criteria will be applicable only within individual child
worker in this case.
3.3.9.2.2. Excluding Reserved Lines from Scheduling
Currently, when users reschedule order lines in Schedule Order Concurrent program,
all the lines are rescheduled irrespective of the lines are already reserved or not.
In Release 12.2.7, now user will have an option to include/exclude reserved lines
from being rescheduled /unscheduled, when the concurrent program is called.
Further, there will be an additional option to differentiate between Inventory
reservations and Non-Inventory reservations for including/excluding reserved lines
from being rescheduled /unscheduled.
3.3.9.3. Manual Item Substitution Post Booking

Oracle Order Management already provides automatic Item substitution post booking via
ATP (through scheduling/re-scheduling).
In Release 12.2.7, user can do manual item substitution on booked orders through all
sales order creation screens utilizing the Related Items window/page.
To enable this functionality the existing profile “OM: Enable Related Items and Manual
Substitutions” should be set to “Yes”
Please note that item substitution post booking is restricted in following additional case:
• A shippable line which is interfaced to shipping can’t be substituted if the substitute
item is not shippable
3.3.9.4. REST Web Services Enhancements

In Release 12.2.7, Read capability has been added in sales order interface web service of
Oracle Integration Repository. A new procedure OE_Inbount_Int. Get_Order has been
added in existing package OE_Inbount_Int to provide the provision to retrieve order
information web service call based on the following parameters:
• Header ID
• Line Id
• Header ID and Line ID
• Order Number
• Order Number and Order Type
In addition, Get_Order API in OE_Order_Pub package has been expanded to support the
above mentioned input parameters.

3.3.9.5.1. Mechanism to prioritize reservation removal by supply source
If the line is reserved against multiple supply sources and the quantity on the order
line is reduced then users will be able to control the sequence in which reservation
(supply source) is removed. This will help in consuming most advantageous/
preferred supply first.
To enable this functionality, a new system parameter “Use Reservation Removal
Sequence” should be set to “Yes”. A new lookup “OM: Reservation Removal
Sequence” has been added for user to define the priority in tag attribute.
3.3.9.5.2. New search field Actual Ship Date
Oracle Order Management provides comprehensive search parameters to find orders
to manage existing orders and returns.
Two new search parameters "from actual ship date" and "to actual ship date" have
been added in release 12.2.7 to provide additional options for the users to find and
manage the orders.
3.3.9.5.3. New Business Events in User Defined Attributes

Two business events oracle.apps.ont.document.preAttributeChange and
oracle.apps.ont.document.postAttributeChange of User Defined Attributes (UDA) are
seeded in release 12.2.7.
Customer can now subscribe to these business events with very minimal setup and
get notification when UDA values on the order and/or line are changed.
3.3.10. Release 12.2.8

3.3.10.1. Enhancements to Integration with Oracle Approvals Management (AME)
Order Management integration with Oracle Approval Management is already available
for Return Orders and Quotes. Following seeded workflows provide the required
integration:
• Quote Workflow “Negotiation Flow - Generic with Approval”
• Order Header Workflow “Order Flow - Mixed or Return with Approval”
In Release 12.2.8, AME approval for “Sales Orders” at Booking has been added by
seeding a new order header workflow "Order Flow - Generic with booking Approval"
and new sub process "Book Order – Manual with AME Approval".
Orders using transaction type with “Use Approvals Management Engine” option selected
and fulfillment flow "Order Flow - Generic with Booking Approval" assigned, will be
now sent to approvers , as determined by AME, for approval when “book order” is
initiated. At this point, order status will be updated to "Pending Internal Approval". Once
approved, eligible order will progress to Booked status. If rejected, order status will be
updated to "Review Required" and order can be modified before submitting again for
approval.
Two new header level attributes “Order_Category” and “Booked” have been seeded in
Approval Management for defining rules for the new approval flow.
Please note that:
1) If an order has been approved once, it will not be sent again for approval on
subsequent updates to it even in the case an order is re-submitted for booking if it
could not be booked previously but was approved (in previous booking process).
2) There are no changes to sales order lines flow and status when using new order
header workflow, and both outbound and return lines behave the same with respect to
status for orders created with new workflow.
3.3.10.2. Item Orderability Enhancements

In Release 12.2.8, following new capabilities have been added:
3.3.10.2.1. Add New Rule Level “Customer Class”
In release 12.2.8, user can define Item Orderability rule based on the “Customer
Class”. For this, a new attribute "Customer Classification" has been added to the rule
level list. The new attribute maps to field "Classification" on Account Receivables
Customer Setup.
3.3.10.2.2. Append Customer Number
For better identification of existing records with rules level - Customer, End
Customer, Ship To Location, Bill To Location and Deliver To Location, their values
have been suffixed with customer number while displaying the records.
For example, Bill To Location "Tulsa" may exist for more than one customer. And,
for Item Orderability Rule level "Bill To Location" value as "Tulsa" there could be
multiple records with different customers. Now, system will display Bill to Location
as "Tulsa;1006" for the record with customer number "1006".
3.3.10.2.3. Enhanced Item Orderability Public API

Item Orderability public API "OE_ITORD_PUB.Import_Item_orderability_rules"
has been enhanced to support "Update" and "Delete" Operations in addition to
existing capability of "Create" and "Insert" Operations.
Moreover, for update/delete operation, users can perform any maintenance activities
at Item Orderability level or at child rule level of it. Please note that operation Update
can also be used to enable/disable Item Orderability level setup or any child rule level
setup.

3.3.10.3.1. Enhancements to Sales Agreement Public API
Currently, users can create new sales agreement through public API
"OE_BLANKET_PUB.Process_Blanket()" using "Insert" and "Create" operations.
In Release 12.2.8, users can also perform "Update" and "Delete" operations through
this public API. With this, flexibility provided through API will be at par with the
capability currently available in sales order creation screens.
New maintenance activities that can be performed using API are:
• Update sales agreement header attributes
• Delete sales agreement
• Add lines to existing sales agreement
• Update sales agreement lines attributes
• Delete sales agreement line
3.3.10.3.2. Enhancements to "Credit Check Processor" Concurrent Program

Currently, Customer can run "Credit Check Processor" concurrent program to re-
evaluate booked orders to apply hold and/or release hold. Here, for applying hold
sales order lines in "Booked" status are considered.
In Release 12.2.8, for applying hold, Credit Check Processor will also consider sales
order lines till "Awaiting Shipping" status but not Picked yet along with existing
"Booked" status for processing.
3.3.10.3.3. Enhancements to "Order Purge" Concurrent Program
Currently, the concurrent program "Order Purge" deletes all the related order
information except order acknowledgment details.
In Release 12.2.8, there is a new option to delete order acknowledgment details as

well while performing "Order Purge".
For this, a new parameter "Purge Acknowledgments" has been added to concurrent
program "Order Purge Selection". Selecting a value "Yes" will delete the order
header and order line acknowledgement details. The existing behavior is retained by
selecting a value "No" which is also the default behavior.
In addition, the form "Purge Set" has been modified to include a new check box
"Purge Acknowledgment" to display whether order acknowledgment details are
selected for purging in the current Purge Set.
3.3.10.3.4. Enhanced Related Items Window

In release 12.2.8, a new folder enabled field "Request Date Qty" has been added on
the Related Items window to display available quantity on requested date. This
quantity is returned by the ATP.
The new field has been added on following screens:

• Related Items window on sales order form
• Related Items window on quick sales orders form
• Related Items window on pricing and availability form
• Related Items window on sales order HTML UI
3.3.10.3.5. Enhanced Fulfillment of Bill Only Lines

As per standard functionality, sales order lines with "Bill Only" flows like "Line
Flow - Generic, Bill Only" and "Line Flow - Generic, Bill Only with Payment
Assurance" are fulfilled and closed immediately as and when the order is booked.
In Release 12.2.8, there is a new option to

- Hold the fulfillment of a line until a desirable time, or
- Cancel the line if the line need not to be progressed further
For this, two new Line flows "Line Flow - Generic, Bill Only with Wait to Fulfill"
and "Line Flow - Generic, Bill Only with Payment Assurance and Wait to Fulfill"
have been seeded.
Now, using these new workflows, Bill Only lines after Booking will wait at a block
activity till the user manually progresses the line for fulfillment with "Fulfill Line -
Eligible" activity from the sales order creation screens.
Alternatively, user also have the option to cancel the line at this point if required.
Lines with standard items, shippable items of models and kits, and service lines
having the reference line in another order will wait at the block activity through new
flows. The non-shippable lines of models and kits, and the service lines referencing
another line in the same order will not be blocked by new flows as such lines will
wait for fulfillment of the dependent shippable lines as per existing design.
3.3.10.3.6. Enhanced Hold Management of Bill Only Lines
Currently, new sales order lines including "Bill Only" lines are evaluated for an
automatic hold if a hold source exists with a hold defined on the "Ship-Line"
workflow activity.
In Release 12.2.8, new sales order lines will be evaluated for an automatic hold based
on the value of existing "Bill Only" checkbox on the OM transaction type setup.
Now, Bill Only lines setup with "Bill Only" checkbox selected on the OM transaction
type will not go on automatic hold for the hold source with a hold defined on the
"Ship-Line" workflow activity.
Please note that the manual hold can still be applied on Bill Only lines as per current
design.
3.4. Oracle Order Management Information Discovery

3.4.1. Release V4
Oracle Order Management Information Discovery is available through the “Information
Discovery” tab in Order Information Portal (OIP). There are three sub-tabs/pages: Open
Orders, Closed Orders and Returns.
Oracle E-Business Suite Order Management Information Discovery empowers order
fulfillment managers, supply chain analysts and business users with the ability to identify
and process delayed orders thereby reducing fulfillment time, maximizing revenue and
ensuring customer satisfaction. In addition, users can analyze product returns to
eliminate them in the future and avoid lost revenue.
Key Features & Benefits:
• Search and process delayed orders
• Key metrics of projected fulfillment delays, associated order value and number of
orders
• Analyze product returns
• Wide range of parameters for multi-faceted analysis of orders and returns
• Search on unstructured order information including attachments and descriptive
flexfields
• Fully integrated with Oracle E-Business Suite
3.4.2. Release V6
3.4.2.1. Customer Explorer

Customer Explorer is a new functional bolt-on feature of Order Management Information
Discovery. It has two major features:
3.4.2.1.1. Customer Search
This feature allows users to find the “right” customer party by using party, account,
address, contact point and relationship attributes. The search results are provided as
the user enters the search criteria without having to press Enter. The user can also
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management Information Discovery 34
search using party (HZ_PARTIES) flexfields. Hence, this feature saves users time by
using one field to search across key customer attributes.
The user can view the related customers, customer contacts and can view the
customer addresses on a map. From the search results, you can drill into the
Transaction Summary page to view the Customer 360.
3.4.2.1.2. Customer 360
This feature allows users to view useful summarized transactional metrics related to
Open Claims, Closed Claims, Budgets, Sales Orders, Return Orders, Service
Requests, Quotes and Installed Base for a customer party. From the Transaction
Summary page, the user can drill into the related Information Discovery applications
for Open Claims, Closed Claims, Budgets, Sales Orders, Return Orders, Service
Requests, Quotes and Installed Base to view and update transactions in the respective
Extension pages.
Customer 360 increases customer service levels with full visibility to customer
transactions including sales and return orders, service requests, quotes, claims,
budgets, and install base. It improves efficiency by drilling into related Information
Discovery applications to view and update transactions.
3.4.3. Release V7
3.4.3.1. Order 360 View

Order 360 View is a new feature that allows users to search on and view metrics and
details related to Purchase Orders and Work Orders directly in the Order Management
Information Discovery page. In addition, users can select multiple orders/order lines and
drill into additional information in the following related Information Discovery pages:
• Purchasing
• Work In Progress
• Inventory Plan Fulfillment
• WMS Plan Fulfillment
• Inventory Track Fulfillment
• WMS Track Fulfillment
• Receivables
3.4.3.2. Customer Explorer

3.4.3.2.1. Customer 360
In addition to the existing metrics, users can view useful summarized transactional
metrics related to Service Contracts and Finance Contracts for a customer party.
From the Transaction Summary page, the user can drill into the related Information
Discovery applications for Service Contracts and Finance Contracts to view
transactions in the respective Extension pages.
3.4.4. Release V8
3.4.4.1. Advanced Search Capabilities

In this Release, Order Management Information Discovery users will have greater
flexibility to filter the records using a combination of additional criteria like “Boolean
Search”, “Partial Search”, “Show More”, “Exclude all” and “Select All”. The new
capabilities added are:
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management Information Discovery 35
• Partial search support for value search from both available refinements or type-ahead
suggestions
• Partial search support for record search
• Partial search support for record search with Boolean expression
• “Exclude All” capability per attribute on available refinements
• “Select All” capability per attribute on available refinements
3.4.4.2. Performance improvement of Graphs

Due to a number of performance improvements, full load and incremental load graphs
will now be significantly faster to load.
3.5. Oracle Mobile Sales Orders for Oracle E-Business Suite

With Oracle Mobile Sales Orders for Oracle E-Business Suite, sales staff can view latest
customer sales order status and take action on the go.
• View orders via my customers list
• Search orders by key attributes (customer, customer PO#, quote #, order#, status,
and product)
• View order and line details and status (customer, product, pricing, holds,
shipping, invoice)
• Monitor shipment alerts for holds and back orders
• View invoices for the selected order
• Collaborate in transaction context with device features such as email, phone, and
text
Oracle Mobile Sales Orders for Oracle E-Business Suite is compatible with
Oracle E-Business Suite 12.1.3 and 12.2.3 and above. To use this app, you must
be a user of Oracle Order Management, with mobile services configured on the
server side by your administrator.
3.5.1. Mobile Release 1.0
3.5.1.1. Accessibility Improvements

• Improvements in springboard labels and Search LOV headers
3.5.1.2. Mobile Application Foundation Updates

• Improvements in login and configuration flow
• Ability to change the URL without having to reinstall the app
• Diagnostics improvements
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Mobile Sales Orders for Oracle E-Business Suite 36
3.5.2.1. Android Support

In previous versions, Oracle Mobile Sales Order for Oracle E-Business Suite was
available only for iOS devices. Starting with version 1.2.0, the app is now available for
Android devices as well.
3.5.2.1. Mobile Foundation Release 3.0 Updates

• Changes to support both iOS and Android with the same client code
• Ability to update server URL from Connection Details page
3.5.3.1. Enhanced Line Details Page Layout

The layout of the item card view in Line Details page has been enhanced.
3.5.3.2. Added Adjustments Details Pages for Order Header and Line Adjustments
Two new pages have been added to show order header and line adjustments. New Order
Header Adjustments page can be accessed from Adjustments field at Order Summary
page whereas, new Line Adjustments page can be accessed from Adjustments field at
More Details page.
These pages show list of adjustments indicating Modifier Name, List Line, Adjusted
Rate, and Adjusted Amount.
3.5.3.3. Added Default Content in Emails

When Email icon is tapped in Contact Card pop-up at Order Summary or More Details
page, we now show the email page with default email content. Default email content
differs based on which contact card was accessed; Order Contact or Line Contact.
For an email to order contact, we default order related information; e.g. Order Alerts,
Order Status, Order Total, Order Adjustments. For an email to line contact, we default
line related information; e.g. Line Alerts, Line Quantity, Line Selling Price, Line Total,
Line Adjustments.
3.5.3.4. Translation Support

This app is available in the following languages:
Brazilian Portuguese, Canadian French, Dutch, English, French, German, Italian,
Japanese, Latin American Spanish, Simplified Chinese, and Spanish.

• Support for enterprise distribution
• Customization support for corporate branding
• Support for Web SSO authentication to delegate authentication to Oracle Access
Manager (OAM)
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Mobile Sales Orders for Oracle E-Business Suite 37
3.5.4.1. View Invoice for the selected Order

User will be able to view list of invoices and total pending balance from all invoices
associated to order header and order lines.

• User installation and usage metrics for administrators
• Updated look and feel for selected app interactions
• Technical updates with uptake of Oracle Mobile Application Framework (MAF)
2.2.2

• Opening Links to External Websites Within an App on Android Devices
• Clearing User Credential Fields
• Uptake of Oracle Mobile Application Framework (MAF) 2.3.1
• Separate Privileges for Developers and Administrators in UI
3.6. Oracle iStore

3.6.1. Overview
Oracle iStore is an electronic commerce application that enables companies to build,

manage, and personalize powerful, global and scalable Internet storefronts. Oracle iStore
may be used in Business-to-Business (B2B), Business-to-Consumer (B2C) and Partner
selling models. With seamless integration to Oracle's CRM and ERP applications, Oracle
iStore provides complete order and inventory management, and enables the execution of
the sales process, from lead generation to post-sales support.
3.6.2. Release 12.1.2

3.6.2.1. Product Comparison
Oracle iStore provides the ability to compare two or more products side by side.
This enhancement provides users the ability to select items from the product catalog and
display a product comparison page showing the products selected and their attributes.
On the Product Comparison page,
• Users have the ability to highlight the features they feel are important for each of
the products being compared. The total score for each product is computed by
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iStore 38
adding the number of features highlighted for the product. The total score for
each product provides an additional data point in the product selection process
and the user may go with the product with the highest total score.
• Users have the ability to arrange the products being compared.
• As a result of this comparison users have the ability to select a product, the
quantity, and add it to the shopping cart.
The Oracle iStore Administrator has the ability to establish an unlimited number of user
defined attributes and groups to be used in product comparisons, thus extending the
product attributes that are available in the inventory master.
3.6.2.2. Automated Password Generation for Secondary Users
Oracle iStore provides the automatic generation of passwords when a primary user
creates a secondary user, and the ability to reset the password for a secondary user.
This enhancement eliminates the need to specify the password when creating the
secondary user.
3.6.2.3. Automated Assignment of Roles and Permissions
Oracle iStore provides the automatic assignment of application roles and responsibilities
when a primary user creates a secondary user.
This enhancement provides Oracle iStore installations the ability to automatically assign
defaulted roles and permissions when creating a new secondary user. The assignment of
roles and permissions has traditionally been a manual process; sometimes the primary
user may forget to include this step. This enhancement eliminates the extra step, thus
streamlining the secondary user creation process.
3.6.2.4. Check for Duplicate Contacts
Oracle iStore will check for a duplicate contact record in the Trading Community
Architecture (TCA) customer master when creating a secondary user.
This enhancement detects duplicate contact records by checking the contact’s email
address against the user repository.
This allows the primary user to make modifications to the secondary user’s contact
information without introducing a duplicate contact.
3.6.2.5. Payment Book Enhancements
The Payment Book functionality in Oracle iStore allows users to create, update and delete
credit card preferences. In this release, Oracle iStore provides administrators the ability to
disable the Payment Book facility and not retain or display credit card preferences.
This enhancement allows the Oracle iStore Administrator to selectively turn off the
Payment Book capability for selected B2B users. Additionally, the Payment Book
capability can be completely turned off for B2C users. If the Payment Book is disabled,
then the Oracle iStore application prompts the user for their credit card information
during the checkout process.
3.6.2.6. Copy Product Content Components
Media that is displayed within Oracle iStore is defined by an administrator, using Oracle
Content Manager to create and maintain content housed in a central repository. Media
content such as images, banners, schematics, data sheets, etc. is assigned to products
through the use of content components within Oracle iStore. When new products are
introduced through Oracle iStore, the administrator will establish the mapping
relationships between the product, its associated media objects, and the actual set of
graphical images to be displayed through the Oracle iStore user interface. Currently, this
is a manual task which the administrator must perform on a product by product basis; this
can result in a very time consuming set up process. The copy product content
components enhancement enables the administrator to take existing media objects and
graphical images for an existing product and copy it across multiple new products.
This enhancement eliminates the repetitive steps needed when defining product media
content. The administrator can now bulk copy media content from one product to many
new products, thus streamlining the set up definition process for seeded and custom
content components.
3.6.3. Release 12.1.3

3.6.3.1. One-Click Shopping List Management
Shopping lists in Oracle iStore are non-transactional entities that contain products which
the end user may wish to purchase, and also help to enable future repeated purchases.
Currently users must add products to their shopping cart, convert the cart to a new
shopping list or add the product directly to an existing shopping list.
In 12.1.3 we have provided a one-click shopping list management capability, making the
shopping list management process more streamlined and intuitive. Users can now add a
product directly to an existing shopping list or a brand new shopping list with a single
click, eliminating the extra steps required in earlier versions of iStore.
3.6.3.2. Product Detail Pop-up
When browsing the product catalog pages within Oracle iStore, a user may want to view
additional information and attributes for a given product in order to make an informative
purchasing decision. Viewing this information required the user to click on a product
hyperlink to display the product details on a separate page. The product detail pop-up
enhancement introduces a new user interface control that provides a pop-up window
when the user selects a new detail icon. Upon invoking this new user interface control,
the user can view more information about the product, and can add that product directly
to the shopping cart.
This enhancement eliminates the need for the Oracle iStore user to navigate to the
product detail page in order to see additional information for a given product.
3.6.3.3. Add To Cart Navigation
Currently, Oracle iStore shopping carts enable users to select products when placing an
online order. As user decides to purchase a product, they place it in their shopping cart
by clicking on an “Add to Cart” button. This adds the product to the shopping cart, but
also navigates the user to the shopping cart page. This navigational behavior can be
distracting because the user loses the product catalog context upon adding products to the
shopping cart.
The Add To Cart Navigation enhancement simplifies the shopping cart process flow by
allowing the Oracle iStore user to add products to their shopping cart while remaining
positioned on the current product catalog page. This enhancement streamlines the
shopping cart process flow by eliminating additional steps.
3.6.4. Release 12.1.3+

3.6.4.1. Multi-customer Access
Oracle iStore Multi-customer Access provides an iStore B2B user the ability to view and
place orders on behalf of multiple customers using a single login ID. The B2B user can
log in to the iStore Customer application and can interact with their default customer, and
if given access to additional customers, can then use a new Switch Customer interface in
the Welcome Bin to change the context of their customer and place orders or view order
history for the “switched” customer.
This enhancement eliminates the need to establish separate B2B user logins for each
customer that the user needs to transact with, and leverages the Trading Community
Architecture (TCA) which supports user responsibilities and roles for “Self Service
Users”.
This feature is forward-ported to 12.2.4.
3.6.4.2. Direct Item Entry Enhancement
Oracle iStore’s Direct Item Entry page supports the use of Cross Reference Type and
Cross Reference Part Number when specifying the product. This enhancement allows
B2B users the ability to specify their own familiar part number instead of having to know
or remember the internal inventory item number on the merchant’s iStore site.
With this enhancement, B2B users can specify the product on the Direct Item Entry page
in one of the three ways:
• Customer Item Cross Reference

• Cross Reference Type and Cross Reference Part Number
• iStore merchant’s internal Inventory part number\
The above information is passed to Order Management when the cart is placed as an
order in Order Management.
3.6.4.3. Mandatory Purchase Order Number
During the checkout process, Oracle iStore merchants have the ability to enforce that a
purchase order number be specified on the B2B and B2C Billing pages. This new feature
within Oracle iStore can be enabled through the use of a new profile option.
The mandatory purchase order enhancement helps streamline the order and fulfillment
processes and prevents orders from failing when a purchase order is mandatory on the
Sales Order.
3.6.4.4. Shopping Cart Purge

This feature was back-ported from 12.2.4. Refer to the full feature description under the
12.2.4 section for Quote Purge in the Quoting product.
3.6.5. Release 12.2
3.6.5.1. Carousel Views for Related Products
Oracle iStore users can be presented with a list of related products within the product
detail page, as well as the shopping cart page. The user must then scroll through a
potentially long list to review the related products. The Carousel View enhancement
provides an alternate way of displaying long lists of related products by introducing a
sliding carousel control; this allows the Oracle iStore user to review the list of related
products horizontally. The user can toggle between the “List” view (which is the current
application behavior), and the “Carousel” view.
This enhancement eliminates vertical scrolling and takes advantage of the screen “real
estate”. The carousel view provides a more streamlined and less cumbersome interface
when viewing related products.
3.6.6. Release 12.2.4

3.6.6.1. Shopping Cart Purge
This feature allows the user to purge shopping carts. Refer to the full feature description
under the 12.2.4 section for Quote Purge in the Quoting product.
This feature is back-ported to 12.1.3+.
3.6.7. Release 12.2.5
3.6.7.1. Address Search Enhancement
This feature provides Oracle iStore users the ability to search on additional fields when
selecting Ship-To, Bill-To and End Customer addresses during the checkout
process. This enhancement alleviates the need to scroll through a long list of addresses to
quickly locate the proper address. The address search enhancement reduces shopping
cart checkout time and improves efficiency by streamlining the address selection process.
3.6.7.2. Line Level Promotions
Offering discounts and coupons are a vital marketing strategy for Oracle iStore
merchants. The line level promotion feature allows Oracle iStore users to enter
promotion codes for individual items in their shopping cart. This enhancement enables
users to apply multiple promotion codes for a single item in their cart in addition to
specifying promotion codes at the shopping cart level.
3.6.8. Release 12.2.7
3.6.8.1. Order Type for a Specialty Site
Currently, the order type can be specified for an operating unit via the Quoting parameter.
Hence, each of the specialty sites within an operating unit must use the same order type.
iStore customers have use cases where specialty sites within an operating unit need to
have different order types. This enhancement removes that restriction and allows iStore
merchants to specify the order type at the specialty site level.
3.6.8.2. Email Notification Style
The email notification style enhancement provides iStore with two business benefits.
First, it allows iStore merchants the ability to specify the default email notification style
for new iStore users. This is done via a profile option. Secondly, iStore users can specify
their personal email notification style preference using the Email Address profile
preferences page.
This feature enhances iStore personalization by enabling B2B and B2C users to choose
from four different notification styles. The new notification styles are “HTML mail”,
“HTML mail with attachments”, “Plain text mail” or “Plain text mail with HTML
attachments”.
3.6.9. Release 12.2.8
3.6.9.1. Promotion Code Enhancement

Promotion codes applied at the shopping cart header level are automatically applied to all
the eligible lines. Thus, it is not possible for a merchant to control the application of a
promotion code to one line but not to another identical line in the same shopping cart.
This is a common business B2B use case where a shopping cart has identical lines with
different Ship-To locations or quantities and a promotion code that must be applied to
only one of the lines.
This enhancement provides merchants granular control on how promotion codes are used.
It allows iStore users to specify promotion codes at (a) the header level only (b) the line
level only (c) both header and line levels. The feature can be turned off as well.
3.6.9.2. Copy Prior Order Items

iStore users typically browse and search the product catalog, or copy items from a saved
list, populate the shopping cart using Direct Item Entry to add items into their shopping
cart. This can potentially slow down the purchasing and checkout process when iStore
users need to just reference items from a prior order for re-ordering purposes and place
them into their shopping cart.
The Copy Prior Order Items feature provides a means for B2B and B2C users to quickly
select several or all of the items from a prior order and add them to the shopping cart.
This makes adding items to the shopping cart more convenient by having a repeat order
capability, which streamlines the on-line purchasing experience.
3.7. Oracle iStore Information Discovery

3.7.1. Overview
Oracle iStore Information Discovery provides users with a robust search tool to
supplement the existing Basic and Advanced search functionality in iStore. It enables
users to search on customer part number, cross reference part number and locate products
easily with auto-suggested searches. Oracle iStore users can also filter on price ranges,
perform product comparisons to highlight product differences, and export search
results. It also provides sophisticated guided navigation to product information, thus
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iStore Information Discovery 43
enabling shoppers to easily choose the “right” product when making purchasing
decisions. Lastly, it delivers an intuitive interface that streamlines the buying process and
enhances the customer usability experience.
3.7.2. V6
3.7.2.1. Enhanced iStore Search

Oracle iStore Information Discovery is fully integrated with the iStore customer facing
application. A global search area is available throughout the iStore customer application,
allowing the user to perform an Information Discovery search at anytime, anywhere. The
search results are then displayed in a dedicated Information Discovery page within iStore.
Native functional operations such as drill down to view product details and add to cart are
also available. The Oracle iStore Information Discovery search facility provides end
users with a sophisticated, integrated interface that replaces the existing Basic and
Advanced search.
3.7.2.2. Customer and Cross Reference Part Number Search

Oracle iStore Information Discovery includes the ability for users to search on Customer
Part Numbers. This allows iStore users to search on products using their own familiar
part number without having to know or remember the merchant’s own internal part
number. iStore users can also search on Cross Reference Part. This allows iStore users
to search on products using cross referenced part numbers established by the merchant.
To further qualify an item’s Cross Reference Part Number, the user can also include a
Cross Reference Type to filter on the Cross Reference Part Number. Both the customer
and the cross reference part number search provides the iStore user with the capability of
utilizing alternate ways when referencing and searching on product catalog items (in
conjunction with internal Oracle Inventory part numbers).
3.7.2.3. Price and Price Range Filter

Oracle iStore Information Discovery includes the ability for users to search and filter on
Prices (Retail Price and Your Price) and Price Ranges. This allows iStore users to view
products based on the purchase price within their budget. When browsing for products,
the user can specify a price or a price range; this will display only those products that fall
within the pricing criteria. Filtering on prices provides the iStore user with the capability
of purchasing products that satisfy their financial needs.
3.7.2.4. Multiple Search Result Views

Upon performing a search, iStore users can choose the display of the search results within
a table view, list view, grid view, or carousel view. The tabular view provides the user
with the ability to examine the search results in a spreadsheet fashion, being to drag and
drop columns, and sort columns. The list and grid views enable the user to easily scroll
through the search results, while the carousel view allows the user to take advantage of
the screen “real estate” and rotate the search results in a horizontal landscape. The
various views make it easy for the end user to identify the desired items when making a
purchasing decision.
3.7.2.5. Product Comparisons

Oracle iStore Information Discovery supports a product comparison feature based on the
items that are retrieved from the search results. Users can select the products within the
search results view and perform a compare, where they can view the details about the
selected products side by side and highlight their differences.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iStore Information Discovery 44
3.7.3. V8
3.7.3.1. Enhanced Product Catalog Search Capabilities

In this Release, iStore Information Discovery users have greater flexibility to search and
filter the product catalog with a combination of additional criteria that takes advantage of
“Partial Search”, “Show More”, “Exclude All” and “Select All”. New capabilities that
have been added include:
• Partial value search in Available Refinements. Example: *text*
• Partial record search for the following attributes:
o Product Name
o Product Number
o Customer Part Number
o Cross Reference Part Number
o Cross Reference Type
3.8. Oracle Shipping

3.8.1. Release 12.1.1
3.8.1.1. Defer Planned Shipment Interface

The Planned Shipment Interface program processes the transportation plan information
passed to Oracle Shipping by Oracle Transportation Management. Companies will now
have the option to defer running this interface, in addition to the current ability to
interface the information real-time. High volumes of deliveries or frequent updates to
deliveries are potential scenarios when deferring the interface and running it periodically
may improve overall system performance.
3.8.1.2. Allow Incremental Shipments for Over-shipment and Under-shipment

Tolerances
On the sales order line, an under-shipment and/or over-shipment tolerance may be
specified to track the minimum acceptable quantity and the maximum acceptable
quantity, which may be shipped relative to the ordered quantity. This business practice is
quite prevalent in industries with variable yields or for indivisible goods (e.g. steel
ingots). When an over-shipment tolerance is specified on a sales order line, the line will
be available to ship confirm until the over-ship tolerance is reached. When an under-
shipment tolerance is specified on a sales order line, the line will be available to ship
confirm until the ordered quantity. If under-ship and over-ship tolerances are being used
together, the line will be available to ship confirm until the over-ship tolerance is reached.
3.8.2. Release 12.1.3
3.8.2.1. Fulfillment Batches for Distributed Warehouse Management System

Delivery details can now be grouped into fulfillment batches based on the criteria
selected in the 'Create Shipment Batches for Fulfillment' concurrent program. The
fulfillment batches can then be sent as a shipment request to the Distributed Warehouse
Management Systems (e.g. Oracle EBS WMS deployed in Distributed/LSP Mode) for
execution. The Distributed Warehouse Management System will need to send the
shipment advice once the shipment request is processed and executed.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Shipping 45
This enhancement also provides the ability to create and ship confirm the shipments
based on the shipment advice received from the Distributed Warehouse Management
System.
Out of the box, the ODI maps allow the shipment request batches to be sent to Oracle
EBS Distributed WMS. The shipment request output can also be used by any 3rd party
Distributed Warehouse Management System / Logistics Service Provider system.
3.8.3. Release 12.2
3.8.3.1. Integration to 3PLs or 3rd Party Distributed Warehouse Management

System
Companies who run their warehousing activities internally on a distributed WMS or
outsource their warehousing activities to a 3rd Party Logistics provider (3PL) can now
send a Shipment Request and receive a Shipment Advice via the XML Gateway. By
using Fulfillment Batches companies can communicate Shipment Requests without being
required to create deliveries on the Host instance.
3.9. Oracle Supply Chain Event Management

Oracle Supply Chain Event Management (SCEM) is a brand new Oracle Fusion
Middleware based solution available in Release 12.1.3 and above, that provides visibility
to events in every link across the extended supply chain. SCEM can correlate various
critical events originating in multitier supply chain and raise real time alerts and
notifications. Alerts and notifications are displayed on flow monitoring Business
Activity Monitoring (BAM) dashboards and are also sent as emails to appropriate users.
SCEM can track all heterogeneous systems in real-time to spot potential problem early
enabling timely response even before exceptions occur. Event routers pick up relevant
events from external event sources like B2B messages and other enterprise applications
Business rules are evaluated and abnormal events are quickly identified to the user. With
comprehensive correlated event tracking, SCEM facilitates faster decision making and
information driven collaboration with customers and partners.
3.9.1. Release 12.1.3
3.9.1.1. Order Fulfillment and Spare Parts Order Templates

SCEM provides ready to use master templates for Order Fulfillment and Spare Parts
Order flows. These built-in templates track sales order fulfillment right from order
creation through shipping and closure. In case of spare parts order flow even the original
Service Request and accompanying task is tracked along with the spare parts order. These
templates can additionally be extended to meet unique requirements, like adding a new
event to be monitored or adding a new source application to the flow. The solution also
includes a JDeveloper extension for building monitoring applications from the ground up.
SCEM solution is fully integrated with Oracle E-Business suite hence enables rapid
deployment of shipped master templates.
3.9.2. Release 12.2.5
3.9.2.1. Back to Back and Procure to Pay Templates
In release 12.2.5 SCEM introduces two new templates:
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Supply Chain Event Management 46
• Back to Back Sales Order Flow (Sell-Source-Ship) – Allows Companies to
seamlessly track Sales Orders and the resulting Purchase Order to ensure timely
delivery to Customers.
• Procure to Pay Flow – Enables tracking of end to end purchasing flow right from
Purchase Order Creation to Payment to Vendors
Additionally in release 12.2.5 a new SCEM designer Web Application is introduced that
makes the designer now available on a Web Browser for easy and quick creation and
editing of business flow templates.
3.10. Oracle Installed Base

3.10.1. Overview
Oracle Installed Base is an Item Instance life cycle tracking application and it enables product
life cycle management at the micro level. It facilitates instance tracking across different
applications and their transactions. Oracle Installed Base provides User Interfaces to easily
view instance ownership, location, change history, transaction history from a single application.
Oracle Installed Base uses ‘Counters’ to help track usage of a product or track equipment
operational details like run hours which can be used for various purposes like Billing or
Maintenance planning.
Oracle Installed Base is a foundation product for Oracle Asset Tracking and Enterprise Asset
Management.
3.10.2. Release 12.2.4
3.10.2.1. Option to track only Customer-owned products using Oracle Installed

Base
Even though Install base tracks all transactions performed on an IB tracked item, for
some organizations it is suffice to track only customer owned item instances. To support
such customer requirement, an additional option has been provided for Install Base
tracking in this release. With this option, such customers can avoid the present default
behavior that tracks both enterprise and customer instances.
These business users can leverage this new option in Install Parameters to track "Only
Customer Owned Instances" and still be able to perform after-sales transactions such as
RMA, Field Service Return on the IB instances.
By enabling this Option the IB Tracking restricts itself from creating any internal instances
and the lifecycle of the IB tracked item starts only on Order Fulfillment to external customer.
Note: Since eAM and Asset Tracking products track internally owned assets for asset
lifecycle tracking, this new option should not be adopted by customers who are using these
products.
3.10.3. Release 12.2.5
3.10.3.1. Tracking of Customer Install Base items
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Installed Base 47
The customer Install Base functionality – which lets organizations to track only
customer/party related transactions on products - was introduced in Release 12.2.4.
Extending that option as a setup at the Item level is added as part of Release 12.2.5. With
this enhancement, you would be able to specify the preference for Install Base tracking at
the master item level. This provides more flexibility to use this feature based on an
individual item’s tracking needs.
3.10.3.2. Install Base Transaction performance improvements

Install Base Transaction processing mechanism is moved away from the Service
Fulfillment Manager (SFM) queue to Install base interface based processing.
This enhancement improves the efficiency of transactions interfacing to IB, as it avoids

the dependency with other product like SFM.
3.10.3.3. Serial Tagging at Sales Order Pick support
Inventory serial tagging functionality is being extended to the Sales Order Pick
transaction in Release 12.2.5. This is applicable for non-Serial controlled Items and
Serial control at Sales Order Shipment items. Install base changes have been incorporated
to support this feature for IB tracked items as well.
3.11. Oracle Installed Base Information Discovery

3.11.1. Overview
Being able to quickly answer business questions such as ‘What products do my
customers own and where are they located?’ is important for organizations to plan better
up-sell/cross-sell campaigns and service delivery. Tracking and managing customer
products information is a critical function that improves efficiency in after-sales support
and service for Installed Base products.
Oracle Installed Base Information Discovery allows users to track and manage customer
products effectively with the objective to improve cross-sell/up-sell opportunities and
after-sales service offerings. EBS application users performing business roles of Sales
Manager / Service Manager can get the following benefits –
• Ability to plan Sales / Service campaigns
• Identify top customers and top selling products
• Manage product configuration effectively
• Access customer installed base details in real-time
3.11.2. Release V4
3.11.2.1. Search by Extended Product Attributes

This feature provides useful capability to Installed Base users to lookup products by their
characteristics or usage. By using this feature, customers can execute search based on
Extended or Additional attribute names or values that are associated to a product.
3.11.2.2. Execute ‘Related Products’ Search

This feature in Installed Base Information Discovery guided navigation is based on the
Item Relationships such as Up-Sell Product and Cross-Sell product defined between
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Installed Base Information Discovery 48
Items. This enables users to search for target products for prospective Up-Sell or Cross-
Sell sales campaigns.
3.11.2.3. Improved Drill-down to Product Configuration

Model-Components relationship between Item Instances or product hierarchy can be
identified easier with Information Discovery search parameter ‘Top Model’. This will
allow users to quickly find out all components in a hierarchy and to identify impacted
products effectively in a re-call/replacement scenario.
3.11.2.4. Identify Installed Base by Geography

Oracle Installed Base Information Discovery lets users to view and lookup the customer
products that are located in a particular geography like Country/State etc., This broadened
search feature allows users to get a consolidated view of product profiles in a geographic
region and utilize that information in after-sale activities like service planning, delivery
and deployment.
3.11.2.5. Track Customer Product Metrics

Metrics on the Installed Base data such as ‘Number of Customer Products Installed’ and
‘Average Age of the products’ provide insights into critical products and their condition.
These tracking metrics will help an organization to pursue new sales opportunities or
Upgrade actions for customer owned products
3.11.3. Release V5
3.11.3.1. User-Definable DFF Search

With this new release of Information Discovery, users will be able to search user-
definable, Descriptive Flex-Fields (DFFs). Many customers use DFFs to capture
information specific to their environment or industry that Oracle products does not
support out-of-the-box.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Installed Base Information Discovery 49
4. New and Changed Features in Contracts
4.1. Oracle Sales Contracts
4.1.1. Release 12.1.1
4.1.1.1. Secure Enterprise Search

Oracle Sales Contracts as well as Repository Contract now leverage Oracle’s Secure
Enterprise Search to better search for structured and unstructured data on sales contracts.
Business and legal users can now perform full-text queries in conjunction with structured
data queries. Secure Enterprise Search is leveraged to search by keyword in important
contract attributes, structured terms in the contract and attached documents. Applying
additional contract attributes such as contract number, contract name,
supplier/customer/party name, contract status, start date, and end date further refine the
search.
4.1.1.2. Structured Terms Authoring for Repository Contracts

Repository Contracts enable customers to easily manage all their contracts online. It
provides basic contract management capabilities and global, secure visibility to key
stakeholders. Repository Contracts is available as a part of Oracle Sales Contracts and/or
Oracle Procurement Contracts.
In Release 12, users created Repository Contracts by capturing key attributes about the
contract (like contract party, dates, amount, etc.) and managed the document files
associated with the contract. Users could also track key deliverables and contract expiry.
With Release 12.1.1, users can now author structured terms and conditions while creating
a Repository contract. These terms are based on standard templates, clauses, and policies
that are defined in the contract terms library. Users can also use the Contract Expert
feature to bring in additional clauses that may be required based on the business terms of
the particular contract. The contract can then be printed for signature, or exported to
Microsoft Word for redlining/collaboration with the external party. The deviations report
functionality will provide a quick overview of all policy violations in the contract.
Structured terms authoring promotes standards based contract authoring and reduces the
overall time-to-contract. Risk associated with non-standard contracts is also mitigated by
ensuring approvers have visibility to all policy violations.
4.1.2. Release 12.1.2

4.1.2.1. Author Individual Clauses in Microsoft Word
Legal clauses are typically managed in Word documents. Organizations using Oracle E-
Business Suite for their enterprise contract management need to be able to create and
update clauses using a rich text editor such as Microsoft Word.
With 12.1.2, users can directly create and edit the clauses in Microsoft Word leveraging
additional formatting features. Importing clause text from Microsoft Word and exporting
clause text to Microsoft Word for edit have been incorporated into both the Contract
Terms Library and the contract authoring flow.
The following formats will be preserved as defined in Microsoft Word:

• Bold, italic, text color, and underlines
• Standard bullets available in Word
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sales Contracts 50
• Numbering schemes (roman numerals, alphabets, numbers) and their indents,
including hanging indents
• List items with non-numbered text between them
• Indent and tabs (Tab spacing/width is determined based on style sheet
information)
• Line spacing
• Text alignment (left, right, and center justification)
• Table formatting
• Hyperlinks, page breaks, and symbols defined in Unicode
This feature requires Microsoft Word Professional 2003 or 2007.
4.1.3. Release 12.1.3+

4.1.3.1. Templates, Rules, Questions and Constants APIs
Importing and updating templates, rules, questions, and constants from external systems
is supported using APIs. There are separate APIs for:
• Templates
• Rules
• Questions
• Constants
4.1.3.2. Contract Terms and Conditions Migration API
The procedures in the Contract Terms and Conditions Migration API are used to apply
templates to a document. Users can add clauses and sections to the document. In addition,
attaching a document as the primary contract document is also possible.
4.1.3.3. Contract Expert Enhancements
The following enhancements have been made to Contract Expert which supports
automation of the contract drafting process:
• Now it is possible to specify if the clause suggested by Contract Expert is
mandatory or not at the rule definition level. If this is empty, template level setup
will be used to determine whether a Contract Expert suggested clause should be
added as mandatory or optional.
• Users can specify based on attributes of the document which section a clause
should be automatically added to by Contract Expert. In the clause creation flow,
the user can specify a variable name which is an attribute of the document, for
example the document format value for printing (see below). The user can now
specify different sections for different values of that variable (example Section A
for value UCF, etc.). When the clause is added to the document by the Contract
Expert, the clause will get added to the section based on the value of the variable
of the document.
• A new rules infrastructure, the Contract Rules Evaluation Engine, is now

available to support customers requiring high performance from the Contract
Expert feature. A new profile option “OKC: Use Contracts Rules Engine” will
control whether the new Contract Rules Evaluation Engine or the original Oracle
Configurator rules engine will be used. This is applicable for both rules
activation and runtime of the Contract Expert feature. This feature is forward-
ported to 12.2.2.
4.1.3.4. Enhancements MS Word Synchronization
Often it is convenient during negotiation and redlining to edit the contract offline in a
word processor. Contract administrators or legal will download the contract into
Microsoft Word for redlining and collaboration and upload the changes made. MS Word
Synchronization is now available for contracts having clauses which were originally
authored in MS Word and imported. This feature is forward-ported to 12.2.2.
4.1.3.5. Apply Multiple Templates to a Sales Document
Previously the system allowed the user to apply only one sales contracts template to the
sales document. The user could change the template if needed. However, often an
organization may have multiple templates which need to be applied to a document. This
new feature allows the user to select and apply multiple templates to the document. All
the clauses from the new templates flow into the document. The user can also view the
different templates that have been added to any document.
4.1.3.6. Multi Row Variables
Users can create user defined manual variables that are tables containing one row per line
or multiple rows. Contract Preview will print the variable values according to the layout
defined for the variable. These variables are not available for Contract Expert Rules. One
example of how multi row variables can be used is that users can create dependent
variables and then integrate those variables to user-defined attributes.
4.1.3.7. Deviation Report for Repository Contracts
Deviation Reporting is now available for Repository Contracts, both as a download and
attached to approval notification. Standard terms may be modified during contract
negotiations, resulting in deviations from company standard policies. For example, a
company may require special approvals for refund terms beyond thirty days. Deviations
in standard terms are also reported in addition to clause deviations to ensure proper
visibility during review and approvals. Business practice organizations can setup these
policy rules and enforce them across the enterprise. The rules can be based on user-
defined variables or responses to other questions asked during the contract authoring
process. These deviations are reported together with other clause deviations in a single
report that can be included for approvals. For each deviation, the report also includes
information on what the standard values should be, and any additional approvals that may
be required. This feature is forward-ported to 12.2.2.
4.1.3.8. Clause Analysis for Repository Contracts
Clause Analysis is now available for Repository Contracts. Legal or Finance may want
to quickly identify all existing contracts that use a certain language that is considered
risky to accurately determine risk exposure. Analyzing the contract language may also
help in revising existing standards to streamline future contract negotiations or reduce
risk. For example, companies can identify the clauses that have been modified the most,
and either revise them to be compliant with industry standards or enforce tighter controls
to avoid such modifications. Users can search for all contracts where certain clauses are
used, or have been modified. The search can be narrowed using various criteria like
contracts with a specific customer, contracts above a certain amount, or contracts
authored using a specific template. Information on the number of times a certain clause
has been used or modified is also provided as part of the results. The results can be
summarized by clause type or clause title and exported to Microsoft Excel for further
analysis. This feature is forward-ported to 12.2.2.
4.1.3.9. Contract Usability Enhancements
The following usability enhancements have been made to improve user productivity:
• Users can view the clause number in the following pages: Add Clause, Contract
Expert Summary, Structured Terms, Update Variables, and Validation Results
• Users can sort the clauses in each section based on the clause number.
Additional flexibility to specify tailored sorting rules is supported by the hook
OKC_CODE_HOOK.sort_clauses.
• Users can create a hyperlink in the Instruction Text column of a clause, click on
the hyperlink, and navigate to an external page.
• Users can add the Clause Description field to the Contract Template, Rules
definition and Contract Terms pages. By default the field is hidden. This field
can be updated from the Contract Template and Rules definition pages. The list
of values for this field comes from a user-defined lookup.
• To support driving contract compliance, the list of all approvers and history of
actions is now available on the Repository Contracts History tab.
4.1.3.10. Contract Expert Performance Improvements

The Contract Expert engine now has improved performance of the complete flow.
Impacts include faster UI and better formatting of the question and answer fields. There
is no change to the Contract Expert process itself. This feature is forward-ported to
12.2.3.
4.1.3.11. Contract Expert History

Contract Expert History allows buyers to view the Contract Expert questions, the
responses provided, and the resultant policy deviations and net clause additions. For
revisions in orders or amendments in a Sourcing document, the user will also be able to
enter the amendment description and also view it in the Contract Expert summary page.
This capability will simplify audit requirements and will provide details around the
responses provided and changes in different revisions and amendments. This feature is
forward-ported to 12.2.4.
4.1.3.12. Delete Multiple Clauses, Sections and Deliverables

A delete function on the Contract Terms page allows users to delete multiple clauses,
sections and deliverables from a draft document. Clauses marked as mandatory will not
be allowed to be deleted. This feature is forward-ported to 12.2.4.
4.1.3.13. Purge Process for Repository Contracts

The contract administrator can purge selected contracts using the Purge Repository
Contracts concurrent program. Users can purge a contract only if the status of the
contract is terminated, cancelled or rejected, or if the contract has expired. This
concurrent program deletes the selected contracts and all related entities. This feature is
4.1.4. Release 12.2
4.1.4.1. Repository Contracts Enhancements

Repository Contracts has been re-designed to provide greater flexibility and improved
capabilities to the contracting professional. The contract administrator can now control
the different entities that are available for each contract type. The addition of custom
signature and approval workflows for each contract type greatly enhances the
applicability of repository contracts in different business scenarios. Repository contracts
also support UDA (User Defined Attributes) pages. So, each contract can contain
multiple additional pages to capture specific business information. This will allow the
repository contracts to be used as a solution for modeling different document
management requirements along with their own process lifecycle. Customers can
leverage repository contracts to integrate them within their existing business flows in
different application modules.
4.1.4.2. UDA support for Deliverables

UDA (Used Defined Attributes) can now be added to deliverables. This will allow
organizations to model and capture relevant information in the context of a deliverable.
This will be available in both Repository.
4.1.4.3. MS Word 2010 Certification

The clause and contract terms sync process is now certified for Microsoft Word 2010.
Users can now download and view clauses and contract terms in MS Word 2010 and also
upload documents edited in MS Word 2010
4.1.5. Release 12.2.4
4.1.5.1. Repository Contracts Printing Enhancement

UDA (User Defined Attributes) fields may be used to capture additional data for each
contract type. The Contract Type setup page now allows the contract administrator to
specify the manner in which UDA attributes are printed by selecting appropriate data and
layout templates.
4.1.6. Release 12.2.5
4.1.6.1. Updating UDA on Approved Contracts

Repository Contract users will be able to add information or update existing values of
user-defined attributes of the contract even after the contract is approved. Users can
configure whether these user defined attribute groups are read only or can be updated
based on the Status of the Contract. The different statuses for which this can be
configured are “Pending Approval”, “Approved”, “Pending Signature”, “Signed”,
“Terminated” and “Cancelled”.
4.2. Oracle Service Contracts

4.2.1. Release 12.1.1
4.2.1.1. Service Contract Import Program

Oracle Service Contracts now offers a feature to import Warranties, Extended
Warranties, unbilled or fully-billed Service Contracts and intangible Subscription
Contracts. This capability allows a service contract to be captured from an external
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Service Contracts 54
system. Once the service contract has been imported, Oracle Service Contracts can be
used for Entitlements and Billing.
4.2.2. Release 12.1.3+
4.2.2.1. Service Contract Renewal Performance Enhancements
4.2.2.1.1. Date Assembler Changes
Currently when a large number of service contracts expire on the same date and
simultaneously need renewing, it can take a long time for the renewal process to
complete. To improve the performance of the service contract renewal process, the
Date Assembler Workflow Manager feature controls the number of service contracts
to be processed concurrently for renewal.
Instead of creating a workflow process for each service contract to be renewed, the
date assembler will insert the details into an interface table and then specific numbers
of workflow processes are created to process the renewal. A new concurrent request
“Service Contracts Date Assembler Workflow Manager” has been introduced to fetch
data from the above mentioned interface table and create the workflow processes for
service contract renewals. The number of records to be fetched is controlled by a new
profile option “OKS: Date Assembler Workflow Queue Size.”
4.2.2.1.2. Re-Pricing enhancements
Oracle Service Contracts has made performance enhancements to the re-pricing of
service contracts during contract renewal.
• Re-price in bulk mode: Bulk mode features will be leveraged to re-price
service contracts. A new profile option “OKS: Use Bulk Loading for Line
Re-price” has been introduced to enable bulk mode re-pricing.
• Re-price in concurrent mode: If the number of lines/sub lines crosses the
pre-defined threshold value, service contracts will be re-priced in concurrent
mode. The threshold is controlled by a new profile option “OKS: Subline
Threshold Value to Launch a Concurrent Program.” When the number of
lines/sub lines cross this threshold then the re-pricing will be done through a
concurrent request to improve the pricing performance. This feature is also
available for manual/automatic renewal processes.
4.2.2.2. Performance Enhancements to Main Billing Program for Usage
Contracts
Oracle Service Contracts has made performance enhancements to the pricing of usage
contracts during the Main Billing Program. When there are a large number of usage
lines, then the Advanced Pricing engine will be called in bulk mode for the eligible lines.
New profile options have been introduced to manage this process:
• OKS: Call QP In Bulk Mode for Usage Line Billing to enable calling the
Advanced Pricing engine in bulk mode
• OKS: Skip QP call in Usage for Zero Quantity to determine whether zero
quantity lines are interfaced to Advanced Pricing
• OKS: Number of Child Requests for Service Contracts Main Billing to control
the number of child requests to be spawned. The default value is 30 in order to
maintain backward compatibility.
4.2.2.3. Mass Update Tool
A new Mass Update Tool, which is available from the Service Contract Authoring form,
can help users manage service contracts with a large number of lines/sub lines. Users can
sort and then update individual lines or a group of lines – such as all lines, all lines for a
configuration, or all lines for a given serial number. Changes are processed in the
background, so that the user can immediately continue onto their next task.
4.2.2.4. Prevent Deletion of Line/Sub line during Contracts Renewal
Oracle Service Contracts has introduced the ability to disallow deletion of lines/sub lines
during contracts renewal to improve contract revenue leakage analysis. When the
customer does not want to continue a service, the line/sub line should be cancelled during
the renewal process. Disallowing deletion of renewed lines/sub lines will ensure users
are properly cancelling lines/sub lines. Administrators and management have the ability
to configure which users will not be allowed to delete lines/sub lines during contract
renewal process.
This is managed using the profile “OKS: Delete Renewed Contract Lines or Sublines.”
When the profile is set to ‘No’, then the user will be required to cancel lines using an
appropriate status value along with an appropriate reason for cancelling the line.
4.2.2.5. Carry Over Self-Service Decline Code onto Service Contract Cancellation
Reason
When customers decline to renew service they select a decline code. This decline code
will now carry over onto the service contract cancellation reason to improve contract
revenue leakage analysis.
4.2.2.6. Revalue Contract during Change in Currency
A new profile option “OKS: Revalue Contract Using Currency Conversion Rate” allows
users to configure whether to automatically re-price or allow manual revaluation when
the currency is changed on a service contract.
4.2.2.7. Specify Cc E-mail Addresses during Quote and Reminders
Users can specify cc email addresses for email quote and reminders as a part of the
contract renewal process.
4.2.2.8. Selective Update of Warranty Contracts upon IB Transfer of Ownership
In certain business scenarios the service during warranty period is provided by the OEM
and during extended warranty is provided by a Partner. In such cases, this feature allows
you to update only the warranty contracts upon IB transfer of ownership. This feature is
4.2.2.9. Re-price on Renewal Consolidation
As a part of Renewal Consolidation, only the lines/ sub lines that are moved from the
Source to the Target Contract are Re-priced as per Target contract’s Price List. All the
lines existing on the Target contract prior to Renewal Consolidation exercise are not re-
priced automatically. This feature is forward-ported to 12.2.4.
4.2.2.10. Flexible Invoice Text Defaulting
A new profile option “OKS: Update Invoice Text during Renewal” allows users to
configure whether the invoice text will be defaulted from the original contract or the
renewed contract.
4.2.2.11. Service Contracts Usability Enhancements
The following usability enhancements have been made to improve user productivity:
• When adding sub lines to an Extended Warranty service line, the Product List of
Values shows available instances with several different sort sequences to choose
from: Party, Site, Customer, System, Item and Model. Now Configuration will
also be an option which displays available instances based on the installed base
configuration. It shows top level instances and allows the user to drill down to
see all instances in the configuration. As with other levels, users should be able
to select one or more displayed instances to add to the contract.
• The cascading attributes action has been enhanced to support concurrent
processing. When a service line had a large number of sub lines, users were
forced to wait until the entire cascade action completed. Now users can specify
attributes to be cascaded to all sub lines in the Cascading Attribute form, and the
user can continue updating the contract while the concurrent program completes
in the background. This is managed through a profile “OKS: Cascade Attributes
Using Concurrent Request.” In the case of the user changing the Effectivity Date
on a service line, then using this feature the user can default the same effectivity
date to all the associated sub lines.
• Users can review the contract details from the FYI (For Your Information)
notification page. When a FYI notification is received by an external user, then
the user can access the contract details link on the notification and launch the
Contract Details page. The user can launch the page only if he/she has access to
the contract.
• During entitlement search, users have the option to view the subscription
contracts having service lines covering item instances. This is managed using the
profile option “OKS: Display Subscription Contracts in Entitlements.”
• During entitlement check, the Respond By and Resolve By dates are returned to
the service request even when they fall outside of the contract coverage effective
start date and end dates.
• During entitlement check, the calculation of ‘Response By’ and ‘Resolve By’
time takes into consideration the customer’s availability defined in the ‘Access
Hours’ setup in Field Service application.
• Users can view the line and sub line number in the status change history page.
• Users can update the billing streams based on the original billing streams
duration. Also, the end date gets adjusted to match the new end date for the line.
• Users can now view the Card Holder’s name for the card specified in the
Payment Method – both at the header as well as contract lines. The card holder’s
name is shown in the Credit Card Number LOV while selecting the credit card.
In addition, if the user is required to enter the details for a new credit card, they
can specify the card holder’s name. This feature is forward-ported to 12.2.4.
• Users can now choose to display either the item description or item part number
in forms as well as HTML pages. This is controlled via the profile option ‘OKS:
Line Level Item Display Preference’.
4.2.2.12. Merge Assets across Contracts
Contract consolidation can have multiple business drivers, such as customer’s request,
installation location of a group of assets etc. Users can now move assets from multiple
source contracts, to a single target contract. This helps in improving the maintainability
of customer contracts, and avoids duplication of assets across the contract base. The
movement of assets is recorded in the execution history of the source contracts.
A new profile option “OKS: Change Party in Contract Merge” allows users to move
assets across the customer base. The re-pricing of the assets moved to target contract is
controlled using “OKS: Pricing Method for Contract Merge” profile option. This feature
is forward-ported to 12.2.4.
4.2.2.13. Drive Contract Coverage by Severity
There might be business need to cover High priority tasks round the clock, but it doesn’t
justify providing similar coverage to a Low or Medium priority task. Oracle Service
Contracts now provides the capability to define contract Coverage Time, Reaction Time
and Resolution Time based on the severity of the task. This enables service organizations
in providing assistance to tasks as per the severity. This results in cost savings by
avoiding manual interventions that are otherwise needed for modifying the planned end
dates and rescheduling tasks as per the severity.
Prior to this release, users defined Reaction and Resolution Times based on specific
number of hours it took to respond to a task. With this release, Reaction and Resolution
Times can be defined as variable number of hours depending on when a task gets created,
thereby ensuring compliance with the promised service level agreements. This feature is
4.2.2.14. Control Generation of Invoice
In certain geographies, such as Latin America, the customers accept invoices only till a
specific day of the month after which they are sent back to the service provider. With this
release, the application provides users the ability to specify the range of days on which
the invoices are accepted by the customers. Any invoice falling outside this range is sent
to the customer in the next billing cycle.
A profile option “OKS: Enable Interface Date Range” with a value of ‘Yes’ enables users
to honor customers’ invoicing preferences by recording the range of days on which the
invoices are accepted by the customer. This feature is forward-ported to 12.2.4.
4.2.2.15. Calculate Estimated Tax with Higher Accuracy

The tax rate and its effectivity can change over the contract duration. Hence, service
organizations need to provide an accurate picture of the estimated tax that the customer
might end up paying. Prior to this release, the application calculated the estimated tax
based on the line/ sub line start date. With this release, Oracle Service Contracts provides
users with an option to calculate tax at contract billing schedule level thereby considering
the changes in tax rate effectivity at that level.
A profile option “OKS: Calculate Tax at Schedule” with a value of ‘Yes’ enables the
application to calculate tax at billing schedule level for all lines/ sub lines. This feature is
4.2.2.16. Close Request for Assistance

During the contract negotiations or renewals, Oracle Service Contracts allows customers
to “Request for Assistance”. Whenever such a request is made, the system records this
request in the Contract History and the Sales Rep is notified. Once the Sales Rep is able
to address the needs of the customer, the Sales Rep can initiate the “Close Request for
Assistance” process. Option is provided to the Sales Rep to send a confirmation email to
the customer and even add the quote to the email. The system displays a Confirmation
Message when the process completes successfully and a record is made in the Contract
history, emails are sent if opted for and the Contract’s Negotiation Status is set to “Quote
Published”.
4.2.2.17. Withdrawal of Published Quotes
There is a need for a Sales Rep to retract a published contract. The application now
provides the Sales Rep a “Withdraw” capability for withdrawing the quote that has been
published to a customer. The Sales Rep can choose to provide an explanation as to why
this is being done. A Confirmation Message is given to the Sales Rep when all the related
internal processes are completed successfully as well as the contract is removed from
“Pending Contracts” within the Customer Acceptance Portal. The Negotiation Status is
set to “Draft” while the Contract Status is set to new status of “Withdrawn” and any
previously enabled reminders on the contract are disabled.
4.2.2.18. Manage Cancellation Risk and Forecast Amount

With the introduction of additional parameters to record the forecasted amount and track
contracts that are at risk, users now have enhanced capabilities within Oracle Service
Contracts to manage the cancellation risk of contracts and derive better estimates for
contract renewals. The new “Amount” parameter works in tandem with the existing
“Percent” field, with a user having to enter a value for either one of them, the other being
derived automatically, thus providing users with a greater flexibility in managing their
renewal estimates. The “Cancellation Risk” parameter allows one to track the renewal
risk level of a given contract, thus providing a more direct visibility into identifying
contracts at risk.
This feature will be forward-ported to 12.2.6.
4.2.2.19. Cancellation Code

The objective of this enhancement is to track the probable or possible
Cancellation Reason for a given contract. Contract Administrators or Sales Rep
would be able to provide Cancellation Reason code and would be able to have
more intuitive reporting of contracts forecasted with a cancellation value.
Editable Cancellation Reason field is available in Service Contract Authoring –
Estimation Page, Mass Update Contract Page under Forecast Group, Update
Contract Page.
Read-only Cancellation Reason field is available in Administration Workbench,
“At Risk” view.
This feature is forward ported to 12.2.7.
4.2.3. Release 12.2

4.2.3.1. Solution Ordering
Users can now order Subscriptions using Oracle Order Management and have the
application create the subscription contracts automatically. The value of the ‘OKS:
Category for Order Management Originated Contracts’ profile option is not considered
during subscription contracts creation. The Oracle Order Management attributes required
for creating subscription contracts are Subscription Template, Duration and Period,
Service Start Date and Service End Date, Service Billing Profile, and Service Billing
Option.
Service Billing Profile is the value that is set for a sales order and lets the user to bill
using multiple periods. If this value is not set for a sales order, then the service or
subscription lines consider the Service Billing Option value as Full Billing from Order
Management.
Service Billing Option values are ‘Full Billing from Order Management’, ‘Full Billing
from Service Contracts’ and ‘First Period Billing from OM, Subsequent from Contracts’.
4.2.4. Release 12.2.4
4.2.4.1. Service Contracts Public APIs

Oracle Service Contracts now offers a wide range of public APIs to carry out Create and
Update operations at various levels in the entire contract document. With this release,
users can create and update contract header, lines, sub lines, billing streams, billing
schedules and contract templates. In addition to these, the APIs also enable users to take
actions on contracts, such as changing contract status, terminating active contracts,
deleting contracts, activating contracts, renewing contracts and cascading attributes from
header to lines/ sub lines. These APIs will help in increasing the usability of the
application and productivity of the users.
4.2.5. Release 12.2.5
4.2.5.1. Enhanced User Interfaces

The latest release of Oracle Service Contracts provides an enhanced and user-friendly
user-interface based of some of the latest web technologies. The new user-interface not
only provides users with a one-stop shop for managing their contracts but has also
simplified and stream-lined the various processes for improved usability. Currently the
new user-interface can be used for managing “Warranty and Extended Warranty”,
“Service Agreement” and “Subscription Contract”, supporting the actions for viewing
and editing contract details, contract renewal, contract termination, change management,
and communications and so on.
4.2.5.2. Enhancements to Subscription Contracts

Oracle Service Contracts supports the creation of Subscription contracts from Oracle
Order Management. Few enhancements have been made in Oracle Service Contracts to
streamline this process and make it more user-friendly.
• Previously, multiple subscriptions by a customer on the same sales order resulted
in multiple contracts. Now, for better management of subscription contracts
created from sales order, Oracle Service Contracts would create a single contract
for all the subscriptions in the same sales order.
• An improved user-interface for creating and managing service from sales order
was introduced, including support for merging of sales order lines into an
existing service agreement.
• Enhancements within Order Management have resulted in support for
subscriptions as promotional items in sales order. As a result, Advanced Pricing
supports subscriptions as promotional items in the modifier setup form. During
the setup, subscriptions will be setup as a promotion with corresponding
subscription template.
Correspondingly, Service Contracts provides an API for Order Management to
calculate the quantity based upon the period, UOM, item, inventory organization
and subscription template id. This quantity is used as a source by Advanced
Pricing to calculate the price.
4.2.6. Release 12.2.7
4.2.6.1. Enhancements to Usage Billing

In some business cases, there is a need to group multiple counter instances,
limited to a usage item, and define Usage Limit so as to provide a better pricing
to the customer and in some cases even control the fair usage. Oracle Service
Contracts is now enabled to support this requirement. This functionality is
accessible through API’s only. Below is the list of new capabilities that Oracle
Service Contracts, can now handle:
• Define Group, which is a logical entity, and add one or more counter instances to
it.
• Move Counter Instances to an existing group or to a new group.
• Ability to define Usage Limit/Allowance on an individual counter instance or on
a group.
• Set Rollover capabilities of unused Usage Limit.
4.3. Contract Renewal Command Center

4.3.1. Overview
Contract Renewal Command Center is a solution that allows users to effectively manage
contract renewals, proactively monitor performance metrics, and efficiently monitor
customers’ service experience, to achieve maximum customer satisfaction. Renewal sales
representatives can leverage the functionalities offered by Sales Representative
Command Center dashboard and renewal sales managers can leverage the Sales Manager
Command Center dashboard. With the powerful search feature, guided navigation, and
drilldown capabilities of Endeca Extensions for Service Contracts, service organizations
can improve compliance with service level agreements as well as keep the entire
organization in sync. Higher customer satisfaction levels can be achieved by constantly
monitoring and addressing issues in a timely manner, which otherwise could potentially
have an adverse effect on the quality of service being delivered.
4.3.2. V5
Renewal sales representative’s main job is to ensure on-time renewal of all the assigned
contracts and provide timely response to all customer queries. Information about
customers’ satisfaction with past service experience, their financial health and credit
rating assist the sales representatives in forecasting whether customers’ would be
renewing their contracts or not.
Renewal sales managers, on the other hand, need to monitor the day to day activities of
the sales representatives reporting to them and track their performance. Their main tasks
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Contract Renewal Command Center 61
are ensuring accurate renewal forecast, mitigating cancelation and termination risks and
determining patterns in cancelation and termination reasons.
4.3.2.1. Identify Renewal Exceptions and Manage Renewals Work Queue
The Sales Representative Command Center dashboard allows sales representatives to

effectively manage contract renewals and perform renewal related activities to ensure that
the contracts are renewed on time. Sales representatives receive alerts about renewed
contracts that are yet to be booked and about active contracts in grace period for which
the renewed contracts have not yet been booked. For sales managers, the Sales Manager
Command Center dashboard provides a comprehensive view of the alerts and work
queues of the sales representatives reporting to them.
4.3.2.2. Monitor Renewal Performance Metrics
Key Performance Indicators (KPIs) like Renewal Rate, Cancelation Rate, Termination
Rate and On Time Renewal provide critical insights into the renewal process and a good
idea about the extent of service revenue leakage and customer satisfaction levels. These
KPIs also help service organizations in evaluating the performance of the sales
representatives by helping them compare the actual performance with the targets assigned
to them.
4.3.2.3. Continuously Monitor and Improve Customer Service Experience
The Command Center allows users to monitor customer’s service requests and address
issues in a timely manner thereby ensuring high quality of service being delivered. It
allows them to proactively take actions to keep the entire service delivery organization in
sync and ensure that all the agreed terms and conditions are impeccably honored.
4.3.2.4. Identify Early Signs of Risks and Strategize Their Remediation
Business events such as bankruptcy, litigations, claims, and so on, provide indication
about customers’ financial health and resultant credit rating, thereby providing an
indication of their likelihood of renewing the contracts in the future. The Command
Center dashboard is the single source of truth of all the customer information that can
help in accurately forecasting contract renewals. Thus the service delivery organization is
able to get a more accurate picture of forecasted service revenue and is able to
proactively monitor high risk contracts that could potentially get canceled or terminated.
4.3.2.5. Monitor Service Revenue Leakage and Strategize Their Mitigation
The Command Center dashboard provides visibility into the service revenue leakage
occurring due to the cancelation or termination of contracts by customers for different
reasons. It provides the sales managers the necessary tools to determine trends in contract
cancelations and terminations. These insights can help the service delivery organization
to take corrective or preventive actions.
4.3.3. V6
Equipment financiers and service providers must effectively manage relationships with
customers and partners to pave the way for attaining customer and partner loyalty while
increasing operational efficiency and balancing ROI for all stakeholders. This new
module consolidates the needs of both Oracle Lease and Finance Management and Oracle
Service Contracts users by providing a relationship-driven view of equipment financing
and service contracts through a command center dashboard as well as analytical portals
that leverage transactional data generated in Oracle as well as external sources.
The Contract Renewal Command Center provides insights organized into objective-
driven pages that provide metrics, charts, graphs and other data to help you manage
customer and partner relationships and make the right decisions to drive loyalty and
balance value.
4.3.3.1. Customer Management

The customer management command center page provides you with information about
your customer relationships, such as the contracts they have with you and the transactions
and customer service information generated during your interactions with them to help
you:
• Drive customer loyalty
• Drive repurchases
• Increase your share of the customer’s spending on financing and service
4.3.3.2. Portfolio Management

The portfolio management command center page provides you with enhanced analytical
and summarized information about your portfolio of customers, contracts and assets to
help you:
• Increase your share of customer spending
• Balance your ROI with the value to your customers
4.3.3.3. Vendor Management

The vendor management command center page provides you with detailed and summary
information about the cash flow generated to and from your partners as well as
information about the portfolio generated through your partner relationships. This page
helps you:
• Drive your vendor loyalty
• Improve your vendors’ cash flow
• Help vendors increase business with you
4.3.3.4. Contracts (Finance and Service)

Two new contract management command center pages, one for finance contracts and one
for service contracts, provides you with the ability to balance the workload of
transactions you need to process to manage your customers’ contracts. These pages help
you
• Increase your operational efficiency
• Drive repurchases from customers
The information in the command center pages is provided through alerts, metrics, and
charts of various types as well as tables of details about your customers, contracts, assets
and transactions. Actionable links from the command center allow for the implementation
of decisions in OLFM or Oracle Service Contracts that you need to make to drive your
business objectives and to track the effectiveness of decision making to your results.

EBS 122 Cum RCD OM

Uploaded by

Copyright:

Available Formats

EBS 122 Cum RCD OM

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EBS 122 Cum RCD OM

Uploaded by

Copyright:

Available Formats

ORACLE E-BUSINESS SUITE

RELEASE CONTENT DOCUMENT

Order Management and Contracts

Prepared by Oracle E-Business Suite Product Development

Last Updated: April 20, 2018

2.1. Purpose of Document

3.1. Oracle Advanced Pricing

3.1.2.1. Pricing Engine Performance Enhancements

3.1.2.2. Purchasing Order Pricing Enhancements

3.1.3.1. Service Item Support in Promotional Modifiers

3.1.3.2. Support of Non-Continuous Price Breaks

3.2. Oracle Configurator

3.2.1.1. Numeric Handling

3.2.2.1. Query-based Rules

3.3. Oracle Order Management

3.3.1.1. Item Orderability

3.3.1.2. Credit Over-shipped Quantity for Referenced RMA

3.3.1.3. Support Decimal Quantity in BSA UI

3.3.1.4. Improved Install Base Search While Ordering Services

3.3.1.5. Delayed Scheduling

3.3.1.7. Customer PO-based Search in Scheduling Organizer

3.3.1.8. Visibility to Latest Configuration Till Picking

3.3.1.9. Line Level Credit Check Enhancement

3.3.1.10. Post Booking Item Substitution

3.3.1.11. Defer Split for Configurations

3.3.1.12. Internal Requisitions/Internal Sales Order Change Management

3.3.1.13. Order Management Productivity Enhancements

3.3.1.14. Sales Agreements Enhancements

3.3.1.15. Seeded Return Line Workflows

3.3.2.1. AIA Order To Cash 2.5 Enhancements

3.3.2.3. Supply Chain Web Services – Order Management

3.3.3.1. International Trade Management Adapter Enhancements for Global Trade

3.3.4.1. Support for Assemble-To-Order (ATO) Items in Pick-To-Order (PTO)

3.3.4.2. Order Information Portal (OIP) Enhancements

3.3.4.3. Tax Calculation on Freight Charges

3.3.4.5. Support for Credit Hold Based on Bill To Customer

3.3.4.6. Selling Services Enhancements

3.3.4.7. Support for Service as Promotional Goods

3.3.4.8. User Defined Attributes (UDA)

3.3.4.9. Scheduling Enhancements

3.3.4.10. Support for Advanced Catch Weight

3.3.4.11. Integration with Oracle Approvals Management (AME)

3.3.4.12. Credit Card Authorization Reversal

For orders/lines on hold, reversal of the authorization and re-authorization can be

A new system parameter "Reversal of Credit Card Authorization and Re-authorization"

3.3.4.13. Additional Business Events

3.3.4.14. Order Management Productivity Enhancements

3.3.5.2. Consider “Assemble To Order” Flag at Warehouse Level

3.3.5.3. Scheduling Enhancements

3.3.5.4. Order Management Productivity Enhancements

Order Management will automatically create a modifier on the referenced

3.3.6.1. HTML User Interface for Order Management

3.3.6.2. Item Substitution on Internal Sales Orders

3.3.6.3. Enabling Configurator for Return Orders (RMA)

3.3.6.4. Order Management Support for Yard Management System

3.3.6.5. Performance Improvements - Bulk Processing

3.3.6.6. Order Management Productivity Enhancements

In Release 12.2.4, External applications can use Order Management Item

3.3.7.2. Subscription Ordering Enhancements