EBS_122_Cum_RCD_OM

ORACLE E-BUSINESS SUITE RELEASE CONTENT DOCUMENT Order Management and Contracts Releases 12.1 and 12.2 (inclusive of 12.02 – 12.0.7) Prepared by EBS Product Management & Strategy Last Updated: August 2, 2013

Version: 1.4 Copyright © 2012, 2013 Oracle Corporation All Rights Reserved

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document ii

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 4 3.1.3.1. Service Item Support in Promotional Modifiers 4 3.1.3.2. Support of Non-Continuous Price Breaks 4

3.2. Oracle Configurator 4 3.2.1. Overview: Fusion Configurator Engine 4 3.2.2. Release 12.1.1 5

3.2.2.1. Numeric Handling 5 3.2.2.2. Improved Defaulting 5 3.2.2.3. Auto-instantiation 5 3.2.2.4. Auto-completion 5

3.3. Oracle Order Management 5 3.3.1. Release 12.1.1 5

3.3.1.1. Item Orderability 5 3.3.1.2. Credit Over-shipped Quantity for Referenced RMA 6 3.3.1.3. Support Decimal Quantity in BSA UI 6 3.3.1.4. Improved Install Base Search While Ordering Services 6 3.3.1.5. Delayed Scheduling 6 3.3.1.6. Enhanced Workflow Activity Hold 7 3.3.1.7. Customer PO-based Search in Scheduling Organizer 7 3.3.1.8. Visibility to Latest Configuration Till Picking 7 3.3.1.9. Line Level Credit Check Enhancement 7 3.3.1.10. Post Booking Item Substitution 7 3.3.1.11. Defer Split for Configurations 7 3.3.1.12. Internal Requisitions/Internal Sales Order Change Management 8 3.3.1.13. Order Management Productivity Enhancements 8 3.3.1.14. Sales Agreements Enhancements 9 3.3.1.15. Seeded Return Line Worflows 9

3.3.2. Release 12.1.2 9 3.3.2.1. AIA Order To Cash 2.5 Enhancements 9 3.3.2.2. Workflow Performance Enhancements 10 3.3.2.3. Supply Chain Web Services – Order Management 10

3.3.3. Release 12.1.3 11

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iii

3.3.3.1. International Trade Management Adapter Enhancements for Global Trade Management (GTM) 11 3.3.4. Release 12.2 11

3.3.4.1. Support for Assemble-To-Order (ATO) Items in Pick-To-Order (PTO) Models and Kits 11 3.3.4.2. Order Information Portal (OIP) Enhancements 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) 15 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) 17 3.3.4.12. Credit Card Authorization Reversal 17 3.3.4.13. Additional Business Events 18 3.3.4.14. Order Management Productivity Enhancements 18

3.4. Oracle Shipping 21 3.4.1. Release 12.1.1 21

3.4.1.1. Defer Planned Shipment Interface 21 3.4.1.2. Allow Incremental Shipments for Over-shipment and Under-shipment Tolerances 21

3.4.2. Release 12.1.3 22 3.4.2.1. Fulfillment Batches for Distributed Warehouse Management System 22

3.4.3. Release 12.2 22 3.4.3.1. Integration to 3PLs or 3rd Party Distributed Warehouse Management System 22

3.5. Oracle Supply Chain Event Management – New Product 22 3.5.1. Release 12.1.3 + 22

3.6. Oracle Order Management Extensions for Oracle Endeca - New Product 23 3.6.1. Release 12.1.3.4 23

3.1. Oracle Installed Base Extensions for Oracle Endeca – New Product 23 3.1.1. Overview 23 3.1.2. Release 12.1.3.4 24

3.1.2.1. Search by Extended Product Attributes 24 3.1.2.2. Execute ‘Related Products’ Search 24 3.1.2.3. Improved Drill-down to Product Configuration 24 3.1.2.4. Identify Installed Base by Geography 24 3.1.2.5. Track Customer Product Metrics 24

4. New and Changed Features in Contracts 25

4.1. Oracle Sales Contracts 25 4.1.1. Release 12.1.1 25

4.1.1.1. Secure Enterprise Search 25 4.1.1.2. Structured Terms Authoring for Repository Contracts 25

4.1.2. Release 12.1.2 25 4.1.2.1. Author Individual Clauses in Microsoft Word 25

4.1.3. Release 12.1.3+ 26 4.1.3.1. Templates, Rules, Questions and Constants APIs 26 4.1.3.2. Contract Terms and Conditions Migration API 26 4.1.3.3. Contract Expert Enhancements 26 4.1.3.4. Enhancements MS Word Synchronization 27 4.1.3.5. Apply Multiple Templates to a Sales Document 27 4.1.3.6. Multi Row Variables 27 4.1.3.7. Deviation Report for Repository Contracts 27 4.1.3.8. Clause Analysis for Repository Contracts 28 4.1.3.9. Contract Usability Enhancements 28

4.1.4. Release 12.2 28 4.1.4.1. Repository Contracts Enhancements 28

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document iv

4.1.4.2. UDA support for Deliverables 29 4.1.4.3. MS Word 2010 Certification 29

4.2. Oracle Service Contracts 29 4.2.1. Release 12.1.1 29

4.2.1.1. Service Contract Import Program 29 4.2.2. Release 12.1.3+ 29

4.2.2.1. Service Contract Renewal Performance Enhancements 29 4.2.2.2. Performance Enhancements to Main Billing Program for Usage Contracts 30

4.2.3. Release 12.2 30 4.2.3.1. Solution Ordering 30 4.2.3.2. Mass Update Tool 31 4.2.3.3. Prevent Deletion of Line/Subline during Contracts Renewal 31 4.2.3.4. Carry Over Self-Service Decline Code onto Service Contract Cancellation Reason 31 4.2.3.5. Revalue Contract during Change in Currency 31 4.2.3.6. Specify Cc Email Addresses during Quote and Reminders 31 4.2.3.7. Flexible Invoice Text Defaulting 32 4.2.3.8. Service Contracts Usability Enhancements 32

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Purpose of Document 1

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 2

2. Introduction

2.1. Purpose of Document

This Release Content Document (RCD) communicates information about new or changed functionality introduced in Oracle E-Business Suite Releases 12.1 and 12.2, and in subsequent Release Update Packs (RUPs) and off-cycle patches. For your convenience, it also includes new or changed functionality introduced in the RUPs for Release 12, including 12.0.2 through 12.0.7.

The features and enhancements described in this document are grouped by product, and then by the release in which they first became available, for example, “Release 12.1.1”. Features released in an off-cycle patch have a special designation – for example, a feature released after 12.1.1, but before 12.1.2, is designated as “Release 12.1.1+”.

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Advanced Pricing 3

3. New and Changed Features in Order Management

3.1. Oracle Advanced Pricing

3.1.1. Release 12.1.1

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

3.1.2. Release 12.1.2

3.1.2.1. Pricing Engine Performance Enhancements

In this release, the performance of Advanced Pricing Engine has been enhanced by using a pattern-based search algorithm which normalizes all setup combinations in to a single hashkey. This feature is optional and enabled through a profile called QP: Pattern Search.

In order to enable this feature, after turning on the profile, users will need to run a one-time pattern upgrade concurrent program called QP Pattern Upgrade to upgrade all existing setups to the new pattern format. All subsequent work in the Advanced Pricing product will leverage this new and faster approach to price determination.

3.1.2.2. Purchasing Order Pricing Enhancements

Oracle Purchasing has extended its integration with Advanced Pricing to provide greater granularity and flexibility in pricing orders and agreements. The extended integration also provides greater transparency to the means by which a price has been determined for orders and agreements.

Oracle Purchasing users can now:

• View the pricing modifier information for a Purchase Order and/or Global Blanket Purchase Agreement line and view the pre-calculated price adjustments applied by the pricing engine

• Manually enter a price modifier, change a modifier rate, and recalculate the price

• Query existing manual modifiers and apply them to a Purchase Order and/or Global Blanket Purchase Agreement unit price

• Change the modifier rate and apply changes to PO or Global Blanket Purchase Agreement Line.

These new features provide an accurate view of pricing information to the buyer, increased flexibility for buyers to price an order and streamlined supplier communication on prices.

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Configurator 4

3.1.3. Release 12.2

3.1.3.1. Service Item Support in Promotional Modifiers

In this release, service items can be used as the “get” item in promotional modifiers. It has become a general business practice to give the service free of cost or at a discounted price to consumers when they buy a high-end-consumer good. Users can now setup promotional modifiers where a service item gets added automatically when a certain finished good is added to the order. This helps in cutting down order creation time, adds efficiency and accuracy of order creator, and enables companies to implement service item pricing/ordering promotional strategies.

To achieve this, users need to provide the service item as a get product in the promotional modifier setup.

3.1.3.2. Support of Non-Continuous Price Breaks

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

This enhancement also allows the tier value to start from any positive value other than 0.

3.2. Oracle Configurator

3.2.1. Overview: Fusion Configurator Engine

Enterprises want to leverage constraint-based technology within their product configuration deployments to reduce the cost of ownership and increase user adoption. With the release of an enhanced constraint-based engine, Oracle Configurator meets this need and continues to be strategically placed to lead in the configuration marketplace.

Various aspects of constraint-based technology provide particular business benefits which are highlighted in the new Fusion Configurator Engine in this first release. The robust constraint-based technology reduces time and cost for development and maintenance of configuration solutions through an easier to maintain architecture that inherently eliminates current engine limitations.

This release includes a superior ownership experience as a result of improved and expanded features. The model developer can leverage improved numeric handling and defaulting, as well as the new auto-instantiation, which automatically creates product structure. More feedback is provided to the end user during a configuration session and the end user can even choose to have a configuration completed based on previously defined preferences.

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Order Management 5

3.2.2. Release 12.1.1

3.2.2.1. Numeric Handling

The improvements in numeric handling create a configuration session that is easier to use and provides more feedback. The allowable range for numeric inputs is now dynamically displayed, resulting in fewer contradictions for the end user and an improved configuration experience. Since constraint technology employs the propagation of domains, in which constraints are inherently bidirectional, rules now propagate the most information possible during selection and Auto-completion.

3.2.2.2. Improved Defaulting

Defaults are more flexible than ever before since any constraint can now be defined as a default. Additionally, modelers can define strategies about how to explore a specific domain by default. For example, when the weight of a configured product is evaluated during a configuration session, a default can be incorporated so that the strategy used attempts to find a solution that has the lowest weight. Defaults can also be prioritized or ordered so they are executed in a sequence defined by the modeler. For example, a model with a weight and a size may have two defaults, one to find the lowest weight and another to find the lowest size. Inherently the sequence of this strategy will affect the outcome. However, the modeler can order the defaults so the strategy may be set to evaluate size before weight.

3.2.2.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.2.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.3. Oracle Order Management

3.3.1. Release 12.1.1

3.3.1.1. Item Orderability

Businesses need the ability to define which customers are allowed to order which products, and the ability to apply the business logic when the order is created. For


example, Customer A may purchase all items except for repair parts and promotional items. Alternately, Customer B buys only repair parts from you.

This new feature from Order Management provides users with an easy way to define orderable products, based on exceptions defined in the Item Orderability rules. It would be possible to apply Orderable Products business rules to items or Item Categories defined for an organization. Based on the rules defined in the Orderability UI, the user would be able to restrict the Items that can be ordered from the Sales Order and Quick Sales Order form. Flexibility is provided to the users for defining Orderability rules either at the Customer Class level or at the “Sold-to” Customer level.

3.3.1.2. Credit Over-shipped Quantity for Referenced RMA

With the existing functionality in Order Management, users can book an RMA for a quantity based on the ordered Quantity. Businesses have requirements to book RMA’s based on shipped quantities, especially in the case of over-shipments, in addition to the current provision based on ordered quantities. In Release 12.1.1, users are provided with an additional option of raising RMAs based on the shipped quantity, if the Invoicing basis is set to ship quantity. For scenarios where the Profile option is based on Ordered Quantity, the existing behavior for RMA will continue.

Additionally, two more seeded line level return workflow types have been provided to cater to business scenarios of “Return with Receipt with No Credit” and “Return with Receipt and Approval with No Credit”.

3.3.1.3. Support Decimal Quantity in BSA UI

This feature provides the flexibility to enter decimal quantities in Blanket Sales Agreements. This flexibility will be at par with the capability currently provided in Sales Order and Quick Sales order screens.

3.3.1.4. Improved Install Base Search While Ordering Services

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

3.3.1.5. Delayed Scheduling

In the existing “Auto Schedule” functionality in Order Management for Standard lines, there are scenarios that might lead to data discrepancy between OM and GOP Demand. The Delayed Scheduling feature in Release 12.1.1 refers to enhancing the “Auto Schedule” feature in Order Management by introducing an additional option to users when they choose to Auto Schedule. A new profile option, called, “OM: Delay Scheduling”, has been introduced for this feature. This new profile option is dependent on the value of the profile “OM: Autoschedule” being set to value “Yes”. You set the value of the profile option, “OM: Delay Scheduling” and “OM: Autoschedule” to “Yes” to enable this feature. Enabling this feature will ensure that GOP calls will be made only when user actually saves the changes and eliminates the data discrepancy between OM and GOP Demand.


This will also enhance the overall performance of the Sales Order, as we will make only one GOP call at the time of saving rather than individual GOP calls for each Line. This will bring a lot of performance improvement especially if Planning is on a different server.

3.3.1.6. Enhanced Workflow Activity Hold

With the existing functionality of Holds in Order Management, the workflow activity hold gets applied to all open records, irrespective of the current workflow status. For instance, a ‘picking activity hold’ gets applied on the record even if it has already passed the ‘picking activity’. With Release 12.1.1, the hold gets applied only on valid records, which have either not reached that specific workflow activity or not in the completed status.

3.3.1.7. Customer PO-based Search in Scheduling Organizer

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

3.3.1.8. Visibility to Latest Configuration Till Picking

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

3.3.1.9. Line Level Credit Check Enhancement

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

3.3.1.10. Post Booking Item Substitution

In Release 12.1.1, Item Substitution functionality support has been extended to post Booking through Scheduling/re-scheduling in Sales Order, Quick Sales Order, and Scheduling Order Organizer forms. Item Substitution functionality is also supported from ASCP Planner’s Workbench (loop-back functionality) till the line is pick-released.

3.3.1.11. Defer Split for Configurations

In Release 12.1.1, order line split for models can be done in concurrent mode so that users don’t have to wait for the split action to complete. While splitting an order line for


a configuration, users will have an option to select a checkbox if it’s needed to defer the split process. If this option is selected, then system will submit a concurrent request to split the order line and in the mean time users can continue with other activities on the sales order.

3.3.1.12. Internal Requisitions/Internal Sales Order Change Management

In Release 12.1.1, internal order processing has been enhanced to offer additional and better-coordinated change management capabilities. Internal requisition and internal sales order change management allows the requester or the shipping organization to change the date, change the quantity, or cancel internal transfer requests. All of these changes will now be visible throughout planning, purchasing and order fulfillment. After an internal requisition has been approved and before the internal sales order line status disallows any more changes, the requester can ask to change the internal requisition, which will initiate a reapproval workflow and log the change history. Once the change request has been approved, affected users will be notified. Planners will also be able to change the need-by date or cancel internal requisitions in the Planner's Workbench. When the shipping organization cancels or makes changes to the scheduled ship date or quantity on an internal sales order, those changes will be automatically cascaded to the internal requisition and visible to planning as well.

• Quantity and Schedule Ship/Arrival Date changes on the Internal Sales Order line will be automatically propagated to the Internal Requisition and vice versa. Cascading of date is optionally controlled through a profile “POR: Sync up Need by date on IR with OM”

• Cancellation of an Internal Sales Order/Line will automatically cancel the corresponding Internal Requisition/Line and vice versa.

• You will be able to view intercompany invoices for a sales order, from the quick sales order form.

• You’ll also be able to create internal sales orders with different order types. Defaulting rules in order management can be used to default appropriate internal order types.

• The urgent flag on the internal requisition line will flow onto the internal sales order line as the shipment priority, based on the profile option “POR: Urgent Flag on Int Req maps to Shipping Priority”

Additionally, please refer to the RCD of Purchasing/iProcurement for more information on this capability.

3.3.1.13. Order Management Productivity Enhancements

In Release 12.1.1, the following new capabilities offer the ability to increase productivity while entering and managing sales orders:

• The functionality of the quick sales order form has been matched with the regular sales order form. Mass change and scheduling organizer capabilities are now available with the Quick Sales Order.

• Mass Change capability in Order Management is also enhanced to support cascading of order header attribute changes to the order lines.

• Copy capability is enhanced to support copying of orders across operating units, creating multiple copies of an order in one operation, copying ship sets and fulfillment sets to new orders. The copy capability automatically populates the current order number value, in the “Get Header Level info from” field, on the


copy form. There is also a new option, in the copy form, to directly navigate to the newly created order after the copy operation.

• New attributes for hold source criteria have been introduced. They are Project, Task, Order type, Line type, Price List, Creation Date, Created By, Sales Channel, Payment Type, Shipping Method, Deliver to location, Source Type, Top Model, Option Item, Payment Term and Order Currency. Also, a single hold source can be used to apply holds across multiple operating units.

• Order header/line workflows, on hold, will automatically restart, when the hold is released, eliminating the need to manually progress the workflows. This enhancement is implemented as an option in holds setup.

• High volume order processing (HVOP) capability is enhanced to support import of orders with taxes and configurations.

• Additional support for Try & Buy scenarios. You can, optionally, update the Customer PO Number on an Order Line even after it has been ship confirmed, but not invoiced. The updated Customer PO Number will be printed on the customer Invoice document, making the reconciliation process for the end customer smooth and error free. This feature is achieved through the relaxation of the seeded processing constraint.

• A public API has been provided for re-pricing an order.

• A new concurrent program for batch re-pricing is introduced with parameters, which could be submitted and scheduled for repricing multiple orders/lines.

3.3.1.14. Sales Agreements Enhancements

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

3.3.1.15. Seeded Return Line Worflows

In Release 12.1.1, two additional order line workflows are seeded for addressing business requirement of returns without credit:

• Return with Receipt – No Credit: Return process which requires only goods receipt and no receivables credit, can be setup by attaching this new workflow to the return line type.

• Return with Receipt and Approval – No Credit: Return process, which also requires approvals before goods receipt and no receivables credit, can be setup by attaching this new workflow to the return line type.

3.3.2. Release 12.1.2

3.3.2.1. AIA Order To Cash 2.5 Enhancements

Order Management has enhanced its integration with Siebel Customer Relationship Management (CRM) or any third party order capture solution via Oracle’s Applications


Integration Architecture (AIA). This solution will enable orders from different channels (web storefronts, partners, call centers etc.) to be captured via a third party order capture solution and passed to Oracle E-Business Suite for order fulfillment and billing. Customer service representatives will be able to enter new orders, monitor order progress and fulfillment and update orders through Siebel CRM.

This AIA Process Integration Pack (PIP) is responsible for synchronization of orders between Siebel CRM and Oracle EBS. New features in version 2.5 of the PIP include:

1) Synchronization of updates made in Siebel to the corresponding order in Order Management

2) Synchronization of scheduling changes driven within Order Management (such as schedule date, ship-from warehouse and shipping method) to the corresponding Siebel order.

3) Configurable synchronization of sales order/line workflow status updates from Order Management to Siebel

3.3.2.2. Workflow Performance Enhancements

In this release, two new enhancements have been added to Order Management to better support application performance in high volume environments.

3.3.2.2.1. Workflow Purge concurrent program

Often, users choose to defer the closure of the Order at the header level until the end of the month. Consequently, the Sales Order Header workflow will remain open throughout the month even though that order has been fulfilled in its entirety. Thus even though corresponding line workflows can and will close, they will not be eligible for purging until the header completes as well. This could potentially increase the load on the ‘Purge Obsolete Workflow Runtime Data’ concurrent program during month end. Additionally, the workflow tables remain unnecessarily loaded throughout the month, largely with closed lines waiting for headers to get closed.

A new concurrent program, “Purge Order Management Workflow,” has been created to facilitate faster and more thorough purging of Order Management workflows. This program will first attempt to close stuck order headers and orphaned errored workflow. The program can then purge child workflows, if they are closed, without waiting for the parent workflow to complete.

3.3.2.2.2. Support of Workflow bulk APIs to High Volume Order Processing program

New workflow API’s have been integrated in the High Volume Order Processing program in order to increase its performance.

3.3.2.3. Supply Chain Web Services – Order Management

As part of this enhancement, web services are provided by exposing business logic contained within Oracle forms through Java APIs. These web services are cataloged in the Oracle Integration Repository and can be browsed though Oracle Integration Repository Browser Interface under respective product family node. By Clicking on the Business Entity in Integration repository, you can view full description, list of web


services for that business entity along with the description of the web service, whereas description of parameters can be seen from the XSD definition of the service available via the generated WSDL.

The following web service is provided for Order Management:

• Sales Order: Create Sales Order, Delete Sales Order, Query Sales Order, Update Sales Order.

3.3.3. Release 12.1.3

3.3.3.1. International Trade Management Adapter Enhancements for Global Trade Management (GTM)

The International Trade Management adapter has been enhanced for Global Trade Management to:

• Support master data synchronization of items

• Support master data synchronization of parties (i.e. organization, person, etc.)

• Send an expanded number of party types

• Deliver additional messages/information

• New option available in the ITM adapter administration that specifically enables the use of Oracle Global Trade Management

There is a new parameter ’Integrated with Global Trade Management’. If this parameter is enabled, EBS will send XML messages to GTM for party synchronization, order export compliance, delivery export compliance screening and item synchronization. EBS will also be able to receive the responses for the order and delivery export compliances.

3.3.4. Release 12.2

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

Currently, while ATO items are supported as optional/non-mandatory items in PTO models, they are not supported as included/mandatory items in PTO Models or Kits. In Release 12.2, ATO items are supported as included/mandatory items in PTO Models as well as Kits. Thus, ATO items that are identified as included/mandatory items in the Bill of Materials of the PTO Model or Kit will have the ATO flag selected and corresponding ATO attributes populated at the time of sales order line creation.

To enable this functionality, the value selected in the profile options “OM: Allow Standard ATO Items as PTO/Kit Included Components” and “BOM: Allow ATO item in a KIT or as mandatory in a PTO Model” should be “Yes” at the site level.


3.3.4.2. Order Information Portal (OIP) Enhancements

In Release 12.2, OIP has been enhanced in the following areas:

• Currently, only contacts associated with the Sold To Customer on the sales order can view and track sales orders through OIP. OIP has been enhanced to allow contacts associated with the Bill To Customer on the sales order to view and track sales orders through OIP.

To enable this functionality, the value selected in the profile option “OM: Order View for External Users based on” should be “Bill to Customer” at the site level.

• External users can subscribe to receive notifications based on key business events such as Scheduling, Schedule Date Changes and Shipping. In addition, external users can choose to receive notifications individually for each sales order or consolidated across sales orders by setting up preferences in Workflow mailer.

• OIP has been integrated with FND Security to enable rules-based access to the summary and detail views of sales orders and deliveries.

• Several search parameters have been added. “Customer Number” has been added to Simple Search. “Customer Number”, “Invoice Number”, “Orders On Hold (Yes/No)”, “Ship To Customer”, “Bill To Customer” and “Deliver To Customer” have been added to Advanced Search.

• Several display fields have been added to the summary and detail views of the sales order and delivery.

Fields added to the summary view of the sales order are “Hold Status” and “Active Holds”.

Fields added to the detail view of the sales order header as well as line are “Request Date”, “Hold Status”, “Active Holds”, “Ship To Customer”, “Ship To Contact”, “Bill To Customer”, “Bill To Contact”, “Deliver To Customer” and Deliver To Contact”. In addition, “Install Base System Names” has been added to the detail view of the sales order line.

Fields added to the detail view of the delivery line are “Ship To Customer”, “Ship To Contact”, “Deliver To Customer”, “Deliver To Contact”, “Schedule Ship Date”, Schedule Arrival Date” and “Serial Number”.

3.3.4.3. Tax Calculation on Freight Charges

Currently, in Order Management, estimated tax is not calculated on freight charges associated with the sales order header and lines. Taxes on freight charges are subsequently calculated in Account Receivables if the value of the system parameter "Invoice Freight as Revenue" is set to “Yes”.

In Release 12.2, estimated taxes on freight charges will also be calculated and displayed in Order Management if the value of the system parameter "Invoice Freight as Revenue" is set to “Yes”. In addition to the sales order creation screens, calculation of estimated taxes on freight charges will be supported in the Process Order API, Order Import and High Volume Order Processing (HVOP).


In addition, the profile option “OM: Delay Tax Calculation” has been added to allow deferral of tax calculation from the time of the user entering the sales order line to the time of the user saving the sales order line.

3.3.4.4. Credit Tolerance for Honoring Manually Released Credit Check Holds

Currently, orders that have been manually released from credit check hold may potentially have a credit check hold reapplied if changes are made to the order.

In Release 12.2, customers can prevent credit check holds from being reapplied on orders that were previously released from credit check hold. Reapplication of credit check hold is prevented if the change in the order amount is within a specified tolerance limit. The tolerance limit can be specified as an absolute amount or a percentage of the order amount released from credit check hold. Tolerance amount and percentage can also be specified together and the lesser of the two will be considered as the tolerance limit. The tolerance limit applies only to increases in the order amount. Decreases in the order amount are always considered to be within tolerance limits.

However, changes to certain attributes that impact the credit exposure calculation will retrigger credit checking regardless of whether changes to the order amount are within the specified tolerance limit e.g. Bill To Customer is changed. In this event, the order could potentially have a credit check hold being reapplied.

To enable this functionality, customers should specify values in the Tolerance “Currency”, “Amount” and/or “Percentage” fields in Credit Check Rules.

3.3.4.5. Support for Credit Hold Based on Bill To Customer

Currently, orders are placed on credit hold if the Sold To Customer is on credit hold. In Release 12.2, customers have the option to place orders on credit hold if the Bill To Customer is on credit hold. Additionally, customers can decide to place the order on credit hold based on the header level Bill To Customer or place the order lines on credit hold based on the line level Bill To Customer.

A new system parameter “Apply Credit Hold Based On” has been added. Options are “Sold To Customer”, “Header Level Bill To Customer” and “Line Level Bill To Customer”. The “Sold To Customer” option is the default option and retains current functionality.

3.3.4.6. Selling Services Enhancements

In Release 12.2, there are several enhancements related to ordering service items.

3.3.4.6.1. Support for Subscription Contracts

Currently, only service contracts of type “Extended Warranty” can be ordered through Order Management.

In Release 12.2, service contracts of type “Subscription Contract” can be ordered as well. Service related attributes such as Start Date, Period and Duration can be specified for “Subscription Contract”. In addition, an “Extended Warranty” can be attached to a “Subscription Contract”.

A new system parameter “Default Behavior for Subscription Item on Order Line” has been added. Set the value to “Subscription Service Line” to enable this feature.


3.3.4.6.2. Billing Options for Extended Warranties & Subscription Contracts

Currently, when an “Extended Warranty” is invoiced through Order Management, the invoice amount is for the entire duration of the “Extended Warranty”. However, in several cases, customers need the ability to specify that the invoice amount be billed in multiple installments during the duration of the “Extended Warranty”.

In Release 12.2, additional billing options have been introduced for “Extended Warranty” and “Subscription Contract”. The options are as follows:

• Retain the existing behavior of generating an invoice for the entire duration. • Generate the invoice for the first installment from Order Management and

subsequent installments from Service Contracts. • Generate invoices for all installments from Service Contracts. In this

scenario, Order Management does not generate any invoices.

A new field “Service Billing Option” has been added to the order line to identify the appropriate billing option. The value in this field can be defaulted by Order Management and can be changed by the user.

In addition, a new field “Billing Profile” has been added to the order line to determine the billing frequency and amount. The “Billing Profiles” available for selection are maintained in Oracle Service Contracts.

3.3.4.6.3. Additional Attributes for Extended Warranties & Subscription Contracts

A new field “Service Coverage Template” has been added to the order line. Values can be specified in this field for “Extended Warranty”.

A new field “Subscription Template” has been added to the order line. Values can be specified in this field for “Subscription Contract”.

The values in these fields can be defaulted by Order Management and can be changed by the user.

3.3.4.6.4. Related Order Information Portal (OIP) Enhancements

A new region “Service Details” has been added in Order Information Portal (OIP) to display service related attributes.

The following fields are available in this region: Service Start Date, Service End Date, Service Duration, Service Period, Coverage Template, Subscription Template, Billing Option, Billing Profile, First Period Bill Amount and First Period Bill To Date.

The new region and fields are hidden by default and need to be enabled for display.

3.3.4.7. Support for Service as Promotional Goods

Currently, only standard items can be defined as promotional goods in Advanced Pricing.

In Release 12.2, service contracts of type “Extended Warranty” can be defined as promotional goods as well. With this new feature, an “Extended Warranty” can be automatically added as a discounted order line that is attached to an eligible product.


3.3.4.8. User Defined Attributes (UDA)

In Release 12.2, “User Defined Attributes” have been added in Order Management. Customers can add several additional fields to the order header and line.

The “User Defined Attributes” framework is in addition to the existing “Descriptive Flexfields” framework.

In addition, new interface tables and a new concurrent program "Import User Defined Attributes” have been added to import these attributes.

3.3.4.9. Scheduling Enhancements

In Release 12.2, there are several enhancements related to scheduling.

3.3.4.9.1. Scheduling of Partially Available Quantity

Currently, during scheduling, if the entire quantity is not available on the requested date, the order line is automatically scheduled with a schedule ship date on which the entire order quantity is available.

In Release 12.2, during scheduling, if only a partial quantity is available on the requested date, Order Management will split the order line to schedule the available quantity on the requested date and schedule the remaining quantity on the available date.

A new system parameter “Scheduling Auto Split Criteria” has been added. Select a value other than “None” to enable this feature.

Please note that this feature is only available for standard items that are ATP-enabled and not part of a Ship/Arrival Set.

This feature is supported in Order Import but not in High Volume Order Processing (HVOP).

3.3.4.9.2. Substitution of Partially Available Quantity

Currently, during scheduling, if the entire quantity for the ordered item is not available on the requested date but is available for a substitute item, the entire order line is scheduled with the substitute item.

In Release 12.2, Order Management will split the line to schedule the ordered item for the available quantity and schedule the substitute item for the remaining quantity.

To enable this feature, set the value to “With Partial Substitution” in the new system parameter “Scheduling Auto Split Criteria”. Set the value to “None” or “With Full Substitution” to retain the existing functionality.

Please note that this feature is only available for standard items that are ATP-enabled and not part of Ship/Arrival Set.

This feature is supported in Order Import but not in High Volume Order Processing (HVOP).


3.3.4.9.3. Additional Controls for the Availability Window

Currently, when the profile "OM: Auto Schedule" is set to Yes, the “Availability Window” is automatically displayed when the user navigates to the “Lines” tab of the Sales Order form.

In Release 12.2, it is possible to disable the automatic display of the “Availability Window” when the profile "OM: Auto Schedule" is set to Yes.

A new profile option “OM: Pop Up Availability Window” has been added. Set the value to “No” to disable the automatic display. Set the value to “Yes” or leave as blank to retain the existing functionality.

3.3.4.10. Support for Advanced Catch Weight

In 12.2, there are several enhancements related to Dual UOM-enabled items in Warehouse-enabled (WMS) organizations. These enhancements are across several Supply Chain products: Order Management, Inventory, Shipping and Warehouse Management.

Please refer to the RCDs of these products for additional information on related enhancements.

Enhancements specific to Order Management are:

3.3.4.10.1. Order Fulfillment based on the Secondary UOM

Currently, on a sales order line, when the Ordered UOM is different from the Primary UOM of the item, an equivalent quantity in the Primary UOM is considered for order fulfillment.

In Release 12.2, there is a new option to fulfill the order based on the equivalent quantity in the Secondary UOM. To enable this functionality, the value populated in a new field “Fulfillment Base” on the order line should be “Secondary”.

A new profile option “OM: Default Fulfillment Base” has been added. Set the value to “Yes” to enable dynamic fulfillment base selection capability.

Order Management defaults the value of the “Fulfillment Base” field based on the Ordered UOM, Primary UOM and Secondary UOM of the ordered item. This value is defaulted on the basis of seeded conditions that determine whether the value in the “Fulfillment Base” field should be "Primary" or “Secondary". In addition, there is a “custom hook” to allow customers to define their own conditions to determine the “Fulfillment Base”.

3.3.4.10.2. Related Pricing Enhancements

Currently, pricing of Dual UOM-enabled items is always calculated on the Shipped Quantity in the Secondary UOM if specified as such in the item definition.

In Release 12.2, two new pricing options have been introduced to determine if pricing should be calculated on the Shipped Quantity in the Ordered UOM or Primary UOM.


3.3.4.10.3. Related Returns (RMA) Enhancements

If the original sales order line is referenced in a return/RMA line, the value of the “Fulfillment Base” field will be inherited from original sales order line.

If the original sales order line is not referenced, the “Fulfillment Base” on the return/RMA line will be determined independently using the same logic as specified for outbound sales order lines.

3.3.4.10.4. Related Availability Window Enhancements

Several fields have been added to the “Availability Window” in the “Ordered Item” and “Substitute Item” tabs.

The new fields are: Primary UOM, On Hand Ordered Quantity and Ordered Quantity Reservable. The On Hand Ordered Quantity and Ordered Quantity Reservable fields display results in the Ordered UOM by converting from the available Primary UOM or Secondary UOM quantity depending on the value in the “Fulfillment Base” field.

3.3.4.11. Integration with Oracle Approvals Management (AME)

Currently, the list of approvers for the transactions requiring approval is a pre-determined list.

In Release 12.2, Order Management has been integrated with Oracle Approval Management to leverage the robust capabilities of the approval rules engine to dynamically determine the list of approvers for Quotes, Sales Agreements and Returns (RMA).

A new option “Use Approvals Management Engine” has been added to the “Transaction Types” form. Select this option to use this feature for specific transaction types.

For the transaction types with the “Use Approvals Management Engine” option selected and appropriate workflow processes assigned, the list of approvers will be determined by Approval Management based on the rules defined for the specific entity (Quotes, Sales Agreements and Returns (RMA). The seeded workflows that support this functionality are “Order Flow - Mixed or Return with Approval” (for RMAs) and “Negotiation Flow - Generic with Approval” for Quotes and Sales Agreements.

With AME, the list of approvers is dynamically generated based on attribute values, conditions, approval types and approval groups. Several attributes have been seeded in Approval Management for defining rules for these entities (Quotes, Sales Agreements and Returns (RMA). In addition to the seeded attributes, customers can define additional attributes for use in rule definition.

3.3.4.12. Credit Card Authorization Reversal

Currently, for an order/ line with credit card payments, Order Management authorizes the credit for the order/line amount and re-validates the availability of a valid authorization on the order/line during the order/line lifecycle.

In Release 12.2, an option to reverse the prior authorization and execute a new authorization when there are changes to the order/line has been added.


In addition, customers can choose various options related to credit card authorization reversal and re-authorization based on changes to the order/line. The options are:

• Reverse the authorization and re-authorize immediately. • Defer the reversal of the authorization and re-authorization to specific events

such as picking, shipping and fulfillment. • Place the order/line on hold.

For orders/lines on hold, reversal of the authorization and re-authorization can be initiated by the “Process Payments” action or running the “Process Pending Payments” concurrent program. A new system parameter "Reversal of Credit Card Authorization and Re-authorization" and a new option “Reversal of Credit Card Authorization and Re-authorization" in the “Transaction Types” form have been added.

3.3.4.13. Additional Business Events

In Release 12.2, several business events have been added.

The “oracle.apps.ont.oip.statuschange.update” business event is invoked during the following changes in the order/line: Booking, Scheduling, Schedule Ship Date Change, Shipping, Fulfillment, Invoicing, Customer Acceptance and Closing.

The “oracle.apps.ont.hold.action” business event is invoked when a hold on an order/line is placed and released.

The “oracle.apps.ont.oip.processfailure.update” business event is invoked when order booking fails.

A new profile option “OM: Raise Status Change Business Event” has been added. Set the value to “Yes” to enable this feature.

Please note that the new business events are available in Release 12.1.3 as well.

3.3.4.14. Order Management Productivity Enhancements

In Release 12.2, the following new capabilities offer the ability to increase productivity while entering and managing sales orders:

3.3.4.14.1. Additional Hold Source Attributes

In Release 12.2, “Customer Number” has been added as an additional hold source for creating order header level holds. “Item Category”, “End Customer” and “End Customer Number” have been added as additional hold sources for creating order line level holds.

3.3.4.14.2. Specify Recipient/Role for Credit Check Hold Notifications

Currently, if credit check hold notifications are enabled, notifications for sales orders placed on credit check hold are sent to the user who created that particular sales order. However, this user may not necessarily be authorized to release the sales order from credit check hold. A new profile option, “OM: Credit Check Notification Recipient”, allows customers to specify the user or role assigned to users who will receive notifications when sales orders are placed on credit check hold.


3.3.4.14.3. Allow Users with View-Only Access to Apply/Release Order Holds

Currently, only users with the ability to edit the sales order can apply/release an order hold. Users with view-only access to sales orders cannot apply/release order holds even if they are authorized to do so. In Release 12.2, users with view-only access can also apply/release order holds assuming that they are authorized to do so.

3.3.4.14.4. Allow Users with Ability to Apply Holds to Search by Hold Name

Currently, only users with the ability to release holds can search for sales orders by hold name. In Release 12.2, users with the ability to apply but not release holds can also search for sales orders by hold name.

3.3.4.14.5. Consistency in Display of Credit Hold Flag after Customer Merge

Currently, when customers are merged, the target customer inherits credit holds from merged customers at the Account and Bill-To site levels. Although Order Management continues to apply holds for the target customer that are inherited from the merged customers, the credit hold flag for inherited credit holds is not displayed as selected when viewed in customer detail. In Release 12.2., this inconsistency has been addressed and inherited credit holds will be displayed as selected in the customer detail screen.

3.3.4.14.6. Additional Defaulting Attribute for Intermediate Ship To Org

In Release 12.2, “Intermediate Ship to Org” at the order line level has been added as an additional attribute for defaulting in the defaulting rules framework. Customers can setup defaulting rules for “Intermediate Ship to Org” based on defaulting source type of "Constant "or "PL/SQL".

3.3.4.14.7. Ability to Search Orders by PO Release Number

Currently, drop-ship orders can be searched by "Related PO Number" in Order Organizer and Quick Order Organizer. In the case of Blanket Purchase Orders, there could potentially be several Blanket Releases. In Release 12.2, a new search parameter “PO Release Number” has been added. If a value is specified in the “Related PO Number” parameter, the “PO Release Number” parameter will list all related Blanket Releases and these two parameters can be used together to search drop-ship orders.

3.3.4.14.8. Automatic Creation of Ship Sets Based on Warehouse

Currently, if the profile option “OM: Assign New Set For Each Line” is set to "No" and the “Line Set” value in the order header is “Ship”, Order Management ensures that all lines in a ship set are shipped from the same warehouse.

In Release 12.2, this functionality is extended by giving customers the option to automatically create new ship sets for each warehouse in an order.

To enable this functionality, a new system parameter “Assign New Ship Set for Each Warehouse” has been added and the value should be set to “Yes”.

3.3.4.14.9. Reassignment of Drop-Ship Orders Created by Inactive Users

In Release 12.2, a new system parameter "Requestor For Drop Ship Orders Created By Inactive Users” has been added. For drop-ship orders, in the event that the user who created the original sales order is no longer an active user, the user specified in


this system parameter will be passed to Purchasing when the Purchase Release process is initiated.

3.3.4.14.10. Copy Automatic Attachments When User Splits Line

Currently, when the user splits a line, manual attachments are copied to the newly created line but automatic attachments are not copied to the newly created line.

In Release 12.2, if there is no change in the Ship To Address during the split, automatic attachments, along with any modifications, will be copied over to the newly created line. If there is a change in the Ship To Address, automatic attachments will be reapplied to the newly created line based on automatic attachment rules.

To enable this feature, the value in the existing profile option "OM: Apply Automatic Attachments" should be set to “Yes”. There is no change in the existing behavior when the value in this profile option is set to “No”.

Please note that there is no change to the behavior of manual attachments when the user splits the line or the behavior of manual and automatic attachments when the system splits the line.

3.3.4.14.11. Ability to View Shippable Lines Only in a Configuration

Currently, in the sales order form, when the "Show Line Details" option is selected in the Tools menu, details of the configuration such as options, classes and included items are displayed in the line “Summary” tab.

In Release12.2, there is an additional option to display only the shippable lines of a configuration when the "Show Line Details" option is selected. To enable this new feature, a new option "Show Shippable Lines Only" has been added to the Tools menu.

3.3.4.14.12. Option for Cost of Goods Sold (COGS) Account derivation in Returns (RMA)

Currently, when advanced accounting is not used for an intercompany sales order, the COGS account for a return/RMA line that references the original sales order line is derived from the referenced order line.

In Release 12.2, customers have the option to derive the COGS account from the attributes of the return/RMA line rather than the referenced sales order line.

A new system parameter “Source Line for deriving COGS account on referenced RMA" has been added. Set the value to "Return Line to be used as Source" to enable this feature. Set the value to "Referenced Sales Line to be used as Source" to retain the existing functionality.

3.3.4.14.13. Serial Item Support in Workflow "Bill Only with Inventory Interface"

In Release 12.2, in addition to current support for lot and revision Items, serial controlled items are also supported by the “Bill Only with Inventory Interface” workflow. As a prerequisite, users have to create reservations against serial number(s) in the Reservation Details form.

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Shipping 21

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.4. Oracle Shipping

3.4.1. Release 12.1.1

3.4.1.1. Defer Planned Shipment Interface

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

3.4.1.2. Allow Incremental Shipments for Over-shipment and Under-shipment Tolerances

On the sales order line, an under-shipment and/or over-shipment tolerance may be specified to track the minimum acceptable quantity and the maximum acceptable quantity, which may be shipped relative to the ordered quantity. This business practice is quite prevalent in industries with variable yields or for indivisible goods (e.g. steel ingots). When an over-shipment tolerance is specified on a sales order line, the line will be available to ship confirm until the over-ship tolerance is reached. When an under-shipment tolerance is specified on a sales order line, the line will be available to ship

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Supply Chain Event Management – New Product 22

confirm until the ordered quantity. If under-ship and over-ship tolerances are being used together, the line will be available to ship confirm until the over-ship tolerance is reached.

3.4.2. Release 12.1.3

3.4.2.1. Fulfillment Batches for Distributed Warehouse Management System

Delivery details can now be grouped into fulfillment batches based on the criteria selected in the 'Create Shipment Batches for Fulfillment' concurrent program. The fulfillment batches can then be sent as a shipment request to the Distributed Warehouse Management Systems (e.g. Oracle EBS WMS deployed in Distributed/LSP Mode) for execution. The Distributed Warehouse Management System will need to send the shipment advice once the shipment request is processed and executed.

This enhancement also provides the ability to create and ship confirm the shipments based on the shipment advice received from the Distributed Warehouse Management System.

Out of the box, the ODI maps allow the shipment request batches to be sent to Oracle EBS Distributed WMS. The shipment request output can also be used by any 3rd party Distributed Warehouse Management System / Logistics Service Provider system.

3.4.3. Release 12.2

3.4.3.1. Integration to 3PLs or 3rd Party Distributed Warehouse Management System

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

3.5. Oracle Supply Chain Event Management – New Product

3.5.1. Release 12.1.3 +

Oracle Supply Chain Event Management (SCEM) is a brand new Oracle Fusion Middleware based solution available in Release 12.1.3, that provides visibility to events in every link across the extended supply chain. SCEM can correlate various critical events originating in multitier supply chain and raise real time alerts and notifications. Alerts and notifications are displayed on flow monitoring Business Activity Monitoring (BAM) dashboards and are also sent as emails to appropriate users.

SCEM can track all heterogeneous systems in real-time to spot potential problem early enabling timely response even before exceptions occur. Event routers pick up relevant events from external event sources like B2B messages and other enterprise applications Business rules are evaluated and abnormal events are quickly identified to the user. With comprehensive correlated event tracking, SCEM facilitates faster decision making and information driven collaboration with customers and partners.

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content DocumentOracle Order Management Extensions for Oracle Endeca - New Product 23

SCEM provides ready to use master templates for Order Fulfillment and Spare Parts Order flows. These built-in templates track sales order fulfillment right from order creation through shipping and closure. In case of spare parts order flow even the original Service Request and accompanying task is tracked along with the spare parts order. These templates can additionally be extended to meet unique requirements, like adding a new event to be monitored or adding a new source application to the flow. The solution also includes a JDeveloper extension for building monitoring applications from the ground up. SCEM solution is fully integrated with Oracle E-Business suite hence enables rapid deployment of shipped master templates.

This feature is forward-ported to 12.2.3

3.6. Oracle Order Management Extensions for Oracle Endeca - New Product

3.6.1. Release 12.1.3.4

Oracle Order Management Extensions for Oracle Endeca is available through the “Information Discovery” tab in Order Information Portal (OIP). There are three sub-tabs/pages: Open Orders, Closed Orders and Returns.

Oracle E-Business Suite Order Management Extensions for Endeca empowers order fulfillment managers, supply chain analysts and business users with the ability to identify and process delayed orders thereby reducing fulfillment time, maximizing revenue and ensuring customer satisfaction. In addition, users can analyze product returns to eliminate them in the future and avoid lost revenue.

Key Features & Benefits: • Search and process delayed orders • Key metrics of projected fulfillment delays, associated order value and number

of orders • Analyze product returns • Wide range of parameters for multi-faceted analysis of orders and returns • Search on unstructured order information including attachments and descriptive

flexfields • Fully integrated with Oracle E-Business Suite

3.1. Oracle Installed Base Extensions for Oracle Endeca – New Product

3.1.1. Overview

Getting to know the answers to questions like ‘what products do my customers own and where are they located?’ is important for organizations to plan better upsell / 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 Extensions for Oracle Endeca 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 –

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Installed Base Extensions for Oracle Endeca – New Product 24

• 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.1.2. Release 12.1.3.4

3.1.2.1. Search by Extended Product Attributes

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

3.1.2.2. Execute ‘Related Products’ Search

This feature in Installed Base Endeca guided navigation is based on the Item Relationships such as Up-Sell Product and Cross-Sell product defined between Items. This enables users to search for target products for prospective Up-Sell or Cross-Sell sales campaigns.

3.1.2.3. Improved Drill-down to Product Configuration

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

3.1.2.4. Identify Installed Base by Geography

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

3.1.2.5. Track Customer Product Metrics

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

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Sales Contracts 25

4. New and Changed Features in Contracts

4.1. Oracle Sales Contracts

4.1.1. Release 12.1.1

4.1.1.1. Secure Enterprise Search

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

4.1.1.2. Structured Terms Authoring for Repository Contracts

Repository Contracts enable customers to easily manage all their contracts online. It provides basic contract management capabilities and global, secure visibility to key stakeholders. Repository Contracts is available as a part of Oracle Sales Contracts and/or Oracle Procurement Contracts.

In Release 12, users created Repository Contracts by capturing key attributes about the contract (like contract party, dates, amount, etc.) and managed the document files associated with the contract. Users could also track key deliverables and contract expiry. With Release 12.1.1, users can now author structured terms and conditions while creating a Repository contract. These terms are based on standard templates, clauses, and policies that are defined in the contract terms library. Users can also use the Contract Expert feature to bring in additional clauses that may be required based on the business terms of the particular contract. The contract can then be printed for signature, or exported to Microsoft Word for redlining/collaboration with the external party. The deviations report functionality will provide a quick overview of all policy violations in the contract.

Structured terms authoring promotes standards based contract authoring and reduces the overall time-to-contract. Risk associated with non-standard contracts is also mitigated by ensuring approvers have visibility to all policy violations.

4.1.2. Release 12.1.2

4.1.2.1. Author Individual Clauses in Microsoft Word

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


The following formats will be preserved as defined in Microsoft Word:

• Bold, italic, text color, and underlines • Standard bullets available in Word • Numbering schemes (roman numerals, alphabets, numbers) and their indents,

including hanging indents • List items with non-numbered text between them • Indent and tabs (Tab spacing/width is determined based on style sheet

information) • Line spacing • Text alignment (left, right, and center justification) • Table formatting • Hyperlinks, page breaks, and symbols defined in Unicode

This feature requires Microsoft Word Professional 2003 or 2007.

4.1.3. Release 12.1.3+

4.1.3.1. Templates, Rules, Questions and Constants APIs

Importing and updating templates, rules, questions, and constants from external systems is supported using APIs. There are separate APIs for:

• Templates • Rules • Questions • Constants

4.1.3.2. Contract Terms and Conditions Migration API

The procedures in the Contract Terms and Conditions Migration API are used to apply templates to a document. Users can add clauses and sections to the document. In addition, attaching a document as the primary contract document is also possible.

4.1.3.3. Contract Expert Enhancements

The following enhancements have been made to Contract Expert which supports automation of the contract drafting process:

• Now it is possible to specify if the clause suggested by Contract Expert is mandatory or not at the rule definition level. If this is empty, template level setup will be used to determine whether a Contract Expert suggested clause should be added as mandatory or optional.

• Users can specify based on attributes of the document which section a clause should be automatically added to by Contract Expert. In the clause creation flow, the user can specify a variable name which is an attribute of the document, for example the document format value for printing (see below). The user can now specify different sections for different values of that variable (example Section A for value UCF, etc.). When the clause is added to the document by the Contract Expert, the clause will get added to the section based on the value of the variable of the document.


• A new rules infrastructure, the Contract Rules Evaluation Engine, is now available to support customers requiring high performance from the Contract Expert feature. A new profile option “OKC: Use Contracts Rules Engine” will control whether the new Contract Rules Evaluation Engine or the original Oracle Configurator rules engine will be used. This is applicable for both rules activation and runtime of the Contract Expert feature. This feature is forward-ported to 12.2.2.

4.1.3.4. Enhancements MS Word Synchronization

Often it is convenient during negotiation and redlining to edit the contract offline in a word processor. Contract administrators or legal will download the contract into Microsoft Word for redlining and collaboration and upload the changes made. MS Word Synchronization is now available for contracts having clauses which were originally authored in MS Word and imported. This feature is forward-ported to 12.2.2.

4.1.3.5. Apply Multiple Templates to a Sales Document

Previously the system allowed the user to apply only one sales contracts template to the sales document. The user could change the template if needed. However, often an organization may have multiple templates which need to be applied to a document. This new feature allows the user to select and apply multiple templates to the document. All the clauses from the new templates flow into the document. The user can also view the different templates that have been added to any document.

4.1.3.6. Multi Row Variables

Users can create user defined manual variables that are tables containing one row per line or multiple rows. Contract Preview will print the variable values according to the layout defined for the variable. These variables are not available for Contract Expert Rules. One example of how multi row variables can be used is that users can create dependent variables and then integrate those variables to user-defined attributes.

4.1.3.7. Deviation Report for Repository Contracts

Deviation Reporting is now available for Repository Contracts, both as a download and attached to approval notification. Standard terms may be modified during contract negotiations, resulting in deviations from company standard policies. For example, a company may require special approvals for refund terms beyond thirty days. Deviations in standard terms are also reported in addition to clause deviations to ensure proper visibility during review and approvals. Business practice organizations can setup these policy rules and enforce them across the enterprise. The rules can be based on user-defined variables or responses to other questions asked during the contract authoring process. These deviations are reported together with other clause deviations in a single report that can be included for approvals. For each deviation, the report also includes


information on what the standard values should be, and any additional approvals that may be required. This feature is forward-ported to 12.2.2.

4.1.3.8. Clause Analysis for Repository Contracts

Clause Analysis is now available for Repository Contracts. Legal or Finance may want to quickly identify all existing contracts that use a certain language that is considered risky to accurately determine risk exposure. Analyzing the contract language may also help in revising existing standards to streamline future contract negotiations or reduce risk. For example, companies can identify the clauses that have been modified the most, and either revise them to be compliant with industry standards or enforce tighter controls to avoid such modifications. Users can search for all contracts where certain clauses are used, or have been modified. The search can be narrowed using various criteria like contracts with a specific customer, contracts above a certain amount, or contracts authored using a specific template. Information on the number of times a certain clause has been used or modified is also provided as part of the results. The results can be summarized by clause type or clause title and exported to Microsoft Excel for further analysis. This feature is forward-ported to 12.2.2.

4.1.3.9. Contract Usability Enhancements

The following usability enhancements have been made to improve user productivity:

• Users can view the clause number in the following pages: Add Clause, Contract Expert Summary, Structured Terms, Update Variables, and Validation Results

• Users can sort the clauses in each section based on the clause number. Additional flexibility to specify tailored sorting rules is supported by the hook OKC_CODE_HOOK.sort_clauses.

• Users can create a hyperlink in the Instruction Text column of a clause, click on the hyperlink, and navigate to an external page.

• Users can add the Clause Description field to the Contract Template, Rules definition and Contract Terms pages. By default the field is hidden. This field can be updated from the Contract Template and Rules definition pages. The list of values for this field comes from a user-defined lookup.

• To support driving contract compliance, the list of all approvers and history of actions is now available on the Repository Contracts History tab.

4.1.4. Release 12.2

4.1.4.1. Repository Contracts Enhancements

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

Oracle E-Business Suite Releases 12.1 and 12.2 Release Content Document Oracle Service Contracts 29

leverage repository contracts to integrate them within their existing business flows in different application modules.

4.1.4.2. UDA support for Deliverables

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

4.1.4.3. MS Word 2010 Certification

The clause and contract terms sync process is now certified for Microsoft Word 2010. Users can now download and view clauses and contract terms in MS Word 2010 and also upload documents edited in MS Word 2010

4.2. Oracle Service Contracts

4.2.1. Release 12.1.1

4.2.1.1. Service Contract Import Program

Oracle Service Contracts now offers a feature to import Warranties, Extended Warranties, unbilled or fully-billed Service Contracts and intangible Subscription Contracts. This capability allows a service contract to be captured from an external 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/sublines 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/sublines 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. This feature is forward-ported to 12.2.2.

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.3. Release 12.2

4.2.3.1. Solution Ordering

Users can now order Subscriptions using Oracle Order Management and have the application create the subscription contracts automatically. The value of the ‘OKS: Category for Order Management Originated Contracts’ profile option is not considered during subscription contracts creation. The Oracle Order Management attributes required for creating subscription contracts are Subscription Template, Duration and Period, Service Start Date and Service End Date, Service Billing Profile, and Service Billing Option.

Service Billing Profile is the value that is set for a sales order and lets the user to bill using multiple periods. If this value is not set for a sales order, then the service or subscription lines consider the Service Billing Option value as Full Billing from Order Management.

Service Billing Option values are ‘Full Billing from Order Management’, ‘Full Billing from Service Contracts’ and ‘First Period Billing from OM, Subsequent from Contracts’.


4.2.3.2. 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/sublines. Users can sort and then update individual lines or a group of lines – such as all lines, all lines for a configuration, or all lines for a given serial number. Changes are processed in the background, so that the user can immediately continue onto their next task.

4.2.3.3. Prevent Deletion of Line/Subline during Contracts Renewal

Oracle Service Contracts has introduced the ability to disallow deletion of lines/sublines during contracts renewal to improve contract revenue leakage analysis. When the customer does not want to continue a service, the line/subline should be cancelled during the renewal process. Disallowing deletion of renewed lines/sublines will ensure users are properly cancelling lines/sublines. Administrators and management have the ability to configure which users will not be allowed to delete lines/sublines 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.3.4. 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.3.5. Revalue Contract during Change in Currency

A new profile option “OKS: Revalue Contract Using Currency Conversion Rate” allows users to configure whether to automatically reprice or allow manual revaluation when the currency is changed on a service contract.

4.2.3.6. Specify Cc Email 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.3.7. 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.3.8. Service Contracts Usability Enhancements

In Release 12.2.2, the following usability enhancements have been made to improve user productivity:

• When adding sublines to an Extended Warranty service line, the Product List of Values shows available instances with several different sort sequences to choose from: Party, Site, Customer, System, Item and Model. Now Configuration will also be an option which displays available instances based on the installed base configuration. It shows top level instances and allows the user to drill down to see all instances in the configuration. As with other levels, users should be able to select one or more displayed instances to add to the contract.

• The cascading attributes action has been enhanced to support concurrent processing. When a service line had a large number of sublines, users were forced to wait until the entire cascade action completed. Now users can specify attributes to be cascaded to all sublines 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 sublines.

• 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.

• Users can view the line and subline 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.

EBS_122_Cum_RCD_OM

Documents

oracle order management

order pricing enhancements

services enhancements

scheduling enhancements

aia order

oracle configurator

oracle corporation

oracle shipping