Ted Paetkau

1
Top Ten Reasons for Implementing Oracle Demand
Planning
Ted Paetkau Implementation Consultant DARC
Corporation
2
7

• Workflow-Automated Process

3
ODP Architecture
Personal Databases
Transaction Source Applications
Shared Database
10.7
Collect andPull
Express build
Create personal
11.0
Planning Server
Writeback
Submit forecast
Publish
11i
Legacy
Online Analytical Processing (OLAP)
4
(No Transcript)
5
6

• Role-Based

6
Demand Planning Roles

• Demand Planning System Administrator
• Oversees the planning cycle
• Sets up the planning system
• Assigns portions of the plan to individual
  planners
• Demand Planning Manager
• Reviews/modifies planners consolidated forecasts
• Responsible for final forecast written to
  planning server

7
Demand Planning Roles

• Demand Planner
• The guts of the demand planning process
• Creates forecasts for assigned area
• Submits forecasts to shared cube for
  consolidation
• Collaborates with other planners as needed

8
5

• Ease of Creating Sophisticated Forecasts

9
Forecast Wizard
10
(No Transcript)
11
(No Transcript)
12
4

• Forecast Analysis Tools

13
Forecast Analysis Tools

• Stored Measures
• Formula measures
• Worksheets
• Reports
• Graphs
• Custom Aggregates
• Events

14
(No Transcript)
15
(No Transcript)
16
Custom Aggregate
17
(No Transcript)
18
3

• Global Forecasting

19
Global Forecast DefinitionDescription
Ship to and ship from for global forecasts
Customer Zone
Customer
Customer Site
Demand Class
Global (Item)
Zone
Ship to
Global Forecast
Consume forecasts with respect to ship to
Forecast distribution assignment set
Organization 1
Organization 2
Organization 3
Ship from locations
20
Ship To location set to All Organizations
21
Global Forecast Consumptionis done in ASCP
Consumption level in plan options, choose Zone
for Global consumption
Consumption level based on DP scenario
ZONE
22
Distribute Global Forecastsis done in ASCP
Assign a Forecast Distribution Assignment Set to
a plan
23
2

• Integration

24
Demand Planning Integration

• Data from Oracle and non-Oracle transaction
  servers pulled into ODP.
• ODP forecasts published to source transaction
  systems can be loaded into MDS.
• ODP forecasts consumed in ASCP
• ODP scenarios read by ASCP as independent demand
• Demand Plans directly used by Inventory
  Optimization
• Customer sales histories imported to ODP from CP
• Customer forecasts published to CP for
  replenishment planning

25
1

• Collaboration

26
Demand Planning Architecture
Personal Databases
Transaction Source Applications
Shared Database
10.7
Collect andPull
Express build
Create personal
11.0
Planning Server
Writeback
Submit forecast
Publish
11i
Legacy
Online Analytical Processing (OLAP)
27
Advanced Planning
Demand Planning

• Forecast Service Parts Usage
• Forecast Returns
• Supersession Forecasting
• Round Fractional Quantities
• Forecast by Demand Class
• Support for Pick to Order Models
• Forecasting of Key Configuration
• Calculate Planning Enhancements
• Oracle Database 9iR2 OLAP

• Acquire Sales History from Customer
• Forecast Based on Scheduled Arrival Date
• Internal Collaboration Enhancements
• New Product Intro Event Allocations
• Up-sell / Cross-Sell Substitution items
• Folders for Measures
• Automate Submissions Process
• Multiple Document Interface
• Preserve Forecast Adjustments
• Display Backcast
• Global Forecasting
• Line of Business Specific DP
• Consumable Mtl Planning for CMRO

Totally New Functionality
28
Why Implement ODP?

• Designed for collaboration
• Role-based
• Sophisticated forecasts with minimal effort
• Analytic tools
• Integration
• Workflow-automated

• Single consensus forecast across the organization
• Accurate view of demand
• Forecast one-time events
• Achieve a consensus forecast rapidly