R12 Planning New Features

8/10/2019 R12 Planning New Features

http://slidepdf.com/reader/full/r12-planning-new-features 1/25

RELEASE CONTENT DOCUMENT

Release 12

Advanced Planning

Prepared by the Advanced Planning Product Management Team

Last Updated: 06/09/2006

Version: 2.0

Copyright © 2006 Oracle. All Rights Reserved



R12 APS Release Content Document, Rev. 01 ii

Table of Contents

1. Disclaimer 1

2. Introduction 2

2.1. Purpose of Document 2

2.2. Reference Documents 2

3. Advanced Planning 3

3.1. Overview 3

3.2. Advanced Supply Chain Planning (ASCP) 4 3.2.1. Features 4

3.2.1.1. Distribution Planning 4 3.2.1.2. Item Attribute Simulation Sets 5 3.2.1.3. Process Manufacturing Enhancements 6

3.2.1.3.1. Support for Complex Routings 6 3.2.1.3.2. Contiguous Operations 7 3.2.1.3.3. Shelf Life 7 3.2.1.3.4. Resource Charges 7 3.2.1.3.5. OPM Inventory Convergence 7

3.2.1.4. OPM Planning Convergence 7 3.2.1.5. Sequence Dependent Setups 8 3.2.1.6.

Gantt Chart Enhancements 8

3.2.1.7. Order Queries 9 3.2.1.8. Reports 9 3.2.1.9. Discrete Manufacturing Integration Enhancements 10

3.2.1.9.1. Actual Work Order Start Dates 10 3.2.1.9.2. Lot-based Component Usage 10

3.2.1.10. Chargeable Subcontracting 10 3.2.1.11. Forecast Spreading for Gregorian Calendars 11

3.3. Demand Planning (DP) 12 3.3.1. Features 12

3.3.1.1. Forecasting Enhancements 12 3.3.1.1.1. Forecast at Day Level 12 3.3.1.1.2. Forecast Seasonal Data at Week Level 12

3.3.1.1.3. Display Smoothed History and Seasonal Factors 12 3.3.1.1.4. Croston’s Method 12

3.3.1.2. Shared Objects 12 3.3.1.3. Selective Forecasting 12 3.3.1.4. Planner Productivity Enhancements 13

3.3.1.4.1. Input Negative Numbers in the Worksheet 13 3.3.1.4.2. Start Date for Moving Totals 13 3.3.1.4.3. Formula-Generated Stored Measures 13

3.3.1.5. Performance Enhancements 13 3.3.1.5.1. Reaggregate Option 13 3.3.1.5.2. Worksheet Performance Enhancements 14



R12 APS Release Content Document, Rev. 01 iii

3.3.1.5.3. Net Change Aggregation 14 3.3.1.5.4. Prevent Even Allocation 14 3.3.1.5.5. Reduce Forced Recalculations 14

3.3.1.6. View Only Access for Planning Manager 14 3.3.1.7. Administration Enhancements 14

3.3.1.7.1. Session Administration 14 3.3.1.7.2. Restart Distribute to Planner Stage 15

3.3.1.8. Collections Enhancements 15 3.3.1.8.1. Collect Facts and Items from a Subset of Organizations 15

3.3.1.8.2. Collect Product Family-Level Manufacturing Forecasts 15 3.3.1.9. Enhanced Support for Forecast Priorities 15 3.3.1.10. Demand History from Internal Sales Orders 15 3.3.1.11. Archiving Process for Oracle Demand Plans 16

3.4. Inventory Optimization (IO) 17 3.4.1. Features 17

3.4.1.1. Demand Fulfillment Lead Time 17 3.4.1.2. Service Agreement Simulation Sets 17 3.4.1.3. Lead Time Variability 18

3.4.1.3.1. Manufacturing Lead Time Variability 18 3.4.1.3.2. In-Transit Lead Time Variability 18 3.4.1.3.3. Enhanced Entry of Purchasing Lead Time Variability 18

3.4.1.4. Plan Level Overrides of Planning Parameters 18

3.4.1.5. Visibility to Forecast Variability 18 3.4.1.6. Enhanced Horizontal Plan 19 3.4.1.7. Item Attribute Simulation Sets 19 3.4.1.8. Order Queries 19

3.5. Global Order Promising (GOP) 20 3.5.1. Features 20

3.5.1.1. OPM-Inventory Convergence 20 3.5.1.2. Lot-based Component Usage 20 3.5.1.3. Distribution Planning 20

3.6. Collaborative Planning (CP) 21 3.6.1. Features 21

3.6.1.1. Distribution Planning 21

3.7. Manufacturing Scheduling (MS) 22



R12 APS Release Content Document, Rev. 01 Advanced Planning 1

1. Disclaimer

This Release Content Document (RCD) describes product features that are proposed for

the specified release of the Oracle E-Business Suite. This document describes new or

changed functionality only. Existing functionality from prior point releases is not

described. It is intended solely to help you assess the business benefits of upgrading to

Release 12.

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




2. Introduction

2.1. Purpose of Document

The Release Content Document (RCD), produced as part of Oracle’s Applications

Product Lifecycle (APL), communicates information about new or changed functionality

in the specified release of the Oracle E-Business Suite. Existing functionality from prior point releases is not described. However, content introduced by Family Packs, Mini-

Packs or Standalone patches since the prior point release has been included in this

document and denoted accordingly.

2.2. Reference Documents

Name Location Completion Date




3. Advanced Planning

3.1. Overview

The major themes for Advanced Planning in Release 12 are:

• Distribution planning enhancements

o Replenish and rebalance inventory across a distribution chain. Consolidate

recommended material movements into truckloads. Fair share limited supply

across customers.

• Process manufacturing enhancements

o Enforce contiguous processing. Support complex routings with multiple

ingredient combination, product separation, and product yield points. Sequence

batches to minimize changeover times.

• Factory planning enhancements

o Sequence production to minimize changeover times. Manipulate shop floor

production plans via a greatly enhanced Gantt chart interface.



R12 APS Release Content Document, Rev. 01 Advanced Supply Chain Planning 4

3.2. Advanced Supply Chain Planning (ASCP)

3.2.1. Features

3.2.1.1. Distribution Planning

The APS distribution planning enhancements provide distribution intensive companies

with the additional features required to effectively plan product movement across thesupply chain. Automating the distribution processes with distribution planning yields an

optimal supply allocation for your distribution network and increased planner efficiency.

The new distribution (DRP) planning features include fair share allocation, multiple

inventory policies, circular sourcing, global forecasting with local allocation of supply,

and ship method selection with load consolidation. Access distribution planning with the

new Distribution Planner responsibility to set up rules and to define and view DRP plans.

For manufacturers, DRP allows the planner to select one or more ASCP manufacturing

plans as supply schedules. It then efficiently distributes the statement of supply from the

ASCP plans. Distributors need only use DRP, and can also define supplier capacities in

Oracle Purchasing that are respected by DRP. DRP supports kitting for distributors withminimal kit assembly requirements.

Use fair share allocation to define rules that automatically allocate scarce supplies

between competing demands with the same priority. With the new supply allocation

form, users specify the fair share allocation methods between multiple organizations. In

the updated assignment set form, planners assign the new supply allocation rules to

organizations, categories, and items. New exceptions alert the planner to supply

allocation problems.

Multiple inventory policies allow planners to specify safety stock, target and maximum

inventory levels for each item-organization. Planners create bands of inventory levels

and inventory levels should fluctuate between the safety stock (or minimum) inventory

level and the target inventory level. Occasionally, inventory may exceed target but never

exceeds the maximum at any point in the distribution network. DRP maintains optimal

inventory balances using supply allocation rules and load consolidation rules to decide

when to ship early, on time or late. New exceptions alert the planner to safety stock,

target and maximum inventory level violations.

Circular sourcing allows the user to create mutual sourcing relationships between

organizations. DRP balances inventory between the defined circular source organizations

before drawing inventory from central sources, thereby achieving efficient distribution of

product without planner intervention. The enhanced sourcing rules form allows the

specification of circular sourcing relationships. New exceptions alert the planner to the

user of circular sources.

Global forecasting allows the planner to create global forecasts and sourcing rules that

automatically allocate both global forecasts and sales orders to the correct source

distribution center. For each demand, global forecasting considers who and where the

customer is, the customer assigned sourcing rules and inventory availability when

selecting the source organization.

Ship method selection and load consolidation between organizations allows the planner

to focus on planner activities. The planner no longer needs to manipulate individual

internal transfers to achieve efficient truck utilization across the distribution network. In




the updated transit times form, the user specifies weight and volume capacity constraints

by ship method. Next, users specify the maximum and minimum shipment utilization

targets in the DRP plan options. DRP creates transfers between organizations that meet

the load consolidation criteria. When DRP violates the shipment minimum or maximum

because of other constraints, the user is alerted to the problem with new exception

messages.

Define DRP plans using the new DRP plan definitions form where the user can specify

global fair share allocation rules, load consolidation targets, planning periods, load

consolidation days horizon, supply allocation bucket sizes and circular sourcing parameters. Users specify the planned organizations with all relevant demand and supply

schedules. Users enable the individual User Defined Decision Rules to control plan

output.

The DRP planners workbench enhancements include the supply allocation plan and the

find opportunities window. The supply allocation plan allows planners to quickly view

and adjust supply allocations between competing demands from customers and other

organizations. Planners use the find opportunities window to quickly find additional

internal transfers to improve a shipment’s utilization. DRP horizontal plan enhancements

allow the planner to easily view the movement of product through a distribution network.

Distribution (DRP) planning is fully integrated with the Oracle E-Business Suite andOracle Supply Chain Planning including Collaborative Planning (CP), Demand Planning

(DP), Inventory Optimization (IO), Advanced Supply Chain Planning (ASCP) and

Global Order Promising (GOP). The planners can integrate DRP, CP and Oracle

Inventory for advanced VMI capabilities. The DRP plan accepts DP and IO output as

demand schedules. GOP can be based on DRP plans, allowing the up to date and

accurate inventory visibility across the supply chain.

3.2.1.2. Item Attribute Simulation Sets

A new setup entity on the APS planning server enables all ASCP plans to more easily

simulate changes to key item attributes. The item attribute simulation set allows you to

attach values of key attributes to item-organizations or to item-regions, then save thoseassignments under an item attribute simulation set name of your choosing. In ASCP plan

options, when you reference a particular item attribute simulation set name, the plan will

use the item attribute values from the named simulation set.

Attributes supported for DRP plans only are:

• DRP Planned

• Max Inventory Days of Supply

• Max Inventory Window

• Target Inventory Days of Supply

• Target Inventory Window

Attributes supported for all ASCP plans are:

• Critical Component

• Preprocessing Lead Time

• Processing Lead Time

• Post processing. Lead Time




• Fixed Lead Time

• Variable Lead Time

• Fixed Order Quantity

• Fixed Days Supply

• Shrinkage Rate

• Fixed Lot Multiple

• Minimum Order Quantity

• Maximum Order Quantity

• Service Level

• Carrying Cost

• Demand Time Fence Days

• Forecast Control

• Planning Time Fence Days

• Standard Cost

• Net Selling Price

• PIP Flag

• Selling Price

• Substitution Window

• Safety Stock Days

• Unit Weight

• Unit Volume

•

Safety Stock Method• Safety Stock Percent

• ABC Class

• Planning Method

• Minimum remaining shelf life days

3.2.1.3. Process Manufacturing Enhancements

The ability of Advanced Supply Chain Planning to plan for process manufacturing

environments has been significantly enhanced as follows:

3.2.1.3.1. Support for Complex Routings

Oracle ASCP supports OPM complex routings with the following characteristics:

• A process can start with multiple operations

• Multiple operations can be executing at the same time

• Single operations can feed multiple operations

• Multiple operations can feed a single operation




• Multiple operations can yield multiple co-products

• Products can be harvested from multiple operations (multiple terminal points)

3.2.1.3.2. Contiguous Operations

In order to support planning according to the common practice of contiguous

processing from raw materials to finished product, ASCP allows you to enforce

minimum and maximum time offsets between two operations. The time offset

constraint can be imposed between the finish of the first operation and the start of thesecond operation, or it can be imposed between the start of the first operation and the

start of the second operation. Planning for contiguous processing is achieved by

imposing finish-to-start maximum time offsets of zero between successive

operations.

3.2.1.3.3. Shelf Life

ASCP respects the expiration date of on-hand lots when pegging them to demand.

For end demands, if the material is planned to arrive at the customer site with a

remaining shelf life less than the parameter Minimum Remaining Shelf Life Days as

set in the item attribute simulation set, ASCP will generate an "insufficient remaining

shelf life" exception.

3.2.1.3.4. Resource Charges

In process manufacturing we might have a work order to produce 1000 units.

Equipment capacity constraints might dictate that those 1000 units actually be made

by producing 100 units and repeating the process 10 times. The individual production

activities are called resource charges.

Oracle ASCP takes into account the individual charges while planning and

scheduling materials and resources. In this process ASCP schedules incremental

feeding from and to chargeable resources.

3.2.1.3.5. OPM Inventory Convergence

Oracle ASCP uses the “Nettable” flag for calculating available on hand quantity for

the netting process. Before this release you could define this flag only at the

subinventory level in the Subinventories window.

With this release, as part of the convergence of Oracle's process and discrete

inventory models, this flag has been moved from the Subinventories window to the

Material Status window, allowing this attribute to be defined at the more granular

levels of locator and lot in addition to the subinventory level.

ASCP supports the more granular definitions of the "Nettable" flag.

In addition, a new checkbox called “Include Non Nettable” in the Subinventory

Netting window of the Plan Options allows you to include the subinventory Non-

Nettable Quantity in the planning process.

3.2.1.4. OPM Planning Convergence

In this release Oracle ASCP unconstrained planning replaces the OPM MRP module.

This allows upgrading OPM customers to use ASCP unconstrained planning in a multi-




org environment. New OPM customers without an ASCP license can only use single org

unconstrained ASCP.

ASCP provides the following advanced features not available in OPM MRP:

• Advanced APS user interface

• Multi-level pegging

• Online planner and simulation capabilities

• Advanced co-product planning

In this release ASCP does not support the following OPM MRP features:

• Replenishment method-specific order modifiers

• Multiple transfer types

• Resizing suggestions

3.2.1.5. Sequence Dependent Setups

During the scheduling process, ASCP explicitly considers setup times that must be

incurred when a resource transitions between tasks that require different setups of theresource. Out of the possible setup sequences on a resource, ASCP will derive one

sequence that minimizes the overall time spent on setting up the resource. Based on user-

specified plan option values, ASCP also trades off the benefit of minimizing setup time

and maximizing resource throughput against the cost of satisfying demands early and

building up inventory.

This capability is available for both discrete and process organizations. ASCP uses the

same setup transition matrix inputs as already used by Manufacturing Scheduling.

When scheduling for a resource for which sequence-dependent setups are specified,

ASCP schedules down to the resource instance level for that resource. Previously, ASCP

scheduled down to the resource level only.

The setup transition matrix associated with a resource can be called up for display from

the Resource details screen of the planner workbench. The calculated setup hours for a

resource can be seen from the horizontal capacity plan for that resource.

3.2.1.6. Gantt Chart Enhancements

The ASCP Gantt chart has been enhanced significantly to increase a planner's ability to

interactively manipulate a schedule output by ASCP and to diagnose problems in the

schedule. Specific enhancements include:

•

Enhanced “Resource View” that shows all activities planned on a resource along thesame horizontal line rather than as separate rows

• Enhanced “Resource View” that gives a picture of bucketed Required Hours versus

Available Hours

• Enhanced “Resource View” that shows the variation of resource units and the units

used over time

• Ability to have multiple views open at the same time e.g. resource view and orders

view




• Ability to transfer information context between the two views e.g. display all

resources used for an order as seen in the orders view over to the resource view

• Ability to save the set of orders or the set of resources as folders that can be invoked

on user command

• Ability to have the other workbench menu options visible when the Gantt chart is

open

• Ability to peg up and down from a supply or a demand. Pegging is shown via arrows

drawn in the right pane of the Gantt chart

• Display of resource instances (for resources with sequence-dependent setups)

• Editing of dates within the left pane of the Gantt chart to manipulate placement of

activities

3.2.1.7. Order Queries

ASCP now supports personal queries for supplies and demands. This allows you to easily

retrieve key supplies such as "purchasing recommendations for supplier Northwest

Supply that need to be released within the next 10 days", and key demands such as "all

top priority sales orders that are satisfied more than 3 days beyond their due date." Order

queries apply to all types of ASCP plans, including the new distribution (DRP) plans.

3.2.1.8. Reports

Oracle ASCP now supports the Planning Detail Report from Oracle Supply Chain

Planning (SCP). You can run this report for a specific plan or based on collected

transaction data.

The SCP Planning Detail Report includes material requirements planning data for a plan

name that you specify. This is a comprehensive planning report that gives you all the

information you need to understand a plan. The report may include the following

sections: Horizontal Listing, Vertical Listing, and detail sections showing gross

requirements, scheduled receipts, planned orders, bill of material and engineeringchanges, expired lot and byproduct information.

This report replaces the following OPM MRP reports:

• MRP Bucketed Material Report

• MRP Material Activity Report

• MRP Action Messages Report

• MRP Error Messages Report

In addition, the Oracle Inventory Reorder Point Report replaces the OPM Reorder Point

Report.

Other OPM MRP reports have been created in a new format. These reports are:

• MPS Material Activity Report (based on source transaction data)

• MPS Bucketed Material Report (based on source transaction data)

The existing Discoverer-based ASCP Planning Detail Report continues to be available.




3.2.1.9. Discrete Manufacturing Integration Enhancements

Oracle ASCP supports the following Oracle Discrete Manufacturing execution

enhancements:

3.2.1.9.1. Actual Work Order Start Dates

Oracle Work In Process (WIP) does not currently capture the actual start times of a

job or activities within a job. With this release, an activity’s actual start date will also

be captured. Current ASCP behavior is to consider a job as having started on itsscheduled start date. With this release ASCP will be able to schedule the completion

of the job using the actual start date.

3.2.1.9.2. Lot-based Component Usage

It is quite common during the assembly of some items to consume components

whose usage does not vary with the job quantity but is fixed. In such cases, the

component usage is deemed to be ‘lot-based’ instead of item-based.

For example:

•

Assembly component is lot based: You are manufacturing a door panelassembly that consists of an injection molded panel and a lock. As part of the job

start process, you produce a fixed number of plastic door panels to cycle in the

process so that you get the parameters set correctly. In such scenarios, you want

to include in the Bill of Material a certain weight of plastic resin that will be used

in the job, irrespective of the job quantity.

• Non-assembly component is lot based: An extrusion process may require that

the extruder’s cylinder be purged of the previous job’s material before running a

new job. This process requires that a special solvent be flushed down the

machine. This solvent is specified on the BOM as a lot-based component.

The above examples illustrate how the usage of certain components will stay fixedand not vary with the size of the job.

ASCP considers lot-based component requirements and ensures correct material

availability.

3.2.1.10. Chargeable Subcontracting

Original Equipment Manufacturers (OEMs) sometimes ship critical components to their

contract manufacturers at the same time that they place orders for complete assemblies.

These ‘sync’ components are meant to arrive at the contractor’s facility right before

assembly of the ordered item begins. Non-sync items, which are generally non-critical

components, are usually shipped in volume quantities to the contract manufacturer.

Both types of components are sold to the contract manufacturer, but any realized or

unrealized gain is not recognized by the OEM for 'sync' components. While ASCP will

provide the planning support for these components, there will be comprehensive support

across the E-Business Suite for managing the underlying transactions.




3.2.1.11. Forecast Spreading for Gregorian Calendars

Previously, the ASCP forecast spreading functionality was limited to forecast scenarios

with time buckets matching the ASCP manufacturing calendar.

With this release, this functionality has been enhanced to apply to forecast scenarios that

use time buckets of Gregorian months.

This functionality is a forward port of an enhancement originally made on top of a

previous release.



R12 APS Release Content Document, Rev. 01 Demand Planning 12

3.3. Demand Planning (DP)

3.3.1. Features

3.3.1.1. Forecasting Enhancements

The statistical forecasting techniques in Oracle Demand Planning are enhanced in several

areas:

3.3.1.1.1. Forecast at Day Level

Forecasting at day-level addresses situations when the demand patterns vary by the

day of the week. For example, beer kegs are sold more on Fridays and Saturdays.

Newspaper is sold more on Sunday than on the remaining days of the week.

3.3.1.1.2. Forecast Seasonal Data at Week Level

The Holt-Winters implementation has been enhanced to support weekly (as opposed

to just monthly) seasonal trends.

3.3.1.1.3. Display Smoothed History and Seasonal Factors

DP automatically performs pre-filtering to smooth demand history to handle outliers

and missing values. DP also automatically calculates seasonal factors. You can now

view the smoothed history and seasonal factors as outputs in DP.

3.3.1.1.4. Croston’s Method

Croston’s method for intermittent demands is now supported.

3.3.1.2. Shared Objects

This feature allows demand planning managers and demand planners to share their

personal objects with other demand planning users. The sharable objects include

documents (reports, graphs, and worksheets), document folders, saved selections, and

custom aggregates.

Demand planning managers can create these objects centrally and then share them with

all the demand planners at any time in the demand planning cycle. This provides a

consistent view of demand planning data to all the users and obviates the need for

demand planners to create the same reports and worksheets individually.


previous release.

3.3.1.3. Selective Forecasting

Selective Forecasting allows users to create a new kind of measure in ODP. This measure

type allows the use of different forecast methods for different products, and allows the

demand for some products to be forecast statistically while the demand for other products

are based on values copied from other measures. After selecting dimension levels in the

same way as when creating a region-copy measure, the user designates one or more

“Forecast” or “Copy” action steps, each one having an associated product selection, date

ranges, and other parameters. The user chooses a set of products for each step by




choosing pre-existing saved selections, or by creating a new saved selection. Proceeding

through the rest of the measure wizard, the allocation, aggregation, and other steps are

similar to those in a simple forecast.

Selective forecasting measures behave similarly to other measures, appearing in the

administrator's measure list and in the document tree under “Forecast” for managers and

planners. The measures are available for distribution, submission, collection, upload, and

in reports, worksheets, and graphs.

3.3.1.4. Planner Productivity Enhancements

DP has been enhanced to improve planner productivity:

3.3.1.4.1. Input Negative Numbers in the Worksheet

Judgmental decisions due to marketing intelligence, new product introductions etc.

are captured either by directly modifying the statistical baseline forecast or by

specifying the adjustments separately and then adding the adjustments to the

statistical baseline forecast. The former process is supported in Oracle Demand

Planning. The latter process requires the additional ability to specify negative

numbers on a worksheet. This feature allows you to manually input negative numbers

on the worksheet to fully accomplish the process of maintaining separate adjustmentsin Oracle Demand Planning.


previous release.

3.3.1.4.2. Start Date for Moving Totals

A cumulative sum or 'moving total' type formula measure can now be specified to

accumulate starting from a specific time period.

3.3.1.4.3. Formula-Generated Stored Measures

You can now use the same set of functions and operations supported for formula

measures (addition, subtraction, multiplication, division, lead, lag, nested formulae,

etc.) for the initial creation of a stored measure. Once created, the stored measure can

be updated on the basis of the generating formula if you explicitly recalculate it.

3.3.1.5. Performance Enhancements

DP has been enhanced to improve performance in a number of areas:

3.3.1.5.1. Reaggregate Option

This feature enables the Administrator to force reaggregation of all measures in theShared database when a change in a hierarchy is detected. The Download process

will automatically determine what hierarchy values have been modified and

reaggregate all measures, i.e. shared and input, for only those values for all time

periods. This allows a measure's values to reflect hierarchy changes without running

a time-consuming re-populate process for the measure.

The Administrator enables the Reaggregate option in the Demand Plan

Administration module by checking a checkbox on the Download screen. The option

is unchecked, i.e. OFF, by default. A Full Distribution for planners’ is required in




order to receive the reaggregated measures. The Reaggregate option will be

examined during distribution, and, if checked, all personal measures will be

reaggregated.

3.3.1.5.2. Worksheet Performance Enhancements

The performance of the worksheet opening, editing, and recalculation operations has

been improved.

3.3.1.5.3. Net Change Aggregation

When you do a quick download of one or more Demand Planning input parameters

(measures) from the planning server, and you use the "update" refresh mode,

aggregation calculations are performed only for those measures values that changed.

3.3.1.5.4. Prevent Even Allocation

Prior to this release, when you entered a value into an empty ('NA') cell in a

worksheet, the value was allocated to the hierarchy levels below using 'even'

allocation. This created an explosion of values in the Demand Planning workspace

and was potentially detrimental to performance.

Now, when you enter a value into an empty 'NA' cell, the value is allocated to the

hierarchy levels below using a 'first level value' allocation method. Only one level

value at each level receives an allocation. This eliminates the explosion of values in

the Demand Planning workspace.

3.3.1.5.5. Reduce Forced Recalculations

Prior to this release, when you edited a value in a worksheet at one hierarchy level

and then tried to edit a value at another level of the same hierarchy, Oracle Demand

Planning would force you to recalculate the worksheet before allowing the second

edit. This enforced consistency of values across hierarchy levels, but potentially

slowed down planners who wanted to make multiple edits without having to wait forrecalculations to complete between each edit.

Demand Planning now supports an administrator option that applies to all worksheets

within a demand plan that turns off the forced recalculation between edits at different

hierarchy levels. Once the worksheet is recalculated or saved, edits are enforced from

the top hierarchy levels down, so it is possible for an edit at a higher hierarchy level

to override an edit at a lower hierarchy level.

3.3.1.6. View Only Access for Planning Manager

A new role is available, Planning Manager – Read Only, which allows a user to view all

data in the Shared database and create documents and share reports. However, datacannot be changed, shared or submitted.

3.3.1.7. Administration Enhancements

A number of administration enhancements allow the Demand Planning Administrator to

more effectively manage the progress of a demand planning cycle.

3.3.1.7.1. Session Administration




A new screen enables the Demand Planning Administrator to view the login sessions

for a demand plan, and, if necessary, terminate them. This allows a demand plan

session to be restarted gracefully in the case of an exceptional error condition without

the need for technical database administrator assistance.

3.3.1.7.2. Restart Distribute to Planner Stage

If the Distribute to Planner stage of the Demand Planning cycle terminates

abnormally, the Demand Plan Administrator can restart the process from the

beginning. Previously, restarting this process required the intervention of a technicaldatabase administrator.

3.3.1.8. Collections Enhancements

3.3.1.8.1. Collect Facts and Items from a Subset of Organizations

A new checkbox in the Organizations sub-form of the Application Instances form

enables an organization for Demand Planning independently of its enablement for

Advanced Supply Chain Planning. This allows companies who have implemented

ASCP at many locations but implemented DP at only a few of those locations to

collect DP fact data from just a small subset of the ASCP-enabled organizations. This

saves time on collections.

If you enable and maintain the same items in all organizations that you plan, you can

also save time on collections by invoking a new option (enabled via profile option)

collect items only from the master organization.

3.3.1.8.2. Collect Product Family-Level Manufacturing Forecasts

Oracle Demand Planning now supports the collection of manufacturing forecasts

defined for product family items.

3.3.1.9. Enhanced Support for Forecast Priorities

In Oracle Demand Planning, you can very flexibly specify, down to the individual entry

level, the priority to be associated with forecasts. You can then feed this information into

Oracle Advanced Supply Chain Planning to drive planning decisions there. This gives

you the freedom to prioritize forecasts by demand class, by customer, by product, by

location, by time.

To set up this capability, you need to define a demand plan with at least two output

scenarios: the normal forecast output scenario, and a "forecast priority" output scenario.

In the Scenarios tab of the demand plan definition form, you can specify for each forecast

output scenario which other output scenario should be interpreted to be the set of forecast

priorities associated with the forecast output scenario. The output levels of the forecast

output scenario and the forecast priority scenario must match. When the forecast outputscenario is used as a demand schedule in an ASCP plan, the associated priorities from the

associated forecast priority scenario are passed into ASCP as the forecast priorities.

3.3.1.10. Demand History from Internal Sales Orders

In Release 11i10, Demand Planning ignored demand history based on internal sales

orders. In Release 12, to support demand planning processes for individual lines of

business within a larger enterprise that runs on a global single E-Business Suite instance,

Demand Planning recognizes demand history from internal sales orders to user-selected




organizations internal organizations. Thus lines of business that run their own demand

plans and fulfill demands from internal organizations can recognize the history of those

demands and create forecasts for those demands.

A new plan option field ("Select Internal Sales Orders For") in the Scope tab of the

demand plan definitions form allows you to specify which internal sales orders to

consider. All internal sales orders containing one of the destination organizations that you

list in the field will be considered.

3.3.1.11. Archiving Process for Oracle Demand Plans

A new process is available for archiving a demand plan for future recovery. Previously,

no process was available for backing up a demand plan.

Two new concurrent requests are available for archiving and restoring a plan. The

concurrent requests are named:

• Archive Demand Plan

• Restore Demand Plan

Both "Archive Demand Plan" and "Restore Demand Plan" require only a demand plan

name as a parameter. The archive process will write to a log named "arch[plan_id].log" inODPDIR.

The DP System Administrator runs a request to Archive or Restore a plan. The DP

System Administrator should ensure there is enough space before starting the archive

and/or restore processes.



R12 APS Release Content Document, Rev. 01 Inventory Optimization 17

3.4. Inventory Optimization (IO)

3.4.1. Features

3.4.1.1. Demand Fulfillment Lead Time

Demand fulfillment lead time (DFLT) is the time allowed by the customer or by

established business practice between order placement and order fulfillment. Customerservice level targets are typically expressed with respect to specific DFLTs (for example,

95% service level for 3-day DFLT). In previous releases, Oracle Inventory Optimization

assumed that the DFLT was zero.

You can specify demand fulfillment lead time at the following levels:

• Item-Org –Demand Class

• Item-Demand Class

• Item-Category-Demand Class

• Item-Org

• Category

• Demand Class

• Customer site

• Customer

• Org-Demand Class

• Org

You can enter DFLT as an integer or a fractional number of days. For example, a 4-hour

DFLT would be entered as 0.167 days.

3.4.1.2. Service Agreement Simulation Sets

A new setup form allows you to enter demand fulfillment lead time (DFLT) and service

level targets together, at each of the levels specified above for demand fulfillment lead

time.

Starting with Release 12, entry of service level targets via flex fields in Oracle Inventory

(for targets at the item-org and org levels), in Oracle Order Management (for targets at

the customer level), and in the Allocation Rules form (for targets at levels involving

demand class) is de-supported. Entry of service level targets is permitted only in the new

integrated demand fulfillment lead time / service level target entry form. Upgrade scripts

facilitate migration of the old setups to the new form.

You can save a collection of service agreement (service level-DFLT) assignments as a

named simulation set. This set can be attached to an IO plan. IO will apply the target

service levels and DFLTs within the simulation set when generating the plan output. This

allows you to simulate different service agreement scenarios using IO.




3.4.1.3. Lead Time Variability

Inventory Optimization's ability to consider variability of various lead times in the

calculation of safety stocks has been expanded as follows:

3.4.1.3.1. Manufacturing Lead Time Variability

In addition to forecast and purchasing lead time variability, Inventory Optimization

now considers manufacturing lead time variability.

Manufacturing lead time variability is expressed as a standard deviation of the item

processing lead time, and is entered via the item details window of the collections

workbench.

The statistical distribution of manufacturing lead time is assumed to be normal.

3.4.1.3.2. In-Transit Lead Time Variability

In addition to forecast and purchasing lead time variability, Inventory Optimization

now considers in-transit lead time variability.

In-transit lead time variability is expressed as a standard deviation of the ship methodtransit time, and is entered via the Transit Times form on the planning server.

The statistical distribution of in-transit lead time is assumed to be normal.

3.4.1.3.3. Enhanced Entry of Purchasing Lead Time Variability

Previously, IO supported the entry of supplier lead time variability only via the

specification of a histogram (a collection of purchasing lead time-probability pairs).

IO now supports the entry of this variability as a single standard deviation value for

the supplier processing lead time. The distribution of supplier variability is assumed

to be normal.

3.4.1.4. Plan Level Overrides of Planning Parameters

To facilitate rapid simulations, you can now enter in plan options plan level overrides of

key Inventory Optimization planning parameters:

• Service level

• Fulfillment lead time (see the design for fulfillment lead time)

• Budget value

• Manufacturing variability - % variation

• Supplier lead time variability - % variation

• In transit lead time variability - % variation

If entered, these values supercede all values specified at more granular levels.

3.4.1.5. Visibility to Forecast Variability

The MAD (mean absolute deviation) and MAPE (mean absolute percentage error)

metrics for forecasts calculated in Oracle Demand Planning and fed into Oracle Inventory




Optimization are now visible in new columns of the supply/demand window of the IO

planner workbench.

3.4.1.6. Enhanced Horizontal Plan

The horizontal plan of the IO planner workbench can now display the following

additional rows:

1. Target Service level (expressed in %)

2. Achieved service level (expressed in %)

3. Mean absolute deviation (MAD)

4. Mean absolute percent error (MAPE)

5. Safety stock – non pooled (units)

6. Safety stock units has four sub-rows to display the percentage of safety stock to be

carried to protect against the variabilities below:

•

Demand variability

• Manufacturing variability

• Supplier lead time variability

• In-transit lead time variability

3.4.1.7. Item Attribute Simulation Sets

Item attribute simulation sets enables all IO plans to more easily simulate changes to key

item attributes. The item attribute simulation set allows you to attach values of key

attributes to item-organizations or to item-regions, then save those assignments under an

item attribute simulation set name of your choosing. In IO plan options, when you

reference a particular item attribute simulation set name, the plan will use the itemattribute values from the named simulation set.

3.4.1.8. Order Queries

IO now supports personal queries for orders. This allows you to easily retrieve key

demand and supply orders such as "forecasts for all items with service level violations".

As the above condition implies, in addition to retrieving orders on the basis of standard

attributes such as quantity, due date, planner code, and order type, you can retrieve orders

related to exceptions that are flagged by IO.



R12 APS Release Content Document, Rev. 01 Global Order Promising 20

3.5. Global Order Promising (GOP)

3.5.1. Features

3.5.1.1. OPM-Inventory Convergence

GOP uses the “Include in ATP” flag for calculating on hand availability for promising to

customers. Before this release you could define this flag only at a subinventory level inthe Subinventories window.

With this release, as part of the convergence of Oracle's process and discrete inventory

models, this flag has been moved from the Subinventories window to the Material Status

window, allowing this attribute to be defined at the more granular levels of locator and

lot in addition to the subinventory level.

GOP supports the more granular definitions of the "Include in ATP" flag.

3.5.1.2. Lot-based Component Usage

GOP respects lot-based component usages during the calculation of promise dates.


Global Order Promising against a DRP plan is supported.



R12 APS Release Content Document, Rev. 01 Collaborative Planning 21

3.6. Collaborative Planning (CP)

3.6.1. Features


You can publish order forecasts and supply commits from a DRP plan to suppliers and

customers in CP. You can receive supply commits posted by suppliers in CP and consider

those as supplier capacity updates in subsequent DRP plan runs.



3.7. Manufacturing Scheduling (MS)

No new features have been introduced in Release 12 of Oracle Manufacturing

Scheduling.