Professional Documents
Culture Documents
O E-B S R V P: Release 12.1 Order Management
O E-B S R V P: Release 12.1 Order Management
Prepared by E-Business Suite Product Management and Strategy Last Updated: Version: April 9, 2009 1.3
Table of Contents
1. 2. 3.
4.
4.2.
4.2.1. 4.2.2.
4.3.
4.3.1. 4.3.2. 4.3.3.
5.
5.2.
5.2.1. 5.2.2.
5.3.
5.3.1. 5.3.2. 5.3.3.
6.
ii
6.1.4.
6.2.
6.2.1. 6.2.2.
7.
7.2.
7.2.1. 7.2.2.
iii
1.
Disclaimer
This Release Value Proposition (RVP) describes the key benefits of select product features proposed for the specified release of the Oracle E-Business Suite. This document describes new or changed functionality between E-Business Suite 11i.10 and 12.1. It is intended solely to help you assess the business benefits and value 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.
Purpose of Document
2.
Introduction
2.1. Purpose of Document
This document describes the value associated with the new features and enhancements that are planned for Oracle E-Business Suite Release 12.1 (inclusive of features and enhancement from Release 12). It is a roadmap that is intended to help you assess the business benefits of Release 12.1 and plan your information technology (IT) projects and investments. The new features and enhancements included in this document are grouped by product. Our goal is to ensure that you leverage technology to its fullest to increase the efficiency and effectiveness of your operations. Please note that the final release may not include every feature discussed in this document, and a specific feature may become part of a different application or have a different product name from that cited in this document.
Purpose of Document
3.
Improve order management productivity Improve customer experience Reduce order management costs
3.1.
3.2.
percent increase in profits, while a ten percent increase means an additional 50 cents in earnings per share (Source: AMR). Not only do customers count on their orders to be perfect, but also they expect the buying experience to be easy, fast, and flexible. Information should be available at their fingertips, such as the latest price book. Ordering complex, configurable products should require a minimum number of clicks. Customers want flexibility on when and how they place and accept sales orders. Business success depends on the ability to attract and retain customers through continuously improving the customer buying experience.
3.3.
4.
Achieve the perfect order Improve customer experience Reduce order management costs
4.1.
4.1.1.
Item Orderability
Businesses need the ability to define which customers are allowed or disallowed to order which products, and the ability to apply this business logic when a customer sales order is created. For example, repair parts may be sold only to authorized dealers; video games may be sold only to customers who meet age requirements; and controlled drugs may only be sold to customers with a valid unexpired DEA license. In Release 12.1, item orderability ensures that companies are selling the right products to the right customers. Flexible rules can be defined which prohibit certain products and/or product categories from being sold to specific customers and/or customer classes.
4.1.2.
4.1.3.
Cascading Changes
On average, customers change sales orders over three times per order. When attributes of the order such as the bill-to or ship-to address, etc. are modified, it is a potentially
error-prone process to require these attributes to be manually changed on each and every line. In Release 12, attributes can be modified on the sales order header, which are then automatically applied to all of the lines on a sales order. The automation of cascading changes from sales order header to lines will improve the number of orders entered, shipped and invoiced without errors and correspondingly result in more perfect orders for your customers. 4.1.3.1. Improved Internal Requisition/Internal Order Change Management
As supply chains have become global, companies have consolidated the number of locations where they hold inventory, which has correspondingly increased the volume of inventory transfers within a companys supply chain network. Internal requisitions are also generated by field service coordinators ordering spare parts within the internal inventory network, R&D organizations obtaining materials needed in the prototyping of new products, warehouse managers manually building shipments of material from one warehouse to another, and employees requesting material which is sourced internally. Since sales orders are changed on average 3.5 times before they are fulfilled, an efficient and automated change management process for requested internal transfers is also important. Automated internal requisition and internal sales order change management in Release 12.1 improves the communication and visibility of changes to internal transfer requests between the requesting and the fulfillment organizations. This reduces the number of stockouts due to a more accurate picture of how much and when the requested material will arrive.
4.1.3.2. Ability to create sales agreements from external/legacy systems Public APIs for creating sales agreements allow you to create sales agreements from quotes and external sources and helping you achieve the perfect order.
4.2.
4.2.1.
Customer Acceptance
In some industries and geographies, invoicing and/or revenue recognition for shipped goods are deferred until the customer formally accepts the material. For example, complex equipment may first be installed and tested before the customer accepts the product. Customer acceptance is a pervasive business practice in some regions, such as Asia Pacific. In Release 12, customer acceptance can be captured using a variety of channels, giving customers their choice of how they prefer to communicate their acceptance of a product. The customer may call or email a sales order administrator, enter the acceptance directly using the self-service user interface of the Order Information Portal, or perform the acceptance in another system (such as their own) and the acceptance will be imported. A product shipment may also be implicitly accepted automatically after a certain number of days. The ability to communicate customer acceptance using several channels enhances the customer experience.
4.2.2.
4.3.
4.3.1.
Shared Services
Shared Services provide a proven way for governments and businesses to gain better control of their finance operations and streamline redundant processing and systems. A Shared Services model of operations drives cost savings and increases information quality. Organizations are increasingly consolidating administrative tasks in Shared Service Centers as a way to focus on their core competencies, increase efficiencies, and better manage and access information. Additionally, they can cut operating costs by eliminating redundant processes, leveraging self-service, automating processes, and standardizing common business practices. Increase the productivity of your shared service personnel with role-based access to various organizations in your corporate structure. In Release 12, Multiple Organization Access Control (MOAC) enables them to process transactions for different operating units without having to change responsibilities. For example, users no longer need to switch responsibilities in order to view, enter or mange customers sales orders. You control who can perform which tasks through security profiles that define each users access to a specified group of operating units.
4.3.2.
4.3.3.
Achieve granular control of order processing by the 17 new attributes for hold source criteria. Order workflows automatically restart when a hold is released. A new concurrent request to reprice order lines, based on several parameters, enables you to automate repricing requirements, reducing order management costs.
5.
Accelerate sales cycle Drive contract compliance Support centralized contract organization
5.1.
5.1.1.
5.1.2.
offline in a word processor to work with the document in a familiar format and easily see changes (redlining). Release 11i10 allowed contract administrators or legal to download the contract into Rich Text Format (RTF) for editing and collaboration in Microsoft Word. In Release 12, Oracle Sales Contracts now supports Microsoft Word Synchronization including import of the Word document and the synchronization of the changes with the structured contract terms stored in the system. Modifications to the original contract can be reviewed before changes are accepted. Policy rules for mandatory and protected clauses are enforced during import, and all clauses modified in Word are marked as non-standard in the system. The Microsoft Word synchronization accelerates the contract collaboration process involving the sales representative, contract administrator, legal and customer.
5.1.3.
5.2.
5.2.1.
5.2.2.
10
Contracts from Oracle Sales using additional bins in the customer 360-degree view that
displays all existing contracts with the customer and active sales agreements. Sales managers can also view the details of specific contracts, or access the signed contract document from the central repository.
5.3.
5.3.1.
5.3.2.
5.3.3.
11
6.
6.1.
Simplified Modeling
The Fusion Configurator Engine provides a number of key new features that make the process of creation and maintenance of configuration models easier and more intuitive. These features enable model developers to simplify the increasing complexity of product offerings and ensure rapid time to market to leverage first mover advantage.
6.1.1.
Improved Defaulting
Rule definition now allows classification of a rule as a default allowing additional flexibility in providing guidance to the end users and more quickly getting them to a complete and valid configuration. In addition to the pre-existing Default Rules model, developers can now also classify Logic Rules, Comparisons, and Statement Rules as being defaults. Using the Rule Sequences model developers now also have the ability to specify a preferred order for executing default rules making it easier to design and build configuration models. This also provides greater control and predictability in the guidance of the end-user towards a set of desirable configurations. Default rules are enforced when possible and may be overridden by end-user selections, but this additional flexibility allows greater control over the starting configuration offered to the end users. End users are able to complete their configurations more quickly, resulting in valuable time savings.
6.1.2.
Simplified Modeling
12
Circular propagation is prevented avoiding costly debugging and configuration rule rework on the part of model designers There is a much reduced need for repetitive contributes rules to express equations, saving time in model development Complications from intermediate values with Comparison Rules are avoided
The enhanced numeric capabilities also allow the Configuration Modeler to more easily translate business rules into Configurator rules.
6.1.3.
6.1.4.
6.2.
6.2.1.
13
Specifying a Sequence for Defaults and Search Decisions Indicating how you want Auto-Complete to provide values for unbound Numeric and Boolean Features Specifying minimum and maximum values for all Model nodes
6.2.2.
14
7.
7.1.
7.1.1.
Price Books
With Release 12, you will be able to reduce costly customizations for creating and distributing pricing information with Oracle Advanced Pricings Price Book functionality that automates price publishing. Prior to Release 12, there were no workarounds to enabling customers to create price books. Companies can now easily create and publish price books to customers and partners via on-line or xml. Price Books gives the user multiple parameters to select from to generate the price report. Companies can view the results of the generated price book before publishing or executing electronically. Price Books also supports Oracle XML Publisher that enables companies to tailor the Price Book to meet the companies presentation standards.
7.2.
7.2.1.
15
customer hierarchies. Yet customer party definitions change frequently and keeping these definitions aligned with the pricing for these customers can be challenging and costly. In Release 12, Advanced Pricing now recognizes customer party hierarchies defined in Oracle Trading Community Architecture (TCA). This new feature significantly reduces maintenance costs in setting up data and reduces errors by looking at the master definition of TCA party information. Now qualifiers need only to be created at the parent party or any level below and Advanced Pricing will automatically apply pricing or discounting at any customers below this level. Also Advanced Pricing automatically looks at the most current TCA party hierarchy thus as the party definition changes in TCA, Advanced Pricing automatically has the most current customer party information.
7.2.2.
16