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: April 5, 2011

Version: 1.0 Copyright © 2011 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.2. Oracle Configurator 4 3.2.1. Overview: Fusion Configurator Engine 4 3.2.2. Release 12.1.1 4

3.2.2.1. Numeric Handling 4 3.2.2.2. Improved Defaulting 4 3.2.2.3. Auto-instantiation 4 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 5 3.3.1.3. Support Decimal Qantity 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 6 3.3.1.7. Customer PO-based Search in Scheduling Organizer 6 3.3.1.8. Visibility to Latest Configuration Till Picking 7 3.3.1.9. Line Level Credit Check Enhancement 7 3.3.1.10. Post Booking Item Substitution 7 3.3.1.11. Defer Split for Configurations 7 3.3.1.12. Internal Requisitions/Internal Sales Order Change Management 7 3.3.1.13. Order Management Productivity Enhancements 8 3.3.1.14. Sales Agreements Enhancements 9 3.3.1.15. Seeded Return Line 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 10 3.3.3.1. International Trade Management Adapter Enhancements for Global Trade Management (GTM) 10

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

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

3.3.4.2. Order Information Portal (OIP) Enhancements 11 3.3.4.3. Tax Calculation on Freight Charges 12 3.3.4.4. Specify Recipient/Role for Credit Check Hold Notifications 12 3.3.4.5. Allow Users with View-Only Access to Release Orders on Credit Check Hold 12 3.3.4.6. Allow Users with Ability to Apply Holds to Search by Hold Name 13 3.3.4.7. Consistency in Display of Credit Hold Flag after Customer Merge 13 3.3.4.8. Increase in Size of Freight Carrier Name Field 13

3.4. Oracle Shipping 13 3.4.1. Release 12.1.1 13

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

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

4. New and Changed Features in Contracts 15

4.1. Oracle Sales Contracts 15 4.1.1. Release 12.1.1 15

4.1.1.1. Structured Terms Authoring in Repository Contracts 15 4.1.1.2. Secure Enterprise Search 15

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

4.1.3. Release 12.2 16 4.1.3.1. Apply Multiple Templates to a Sales Document 16 4.1.3.2. Templates, Rules, Questions and Constants Import 16 4.1.3.3. New Clause Descriptor Field 16 4.1.3.4. Clause Mandatory Attribute at Rule level 17 4.1.3.5. Display Clause Numbers in Different Pages 17

4.2. Oracle Service Contracts 17 4.2.1. Release 12.1.1 17

4.2.1.1. Service Contract Import Program 17 4.2.2. Release 12.2 17

4.2.2.1. Service Contract Re-pricing Performance Enhancements 17 4.2.2.2. Contract Renewal Performance Enhancements - Date Assembler Changes 18

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

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

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

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 Qantity 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 Pr iority”

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 Booking, Scheduling, Schedule Date Changes and Shipping. In addition, external users can choose to receive notifications individually for each sales orders 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. 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.5. Allow Users with View-Only Access to Release Orders on Credit Check Hold

Currently, only users with the ability to edit the sales order can release a sales order that has been placed on credit check hold. Users with view-only access to sales orders cannot release orders that have been put on credit check hold even if they are authorized to do

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

so. In Release 12.2, users with view-only access can also release sales orders from credit check assuming that they are authorized to do so.

3.3.4.6. 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.7. 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.8. 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 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.

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

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.

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

4. New and Changed Features in Contracts

4.1. Oracle Sales Contracts

4.1.1. Release 12.1.1

4.1.1.1. Structured Terms Authoring in Repository Contracts

The Contracts Repository module enables customers to easily manage all their contracts online. It provides basic contract management capabilities and global, secure visibility to key stakeholders.

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.1.2. Secure Enterprise Search

Oracle Sales Contracts now leverages 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.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

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

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

4.1.3.1. 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 the 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.2. Templates, Rules, Questions and Constants Import

Importing new templates, rules, questions, and constants is supported using APIs. There are separate APIs for:

• Templates

• Rules

• Questions and Constants

These can be used to both create new entities and update existing templates and rules. The APIs return error and warning messages which can be processed and analyzed by the customer.

4.1.3.3. New Clause Descriptor Field

There is a new hidden clause descriptor field added to the Contract Template, Rules definition and Contract Terms pages. This field can be updated from Contract Template and Rules definition pages. The list of values for this field comes from a user defined lookup.

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

4.1.3.4. Clause Mandatory Attribute at Rule level

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.

4.1.3.5. Display Clause Numbers in Different Pages

Clauses are often recognized by the clause numbers – and this is especially true in the case of public sector / government organizations. The users often use the clause numbers to locate and use a clause, rather than the clause title. Since it is so important to display the clause number along with the title, the clause number will be available on the following pages:

• Contract Terms page

• Search Results page when adding a new clause to a contract or template

• Update Variables page

• Contract Expert summary page

• Contract Expert – submit for approval page

• Contract Expert – create rule – add clause page

The number column in most cases will not be visible by default and will have to be rendered via personalization.

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

4.2.2.1. Service Contract Re-pricing Performance Enhancements

In Release 12.2 Oracle Service Contracts has made performance enhancements to the re-pricing of service contracts during contract renewal.

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

• 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. Contract Renewal Performance Enhancements - 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 to complete the renewal process. To improve the performance of the service contract renewal process, this feature controls the number of service contracts to be processed concurrently for renewal.

In Release 12.2 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.”

ebs_122_cum_rcd_om

Documents