Professional Documents
Culture Documents
Copyright © 2011, 2019, 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.1.4. Release 12.2.9 4
3.1.4.1. Evaluation of Factors based on Ranks in Factor List 4
3.1.4.2. WebADI Support for Price Lists and Modifiers 4
3.1.4.3. Evaluation of Passed in Modifier 5
3.2. Oracle Configurator 5
3.2.1. Release 12.1.1 5
Overview: Fusion Configurator Engine 5
3.2.1.1. Numeric Handling 5
3.2.1.2. Improved Defaulting 5
3.2.1.3. Auto-instantiation 6
3.2.1.4. Auto-completion 6
3.2.2. Release 12.2.5 6
3.2.2.1. Query-based Rules 6
3.3. Oracle Order Management 6
3.3.1. Release 12.1.1 6
3.3.1.1. Item Orderability 6
3.3.1.2. Credit Over-shipped Quantity for Referenced RMA 7
3.3.1.3. Support Decimal Quantity in BSA UI 7
3.3.1.4. Improved Install Base Search While Ordering Services 7
3.3.1.5. Delayed Scheduling 7
3.3.1.6. Enhanced Workflow Activity Hold 7
3.3.1.7. Customer PO-based Search in Scheduling Organizer 8
3.3.1.8. Visibility to Latest Configuration Till Picking 8
3.3.1.9. Line Level Credit Check Enhancement 8
3.3.1.10. Post Booking Item Substitution 8
3.3.1.11. Defer Split for Configurations 8
3.3.1.12. Internal Requisitions/Internal Sales Order Change Management 8
3.3.1.13. Order Management Productivity Enhancements 9
3.3.1.14. Sales Agreements Enhancements 10
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document ii
3.3.1.15. Seeded Return Line Workflows 10
3.3.2. Release 12.1.2 10
3.3.2.1. AIA Order To Cash 2.5 Enhancements 10
3.3.2.2. Workflow Performance Enhancements 10
3.3.2.3. Supply Chain Web Services – Order Management 11
3.3.3. Release 12.1.3 11
3.3.3.1. International Trade Management Adapter Enhancements for Global Trade Management (GTM) 11
3.3.4. Release 12.2 12
3.3.4.1. Support for Assemble-To-Order (ATO) Items in Pick-To-Order (PTO) Models and Kits 12
3.3.4.2. Order Information Portal (OIP) Enhancements 12
3.3.4.3. Tax Calculation on Freight Charges 12
3.3.4.4. Credit Tolerance for Honoring Manually Released Credit Check Holds 13
3.3.4.5. Support for Credit Hold Based on Bill To Customer 13
3.3.4.6. Selling Services Enhancements 13
3.3.4.7. Support for Service as Promotional Goods 14
3.3.4.8. User Defined Attributes (UDA) 14
3.3.4.9. Scheduling Enhancements 15
3.3.4.10. Support for Advanced Catch Weight 16
3.3.4.11. Integration with Oracle Approvals Management (AME) 16
3.3.4.12. Credit Card Authorization Reversal 17
3.3.4.13. Additional Business Events 17
3.3.4.14. Order Management Productivity Enhancements 18
3.3.5. Release 12.2.3 20
3.3.5.1. Support for “Online” Mode for Line Level Credit Checking 20
3.3.5.2. Consider “Assemble To Order” Flag at Warehouse Level 20
3.3.5.3. Scheduling Enhancements 21
3.3.5.4. Order Management Productivity Enhancements 21
3.3.6. Release 12.2.4 23
3.3.6.1. HTML User Interface for Order Management 23
3.3.6.2. Item Substitution on Internal Sales Orders 23
3.3.6.3. Enabling Configurator for Return Orders (RMA) 23
3.3.6.4. Order Management Support for Yard Management System 24
3.3.6.5. Performance Improvements - Bulk Processing 24
3.3.6.6. Order Management Productivity Enhancements 24
3.3.7. Release 12.2.5 25
3.3.7.1. Enhanced Gross Margin Calculations 25
3.3.7.2. Subscription Ordering Enhancements 25
3.3.7.3. Order Management Support for Serial Tagging at Sales Order Pick 26
3.3.7.4. Performance Improvements in Scheduling Process and Schedule Order Program 26
3.3.7.5. Order Management Productivity Enhancements 26
3.3.8. Release 12.2.6 28
3.3.8.1. Recurring Billing 28
3.3.8.2. Synchronization of Promise Date changes on Purchase Order with Drop Ship Sales Order 28
3.3.8.3. Performance Improvements in Process Order API 29
3.3.8.4. Performance Improvements in Scheduling Process and Schedule Order Program 29
3.3.8.5. Performance Improvements in Order Import Program 29
3.3.8.6. Order Management Productivity Enhancements 29
3.3.9. Release 12.2.7 30
3.3.9.1. Milestone Billing 30
3.3.9.2. Schedule Orders Enhancements 30
3.3.9.3. Manual Item Substitution Post Booking 31
3.3.9.4. REST Web Services Enhancements 31
3.3.9.5. Order Management Productivity Enhancements 31
3.3.10. Release 12.2.8 32
3.3.10.1. Enhancements to Integration with Oracle Approvals Management (AME) 32
3.3.10.2. Item Orderability Enhancements 32
3.3.10.3. Order Management Productivity Enhancements 33
3.3.10.4. Orders Dashboard 35
3.3.11. Release 12.2.9 35
3.3.11.1. Usage Based Billing 35
3.3.11.2. Cancel Unshipped Lines at First Shipment 35
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iii
3.3.11.3. New Entity Customer Service Representative (CSR) in Order Management 36
3.3.11.4. Ability to determine which attributes trigger Repricing 36
3.3.11.5. Returns (RMA) Enhancements 37
3.3.11.6. Partial Period Revenue Accounting for Models and its Components 37
3.3.11.7. Order Management Productivity Enhancements 37
3.3.12. Release 12.2.9+ 38
3.3.12.1. Bulk Assignment of Customer Service Representative (CSR) 38
3.4. Oracle Order Management Command Center 38
3.4.1. Overview 38
3.4.2. Release 12.2.8 38
3.4.2.1. Orders Dashboard 38
3.4.3. Release 12.2.8+ 38
3.4.3.1. Enhancements to Orders Dashboard 39
3.5. Oracle Order Management Information Discovery 39
3.5.1. Release V4 39
3.5.2. Release V6 40
3.5.2.1. Customer Explorer 40
3.5.3. Release V7 40
3.5.3.1. Order 360 View 40
3.5.3.2. Customer Explorer 40
3.5.4. Release V8 41
3.5.4.1. Advanced Search Capabilities 41
3.5.4.2. Performance improvement of Graphs 41
3.6. Oracle Mobile Sales Orders for Oracle E-Business Suite 41
3.6.1. Mobile Release 1.0 42
3.6.1.1. Accessibility Improvements 42
3.6.1.2. Mobile Application Foundation Updates 42
3.6.2. Mobile Release 2.0 42
3.6.2.1. Android Support 42
3.6.2.1. Mobile Foundation Release 3.0 Updates 42
3.6.3. Mobile Release 3.0 42
3.6.3.1. Enhanced Line Details Page Layout 42
3.6.3.2. Added Adjustments Details Pages for Order Header and Line Adjustments 42
3.6.3.3. Added Default Content in Emails 42
3.6.3.4. Translation Support 42
3.6.3.5. Mobile Foundation Release 4.0 Updates 43
3.6.4. Mobile Release 4.0 43
3.6.4.1. View Invoice for the selected Order 43
3.6.4.2. Mobile Foundation Release 5.0 Updates 43
3.6.5. Mobile Release 5.0 43
3.6.5.1. Mobile Foundation Release 6.0 Updates 43
3.6.6. Mobile Release 8.0 – Client Version 1.7.0 43
3.6.6.1. Mobile Foundation Release 8.0 Updates 43
3.7. Oracle iStore 43
3.7.1. Overview 43
3.7.2. Release 12.1.2 44
3.7.2.1. Product Comparison 44
3.7.2.2. Automated Password Generation for Secondary Users 44
3.7.2.3. Automated Assignment of Roles and Permissions 44
3.7.2.4. Check for Duplicate Contacts 44
3.7.2.5. Payment Book Enhancements 45
3.7.2.6. Copy Product Content Components 45
3.7.3. Release 12.1.3 45
3.7.3.1. One-Click Shopping List Management 45
3.7.3.2. Product Detail Pop-up 46
3.7.3.3. Add To Cart Navigation 46
3.7.4. Release 12.1.3+ 46
3.7.4.1. Multi-customer Access 46
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iv
3.7.4.2. Direct Item Entry Enhancement 46
3.7.4.3. Mandatory Purchase Order Number 47
3.7.4.4. Shopping Cart Purge 47
3.7.5. Release 12.2 47
3.7.5.1. Carousel Views for Related Products 47
3.7.6. Release 12.2.4 47
3.7.6.1. Shopping Cart Purge 47
3.7.7. Release 12.2.5 48
3.7.7.1. Address Search Enhancement 48
3.7.7.2. Line Level Promotions 48
3.7.8. Release 12.2.7 48
3.7.8.1. Order Type for a Specialty Site 48
3.7.8.2. Email Notification Style 48
3.7.9. Release 12.2.8 48
3.7.9.1. Promotion Code Enhancement 48
3.7.9.2. Copy Prior Order Items 49
3.8. Oracle iStore Information Discovery 49
3.8.1. Overview 49
3.8.2. V6 49
3.8.2.1. Enhanced iStore Search 49
3.8.2.2. Customer and Cross Reference Part Number Search 49
3.8.2.3. Price and Price Range Filter 50
3.8.2.4. Multiple Search Result Views 50
3.8.2.5. Product Comparisons 50
3.8.3. V8 50
3.8.3.1. Enhanced Product Catalog Search Capabilities 50
3.9. Oracle Shipping 50
3.9.1. Release 12.1.1 50
3.9.1.1. Defer Planned Shipment Interface 50
3.9.1.2. Allow Incremental Shipments for Over-shipment and Under-shipment Tolerances 51
3.9.2. Release 12.1.3 51
3.9.2.1. Fulfillment Batches for Distributed Warehouse Management System 51
3.9.3. Release 12.2 51
3.9.3.1. Integration to 3PLs or 3rd Party Distributed Warehouse Management System 51
3.10. Oracle Supply Chain Event Management 51
3.10.1. Release 12.1.3 52
3.10.1.1. Order Fulfillment and Spare Parts Order Templates 52
3.10.2. Release 12.2.5 52
3.10.2.1. Back to Back and Procure to Pay Templates 52
3.11. Oracle Installed Base 52
3.11.1. Overview 52
3.11.2. Release 12.2.4 53
3.11.2.1. Option to track only Customer-owned products using Oracle Installed Base 53
3.11.3. Release 12.2.5 53
3.11.3.1. Tracking of Customer Install Base items 53
3.11.3.2. Install Base Transaction performance improvements 53
3.11.3.3. Serial Tagging at Sales Order Pick support 53
3.12. Oracle Installed Base Information Discovery 54
3.12.1. Overview 54
3.12.2. Release V4 54
3.12.2.1. Search by Extended Product Attributes 54
3.12.2.2. Execute ‘Related Products’ Search 54
3.12.2.3. Improved Drill-down to Product Configuration 54
3.12.2.4. Identify Installed Base by Geography 54
3.12.2.5. Track Customer Product Metrics 54
3.12.3. Release V5 55
3.12.3.1. User-Definable DFF Search 55
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document v
4. New and Changed Features in Contracts 56
4.1. Oracle Sales Contracts 56
4.1.1. Release 12.1.1 56
4.1.1.1. Secure Enterprise Search 56
4.1.1.2. Structured Terms Authoring for Repository Contracts 56
4.1.2. Release 12.1.2 56
4.1.2.1. Author Individual Clauses in Microsoft Word 56
4.1.3. Release 12.1.3+ 57
4.1.3.1. Templates, Rules, Questions and Constants APIs 57
4.1.3.2. Contract Terms and Conditions Migration API 57
4.1.3.3. Contract Expert Enhancements 57
4.1.3.4. Enhancements MS Word Synchronization 58
4.1.3.5. Apply Multiple Templates to a Sales Document 58
4.1.3.6. Multi Row Variables 58
4.1.3.7. Deviation Report for Repository Contracts 58
4.1.3.8. Clause Analysis for Repository Contracts 58
4.1.3.9. Contract Usability Enhancements 59
4.1.3.10. Contract Expert Performance Improvements 59
4.1.3.11. Contract Expert History 59
4.1.3.12. Delete Multiple Clauses, Sections and Deliverables 59
4.1.3.13. Purge Process for Repository Contracts 59
4.1.4. Release 12.2 60
4.1.4.1. Repository Contracts Enhancements 60
4.1.4.2. UDA support for Deliverables 60
4.1.4.3. MS Word 2010 Certification 60
4.1.5. Release 12.2.4 60
4.1.5.1. Repository Contracts Printing Enhancement 60
4.1.6. Release 12.2.5 60
4.1.6.1. Updating UDA on Approved Contracts 60
4.2. Oracle Service Contracts 60
4.2.1. Release 12.1.1 60
4.2.1.1. Service Contract Import Program 60
4.2.2. Release 12.1.3+ 61
4.2.2.1. Service Contract Renewal Performance Enhancements 61
4.2.2.2. Performance Enhancements to Main Billing Program for Usage Contracts 61
4.2.2.3. Mass Update Tool 61
4.2.2.4. Prevent Deletion of Line/Sub line during Contracts Renewal 62
4.2.2.5. Carry Over Self-Service Decline Code onto Service Contract Cancellation Reason 62
4.2.2.6. Revalue Contract during Change in Currency 62
4.2.2.7. Specify Cc E-mail Addresses during Quote and Reminders 62
4.2.2.8. Selective Update of Warranty Contracts upon IB Transfer of Ownership 62
4.2.2.9. Re-price on Renewal Consolidation 62
4.2.2.10. Flexible Invoice Text Defaulting 62
4.2.2.11. Service Contracts Usability Enhancements 62
4.2.2.12. Merge Assets across Contracts 63
4.2.2.13. Drive Contract Coverage by Severity 64
4.2.2.14. Control Generation of Invoice 64
4.2.2.15. Calculate Estimated Tax with Higher Accuracy 64
4.2.2.16. Close Request for Assistance 64
4.2.2.17. Withdrawal of Published Quotes 65
4.2.2.18. Manage Cancellation Risk and Forecast Amount 65
4.2.2.19. Cancellation Code 65
4.2.3. Release 12.2 65
4.2.3.1. Solution Ordering 65
4.2.4. Release 12.2.4 66
4.2.4.1. Service Contracts Public APIs 66
4.2.5. Release 12.2.5 66
4.2.5.1. Enhanced User Interfaces 66
4.2.5.2. Enhancements to Subscription Contracts 66
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document vi
4.2.6. Release 12.2.7 67
4.2.6.1. Enhancements to Usage Billing 67
4.3. Contract Renewal Command Center 67
4.3.1. Overview 67
4.3.2. V5 67
4.3.2.1. Identify Renewal Exceptions and Manage Renewals Work Queue 68
4.3.2.2. Monitor Renewal Performance Metrics 68
4.3.2.3. Continuously Monitor and Improve Customer Service Experience 68
4.3.2.4. Identify Early Signs of Risks and Strategize Their Remediation 68
4.3.2.5. Monitor Service Revenue Leakage and Strategize Their Mitigation 68
4.3.3. V6 68
4.3.3.1. Customer Management 69
4.3.3.2. Portfolio Management 69
4.3.3.3. Vendor Management 69
4.3.3.4. Contracts (Finance and Service) 69
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document vii
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
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.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
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.
In Release 12.2.9, a new column "Factor Rank" has been added for the users to
explicitly assign a numeric value to the factors. Now, pricing engine will evaluate
factor ranks to determine adjustment factor in the pricing formula.
Please note that factors with least value will be given highest precedence.
In Release 12.2.9, users can populate pricing interface tables using WebADI.
With added validations and excel integration, WebADI will offer better control to
users on their data and minimise data corruption.
A new option "WebADI" with dropdown list has been added on "Lists" tab of
Oracle Pricing User Page to create or update the price list and modifiers.
In addition, a new page has been added to update price lists and modifiers for
selection of parameters for content in UPDATE action mode.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Advanced Pricing 4
3.1.4.3. Evaluation of Passed in Modifier
Currently, for a particular price request call a traditional/pattern pricing engine
call is made and pricing engine returns all the valid modifiers.
In Release 12.2.9, calling products have the option to pass the Modifier List Line
ID information with Qualifier Context as MODLIST and Qualifier Attribute as
QUALIFIER_ATTRIBUTE7. If passed, pricing engine will just validate/evaluate
order pricing for a particular modifier instead of a regular pricing engine call. This
will enhance the performance significantly.
This feature is supported in both Pattern Engine and Traditional Engine.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Configurator 5
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
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 6
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”.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 7
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 8
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 9
• 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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 10
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 11
3.3.4. Release 12.2
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 12
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 13
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 14
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 15
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 16
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 17
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 18
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 19
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 20
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 21
• There is no modifier on the source order line to account for the
difference between the list and selling price
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 22
3.3.6. Release 12.2.4
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 23
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 24
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 25
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.
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".
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 26
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.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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 27
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).
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 28
Additionally, please refer to the RCD of Purchasing/iSupplier for more information on
this capability
Please refer to Order Management 12.2.5 RCD for more details on this feature.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 29
drop ship orders will honor the value on this field while displaying the related orders
and order Lines on Summary and Lines tab respectively.
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 30
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.
In addition, Get_Order API in OE_Order_Pub package has been expanded to support the
above mentioned input parameters.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 31
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.
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 32
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".
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
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 33
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 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.
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 34
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 35
Option to cancel unshipped lines is available at customer account level as setup to
identify the customers who do not accept backorders.
The option at the customer account level enables the new behavior for its all future
orders. As there can be multiple ship-to sites for a given customer account, the option
selected at account level will be applicable for all of its ship-to sites. Name of the new
option is “Cancel Unshipped Lines”.
In Order Management, when a new order is created with a (sold-to) customer, Order
Management will default the value of “Cancel Unshipped Lines” to a new checkbox
"Cancel Unshipped Lines” on the order header using defaulting rules. Users can
change/override this value until any one line gets Picked.
After ship confirmation, once Interface Trip Stop process is complete, Order
Management will update status of the fully/partially shipped lines as per current design
and additionally cancel the remaining quantity/order lines based on value of “Cancel
Unshipped Lines” on the order.
Please note that scope of the lines considered for cancelation is “lines belonging to a
specific ship-to site of the order(s) of which a delivery is being ship confirmed”.
Please refer to TCA and Shipping RCD for the respective product changes.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 36
3.3.11.5. Returns (RMA) Enhancements
3.3.11.5.1. Ability to receive returns in any UOM
Currently, referenced RMAs can only be entered in the same UOM as the original
outbound order.
In Release 12.2.9, referenced RMAs can be entered in a different UOM from the
original outbound order. Further, RMA credit will be calculated based on the original
outbound order.
3.3.11.6. Partial Period Revenue Accounting for Models and its Components
Accounting rule details captured in Order Management drive the revenue recognition in
Oracle Receivables. The details include a) Accounting Rule of type Fixed, Variable or
Partial Periods, b) Accounting Start Date and Accounting End Date and c) Accounting
Duration.
Currently, accounting rule of type “Partial Periods” are supported for Standard Items and
Services only.
In Release 12.2.9, accounting rule of type “Partial Periods” has been extended to other
item types like Model and Option. After this change, Users can now setup any accounting
rule for any item type in both Outbound and Return Orders.
In addition to the sales order creation screens this feature is supported in Process Order
API and Order Import but not in High Volume Order Processing (HVOP).
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 37
3.3.11.7.3. Copy Billing Plan
If the Recurring Billing framework has been enabled, there is a new option in the
Copy Order/Copy Line action to copy billing plans. There is a checkbox for “Billing
Plan” which is selected by default. This feature is supported for all the types of
billing plans in the Recurring Billing framework.
For any type of billing plan, billing plans will only be copied if billing has not yet
started i.e. “Billing Plan Status” = “Open”.
The concurrent program has three parameters: Customer, Customer Service Rep and
Override Existing Assignment. All the parameters are optional.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management Command Center 38
3.4.3.1. Enhancements to Orders Dashboard
In Release 12.2.8+, following new capabilities have been added:
3.4.3.1.1. Display assigned Orders to Login User by Default / Deep Link
Currently, Order Management Command Center displays sales orders as per Multi-
Org Access Control (MOAC) setup for the login EBS user.
In this release, if login user is also setup as Customer Service Rep (CSR) on certain
sales orders then Orders Dashboard will display only such sales orders by default.
Thus, user will see his/her list of orders for viewing and taking timely action to
effectively manage his/her customers’ orders. The relatively shorter list helps user to
prioritize the actions on important orders.
To view all orders based on MOAC setup, user can remove the pre-applied filter on
Customer Service Rep.
3.4.3.1.2. New attributes in Available Refinements and Order Lines Result Table
Following new attributes have been added:
Available Refinements : Customer Service Rep, Ship To State, Ship To Country,
Order Total, Line Amount, Order Type
Order Result Table : Customer Service Rep
Order Lines Result Table: Ship To State, Ship To Country, Shipment Method, Carrier
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management Information Discovery 39
• Fully integrated with Oracle E-Business Suite
3.5.2. Release V6
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management Information Discovery 40
Discovery applications for Service Contracts and Finance Contracts to view
transactions in the respective Extension pages.
3.5.4. Release V8
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Mobile Sales Orders for Oracle E-Business Suite 41
3.6.1. Mobile Release 1.0
3.6.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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Mobile Sales Orders for Oracle E-Business Suite 42
3.6.3.5. Mobile Foundation Release 4.0 Updates
• 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 iStore 43
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.
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.
• 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
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.
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.
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.
Oracle iStore will check for a duplicate contact record in the Trading Community
Architecture (TCA) customer master when creating a secondary user.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iStore 44
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.
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.
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.
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iStore 45
3.7.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.
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.
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”.
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iStore 46
With this enhancement, B2B users can specify the product on the Direct Item Entry page
in one of the three ways:
The above information is passed to Order Management when the cart is placed as an
order in Order Management.
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.
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iStore 47
3.7.7. Release 12.2.5
3.7.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.7.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.7.8. Release 12.2.7
3.7.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.7.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”.
This feature is back-ported to 12.1.3+.
3.7.9. Release 12.2.8
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iStore 48
3.7.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.
This feature is back-ported to 12.1.3+.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle iStore Information Discovery 49
3.8.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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Shipping 50
deliveries are potential scenarios when deferring the interface and running it periodically
may improve overall system performance.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Supply Chain Event Management 51
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.10.1. Release 12.1.3
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.
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Installed Base 52
3.11.2. Release 12.2.4
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.
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.
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Installed Base 53
3.12. Oracle Installed Base Information Discovery
3.12.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.12.2. Release V4
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Installed Base Information Discovery 54
3.12.3. Release V5
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Installed Base Information Discovery 55
4. New and Changed Features in Contracts
4.1. Oracle Sales Contracts
4.1.1. Release 12.1.1
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sales Contracts 56
• 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
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sales Contracts 57
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
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sales Contracts 58
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sales Contracts 59
4.1.4. Release 12.2
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Service Contracts 60
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
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Service Contracts 61
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
forward-ported to 12.2.4.
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
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Service Contracts 62
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’.
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
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Service Contracts 63
controlled using “OKS: Pricing Method for Contract Merge” profile option. This feature
is forward-ported to 12.2.4.
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
forward-ported to 12.2.4.
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Service Contracts 64
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.
This feature is forward-ported to 12.2.5.
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
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Service Contracts 65
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’.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Service Contracts 66
and subscription template id. This quantity is used as a source by Advanced
Pricing to calculate the price.
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 67
are ensuring accurate renewal forecast, mitigating cancelation and termination risks and
determining patterns in cancelation and termination reasons.
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.
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.
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.
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
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Contract Renewal Command Center 68
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.
Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Contract Renewal Command Center 69