ORACLE E-BUSINESS SUITE RELEASE CONTENT DOCUMENT

Value Chain Planning Releases 12.1 and 12.2 (inclusive of 12.0.2 – 12.0.7)

Prepared by the VCP Product Management and Strategy Teams

Last Updated: Version:

April 5, 2011 1.0

Copyright © 2011 Oracle Corporation All Rights Reserved

Table of Contents

1. 2.
2.1.

Disclaimer Introduction
Purpose of Document

1 2
2

3.
3.1.

New and Changed Features in Value Chain Planning
Collections
3.1.1. Release 12.1.1 3.1.1.1. Backward Compatibility to 11i10

3
3
3 3

3.2.

Oracle Advanced Planning Command Center
3.2.1. Product Overview 3.2.2. Release 12.1.1 3.2.2.1. Sales and Operations Planning Dashboard 3.2.2.2. Supply Chain Analyst Dashboard 3.2.2.3. Analytical Framework 3.2.2.4. Scenario Management 3.2.2.5. Supply Chain Planning Web Services 3.2.2.6. Seeded BPEL Processes 3.2.2.7. Process Automation 3.2.2.8. Activity Management 3.2.3. Release 12.1.2 3.2.3.1. Compatibility with 11.5.10 Planning Server 3.2.3.2. Integration to Third Party Planning Systems 3.2.3.3. Ability to Run APCC Standalone 3.2.3.4. Rich User Interface Enhancements 3.2.4. Release 12.1.3 3.2.4.1. Analysis of Inventory and Service Levels 3.2.4.2. Analysis of Excess and Obsolescence 3.2.4.3. Enhanced Sales and Operations Planning Dashboard 3.2.4.4. Supply Chain Risk Management Dashboard 3.2.4.5. Revenue Gap Analysis 3.2.4.6. Collaboration Workspaces for Unstructured Collaboration 3.2.4.7. Enhanced Exceptions Analysis 3.2.4.8. Integration with Rapid Planning 3.2.4.9. Plan Versus Collected Data Comparison 3.2.5. Release 12.1.3.2 3.2.5.1. New Dimension – End Item 3.2.5.2. New Dimension – Parent Model 3.2.6. Release 12.2 3.2.6.1. Plan-specific Forecasting Measures 3.2.6.2. Custom Series from Demantra DM and RT S&OP 3.2.6.3. Support for Custom Demantra Product Hierarchy 3.2.6.4. Integration with Distribution Planning

3
3 4 4 5 6 7 7 7 8 8 8 8 9 9 10 10 10 10 10 11 12 12 12 13 13 13 13 14 14 14 14 15 15

3.3.

Oracle Advanced Supply Chain Planning

16
ii

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

3.3.1. Release 12.1.1 3.3.1.1. Oracle Transportation Management Integration 3.3.1.2. Optimization Enhancements 3.3.1.3. Contiguous Processing 3.3.1.4. Minimum Remaining Shelf Life 3.3.1.5. Distribution Planning Scalability Enhancements 3.3.1.6. End Item Substitution Enhancements 3.3.1.7. Production Schedules as Inputs 3.3.1.8. Safety Lead Time 3.3.1.9. Customization of Horizontal Plan 3.3.1.10. Supply Tolerancing Enhancements 3.3.1.11. Buy Order Processing Lead Time Backward Compatibility 3.3.2. Release 12.1.2 3.3.2.1. Release Recommendations for Internal Requisitions 3.3.2.2. Turn Off Planned Order Creation 3.3.2.3. Consume Purchase Orders in First In, First Out Sequence 3.3.3. Release 12.1.3 3.3.3.1. Forecast Spreading Based on Shipping Calendar 3.3.3.1. Excluding Planned Orders from Supply Tolerancing 3.3.3.2. Maximize Use-Up of Substitute Components 3.3.3.3. Distribution Planning Enhanced Order Modifier Support 3.3.4. Release 12.1.3.2 3.3.4.1. Forecast Explosion Enhancements 3.3.5. Release 12.2 3.3.5.1. Supplier Capacity Consumption Enhancement 3.3.5.2. Enhanced Exception Management

16 16 16 16 17 17 17 18 18 18 18 19 19 19 19 20 20 20 21 22 23 23 23 24 24 25

3.4.

Oracle Collaborative Planning
3.4.1. Release 12.1.1 3.4.1.1. Export Exception Details 3.4.1.2. Detailed Supply Commit Based on ASCP Pegging 3.4.1.3. Search Exceptions by Buyer and Planner 3.4.2. Release 12.1.2 3.4.2.1. Rich User Interface Enhancements 3.4.3. Release 12.1.3 3.4.4. Release 12.2

25
25 25 25 25 26 26 26 26

3.5.

Oracle Demand Planning
3.5.1. Release 12.1.1 3.5.1.1. Clear Data in Worksheets 3.5.1.2. Default Even Allocation Over Time 3.5.1.3. Plan Security by Responsibility and Organization 3.5.1.4. Sort by Product in Planning Percentages Worksheet 3.5.1.5. Data Selection Tools for Region Copy Selector 3.5.1.6. Prevent Planners from Editing Measures in View Scope 3.5.2. Release 12.1.2 3.5.3. Release 12.1.3 3.5.4. Release 12.2

26
26 26 26 26 27 27 27 27 27 27

3.6.

Oracle Demand Signal Repository
3.6.1. Product Overview 3.6.2. Release 12.1.1 3.6.2.1. Customer Organization Hierarchy 3.6.2.2. Multiple Calendar Support 3.6.2.3. Customer Item Hierarchy 3.6.2.4. Manufacturer Item Hierarchy 3.6.2.5. Multiple Currency Support 3.6.2.6. Alternate Units of Measure 3.6.2.7. Authorized Distribution 3.6.2.8. Sales Allocation

27
27 28 28 28 28 29 29 29 29 30

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

iii

4.6.9. Analytical Engine on Solaris 10 3. User Defined Fields 3.17. Release 12.7.25. All Commodity Volume (ACV) / External Measures 3. Inventory 3.11.2 30 30 30 30 30 31 31 31 31 32 32 32 32 33 33 33 33 34 34 34 34 35 35 36 37 37 38 39 39 39 40 40 40 41 43 43 44 44 3.4.8. Engine Performance Improvements 3.2.19.6.18. Type 2 Slowly Changing Dimensions 3.1.4.2.1.2.1.3.24.1.2.7.14.6. Category Growth Analysis Reports 3.5.7. Third Party Distributors 3.2.6.4.6.2.2 3.4.2.27.26.6. Retail Merchandising System (RMS) Integration 3.6. Calendar Month Support in Weekly System 3. Sales Facts 3.4.6.1.7.1.5.6.6.1.13.6. Release 12.2. Release 12.7. Enhanced Integration with Advanced Planning Command Center 47 47 47 3.8.7.3.4.1.3. Oracle Demantra Demand Management 3.6.23. Operations Scorecard 3.9.1.7.4.4.2 47 47 Oracle E-Business Suite Releases 12. Demand Variability Definition 3.3.7.6.6.3. Ad-Hoc Reporting 3. Average Price Analysis Report 3. Release 12.2. Demantra Demand Management Integration 3. Import from Excel 3.1.7.6.6.9.9.6.3.2. General Engine Enhancements 3.1.2.2.1. Product to Category Coverage Reports 3.6.1.10. Asynchronous Workflow Support 44 44 44 45 45 45 45 45 46 46 46 46 46 47 3.12. Integration Data Profile Hints 3.7.20.12. Technology Stack 3.6. TDLinx Store/Outlet Adapter 3. Release 12.2. Store Clusters 3. Sales Scorecard 3.6. Shipments 3. Oracle Demantra – All Products 3. Alternate Organization Hierarchy 3.10.6.1. Promotion Plans 3.6.1.1. Release 12.6. Manufacturer Shipments 3.15.6.3.6.2.1. Category Sales Analysis Dashboard 3.6. Exception Management Dashboard 3. Database Performance Improvements 3. Improved Multi-Language Support 3.1 and 12. Orders 3. Item Clusters 3.2. Supply Chain Scorecard 3.6.1.6.7.2. Manufacturer Promotions 3.6.2.3 3.3.8.6.1.6.2.4.3.1.6.5.2 3.2.6. Scorecard Enhancements (Goals & Thresholds) 3.1.3.2 3.2.3.2.7.6.5. Top and Bottom Performers Reports 3. Customer Shipment Facts 3.8.6. Configure Rolling Profile Groups 3.2 Release Content Document iv .11.6.7.22. Replenishment Rules 3.8.3.8.6.16.4.1.7.4.6. Category Sales by Type Reports 3.7. Forecast Type and Purpose Code 3. Web Services Integration 3.2. Sales Forecasts 3.7.6.3.21.6. Allocation Rules 3.7. Oracle Demantra Real-time Sales and Operations Planning 3.6.

9. Minimize Work Order Schedule Infeasibilities 3. Maintenance Work Order Scheduling 51 51 51 51 52 53 53 54 55 55 56 57 59 60 61 62 65 67 69 69 70 70 71 72 72 73 73 75 76 77 78 79 80 80 v Oracle E-Business Suite Releases 12. Batchable Resources 3. Automatic Reconciliation of Schedule Backlog 3.10.12.1.14.2.3 3.1.14.2 Release Content Document .14.11.1.1. Enabling Nodal Tuning 3. Resource-specific Cycle Times for Campaign Run Optimization 3.2.19.3. Release 12.11.1.14.3.1. Oracle Production Scheduling 3.1.2 3.13.3 3.1. Drilldowns from the Work Order Editor to the Gantt Charts 3.2.14.2. Oracle Demantra Predictive Trade Planning 3. Work Order Centric KPI Comparisons 3. Release 12.1.14. Undo Functionality for Manual Scheduling 3. Release 12.3.1.11. Release 12.2 3.1 3. Find Functionality for Model Objects 3. Attribute Based Sequence Dependent Setups 3. Disable Units of Effort for Setup and Cleanup Operations 3.1.1.8.1 and 12.18. Enhanced Budget Constraints 3.14. Release 12.14.14.1. Consistent Resource Assignment within a Portion of a Routing 3. Oracle Inventory Optimization 3. Hard Links Between Work Orders 3.1.13.2. Enhanced Forward ATP 3.1. Access Operation and Routings from Operation Instances 3.14.4. Visualization of Campaign Run Optimization Cycle Boundaries 3.1.10. Release 12.14.2 49 49 49 49 49 50 3. Auto-create Work Orders Directly from Demands 3.1. Visibility to Demand Fulfilled via Starting Inventory 3.1.1.13.14.12.4.14.1.13.4.2 3.7. Enhanced Auto-generated Routings 3. Release 12.1.14. Release 12. Resource “All of” Sets 3.2 3. Release 12. PS XML Model – Unique Extension 3.3 3.1. Production Scheduling as a Web Service Call 3.13.6.8.14. Enhanced Alerts 3.1.1.1.13. Resource Business Objectives 3. Units of Measure on Items 3. Export Selected Model Data During Schedule Publish 3.1.14.14.12.14.1.1.2. Improved Cost Modeling Enhanced Integration with Advanced Planning Command Center 47 48 3.3.14.14. Selective Work Order Release to Production 3.14.1.14. 3. HP and AIX 3.1.1.1.1. Mass Change on Items and Resources 3.7.14.15.1.12.14.14.4.14.1.14. New Alert Type and Drilldowns 3.1.2.13. PS Data Connector Port to Sun.14.1.1.13.2.14.14.20.1.17.12. Release 12.2.14.10.14.11. Release 12.2.1.3.1 3.1.1.2.12.14.3.16. Release 12.1 3.2.1.2 3.1.2.5.1.21.1.6. Enabling ‘Dynamic Open Link’ capabilities and Demantra Anywhere 48 48 48 3. Support for Intermittent Demands 3.3.1.3.10. Oracle Global Order Promising 3.9.14. Enhancements to Optimization 48 48 48 49 3. Dynamic Throughput Rates on Resources 3.3. Oracle Demantra Trade Promotion Optimization 3. Release 12.11.2.1.2.12.1.5.2 50 50 50 50 50 50 50 3.1.14.9.

3 3.15.14.15.14.3.4.1. Supply Tolerancing 3.15.15.2.2.3. User Defined Ideal Sequence 3.1.15.15.1.2. Rapid Planning – Sales and Operations Planning Integration 3. Unconstrained Planning 3.7.15.15.2.3. Multi-Planner Collaboration 3.18. Release 12. Simulation Edits of Approved Supplier Lists and Supplier Capacity 3.1.16. Simulation Edits of Additional Item Attributes 3.15.39. Oracle Rapid Planning 3.15.2.15.14.9. Rapid Planning – Global Order Promising Integration 3.9.2.3. Functional and Data Security 3. Simulation Edits of Processes 3. Release 12.15.3.32. Bills of Material and BOM Effectivity 3.27.33.3.34.7.3.2.38.15. Product Overview 3.14.15. End Item Substitution 3.2.6.31.5.4.15.3. Lead Times and Planning Time Fence 3. Inventory Reservations 3.15.2.2. Disable Multiple Release from the Same Plan for the Same Order 3.2. Respect Demand Priority Rules 3.28.3.15.30.15. All-in-one Supply/Demand View 3.3.3. Shipping.5. Supplier Capacity 3.2.25.2.15. Exceptions 3.15.22.3.1 and 12.2. Default Order Sizing 3.15.15. Safety Stock Enhancements 3.15.15.4.2.2.2.21. Improved Operation Status Logic in OPM integration 3.15.15. Release New Planned Orders and Reschedule Recommendations 3.15. By-products and Co-products 3.8.14.3.14.6.17.2 Release Content Document . Flexible User Interface 3.15. Mass Edits 3.15.15.4.2. Late Demand Diagnosis 3.20.2. Demand Pull-In and Upside Processing 3.15.3.3. Demand and Supply Pegging 3.15.7.2. Favorite Lists 3.26.8.24.15. Global Forecasting 3.15.36.15. Aggregate.2.15. Order Comparison 3.23.10.15.6.2. Clear to Build 3. Constrained Planning 3. Fast Simulation 3. Receiving and Carrier Calendars 3.19.2.3.2. Planner Action: Firm Existing Supplies 3.12.2. Release 12.15.2.2. Configure to Order 3.2.2.2.14.15.15.15. Demand Forecasts 3. Mass Update Enhancements for Firm Date on Demands and Supplies 3. Routing Operation and Resource Scheduling 3.3 3.15. Advanced Work Order Filtering 3.2.2 84 86 88 89 91 91 93 3.2.2.15.3.14. Planner Action: Firm Planned Supplies 3.15.29.15.37.2. Mass Update Enhancements for Resource Availability 3.2.2.15.3.3. Integration with Advanced Planning Command Center 3. Embedded Analytics 3.3. Safety Stock Lead Time 3.35.15. Scheduling Rapid Planning Runs in Batch Mode 93 93 94 94 94 94 95 95 95 96 96 96 96 97 97 97 97 98 98 98 98 99 99 99 100 100 100 100 100 101 102 102 103 103 104 105 105 105 106 106 106 106 107 107 108 109 110 110 111 111 111 112 vi Oracle E-Business Suite Releases 12.13.15. Plan Comparisons 3. Editable Material Horizontal View 3.2.2.11.1.2.3.15.15.15. Order Modifiers 3. Simulation Sets 3.2.2.5. Control Application of Purchase Item Order Multiples Beyond Lead Time 3. Supply Chain Sourcing 3.2.15.15.2.

16.1.1.1.1.16. Collect Installed Base under Contract 3.2.1.1.3.2.3. Planner Work Lists 3. Query-based Auto-release 3. Collect Field Replaceable Unit Bills of Material 3.1.7. Natural Time Fence 3.11.5.16. Support for Part Condition 3.16.16.4.16. Global Forecasting Display in the Material Plan 3. Integration to Spares Management for External Repairs 3. Fair Share 3. Key Performance Indicators 3.17.6.16.16. Oracle Strategic Network Optimization 3.17.2.12.3.1 3. Release 12.2.3. Release 12.3.4.4.17.3.16.2.4.4.15.5.1.2.13.2.4.16.16.5. Auto-release of Planning Recommendations 3. Integration with Advanced Supply Chain Planning 3.2.16.3 3.8.2.1.9.15.2. Release 12.2.3.2 3. Returns Forecasts 3. Re-order Point-based Parts Planning 3. Integration with APCC . Solver Upgrade 122 122 122 123 125 128 129 129 130 130 130 131 Oracle E-Business Suite Releases 12.17.2. Usability Enhancements 3. Material Plan Display Order 3. Supersession Notes 3.2. Release 12.2.6.10.16.1. Planner Worklist Enhancement 3. Import into a Simulation Set 3.15. Support Multiple Move-in / Move-out Lines for a Repair Order 114 114 114 114 114 115 115 115 115 116 116 116 116 116 116 116 117 117 117 117 118 118 118 119 119 119 120 120 121 121 121 122 122 122 3. Multi-process Inline Forecasting 3.14.2. Integration to Depot Repair for Internal Repairs 3.16.1.3. Supersession Chain-Specific Replanning 3. Enhanced Search Capability 3.3.2 3.16.16.16.2.1. Release 12.4.1.Service Parts Planner Dashboard 3.1 3. Alerts 3.2 Release Content Document vii .16.16.17.2. Execution Net Change Planning 3.17.16.3. Minimize New Buys 3.17.12.16.1. Intermittent Demand Flag 3. Blow Through Phantom Items in Clear to Build 3.2.3.2 112 112 112 113 113 113 113 114 114 3.16. Service Parts Planning Workbench 3.4.1.4.16.2.16.10. Display of Decimal Precision 3.15.1.16.15.1 and 12.15.11.17.16.3.1.17. Aggregate Assignment Set and Lane Definition 3.4.16. Supply Chain Risk Management 3. Specify Scenario File in the Plan Options 3.2 3.2.16.15.2 3. Criticality Matrix 3.1.14. Release 12.3.15.4.3.6.17. Release 12. Life Time Buys 3. Release 12.5.3.13.5.3. Integration with Collaborative Planning 3. Last Saved Information for Plan Options 3. Oracle Service Parts Planning 3.4.3.1.2. Support for Supersessions 3. Integrated Demand and Supply Planning 3. Release 12.5.3.17.16.15.16.16.15.2.1.3.17.2.17.5. Product Overview 3.16.16.4. Release 12.2 3.3 3.1.5.3.16.16.

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 releases is not described. It is intended solely to help you assess the business benefits of upgrading to the specified release of the Oracle E-Business Suite. This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Software License and Service Agreement, which has been executed and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. This document is for informational purposes only and is intended solely to assist you in planning for the implementation and upgrade of the product features described. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle. Due to the nature of the product architecture, it may not be possible to safely include all features described in this document without risking significant destabilization of the code.

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

Purpose of Document

1

2.

Introduction
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

Purpose of Document

2

3.

New and Changed Features in Value Chain Planning
3.1. Collections
3.1.1. Release 12.1.1
3.1.1.1. Backward Compatibility to 11i10 Oracle Advanced Planning Release 12.1.1 supports, through a Collections backward compatibility patch, the configuration where the source is E-Business Suite 11i10, and the destination (planning server) is Release 12.1.1. This backward compatibility applies to Advanced Supply Chain Planning, Distribution Planning (see exclusion below), RealTime Sales and Operations Planning, Demand Management, Demand Planning, Inventory Optimization, Global Order Promising, Collaborative Planning, Advanced Planning Command Center, and Service Parts Planning. Specific capabilities not supported in this configuration are: • • • • Advanced Supply Chain Planning − Oracle Transportation Management Integration Distribution Planning − release of cancel requisition recommendations Service Parts Planning − integration to Spares Management Service Parts Planning − integration to Depot Repair

3.2.

Oracle Advanced Planning Command Center
3.2.1. Product Overview
Most supply chain planning processes, considered in their entirety, consist of multiple decision-making sub-processes often performed by different groups that are chained together. For example, a typical sales and operations planning cycle consists of forecasting performed by different lines of business such as sales, marketing, finance and manufacturing and distribution, a consensus demand review, inventory planning and review, supply planning and review, and executive review. These sub-processes may be supported by different underlying supply chain planning applications (Demand Management, Inventory Optimization, Strategic Network Optimization, Service Parts Planning and Advanced Supply Chain Planning.) The overall planning processes are difficult to orchestrate because the planning data required are buried in multiple underlying supply chain planning applications and because the human stakeholders come from multiple organizations. Oracle Advanced Planning Command Center is a new product that pulls together planning outputs from multiple E-Business Suite supply chain planning applications and makes them available for reporting and analysis within a unified user interface based on Oracle Business Intelligence Enterprise Edition (OBIEE). The planning outputs are viewable via seeded role-based dashboards, and are also accessible to custom OBIEE reports and dashboards constructed by the user. Seeded dashboards support the Sales and Operations Planning and Supply Chain Plan Analysis business processes.

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

Collections

3

3. monitor and review the result of complex.2. hub and spoke planning). Release 12. marketing. manufacturing/distribution.2. financial.Oracle Advanced Planning Command Center offers an extensive list of web services that decompose Oracle Advanced Planning capabilities into atomic functional pieces (for example. Sales and Operations Planning Dashboard The Sales and Operations Planning Dashboard included with Advanced Planning Command Center provides all participants in the Sales and Operations Planning process with interactive access to summary and detailed data required when executing the demand review. Oracle Advanced Planning Command Center provides extensive plan and scenario comparison capabilities.1.1 3.1 and 12. and consensus forecasts changed over time? Is our backlog increasing? How are we tracking to forecast? The Supply Review page answers questions such as: Are we supply constrained? Where are our resource constraints? Are we producing to plan? The Executive Review page answers questions such as: Are we on plan financially? For which product categories are we revenue targets? Dashboard level reports provide easy comparison of S&OP scenarios. inter-organizational and inter-disciplinary planning processes that span multiple supply chain planning applications (including external applications). Advanced Supply Chain Planning (ASCP) plans and Strategic Network Optimization (SNO) plans for seamless extended analysis. Oracle E-Business Suite Releases 12.1. run collections. Reports in the Sales and Operations Planning Dashboard drill directly into underlying Demantra Real-Time Sales and Operations Planning worksheets. the ability to automate.2.) These web services are leveraged by seeded Oracle Business Process Execution Language (BPEL) processes that can be used out of the box to automate Sales and Operations Planning and Forecast. The Demand Review page answers questions such as: • • • • • • • • How have my sales.2. Users can also create an infinite variety of custom BPEL processes to automate and orchestrate their specific in-house planning flows (for example. Oracle Advanced Planning Command Center provides: • • a robust reporting and analysis framework for supply chain planning. It also allows you to assign manual activities required for the evaluation and execution of alternative business scenarios and monitor and orchestrate the completion of those activities.2 Release Content Document Oracle Advanced Planning Command Center 4 . Inventory and Supply Planning business flows. orchestrate. run a supply chain plan. generate a statistical forecast. archive a plan. supply review and executive review phases of an S&OP cycle.

2.2 Release Content Document .1 and 12. The SCA Dashboard has the following pages and reports: Plan Health • • • shipment and production trends demand and supply summary resource summary Oracle Advanced Planning Command Center 5 Oracle E-Business Suite Releases 12.2. It enables easy comparisons between plans.Operating Plan and Budget by Category Profitability KPI Cost Breakdown KPI Demand Review Forecast Comparison Forecast Accuracy Projected Backlog Top Forecast Attainment by Category Forecast – Scenario Comparison Top Abs Diff – Consensus Forecast and Budget by Category Consensus Forecast Difference by Customer Consensus Forecast Difference by Customer Supply Review Consolidated Analysis Demand Fill Production to Plan by Organization Production Plan Top Resource Utilization Top Supplier Capacity Utilization Consolidated Analysis – Scenario Comparison Bottom Demand Fill % by Customer Supply Change by Category Production Plan Comparison by Organization 3. Supply Chain Analyst Dashboard The Supply Chain Analyst (SCA) Dashboard included with Advanced Planning Command Center provides easy access to summary and trend data for Advanced Supply Chain Planning and Strategic Network Optimization plans.The following reports are available at the page level in the Sales and Operations Planning Dashboard: Executive Review • • • • • • • • • • • • • • • • • • • • • • • • • • • • • • Executive Summary Consolidated Analysis Profit and Loss Constrained Forecast Comparison Cumulative Budget Tracking Key Performance Indicators Forecast Accuracy Customer Service Inventory and Production KPI Top Difference .2.

2. rationalized against a consistent set of dimensions.) 3. and exceptions across scenarios instead of across plans. etc. It allows you to compare demand and supply summary information.) from Oracle E-Business Suite. and allows you to view Oracle E-Business Suite Releases 12. shipments. inventory value. Inventory Optimization and Strategic Network Optimization). resource utilization. inventory.2. Real-Time Sales and Operations Planning. (A scenario is a grouping of plans whose results should be added together and viewed as a whole. More than 20 dimensions are seeded. APCC contains more than 200 measures (both stored measures that are read into APCC and measures such as costed inventory that are derived). resource information. Analytical Framework APCC provides a central Oracle Business Intelligence Enterprise Edition (OBIEE)-based repository that automatically pulls plan data from a wide cross-section of Advanced Planning applications (Demand Management. as well as execution data (orders.• • • • • • • • • • • • • • • • • • • • • exceptions summary Demand and Supply demand and supply summary demand change by customer supply change by category demand and supply trends demand by customer supply by category Resources resource summary most utilized resources least utilized resources resources with most change in utilization resource utilization trend Exceptions demand exceptions summary inventory exceptions summary alternate exceptions summary reschedule exceptions summary resource exceptions summary exceptions summary by category exceptions summary by organization Historical Performance key supply chain performance metrics (shipments to plan.2 Release Content Document Oracle Advanced Planning Command Center 6 . Advanced Supply Chain Planning.3.1 and 12. The APCC analytical framework repository allows completely user-configurable reporting against Advanced Planning data. production to plan. serves as the foundation for the seeded Sales and Operations Planning and Supply Chain Analyst Dashboards. WIP completions. days of cover) supply chain metrics trend Scenario Analysis • This page is similar to the Plan Health page.

2. 3. Inventory.1 and 12. generating a forecast in Demantra Demand Management (DM).2.2.2. These web services are callable from user-defined Business Process Execution Language (BPEL) flows.6. You can also use scenario sets to group and filter data in APCC dashboards and reports. Scenario Management You can group multiple plans of different types together into a scenario. Supply Chain Planning Web Services Many key Advanced Planning functions have now been made accessible via web services. The Forecast. The specific web services that have been enabled are: • • • • • • • • • • • • Check concurrent program status Launch ASCP and Demantra batch collections Global Order Promising Launch plan management batch processes such as copy/purge plans Launch Strategic Network Optimization batch processes Manage planning process scenarios Launch Service Parts Planning batch processes Launch Inventory Optimization batch processes Launch Distribution Planning batch processes Launch Advanced Supply Chain Planning batch processes Upload external data into APS (forecasts.data from multiple underlying Advanced Planning applications simultaneously in a unified interface. Seeded BPEL Processes Two seeded BPEL processes take leverage the supply chain planning web services offered by APCC to automate and orchestrate key supply chain planning flows.2. marketing forecast review. running an Advanced Supply Chain Planning plan using the DM and IO plan outputs as input. sales forecast review. uploads the consensus forecast from Demantra Real-Time Sales & Operations Planning (RT S&OP) to the planning Oracle E-Business Suite Releases 12. Scenario Sets are groupings of related scenarios (for example. 3.2. safety stock.5. planned supply) Launch Demantra process (launch Demantra workflow.4. and an Advanced Supply Chain Planning plan that together evaluate a sales and operations planning scenario. and then use that scenario to group and filter data in APCC dashboards and reports. an Inventory Optimization plan. assign alternative name to Demantra scenario in planning server) 3. alternate supply/demand scenarios being evaluated within a particular sales and operations planning cycle). Typical scenarios might be: a Demantra Demand Management consensus forecast. and therefore permit limitless automation of supply chain planning business flows. or one "hub" and a number of "spoke" ASCP plans whose outputs need to be fused together to provide visibility to planning results for the entire supply chain. running an Inventory Optimization (IO) plan utilizing the DM output as input. and Supply Planning BPEL process automates a sequence of running collections. and demand forecast review activities and assigns them to key stakeholders.2 Release Content Document Oracle Advanced Planning Command Center 7 . The Sales and Operations Planning BPEL process runs collections. creates financial forecast review.

the configuration where the Planning Server (where all the other APS modules are on) is 11. 3. assign process steps to owners.10 Planning Server Oracle Advanced Planning Command Center Release 12. They can drill from a display of activities in the APCC reporting layer directly into the APCC Activities screen for further detail. 3.2.1.1.2 3.3.2. Assigned activities can be updated with progress status by the assignees and can be flexibly queried within the APCC Activities screen for monitoring purposes. then creates consensus demand review and executive review activities and assigns them to the appropriate stakeholders. Such assignments become system activities with owning individuals.8.) The deployment configuration is as shown below.1. Planners working with APCC dashboards and reports benefit from an iBot that informs them of open activities assigned to them. runs a Strategic Network Optimization (SNO) plan with the RT S&OP consensus forecast as input.server. Oracle E-Business Suite Releases 12.2. APCC thus provides a comprehensive way to stay on top of all the system and manual activities needed to complete complex supply chain planning processes and scenario evaluations. You can also assign arbitrary manual activities to individuals. pulls the SNO constrained forecast/production plan output back into RT S&OP.2.2. Process Automation You can create planning processes and attach to them seeded or custom BPEL processes.2. Planning processes allow you to launch or halt associated BPEL processes. The Planning Process user interface allows you to specify input parameters such as plan names to the underlying BPEL processes.7.3. Activities support file attachments. Compatibility with 11. Activity Management Process automation steps can be assigned to individuals using the Planning Process user interface.1. through a Collections backward compatibility patch. 3. optionally tied to a scenario or scenario set.2 Release Content Document Oracle Advanced Planning Command Center 8 . Release 12.10.5. the source Oracle eBusiness Suite is also on 11. see the key steps of the underlying BPEL process. to enable completely flexible planning automation. and monitor the progress of the BPEL process as it runs. to allow more complete descriptions of required steps or inclusion of supplemental information.5.2 supports.1 and 12.2.10 and only the Advanced Planning Command Center is on 12.5.

5.2. APCC now provides a complete. All dimensions are collected (or loaded using legacy uploads) into the APCC instance. User Option at Plan launch to “push” Multiple EBS (11. Oracle E-Business Suite Releases 12.1.10 even if they are published to APCC.10) or Legacy instances or Legacy instances Collect into both instances APS 12. However. 3. 3.1. standalone 12.2 Release Content Document Oracle Advanced Planning Command Center 9 . Advanced Supply Chain Planning and Inventory Optimization.1 This deployment configuration will be subject to the following specific limitations.2 customers. Ability to Run APCC Standalone For 11.1 APS Operational Data Store 12. 3. collections into APCC is only required for dimension keys.5. Integration to Third Party Planning Systems You can now deploy APCC against third party planning systems.10 Oracle Demantra 7.5. Need to collect into both APCC and APS instances.5.1.5.csv) upload user interface.10 and 12.10) Multiple EBS (11. or via a new Import Plan Summary concurrent program.2 Advanced Supply Chain Planning 11.2 instances. The drill-downs into other applications (Advanced Supply Chain Planning / Inventory Optimization / Demand Management) will not work. The New Planning Web Services and BPEL Processes in APCC instance (in “Processes” tab in Advanced Planning Scenario Manager) cannot use Plans and Forecasts from APS 11. 1.10 APS Operational Data Store 11. The key assumptions/limitations here are: 1. No Contextual Drilldowns from the Dashboards into the planning applications.2 and APCC is deployed in the same instance. This will be made available only for Demand Management. 3.3. 2.5. 4. The APCC OBIEE fact repository can be loaded either via a new flat file (.APS 11. out-of-box integration to a separate.10 Out-of-box Integration. 2.2 APCC instance.5.5. No support for Strategic Network Optimization in APCC. But users can still build scenarios from these plans and forecasts from 11.5. The EBS source instance setups (including instance codes) are identical in the 11.1. So the collection frequency could be less for APCC.3.2.10.1 and 12.10 and R12.3.1/7. This will be available only in the configuration where the planning server is upgraded to 12. 4.1 Advanced Planning Command Center 12.2.

These include a redesigned applications home page with more efficient navigation.4.2. Enhanced Sales and Operations Planning Dashboard The Sales and Operations Planning (S&OP) dashboard is enhanced to include the following new measures: o Shipment history .2.4.Supplier Lead Time Variability Percent Safety Stock . and inline file attachments for process activities.2. Analysis of Inventory and Service Levels The current Supply Chain Analyst (SCA) dashboard in APCC has been enhanced with new measures and related reports to support Inventory Analysis workflows.3.2.3.2. The following new reports are included in a new tab in the SCA dashboard.4.4.2.4. o o o o o Excess and Obsolescence Summary Excess Details Obsolescence Details Excess Details across Plans Obsolescence Details across Plans Some of the new measures introduced as part of this include the following: o o o o o o o o Demand within Obsolescence horizon Demand within Excess Horizon Excess On-order in units and value in multiple currencies Excess On-hand in units and value in multiple currencies Obsolete On-order in units and value in multiple currencies Obsolete On-hand in units and value in multiple currencies Total Excess in units and value in multiple currencies Total Obsolescence in units and value in multiple currencies 3. The following new reports are included in the SCA dashboard.Inventory Value Safety Stock – Postponement Analysis Inventory Measures Trend Inventory Measures Trend by Category-Organization Some of the new measures introduced as part of this include the following: o o o o o Safety Stock (Days) Percent Safety Stock . o o o o o o Inventory Performance Summary Top N – Service Level Short Fall by Category Top N .2.Demand Variability Percent Safety Stock .Transportation Lead Time Variability 3. Analysis of Excess and Obsolescence The current Supply Chain Analyst (SCA) dashboard in APCC has been enhanced with new measures and related reports to support analysis of Excess and Obselete inventory.1.3. multi-level navigation menus with saved favorites.2 Release Content Document . "look-ahead" lists of values that automatically complete partial user entries. 3.Manufacturing Lead Time Variability Percent Safety Stock .1. Release 12.3 3. Rich User Interface Enhancements APCC incorporates new rich user interface capabilities of E-Business Suite 12.1 and 12.1.Lag by 52 week Oracle Advanced Planning Command Center 10 Oracle E-Business Suite Releases 12.

2 Release Content Document Oracle Advanced Planning Command Center 11 .1 and 12.Operating Plan and Budget by Category Financial Trend Analysis Profit & Loss Monthly Margin Difference by Category Year-over-Year Financials Financial Forecast and Budget Comparison Top % Difference . Supply Chain Risk Management Dashboard The Supply Chain Risk Management (SCRM) dashboard is a new dashboard and enables users to review and compare key metrics in a single interface.4.Budget and Annual Plan by Organization Top Revenue Cost by Organization Bottom Margin Profitability KPI Cost Breakdown KPI This new Financial Review page enables planners and executives to answer questions like: o o o o o Are we on plan financially? How are product categories performing financially? What has changed financially since last fiscal quarter/month? How/Where/Why has profitability changed? Is there any need to revise financial forecast? 3. Also.4. providing true Enterprise Planning capabilities to the SCRM discipline.2.o o Operating Plan Financial Forecast In addition. the existing reports have been updated with new usability enhancements and new navigations to more drill-down reports. Oracle E-Business Suite Releases 12. It enables executives and planners to answer questions like: o o o o o o What is the impact to my margins if there is a sudden drop in demand? When do I return to profitability? What is the cost difference between sourcing strategies in the event of the demand drop? What impact does increased lead times have on my inventory strategy? What is the impact of off-shoring to my Total Delivered Cost? What is the impact of off-shoring to my Margins? The following new measures are introduced as part of this feature: o o o o o o o Facility Startup/Shutdown Costs Fixed Costs Count of Sources Carrying Cost without Postponement Safety Stock without Postponement Inventory Budget Product Miles The dashboard contains four different tabs . a new tab called Financial Review has been added with the following reports o o o o o o o o o o o o o o Financial Summary Operating Plan and Financial Forecast Comparison Top % Difference . Supply Chain Sourcing and Glossary.Executive Review. Inventory Analysis.

Collaboration Workspaces for Unstructured Collaboration This feature lets users to quickly band into ad-hoc. Discussions. Group Calendars. Documents.2.2. These collaborative group spaces support customized Worklists. and to APCC dashboards.6. 3. In addition.7.5. the group space home page has navigation links to applications such as Rapid Planning and Sales and Operations Planning. Revenue Gap Analysis This feature enables Supply Chain Analysts and Sales and Operations Planners to do additional reporting and analysis to close gaps between the current shipment rate and the revenue targets established as part of the sales and operations plan. Enhanced Exceptions Analysis The Supply Chain Analyst Dashboard has been enhanced to include additional measures and reports in support of improved exception analysis. Each group space is linked to a Scenario created in Advanced Planning Command Center and users can choose to auto-create a group space when a scenario is created. The Supply Chain Analyst (SCA) dashboard has been enhanced to add the following reports in the Scenario analysis tab: o o o o o o o o o o Backlog Analysis – Units & Value Bookings Performance – Units & Value Current Shipment Plan Demand and Supply Summary Demand Utilization – Units & Value Demand Utilization Split – Baseline Plan Left to Book .4. the following reports have been enhanced with additional page/report filters: o o o o Demand Exceptions Summary Inventory Exceptions Summary Alternate Exceptions Summary Resource Exceptions Summary Oracle Advanced Planning Command Center 12 Oracle E-Business Suite Releases 12.2 Release Content Document . This is most critical as the end of a period or quarter approaches and gaps remain.By Quarter Sales Order Analysis – Units & Value Shipment Performance – Units & Value Supply Utilization – Units & Value The Sales and Operations Planning (S&OP) dashboard has also been enhanced to add / modify the following reports: o o Current Shipment Plan Supply Summary 3. virtual groups for specific planning tasks and allows those groups to share structured and unstructured content.1 and 12.4.2. flexible portal-like user interface that brings together components of various planning applications and the a variety of collaboration tools. Each group has access to a single. Two new reports have been added as part of this feature: o o Item Exceptions Summary Resource Exceptions Summary In addition to the above.4.3. Issues and Notes. Tags.

Shipment Receipts. 3. Plan Versus Collected Data Comparison Oracle Advanced Planning Command Center now offers a view of key supply and demand measures based on the latest transaction data collected into the Operational Data Store.5. These archived versions can then be viewed in all related reports and dashboards.5. 3.4.2. There are no new seeded reports that use this new dimension.9.8.o o o Reschedules Exceptions Summary Exception Summary by Category Exception Summary by Organization 3.1 and 12.4.1. Rapid Planning plans can be archived and published to Advanced Planning Command Center.3.1. This feature is available for ASCP plans only.2. Note: This dimension is enabled only when the profile option "MSC: Enable Model and End Item Dimensions in APCC" is set to Yes. All Rapid Planning simulation plans can be used in the Process Automation functionality to build process flows in Advanced Planning Command Center. users can analyze all upstream component supplies (such as On Hand. New Dimension – End Item This is a new one-level dimension that enables users to build reports for analysis by the Finished Good items as derived from the pegging generated in an ASCP plan. These measures are available in the Supply Chain Analyst Dashboard under the plan name of "Collections". Integration with Rapid Planning Oracle Advanced Planning Command Center now offers pre-built integration with Rapid Planning. Oracle E-Business Suite Releases 12.2 3. An example of this type of analysis may include a comparison of expected receipts of material in the next few weeks based on the Plan versus what is currently in the execution system (as brought over to Value Chain Planning via Collections). and Planned Orders) and see the breakdown by End Items (Finished Goods) that are driving the component demand. Users can compare them with Plans to get insights into the variances between what is in a Plan (including changes introduced due to plan recommendations and user changes) and the latest real-time transactional data. Release 12.2 Release Content Document Oracle Advanced Planning Command Center 13 .2. The Advanced Planning Command Center’s Supply Chain Analyst dashboard supports drill-down directly into the Rapid Planning application.2. Purchase Orders. and is enabled for the following two measures only: • • Order Quantity Total Supply Using the Order Quantity measure and the Order Type filter. This dimension is available in the seeded Advanced Planning Catalog.

New Dimension – Parent Model This is a new one-level dimension that enables users to build reports for analysis of Options in ATO models by the Parent Model based on forecast explosion in an ASCP Plan.6. This enhances the analysis that users can do in APCC. These serve the same purpose as the current workflow “Export OBI-EE Data” and the concurrent program “Assign Plan Name. and financial forecast measures across scenarios.2 3. Custom Series from Demantra DM and RT S&OP You can configure the integration data profiles in Demantra to publish custom series created in either DM or RT S&OP to APCC. compare or finally purge these plans like any other supply plan. The selected series must not have any complex calculations or client expressions in Demantra. even their components will have the break-up by the Parent Model so that end users can analyze all upstream components and understand the source of their demand by viewing the break-up by the Parent Model. 3. You can provide a plan name as a parameter in the new Demantra workflow processes called “Publish S&OP-APCC Measures” (for RT S&OP) and “Publish DM-APCC Measures” (for DM).2. Shipment Receipts.” 3. You can alter the mix or add more measures by running a new concurrent program. Users can analyze. projected backlog. This feature is available in ASCP plans only.1.2.5. The name of the category set is based on the profile option "MSC: APCC Key Component Category Set. There are no new seeded reports that use this new dimension.3.6. Purchase Orders. this feature collects any 15 measures (10 forecasting measures and 5 historical measures) that you choose. striped by “Demand Plan”.2 Release Content Document Oracle Advanced Planning Command Center 14 . By default. Release 12.2.6. This dimension is available in the seeded Advanced Planning Catalog. Plan-specific Forecasting Measures This feature enables all forecasting measures (not just Consensus Forecast) from Demantra Demand Management and Demantra Real-time Sales and Operations Planning to be analyzed in Advanced Planning Command Center. Note: This dimension is enabled only for those options and key components that are assigned to a special category set.2.2. and Planned Orders) and see the breakdown by Parent ATO Models that are driving this option demand. In the case where the Options are manufactured assemblies. “Collect Demantra customization information to APCC”. users can analyze all option supplies (such as On Hand.1 and 12.2. and is enabled for the following two measures only: • • Order Quantity Total Supply Using the Order Quantity measure and the Order Type filter." Note: This dimension is enabled only when the profile option "MSC: Enable Model & End Item dimensions in APCC" is set to Yes. Oracle E-Business Suite Releases 12. as it is now possible to easily compare sales forecast.

You can also use the spreadsheet file upload capabilities to load DRP plan data into APCC. value and days of supply) Fill Rate The following measures are specific to DRP plans and will also be published to APCC: Maximum Inventory Level (Units) Maximum Inventory Level (Days of Supply) Target Inventory Level (Units) Target Inventory Level (Days of Supply) The seeded reports and dashboards in APCC are not designed for DRP plans or scenarios with DRP plans. 3. Integration with Distribution Planning In Release 12.6.2. This will enable DRP users to leverage APCC to analyze DRP plans through custom reports and dashboards. You should build custom reports or dashboards for analyzing DRP plans. Oracle E-Business Suite Releases 12. None of the seeded reports or dashboards use this custom hierarchy. You must set the profile “MSC: Additional Demantra Item Hierarchy in APCC” to the name of the hierarchy in Demantra and then run the standard “Refresh APCC Materialized Views” concurrent program to make that custom hierarchy available in APCC. The concurrent program “Archive Plan Summary” will now support DRP plan types.6.3. For example.3. DRP plans can be published to Advanced Planning Command Center. Support for Custom Demantra Product Hierarchy You can now bring an additional product hierarchy from Demantra into APCC. You can now create a new four-level hierarchy such as “Item < Product SubGroup < Product Group < Product Line” in Demantra and easily bring it into APCC for use in analysis.2. This is limited to one custom product hierarchy and supports a maximum of 10 levels.2 Release Content Document Oracle Advanced Planning Command Center 15 .2.1 and 12.4. the product category hierarchy available in APCC as default is a two-level hierarchy. There is no automatic publish of DRP plans to APCC at the time of DRP plan launch. Only the following DRP plan measures will be published to APCC: • • • • • • • • • • • • • • • • • • • • Order Quantity (all DRP order types) Exception Count (all DRP exception types) Exception Quantity/Value (reporting/functional currencies) Inventory Turns Scheduled Receipts On Hand Carrying Cost (reporting/functional currencies) Purchasing Cost (reporting/functional currencies) Total Supply Chain Cost (reporting/functional currencies) Revenues (reporting/functional currencies) Gross Margin (reporting/functional currencies) Gross Margin % Total Supply Total Demand Projected Available Balance (units.

3.2 Release Content Document Oracle Advanced Supply Chain Planning 16 .3.2. ASCP now does a more accurate job of offloading: it offloads primary sources and processes more fully before offloading to alternates. Contiguous Processing In the process industries. 3.3. projected material arrival dates Provide a Business Process Execution Language (BPEL) process and associated web services to consume events and generate planning exceptions to provide planners real time visibility to transportation delays Use the updated dates in ASCP interactive planning calculations to calculate the impact of transportation delays on downstream orders and take corrective action • 3.3.1 3. and substitute items. For customers for whom day-level planning results are sufficiently detailed.1. More Accurate Offloading to Alternates It is often desired to offload to alternate sources or processes only once a primary source or process runs out of capacity.3.1. Optimization Enhancements Oracle ASCP enables planners to efficiently manage many products and supply chain locations by intelligently selecting alternate sources.2. because intermediate products may be unstable or because intermediate products are transported from process to process without any provision for storage in between. 3. Oracle Transportation Management Integration Most planning systems have no visibility to delays in transportation and their impact to manufacturing utilization or customer service.1.3. With this release.1. bills of material. This allows you to cap the maximum time duration between upstream Oracle E-Business Suite Releases 12.1 and 12. many products need to be processed contiguously from raw materials to finished goods.1. ASCP's automated decision-making capabilities have been enhanced in the following ways.2. Day-Level Planning A new "day-level" planning mode allows ASCP to automate the selection of alternates while generating planning results at the day level of granularity. manufacturing processes.1. Release 12.1. Oracle Advanced Supply Chain Planning 3.3. ASCP respects Oracle Process Manufacturing standard and max delays between routings. This planning mode skips the final detailed scheduling solution phase that is now undertaken with any constrained or optimized plan run. this is a way to run plans in a shorter amount of time than was previously possible (due to the fact that the final detailed scheduling phase is skipped). With this release.2.3.1.3.3. With this release ASCP will: • • Leverage Oracle Transportation Management (OTM) Supply Chain Event Management to obtain real-time.1. and planning results show fewer instances of primary source/process overloading before offloading to alternates.

With this release. Prior to this release.2 Release Content Document Oracle Advanced Supply Chain Planning 17 . the number of items at each location may be in the tens of thousands or more. they must have a certain minimum duration of remaining shelf life.3. In conjunction with the above change.3.4. the load consolidation phase of Distribution Planning has been decoupled from the demand push-down and supply allocation phase mentioned above and is now also done concurrently in a multi-process fashion.6. 3. item-customer site and sales order levels. The above behavior is optional.and downstream make supplies and enforce contiguous processing. Sales orderlevel MRSLs can only be entered via customization that populates a new column in the MSC_SALES_ORDERS table on the planning server. This is a trade-off that the user optionally makes for the sake of better performance. ASCP now supports minimum remaining shelf life (MRSL) constraints specified at the itemorganization. Distribution Planning Scalability Enhancements Distribution enterprises often need to manage large numbers of locations and items: the number of locations may be in the thousands. First. the ASCP sales order release process has been enhanced to support the passing back of ASCP substitute item recommendations back to the associated sales orders in Order Management. The partitioning of the distribution planning problem into pieces that can be solved in parallel is done automatically. You can also enforce a minimum (standard) delay between make supplies in order to accurately reflect processing constraints such as cool-down periods.3.1.1. such end-item substitution recommendations made by ASCP could not be automatically released back and implemented in Order Management. 3. so that there will be enough time for the end consumer to buy and use the products. Such a configuration can either be a single planning server with multiple processors.5. this may reduce how well Distribution Planning is able to consolidate loads relative to its base behavior in Release 12. the phase of planning that calculates the independent and dependent demands at each distribution location and allocates scarce supply to those demands has been made multi-process. One way in which ASCP helps in this regards is to recommend the use of available substitute item supplies when the demanded item is not on hand. Distribution Planning incorporates the following scalability enhancements.1. in order to take advantage of the parallelization capabilities of multi-processor hardware configurations. End Item Substitution Enhancements Use-up of on hand inventory is critical to controlling storage and obsolescence costs at many companies.1 and 12. 3. or multiple servers logically linked together via Real Application Clusters. Functionally. With this release. Minimum Remaining Shelf Life Products such as groceries and pharmaceuticals have limited shelf lives. Oracle E-Business Suite Releases 12. Item-organization and itemcustomer site-level MRSLs are specified via item attribute simulation sets. because the consolidation calculations in downstream supply chain layers now no longer factor in the consolidation outputs from upstream layers. and is enabled via profile options. Customers of such products typically impose rules that dictate that when such products arrive at the customer site. Planning in such an environment requires a focus on scalability.

3. This capability is not supported for R12.1.3. 3. ASCP can optionally search for them in ascending order of substitution relationship date effectivity. planning should not recommend that the extra 35 pounds be split off to be used to satisfy other demands.950 pounds or 10. it is now possible to configure ASCP to not infer that Item C is a substitute for Item A.1. ASCP now offers the option of hedging against uncertain demand by generating supplies to meet demands ahead of time.3.000 pounds should be considered to be satisfied completely by a 9.10. This feature is turned on via the MSO: Use Safety Lead Time profile option.1 and 11i10 source instances.950 pound coil. One typical application of this capability is to display demands and supplies in alternate units of measure. This allows ASCP plans to remain consistent with short-term scheduling decisions made in PS. 3. The same mechanism can be used to customize data values in standard rows of the horizontal plan. process variability often creates supply output quantities that vary about a nominal amount. Planned orders scheduled in PS come into ASCP as firm planned orders.035 pound coil. by user or by preference. Supply Tolerancing Enhancements In the process industries. For example.035 pounds. Production Schedules as Inputs You can now publish planned orders directly from Production Scheduling into an ASCP plan. The planning requirements are to be able to tolerate minor discrepancies between demand and supply so as to prevent unnecessary production and impractical supply splits. The custom row can be selectively displayed. 3.x source instances. This provides a mechanism for dictating the item order of ASCP's search for end-item substitutes. It is supported for R12.3.000 pound" coil of aluminum sheet may actually come out to be 9. a demand for 10. A new custom row in the horizontal plan allows a user to display a custom order type (for example.0. Safety Lead Time In lieu of generating supplies to meet target safety stock quantities. The amount of time that demands are met ahead of time is the "safety lead time". If Item B is a substitute for Item A.1.7. and Item C is a substitute for Item B. The logic to calculate custom order type data values must be provided by the user via a custom PL/SQL program unit that is pointed to by the profile option MSC: Horizontal Plan Extension Program. When searching for end-item substitute supplies.ASCP also supports an option to recognize explicitly modeled item substitution relationships only and thus turn off the inference of chained substitutions. Projected Available Balance Dollar Value) and label it appropriately.1.1 and 12.8. For example. When the same demand is satisfied with a 10. a "10. and is specified via the Safety Stock Percent item attribute (100% per one day of safety lead time). 3. Customization of Horizontal Plan ASCP supports the ability to customize the row labels and numbers displayed in the horizontal plan.9.2 Release Content Document Oracle Advanced Supply Chain Planning 18 . Oracle E-Business Suite Releases 12.1.

and cancellation recommendations for internal requisitions.000 pound coil to cover the supply deficit.2. New with this release is the ability for the user to optionally specify Shortage and Excess Tolerance Percentages (via customization) at the item-organization level in the staging table MSC_ST_SYSTEM_ITEMS.1. Release Recommendations for Internal Requisitions You can now release reschedule in. Also new is ASCP's ability to delay the satisfaction of 'small' demands until sufficient outstanding demand has accumulated to warrant the production of a standard-sized batch. You can also release manual overrides of internal requisition date and quantity. ASCP will look at these staging table values in lieu of the profile option values. Starting in 11i10.3.2. reschedule out.ASCP supports the concept of supply tolerancing through Shortage Tolerance and Excess Tolerance Percent pegging controls that dictate when demands and supplies are considered to be fully pegged. Oracle Purchasing did not support changes to an internal requisition after the corresponding internal sales order had been created in Oracle Order Management. This restriction has now been removed. Supply tolerancing support where Shortage and Excess Tolerance Percentages are input as global profile option values is existing capability.3. 'Small' is defined to be a percentage of the Fixed Lot Multiple order modifier. but will peg that supply to excess so that it is moved to the end of the planning horizon. a new profile option MSC: Buy Order Processing Lead Time Calendar allows you to either revert back to the 11i9 behavior (when it is set to 'Org Manufacturing Calendar') or use the 11i10 behavior (when it is set to 'Supplier Capacity Calendar'). ASCP will still generate a recommendation for an extra 10.3.1.2 3.3.2. 3.2.1 and 12.1.950 pound coil above. Use cases for this capability are: Oracle E-Business Suite Releases 12.11. if it was assigned on the Approved Supplier List. 3. Otherwise the processing lead time was offset based on a 24x7 calendar. Buy Order Processing Lead Time Backward Compatibility In 11i9 the processing lead time for buy planned orders was offset based on the org manufacturing calendar. the processing lead time for buy planned orders was offset based on the Supplier Capacity Calendar. If these values are populated. 3. Previously. Turn Off Planned Order Creation You can turn off planned order creation for an item via the new Item Mass Maintenance item attribute "New Planned Order Creation". This percentage can be entered (via customization) in the planner server table MSC_SYSTEM_ITEMS. The permissible values are: “Create New Planned Orders” (default) and “Do Not Create New Planned Orders”. This prevents the planner from accidentally releasing unneeded work to the production floor.2 Release Content Document Oracle Advanced Supply Chain Planning 19 . In order to preserve behavior compatibility with 11i9 for customers who may have set their buy item processing lead times assuming org manufacturing calendar offsetting and are upgrading from 11i9 to R12.1.1. In the example with the 9. Release 12. ASCP's recommendations for internal orders can now be successfully released from the planner workbench.

This feature is useful for minimizing the impact of purchase order change recommendations on suppliers. To enable phasing out of item components and their replacement with newer ingredients. it is required that there be no new order or build for the phased out item. It is also available in Distribution Planning. but available stock can be distributed and sold. The existing supply of the phased out item is to be used up.3. 3.3.• A by-product defined in the BOM can be used as downstream component. if within a week there is a demand of 1 on Friday. For example.1.3. Release 12.2.3. The list of values for this profile option includes: Organization Manufacturing Calendar – This is the default value. and purchase order supplies of 1 each on Monday and Thursday. but no new supplies should be manufactured to meet Sales Order demand. Constrained (Classic) With Decision Rules and Optimized (Classic) planning modes. The requirement is to ensure that while all available supplies of the by-product are consumed.3 3. Oracle E-Business Suite Releases 12. In this release a new profile option “MSC: Forecast Spreading Calendar” enables users to spread forecasts based on the shipping calendar in addition to the manufacturing calendar. Consume Purchase Orders in First In.3. Use of existing purchase order supplies in this chronological fashion applies across substitute components: if the Monday and Thursday purchase orders in our example are in fact different items but substitute components. Forecast Spreading Based on Shipping Calendar Before this release ASCP supported forecast spreading based on only manufacturing calendar.1 and 12.3. No new supplies for certain products are to be made. The system will use the organization manufacturing calendar for spreading the forecast.1. In addition. ASCP would match the Monday purchase order to the Friday demand and recommend the cancellation of the Thursday purchase order. 3. It is not available in the Unconstrained. Organization Shipping Calendar – The system will use the organization shipping calendar for spreading the forecast. Constrained (Classic). no supplies for this item are purchased. First Out Sequence Standard ASCP behavior matches supplies to demands in a way that minimizes inventory. ASCP would still consume the Monday purchase order and cancel the Thursday purchase order. With this (optional) feature.2 Release Content Document Oracle Advanced Supply Chain Planning 20 . Sales Orders can be taken for the by-product and shipped as supplies are available. • • This features is only available in the Constrained (Without Scheduling) and Constrained (With Scheduling) planning modes. ASCP would match the Thursday purchase order to the Friday demand and recommend the cancellation of the Monday purchase order.

This is the default value.3. Based on the shipping calendar. No – The shortage tolerance and excess percentages are applied only to existing supplies (such as On Hand. Example: Consider an organization with a manufacturing calendar that has both Saturday and Sunday as non-working days. With this release ASCP provides a profile option called “MSC: Apply shortage and excess tolerance percentages to planned orders”. Excluding Planned Orders from Supply Tolerancing Before this release the Shortage Tolerance Percent and Excess Tolerance Percent were applied to all order types including planned orders. WIP). The list of values for this profile option includes: Yes – The shortage tolerance and excess percentages are applied to all supplies including planned orders. while matching existing supplies (which may have irregular quantities due to actual process yields) to demands using a supply tolerance. The result is shown in the following table: Monday Tuesday Wednesda y 5 20 11 20 17 20 24 20 25 20 18 20 26 20 20 19 20 27 20 12 20 20 20 28 40 20 13 20 21 40 29 0 Thursda y 6 20 14 40 22 0 30 Friday Saturday Sunday Date Forecast Date Forecast Date Forecast Date Forecast 3 20 10 4 7 40 8 0 15 0 9 16 23 3. therefore ASCP moves and adds up the Saturdays’ forecasts to Fridays’ forecasts (20 + 20 = 40). On the other hand the shipping calendar has only Sunday as the only non-working day of the week. When this profile option is set to No. Example – Consider an item with 2 demands: Demand1= 10200 Demand2= 10200 Fixed Order Quantity = 2000 Oracle E-Business Suite Releases 12.1 and 12. it allows ASCP to generate planned orders that satisfy 100% of demand.Note – A forecast for a non-working day in the manufacturing calendar is moved to the previous working day. a forecast of 480 units for period 3 (March) is spread evenly to daily buckets from Monday to Saturday (total of 24 buckets).3.1. That results in the daily forecast quantity of 20 (480 / 24 = 20). Since Saturday is not a working day based on the manufacturing calendar.2 Release Content Document Oracle Advanced Supply Chain Planning 21 .

2 – MSO: Postpone Use of Alternates to Latest Possible Time This profile option enables ASCP to plan supplies with respect to the timing of alternates’ usage. On the other hand. In addition to the above profile option.0018 Excess Tolerance Quantity = 10200 × 0. You need to set the value of this profile option to 0 (consider both existing substitute component supplies and existing alternate BOM component supplies) or 1 (consider existing substitute component supplies but not existing alternate BOM component supplies) to use this enhancement.3. Oracle E-Business Suite Releases 12.0018 = 1836 If the profile option “MSC: Apply shortage and excess tolerance percentages to planned orders” is set to “No”. and there is no existing supply for substitute components. ASCP generates new planned orders for the primary components before substitute components. This is the default value. You need to set the value of this profile option to “No” to use this feature.2 Release Content Document Oracle Advanced Supply Chain Planning 22 . Maximize Use-Up of Substitute Components With this release ASCP provides a new profile option called “MSO: Use up existing supply of primary components before substitute” that allows you to maximize usage of substitute components. 3. If this profile option is set to “No”. ASCP creates 6 planned orders of 2000 to satisfy Demand1 of 10200. No – ASCP uses the existing supply of substitute components before primary components. Comp This profile option allows you to control how the existing supplies in substitute components / alternate BOM paths are used by ASCP. The other planned order of 2000 is used for satisfying Demand2. In this case Demand1 is satisfied with an allowed shortage of 200. you need to set the following 2 profile options to use this feature: 1 – MSO: Use Existing Supplies in Alternate BOM/Subs. but it uses (pegs) only 5 of those to satisfy this demand since (10200 – 10000) < 204. if the profile option is set to “Yes”.MSC: Demand Satisfied Percent Threshold for Pegging = 98 Shortage Tolerance Quantity = 10200 × (100 – 98) / 100 = 204 MSC: Minimum Supply/Demand Percent for Pegging = 0. In this case Demand1 is satisfied completely and the excess of 1800 (12000 – 10200) is used to satisfy Demand2 ignoring the excess tolerance percent even though 1800 < 1836. then ASCP initially creates 6 planned orders to satisfy Demand1. Values 2 (consider neither existing substitute component supplies nor existing alternate BOM component supplies) and 3 (consider existing alternate BOM component supplies but not existing substitute component supplies) are not compatible with this feature. The list of values for this profile option includes: Yes – ASCP uses the existing supply of primary components before substitute components.3.2.1 and 12.

Generate new planned orders for substitute components With the feature turned on (MSO: Use up existing supply of primary components before substitute = No): 1. Use on hand and scheduled receipts of primary components 2. Forecast Explosion Enhancements The enhancements to the forecast explosion process in ASCP include: • While exploding forecasts of ATO Models. This information is used for reporting and analysis in Advanced Planning Command Center. This is in addition to the currently supported fixed lot multiplier and round order modifiers. Note: When using Demantra Demand Management to feed forecasts into Advanced Supply Chain Planning. or Fixed Lot Multiplier.3. Generate new planned orders for primary components 4. 3. Use on hand and scheduled receipts of substitute components 2. Users can specify maximum and minimum order quantity as an item attribute.2 Release Content Document Oracle Advanced Supply Chain Planning 23 .4. Distribution Planning Enhanced Order Modifier Support Distribution planning now supports two more order modifiers: maximum order quantity and minimum order quantity.1.3.ASCP behavior with respect to this feature is summarized as follows: With the feature turned off (MSO: Use up existing supply of primary components before substitute = Yes): 1.1 and 12. Generate new planned orders for primary components 4. ASCP traces the exploded forecasts of option classes and options to the top model forecast that is the source of the original demand.3. the seeded data integration profile publishes both the Model forecasts and the exploded forecasts by default. Release 12. Use on hand and scheduled receipts of substitute components 3.3. Order modifiers specified on a supply allocation rule are applied to transfers between organizations. This enhancement is only available with the Constrained (Without Scheduling) planning mode. The on hand of a substitute component may be partially used if it is greater than the order modifiers but it is not a multiple of them.1. Fixed Order Quantity.3.2 3. Use on hand and scheduled receipts of primary components 3. Users can also choose to specify each newly supported order modifier on the supply allocation rule. When using this Oracle E-Business Suite Releases 12. Generate new planned orders for substitute components Note that the on hand of a substitute component will not be used if it is less than the Minimum Order Quantity. 3.4.3.

1 and 12. If the planning percentages from Demantra are not available. the explosion will use the usages on the Bills of Material as the default. only determine which date is selected from the purchase order to use within planning as the suggested dock date. This provides more flexibility for users to decide how supplier capacity should be consumed by purchase orders inside and outside the planning time fence. The new profile option “MSC: Supplier Capacity Consumption by Purchase Orders” has four settings. • The forecast explosion process will now be able to use the Planning percentages from Demantra Demand Management (if published). The two choices. the existing profile option “MSC: Purchase Order Dock Date Calculation Preference” does not affect supplier capacity consumption. Note: The Planning Percentages need to be published from Demantra using a custom data integration profile. If you select “Unacknowledged Purchase Orders Only” then this behavior is similar to current behavior where purchase orders without a promise date consume supplier capacity. The profile also allows users to decide whether to consume supplier capacity with all purchase orders or only unacknowledged purchase orders. Both these enhancements are available only when the plan option 'Explode Forecast' is turned on and the forecast control for the Options and Option Classes is set to Consume and Derive.2 Release Content Document Oracle Advanced Supply Chain Planning 24 .5.2 3. users will need to set up a custom profile to not publish the exploded forecast demand so that there is no double counting of dependent demand.1. The seeded profile does not publish this by default.option to explode forecasts in ASCP. Supplier Capacity Consumption Enhancement A new profile option is introduced to control supplier capacity consumption by purchase orders.3. singleorganization models and multi-level. ASCP does not consume supplier capacity with any purchase order which has a dock date inside of the item or supplier-item lead time. The supplier capacity horizontal plan is enhanced to display the supplier capacity consumption based on the new profile option. If the purchase order dock date is outside of lead time. then the purchase order consumes supplier capacity. The newest choice is “Purchase Orders outside Lead Time Only”. These features are valid for local and global forecasts and also in both simple. With this choice.3. multi-organization models. Release 12. Users can set supplier capacity to accumulate at lead time and only purchase orders outside of lead time consume supplier capacity. Oracle E-Business Suite Releases 12. Promise Date and Need by Date. 3. With this enhancement. You can select “Yes” and all purchase orders consume supplier capacity or “No Consumption” (default) and then no purchase orders consume supplier capacity.5.

1. corresponding to the individual pegging quantities and dates. When the plan is run. Oracle E-Business Suite Releases 12.2.4.4.3. 3. two supply commit records will be published.csv file that can be opened in spreadsheet and other external applications.1.2 Release Content Document Oracle Collaborative Planning 25 . You can save the Exception Group and attach it to plans using a new plan option field. Oracle Collaborative Planning 3. Search Exceptions by Buyer and Planner The search criteria in the exceptions detail screen have been enhanced to include "Buyer Code" and "Planner Code". Enhanced Exception Management Prior to this enhancement.1. A new window called Exception Group allows you to select specific exceptions from a list of available exceptions.3.1. if a demand is satisfied by pegging against on hand and also a planned production batch. ASCP generates only the exceptions listed in the Exception Group. 3.1.1 and 12.4.3. Data can be exported for one user selected exception class at a time. or for all exception classes together.5.4. The structure of the exported data is similar to what is seen on the Exception Details screen. The Exception Group allows you to further limit the number of exceptions generated by restricting the generated exceptions to only selected • • • Organizations Item Categories and to those with dates within a specified Exception Time Fence (Days) 3.1. ASCP published only a single supply commit record to Collaborative Planning on the date when the demand was completely satisfied. With the new behavior. thus saving the computational burden of generating unneeded exceptions.4. Detailed Supply Commit Based on ASCP Pegging ASCP will publish supply commits to Collaborative Planning based on how end item supplies are pegged to the end item demands in the ASCP plan. This new behavior is enabled by the profile option MSC: Publish Supply Commit Based on Pegging Information. You can now control which exceptions ASCP generates. Release 12. Earlier. Export Exception Details This enhancement enables the export of the Collaborative Planning Exceptions Detail screen to a .2.1 3. ASCP generated all exceptions for all items and resources with attached exception sets.

Users can then access only plans defined for the Organizations associated with their Responsibility. The data is replaced with a null/NA.1.1. Clear Data in Worksheets This feature allows the user to clear data from existing cells in a worksheet.1. Release 12. 3.5.1.2.1 and 12.4.1.1 3. Release 12.2.2.2 3. one of which signifies that the fallback default allocation for the time dimension will be even.3 There are no new enhancements in Oracle Collaborative Planning in Release 12.2 Release Content Document Oracle Demand Planning 26 .3.5.5. Release 12. The Fill Data dialog in the worksheet now allows a null entry.4. Default Even Allocation Over Time This feature gives the user the ability to allocate evenly down the time dimension and use "first" allocation for other dimensions when an allocation basis is not available. Plan Security by Responsibility and Organization This feature prevents users from one Business Unit from accessing demand plans set up for another Business Unit. Oracle Demand Planning 3. The Demand Planning System Administrator can now associate Demand Plan Responsibilities with specific Organizations. By default a Responsibility is associated with all Organizations.1. Oracle E-Business Suite Releases 12.3. 3.1.2. The profile MSD: Use Classic Even Allocation can now have three values.4. use even allocation No.3. Release 12. Organization(s) are selected during plan definition. 3. use first allocation No.2.1.1. 3.4. The three valid choices for the profile are: • • • Yes.4. use first allocation for all dimensions except Time 3.3.1.5.1. Rich User Interface Enhancements Oracle Collaborative Planning incorporates new rich user interface capabilities of EBusiness Suite 12.5. These include a redesigned applications home page with more efficient navigation. and "look-ahead" lists of values that automatically complete partial user entries. A recalculate is required to reflect the change across all levels of the hierarchy. multi-level navigation menus with saved favorites.2 There are no new enhancements in Oracle Collaborative Planning in Release 12.

Sort by Product in Planning Percentages Worksheet This feature adds a sort capability for Product to the Selector for the Planning Percentage Worksheet.1. The DSR transforms retailer data into manufacturer terms – including manufacturer item identification. returns. Prevent Planners from Editing Measures in View Scope This feature allows you to prevent planners from changing worksheet values in measures in their view scope. manufacturer hierarchies and calendars.6.5.2. Planners can continue to change worksheet values in measures in their assignment scope.1. 3. The Demand Signal Repository data model is based upon the Oracle Data Warehouse for Retail (ODWR) data model. 3. A high-performance data loading facility cleanses the data and allocates it to a uniform set of dimension levels.2 There are no new enhancements in Oracle Demand Planning in Release 12.1.5. adapted to a manufacturer point of view. 3. store orders and receipts. The user now has the ability to sort the Product dimension in ascending or descending order to facilitate selection of models and options. and allows users to develop custom reports that combine the data in customer-specific ways.3. Product Overview The Oracle Demand Signal Repository (DSR) helps manufacturers collect detailed retailer and other demand data. Release 12.4. Oracle E-Business Suite Releases 12.5.3.1. and respond via a SOA-enabled services library. Oracle Demand Signal Repository 3.1 and 12.1.2 Release Content Document Oracle Demand Signal Repository 27 .1. 3.5. on-hand inventory.4.2.1.6. Whether this feature is enabled or not. Release 12.6.5. 3. only values in a demand planner's assignment scope are passed back to the shared workspace during internal collaboration. Release 12. An extensive OBIEE metadata layer sits on top of the ODWR data model.5. analyze it to identify issues and opportunities.2 There are no new enhancements in Oracle Demand Planning in Release 12. Data Selection Tools for Region Copy Selector This feature makes all the Selector tools available to the user when creating a Region Copy measure to facilitate data selection.2. store promotions and sales/order forecasts.1.3 There are no new enhancements in Oracle Demand Planning in Release 12. Typical retail data sources include daily point-of-sale. 3.3.5.

The lowest level in the customer item hierarchy is the SKU. The other levels of the organization hierarchy (listed from top to bottom) include: Retail Group. This enables the Business Unit to be analyzed by a geographic dimension.2. The customer organization hierarchy supports the slowly changing dimension (SCD) type 2 feature.g. The consumer goods manufacturer can use all calendar types.2. fiscal..2. or aggregated to a higher level as needed. DSR allows you to aggregate fact data to any level of the customer’s organization hierarchy. general contact. and VAT information.2. restrooms. number of window displays. Customer Item Hierarchy DSR captures customer item information as well as customer item hierarchy to allow consumer goods manufacturers to view customer data based on the manner in which the customer organizes their product groupings. This feature keeps historical data (e. the two most common types of business units are stores and customer distribution centers. DSR also provides additional calendars types including business. SKUs can be associated to a brand or group into item clusters to allow further analysis. Release 12.1.6. Multiple Calendar Support In addition to the standard Gregorian calendar. By having a separate business calendar for each customer. While business unit types are user-defined. Additionally. and planning calendar type. the account team or category manager can view data in terms of the customer’s week. month. etc.). Each business unit has a physical address. size. Area. as well as store-specific attributes such as store manager. etc. The lowest level in the organization hierarchy is the Business Unit which is a single customer location. 3. cost. variety. Region.2.6. on-hand inventory and other data at daily store level. Additionally.1. sales) associated with the hierarchical structure in effect at the time. business units can be associated with a distribution channel and/or a market area to allow analysis by channel or a market area (such as the Los Angeles market). DSR captures several business unit attributes such as address.3. as well as the organization hierarchy.1 3. style. etc. Oracle E-Business Suite Releases 12. District. whereas the only calendar type that supports customer-specific calendars is the business calendar. color.6.2 Release Content Document Oracle Demand Signal Repository 28 . DSR captures several attributes at the SKU level including price. 3. Customer Organization Hierarchy DSR captures customer organizational information as well as customer organizational hierarchy to allow CG Manufacturer’s to view customer data based on the customer’s perspective of their organization. physical properties (store size. Chain.1 and 12.6. and finally Business Unit.DSR web services provide complementary applications such as Demantra Demand Management with cleansed retail point of sale. advertising. to ensure proper analysis. 3.

Subcategory. Item and finally SKU.2. Alternate Units of Measure In DSR the typical base unit of measure is a saleable unit or “Each” (EA). The customer item hierarchy supports the slowly changing dimension (SCD) type 2 feature. whereas the customer’s item hierarchy is eight levels deep (to accommodate the broad range of products carried by retailers). This feature keeps historical data (e. Like the customer item hierarchy.6. 3.6. DSR allows you to aggregate fact data to any level of the customer’s item hierarchy. The lowest level in the manufacturer item hierarchy is the SKU. Manufacturer Item Hierarchy DSR captures the manufacturer’s item information as well as item hierarchy to allow consumer goods manufacturers to view data by the product categorization and descriptions used within their own company. DSR supports alternate units of measure (kilos. Each SKU has a ratio to convert the primary UOM quantity to the alternate UOM quantity. Group. If needed. 3.2.6.g.4. Division. controls whether stores must be authorized to carry an item. The first is the retailer’s corporate currency. The manufacturer’s item hierarchy is seven levels deep. the manufacturer’s item hierarchy also supports the slowly changing dimension (SCD) type 2 feature. 3. sales) associated with the hierarchical structure in effect at the time. 3. to ensure proper analysis.5. Multiple Currency Support Monetary values within DSR can be represented in one of two currencies. Class.g. reports will use the manufacturer reporting currency. sales) associated with the hierarchical structure in effect at the time. shipping or marketing requirements. a beverage company might select volume in liters as their alternative UOM. This feature keeps historical data (e. Oracle E-Business Suite Releases 12. DSR captures several attributes at the SKU level which can differ from the retailer’s SKU attribute values.The other levels of the customer item hierarchy (listed from top to bottom) include: Company. The other levels of the manufacturer’s item hierarchy (listed from top to bottom) include: Company.. Division.6. Subclass.2 Release Content Document Oracle Demand Signal Repository 29 .. The second is the reporting currency of the manufacturer. Category.1 and 12. By default. Item and finally SKU. Department. the reports can be customized to replace the reporting currency with the retailer currency. stats) to address manufacturing. For example. Authorized Distribution A system parameter.7. whereas each retailer can have a different currency.2. DSR converts values from the retailer’s currency to the manufacturer’s reporting currency based upon a conversion table.2. called discovery mode. Group. to ensure proper analysis.6. liters.

Data supplied at an aggregate level is allocated down to the day during the load process. Shipments The shipments process flow loads shipped units and monetary amount for a given business unit/item/day. weekly. and quality hold quantities.When discovery mode is off. so no allocation logic is supported for order data. 3. Sales reported at an aggregate level are allocated to the lowest level (by business unit / day). business unit level (either store or DC).6. Inventory The item inventory process flow loads on-hand. units returned and their related monetary value and cost.6.2. Sales Facts The DSR sales & return process flow loads units sold.g. data can be reported at the business unit level (e. in-transit. Organization and time-level allocation profiles define the percentage of the aggregate value to be allocated to each the day or location.11. backordered. Sales Forecasts The sales forecast process flow loads forecasted sales units and their related monetary value. 3. Orders (like Shipments) are reported against a specific store or distribution center.6. in order for a data value to be the same when re-aggregated to the level at which it was originally received.10.. store) or at a higher level in the organization for a given day or week. items must be pre-associated with a valid business unit (aka store) in order to successfully process sales and forecast data for that business unit/item combination.2 Release Content Document Oracle Demand Signal Repository 30 .2. Oracle E-Business Suite Releases 12. chain-level data must be allocated to a daily. For example. again no allocation logic is supported for order data. Item Inventory (like Shipments and Orders) are reported against a specific store or distribution center. the data loading process will create a new authorized item/store record the first time that it encounters a SKU at a business unit (store) where it has never previously been reported.2.6. 3.9.8.6.g.2.2. 3. 3. Sales Allocation Fact data in Demand Signal Repository is always stored at the lowest level by SKU/Business Unit/Day.. Like the sales and returns process flow.6.13. Data can be reported at the business unit level (e. 3. net costs. When item discovery mode is on. Allocation preserves any fractional quantity. Sales forecasted at an aggregate level are allocated to the lowest level (by business unit / day).1 and 12. received.2. and retail amounts for a given business unit/item/location/day.12. Shipments are reported against a specific store or distribution center. no allocation logic is supported for shipment data. store) or at a higher level in the organization for a given day or week. Orders The orders process flow loads order quantity and monetary amount for a given business unit/item/day.

Two separate reports are available: The “Product to Category Coverage by Quarter” and the “Product to Category Coverage by Period”. etc. across time and to the brand and item levels. 3.2. Product Mix provides a breakdown of sales by product category across retailers.6. Product to Category Coverage Reports The Product to Category Coverage reports shows the percentage of category. Channel (grocery retail.6. Two reports are available: The “Category Growth Analysis by Volume” report and the “Category Growth Analysis by Sales” report The available filters include: • Time (year.6.2. in a single dashboard Tracking performance relative to pre-defined thresholds Drill-down capabilities to view supporting data Ability to view by retailer or manufacturer hierarchy Automatic delivery of the underlying reports via MS Office tools. Sales Growth Percent Change to Previous Period displays the growth (or decline) of this period’s sales to the prior period. mass merchandiser.14.1 and 12. Oracle Demand Signal Repository 31 Oracle E-Business Suite Releases 12.2. Category Growth Analysis Reports The Category Growth Analysis reports measure category’s growth by sales volume and monetary value. drug. Product Contribution to Profit lists the top performing products based on contribution to their respective product category. or measures. Some of the key characteristics of the dashboard include: • • • • • Displaying multiple KPIs. Promotion Plans The promotions plan process flow loads information on what promotions are in effect at a store for an item during a given time period. 3. as well as whether the promotion includes an associated price discount or not.). month).6. brand or item penetration (by unit sales and monetary sales) into specific channels of distribution (e. grocery retail. etc.2.16.17. quarter. This includes: • • • • • • Retailer Net Cost to Gross Margin is a quick reference into the profitability of each product category carried by the retailer.3. Category Sales Analysis Dashboard The Category Management Dashboard displays key measures that are important to a Category Manager. mass merchandiser. Category Sales by Type displays the breakdown by promotional versus nonpromotional sales.) Product Category or Item Item Type (manufacturer item or retailer items) 3.15.g. Category Coverage provides a breakdown of sales by retailer by product category. quarter month). The available filters include: • • • • Time (year. wholesale /club.2 Release Content Document .

mass merchandiser. month). Promotion Sales are sales from the retail POS system that are priced and/or based on a promotion. Four reports are available: • • • • • • • • • Top Performers by Profit Bottom Performers by Profit Top Performers by Sales Bottom Performers by Sales The available filters include: Top Performer (which is the number to display. Channel (grocery retail.18.6.19.6. Top and Bottom Performers Reports The top and bottom performers reports provide an immediate view of the top performers and bottom performers by profit or sales amount. Regular Sales are sales from the retail POS system that are priced at standard Non-Promotion periods or pricing. The available filters include: • • • Time (year.2.1 and 12. etc. Average Price Analysis Report The Average Price Analysis report compares unit sales and average retail sales price to the same period last year.) Product Category Item Type (manufacturer item or retailer items) 3. Ad-Hoc Reporting Demand Signal Repository leverages native OBIEE functionality to produce ad-hoc reports. Category Sales by Type Reports The Category Sales by Type report shows category sales units and monetary sales by promotion type.6. etc. quarter.) Product Category Item Type (manufacturer item or retailer items) Market Area 3.2. mass merchandiser.2.6.20. Two reports are available: The “Category Sales Volume by Type: and the “Category Sales Value by Type” report. The available filters include: • • • • Time (year. Product Category Item Type (manufacturer item or retailer items) 3.2 Release Content Document Oracle Demand Signal Repository 32 .• • • • Channel (grocery retail. quarter. Product Category Item Type (manufacturer item or retailer items) Customer 3. This includes: Oracle E-Business Suite Releases 12. quarter. month).21. the default if left blank is 10) Time (year. month).2.

Invoice accuracy %. In-Stock %.24. Supply Chain Scorecard The Supply Chain scorecard shows results against goal comparisons for seven supplychain oriented measures. and Forecast Accuracy.23. Like the Sales Scorecard. The four sections are: • • • • “Latest Results” for the selected company (aka customer). based on existing dimensions.1 and 12. Order Cycle Time. not at a more granular level (such as category or region). on a map. 3. On-hand Inventory.2 Release Content Document Oracle Demand Signal Repository 33 . the top two sections show company performance. Gross Marting Percent. Shipments.2. graph. Unit Sales.6. chart. it is divided into four panels. Demantra Demand Management Integration Demand Signal Repository has a pre-built outbound integration of aggregated demand signals to Demantra.• • • • • Flexible creation of ad hoc/new reports by end users which can then be published to a wider audience Ability to view data in multiple formats. and Percent returns 3. Shipments Oracle E-Business Suite Releases 12. including pivot table. Deduction amount. Operations Scorecard The operations tab is divided into two panels. 3. etc. Item data synchronization % and Item data accuracy %) are external measures imported into DSR through the ETL process. to show sales by store. Also like the Sales Scorecard. All seven measures (Perfect order %.2.22. Ability to drill down to lowest level of detail. Data sent from DSR to Demantra includes: • • • Retailer Point of Sale Sales and Forecast Retailer On-Hand Inventory.25. “Overall Company” YTD results broken down by product Category The measures displayed in each of the four quadrants include Monetary Sales. PowerPoint. Orders. Sales Scorecard The sales scorecard is divided into four sections which the users can filter by customer and/or date. Order change %. with the left panels showing the latest results and the right panels showing values summarized by year.2. 3. etc.6. Operational measures are only available at supply chain level. Category Share. the bottom two sections show performance across all manufacturer products at the customer organization’s “region” level. and On-Time Delivery. For example. Forecast. “Latest Results” broken down by product category “Overall Company” YTD results. And the ability to integrate geographic visualization. Retailer Gross Margin. Category Sales. Payment days. etc. Inventory Cover. like retail or manufacture item or organization hierarchy Seamless integration with MS Office tools to export to Excel.2. The measures for each of the four sections of the supply chain scorecard include Service Level. zip code. and Promotions Distribution Center On Hand-Inventory.6. however.6.

3. to locate issues and create exceptions.2. as well as on-hand inventory. Shipments. as needed.2. Promotional Price Deviation Exception which reports where promotion price is discounted more than 10% of average selling price Oracle E-Business Suite Releases 12.3. and Receipts 3.6. Sales Forecast Accuracy Exception where sales forecast accuracy varies significantly from the average. In-flight Promotional Lift Exception which reports on promoted items whose sales is less than 110% of average sales.1.3. Retail Merchandising System (RMS) Integration The Retail Merchandising System (RMS) Integration provides an out-of the box integration of EDI 852 data coming from Oracle’s RMS system into Oracle’s Demand Signal Repository (DSR) module. the Exception Management Dashboard aggregates and displays exceptions by customer and product category. Release 12. The exception types analyzed within the Exception Management Dashboard include: • • • • • • • • Out of Stock Exception where on-hand quantity was reported as zero Imputed Out of Stock Exception where sales are significantly below expected sales and the probability is very high that the product is out of stock. Orders. New Item Not Selling Exception which reports on items introduced at the store within the last 30 days which have no sales. pre-built queries can be run periodically. listing them in order from highest to lowest number of exception so users can address the most critical areas first.1.6.26. and Promotions On-Hand and In-Transit Inventory. Backorders.2 3.1 and 12. Reorder Point Exception where inventory levels (on-hand plus back order quantity) are below the customer’s reorder point.27. Exception Management Dashboard The Exception Management Dashboard automatically sifts through vast amounts of customer data to quickly detect potential problems in key business processes. Web Services Integration If you desire outbound integration with other Oracle or Non-Oracle applications. Forecasts. 3.2 Release Content Document Oracle Demand Signal Repository 34 . The EDI 852 file from RMS populates DSR’s sales and return data.6. Once exceptions have been created. Using OBIEE’s iBot functionality. Overstock Exception where on-hand inventory levels are above the customer’s reorder point. Demand Signal Repository includes a standards-based web services integration to support most common access scenarios including: • • Store POS.6.

deviation between the two for the selected week as well as prior week. as well as geographic region or sub-region. the existing set of business unit (store) attributes were enhanced to include additional data elements. TDLinx Store/Outlet Adapter Demand Signal Repository has created an adapter to load AC Nielsen TDLinx store/outlet data. baseline sales.2. promotional price. if needed. When loading the external measures the product and geography keys supplied by the syndicated data provider are translated into the appropriate organization. DSR provides an initial set of 100 generic measures which are renamed during implementation to match the measures purchased. The Inventory Position report shows the previous week’s ending balance. geography. The set of syndicated consumption data includes pre-calculated ACV measures as well as other measures such as sales by promotion type. • • Exception history is retained to allow users to track trends on whether exceptions are increasing or decreasing.3. Syndicated consumption data can be purchased at various levels of the product hierarchy and customer organization hierarchy. 3.) is also displayed. as well as other attributes. From there the existing Organization Hierarchy ETL process flow can be used to update the Organization Business Unit (DDR_R_BSNS_UNIT) target table. sub-channel code. The TDLinx store/outlet adapter maps data from the AC Nielson source CSV file to the Organization Business Unit Interface table. As a result. • • The Forecast Accuracy report shows actual versus forecasted sales. quantity sold. reorder point. the number of measures can be extended. A sample set of measures along with an out-of-the-box report is available to use as is. in addition to the average sales per store selling. max. In addition. product or geography hierarchy levels. etc.1 and 12. actual revenue and expected revenue. 3.3. The customer’s replenishment information (min. receipts. Oracle E-Business Suite Releases 12.6. or rename and revise based on specific customer needs. retail group. All Commodity Volume (ACV) / External Measures Many companies using Demand Signal Repository purchase consumption data from syndicated data providers to analyze market penetration by retailer.3. and coupon sales.From each one of these exception types users have the option to view one of the following reports to get more information. such as status. The Item Distribution report shows the number of authorized stores and the number of authorized stores not selling. The Price Deviation report shows average sales price.6. product and time.2 Release Content Document Oracle Demand Signal Repository 35 . sales and both an expected ending balance and an actual ending balance.

operations and supply chain scorecards have been enhanced to improve usability (see illustration below). In addition..3. These enhancements include: • • • • • Driving performance indicators (red. the scorecard compared a yearly goal against the associated measure (e. Previously.3. Monitoring weekly performance results as opposed to daily performance Color-coded performance indicators which are based on the loaded goals and thresholds. yellow green indicators) based on externally-loaded goals and thresholds.2 Release Content Document Oracle Demand Signal Repository 36 . Scorecard Enhancements (Goals & Thresholds) The sales.1 and 12. the associated chart is displayed first (before any table data) On the operations scorecard. “Latest Results” are now based on weekly results. goals and thresholds. which was too granular.6.4. the following enhancements were made to improve readability: • • Both the measure value and the color-coded performance indicator are displayed on the main scorecard pages When drilling down from the scorecard. the Deduction Balance measure has replaced the Deduction Amount measure. “Overall Results” are now based on YTD results. Previously. the latest results displayed daily values.g. the year filter criteria is passed to the underlying report. unit sales) for a given year. This allows users to monitor performance throughout the year (rather than waiting until the end of the year). In addition. Oracle E-Business Suite Releases 12.

. Lifestyle.g. Store Clusters DSR supports the ability to group “like” stores (or distribution centers) together to execute strategies related to specific store formats. Average income.3. Coastal) to see breakdown of sales by each unique cluster. weather zones. 3. Item Clusters Similar to store clusters. or other characteristics. DSR supports the ability to group “like” SKUs together to evaluate sales strategies and promotional activities. primary shopper and brand perception. Each business unit (store or distribution center) may be associated to one or more store clusters.3. A store cluster report is available to analyze sales by store cluster type (e.3.6. Oracle E-Business Suite Releases 12. consumer demographics. The example below illustrates how stores from different retailers can be assigned to store clusters based on average income.6.1 and 12. The example below illustrates how SKUs from different product categories can be assigned to item clusters based on average container material.6.2 Release Content Document Oracle Demand Signal Repository 37 .5. lifestyle and geographic location.

2 Release Content Document Oracle Demand Signal Repository 38 .6. or to anticipate future order volumes.3.3. The replenishment rules are used by the exception management workbench to display over and under stock conditions.7. This information can be used to determine whether out-of-stocks or overstocks are being caused by an inappropriate inventory management policy. The replenishment rules are also accessible to the end user when building ad-hoc queries. Replenishment Rules DSR supports the loading of customer replenishment rules to provide visibility into the criteria used by the store or distribution center when reordering products. Oracle E-Business Suite Releases 12.1 and 12.

Release 12.1 and 12.4. The functionality within this feature includes: • • • The ability to load manufacturer promotion information using out of the box generic interface tables and Oracle Warehouse Builder process flows The ability to associate sales to a manufacturer promotion to report promoted vs.1.3.g.1.6.8. actual ACV % by manufacturer promotion Oracle E-Business Suite Releases 12. so end users can view the percentages that were used when allocating sales facts to the business unit or day level. non-compliant sales (e.3 3.6.2 Release Content Document Oracle Demand Signal Repository 39 .4. actual promotion sales Expected vs. Allocation Rules DSR has the ability to allocate POS and sales forecast facts received at an aggregate level to the business unit / day level.3. sales that should have been promoted) A new Manufacturer Promotion Dashboard which shows: o o o o Weekly sales compliance trend broken down by promoted and noncompliant sales Manufacturer promotion compliance by product category which displays promoted and non-promoted sales by product category Expected vs.. Manufacturer Promotions Oracle Demand Signal Repository has been extended to include the capture and analysis of Manufacturer Promotions.6. The time allocation and organization allocation percentages have been exposed in the BI Answers catalog. 3.

feature. Oracle Demand Signal Repository has been enhanced to capture manufacturer shipments to provide end to end visibility of products as they leave the manufacturer’s site all the way to the store and ultimate sale to the consumer. actual sales by promotion type (e.. Customer Shipment Facts As part of the manufacturer shipments enhancements. The functionality within this feature includes: • Creation of a new Organization Type for distributors Oracle Demand Signal Repository 40 Oracle E-Business Suite Releases 12. Third Party Distributors Manufacturers may ship product to customers via third party distributors. In addition.2. In previous releases.g. etc. display. retailers).3. but did not have visibility into shipments leaving the manufacturer’s facilities.6..4. In previous releases of Oracle Demand Signal Repository distributors were not distinguishable from other organizations (e. a new organization type has been created specifically for distributors.4. receipts (by product category and business unit) to spot potential product diversion issues Customer shipment throughput of inbound shipments vs. a new distributor dashboard has been created.g.4. Oracle Demand Signal Repository provided visibility of products at customer locations (either distribution centers or retail stores). Manufacturer Promotion Detail Results which compare actual promotion results against expectations at the promotion/customer/SKU level. outbound shipments 3. 3.o o • Expected vs.1 and 12. forecasted customer shipments Customer shipments vs. Manufacturer Shipments Manufacturers need visibility into products as they move downstream in the supply chain to the consumer.) to analyze results by promotion tactic Promotion compliance by promotion type Context sensitive drilldowns are available from the manufacturer promotion dashboard to display: o o Manufacturer Promotion Summary Results which compare actual promotion results against expectations at the promotion/customer level. The functionality within this feature includes: • • • The ability to load the manufacturer’s organization hierarchy to define locations from where product is shipped The ability to load manufacturer shipment information using out of the box generic interface tables and Oracle Warehouse Builder process flows A new Shipment Dashboard which shows: o o o o o Manufacturer shipment trend Customer sales trend (to compare against manufacturer shipments) Actual vs. 3.4.2 Release Content Document . To provide better visibility into third party distributors. customer shipment facts were also enhanced to capture ship-to location and shipment cost information.6.6.

Oracle Demand Signal Repository has had the ability to capture and analyze facts based on the customer’s view of their organization structure. Manufacturers who subscribe to a syndicated data provider service for account information can load this information into the alternate organization hierarchy and leave the original customer organization hierarchy untouched. The Alternate Organization Hierarchy feature allows alternate views of the customer’s organization to co-exist within DSR along with the original customer organization hierarchy. This includes loading: o o o Distributor shipments Distributor inventory Distributor shipment forecast (see Forecast Type and Purpose Code enhancement) • Creation of a new Distributor dashboard which shows: o o o o o o o o Manufacturer shipments by distributor Distributor shipments by customer Weekly manufacturer shipment trend Forecast accuracy by distributor Distributor inventory by product category Customer shipments by distributor Distributor throughput (inbound and outbound shipments) by product Category Weekly distributor throughput trend 3. collecting and aggregating consumption data. or the type of analysis performed. Facts can be inquired upon using the original customer organization hierarchy. For example: Example 1 – Syndicated Data Provider.g. or one or more alternate organization hierarchies. This view is oftentimes different from how the customer views its organization structure. which can vary depending on the source of the data.1 and 12.5.6.4. Alternate Organization Hierarchy Since its inaugural release.. Manufacturers and their supply chain partners (e.2 Release Content Document Oracle Demand Signal Repository 41 . This includes loading: o o o o Distributor organization hierarchy Distributor item hierarchy Distributor business calendar Distributor replenishment rules • The ability to load distributor fact information using out of the box generic interface tables and Oracle Warehouse Builder process flows. etc. Oracle E-Business Suite Releases 12. promotion planning. syndicated data providers) may have their own view of how the customer’s organization is structured for purposes of account management.• The ability to load distributor reference information using out of the box generic interface tables and Oracle Warehouse Builder process flows. The Alternate Organization Hierarchy provides a flexible organization structure.

To use additional alternate organization hierarchies.). the promotion may apply to a level within the retailer’s organization. A sample report.g. Ability to analyze fact data at a level that is equivalent to other systems in use by the Manufacturer.so that account team’s can still talk to customers in terms of the customer’s view of their organization. The manufacturer’s own view of the customer’s organization may be based on how the customer’s buying organization is structured. The functionality within this feature includes: • • The ability to define the types of alternate organization hierarchies to be used (e.. east. • o • • The ability to associate syndicated consumption data to any account within an alternate organization hierarchy.g. For example.g. called Sales Performance by Account. jewelry.) The ability to configure the DSR repository to expose additional hierarchies and/or levels and name each level according to desired use (see additional information below) The ability to load alternate organization hierarchy information using out of the box generic interface tables and Oracle Warehouse Builder process flows. The association between a business unit (e. a level in an alternate organization hierarchy). west.. Example 2 – Customer Buying Organization / Planning Hierarchy. store or distribution center) and an account in the alternate organization hierarchy. Up to ten levels within an alternate Oracle E-Business Suite Releases 12. a retail department (e... such as promotion planning and execution.e. Additional Information DSR ships with a sample alternate organization hierarchy exposed in the Answers web catalog which has four levels exposed. For example.2 Release Content Document Oracle Demand Signal Repository 42 . including a set of 20 user-defined attributes which can be customized. One or more of these views of the customer organization can be loaded to the alternate organization hierarchy. and the parent account to which each child account belongs.g. Information loaded includes: o o The types of alternate organization hierarchies in use The attributes associated with each account within an alternate organization hierarchy. Buying Organization. which represents the area for which a buyer is responsible. etc. etc. AC Nielsen. has been made available to illustrate how the alternate organization can be used to build other reports. When performing activities.) or buying region (e. which would be equivalent to the planning account used in Demantra Predictive Trade Planning or Siebel Consumer Goods.1 and 12. the DSR repository must be modified to define the number of levels being used and the names of each level to be exposed.. to analyze and report on DSR retail demand data by planning account (i. The business benefits to having alternate organization hierarchies include: • • Ability to view customer data at aggregate levels that represent the various ways in which the manufacturer conducts business with the customer. giftware. etc.

organization hierarchy can be exposed without requiring any physical data model changes.4.7. The functionality within this feature includes: • The ability to capture different types of forecasts coming from the retailer/customer. In one case. forecasts were assumed to be sales related. Oracle Demand Signal Repository has enhanced the forecast facts to provide additional types of forecast. 3. there was no way to distinguish baseline from incremental forecast. The forecast type code indicates whether the forecast quantity includes only base demand (without promotional volumes).2 Release Content Document Oracle Demand Signal Repository 43 . a set of 20 userdefined attributes (10 alphanumeric. incremental forecast. or "total" demand (including both base and promo).4. 3. To differentiate the types of forecasts provided by the retailer. User Defined Fields To provide flexibility in capturing additional attributes within Oracle Demand Signal Repository. while in other cases. The forecast purpose code indicates whether a forecast represents a projected sales quantity (for stores). the forecasts may represent projected orders or shipments for the distribution centers.6. In addition. Forecast Type and Purpose Code Prior to this release of Oracle Demand Signal Repository. This is to maintain parity with the original intent of the reports. • o • Existing out of the box reports and dashboards were modified to specify that the forecast data being displayed had a Forecast Purpose code of SALES and a Forecast Type of TOTAL. o Forecast Purpose. promotional demand only. the forecast data contains two additional attributes. Forecast Type.6. Oracle E-Business Suite Releases 12. as well as defining baseline vs.1 and 12. As of this release. order quantity (for distribution locations). the forecast may represent projected store sales. without requiring changes to the physical data model. 10 numeric) have been added to the entities listed below: • • • • • • Manufacturer Item Hierarchy (all levels) Organization Hierarchy (all levels) Retailer Item Hierarchy (all levels) Item Cluster Definition Retailer Cluster Definition Customer Promotion Plans Manufacturer’s needing to capture additional attributes against these entities can leverage the out of the box interface tables and Oracle Warehouse Builder process flows without needing to make any customizations.6. shipment quantity (for distribution locations) or a projected receipt quantity (for either stores or DCs).

2.7.4.2 There are no new features in Oracle Demand Signal Repository in Release 12.6. Calendar Month Support in Weekly System Each Oracle Demantra implementation has a core time resolution definition.1. With this release.1. which in turns drives the Oracle E-Business Suite Releases 12. the Type 2 SCD feature is always turned on for these three dimensions.8. Oracle Demand Signal Repository supports Type 2 Slowly Changing Dimensions (SCD) on the following dimensions: • • • Organization Manufacturer Item Hierarchy Customer (Retail) Item Hierarchy Historically.1. This definition drives the resolution of data kept in the system.1 and 12.3.7. Release 12.2 Release Content Document Oracle Demantra – All Products 44 . Type 2 SCD functionality can be turned off at implementation time to give customers the option whether to use this feature or not.7. Release 12.5. 3.6. 3. Type 2 Slowly Changing Dimensions By default.2 3. Oracle Demantra – All Products 3.

we extend our operating system support of the analytical engine to include Solaris 10. A template for import can be generated via an enhanced version of the Export to Excel feature.xls file) into a compatible worksheet. 3.granularity of data available to users. as weeks do not aggregate wholly into calendar months. the Sales_Data_Engine will not be created for every engine branch but instead the data will be retrieved from the Sales_Data table directory. as well as key Demantra processes.3. Quarters and Years 3. With this configuration.month calendar rollups.6. Engine Performance Improvements This release sets engine pass through as the default configuration for the analytical engine.4.7. In order to keep them active.1.1. Quarters and Years Update data in Calendar Months. Demantra 12. Dying_time. some SKUs are promotional and are only sold every few years. improve implementation delivery times and maintain or improve engine run times.7. This release will enhance the Demantra data model to enable supporting week-to. Currently this data granularity serves as the smallest building block upon which all time management and display is done. Analytical Engine on Solaris 10 In this release. Import from Excel This release enables customers to import data directly from a file (tab-delimited Unicode format only. dying time could be set to a very high number while in other SKUs a shorter time could be used to trigger deactivation.2 includes support for multiple languages within a single instance. Oracle E-Business Suite Releases 12.5. If a customer’s business requirements include support of both weeks and calendar months they cannot achieve this using a weekly system.1. This will enable users to select from a list of supported languages at login. This will enable users to quickly import data such as customer forecast. can be named as . Improved Multi-Language Support As a further improvement on language support. and review and collaborate in their selected language. or data they have manipulated in Excel for mass updates (such as planning percentages). As an example of the business justification.7.2 Release Content Document Oracle Demantra – All Products 45 . This will reduce configuration time needed to apply this configuration at key customers.7.7.1. 3. 3. General Engine Enhancements This release enables control of combination life-cycle parameters to be configured locally or globally.2.1. mature_age and hist_glob_prop will support a global configuration with local overrides. Currently the only way to support this requirement is to have a system where the lowest time resolution is daily. Functionality supported: • • • Pre-configured Calendar Months time aggregation View Weekly data via Calendar Months.1 and 12. 3.

Database Performance Improvements Database performance can decline due to out-of-order tables or incorrectly defined primary keys.1 and 12.8. This new option.0 3.x and 7. Integration Data Profile Hints Integration Interface hints are defined in the Business Modeler for Data Profiles.7.2 Release Content Document Oracle Demantra – All Products 46 .7. Further.7. Demand Variability Definition The user interface for standard error (currently erroneously labeled ‘Safety Stock’) is relocated from the Business Logic Engine (BLE) to the Business Modeler and renamed to ‘Demand Variability’.1.0 Applications Client Runtime Java: 6.7. Oracle E-Business Suite Releases 12. System administrators will be able to define both data and population hints within the Data Profile wizard. This will better consolidate all system administrator tasks into one administrative application.2 aligns with the EBS Technology Stack.3.10. 3. performance of the procedures that calculate standard error is improved by implementing multi-threading. including the following extensions and version upgrades above existing supported technologies: • • • • • • • • • • • Oracle Weblogic 11g CPLEX 12 for Trade Promotion Optimization Oracle Connection Manager 11g (OCM) Oracle Access Manager 11g (replaces SSO) Internet Explorer 9 Firefox 4 Safari 5 Applications Middle Tier JDK: Java 6.0 In addition.1. Configure Rolling Profile Groups A new user interface is provided to define Rolling Profile Groups in the Business Modeler. the configuration of Rolling Data Profiles was found under the ‘Engine’ menu.7. Technology Stack Demantra 12.11.1. Previously.1. In this release we provide standard mechanisms for performing database ‘health checks’(both a quick and thorough version) and procedures to rebuild key data tables like SALES_DATA and MDP_MATRIX if necessary. is moved under the ‘Configuration’ menu in the Business Modeler. The key focus of this design is to provide a means of assessing and addressing declines in database performance due to out-of-order tables.9.7.0 Tomcat 6. as well as the definition of Rolling Data Profiles. 3. 3. we will support the following version upgrades: IBM WebSphere or WebSphere Express 7.1. This procedure will be dynamically created in Demantra and can be run either while the application server is live or during a period when the application server is down.

3. and manufacturing costs. if customer forecasts are maintained in a Demand Management series then this forecast data can be published to a seeded. There is support for publishing custom demand series to APCC forecasting measures. Asynchronous mode of operation means the workflow will not be required to wait for the current step to complete in order to proceed to the next step in the workflow. However. Seeded integration with Strategic Network Optimization brings planning costs at the item. Enhanced Integration with Advanced Planning Command Center Demand Management seeds integration with Oracle Advanced Planning Command Center.1 and 12. Release 12.2 3.g.9.1. This mode of operation works well for most types of workflow steps currently supported in the workflow editor. For example. there are certain types of workflow steps for which an asynchronous mode of operation would be useful.2 3. 3. Oracle Demantra Demand Management 3. if a custom item hierarchy has been defined in the Business Modeler (e.8. These measures are archived by plan for immediate scenario comparison to facilitate faster development of profitable demand shaping strategies. Asynchronous support is provided for the following types of workflow steps: • • • • Launch Workflow Step User Step Group Step Exception Step Many of these steps are simply used to notify users of data to review or exceptions to take note of..1. Once the notification has been sent.1. Supply cost breakdown is by transportation. organization and time level by plan scenario rather than deriving total cost using standard costs in S&OP.3.8.9. This Oracle E-Business Suite Releases 12.9.e. Demand plan measures can be published to the Advanced Planning Command Center (APCC) and used in dashboard reports. Improved Cost Modeling Detailed supply cost modeling is available in S&OP. they wait for the step to complete before proceeding to the next step in the workflow).1. Asynchronous Workflow Support Currently.1. generic APCC measure. Item < Product SubGroup < Product Group < Product Line) then this structure can be replicated automatically in APCC.1. the workflow should proceed to completion rather than wait for the user to mark as ‘Done’.7. storage.8.2 Release Content Document Oracle Demantra Demand Management 47 .12. Oracle Demantra Real-time Sales and Operations Planning 3.1. For example. Release 12. Integration is also available for a limited item hierarchy mapping between Demand Management and APCC. workflow steps in Demantra workflows operate in a synchronous mode (i. purchase.

and financial forecast measures between scenarios to evaluate plan differences.11.1. customers who have licensed Predictive Trade Planning are able to use DOL to export promotion data from Demantra into third party reporting tools such as Microsoft Excel.enables our customers to understand the cost trade-offs between plan scenarios for a more profitable response.2 3.2 3. This enhancement improves decision support through more detailed cost analysis.11.1. Dynamic Open Link (DOL) and Demantra Anywhere (DA) were available only if the Sales and Operations Planning component was installed. a SNO plan scenario may indicate higher transportation and supply costs due to outsourcing whereas an alternative plan scenario that increases resource capacity may reflect higher manufacturing and storage costs. projected backlog. 3.10. and can be archived and are therefore comparable between scenarios.2.10. Oracle Demantra Predictive Trade Planning 3. In this release. Release 12. Item < Product SubGroup < Product Group < Product Line) then this structure can be replicated automatically in APCC.10. They will also be able to leverage the thin client of DA for promotions planning. 3.g. Publish custom measures: Support for publishing custom S&OP series to APCC. there was no ability to compare sales forecast. For example. This diminished the utility of the APCC for demand data analysis.1.9. 3. S&OP leverages the same integration enhancements as in DM. These enhancements to S&OP-APCC integration include: • • • Streamlined publish process for Forecasting measures: All Forecasting measures are published in a single workflow thereby eliminating manual steps. This includes both forecast and historical measures. Oracle Demantra Trade Promotion Optimization 3. For example. we enable this advanced analytical Oracle E-Business Suite Releases 12. Release 12.1. In this release. nodal tuning was only available to Advanced Forecasting and Demand Modeling (AFDM) customers.1.1 and 12. For example.2 Release Content Document Oracle Demantra Predictive Trade Planning 48 . Enhanced Integration with Advanced Planning Command Center Prior to this release. Enabling Nodal Tuning Previously. All Forecasting measures published from S&OP (excluding historical data series) are now striped by plan name.1. Enabling ‘Dynamic Open Link’ capabilities and Demantra Anywhere Previously.11. nearly all of the Forecasting measures from S&OP were plan independent in APCC and publishing overwrote the previous set of values.1. if a custom item hierarchy has been defined in the Business Modeler (e. Item Hierarchy Mapping: Provide limited mapping of item hierarchy between the Business Modeler and APCC.

This feature increases the computation burden of the order promising calculation. due to which GOP searches for supply later than the requested date). 3.12.1. In this version. Release 12. In previous releases.2.1. • • • • 3.1 and 12. you should not run a TPR simultaneously with an Ad.1. Enhanced Forward ATP Prior to this enhancement.3.1.1. 3. the buydown calculation was deterministic and calculated using the minimum retailer margin constraint.12. buydown is now part of the optimization problem and the value is selected by the optimization process.2. Control over impact of financial constraints: Provide the ability to turn off financial constraints such as minimum manufacturer or retail margins.1.2 Release Content Document Oracle Global Order Promising 49 . customers might require that value be used as the baseline for the promotion when calculating Revenue and Profit. especially in very constrained supply scenarios.2.12. With this enhancement.12.3 3. This did not guarantee that the source with the best promise date would get selected. Enhancements to Optimization A number of enhancements are introduced: • Exclusion rules: Users will be able to define a set of conditions that should not occur together in a solution.1. Release 12.functionality for Predictive Trade Planning customers who purchase Trade Promotion Optimization.3. Oracle E-Business Suite Releases 12. This enables more granular control of the analytical engine. In this release. Define baseline: If a manual override was done to the baseline forecast. With this enhanced behavior. For example.12. GOP returns the best possible promise date by combining availability across all sources. GOP would consider sources in rank order and select the first source that yielded a promise date less than or equal to the latest acceptable date. Vehicle cost overrides: The vehicle_cost expression has been changed to allow cost event overrides per causal and per transpose. and may impact GOP performance. The enhancement is enabled by enabling the profile “MSC: Use Enhanced Forward ATP”.1. during forward scheduling (when there is insufficient supply to promise a demand on its requested date.1.2 There are no new features in Oracle Global Order Promising in Release 12.11. we provide control over the expression denoting baseline. Oracle Global Order Promising 3. Release 12.1 There are no new features in Oracle Global Order Promising in Release 12. Optimized buydown: Buydown is now optimized like other variables in the optimizer. and discount should exclude discounts in a certain range. GOP uses iterative search logic to determine the most optimal promise date during forward scheduling. 3.

1.1.3. IO did not have the ability to ensure integer valued safety stock solutions within input budget constraints. In addition. Release 12. Support for Intermittent Demands Inventory Optimization now explicitly supports forecasts that represent intermittent demands.1. Release 12.2. Release 12.13. 3. will now be assumed by IO to have a more appropriate Poisson error distribution about the forecasted mean.2.1. or forecasts that are designated via plan options to be of the intermittent demand variety. 3. Oracle Inventory Optimization 3.13.1. Forecasts that are fed into IO from Service Parts Planning that have been generated using a statistical method designated as being for intermittent demands. A new heuristic ensures integer valued safety stocks while respecting input budget constraints.2 Release Content Document Oracle Inventory Optimization 50 . Enhanced Budget Constraints Prior to this release.13.1.2.4.13. Release 12.2 There are no new features in Oracle Inventory Optimization in Release 12.3. Release 12. 3.12.3. IO intelligently distributes small calculated total safety stock targets across multiple echelons of a supply chain so that the location-specific targets are integer numbers.13.1.4.13.1 and 12.13. A few points about the new heuristic: • • • It is applicable only for a single level supply chain It is applicable only for plan level and organization level budgets It is applicable for both intermittent and non-intermittent demand streams 3. This new heuristic is enabled by setting the profile option “MSR: Budget Heuristic” to Yes (the default value is No). Oracle E-Business Suite Releases 12.3 3.2.2 There are no new features in Oracle Inventory Optimization in Release 12.1.2 There are no new features in Oracle Global Order Promising in Release 12.1 3.

Enhanced Alerts In PS.1. This enhancement provides improved visualization throughout the model and schedule views.14. Integration processes automatically populate this list when PS is run in an integrated manner o 3. Alerts have been broken down into four distinct categories (Work Order.14.1. Release 12.1.1.14. Oracle Production Scheduling 3.3. Inventory and Resource) and various types within each. o A global “Unit Of Measure” tab has been added to the scenario properties where users can visualize / define units of measure.2 Release Content Document Oracle Production Scheduling 51 . Units of Measure on Items A “Unit Of Measure” has been added as an explicit attribute of every item. Demand.14.1 and 12.1. These alert categories and types are added to the Model Workspace in the form of a tree control for easier navigation and summary data visualization Oracle E-Business Suite Releases 12.1 3.2.

Work Order Centric KPI Comparisons The KPI comparison view can now be viewed as either Demand centric or Work Order Centric. you can now understand the impact on the work order schedule when comparing scenarios. Via a new dropdown option.3. Oracle E-Business Suite Releases 12.2 Release Content Document Oracle Production Scheduling 52 .The alert view is now tab based and summarized by category / type and is context sensitive to selection within the Model Workspace for easier navigation 3.1.14.1 and 12.

This avoids the user having to navigate back through to the model workspace or the “where used” properties of a resource to in order to be open an operation. Right click | Add Production Work Order).e. Oracle E-Business Suite Releases 12. Auto-create Work Orders Directly from Demands For schedule prototyping purposes.2 Release Content Document Oracle Production Scheduling 53 . Access Operation and Routings from Operation Instances This usability enhancement allows the user to perform a right click on a given operation in any of the schedule Gantt charts and easily drill down to the operation and/or routing diagrams. users sometimes create Work Orders directly in the PS in Work Order Editor using standard functionality.5.3.1 and 12.14.1.4. scenario simulation purposes and/or product demonstrations. 3.14. users usually peg these back to a given sales order. Once the work order is created.1. (i.

A simple right click on a demand or a folder or a subset / mixture of folders and demands (via multi-select) allows users to automatically create a work order per demand. You can limit the search to the following (by chosen scenario): o o o o o o o o o o All (will search all model objects listed below and their description fields as well) Supplies and Demands only Work Orders only All Resources Crews only Machines only Tools only Items only Operations only Routings only Selecting and double clicking the result (or selecting the “Open button) will drilldown to the selected object.2 Release Content Document Oracle Production Scheduling 54 .6.14.This works well.1. For example. Find Functionality for Model Objects Find functionality is now available in PS using “CTRL-F” via the PS toolbar by selecting Edit | Find.1 and 12. double clicking the operation code will open the operation diagram Oracle E-Business Suite Releases 12. This will launch a “Find” dialog box which provides text based searching in the PS model and the ability to drilldown to the “found” objects. but if there are many sales orders and the user wishes to create a work order for each demand / line item combination this could potentially take quite a bit of time. A new feature has been added to PS that allows users to automatically create Work Orders for a given sales order without even navigating to the Work Order Editor. 3.

“Material 1” is consumed in operation A and pegged to both an on-hand quantity and a purchase recommendation.3. This release addresses this by explicitly detailing each of the pegging relationships.1 and 12. The production below it indicates the remaining quantity is from manufacturing activities. if an order was fulfilled from both production and either starting inventory or a supply event.1.1. This applies to materials. WIP and finished goods.14. >1 work order operations having an Active Status on the work order routing operation step which conflicts with another work order >1 work order operations with a “firm” status with overlapping date ranges For example. the area shaded in yellow indicates a point in time that occurs prior to the horizon start. Visibility to Demand Fulfilled via Starting Inventory In previous versions of PS. The demand for “Item A” shows a green diamond at the start of horizon indicating some of the order is taken from inventory. the starting inventory was not simultaneously displayed in the Production Pegging view (only the Production).8.2 Release Content Document Oracle Production Scheduling 55 . in the screen capture below. There are a variety of different scenarios which cause backlog in the schedule for example: o o o Work order operations having a Firm Start Date. Firm End Date. Oracle E-Business Suite Releases 12.7. “Material 2” is pegged to starting inventory and an incoming purchase order. or Firm Date Range in the past. Automatic Reconciliation of Schedule Backlog It is common to see shop floor backlog in the schedule views to notify the scheduler that the shop floor is behind and action should be taken to reconcile the situation.14. each represented with a diamond representing incoming supply 3.

While this provides excellent feedback to users. This can also be persisted in the data model for a given resource as well. but only if they share 1 or more similar “Attributes” (such as Temperature. Oracle E-Business Suite Releases 12. in the diagram below. the operations running behind will be one of several operations that are contained within a routing. Color.9. The operations on the applicable resource are “pushed forward”. Operations running in the past will be pushed to start at the beginning of the horizon. Any upstream or downstream pegged operations of this operation will be pushed forward (if precedence constraints dictate). Duration etc) and “Attribute Value” such as 1 Hour @ 400 Degrees Typically. these resources have several “spots” or something equivalent in them.e. 3. Enabling this flag (or setting it in the data model) and performing a repair solve will “push forward” all operations on that resource to the start of the horizon while maintaining operation sequence and at the same time respecting upstream / downstream precedence constraints. Enabling this flag (or setting it in the data model) and performing a coldsolve will accomplish the same thing without user intervention (i. selects “Enforce Horizon Start” and performs a repair solve (or cold solve). This release of PS provides the user with a right click menu item “Enforce Horizon Start” on resources. In many cases. For example. the operations running on Die Bonder 2 are running behind. maintaining the original sequence. Batchable Resources A “Batchable” resource can be described as a machine / oven / kiln (or similar) that can process one or more items simultaneously.2 Release Content Document Oracle Production Scheduling 56 . (Users are also able to multi-select and enable this flag for all highlighted resources). performs a right click. it could potentially be somewhat cumbersome to do when there are many operations running behind and/or many resources in the model. moving operations from the past to horizon start may have consequences on other operations in the routing. it also introduces another issue – the operations can not actually be run in the past. The sequence of operations on the resource will not be changed. reconciling the schedule was primarily performed by using Cut | Paste in the Resource Gantt. Items when processes within these resources consume 1 or more of these spots. Since routings have precedence constraints between operations. Auto-reconciliation). While this method worked well.1 and 12. Prior to this release of PS. The user selects Die Bonder 2.1.14.

o For example.1. all operations will be grouped together of the same temperature up to the max capacity of the resource. the user can switch the order (via cut/paste.2 Release Content Document Oracle Production Scheduling 57 . paste entire batches between ovens. if a sequence on a resource is scheduled to be 10 Hours at 500 Degrees followed by 12 Hours at 400 Degrees. Bubble help indicates the attributes of the batch and one can utilize an option in the Toolbar which allows you to highlight only certain batches if you wish (in orange). Manually move operations between batches if desired or manually move an entire batch. 3. move operations from batch to another.This enhancement to PS enables the following behavior: o o o o o o Allows users to explicitly define a given resource as “Batchable” along with a minimum and maximum spot capacity Define a pull forward window to allow a resource to be filled to it’s minimum spot capacity Allow users to explicitly associate 1 or more user defined attributes and attribute values to an item. T Automatic grouping of operations on a batchable resource by attribute If this is 1 attribute (such as temperature).10. In many cases. this implies that all operations sharing the same duration and temperature will be run together to the max capacity of the resource. this resource set recurs in an upstream or downstream operation(s). These alternate resources are modeled via the use of resource sets. the Resource Gantt below illustrates several ovens (CC4101 -> CC4105). In many cases. For example. re-sequence in the resource gantt). The summary colour at the oven level indicates spot utilization. Each of these ovens constrain a variety of operations which are running at the same time and grouped by temperature and duration. resequence batches and even manually move operations into another batch which does not share the same attributes (you will be provided with a warning…). If the user groups by more than 1 attribute (for example temperature and duration). You can cut. Consistent Resource Assignment within a Portion of a Routing Alternate resources in a given manufacturing operation are very common amongst most Production Scheduling customer models. Batches are of course applicable to regular manual scheduling activities. drag/drop. it is imperative that once a resource is chosen in Oracle E-Business Suite Releases 12.14.1 and 12.

resource assignment must be the same for the following 2 operation steps. Oracle E-Business Suite Releases 12. all operations run on either M1 or M2. With the exception of the Cooling operation. Users expressed the desire to be able to perform consistent resource assignment within only a selected group of operations within this routing .Setup(2). run and cleanup operation where it is then cooled. the same logic occurs for the next recurrence of the setup. The item passes through a recursive process . The user opens up the properties of the routing and creates 2 distinct group and assigns the first 3 operations to the first group and the last 3 operations to the second group as illustrated. This enhancement in PS allows users to be able to configure PS to do just this. (You don’t want to cleanup a machine that you didn’t run on). Consider the following manufacturing routing.50 and 60 even though share a common resource with their preceding operations can run on the alternate. The cooling process occurs in a staging area. 20 and 30 must run on the same resource but steps 40. it must through a setup. Run(2). it must also be chosen in a downstream operation.     When the first setup operation occurs on either M1 or M2. To make item “A”. and Cleanup(2). as illustrated for the first Run operation.1 and 12. run and cleanup operations.for example. operation steps 10. it must also be chosen in the run and cleanup.an upstream operation. but a different alternate can be chosen. If M1 is chosen in the setup operation. The first three steps must run on the same machine and the last three steps must also run on the same machine. This works well in PS and previously was a routing wide configurable option known as “Consistent Resource Assignment”.2 Release Content Document Oracle Production Scheduling 58 . However. after the cooling operation takes place.

Cycle sizes are now flexible. If the user is using All of Sets (i.The user performs a solve. 4 days etc. In a previous release of PS. Day or a Week. Resource-specific Cycle Times for Campaign Run Optimization PS provides the ability to define: o Minimum cycle times in various bucket sizes. The group must be the same.14.1. 3. When migrating a model from previous versions. consistent resource assignment applies to the group. The point is the operations in the groups share the same resource. the remaining three operations are run on M2. >1 Resource such as a Machine1 and Tool1 OR a Machine2 and Tool2).    If operations are not assigned to groups. For example. they are permitted to be run on any given resource. i. Oracle E-Business Suite Releases 12. The first three operations are run on M1.2 Release Content Document Oracle Production Scheduling 59 . After the cooling operation. a cycle can be 2 weeks. cycle size was either a Shift. This could of course all be on M1 or all of M2 or in reverse order.e.e.11.1 and 12. the import will detect if a routing has consistent resource assignment selected and auto-create a group and assign all operations to it.

A firm date range on a work order operation which is shorter than total operation run / elapsed time In prior versions of PS: o o o If the dates fell within the fixed time fence. Therefore. Minimize Work Order Schedule Infeasibilities As Production Scheduling is a finite capacity scheduling application.1 and 12. For example. some situations can occur which would result in an infeasible production schedule.12. alerting and solver handling of problematic inputs. 3.If the resource specific cycle size checkbox is selected.1. and has drastically improved throughout the past several releases. different lines in the plant can be on their own cycle times rather than having to adhere to global cycle. For example. planners can enable this flag by CRO resource. take the following 2 work orders which are both firmed at the same time outside of the FTF: Oracle E-Business Suite Releases 12. This release continues to improve on this theme. These situations are always being monitored and resolved through improved data validation. In this release there is an added capability for the solver to resolve conflicts of this type outside of the fixed time fence if necessary to avoid this situation. PS would reconcile the infeasibility and alert the planner that shop floor backlog exists If these work order operations were outside of the fixed time fence this resulted in an infeasible schedule.14.2 Release Content Document Oracle Production Scheduling 60 . it is quite common and sometimes unavoidable to have: o o >1 work order operation firmed on a same single capacity resource with overlapping date / times.

it is quite possible that the first operation may be a setup operation and the last operation may be a cleanup operation. if this feature is leveraged. the schedule is feasible.14. Supporting alerts are also provided to the user to indicate the firm date violation. but PS will break it down according to the routing lot multiple. In the example below. The feature can be enabled as either a global option applying to all routings. Disable Units of Effort for Setup and Cleanup Operations PS has a differentiating feature introduced several releases ago which provides the ability to schedule Work Orders according to their individual “unit of effort.” This feature cross references the routing template to “break down” work order operations into the lot multiples specified on the routing.1. Oracle E-Business Suite Releases 12. or the user can specify the feature for specific routings. a work order is scheduled to release inventory according to every lot multiple. inventory is moved between operations in 25 unit increments – the work order has only 3 operations listed on it.1 and 12.2 Release Content Document Oracle Production Scheduling 61 .13.Solved in a previous version – the schedule was infeasible and the planner was provided with an error message indicative of such. For example.    Inventory Production and Consumption is accurate Makespan is accurate Resource usage is accurate In some cases. 3. The highest priority work order is moved to start earlier in the horizon. In this release.

14.14. Oracle E-Business Suite Releases 12. Production or Cleanup”.1 and 12. The new operation structure within PS is depicted below. This type of set can be referred to as a “one of” type of set. Resource “All of” Sets PS provides excellent resource offloading functionality within an operation (e.2 Release Content Document Oracle Production Scheduling 62 .g. Setup and Cleanup operations will not be broken down to their units of effort. For example. etc. meaning one of the resources within the set must be used. Operator 2 can only run Line 3 and Line 2. Machine 1 can be substituted for Machine 2. Crew 1 for Crew 2. the setup & cleanup operations only need to be executed once as opposed to three times. This release of PS has the ability to specify an operation of type “Setup. This means that resource exclusivity relationships can now be defined directly within a given operation as opposed to having to use Operation Sets.1. This release adds a new set type on operations that support resource replacement “groups” within PS ( an “All of” type of set).In this case. 3. Operator 1 can only run Line 1 and Line 3.) via the use of “Resource Sets”.

Pasting to a different time on the same set will be highlighted in light blue.The work order editor has a new column to indicate the name of the “all of” set. plus single resources. If an alternate set has a different number of resources.2 Release Content Document Oracle Production Scheduling 63 . Paste targets in the Gantt charts are consistent with previous versions of PS. Oracle E-Business Suite Releases 12. rows will be added / subtracted as appropriate. Offloading to an alternate set will show the target in orange. This is where manual overrides can be made to which set is attached to the work order. A “1 of” resource set can contain a mixture of “All of” sets.1 and 12.

The overall approach is virtually the same as previous versions of PS. At this point. so the user will have visibility into which “All of” set has been chosen without expanding all of the sets. it must also be chosen in a subsequent step. From an offloading perspective. Oracle E-Business Suite Releases 12. In this release. If any one of the resources in the target “All of” set have their offload thresholds violated prior to the offloading taking place.2 Release Content Document Oracle Production Scheduling 64 . but the offloading calculation must be applied to all members of the set. offloading will still occur to less loaded (but still overloaded) alternates. The operations on the solver selected “All of Set” is summarized on the set name. the operation will not be offloaded to that set.if no alternates have available capacity. This effectively spreads the load and will help get orders met as quickly as possible. If the primary is significantly overloaded. If any one of the resources within an “All of” set have their threshold violated. all resources will be offloaded. Prior to this release. If “Line 1” was chosen in Step 1 of a routing. an additional alternate will be evaluated .The “All of Sets” are shown in the Production Pegging View. Consistent Resource Assignment applies to members of the “all of” set. no offloading should take place. The PS “Consistent Resource Assignment” feature is also impacted by this enhancement.1 and 12. Consistent Resource Assignment across routing steps was based on a single resource.

To make Item A. Hard Links Between Work Orders This enhancement allows a “many to many” relationship amongst Work Orders along with the ability for the user to specify precedence constraints between these Work Orders.15.1. the following routing steps take place.3. Oracle E-Business Suite Releases 12. Material A is a subassembly also manufactured in the plant as per the following process. Assume the following manufacturing process. The business requirements for this enhancement are best explained with a simple example. Item A is produced by Operation C. These Work Orders are related through inventory. Operation A consumes an inventory “Material A”. The lot multiple across the manufacturing routing is 25 units. Assume the user creates a work order for the finished good and the material (50 units each). so will generally schedule JIT and have some degree of overlap as illustrated below.14. This is handy if a specific sequence is required between several work orders.1 and 12. The material is produced by Operation C1.2 Release Content Document Oracle Production Scheduling 65 . The lot multiple across this routing is also 25 units.

Assume the user populates “Starts After End” with a minimum separation time of 5 Hours. In this case. therefore there are 2 routing instances and separation is applied twice. Precedence relationships (to facilitate a cooling process. When “Units of Effort” is used. inspection etc) can also be specified. quality reasons etc).2 Release Content Document Oracle Production Scheduling 66 . the Work Orders are for 50 units each (remember. the routing has a lot multiple of 25 units).1 and 12.If the user wishes to explicitly relate these Work Orders to one another (for example for lot control. the 5 hour minimum separation is applied to the pegged work order routing instances. The relationships between the Work Orders can be “many to many”. Oracle E-Business Suite Releases 12. they can specify the relationship in the work order editor in the new “Related Work Orders” tab. along with min / max separation constraints. Manual Scheduling within PS will have all appropriate precedence relationships respected. • • A given work order can be linked to many “next” work orders A given work order can have many “previous” work orders.

2 Release Content Document Oracle Production Scheduling 67 . The net effect of dynamic rate changes is simple – they make a given manufacturing operation take more or less time to complete in a given time interval. Dynamic Throughput Rates on Resources Some customers vary their production rates fairly dynamically and frequently. B. Item D is produced in runs of 1700 units per week. A. There are various reasons why the speed of a production line may change which may include (but by no means are limited to) areas such as: • • • • • • trial manufacturing process changes line improvements labour constraints new product development temperature / humidity variations This release of PS provides the user with the ability to specify dynamic rates on a resource (crew. At “normal” speeds. For example.14.16. it produces product at a rate of 100 units per hour. C and D. tool). For example. Oracle E-Business Suite Releases 12. machine. the packer now runs at the following throughput rates: • • • 80% in the 1st week 100% in the 2nd week 150% in the 3rd week The user navigates to the Packer resource properties to the “Throughput tab” and defines the appropriate dynamic percentages.1.3. In this example. the speed of a line can change daily or weekly based on available labor.1 and 12. Packing Line #1 produces items. Assume due to a labour constraint.

resources can have different throughput rates for different date ranges. If production is offloaded to an alternate resource with a different throughput.1 and 12. For example. if an operation requires both “Packer 1” and “Tool 1” and they have competing dynamic throughput rates and effective ranges. In a resource set. the “lowest” value for a given time interval “wins”. the operation duration on the alternate resource will reflect the new throughput.The speed at which the items are produced can clearly be seen in Gantt chart by the operation length as well as by looking at the steepness of the slope of the item graph for a given item. If >1 resource on the operation also has a dynamic throughput range. Oracle E-Business Suite Releases 12.2 Release Content Document Oracle Production Scheduling 68 .

the operation duration should change according to the throughput in effect. (i. Remove Idle etc) that has a different throughput rate defined. the repair solve will recognize and change the duration of the operation accordingly.e.  Interactively. Oracle E-Business Suite Releases 12. changeover rules. HP and AIX The PS SCBM / Oracle EBS data connector now runs on the following platforms:  Windows (previously supported)  Linux (previously supported)  Sun (New)  HP (New)  AIX (New) This allows for the PS connector to be deployed on a central server apart from PS if desired.18. the published model is based off of the approved schedule Since the schedule publish process batch file points to a named scenario.14.2 Release Content Document Oracle Production Scheduling 69 . you can export the model from any given scenario which may or may not be the approved schedule.1. All command syntaxes stays the same 3. This is useful if PS is to be the system of record for any data that is not available within the ERP system. machines. If the user offloads an operation manually to a different resource with a different rate.1 and 12. crews. operations etc). 3.  The next time a model is imported into PS. If the user changes the rate on a resource and runs a repair solve. the chosen data will be exported to a user named XML file. integration processes could be extended to reference the various data model elements exported from the previous scheduling session which could amend to the new model prior to import A new tab in the Publish Profiles allows users to define which data objects to publish Whenever the Publish Process is called (whether in batch or interactively). groups. Export Selected Model Data During Schedule Publish As part of the File | Publish process. tools. users now have the ability to publish the PS model or chosen objects of the data model in XML format. Resequencing. Aspects of the model can be output to a user defined filename – any object within the model can be output to this specific file.If an operation is moved to a timeslot via manual scheduling (Cut | Paste.14. PS Data Connector Port to Sun. the operation duration will change according to the throughput in effect.1.17.

xml. but will launch PS directly upon being double clicked. No corresponding routing exists in PS. The .  Contrary to the above.2 Release Content Document Oracle Production Scheduling 70 .1 and 12.1. The icon for either is the PS standard icon.  Operation Sets specified on the work order routing Oracle E-Business Suite Releases 12.opz file is still standard compressed XML format.20.  Missing items on the work order bill of material  Additional operations included on the work order routing.ops file is still standard XML format.19. The PS XML compressed file can be the standard .14. Enhanced Auto-generated Routings The list below outlines a few typical scenarios that cause “Auto-Generation” of Operations and Routing templates based on work order structure within Production Scheduling:  Work orders which were generated in a “Configurator” program.  Missing operations on the work order routing (for example. machines or tools included on the work order bill of resource.gz extension or uniquely to PS as an . Essentially. 3.3. The . Oracle EBS does not pass “Closed” work order operations to PS).1. Work Orders are dynamically created and passed to PS. PS XML Model – Unique Extension The PS XML data files which can be imported and exported now have an additional extension available.  Non-standard crews.xml extension or uniquely to PS as an . sometimes the work order would be missing crews. machines or tools on work order operations.14.ops.  Non-standard items included on the work order bill of material.opz. The PS XML non compressed file can be the standard . but will launch PS directly upon being double clicked.

The user can override this if desired.1. a new feature was added to PS which removed the PS dependency on having a routing template pre-created in the model for every work order in the application. This release of PS has enhanced logic in the import process which addresses these 2 issues.14. If operations differ from their standard templates. Similarly for resource sets . If the user wishes to include / exclude individual work orders from this process (regardless of start time).21. Oracle E-Business Suite Releases 12. nor were the resource sets being constructed. the precedence constraints as specified on the work order routing will be used when the auto-generated routing is created. This launches a new dialog view which lists all work orders and their various attributes. When PS was generating this routing and operation templates.1 and 12. after analyzing the schedule. 3.the operation template is reference to reconstruct the resource sets. the general business process is to publish the schedule back to ERP. This new release provides a new mechanism for the user to be able to individually select which work orders are released back to ERP. it was not reading the precedence constraints on the work order routing between the operations. For example. the import now looks at the operation codes and cross references the precedence constraints on the routing.2 Release Content Document Oracle Production Scheduling 71 . PS dynamically cross references the work order routing against the routing template during the import process. If a work order starts before the end of this timefence. The publish process within PS uses a “Release” timefence to filter out work orders from the release process. The user then performs a right click on the scenario name and selects a new option “Edit Work Order Release”. a newly created operation will be present in the routing as well. Selective Work Order Release to Production After a user approves a schedule within PS. one can expect to see a newly created routing which directly corresponds to the work order in question. If a work order meets on of the problematic scenarios outlined earlier. this was not possible prior to this release. When generating the precedence constraints for the auto-generated routing. the user approves the schedule he/she is happy with. The Publish Profile selected has a Release Horizon. For those scenarios outlined. Any Work Orders starting within this release horizon will be auto-selected.In a previous release of PS. it will be included in the release. If the work order has different precedence constraints than the routing template.

solver objectives cannot be set changed each stage – they are set at a global level. it sometimes is desirable for users to be able to dictate to the Production Scheduling solver which resources to focus on first.2. a Stage) 2) Insert breakpoints where the user can review solve progress at any given stage (and even refine the schedule as appropriate via manual scheduling and then resume the larger solve process). The scope of this enhancement is to allow different solver objectives by solve stage. However.14. Currently in Production Scheduling.1. Addressing the most critical constraints first breaks down sequencing problems into smaller sub-problems which are generally “easier” to resolve.essentially enabling scheduling in an incremental fashion via some simple configuration in the application.2. Resource Business Objectives From a resource perspective. tool capacity and calendar constraints simultaneously when sequencing operations.2 3. Production Scheduling generically considers all crew.1 and 12. This approach optimizes the bottleneck stage while minimizing WIP between upstream / downstream stages. However.3. users can dictate to the solver engine which resource or group of resources should be focused on and in what order . Focusing and resolving the most critical constraints in the scheduling horizon has been regarded as the most effective scheduling strategy to resolve multistage floating bottleneck problems when sequencing operations.e. then mix the upstream materials JIT.1. then immediately pack the kits and assemblies from the molding using a prebuild solve strategy. Oracle E-Business Suite Releases 12.14. For example. Release 12. This enhancement will allow users to: 1) Set solver objectives by group of resources (i.2 Release Content Document Oracle Production Scheduling 72 . one may wish to optimize changeovers on the injection molder. machine.

14. It also allows for batch solving of multiple plans (i. and AIX platforms. 3. Automation of the “what if” process).e.2 Release Content Document .3.the solver and application have been decoupled such that the import and solve process can optionally be run on the server – this includes Linux.2.2. Sun Solaris.3) Setup Multi-stage Campaign Run Optimization (CRO) – users will have the ability the utilize the CRO algorithm in a multi-stage fashion provided the stages have decoupling inventory and the CRO resource is not recursive. This enhancement will have many benefits including: • Increase PS market applicability • Address business where multi-stage strategies are necessary • Minimization of Work In Progress Inventory (Directly address make | store | pack requirements) Reduce cost of ownership for our customers • Directly enabling user scheduling strategy this eliminating potential complex workarounds to achieve desired results Allow multi-stage use of the Campaign Run Optimization Algorithm which also provides: • Multi-stage routing offloading • Improved alternate resource selection • Multi-level SDS minimization and min run length 3. The user interface continues to run on the planners windows client (includes support for Vista). This enhancement also includes improved application status logging and filtering . This enables Production Scheduling users to have their models presolved on the server – saving time and improving efficiency.14. Production Scheduling as a Web Service Call Production Scheduling has been enhanced to be able to be called as a service . Undo Functionality for Manual Scheduling • • Manual Scheduling in Production Scheduling includes a variety of activities such as:   Cut/Paste Resequence Oracle Production Scheduling 73 Oracle E-Business Suite Releases 12.1 and 12.including access to various event statuses and solver statistics log from within Production Scheduling for events which took place on the server. The server side functionality creates a deployable solved model which includes import and solver statistics in log files which are all downloaded to the client desktop on planner request. HP-UX.2.

The Undo action reverts back to the previous “solve state” prior to the change. For example: Action: {solve stage | breakpoint} | manual change | Repair | Undo Result: Will undo the manual change Action: {solve stage} | {solve stage | breakpoint} Undo Result: Will undo the 2nd solve stage – result will revert back to the first solve stage Oracle E-Business Suite Releases 12.upon which the solution will revert back to the previous solved “stage”. Examples include: Action: {manual change} | UNDO Result: Will undo the manual change Action: {manual change} | Repair | UNDO Result: Will undo the repair and manual change Action: {manual change} | {manual change} | UNDO | … Result: Will undo both manual changes Action: {manual change} | {manual change} | Repair | UNDO Result: Will undo the repair and manual changes Action: {manual change} | Repair | {manual change} | Repair | UNDO Result: Will undo the 2nd repair and 2nd manual change Action: {manual change} | Repair | {manual change} | Repair | UNDO | UNDO Result: Will undo the both repairs and both manual changes Undo also applies to another new feature in Production Scheduling (Resource Business Objectives).       Remove idle Change durations of operation instances Change start or end times of operations Change calendar events in the Gantt charts (add / remove / change) Change resource assignment (i. This enhancement to Production Scheduling provides the ability to “Undo” these changes. However it is possible that the user may not accept the repaired schedule or simply made a mistake when implementing this change. manually offload) Fixing / Unfixing operations (single or multiple operations) Change lead times for Purchase Order Recommendations.1 and 12. Following each of these actions. Undo can be performed within this context as well.e.2 Release Content Document Oracle Production Scheduling 74 . This includes the ability to undo manual changes in the stage itself as well as to completely undo a given “stage” of the solve process . At a breakpoint) in the solve process.e. there is a repair based solve action to institute the change and “repair” any upstream / downstream ramifications this change may have caused. Included in this feature is the ability to solve groups of resources in a “Stage” and perform manual scheduling activities between stages (i.

which currently do not have these setups either represented or optimized. providing the ability to specify a Flavour Changeover (Attribute) which includes Apple -> Blueberry (Attribute Values) etc.1 and 12. Operations and Groups will have attributes assigned to them. Changeover rules specified by attribute will automatically associated all operations sharing the same attribute. 2) Extend sequence dependent setups to Batchable resources.14.4.2 Release Content Document Oracle Production Scheduling 75 .3. Attribute Based Sequence Dependent Setups This enhancement to Production Scheduling is two-fold: 1) Improves the current sequence dependent setup rule representation to be Attribute based rather than having to specify rules by operation code or group. The Production Scheduling integration to Oracle EBS will use Setup Type as an attribute and various values associated with Setup Type as the appropriate Attribute Values. Users will now have the ability to specify changeover rules by attribute type / value.2. For example. Oracle E-Business Suite Releases 12.

This provides for improved visibility to changeover patterns in and across manufacturing cycle boundaries.1 and 12. Visualization of Campaign Run Optimization Cycle Boundaries This enhancement allows users to explicitly visualize manufacturing cycle boundaries when using Campaign Run Optimization.2. Oracle E-Business Suite Releases 12. can the flavor changeover be performed at the same time or does it have to follow the size changeover? 3.This enhancement to Production Scheduling also allows the user to specify if changeovers can be concurrent or sequential if multiple attributes are specified and can be performed at once.14.2 Release Content Document Oracle Production Scheduling 76 .5. For example – if I am performing a size changeover.

CRO Manufacturing Cycle Boundaries shown in brown.

3.14.2.6. New Alert Type and Drilldowns A new “Resource Utilization” alert has been introduced to indicate when resources which are not part of a bottleneck resource group have capacity violations (when capacity constraints are relaxed) Drilldowns to the Gantt charts from all resource alerts are included this new alert as well.

When using Batchable resources, drilldowns are also now provided from the “Minimum Batch Violation” alerts as previous versions did not allow this.

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

Oracle Production Scheduling

77

3.14.2.7. Drilldowns from the Work Order Editor to the Gantt Charts Additional drilldowns introduced in the application make finding work orders in the Gantt charts much easier. The drilldown from the work order editor which is launched via right click in the editor from the operation code takes the user directly to either the Production Pegging view, the Resource or Operation Gantt views. Drilldown from the Work Order Editor highlights the selected operation and performs a context sensitive zoom as well.

Drilldown zooms and highlights the application operation:

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

Oracle Production Scheduling

78

3.14.2.8. Mass Change on Items and Resources For mass change simulations, Production Scheduling now provides the ability to mass edit item and resource properties. All item properties and resource properties can easily be changed simply by multi-selecting the appropriate items or resources in the model workspace and invoking the “change” function. Change is specific to the scenario and session only for simulation and scenario comparison purposes (changes are not sent back to ERP) Changing Item Data via right click on >1 items and selection of “Change” in the menu:

Mass Change of Resource Data:

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

Oracle Production Scheduling

79

Milestones – These provide the ability to specify logical groupings of work orders within a Visit.3. Work Breakdown Structure – Several new key attributes have been added to work orders which can be used for organizing and filtering work orders. the following key capabilities are now available in Oracle Production Scheduling: Collection of Oracle cMRO Work Orders Production Scheduling now optionally collects Oracle CMRO maintenance work orders.1. The overall architecture is represented in the following diagram. An API into these new tables to augment collected data has been added to complement the existing collections framework as PS requires this information to generate a maintenance schedule. Currently.3. housing information such as visits. It must account for: • • • • • • Visit start / end dates Visit milestones Task hierarchies Crew. tool. The combination of Visits and Milestones provides a capability to define task hierarchies that flexibly group work orders together in both concurrent and sequential patterns where work can diverge and converge. Several new constructs have been introduced into PS to allow for this: Visits – This new data construct allows users to associate one or more work orders. have been added into the Operational Data Store (ODS) as this information is required to properly schedule cMRO work orders.3.1. where the work orders will fall inside Visit envelope dates such as the anticipated aircraft arrival into a maintenance depot and the request date associated with the completion of the Visit. machine.14.3 3. work breakdown structure. work order relationships.14. this information is not available to standard planning collections from cMRO. New Operational Data Store Tables for Data Augmentation Six new tables. The scheduling of visits must take into consideration numerous constraints. and milestones.1 and 12. Release 12. and material constraints Operation / work order precedence constraints Grouping of work based on work breakdown structure To support these requirements. Oracle E-Business Suite Releases 12.2 Release Content Document Oracle Production Scheduling 80 . Maintenance Work Order Scheduling The scheduling of maintenance resources at a maintenance depot can be quite complex.

1 and 12. Visits and milestones are presented in various views in Production Scheduling and allow the planner to leverage the rich set of existing functionality to review and refine the schedule. tracking. and Work Order views. Advanced Work Order Filtering Work order filters can be used to facilitate the review and analysis of the schedule and allow the planner to “slice and dice” the data in the various Gantt. and Complex Task Hierarchy Relationships Visits have been added to Oracle Production Scheduling to allow for scheduling. While this feature has been added to facilitate cMRO workflows. it will benefit many of our existing manufacturing customers as they will also be able to filter on many of the existing constructs already available in work orders. and grouping of tasks in the form of work orders and milestones. Milestones. Utilization. This feature allows the planner to hone in on specific tasks and answer questions such as “show me all work orders in stage 3a from July 2-July 4 utilizing the Advanced Airframe and Power crew which are firm”.Support for Visits. Oracle E-Business Suite Releases 12. Visits and milestones also present new constraints which govern the production schedule that is generated.2 Release Content Document Oracle Production Scheduling 81 .

1 and 12.Oracle E-Business Suite Releases 12.2 Release Content Document Oracle Production Scheduling 82 .

2 Release Content Document Oracle Production Scheduling 83 .1 and 12. Oracle E-Business Suite Releases 12. The work breakdown structure is populated as work order attributes and can be viewed in the work order editor.Representation of Work Breakdown Structure The logical grouping of work can be accomplished by leveraging the Work Breakdown Structure constructs in PS. A Display Parameter tab has been augmented in the Plan options screen with new data that can be used to create logical groupings of work orders. This allows for advanced filtering in Work Order Filters where they can be used to group work orders in the various views when analyzing the schedule.

Disable Multiple Release from the Same Plan for the Same Order This enhancement allows Production Scheduling to keep track of work orders which are sent back to source as “Released” and disable subsequent release from the same plan to Oracle E-Business Suite Releases 12.Once the model is reviewed and analyzed in Production Scheduling.3.2. 3.2 Release Content Document Oracle Production Scheduling 84 . but focus has been on solving aircraft short term maintenance scheduling problems. The solution may be applicable for other industries with similar requirements.14.1 and 12. work order dates generated by the schedule and can than be released back to cMRO for execution.

prevent creating duplicate supplies in the ERP system. The user solves the model (if not already solved on the server). the Work Order Release Checkbox is no longer selectable for those work orders: Oracle E-Business Suite Releases 12. as re-importing from XML source will not preserve this information. the user will then approve or “Release” selected Work Orders to source and publish to ASCP as she/he deems appropriate (no change to existing functionality).dxt file (PS persistence for solved models). The user is also free to close the model and reopen the . Illustration: The user selects the first four work orders for release: The user “releases” back to source: On subsequent navigation to the Release View. the user will not be able to release the same work orders from the application as the checkbox indicating which work orders to release will be grayed out. The user then saves the schedule as a .2 Release Content Document Oracle Production Scheduling 85 .dxt file as necessary. This process functions per the procedure below: • • • • • The user generates a plan and downloads to the client per standard procedures. This is a key step. Once the scheduler is happy with the plan.1 and 12. After this action.

or in the global solver options): Oracle E-Business Suite Releases 12. The solver performs an evaluation of these penalties and computes the ideal sequence on this resource. The changeover matrix contains the applicable penalty factors of moving between different operations producing different items. users simply wish to dictate this order of operations to the solver in lieu of having to construct a penalty matrix to influence this. alternate routings or violating safety stock in and across manufacturing cycles and may optionally pull work forward to delay operations appropriately. 3. User Defined Ideal Sequence Production Scheduling natively provides the ability to dynamically calculate an ideal operation sequence for Campaign Run Optimized Resources per manufacturing cycle.14. Any work orders not previously marked as released will still be available for release or publish (as planned orders) into ASCP. CRO then optimally computes the tradeoff between carrying inventory. using alternate machines. they can open the original XML file that was downloaded from integration. This is based on changeover cost or time (user specified) in the Scenario / Solver Options. While this is possible to configure using costs. this enhancement allows users to specify the sequence operations should be scheduled in CRO according to attribute. as illustrated. and is available for CRO resources only.1 and 12.3. Solver options are enhanced to indicate the Run Sequence as User Defined (by solve stage. stocking out.• • If the user does want to release the same work orders again for some reason. incurring changeovers. In many environments. This is an alternate sequencing strategy compared to the current CRO sequencing strategies of Cost or Time.2 Release Content Document Oracle Production Scheduling 86 .3.

there are Grades A and B. Assume the user defined Ideal Sequence is to cycle by size and grade within the size. as outlined in the following example: 1/4 Inch-Grade A -> 1/4 Inch Grade B -> 1/3 Inch-Grade A -> 1/3 Inch Grade B -> 1/2 Inch-Grade A -> 1/2 Inch Grade B. This would be setup in Production Scheduling in the Attributes tab where attributes are associated to resources. 1/3 Inch and 1/4 Inch as attribute values.2 Release Content Document Oracle Production Scheduling 87 . Oracle E-Business Suite Releases 12. take attributes “Size” and “Grade”. t h e “order” in which the selected attributes and attribute values in the right column are structured in the UI dictates the ideal sequence of operations (the operations must be associated to these attributes).The mechanism in which the “ideal” sequence is defined is by selecting and sorting of associated attributes and their attribute values on CRO resources in the model. E s s e n t i a l l y .1 and 12. If Grade was more important than size. The sequence would then cycle by Grade and then Size within the Grade. For example. Within “Size” there are 1/4 Inch. then the user could move the Grade above the Size Attribute. Within the “Grade” attribute.

and Internal Sales Orders. However. it will have Work Orders as a source of supply.3. 3. there may not be an additional work order created for the extra 1 unit in ASCP (lot sized of course) due to a supply tolerancing feature it has (this can be at any level in the bill of material).in some cases. Instantiating net new production disrupts other production runs.1 and 12.999) and have an order quantity of 135.14. typically one would assume there are sufficient supply quantities generated in the form of work orders to meet the stated demand requirements for the organization being scheduled by the time you are actually scheduling your facility.2 Release Content Document Oracle Production Scheduling 88 . PS naturally uses the routing lot size to recommend new production . Forecasts. PS does not have this explicit supply tolerancing feature. Since PS is a scheduling application. The net result is that PS may recommend extra production as PS sees the need to balance supply and demand down to the unit.000 (finished good or intermediate). A feature has been added to Production Scheduling to be able to essentially “shut off” any PS created net new production suggestions to avoid these situations.4. However. if you have supply (say an on-hand inventory of 134.000lbs per run) and completely unnecessary as it is perfectly acceptable to ship 1lb less than order size. this could be very large (such as 100. For example. Demands are created via Sales Orders. Supply Tolerancing The Production Scheduling integration infrastructure to Oracle EBS and JD Edwards EnterpriseOne uses “Work Orders” as the vehicle to communicate production requirements and schedules between systems. When a PS plan is created.This is a very powerful tool to help make sequencing decisions and reduce changeovers in the model. steals capacity and materials – schedule quality is inevitably diminished. Transfer Orders Out. in some cases it is acceptable for demands to be shorted by a certain quantity or percentage without the generation of additional supply requirements. This exists in Tools | Options | Global Settings: Oracle E-Business Suite Releases 12. etc.

customers do find these order multiples to be useful for various types of modeling approaches. only work order supply production will be scheduled). Control Application of Purchase Item Order Multiples Beyond Lead Time Items marked as “Purchased” in Production Scheduling must be associated with a source of supply (i.With this flag enabled. there is a flag entitled “Relax Purchase Items Beyond Lead Time”. It is key to note that Production Scheduling is not intended to plan procurement specifically. supply for these purchased items is essentially unconstrained – therefore the purchase item multiple is not especially relevant. If there is insufficient work order supply.14.3. Beyond lead time.2 Release Content Document Oracle Production Scheduling 89 . 3. Keeping these “relaxed” helps solve performance and is generally recommended. a Supplier) and a corresponding order multiple must be modeled.e. Oracle E-Business Suite Releases 12.5. Utilizing this feature assumes work order supply is sufficient to meet demand. there will be no net new production recommendations generated at any level in the BOM (i. A PS log message is generated to indicate what inventory quantity adjustments were made. inventory will be automatically added to prevent levels from falling below zero (i. A feature has been added to be able to control whether or not purchase item multiples are respected beyond supplier lead time or not. Demand is permitted to be shorted). However.e. In the PS Plan Solver Options.1 and 12. Default is set to ‘Yes”.e. but to be constrained by lead time only.

the item graph is displayed taking into account the order multiples.1 and 12. If the flag is set to “No”.When this flag is enabled. Beyond the lead time. the item graph is shaded to indicate infinite supply. the order multiple is internally set to a very large value and effectively ignored beyond lead time – one will see the addition of a new red line in the item graph to represent the time of the item.2 Release Content Document Oracle Production Scheduling 90 . Oracle E-Business Suite Releases 12.

2 Release Content Document Oracle Production Scheduling 91 .14.6.7. Utilization.3. The results are previewed in the bottom of the filtering view and planners can drill-down to the Work Order Editor directly from here as well if desired. In order to address this. VCP collections introduced a new column entitled “operation_status”. Improved Operation Status Logic in OPM integration If an OPM Batch Operation has a “firm start” resource but is still in pending state.3. The corresponding PS integration code has been modified to read this new status from this new column to set an operation as Open. 3. The OPM system will populate the operation status as Pending.14. and Pegging views in a multi-dimensional fashion and filter the content of these views. This feature allows the planner to hone in on specific areas of the schedule only – for example “show me all work orders in from October 25 – November 5 running on Resource (or Group) which have a Firm Start status”. Oracle E-Business Suite Releases 12.1 and 12. the PS integration code was previously interpreting this operation as Active when importing into Production Scheduling. Advanced Work Order Filtering This release provides new work order filtering capabilities which allows planners to further “slice and dice” data in the various Gantt.3. WIP or Closed. Active or Closed in Production Scheduling.

Selecting “OK” will filter out the various Gantt Charts.A new “Work Order Filter” view has been added to PS which is accessible off of the toolbar. Selecting the icon launch the filtering window. The user then inputs criteria.1 and 12.2 Release Content Document Oracle Production Scheduling 92 . Oracle E-Business Suite Releases 12.

15. Rapid Planning delivers fast. heuristic based engine that generates supply chain plans that span the enterprise manufacturing and distribution networks covering the supply chain from supplies to customers.15.4. Oracle E-Business Suite Releases 12. 3.14.1 and 12.2 Release Content Document Oracle Rapid Planning 93 . Oracle Rapid Planning 3.2 There are no new features in Oracle Production Scheduling in Release 12. This is a very useful feature which provides a very advanced level of filtering capability into an already rich user interface.2. comprehensive plans that respect material and resource capacity constraints.1. Product Overview Oracle Rapid Planning is a fast.You can create as many filters as you like which are specific for various analysis purposes and even save them locally as a file (and send to your colleagues). Release 12. 3.

etc. Rapid Planning leverages the integration capabilities of the Value Chain Planning suite which means it can be deployed and integrated out-of-the-box with Oracle E-Business Suite or with heterogeneous back-end systems.15.2.3. but replan only incremental changes 3.15. Flexible User Interface This application enables a completely new rich-client user interface built using 11gR1 Fusion Middleware technologies and supports configurable workspaces. but complete replan Without snapshot.2. It allows planners to evaluate the consequences of these changes and also compare and contrast various alternative courses of action based upon user configurable metrics. Simulation Sets Oracle Rapid Planning makes simulations very easy through the powerful feature of simulation sets. It also re-calculates the exceptions. Rapid Planning supports input of simulation changes to master data like items. Rapid Planning is integrated with Oracle E-Business Suite R12.2. to make the user experience very productive as well as easy to use. dynamic tabs.2. Release 12. Fast Simulation Oracle Rapid Planning uses an in-memory engine that can very quickly react and recompute the impacts of any user changes and report. 3. Rapid Planning utilizes the proven Advanced Planning collections architecture to integrate your source system reference and transaction data to the Rapid Planning engine. the consequences across the supply chain.3 3.1.1. key performance indicators to reflect these impacts.2. resources. routing operations in two ways: • • Change the master data inside a particular plan and re-solve Change the master data in a simulation set for repetitive use in more than one plan The planning engine can be invoked in three different modes • • • With snapshot and complete replan Without snapshot. components and substitutes Resource Availability Manufacturing Order Resource Requirements Manufacturing Order Operation Networks Calendars Oracle Rapid Planning 94 Oracle E-Business Suite Releases 12. bills of materials. 3. • • • • • • • • • • Items End Item Substitution relationships Resources Routings and operations Routing Operation Networks Bill of Materials. in real time.15.Oracle Rapid Planning provides users an ability to simulate and quickly evaluate impacts of various changes in demand and supply conditions.1 and 12.2 Release Content Document .15.1 and R11i10. flexible layouts. A simulation set is a collection of changes to the attributes of any of the following master data entities.

increase the post-processing leadtime of all items in category ‘ABC’ by 10%) through the massedit feature. Oracle E-Business Suite Releases 12. Aggregate. Users can undo the simulation changes at an attirbute-level by using “set value to original” operator to revert to the original value. The system will allocate the updates to individual items and days. Product Cateogry. but now on-time Was late.1 and 12. 3. etc. For example. Product Family and Item. Users can also update the aggregate level horizontal plans. users can use order-by-order comparison view where they can compare any two plans (or a single plan with its previous run) and make the following comparions: • • • • Was on-time. “increasy by %”.15. This feature is supported for almost all entities like items. “decrease by”. This saves a lot of time and effort for the planners. demands. etc. but now less late Was late.4. but now more late 3.2 Release Content Document Oracle Rapid Planning 95 . users can update forecast quantity at the product category or even at a period level. Once the plans are run. “increase by”.5.2. Mass Edits Users can make quickly make updates on a large number of rows (for example. but now late Was late.6. resources. time granularity. 3. supplies. “decrease by %”. These simulation sets can then be referenced in different plans through a plan option.15. firming.• Supplier capacity This feature enables planners to do “what-if” analysis without having to make these changes permanent or without the need to make these changes in the source ERP systems and re-collect to see their impacts. etc. Editable Material Horizontal View The application supports a material plan with a layout wizard that lets the users to customize the layout including the measures displayed.15.2. etc. Plan Comparisons Oracle Rapid Planning allows users to quickly make multiple copies and then use them as alternatives for corrective actions.reports and graphs All exception views Supply and Demand view Material and Resource horizontal plans In addition.2. The aggregations are done real-time and take into account all current user changes. users can compare any two plans (or one plan with its previous run) inside any of the following four views: • • • • All analytics . Users can update using various operators like “set value to”. Users can also specify two aggregation levels from a choice of Organization.

users can drill either upstream or downstream to view the supply chain from a single order. This enables for a consolidated view of the entire tree without having to switch between multiple views..15.2. Rapid Planning unconstrained plans produce a full complement of exception messages to alert the planner to critical constraint violations. alternate Oracle E-Business Suite Releases 12. and “Supplier Capacity Violated”.15. These archived versions can then be viewed in all the related reports and dashboards. Rapid Planning calculates the capacities consumed by existing WIP schedules and purchased supplies and allocates the remaining capacity to new planned orders. All-in-one Supply/Demand View Oracle Rapid Planning enables an integrated view of supply/demand orders and their associated pegging.10. These exception messages include “Orders with Insufficient Lead Time”.15.1 and 12. Rapid Planning searches for the entire supply chain for item substitutes. Integration with Advanced Planning Command Center Oracle Rapid Planning comes with pre-built integration with Advanced Planning Command Center. Rapid Planning output is constrained by purchasing.3. 3. In a single view. Rapid Planning can automatically search for and find alternates and substitutes across the supply chain and create planned orders to meet demands on time. The unconstrained plan output can optionally respect the planning time fence to allow planners to freeze the plan for the initial period. by resource calendars and capacities. 3. They can then retrace the steps back to original state of the supply/demand view 3. Unconstrained Planning Planners can run Rapid Planning in an unconstrained mode. Rapid Planning unconstrained planning can also calculate resource requirements to generate resource usage and resource overload data. Rapid Planning plans can be archived. problems with specific demands are highlighted by the exception messages for sales orders and forecasts at risk due to material shortages or resource shortages. In addition. When the primary supply source is late. alternate organizations. Constrained Planning Rapid Planning offers a full set of constrained planning features. Rapid Planning constraint based planning includes the ability to search among many alternate supply types. The Advanced Planning Command Center’s Supply Chain Analyst dashboard supports drill-down directly into the Rapid Planning Application. published to Advanced Planning Command Center.2.7. All Rapid Planning Simulation plans can be used in the Process Automation functionality to build process flows in Advanced Planning Command Center. distribution and transit lead times.8. Rapid Planning performs simultaneous material and resource capacity constraint based planning. Constrained planning allows planners to automate many types of planning decisions and focus on the critical issues.2.9. Users can also focus an a single order upstream or downstream and then reverse direction to look at the “where-used” or the opposite views.2. “Resource Overloaded”.15. The unconstrained option allows planners to see the required material availability and resource capacity to find what needs to be arranged in order to meet all demands on time.2 Release Content Document Oracle Rapid Planning 96 . and by supplier capacity.

1 and 12.2 Release Content Document Oracle Rapid Planning 97 .14. if the forecast is a weekly forecast. The forecast consumption features allow the planner to include both forecasts and actual sales orders without double counting demand. During plan definition. Rapid Planning performs forecast consumption and allows the planner to optionally explode forecasts. This allows the planner to accept aggregate (weekly or period) forecasts and more accurately plan supplies in daily buckets.15. Sourcing rules and bills of distribution specify date–effective sourcing strategies. The planner can use pegging to trace component or resource problems up to the affected sales orders.11. combining replenishment sources with source rankings. categories.15. allowing the planner to easily compare results from two different plans using different demand prioritization approaches. Alternatively. For example.2. Demand and Supply Pegging Rapid Planning pegging links supplies to demands so that the planner can easily identify demand impacts when supply dates change. the planner can choose to spread the forecast to daily buckets and also optionally set the forecast consumption forward and backward day controls. Supply Chain Sourcing Rapid Planning is compatible with the sourcing rules. Oracle Demand Planning integration to Oracle Rapid Planning is not supported.12.2. 3. The most urgent demands have the best chance of being satisfied on time. Pegging also enables the planner to identify which supplies are linked to critical demands and ensure that those supplies remain on schedule. the planner can select forecast spreading option. Demand priority rules control the sequence of demand priorities assigned to all demands. Respect Demand Priority Rules Demand priority rules can be specified at the plan level. Planners can select the enforce demand time fence plan option and forecasts inside the demand time fence are not included as demands in the plan. Sourcing rules and bills of distribution determine the movement of materials between organizations in your global enterprise.suppliers. Demand Forecasts Rapid Planning utilizes forecast and demand data from Oracle Demantra. 3. Rapid Planning can use externally specified demand priorities for sales orders and forecasts. If Rapid Planning selects an alternate Oracle E-Business Suite Releases 12. Rapid Planning can select primary or alternate sources depending on supply constraints to provide the best demand satisfaction dates. 3. bills of distribution and assignment sets used by Oracle Purchasing or upload supply chain sourcing definitions via file loaders. 3.15.2. Users can flexibly assign sourcing rules to individual items. alternate resources and substitute components to locate the supply source that provides the delivery date closest the demand due date. these organizations include your suppliers and the materials include those items made at the manufacturing organizations. organizations and regions to define the complete supply chain from suppliers to customers.13.2. alternate BOM and routing.15.

The supplier capacity calendar also governs how the supplier processing time is calculated. Users can also enter item-supplier specific order modifiers. Bills of Material and BOM Effectivity Rapid Planning is integrated with Oracle BOM or you can upload bills of material and routings via file loaders. You can order material and plan resources that you need for new revisions ahead of time. If alternate bills of material are specified. Rapid Planning also uses existing WIP standard and non-standard job by-products and co-products as available supply. By-products and Co-products By-products and co-products specified on the BOM are evaluated by Rapid Planning. Rapid Planning can allocate planned orders based the constraints of the suppliers. The planning engine will calculate component requirements based on the BOM effectivity date and also considering component effectivity dates.2.2 Release Content Document Oracle Rapid Planning 98 . New planned orders include by-products and co-products which can be used as supply available on the completion dates. You can Oracle E-Business Suite Releases 12. 3.2.1 and 12. then the selection is reported by the exception message “Order Sourced from Alternate Facility”. Rapid Planning respects BOM effectivity dates. Substitute component selections are reported by the exception message “Planned Order uses Substitute Component”.2. 3.15. 3.2. If the order is sourced from an alternate supplier. It supports single-level and multi-level bills of material. then the alternate bill may be recommended if there are supply constraints on the primary bill of material and routing. Rapid Planning recognizes the item-supplier specific parameters and applies them as sources of supply are evaluated to find supply that meets a demand on time. Planned orders are assigned supplier sources in respect to their capacity.18.15. Rapid Planning recognizes and recommends substitute components when primary components are delayed or not available. 3. then the selection is reported by the exception message “Order Sourced from Alternate Supplier”. The supplier capacity calendar governs how supplier capacity is accumulated over a period of time. Supplier capacity is only accumulated on the working days according to the supplier capacity calendar.15.17. Routing Operation and Resource Scheduling Rapid Planning constrained planning respects resource capacity and schedules new planned orders and existing discrete jobs to avoid resource capacity overloads. alternative sources are used. You can specify item-supplier lead times and supplier capacity calendars.16. Rapid Planning evaluates the engineering change orders as of their scheduled effective date.organization to source an order. Supplier Capacity You can specify time–phased capacity of individual suppliers to specific items in Oracle Purchasing or upload supplier capacity via file loaders. Alternate bills of material selections are reported by the exception message “Planned Order uses Alternate BOM/Routing”.15. Rapid Planning uses the ranking information you specify in sourcing rules and first attempts to source the planned orders with the primary sources.15. If the capacity to fulfill the demand is not available.

Planners can select certain bottleneck resources to perform constrained planning. Rapid Planning also chooses alternate routings when required because of constraints on the primary BOM and routing. Order Modifiers Rapid Planning includes the user specified order modifiers at the item organization level and creates new planned orders respecting the order modifiers. maximum order size. 3. When item substitutes are selected. Lead Times and Planning Time Fence Rapid Planning respects manufacturing and purchasing lead times. Rapid Planning respects prior and next operation scheduling controls.1 and 12. users can specify supplier specific order modifiers which are respected by Rapid Planning when creating new planned orders sourced from the supplier. Rapid Planning respects planning time fences defined at the item organization level which allows the user to freeze the schedule during the initial periods of the plan.15. Order modifiers respected include minimum order size. Resource efficiency and utilization are used by Rapid Planning resource requirement calculations. 3.15. resources and resource capacity in Oracle BOM or upload via file loaders.define routings.2.21. fixed order quantity. End Item Substitution Rapid Planning uses end item substitution rules to find acceptable substitute item supplies when the requested item is not available for the demand request date. processing and post-processing lead times. Additionally. Users can set preprocessing. Rapid Planning creates schedules that do not overload the selected bottleneck resources and reports overloads on the non-bottleneck resources. Rapid Planning constraint based planning respects these lead times. Oracle E-Business Suite Releases 12. You can specify simultaneous resources and set the maximum assigned units for each resource requirement to control scheduling results. 3. If you can specify alternate resources. Rapid Planning respects routing effectivity dates. This allows the planner to focus on the critical bottleneck resources.15. Rapid Planning selects alternates and schedules around constraints on primary resources to meet demands on time.2 Release Content Document Oracle Rapid Planning 99 .19.20. fixed lot multiplier and round order quantity. Resource requirements are generated using routings which are effective on the start date of the planned order. Substitution is based on user-defined rules that can be effective either in one direction or in both directions.2. Customer specific item substitution rules can also be specified which are respected by Rapid Planning when searching for supplies for that customer’s demands. defining a chain of substitution relationships. Alternate selections reported with the exception messages “Planned Order uses Alternate Resource” and “Planned Order uses Alternate BOM/Routing”. Rapid Planning alerts the planning with the exception message “Demand Satisfied Using End Item Substitution”.2. Other resources are planned in an unconstrained mode using the resource lead time during scheduling.

2. The receiving calendar governs the receiving activities at the organizations or customer sites that receive goods.15. the planner can pull in or push out the new planned orders and selectively firm the planned orders. The carrier calendar indicates the working and non-working days and times for material that is in transit using different means of transport. This creates an inventory buffer to protect against fluctuations in lead time. Rapid Planning schedules each type of supply or demand considering the working and non working days in the appropriate set of calendars. and supply (for example.2. Shipping. When required. The planning engine allows organizations to receive shipments only on a working day. the planner can pull in or push out the existing supply and firm it. demand (for example. Safety Stock Lead Time Rapid Planning considers safety stock lead time that is user controllable at the item organization level. 3. Planners can adjust recommendation due dates and then release the new planned orders or the reschedule of existing planned orders Oracle E-Business Suite Releases 12.22.25.24. and shipment to customers.3.15. When required.15.2.26. Planners can selectively release planning recommendations or choose to release all recommendations. certain methods of shipment such as parcel carriers may not work on weekends. and customer facilities may be able to ship or receive goods on specific days. variable supplier lead times and irregular operation yields) 3. 3. Release New Planned Orders and Reschedule Recommendations Planners can easily release recommendations from Rapid Planning to execution systems. inter facility shipments. Planner Action: Firm Planned Supplies Planners can review new planned make and buy orders while comparing to the pegged demands. The shipping calendar indicates the valid working days for shipment activities originating from suppliers and organizations. Each of these activities is controlled by a set of calendars. The planning engine does not recommend a shipment out from those facilities if the date is a non-working day. Manufacturing.2. 3. For example.23. You use it to instruct the planning engine to schedule supplies in advance of the demand due dates that peg to them. Receiving and Carrier Calendars Rapid Planning plans a variety of supply chain activities like manufacturing. This may cause the transit time to be stretched over the weekends. forecast error). Planner Action: Firm Existing Supplies Planners can review existing WIP jobs and purchase orders while comparing to the pegged demands. Safety stock lead time is a lead time that you add to the normal lead time of make and buy items.2 Release Content Document Oracle Rapid Planning 100 . Rapid Planning respects the firm flag by not changing the schedule dates and by consuming material and resource capacity before scheduling non-firm supplies. Rapid Planning reports any overload situations caused by firm planned orders.2. purchases.15. Rapid Planning reports any overload situations caused by firm supplies. Rapid Planning respects the firm flag by not changing the schedule dates and by consuming material and resource capacity before scheduling non-firm supplies. supplier.1 and 12.15.

Rapid Planning release processes are fully integrated with Oracle Purchasing and Order WIP.2. 3. Exceptions Rapid Planning generates the following 24 exception types. these selections are also be released as part of the make order. Search criteria can be saved with a user specified name for future use.27. Within an exception type. Rapid Planning allows the user to specify the auto-release of planned orders within the release time fence. Users can set the release time as the item organization attribute. • • • • • • • • • • • • • • • • • • • • • • • • Past Due Sales Orders Late Replenishment for Sales Order Late Replenishment for Forecast Demand Quantity Not Satisfied Resource Overloaded Exception: Supplier Capacity Overloaded Items with a Shortage Items below Safety Stock Items with Excess Inventory Past Due Orders Orders to be rescheduled out Orders to be cancelled Orders to be rescheduled in Order with Insufficient Lead Time Sales Order/Forecast at Risk due to a resource shortage Sales Order/Forecast at Risk due to material shortage Late Supply pegged to Forecast Late supply pegged to Sales Order Planned Order uses alternate BOM/Routing Planned Order uses Substitute Component Planned Order uses Alternate Resource Order Sourced from Alternate Facility Order sourced from Alternate Supplier Demand Satisfied Using End Item Substitution Exceptions are generated only when a plan run has completed.1 and 12.15. Auto-release of planned orders occurs immediately after the Rapid Planning plan processes complete. The release processes also allow for integration to third party systems. Users can choose to enable or disable the display of specific exception types.New planned make orders are released with an alternate BOM/Routing recommendation.2 Release Content Document Oracle Rapid Planning 101 . and are displayed within the "Exceptions" view in Rapid Planning. users can specify search criteria or filters to specify the exceptions that must be displayed. If Rapid Planning selects substitute components and alternate resources. and specify their arrangement within the Exceptions view through a configuration mechanism. and are not regenerated when manual edits are made to a plan. Oracle E-Business Suite Releases 12.

The view tells the planner what material and resource constraints caused the demand to be satisfied late. exceptions for the base plan and compared plan for an exception type are displayed in adjacent tabs. In a Plan Comparison mode. associated filter conditions.2. Quantity.28. Late Demand Diagnosis Rapid Planning generates. etc) for the supported exception types as metrics. navigation to other related Rapid Planning views has been provided in context of the exception’s attributes (Item. Rapid Planning can display the following plan metrics: • • • • • • • • • • • • • • • Stock Outs (in days) Fill Rate (%) Inventory Turns Safety Stock violations (in days) Revenue Gross margin (%) Manufacturing Cost Purchasing Cost On Time Orders (%) Resource Utilization (%) Supplier Capacity Utilization (%) Clear to Build (% of orders) Clear to Build Component Availability(%) Ready to Build (%) Top N Shortage Components (%) In addition to the above metrics. Rapid Planning can also display different facts (Count. Exceptions generated in Rapid Planning can be exported to MS Excel for further analysis.15. 3.From an exception. Now Late”) are provided. Org.1 and 12. Selection of the metrics that must be displayed. and their layout within the Analytics view can be configured at a user level. The name of the exception type also has the name of the associated plan to easily identify which plan the listed exceptions belong to. When Plan Comparison is enabled in Rapid Planning. as well as an assessment of how severe each constraint is. 3. root cause information that can be viewed in a new Constraints view. Value.29. values from both the base and the compared plans are shown together for easy visibility and comparison.15.g. Oracle E-Business Suite Releases 12. Search capabilities are also provided to restrict the comparison to a user defined selection. To easily compare end demands planned differently across the base and compared plans.2 Release Content Document Oracle Rapid Planning 102 . seeded comparison mechanisms (e. Resource. Embedded Analytics KPI’s/Metrics are displayed in Rapid Planning in a separate “Analytics” view. for each late demand. etc). The Analytics view also enables the comparison of end order satisfaction across two plans within an Order Comparison region. “Was On Time. their display levels.2.

Model forecasts are exploded to option. 3. substitute components on bills of material. Rapid Planning can also optionally explode the forecast for the top level model.2. demand class. Rapid Planning can accept forecasts for assemble to order (ATO) models and pick to order (PTO) models as demand schedules. alternate sources on sourcing rules. 3. Supplies are scheduled and created as needed for all lower levels. requested quantity. alternate bills of material and routings.31. Configured sales orders consume the model and lower level forecasts. Forecast distribution is performed in an unconstrained manner based on the user defined percentages in the sourcing rules. Rapid Planning will report the following types of constraints: • Material Constraint o Lead Time Constraint o Planning Time Fence Constraint o Date Effectivity Constraint o WIP Window Constraint Resource Constraint Supplier Constraint • • These constraints will be reported along all alternate paths: alternate resources on routings. This is done in Oracle Demand Management.15.2. and end item substitutes. You can choose a ship-to consumption level in Rapid Planning. Each constraint will have information such as requested date. Rapid Planning will plan for the unconsumed model. Forecasts can have reference to ship-to entities such as customer site and zone. You can use sourcing rules to distribute consumed global forecasts to appropriate shipment organizations. Single level and multi-level ATO models are supported by Rapid Planning. option and option class forecasts as well as planning for the configured items. You can provide pre-exploded forecast values of your ATO and PTO models and components to Rapid Planning. option class and component forecasts within Rapid Planning using the 'Explode Forecast' plan option.1 and 12.2 Release Content Document Oracle Rapid Planning 103 . Rapid Planning issues exception messages when a distributed forecast demand at an organization cannot be met on time by supply in that organization. Configured to order sales orders consume model forecasts at each level of the multi-level model. After forecast explosion. zone (global forecasts). customer site.15. Configure to Order Rapid Planning supports configure to order environments.For every late demand. shortage (both in absolute quantity and percentage terms) so that planners can immediately see what actions to take to resolve each late fulfillment of a demand. Global Forecasting Global forecasting allows you to define forecasts without the context of a shipment organization. ATO and PTO forecasts from Oracle Demand Management and EBusiness Suite R12 and R11i10 are supported. available quantity. Rapid Oracle E-Business Suite Releases 12. and item organization.30. Rapid Planning supports forecast consumption at various levels such as customer. Multi-level ATO models include models at lower levels of the BOM structure.

to net existing supplies of pre-configured stock at any supply chain bill of material level. Customer Site. A forecast for a lower level ATO configuration that will be stocked will be consumed by a sales order for the top level configured model. Rapid Planning will consume the forecast for this specific configuration first. and Zone. Rapid Planning plans only consider ATO sales orders after they have been progressed to include a linked configured item. For example. Users can override the default order sizing algorithm by specifying a new itemorganization attribute called planning unit of work. The global forecasts can be consumed at different levels such as Global (Item). 3.32. In the absence of order modifiers. For example.15. Rapid Planning allows you to plan based on the aggregate capacity of the supplier-supplier site to build the base model. Default order sizing is only applied to new planned orders and does not affect the quantity of an existing supply. Rapid Planning reduces the order size to fit within the remaining capacity in a day.1 and 12. A supplier capacity statement for the ATO model is consumed by the ATO items that are created based on this model. User can set the planning unit of work to larger than daily capacities and Rapid Planning will create new planned orders that typically span several days up to the specified planning unit of work. set planning unit of work to 8 hours and the resulting new planned orders will not exceed 8 hour shifts in duration.2.for example. Default Order Sizing Rapid Planning provides support for default order sizing to improve scheduling results. Customer. Oracle E-Business Suite Releases 12. Multi-level multi-organization models are supported. Rapid Planning sizes orders to daily production capacity. KPIs illustrating supplier capacity metrics. The user can set planning unit of work to the number of hours for the duration of the maximum order size.2 Release Content Document Oracle Rapid Planning 104 . If you have multi-organization models you must use global forecasting for forecast consumption to be correct. A multi-organization model is one which contains top level or some lower-level models which are transferred between organizations. Smaller order sizes improve scheduling flexibility which leads to higher fill rates and on time supplies. then all order sizes equal fixed order quantity without regard to the planning unit of work. Organization. The default order sizing does not override existing item-organization order modifiers. as well as exception messages are provided to help you make an informed decision.Planning will consume and plan supplies for the unconsumed forecast demand at each level. When some capacity is consumed on a day. For procured configurations. if the fixed order quantity is specified. Rapid Planning distributes global forecasts for ATO and PTO models across organizations based on the user-specified sourcing rule percentages. Any remaining demand will then consume the forecast for the associated ATO model. This allows Rapid Planning to schedule these sales orders with all the capabilities provided for standard items .

33.2.15. Inventory Reservations Rapid Planning recognizes on hand inventory reservations to sales orders. “Clear to Build Date”. WIP job. You can export consensus forecast data from Realtime Sales and Operations Planning to Rapid Planning plan. Equivalent KPIs can be configured to view these attributes at aggregate levels. Selectively de-prioritize certain make orders from allocation of on-hand – these selected orders will be given lower priority when on-hand is allocated to Make Orders in the next plan run. Clear to Build A make order (planned make order. Rapid Planning – Sales and Operations Planning Integration Rapid Planning plans will be visible in Demantra Real-time Sales and Operations Planning.) is “Clear to Build” if all its component requirements are pegged to on-hand supply. Reservations for both full and partial demand quantities are supported.2. these make orders could potentially contribute to the improvement of the clear to build status of the target orders. The dashboard allows a user to: • • • • • Search for the make orders for which the user wants the Clear to Build status to be improved. “Ready to Build %”.1 and 12.35. Prioritize specific make orders for Clear to Build – this results in on-hand being allocated to these make orders preferentially when the plan is launched next. View how a specific component is allocated to multiple make orders. The Clear to Build status on make orders are visible through new order level attributes: “Clear to Build Status”.3. In the case of a partial reservation. 3.2. The on hand supply that is reserved to a sales order cannot be used for any other demand. etc. View contentions for selected make orders – contentions are other make orders that share common components.15. This data from the Rapid Planning plan will now be visible in Real-time Sales and Operations Planning worksheets. Rapid Planning provides visibility to the Clear to Build status of Make Orders. both at the individual make order level as well as at aggregate levels through new key performance indicators (KPIs). each sales order demand includes a new field which displays the quantity of on hand inventory that is reserved to the sales order. Rapid Planning also allows user to control allocation of scarce on-hand component supply to make orders by explicitly prioritizing or de-prioritizing specific make orders.34. Rapid Planning generates pegging of on-hand supply to sales orders that matches the reservations recorded in the source transaction system.2 Release Content Document Oracle Rapid Planning 105 . and “Clear to Build Component Availability %”. Oracle E-Business Suite Releases 12. The integration between Rapid Planning and Real-time Sales and Operations Planning is similar to the existing Advanced Supply Chain Planning to Real-time Sales and Operations Planning integration. Rapid Planning schedules supplies for the unreserved quantity of the sales order. This can be achieved through a new Rapid Planning view called the Clear to Build Dashboard. and prioritize or de-prioritize make orders for on-hand allocation based on this component allocation view. 3.15. In the supply and demand window. You can read the supply data from a Rapid Planning plan back into Real-time Sales and Operations Planning.

GOP accords the highest preference to supply from a Rapid Planning plan. 24 by 7 ATP is not enabled against Rapid Planning plans.38. Multi-Planner Collaboration Rapid Planning allows a user to save changes made to data in Rapid Planning to a simulation set. or sales orders at specific organizations.15. Order Comparison In a Plan Comparison mode. o Organization: Here.2.2. Functional and Data Security This enhancement provides Rapid Planning with: Functional Security • This is the ability to dictate which functions (Create. Planned Orders.37. This avoids inconsistencies between the current output of the Rapid Planning plan and the version against which GOP is promising orders.) will not be visible within the Rapid Planning plan itself. Rapid Planning’s Analytics view now has an additional tab that displays “Order Comparison. Any Rapid Planning plan that is enabled for ATP will not be editable. When the base plan is launched again with reference to this simulation set. Rapid Planning – GOP integration allows an enterprise to react quickly to unforeseen events.1 and 12. Load. and Release) a responsibility should have access to. and which demands have increased or decreased their lateness in the comparison plan versus the base plan.2. Delete. Close. Users can view which demands were planned on time in the base plan. A user can save a specific record.15. by enabling quick integration between planning simulations and the order promising process. Data Security • Data access can be controlled at two levels. you can assign organizations to a responsibility.2 Release Content Document Oracle Rapid Planning 106 . 3. but are delayed in the comparison plan and vice versa. 3. Also. Then. 3. If there are a mix of ASCP and Rapid Planning plans that have supplies for an Item/Org.15. all the user changes will be considered in the next version of the Rapid Planning plan.3. Update / Edit. sales orders for specific items.39. The supply from this plan is considered by GOP when promising orders if GOP is set up to promise orders against a plan output. Copy. Save.15.2. Multiple planners can thus work on simulation copies of a base plan and save the results of their simulation to a common simulation set. or changes across multiple Rapid Planning views to a named simulation set through a single click action. Rapid Planning – Global Order Promising Integration Rapid Planning plans can now be used by Global Order Promising (GOP) to promise orders. Launch. any inserts that GOP makes into the plan (Sales Orders. multiple records within a Rapid Planning view. A search region allows users to query up only sales orders of interest – for example.” This allows users to compare demand satisfaction of sales orders across two plans intelligently. etc. users with that responsibility will have access to (i) all Plans in Oracle E-Business Suite Releases 12.36.

15. In the example illustrated above.1. Plan: A user creating a plan can mark the Plan as Private or Public.3. a demand is initially committed for week 7. but guarantee promise date / commit date. This feature enables Rapid Planning to better utilize excess inventory and potentially improve fill rates. the earlier commit date is preserved. It lets planners improve responsiveness by providing the ability to improve to request date. revised Request Dates from customers. In the cases where it cannot improve the earlier commit date. Oracle E-Business Suite Releases 12. by all users) provided they have the necessary Organization level security granted. In case of Private plans.including preserving the supply allocation (pegging). However. If the customer comes up with a request to satisfy the demand by week 2.15. This enables planners to maximize revenue by trying to meet new. as a result.3 3. A Private plan is only accessible by specific users to whom access has been granted (access is granted by the user who created the plan and marked it as Private). users will have access all items and organizations within that plan.1 and 12. Release 12. A Public plan is accessible by all responsibilities (and. 3. There is excess inventory from weeks 3 to 6. in this case week 3.o which the organizations exist and (ii) all items within those organizations. Rapid Planning will now try to satisfy the demand on the feasible date closest to the new request date. Rapid Planning generates two new exceptions: • Late Replenishment for a Pull-in Sales Order/Forecast: Generated whenever any partial quantity of the demand is met after the revised demand date.3. Demand Pull-In and Upside Processing This feature allows Rapid Planning to seek to improve on the fulfillment date of a demand while guaranteeing that no previously committed date for any demand will be made any worse.3.2 Release Content Document Oracle Rapid Planning 107 . Rapid Planning can now plan considering multiple dates with different priorities on a single demand. fall back to previously committed dates . the actions the user can take are controlled by the Function Security of the user’s responsibility. but when they cannot.1.

both the above exceptions will be generated for that demand. Value. single-click navigation to Material/Resource Plans. Days. Quantity by Revised Date) Forecasts Pulled-in (Count. Users can use any of the following measures to create these dynamic lists • Fill Rate % Oracle E-Business Suite Releases 12. resources and suppliers and save them as favorite lists that can be used later as a shortcut to all the related information about those items. Quantity) Late Replenishment for a Pull-in Forecast (Count. resources or suppliers. For example. Users will then see the resultant list based on the plan. Exceptions. assembly. accessible across plans. This will enable navigation to the Material Plan that places items in supply chain bill order: for example. Users can have multiple named lists per user.1 and 12. Value. Rapid Planning also generates the following new measures for analysis that users can use to create graphs in the analytics tab of the Rapid Planning workbench. Quantity) Sales Order Pulled-in (Count. Quantity by Demand Date.• Sales Order / Forecast Pulled in: Generated whenever the demand is satisfied prior to the original demand satisfied date. Dynamic Lists Users can also create lists based on certain conditions that then construct the list dynamically every time. If a demand is partially met on a revised demand date and partially met on the earlier commit date. 3.2. resources and/or suppliers by saving to a favorite list from other views in the workbench including Items. Value. Quantity by Revised Date) Based on the successful pull-ins. Value. Static Lists Users can create a list with an enumerated list of items. Supplies and Demands for multiple items. Users can organize the order of the list to reflect supply chain structure by using move up/down actions. resources or suppliers. • • • • Late Replenishment for a Pull-in Sales Order (Count.3. Favorite Lists This feature allows users to create user-defined lists of items. then components. planners can now also release the changes to sales orders from the workbench to the source system's Order Management application to send the updates to quantity and the scheduled ship date. sub-assembly. and Supplies and Demands. users can create a list based on a condition like 'Bottom 10 items based on fill rate %'. They can access the lists from the left navigator pane and drill using an easy. Suppliers. Days. Resources. Based on the above two exceptions.15.2 Release Content Document Oracle Rapid Planning 108 . Quantity by Demand Date.

15. users also have the option to input a non-time phased safety stock quantity for each item using a new item attribute called 'Target Safety Stock Override'. it is displayed in terms of quantity by converting the safety lead time into safety stock quantity (not time phased) using the formula above. Users can enable this behavior of deriving the safety stock lead time from the quantity (instead from the safety stock %) using a new plan option called Safety Stock Lead Time Method. Oracle E-Business Suite Releases 12. It also lets planners use time-phased safety stock quantity (units) as input to calculate the safety stock lead time. Resource or Supplier. Organization.• • • • • • • Inventory Turns On time Orders % Late Replenishment for Sales Order / Forecast (value) Demand Quantity not Satisfied (value) Resource Utilization % Supplier Capacity Utilization % Purchasing Cost Users can create these dynamic lists by creating a metric in the analytics tab using any of the above measures with any of these applicable dimensions ("view by") .3. It also provides an easy to understand view of supply and demand that includes the safety stock (target and actual) expressed in quantity (units). The safety stock lead time is calculated from the safety stock quantity using a simple formula: Safety Stock Lead Time (Days) = Avg (Safety Stock Quantity) / Avg Daily Demand in the Plan The material plan displays two additional measures: • • Target Safety Stock: This is the time-phased safety stock quantity that is defined by the user or collected from a source system. In addition to the above. 3. Actual Safety Stock: This is the safety stock quantity that the plan has planned for. This enables Rapid Planning to be easily integrated with other applications that generate safety stock quantity in units.Item.2 Release Content Document Oracle Rapid Planning 109 . Safety Stock Enhancements This enhancement enables users to view an item’s safety stock profile in quantity (units) even though the planning was done using a safety stock lead time approach. Though the plan has actually planned using a safety lead time approach.1 and 12.3.

Simulation Edits of Approved Supplier Lists and Supplier Capacity Users can now do what-if simulation based on attributes of Approved Supplier Lists and Supplier Capacity as listed below. Edits to Demand Time Fence Days and Release Time Fence Days are only applicable in plan inputs mode using simulation sets. Decrease by. However.5. The impact of these user changes on the time fence attributes and the cost/price attributes can be seen (after running the plan) on exceptions such as ‘Orders to be Rescheduled In’ and measures such as Revenues and Gross Margin.15. Set Value To. Reset to Original. Increase by %.15. • Approved Supplier List attributes o o o o • Processing Lead Time Min Order Qty Fixed Lot Multiplier Supplier Price Supplier Capacity attributes o o o From Date To Date Capacity Users can simulate changes to these attributes in a specific plan or as part of a simulation set that can be used across plans.1 and 12.3.3.2 Release Content Document Oracle Rapid Planning 110 .4.3. Decrease by %. Also this is still applicable only for global Approved Supplier Lists: any update to a single org propagates to all orgs. For all the above attributes users can use the standard mass update features like Increase by. users cannot add a new Approved Supplier (Item-Supplier) entry that does not already exist. Simulation Edits of Additional Item Attributes Users can now do what-if simulation based on more item attributes listed below: • • • • • • Planning Time Fence Days Release Time Fence Days Demand Time Fence Days Selling Price Standard Cost Discount % Users can edit these and see the impacts on plan recommendations and cost metrics after running a simulation. Oracle E-Business Suite Releases 12. 3.

This lets users to do actions like firm all Sales Order demands for an item to their respective request dates in a single update even though the dates are all different.15. 3.Users can view the impact of these simulation changes in all related measures. Users can copy (duplicate) an existing operation or activity and edit any of the following attributes to either create a new operation and/or activity in that operation.3. These mass update actions are available in both plans and plan inputs. All Date operations in this mass update are based on calendar (24x7) days and not working days. 'Increase by'.3. 'Request Date+' and 'Suggested Due Date+'. users cannot create new routings.15.2 Release Content Document Oracle Rapid Planning 111 . mass updates to To Time also support the relative date/time operator 'From Time+'. This takes a positive or a negative number (say 'n') and sets the To Time to 'n' hours relative to the From Time. These mass update actions are available in both plans and plan inputs. The last two operators take a positive or a negative number (say 'n') and set the Firm Date to 'n' days relative to the Request Date or the Suggested Due Date. For example. Oracle E-Business Suite Releases 12. This lets users to do actions such as ‘shorten all shifts in a week by 1 hour’ in a single update even though there are multiple shifts with different To Time's.3. Mass Update Enhancements for Firm Date on Demands and Supplies Mass updates to the field Firm Date now support additional operators: 'Decrease by'.7. Mass Update Enhancements for Resource Availability Mass updates to the fields From Time and To Time now support additional operators: 'Decrease by' and 'Increase by'. a what-if change to supplier price impacts related purchasing metrics. The following attributes of the routing operations and activities can be updated: • • • • • • Disable Date (operation) Effective Date (operation) Operation Yield Resource Assigned Units Rate or Amount Users can use these attributes to simulate changes to their manufacturing processes in a specific plan or as part of a simulation set that can be used across plans.15. Whenever the action results in the To Time being earlier than From Time.6. 3. 3. Simulation Edits of Processes Users can now do what-if simulation based on changes to their manufacturing processes (routings). it will be interpreted as a shift ending the next day.8.1 and 12. In addition. However.

3. and profile option (4) above controls the display of all Oracle E-Business Suite Releases 12. in the Material Plan and Resource Plan views. This lets users to structure the Material Plan views in the same order as their supply chain structure starting from the assembly all the way down to the components. Here is the list of profile options and the types of fields they control. In addition. plans in Rapid Planning could be launched only in interactive mode.15. 3.3. Bill of Materials.). the 'Starts With' and 'Contains' operators. users have the option to either calculate the lateness constraints or not.15. the Material Plan is displayed in the order of the categories corresponding to the sorted selected items. The search operators will now include. Material Plan Display Order This enhancement supports display of Material Plan in a user-defined item order. Display of Decimal Precision This feature enables users to have control on the maximum number of decimal digits displayed for different types of numeric fields displayed in the workbench using a set of responsibility-level profile options. these two fields Item and Resource have a new 'Among' operator where users can select multiple items or resources to be displayed in the results.9. Plans launched in this mode are always launched with refresh snapshot. • • • • • • MSC: Max display decimals for Quantity MSC: Max display decimals for Time MSC: Max display decimals for Quantity (aggregates) MSC: Max display decimals for Time (aggregates) MSC: Max display decimals for Currency MSC: Max display decimals for Ratios/Percentages Profile option (3) above controls the display of all aggregate quantities especially in the Material Plan and in Analytics. Supply and Demand. If the default Material Plan layout for the user is set to Category or Category-Org.3. close the plan (in which case it would not be immediately available for simulation). apart from the standard 'Equal To' operator. The sequence of items listed in the Material Plan will be derived from the sort order seen in the view that the user is coming into the Material Plan from (including Favorites List. 3. Enhanced Search Capability This enhancement enables additional search operators for fields Item and Resource in all views. Items.15.10.15. 3.11. Scheduling Rapid Planning Runs in Batch Mode Prior to this release. and Exceptions.3. or do nothing (keep the plan available for simulation). and to save the plan (to the database).1 and 12. This feature lets users to schedule the Rapid Planning plan run in the background using a new concurrent program “Launch Simulation Planner”.12.3. While launching this program.2 Release Content Document Oracle Rapid Planning 112 .

aggregate time/hours in the Resource Plan and in Analytics. The rest of the profiles control the display of decimals in all other views for the type of fields indicated above. These profiles are only for display purposes and do not control the precision of the internal values or the editable decimal precision. 3.15.3.13. Last Saved Information for Plan Options The plan options window now displays the fields Last Saved By and Last Saved Date to indicate who last updated the plan and when the plan was last updated. These fields are also updated when a plan is run with the details of time of plan run and the user that ran the plan. 3.15.3.14. Blow Through Phantom Items in Clear to Build The Clear to Build workbench’s Component Allocation View has been enhanced to display the actual components required by a make order by blowing through the make item’s phantom sub-assemblies. This provides visibility into the real component requirements for the make order and allows the user to reallocate scarce component availability as required. 3.15.3.15. Global Forecasting Display in the Material Plan Global forecasting allows you to define forecasts without the context of a shipment organization. You can use sourcing rules to distribute consumed global forecasts to appropriate shipment organizations. Forecast distribution is performed in an unconstrained manner based on the user defined percentages in the sourcing rules. With this release of Rapid Planning, the Material Plan has been enhanced to display global forecasts. This provides users with the ability to view the original global forecast quantities, forecast consumption and the distribution of the global forecasts to specific organizations. The Material Plan view of global forecasts also shows the spreading of forecasts to the various time buckets. 3.15.3.16. Auto-release of Planning Recommendations Rapid Planning now supports the auto-release of new planned orders. This is controlled with a new plan option, “Enable Auto Release.” Users can set the release time fence by editing an item-organization attribute. Rapid Planning will automatically release new planned orders when the suggested start date is inside the release time fence. Rapid Planning also supports the auto-release of reschedules and cancelations. This is controlled with a new plan option, “Auto Release Reschedules.” The release time fence item attribute also determines when auto release of reschedules and cancelations is performed. Simulation planning in Rapid Planning has been enhanced to work seamlessly with the release of planned orders and reschedules. If recommendations are released, the simulation plan ‘remembers’ what was released and does not create duplicate supplies. As planners release planned orders and then simulate new conditions, the plan has a record of what has already been released. The simulation plan treats the released plan orders as firm supplies.

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

Oracle Rapid Planning

113

3.15.3.17. Natural Time Fence Rapid Planning now supports the natural time fence. A new plan option called Create Time Fence has been provided in the Advanced tab of plan options. When checked, the planning engine will evaluate existing firm supplies for an item and use the latest completion date as the new planning time fence date for the item. This allows the planner or the shop floor scheduler or purchasing agent to firm a schedule of supplies, and new planned orders will not be created earlier than the firmed supplies. Two additional profile options are provided in the Advanced tab to extend the use of the natural time fence. The option Firm Planned Order Time Fence instructs the planning engine to create a natural time fence on the completion date of the latest firm planned order. The option Firm Internal Requisition Time Fence instructs the planning engine to create a natural time fence on the completion date of the latest firm internal requisition.

3.15.4.

Release 12.2
There are no new features in Oracle Rapid Planning in Release 12.2.

3.16. Oracle Service Parts Planning
3.16.1. Product Overview
Oracle Service Parts Planning (SPP) brings advanced multi-echelon supply chain planning to a service supply chain consisting of internal warehouses, emergency stocking locations, internal repair depots, external repair vendors, and external new buy vendors. Oracle SPP is a new product dedicated to the service parts planning domain. It offers an integrated forecasting and replenishment planning workbench, planning logic dedicated to the unique characteristics of the service parts planning domain (such as reverse logistics, multiple part conditions, and part supersession), and seamless integration to Oracle Supply Chain Management and Oracle Service (Spares Management and Depot Repair) applications to support execution of planned replenishment actions, including external and internal repair.

3.16.2.

Release 12.1.1
3.16.2.1. Integrated Demand and Supply Planning By running a single Service Plan, you can regenerate both the forecasts and the replenishment recommendations (procurement, transfer, and repair) for an entire service supply chain. A service parts planning workbench lets you view and manipulate forecasts as well as transfer, and new buy and repair recommendations and transactions. All demand/supply, exception, item attribute and comments pertaining to a service part are visible in a single screen, creating a very efficient user experience for the planner. 3.16.2.2. Service Parts Planning Workbench In service environments, it is common for planning responsibility to be divided across planners by item, and for planners to analyze, change, and execute plans on an item by

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

Oracle Service Parts Planning

114

item basis. To support this practice, a new SPP screen shows in a single window the following information about an item: • • • • • Values of key item attributes Horizontal supply and demand plan Planner comments relating to the item Exceptions relating to the item Demand history and forecast

The SPP Workbench can display demand and supply information at the level of a single item, or aggregated across multiple revisions of the item’s supersession chain. It can display demand and supply information at a single location, or aggregated across userdefined groups of locations (inventory organizations). 3.16.2.3. Integration to Spares Management for External Repairs SPP plans for repair of defective spare parts at external vendors. Movement of defective parts to the repair vendor, repair lead times and yields at the repair vendor, and movement of repaired (good) parts back to an internal warehouse are considered. The repair vendor must be modeled as an inventory organization. Upon release of a recommendation for external repair, integration with Oracle Spares Management automatically creates the repair purchase order to the repair vendor, the internal sales order to move defectives to the repair vendor, and the underlying work orders necessary to progress the repair through the repair vendor. (Management of the work orders is automatic and does not require user intervention.) Tracking of repair progress is done through a workbench in Oracle Spares Management. 3.16.2.4. Integration to Depot Repair for Internal Repairs SPP plans for repair of defective spare parts at internal repair depots. Movement of defective parts to the repair vendor, repair lead times and yields at the repair vendor, and movement of repaired (good) parts back to an internal warehouse are considered. The repair depot must be modeled as an inventory organization. Upon release of a recommendation for internal repair, integration with Oracle Depot Repair automatically creates the transfer order to move defectives to the internal repair depot, the repair work order at the repair depot, and the transfer order to move the repaired spare parts back to a warehouse. Tracking of repair progress is done through a workbench in Oracle Depot Repair. 3.16.2.5. Support for Part Condition SPP distinguishes between supplies of a single spare part that are of different conditions: good and defective. This allows SPP to recommend appropriate repairs to satisfy demand for good spare parts. 3.16.2.6. Criticality Matrix You can group items into various criticalities on the basis of a flexible number of attributes such as cost, order frequency, reliability, and impact of failure. You can then specify forecasting methods and service level targets by criticality.

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

Oracle Service Parts Planning

115

3. The work list shows the most important to-dos (items to replan.3.2.7. Planner Work Lists SPP can generate a personal work list for each planner that dynamically lists items controlled by the planner that have important exceptions (for example.2. Minimize New Buys SPP exhausts on-hand supplies of substitutable item revisions and options for repair of defective supplies before recommending. Recommendations for repairs will not exceed the forecasted and available supply of defective spare parts.16. SPP can receive supply commits uploaded to CP from new buy suppliers and trigger exception messages when those commit levels are exceeded.10. Supersession Chain-Specific Replanning When a planner is working on a service part in the planner workbench. purchase of new spare parts to satisfy spares demand.) 3.16. The type and severity of exceptions that qualify items for the work list and the type of recommendations that qualify for the work list can be specified by the planner.11.13. Support for Supersessions SPP automatically uses supplies of later revisions of an item to satisfy demand for earlier revisions of the item. new buy orders that need to be released within the next 5 days). Forecasts are automatically created for the latest item revision in a supersession chain on the basis of the combined histories of the latest item revision and all previous item revisions. 3. (The latter date may be well beyond the end of the planning horizon. Returns Forecasts Forecasts of returns of defectives from the field are recognized as supply during the planning process.2.2. as a last resort.2.8.16. Integration with Collaborative Planning SPP supports the publishing of new buy order forecasts to new buy suppliers and repair order forecasts to external repair suppliers.16. Revisions are defined via supersession item relationships in either Oracle Inventory or Oracle Spares Management. recommendations to release) that each planner must take care of at any given time. Oracle E-Business Suite Releases 12. Suppliers can view and respond to these order forecasts through Collaborative Planning (CP). External repair suppliers can also view in CP forecasts of defective shipments to their facilities as planned in SPP.16. late replenishments where the number of days late is greater than 3) and those that have key recommendations (for example. he or she can initiate a quick replan of just the supersession chain involving the part on display.1 and 12.2. This allows the planner to perform adjustments such as expediting repair or purchase orders.16. Life Time Buys When a service part is obsoleted in advance of the end of the useful life of the products that require it for service. SPP recognizes life time buy events as defined in the item attribute simulation set and recommends appropriate 'life time buys' that fulfill demand anticipated to fall between the life time buy date and the end of life date. 3. a last or 'life time buy' must be undertaken. 3.2.9. 3.12.16.2 Release Content Document Oracle Service Parts Planning 116 .

item attributes. normally-distributed demand variability for non-intermittent demands. On the functional side. Multiple planners can therefore work concurrently on the same SPP plan.1. you can now launch multiple processes. it will overlay those plan results on top of pre-existing plan results for other items.16. This will be available both on the Item-Organization and Oracle E-Business Suite Releases 12. with a new item attribute 'Intermittent Demand' added. Scalability of planning calculations is a primary concern.14. This profile determines the number of such processes that are launched in parallel for forecasting. This attribute will be used to specify whether the history pattern is intermittent or not. IO assumes Poisson-distributed demand variability for intermittent demands.2 has an enhanced Item Attribute Mass Maintenance (IMM) form. Release 12.3. While previously a single 'Memory Based Forecaster' process was launched to generate a forecast for all items in the plan. Execution Net Change Planning Service parts planning environments are characterized by high part and location counts. supersession or repair to relationships.3.1 and 12. so that forecasts for different item-chains are generated in parallel. Previously the SPP Forecast Rule screen had an option to specify whether the history data was intermittent or not. Intermittent Demand Flag Whether the history data for an item is intermittent or not determines: • • the forecast methods that Oracle Service Parts Planning (SPP) employs to generate a 'Blended' (Bayesian weighted average) forecast.2 Release Content Document Oracle Service Parts Planning 117 . and will be referred to by the SPP forecasting engine. The planner's replanning action will not affect the planning results of any other part in other supersession chains.2 3. Release 12.16. This feature operates in conjunction with net change collections. then quickly recalibrate the supply / demand balance of the part being worked.2.16. and by IO. and the safety stock calculation method used by Oracle Inventory Optimization (IO).2. each on their own parts. 3. or just one of those. Multi-process Inline Forecasting The performance of Inline Forecasting in Oracle Service Parts Planning (SPP) has been significantly enhanced through the introduction of a new profile option "MSO: Number of processes for Inline Forecast". or supplier capacity. 3. The replan can include forecasting and replenishment planning.16. and while leaving the preexisting planning results of other parts intact.1. This approach this had two inherent issues: (i) the forecast rule is independent of item and (ii) non-SPP users of Oracle Inventory Optimization needed to set up SPP Forecast Rules in order to trigger IO's intermittent demand calculations. without impacting each other's work. If the "Net Change" launch option of SPP toggled to Yes. SPP will only generate fresh plan results for new parts or those parts that have experienced net changes in demand/supply.or changing the forecast either manually or by switching statistical forecasting methods. 3. SPP enhances scalability by planning parts only when necessary.1.3.

4. depending on this safety stock target and future demand.3 3. 3.16. Orders are usually created for the economic order quantity. The user also has the option to override the system computed values. The values of safety stock and EOQ can be recalculated during a planning run.Item-Zone tab of the IMM.2 Release Content Document Oracle Service Parts Planning 118 . Oracle E-Business Suite Releases 12. It uses demand forecasts and item lead times to decide when to place a new order in order to avoid dipping into safety stock.16. The options on the Forecast Rule screen to specify whether history is intermittent or not have been removed. and it is easier to drill down from this prioritized list of tasks to details regarding each. Planner Worklist Enhancement Oracle Service Parts Planning already had a 'Planner Worklist' that could be set up for each planner so that it dynamically lists important exceptions / key recommendations on his items.3 has been enhanced to support Re-order point based planning. or reads in safety stock targets from other sources (like Inventory Optimization). This shows the most important to-dos that each planner must take care of at any given time.1 and 12. The grouping of exceptions and recommendations has been rationalized so that the results are presented in a more concise manner.16. 3.1. in order to strike a balance between purchasing and carrying costs. SPP computes the safety stock target for a part based on mean absolute deviation (for parts with regular demand) or assuming a Poisson distribution (for parts with intermittent demand).1.4. It then dynamically determines when to place an order.1. The Planner Worklist has been further enhanced in Oracle Service Parts Planning 12.1. or they can be retained at their existing values. Re-order Point-based Parts Planning Reorder point based planning is a widely adopted method of planning replenishments for service parts. so that new orders are placed for this quantity. SPP also computes the Economic Order Quantity using the standard formula.3. Release 12.3. PAB Profile Q u a n t i t y Time Re-order Quantity Safety Stock Demand Supply Oracle Service Parts Planning 12.2.

2. Integration with APCC . and the second coming from the service supply chain. SPP 12. SPP can source parts from the manufacturing supply chain.16.4. Thus SPP would take in demand from the Service supply chain and try to meet these demands through repair of defective parts.4. Thus the manufacturing facility that manufactures the parts will have two sets of demands – one coming from the manufacturing supply chain. 3. In case all demands cannot be met in this manner. Integration with Advanced Supply Chain Planning An OEM manufacturing products often manufactures spare parts for them too. A standard format spreadsheet template is provided as part of legacy collections flat file loads.1.16. Typically the OEM would have a distinct service supply chain. This is however difficult to use when the planner has to manually enter or edit values for each attribute in the forms UI. Oracle Advanced Supply Chain Planning (ASCP) plans for the manufacturing supply chain and currently handles the first stream of demand.3 has been enhanced to support a mass upload of item attribute values into the simulation set. and then upload the spreadsheet file to mass update the values for the respective attributes on the items. In case there is not sufficient supply of defective parts (that can be repaired) in the service supply chain. This ‘demand’ for spare parts from SPP is read in by ASCP (by virtue of the SPP plan being a demand schedule in the ASCP plan). ASCP is now integrated with Oracle Service Parts Planning (SPP) which plans for the service supply chain. 3.1 and 12.4. The planner can use this template to enter / edit / delete attribute values. ASCP then plans the manufacture.3. new parts may have to be manufactured.4. where defective products are returned and repaired.2 Release Content Document Oracle Service Parts Planning 119 .16. Service Parts Plans can be archived and published to Advanced Oracle E-Business Suite Releases 12.Service Parts Planner Dashboard A new Service Parts Planner dashboard is now available in Advanced Planning Command Center. The Planner Workbench (Supply Demand Analysis) screen has also been enhanced to enable update of item attributes that will then be considered in an online replan.3. Import into a Simulation Set The Simulation Set in SPP is used by planners for mass maintenance of data.

3.3.2 to support this. The Demand and Supply page enables the planner to start with an overall view of demand satisfaction in the service supply chain. profitability and achieved versus target safety stocks. The Service Parts Planner dashboard is structured to address the typical questions that a parts planner would have and includes a number of service-specific measures and KPIs. so that the planner can identify the various demands that are competing for constrained supplies within a time bucket. service contracts performance. A ‘Supply Allocation Rule’ screen has been added to SPP to specify the organizations whose demands can compete for constrained supplies at a source organization. Supplies are also fair shared among safety stock demands.’ In case of a tie.1. summarizes demand and supply.16. Release 12. However. SPP allocates supplies to demands based on the demand priority. compare against SPP plan output. the organization priority specified in the Supply Allocation Rule is used as a tiebreaker. revenues. Oracle E-Business Suite Releases 12. The SPP dashboard has five pages: the first. exceptions. and review costs. The planner can see compliance to service contracts.1 and 12. Fair Share In case of constrained supplies.5.1. a Plan Health summary. such as repairs versus new buys.1. 3. The SPP Supply Demand Analysis window has been enhanced to add an ‘Unconstrained Demand’ row.Planning Command Center. The reports on this page are based on Inventory Optimization plans.2 3. The Service Level Agreement Analysis page is meant for evaluating service contracts. SPP has therefore been enhanced in release 12. If there is insufficient supply and there are multiple competing demands of the same priority in the ‘allocation bucket’. supplies at the source organization are fair shared amongst them in the ratio of the ‘current demand. planners may prefer to fair share constrained supplies among competing demands of the same priority from different organizations.5. The planner can compare how actuals for measures such as shipments and returns. after reserving a portion of the supplies to meet the source organization safety stock target. The archived versions can then be viewed in reports and dashboards. and service agreements.2 Release Content Document Oracle Service Parts Planning 120 . Oracle Service Parts Planning (SPP) previously allocated the available supplies to the first demand. internal versus external repairs. SPP considers demands across the supersession chain while fair sharing supplies. and drill down all the way into the SPP planner workbench.16. The Exceptions page of the Service Parts Planner dashboard highlights key exceptions in the service parts plan and enables the planner to investigate their causes. Finally the Historical Performance page gives the planner a picture of how the plan is tracking against actuals.

Collect Field Replaceable Unit Bills of Material Forecasting the requirement of parts to service an Installed Base under contract (as detailed above) requires information on the various components (called Field Replaceable Units) in the install base item that are eligible for service. The Oracle Value Chain Planning Server Parts Planning solution has been enhanced in Release 12.1. when you collect the Installed Base under Contract.3.16. say orders for items can be blocked from release if the forecast accuracy is too low.1 and 12. 3. and then specify whether (a) the records returned by the query should be released or (b) the records returned by the query (say ones that cause an exception) should be blocked from release. In order to enable this. This FRU BOM is then used in Demantra Demand Management to compute the failure rate of parts.2 to enable ‘Query-based Autorelease’. which is then used in computing the service parts forecast. when a single order is for a very large value) before the order is released. the planner may want to be alerted in specific scenarios (for example. manually releasing planned orders to execution is often not an option. along with the computed failure rate of each service part in the Installed Base item. or (b) if the debrief on a service request for the Installed Base item includes a part belonging to this category set.2. You can now collect a new entity. certain forecasting related metrics (like MAPE) are computed in Demantra and exported to SPP. In addition to these. ‘Installed Base under Contract. to determine the service parts forecast.5. 3.16. so that the release action is applied to all orders for the particular item/supersession. SPP has therefore been enhanced in release 12. Oracle E-Business Suite Releases 12. an ‘Applied-to’ column has been added. This information is then used. the number of installed units that were under contract is determined. for each period.3. As a result.4. Previously.’ When this is entity is collected.1. the installed base history and contract history are examined. the Field Replaceable Units (FRU) BOM can be automatically derived.16. In Release 12. The planner can now define queries.3. A profile option has been added to specify the period for which this information must be collected. and all other orders be released. However. Collect Installed Base under Contract A planner might want to forecast the demand for service parts that is likely to arise in the future. or to all orders for that item/supersession in that organization.5.1.2.3. and therefore an even higher number of planned orders. so that.2 to provide this capability. FRU BOMs are then derived based on parts belonging to this category set: (a) that are part of the manufacturing BOM of the Install Base item.3.5.2 Release Content Document Oracle Service Parts Planning 121 . SPP provided the option to auto-release all orders within the release time fence. and. These metrics have been enabled for inclusion in queries. in order to service the Installed Base of products that are covered under contracts. Query-based Auto-release Service supply chains often have millions of parts that are planned for. all FRUs have to be included in a designated category set. Further.

6. companies are searching for ways to improve their supply chains in order to absorb disruptions that occur unexpectedly. Supersession Notes Customers often require the ability to add free form notes while creating a supersession relationship. While providing other substantial benefits.1. the SPP release code calls an Oracle Depot Repair API. Release 12. Support Multiple Move-in / Move-out Lines for a Repair Order In case the depot organization is different from the central warehouse and defectives are not at the depot organization. Order to move defectives in for repair (move-in line). 3.1. These notes must then be visible to a planner in Service Parts Planning.2 Release Content Document Oracle Strategic Network Optimization 122 .1.1. for example. 2.3. Supply Demand Analysis.3. repair order and the move-out line. During the release process.17.1. can Oracle E-Business Suite Releases 12.16. the repair order and the move-out line in the SPP engine.17.1.5. and display them on the key screens where a planner may review the supersession: the Planner Worklist. SPP therefore will no longer enforce one to one to one pegging between the move-in line. 3. the Depot Repair API did not support multiple move-in and/or move-out lines for a repair order.2. Corresponding to this.usually in the form of inventory .2 to pull in the notes that are created in Spares Management. information about when the supersession is for dangerous goods. Just-in-time. Supply Chain Risk Management Due to the dynamic nature of the global business environment.5. Slack in the supply chain .is no longer an acceptable hedging strategy and a sudden change such as a missed supply. Oracle Strategic Network Optimization 3. Release 12.2 3.16. Oracle Service Parts Planning has been enhanced in Release 12. and Supersession screens. Oracle Service Parts Planning (SPP) generates three separate planned order recommendations for internal repair. Non Standard repair work order to repair the part (repair work order). Until Release 12. The Depot Rapair API is being enhanced in Release 12.2 to support multiple move-in / move-out lines for a repair order. 3. They are: 1. which creates execution documents for the move-in line.1 3. These notes usually contain detailed information about the relationship. the repair order and the move-out line.17.6. This meant that there had to be a one to one to one pegging between the move-in line. Order to move usable inventory to the demanding organization (move-out line). and Lean Manufacturing initiatives have hindered many business's ability to absorb the impact of unexpected events.1 and 12. the SPP release capability is being enhanced to support this situation.16. The notes are created in Oracle Spares Management while defining the relationship.

or risk. Consideration for a more flexible framework to support non-traditional uses will be considered in the future. the element of surprise needs to be reflected in the solution. the type of alert violation will be identified. Reports (Smart graphs) are typically created to supplement the Sets and present the information in a more useful format. The current mechanism to view and manage alerts in SNO is by using the Over and Under User Sets.17. For example. the generic Over/Under categorization makes it difficult for users to quickly identify exceptions of a certain type. Less sensational events. The following enhancement will allow planners to analyze and mitigate risk by:    The Ability to consider unplanned. this is not a realistic hedging strategy. These simulations can also be run proactively to determine the potential exposure.have an immediate impact on a companies' operations.2 Release Content Document Oracle Strategic Network Optimization 123 . In order to simulate the unpredictable nature of such events. the simulation of an unexpected plant shutdown in the future will trigger inventory pre-build in anticipation of this event in most software packages. Since this event occurs unexpectedly. recent hurricanes have proved disastrous and exposed many weaknesses and companies' existing supply chain. This requirement will be a key differentiator for the Strategic Network Optimization and strengthen its position in the marketplace as the leader in Supply Chain Risk Management decision support systems. While this is useful. This provides the planner with the ability to quickly identify Oracle E-Business Suite Releases 12. Strategic Network Optimization will simulate the surprise nature of this event and will present realistic options should such and event occur. While most advanced planning software packages have simulation capabilities. Alerts are categorized based on the business area. It will also provide a familiar alert workflow that is typical in many planning applications. Within each category.1 and 12. 3. Alerts Alerts are used to assist the planner with identifying and resolving exceptions after solving the model. Introducing an alert framework in SNO alleviates the need to use both Sets and reports to manage and review exceptions in the model. SNO is often used to solve non-traditional supply chain problems. The ability to run simulations for these unexpected events is necessary for companies to manage risk and these capabilities are now available in Strategic Network Optimization. if a plant is unexpectedly shut down due to a natural disaster the solver should not pre-build inventory in anticipation of this event. such as an unexpected line shutdown can also have a material impact to the business. Because of it flexibility. that your company faces. Reports require set up beforehand and multiple reports are needed to identify exceptions of different types. As an example. and planned events and it’s impact on the supply chain Easily compare scenarios using various Key Performance Indicators Ability to consider multiple demand series and safety stock plans Vital to this enhancement is the concept of unplanned events. As an example. This enhancement focuses on the traditional strategic and tactical manufacturing & distribution use of the application.2. considering the unexpected nature of an event is absent.1.

total of (68) exceptions were found when the model was solved. as seen in the example above. Within Alerts. at the root level of Alerts. You can drill-down to the exact location of the exception within a node or arc. The ability to drill-down and easily navigate to the node or arc of interest is also an important requirement that is addressed. If no exceptions are found in the model. Alerts will provide the following benefits:     Alerts provide an immediate visual representation of exceptions. Alerts has no number in brackets next to it and the font is not bolded. In the example above.1 and 12.and focus on the area of interest. (42) Demand alerts. This image shows the new Alerts area at the bottom of the Strategic Network Optimization main user interface: The number and type of alerts is displayed in the Model Workspace area. Little set up is required to use alerts. a green checkmark is displayed next to the exception type. the number of alerts is displayed in brackets and the word Alerts is displayed in bold font. there are several specific types of exceptions. and (4) Transportation alerts were found for a total of (68). which are faster and more informative than using sets to identify exception. there are six different alert categories. Within each alert category. Oracle E-Business Suite Releases 12. If an exception is found. (22) Inventory alerts.2 Release Content Document Oracle Strategic Network Optimization 124 . In the example above. The number of exception found within each type of alert is displayed next to the alert category in the Model Workspace area. a red exclamation mark is displayed next to the exception type and if no exceptions are found. Alert categorization is more specific than Over and Under User Sets categorization. In the Model Workspace tree.

a new Category drop-down list was added to nodes and arcs: 3. using the up and down arrows at the top of the section. The six tabs. as seen in the example above. Transportation. minimizing inventory costs. the Alerts section at the bottom of the main user interface expands. If you double-click an Alerts folder in the Model Workspace tree. Key Performance Indicators After running a scenario. KPIs are only visible in Key Performance Indicators view. Inventory. Key Performance Indicators (KPIs) can help you make detailed scenario comparisons. This section can be shown. or providing the highest percentage of machine utilization.1 and 12. Single-clicking on an item in the Alerts section of the Model Workspace tree displays the alert in the Alerts section at the bottom of the main user interface. Manufacturing.1.17. expanded. KPIs can show you which scenario is most efficient at filling demand.The Alerts section can be displayed across the bottom of the main user interface. each node or arc that you want to be alerted about is assigned an alert category. To assign an alert category. Costs are categorized based on the types of costs in the nodes and arcs and are summed across the whole planning horizon. and Other reflect the alerts results and match the Alerts section in the Model Workspace tree.3. Supply. or collapsed. Demand.2 Release Content Document Oracle Strategic Network Optimization 125 . An example of the Key Performance Indicators View Strategic Network Optimization has nine different KPIs: Oracle E-Business Suite Releases 12. When using alerts. not by period. They provide you with graphical representation of various metrics in a model.

The sum of all costs for any node or arc in the model where Category is null.         Total Cost . the data can also be displayed in pie chart format or polar format by clicking the Pie or Polar tabs.Machine utilization expressed as a percentage.2 Release Content Document Oracle Strategic Network Optimization 126 . Key Performance Indicator data is displayed in bar chart format. Other Cost . each scenario defined in the Model Workspace appears in the Key Performance Indicators view.Demand Fill Rate expressed as a percentage. Supply Cost .The sum of all costs for any node or arc in the model where Category is set to Supply.The sum of all costs for any node or arc in the model where Category is set to Manufacturing. Transportation Cost . However. Production Cost .The sum of all costs for any node or arc in the model where Category is set to Inventory. Demand Fill Rate % . A polar chart displays points in a graph based on data in the scenario.The sum of all costs in the model. Oracle E-Business Suite Releases 12. By default.1 and 12. An example of a polar chart can be seen here below: = Polar chart By default.Labor utilization expressed as a percentage. Labor Utilization % . Machine Utilization % . However. you can use the KPI Selection Dialog to choose which key performance indicators scenarios are displayed. Inventory Cost .The sum of all costs for any node or arc in the model where Category is set to Transportation.

Events are created and then added to scenarios.1 and 12. Each scenario should have at least one event assigned to it. scenarios are now created and run from the Model Workspace tree as seen below: Scenarios & Events in the Model Workspace Tree The concept of events is new to this version of Strategic Network Optimization.KPI Selection Dialog The concept of scenarios was introduced in previous versions of Strategic Network Optimization. they are complete surprises. They specify the find and replace functions which are performed within the model. A sudden change such as a missed supply can have an immediate impact on a company’s operations. However. Unplanned events allow you to incorporate the concept of surprise into your model’s solution. Oracle E-Business Suite Releases 12.2 Release Content Document Oracle Strategic Network Optimization 127 . They are used when there is no warning that the event will occur. Examples of unplanned events which can massively interrupt supply chain operations include natural disasters such as hurricanes and floods. Events are individual occurrences which impact the supply chain. If you run a scenario with no events in it. There are two kinds of events:   Unplanned Planned Unplanned events have been added to support Supply Chain Risk Management. Several events can be added to the same scenario. the model baseline solves.

Planned events are not surprises and there is at least some react time involved. For example. navigation. The node color has also been changed to match the color of the application and block images have been updated in the sample models. This enhancement provides the following in SNO:    Combined dialog boxes for Find.1.1 and 12. The usability suffers further as the number of modal dialogs that pop up can be many. The purpose for initiating any of these utilities are many – from model creation. a simple Find query with an ensuing replace opens up to seven dialog boxes which must than be closed. These include:         Find & Replace Hide Nodes Hide Arcs Fat Arcs Align Nodes in Columns Align Nodes in Rows Select Adjacent nodes Show/hide map legend Improved Map Legend The map legend has been improved to provide the ability to move the legend outside of the map view to prevent the legend from covering up key areas of the map. anticipated shortages. Usability Enhancements The investment in usability continues with this release. yet different dialogs is confusing. and increases in demand caused by promotions. Oracle E-Business Suite Releases 12. and Find Export Ability to access the dialog boxes with shortcuts versus the multi-nested menus Improved usability with a more intuitive graphical user interface Quick access to common functions in the toolbar Commonly used functions have been added to the toolbar for easy access. and Find Export are essential tools required by consultants. there is some overlap and the fact that they each have similar. there is at least some time to make other supply arrangements and activate contingency plans.4. pre-sales. The ability to specify a shape and color has also been added in this release. and customers. With this advance warning. While each function serves a distinct purpose. In addition to the Alerts. and data editing to name a few. 3.17. Replace. Examples of planned events include seasonal supply chain interruptions. Replace. Overall Look and Feel Node icons have replaced the dated node symbols to make the nodes easier to identify.2 Release Content Document Oracle Strategic Network Optimization 128 . and KPI view the following enhancements have been incorporated to improve the overall user experience: Improved Find and Replace Find.

Oracle E-Business Suite Releases 12.2 3.1 and 12.17. assignment sets and lanes are required to be defined for each item that needs to be considered in a plan.17. For example. Aggregate Assignment Set and Lane Definition When setting up a Strategic Plan.2. This will also decrease the number of initial setup problems since the most common problem is missing one of the many assignments or lanes that need to be defined. For assignment sets the number of itemorganization combinations can potentially be very large since many of the aggregate assignment levels are currently not supported. Support for specificity rules to allow for defaulting.3. The purpose of this enhancement is to ease the set-up required when defining strategic plans.1. A simple example will illustrate the current challenge. truck)=2 For this small supply chain 2 x 100 x 2 = 400 individual lanes would need to be entered. Support lane definition for regions or zones This enhancement will ensure consistency with the other planning products and greatly improve usability. when setting up lanes from organization to customers each individual lane needs to be defined for every itemorganization-customer site-ship method combination.1. a sourcing rule at the item-organization level will override a previously defined assignment at the category-organization level. The setup for this can become very tedious and error prone.2. This is achieved by:    Support all available assignment type levels for input assignment sets. Similarly. Release 12. Number of customer sites =100 Average Number of DC’s per customer site=2 Number of ship methods (rail.2 Release Content Document Oracle Strategic Network Optimization 129 .

2 Release Content Document Oracle Strategic Network Optimization 130 .1.4. Specify Scenario File in the Plan Options This enhancement improves the usability and robustness of Strategic Network Optimization when deployed leveraging the standard integration to Oracle EBS or EnterpriseOne.17.1 and 12.3 There are no new enhancements in Oracle Strategic Network Optimization in Release 12. Oracle E-Business Suite Releases 12. 3. In many cases it is necessary to augment the model that is created using the standard integrated process as the information may not be available in the source system or the modeling constructs might need to be altered to satisfy specific business requirements.17.2 3.3.17.4.1.1. Release 12. Some examples include • • • • Adjusting node-specific penalty costs Considering future currencies Modeling unique supply chain constraints Leveraging Risk Adjusted Costs These types of changes may be accommodated leveraging Strategic Network Optimization’s import file. The plan options have been modified to allow the specification of one or more scenario files (import files) to the plan.3.3. Release 12.

2. the CPLEX version has been upgraded from version 10.2. This will be especially valuable to our customers with larger SNO models.17.Currently this can only be accomplished on the server side by expert users and requires access to the server. and Strategic Network Optimization batch import commands. scripts.1 and 12. Oracle E-Business Suite Releases 12.4.2 Release Content Document Oracle Strategic Network Optimization 131 . In this release.0 to 12. SNO leverages the industry standard CPLEX solver which is capable of solving large scale Linear Programming problems. which enables the SNO solver to run significantly faster while requiring less memory. Providing the ability to attach scenario files to the plan options will: • • • • Lower the Total Cost of Ownership by providing an easy mechanism to import model customizations Improve usability and adoption in the field Decrease data and model errors as the appropriate version of the scenario/import file can be attached to the plan Expand the relevance of the standard integrated model 3. Solver Upgrade Strategic Network Optimization leverages linear optimization in combination with a number of heuristics to solve long term supply chain planning problems. The following diagram illustrates this enhancement in context of the overall architecture. appropriate server permissions and knowledge of the back end file structure. Server side customizations will still be available and is the recommended approach for significant customizations.

Typical Capital Asset Management problems include: • • • • • • How many facilities (Plants/DC’s) should I have? Where should my facilities be located? What impact will off shoring have on my supply chain Can I rationalize my facilities without compromising my ability to meet demand? How can I mitigate supply chain risk? When should I open/close my facilities? Leveraging the MIP algorithm will better align SNO with current cost-driven objectives used in facility planning.The new CPLEX version also comes bundled with a Mixed Integer Programming (MIP) solver which allows SNO to provide better (lower cost) solutions for go/no-go problems.1 and 12.2 Release Content Document Oracle Strategic Network Optimization 132 . Oracle E-Business Suite Releases 12. including Capital Asset Management.