Forecast 2 Plano DP 3

Oracle Advanced Supply Chain Planning R11i (Release 11.5.
10)
FORECAST TO PLAN USING ORACLE

DEMAND PLANNING
Prepared by Oracle Applications Manufacturing BDE

Author: Sanjeev Kale
Creation Date: January 18, 2005
Last Updated: March 7, 2005
Copyright 2002 Oracle Corporation

All Rights Reserved
Page 1
Oracle Advanced Supply Chain Planning R11i (Release 11.5.10)
Introduction............................................................................................................................................................................................. 3
Oracle Demand Planning Data Loader Steps.......................................................................................................................................... 4
Method I Prior to 11.5.10................................................................................................................................................................. 4
Using Excel Spread Sheet to Import Data into Oracle Demand Planning.......................................................................................... 4
Populating the staging tables using the worksheets (*.csv) via sqlldr.............................................................................................. 14
Method II 11.5.10 Collect Flat File Data Self Service ................................................................................................................ 16
Oracle Demand Planning Running Data Pull .................................................................................................................................... 23
Oracle Demand Planning Define Demand Plan................................................................................................................................. 28
Oracle Demand Planning Generate Sales Forecast............................................................................................................................ 34
Oracle Demand Planning Achieve Consensus Forecast ..................................................................................................................... 44
Advanced Supply Chain Plan Create and Launch Plan ...................................................................................................................... 63
Hierarchies used in the seeded Vision Demand Plans .......................................................................................................................... 68
Glossary ................................................................................................................................................................................................ 89
Page 2
Introduction
The purpose of the document is to walk you through the set up and understanding of Oracle Demand Planning. I have
made certain assumptions while writing this. They are as follows
You are using 11.5.10 version of Oracle Application.

This data has been tested and works on Vision Database.
Page 3
Oracle Demand Planning Data Loader Steps

Method I Prior to 11.5.10
Using Excel Spread Sheet to Import Data into Oracle Demand Planning
The purpose of this paper is to walk through the steps required to update the Excel Spread Sheet to upload custom data.
It will walk you through examples of updating data in the order that is easiest to use. By using the spreadsheet the
shipping/booking history information as well as the level values will be loaded via the staging tables. This is in lieu of
pulling the data from the Order Management transaction system. We are only using the seeded levels and hierarchies. To
customize hierarchies, please refer to the Advanced Topics section of the Demand Planning Users Guide and to the
white papers available on the APS website. Please find attached with this document a file named ODP.zip.
The Process
1) Go through the spreadsheet and the ODP Data Loader Steps document, which are provided in the same zip file
from where you accessed this document.
2) Model the changes on paper first.
3) Modify the spreadsheet as required for your changes.
4) Populate the modified data (spreadsheet) into the staging tables on the planning server using the loader
program. This replicates what the collection programs would do if it were to be collecting the data from the
planning server. The loader program and vision demo data spreadsheet are included for your convenience.
Please go through this document and the ODP Data Loader Steps document before starting the process.
5) Build and validate the Demand Plan as the Demand Planning System Administrator.
6) Build the demand plan (Cube) as the Demand Planning Administrator
7) Go through the Demand planning Process as explained in user guide and other documents.
8) You should be prepared to go through a few iterations of this process. It is best to not make sweeping changes
in the spreadsheet unless you are comfortable with the process. It is easiest to restrict the changes to only the
level values (such as, the names of the products, customers etc.).
Step 1 Populate the MSD_ST_LEVEL_VALUES worksheet
Page 4
Define the Level Values you are going to use. The level value is the item name, customer name, ship to etc that
you will be using. This is done on the Level Value worksheet. There are 33 different levels that are system defined
and populated.
Following Rules must be observed for populating level values.
1) All levels, 1 - 33 must be present with values.

2) All primary keys must be unique within the level. You can have the same primary key in two different levels,
but not within the same level.
3) The level values and the shipment/booking data are going to be loaded via the flat files, the primary keys
for some of the levels need to map back to the source transaction tables. The mapping instructions will be
provided in the next few sections.
4) You only need to change the values for the items you want to resemble the prospects data. For example, if
you only need to change the item numbers and the customers, then you can leave the rest of the level
values as they are.
5) One level value can have only one parent level value in a hierarchy.
Instance_id can be extracted from MSC_APPS_INSTANCES as follows
select INSTANCE_ID
from MSC_APPS_INSTANCES
where INSTANCE_CODE='TST'
Level_id - Is a system defined level id. The level ids are listed below
Level ID relating to Product Hierarchy
1 Item
2 Product Category
3 Product Family
28 All Products
Page 5
Level ID Relating to Ship From Hierarchy
7 Organization
8 Operating unit
9 Legal Entity
10 Business group
29 All Organizations
Level ID relating to Ship To Relationships
11 Ship to location
12 Region
13 Country
14 Area
15 Customer
16 Customer Class
17 Customer Group
30 All Geography
Level IDs relating to Sales Reps
18 Sales Representative
19 Sales Manager 1
20 Sales Manager 2
21 Sales Manager 3
22 Sales Manager 4
32 All Sales Representatives
Page 6
Level IDs Relating to Sales Groups
23 Sales Group 1
24 Sales Group 2
25 Sales Group 3
26 Sales Group 4
32 All Sales Representatives
Level IDs Relating to Sales Channel
27 Sales Channel
33 All Sales Channels
The highlighted level ids are significant in that the primary keys (SR_LEVEL_PK) for this need to map to
the values in the appropriate source transaction tables.
The following table describes the suggested scripts that will extract these primary key values
LEVEL_ID LEVEL NAME SCRIPT TO EXTRACT SR_LEVEL_PK

1 Item select SR_INVENTORY_ITEM_ID,ITEM_NAME
from MSC_SYSTEM_ITEMS
where ITEM_NAME IN(AS66311,CM66321,'CM66326')
and ORGANIZATION_ID=207
and PLAN_ID=-1;
2 Product Category select CATEGORY_ID
from MTL_CATEGORIES_V
where STRUCTURE_NAME = 'Item Categories'
and CATEGORY_CONCAT_SEGS = COMPUTER.HANDHELD;
3 Product Family select CATEGORY_ID
where STRUCTURE_NAME = 'Product Family'
and CATEGORY_CONCAT_SEGS = ' Hardware';
select ORGANIZATION_ID
7 Organization from MTL_PARAMETERS
where ORGANIZATION_CODE='M1';
8 Operating Unit select OPERATING_UNITS_ID
Page 7
from HRFG_OPERATING_UNITS
where OPERATING_UNIT_NAME= Vision Operations;
Note:
The operating unit name for your organization can be
determined by viewing the Accounting Information for your
Organization Setup. This is usually a 3-segment flexfield
that contains the set of books, operating unit, and legal
entity names.
Inventory > Setup > Organizations > Organizations

9 Legal Entity select LEGAL_ENTITY_ID
where LEGAL_ENTITY_NAME= Vision Operations;
Note:
The legal entity name for your organization can be
determined by viewing the Accounting Information for your
Organization Setup. This is usually a 3-segment flexfield
that contains the set of books, operating unit, and legal
entity names.

10 Business Group select BUSINESS_GROUP_ID, BUSINESS_GROUP_NAME
where LEGAL_ENTITY_NAME= Vision Operations
and OPERATING_UNIT_NAME= Vision Operations;
Note:
The legal entity name and the operating unit name for
your organization can be determined by viewing the
Accounting Information for your Organization Setup. This
is usually a 3-segment flexfield that contains the set of
books, operating unit, and legal entity names.

11 Ship To Location select RAC.customer_name,RAC.customer_id,
ACS.customer_site_id
from arfg_customer_sites ACS,
ra_addresses_all RAL,
ra_customers RAC
Page 8
where RAC.customer_name='Computer Service and Rentals'
and RAC.customer_id=RAL.customer_id
and RAL.address_id=ACS.address_id
and ACS.site_usage = 'Ship To';
NOTE:
The Ship-to-Location primary key will be the extracted
ACS.customer_site_id.
15 Customer select RAC.customer_name,RAC.customer_id,
ACS.customer_site_id
ra_customers RAC
NOTE:
The Customer primary key will be the extracted
RAC.customer_id.
12 Region If the Region level value is interpreted as the city,
county or state, the information can be extracted from
RA_ADDRESSES_ALL:
select RAC.customer_name,RAC.customer_id,
ACS.customer_site_id,RAL.city,
RAL.state, RAL.county, RAL.country
ra_customers RAC
Since the primary key for this level value is not

significant, you can assign any primary key.
13 Country The Country level value can be extracted from
RA_ADDRESSES_ALL:
Page 9
select RAC.customer_name,RAC.customer_id,
ACS.customer_site_id, RAL.city,
RAL.state, RAL.county, RAL.country
ra_customers RAC
where RAC.customer_name=' Computer Service and Rentals'
Since the primary key for this level value is not

significant, you can assign any primary key.
18 Sales Representative select salesrep_id, SUBSTR(name,1,35)
from RA_SALESREPS_ALL
ORDER BY NAME;
In this paper we will be using following information
Item = AS66311,CM66321, CM66326 and the item category = COMPUTER.HANDHELD and Product Family =
Hardware, Organization = M1 and will be using the following customer with their corresponding ship to location
Computer Service and Rentals - Chattanooga= 1249, Tempe= 1028, Toronto= 1072
AT&T Universal Card - San Mateo = 5684, San Jose = 5911, Jacksonville = 1062
Business World - San Jose = 7718, San Mateo = 3915
Nicole Aron - San Jose = 6352
Hilman and Associates - Tulsa = 1279
Example
Primary level key for level_id =3 (Item)

select SR_INVENTORY_ITEM_ID,ITEM_NAME
from MSC_SYSTEM_ITEMS
where ITEM_NAME IN('AS66311')
and ORGANIZATION_ID=207
and PLAN_ID=-1;
SR_INVENTORY_ITEM_ID ITEM_NAME
-------------------- ----------
2848 AS66311
Page 10
Primary level key for level_id =2 (Product Category)

select CATEGORY_ID
where STRUCTURE_NAME = 'Item Categories'
and CATEGORY_CONCAT_SEGS ='COMPUTER.HANDHELD'
CATEGORY_ID
-----------
1375
Primary level key for level_id =3 (Product Family)

select CATEGORY_ID
where STRUCTURE_NAME = 'Product Family'
and CATEGORY_CONCAT_SEGS = 'Hardware';
CATEGORY_ID
-----------
1535
The worksheet entry would be as follows
Instance Level Id Level Value Sr Level PK

21 1 AS66311 2848
21 2 COMPUTER.HANDHELD 1375
21 3 Hardware 1575
Step 2 Populate the MSD_ST_LEVEL_ASSOCIATIONS worksheet
This worksheet is used to relate the level values from one level to another. In essence you are filling the hierarchy
that has been defined. The product hierarchy is referenced below
Page 11
All
Products
Level ID 28
PK 1
Product Category
Product
Level ID 2
COMPUTER.HANDHELD
Family
PK 1375 Level ID 3
Hardware
PK 1575
Item
Level ID 1
AS66311
PK 2848
To interpret the level value association, Level 1 Item (Primary Key = 2848) rolls up to both Level 2, Product
Category (Primary key = 1375) and Product Family (Primary key = 1575). Level 2 rolls up to level 28 All
Products (Primary key =1) similarly Level 3 rolls up to level 28 All Products (Primary key =1)
The worksheet entry would look as follows
Level Value Parent Level Parent Level

Instance Level Id PK ID Value PK
21 1 2848 2 1375
21 1 2848 3 1575
21 2 1375 28 1
21 3 1575 28 1
Step 3 Populate the MSD_ST_SHIPMENT_DATA and/or MSD_ST_BOOKING_DATA worksheet
The process is the same for both of these worksheets. The difference between the two is the shipment data
worksheet has actual ship dates and the booking worksheet does not. This worksheet is used to create
shipment data. In its present form it has shipping history that starts in Jan 1998 and goes through Feb 2000.
You will probably need to change the dates to reflect the data.
Page 12
Instance = Instance_id from MSC_APPS_INSTANCES

Org = The Ship from Location
Org PK = The Org Primary Key
Model Number = The Item Number
Item PK = The Item Primary Key
Customer No = The Customer Name
Cust PK = The Customers Primary Key
Ship To = The Ship to Customer Location
Ship To PK = The Ship to Location Primary Key
Sales Rep = The Sales Rep
Sales Rep PK = The Sales Rep Primary Key
Sales Channel = The Name of the Sales Channel
Sales Channel PK = The Primary Key of the sales Channel.
Book Date = The date the Order was booked
Requested Date = The date the order was requested
Promise Date = The date the order was promised
Shipped Date = The date the order was shipped
Quantity = the number of units shipped
Amount = the value of the shipment.
Step 4 Populate the MSD_ST_PRICE_LIST to define the prices
If you want your forecast to have amounts, vs. just quantities, you need to enter price list data so the
forecast has something to base the value or the amount calculation on. If these are 0 you will not get an
amount number in the cube.
Key for the worksheet
Instance = MSC_APPS_INSTANCES.INSTANCE_ID
Price List Name = Free text Not validated against price list in OM
ORG LVL Id = What is the Org Level ID Or what level for the Org Dimension are you going to be
controlling the pricing at. In this example it is 29 (All Organizations)
Page 13
Sr Org Lvl Pk = What is the Level Value for the Org Hierarchy in our case the Primary Key is 1 or All
orgs
Prod Lvl Id = What is the product level ID - Or what level of the product Dimension are you going to be
controlling price at. In this example the Product Level Id = 1 (Item)
SR_Prod_LVL_PK What is the level value for the product ID this is where you would enter the level
value for the item number if you were controlling price at the item level. The extraction process for this
primary key is described in an earlier section.
Geolvl ID What is the Level ID for the Geography Dimension you are going to be controlling pricing at.
in this example it is 30 (All Geography)
SR GEO LVL PK What is the geography level value. In this example the primary key =1 or All
Geography.
Sales Channel Lvl Id What is the Level Id for the Sales Channel Dimension you are going to be
controlling pricing at in this example it is 33
Sales Channel Lvl PK What is the Primary Key for the Sales Channel in this example the Primary Key
= 1 or all Sales Channels.
Sales Rep Lvl Id What is the Level Id for the Sales Rep Dimension you are going to be controlling
pricing at in this example it is 32 All Sales Reps
Sales Rep Lvl PK What is the primary key for the sales reps in this example the primary key = 1 or all
Sales Reps
Start Date End Dates Enter the start and end date for the pricing
Price Enter the price
Priority will override any overlapping date ranges or other conflicts, such as two prices are applicable
for a customer at any point in time. The price with a Priority 1 will be applied before the price with a
priority two.
At this time we are not going to populate the MSD_ST_PRICE_LIST.
Populating the staging tables using the worksheets (*.csv) via sqlldr
1. ftp the following files from the ODP.zip to the unix
Page 14
msd_st_level_associations.csv
msd_st_level_associations.ctl
msd_st_level_values.csv
msd_st_level_values.ctl
msd_st_shipment_data.csv
msd_st_shipment_data.ctl
refresh_stage.sql
refresh_fact.sql
update_sr_orig_item_pk.sql
2. Rename the following files
$ mv msd_st_level_values.csv msd_st_level_values.csv1
$ mv msd_st_level_associations.csv msd_st_level_associations.csv1
$ mv msd_st_shipment_data.csv msd_st_shipment_data.csv1
3. Execute the following commnd on each of the *.csv file. The reason for performing the following is to truncate the
additional Carriage Return character added by windows in the csv file. Other wise you will get ORA-1722 "invalid
number"
$ tr -d '\r' < msd_st_level_values.csv1 > msd_st_level_values.csv

$ tr -d '\r' < msd_st_level_associations.csv1 > msd_st_level_associations.csv
$ tr -d '\r' < msd_st_shipment_data.csv1 > msd_st_shipment_data.csv
$ rm *.csv1
4. Execute the following commands to populate the staging tables.
$ sqlplus apps/apps @refresh_stage.sql

$ sqlldr apps/apps control=msd_st_level_values.ctl
$ sqlldr apps/apps control=msd_st_level_associations.ctl
$ sqlldr apps/apps control=msd_st_shipment_data.ctl
$ sqlplus apps/apps @update_sr_orig_item_pk.sql
$ sqlplus apps/apps @refresh_fact.sql
Page 15
Method II 11.5.10 Collect Flat File Data Self Service
To use this option, you need to create data files by downloading the templates and specifying the data in the
templates. Next, you load data files into Oracle Demand Planning by specifying the location of control and data
files.
To load data files using Self Service user interface:

1. Select the Demand Planning System Administrator responsibility.
2. In the Navigator, select Collections Collect from Legacy Systems Collect Flat File Data Self Service. The Self
Service page appears.
3. Select download link to download the template zip file.
4. Select Browse to select the data file to upload.
5. Submit the concurrent request for DP Purge Program.
6. Select Start Load Now to load the data file in Oracle Demand Planning.
To perform flat file loads:
1. Download the OATemplate.exe and extract the contents into a directory. You can download the template by
selecting the Load Setup Data link from the Admin tab in Collaborative Planning, or through the self-service
load menu from your APS application. Click the link to Download Templates.
2. Open up Microsoft Excel using the ExcelLoad.xlt file. When prompted, select Enable Macros.You will see the
APS menu option appear on the menu bar in Excel.
3. Import the appropriate *.dat file for the entity you want to upload by selecting the Import option from the APS
menu.If you are importing the dat file for the first time, then the Excel would prompt you to enter the Date
format(in which all the dates in the dat files would be converted) and the Delimiter(this value will be used
internally to seperate different columns in the dat file and will correspond to the "MSC: Self Service Loads
Delimiter" profile). Once the user enters these values, these would be stored internally (and the user is not
required to keyin these again). However, the user can change date format/delimiter by following the path: APS
Menu->User Options. This will open a window for modifying the values.The user can perform three actions on
this window 'Apply'- that applies all the changes on currently open sheet; 'Apply & Save'- that applies all the
changes on currently open sheet and also saves these settings(date format/delimiter) for the user; 'Cancel'- that
does nothing.
Page 16
NOTE: Currently we are supporting six date formats and two delimiters.While uploading the file, make
sure that the demimiter set in the dat file matches with the delimiter value in "MSC: Self Service
Loads Delimiter" profile, else the laod will fail.
4. Make changes and export the *.dat file by selecting the Export option from the APS menu. .
5. Return to the Collaborative Planning application and navigate to the Load Setup Data page under the Admin
tasks.
6. Browse for the *.dat file and load it by clicking the "Load Setup Data" link.
NOTE: Alternatively, you can load multiple *.dat files at the same time by placing them in one .zip file. Browse
and select the Zip file. Some files such as TradingPartner.dat and TradingPartnerSite.dat must be loaded
together in a Zip file. In this case, import the files, make changes, and export the files separately to your
computer. Then place the two files together in a single Zip file. Complete steps 5 and 6 above.
Description and format of the upload files: Each file that you upload is stored with the extension .dat. The first
row of each *.dat file contains columns that define the attributes for the entity that you want to load. For each *.dat
file, the definition of the columns that it contains is provided below. In this particular we will look at just the following
three files, since we will be using only these three.
LevelValue.dat Purpose:Use this file to define level members within a level of a demand planning hierarchy.
Field Name Description

Source Instance Code Source instance code defined on the planning server.
Level Name Name of the level in a demand planning hierarchy.
Level Value Value of the level.
Level Value Description Description of the level value.
Attribute1
Attribute2
Attribute3
Attribute4
Attribute5
Page 17
LevelAssociation.dat Purpose: Use this file to define a hierarchy or level associations in demand planning.

Level Name Name of a level in a demand planning hierarchy.
Sr. Level Value Value of this level.
Parent Level Name Name of the parent's level in the demand planning hierarchy.
Sr. Parent Level Value Value of the parent level.
Attribute1
Attribute2
Attribute3
Attribute4
Attribute5
Page 18
ShipmentData.dat Purpose:Use this file to load historical order shipments used in demand planning.

Inv Org Organization identifier on the planning server. The Inv Org is the same as the Organization.
Item Inventory item name.
Customer Customer name
Sales Channel Sales channel through which order is fulfilled.
Sales Representative Sales representative.
Ship To Loc Ship-to location.
User Defined Level1
User Defined1
User Defined Level 2
User Defined2
Demand Class Name of the Demand Class.Defaulted, if not provided.
Booked Date Date the order is booked.
Requested Date Date the order is requested; customer's request date.
Promised Date Date the order is promised.
Shipped Date Date the order is shipped.
Schedule Ship Date
Schedule Arrival Date
Amount Amount in the demand plan currency.
Quantity Shipped Quantity
Original Item
Parent Item Name The name of the Parent Item
Page 19
Open up Microsoft Excel using the ExcelLoad.xlt file. When prompted, select Enable Macros.You will see the APS
menu option appear on the menu bar in Excel.
Import the appropriate LevelValue.dat file by selecting the Import option from the APS menu. Please add the data
provided. Make changes and export the *.dat file by selecting the Export option from the APS menu. Repeat this
procedure for LevelAssociations.dat, and ShipmentData.dat.
Add these three files to a zip file named as (Xxodptst.zip).
Page 20
Page 21
The following request are launched by this process
REQ_ID CPRG_NAME
========= ================================================
2721886 User File Upload
2721887 Loader Worker
2721890 Pre-Process Monitor
2721891 MSC Pre Process Worker
2721894 Pull Level Values
2721895 Pull Shipment Data
2721896 Planning ODS Load
2721897 Planning ODS Load Worker
2721900 Planning Data Collection - Purge Staging Tables
Page 22
Oracle Demand Planning Running Data Pull
To understand the Dimension Hierarchies logon to the application as mfg/welcome user and select the Demand
Planning System Administrator and the navigation is Other Dimension Viewer
Page 23
The Data has been populated in the MSD_ST% tables now we have to run the following data pull program in this
order, Navigation path CollectionsPull Data
Level Values complete refresh = yes
Shipment Data
Page 24
After the Data Pull program completes succesfully, execute the following SQL and verify the data with the worksheet
data.
col INSTANCE format A4

col LEVEL_VALUE FORMAT A35
COL SR_LEVEL_PK FORMAT A15
select instance,
level_id,
level_value,
sr_level_pk,
level_pk
from MSD_LEVEL_VALUES;
select mla.instance,
mla.level_id "Level ID",
a.level_value "Level Value",
mla.parent_level_id "PLevel ID",
b.level_value "Parent Level Value"
from MSD_LEVEL_ASSOCIATIONS mla,
MSD_LEVEL_VALUES a,
MSD_LEVEL_VALUES b
where mla.instance = a.instance
and mla.sr_level_pk = a.sr_level_pk
and mla.instance = b.instance
and mla.sr_parent_level_pk = b.sr_level_pk
order by 2;
select * from MSD_SHIPMENT_DATA;
You can verify the level values and level associations by Login as Demand Planning System Administrator,
Navigation path Dimension Values Level Values. Enter Dimension = Product, Level=Item
Page 25
Dimension Values Level Associations. Enter Dimension = Product, Parent Level Name =Product Category
Page 26
After verifying the data matches to the worksheet data. Run the Audit Fact process to validate the fact data. Please
make sure the Audit Fact process completes without error, If it completes with warning we can ignore the warning.
Page 27
Oracle Demand Planning Define Demand Plan
Oracle Navigation Path Specific step

Process/Procedures
Logon to the application Demand Plans
as mfg/welcome
Responsibility =
Demand Planning
System Administrator
Select Organization Code=TST:M1
This will list all the Demand Plans available.
Click cancel
Name = XXODPPLAN Gregorian = Day
Description = XX Test ODP Plan Manufacturing = Day
Base UOM = Ea
Dimension Tab Dimension User Dimension
Geography Geograghy Click on DP Hierarchies
Hierarchy Name Dimension Name
Customer Class Geograghy
Geograghy Geograghy
Dimension User Dimension

Ship from Location Ship from Location
Click on DP Hierarchies
Organization Ship from Location
Page 28

Process/Procedures
Product Product Click on DP Hierarchies
Product Category Product
Product Family Product

Time Time Click on DP Hierarchies
Gregorian Calendar
Manufacturing Calendar Vision01
Input Parameters Tab Type = Shipmet History Shipped Items

Forecast by = Shipped Date
Start Date = 01-APR-1998
End Date = 30-JUN-1999
Quantity Used = Quantity
Amount Used = Amount
Page 29

Process/Procedures
Scenarios Tab Name = XXTESTODP
Description = 2005 Forecast
Forecast based on = Shipmet History Shipped Items
Forecast Period Type = Shipped Date
Output Period Type = Day
History Start Date = 01-APR-1998
History End Date = 30-JUN-1999
Horizon Start Date = 01-Jan-2005
Horizon End Date = 31-Dec-2005
Click on Output levels Buttons
Output levels
Dimension Level
Product Item
Ship from Location Organization
Geography Ship To Location
Verify the Lowest Time level for Manufacturing is Day

Click on the Validate
Plan, this will launch a
concurrent process, After
the process completes
successfully, requery the
XXODPPLAN. The
Status should be valid
Page 30

Process/Procedures
Demand Plan This will launch SSA window with XXODPPLAN status = Not
Administration built.
Click on XXODPPLAN A message will appear that the Plan
needs to be built This plan does not exist. Do you wish to
build it?
Click Yes
Following message appears A data download process has
been initiated. Please wait for a workflow notification
Click on Exit
Page 31
The Status will now show In-Progress/Built, You can click on the Status link to view the batch log for a plan. When the
download is completed succesfully, the batch log would look like as follows
Page 32
Demand Plan - SKODPPLAN
01/20/2005-21:54:10 -> Begin Downloading Data from Planning Server.
01/20/2005-21:54:10 -> Generating Express metadata structures.
01/20/2005-21:54:11 -> Loading specified Demand Plan information.
01/20/2005-21:54:11 -> Loading Dimension information.
01/20/2005-21:54:11 -> Loading Hierarchy and Level information.
01/20/2005-21:54:11 -> Generating DP Dimension metadata.
01/20/2005-21:54:12 -> Generating DP Hierarchy and Level metadata.
01/20/2005-21:54:12 -> Processing Attributes.
01/20/2005-21:54:12 -> Loading Time dimension values.
01/20/2005-21:54:35 -> Loading dimension values.
01/20/2005-21:54:35 -> Verify that all dimensions have values.
01/20/2005-21:54:35 -> Setting backend hierarchy information.
01/20/2005-21:54:36 -> Loading Input Parameters and Scenarios.
01/20/2005-21:54:38 -> Loading Item Unit of Measure information.
01/20/2005-21:54:38 -> Loading events.
01/20/2005-21:54:39 -> Loading data for specified Input Parameters.
01/20/2005-21:54:39 -> Loading data for the following Input Parameter: Shipment History - Shipped
Items:Shipped Date.
01/20/2005-21:54:42 -> Loading Unit of Measure conversion information.
01/20/2005-21:54:42 -> Calculating conversion coefficients for Product dimension.
01/20/2005-21:54:42 -> Loading variable Product pricing information.
01/20/2005-21:54:42 -> Converting for Express Objects.
01/20/2005-21:54:43 -> Converting to application metadata.
01/20/2005-21:55:49 -> Synchronizing variable names.
01/20/2005-21:55:49 -> Creating required worksheet objects.
01/20/2005-21:55:49 -> Creating required Workflow objects in the Master database.
01/20/2005-21:55:49 -> Aggregating input parameters needed for allocation.
01/20/2005-21:55:55 -> Allocating input parameters.
01/20/2005-21:55:55 -> Apply intelligent rounding to specified input parameters.
01/20/2005-21:55:55 -> Aggregating other input parameters.
01/20/2005-21:55:55 -> Setting DP system flags.
01/20/2005-21:56:04 -> Completed Downloading Data from Planning Server.
With this process completed we have built the Demand Plan.
Page 33
Oracle Demand Planning Generate Sales Forecast

Process/Procedures
Logon to the application Demand Plan Click on the XXODPPLAN
as mfg/welcome Administration
Responsibility =
Demand Planning
In the Demand Plan Highlight the measure Forecast of Shipment History
Navigator click on Shipped Date
Measures
Click on Edit button. This will pop up the measure Wizard
Data Transformation window.
Select Forecast Tab In the Forecast Levels region, set the levels for the
Dimensions as follows
Geography Ship to Location

Ship from Location Organization
Product Item
Time Gregorian Month
What time period do you want to base your forecast? (this
should default from you Plan definition). Set it to
From APR 1998

To JUN 1999
Page 34

Process/Procedures
What time period do you want to forecast?
From Current Month

To A Year Later
Click Finish This completes the Forecast measure definitions.
Populate Measures Highlight the plane name Select Populate Measures radio button
This is run to calculate at top of the Demand
measures in the shared Plan Navigator Click apply
database. The process
calculates measures that
have been downloaded
from the Demand
Planning Server.
The status of Populate Measures should eventually change
from Blank to Running to a date and time stamp with the
completion date.
The Demand Plan Navigator shoul look this.
Page 35
Page 36

Process/Procedures
Demand Planner Highlight Demand In the right Panel click on Settings button
Assignments Planner Assignments in
Distribute data segments the Demand Plan Change All Geography dropdown to Customer
among Demand Planners. Navigator Change All Organization to Organization
Change All Product dropdown to Item
Click OK
In the right Panel click on New button
Highlight Untitled Assignment 1, replace text with planner

name ODP Assignment for MFG1. Use the dropdown to
select a username
that have the Demand Planner responsibility assigned to
them. The LOV will show only those users who has Demand
Planner assigned. In this case I will select MFG1.
Click on Edit in the right Select Data Window will appear,
pane, to edit the scope of Select Value for Geography.
this Planners Select Computer Service and Rental and click on
assignment. the > button
Select Value for Ship from Location.
Select M1 and click on the > button
Select Value for Product.
Select AS66311 and click on the > button
Select Value for Measure.
Select Forecast of Shipment History
Shipped Items:Shipped Date and click on the > button
Click on OK button.
Page 37

Process/Procedures

name ODP Assignment for MFG2. Use the dropdown to
select a username
that have the Demand Planner responsibility assigned to
them. The LOV will show only those users who has Demand
Planner assigned. In this case I will select MFG2.
this Planners Select AT&T Universal Card and click on
assignment. the > button
Select AS66311, CM66321,CM66326
and click on the > button
Click on OK button.

name ODP Assignment for MFGMGR. Use the
dropdown to select a username hat have the Demand
Planner responsibility assigned to them. The LOV will show
only those users who has Demand Planner assigned. In
this case I will select MFG.
Page 38

Process/Procedures
this Planners Select AT&T Universal Card
assignment. and Computer Service and Rental and click on the >
button
Select AS66311, CM66321,CM66326
Click on OK button.
Distribute to Planners Highlight the plane name Select Distribute to Planners radio button
The process distributes at top of the Demand
all measures that have Plan Navigator Click apply
been marked for
distribution as well as any The status of Distribute to Planners should eventually
measures that have been change from Blank to Running to a date and time stamp with
defined by the Demand the completion date.
Plan Manager since the
last time that the batch
was run. The process
also distributes data
assignments
Page 39
The Demand Planner Assignment screnn should look like as follows
Page 40
Page 41
Page 42
The baseline forecast has been distributed to the individual planners. MFG1 Planner will plan the forecast for the
customer Computer Service and Rentals where as MFG2 Planner will plan the forecast for the customer AT&T
Universal Card.
Page 43
Oracle Demand Planning Achieve Consensus Forecast

Process/Procedures
Logon to the application Click on the XXODPPLAN
as MFG/welcome
Responsibility = Demand Planning worrksheet window appears.
Demand Plan Manager
Click on the New icon In the right pane, click on Choose Values from List icon on
(First icon) on the the document toolbar and select Measure
Navigation toolbar), Clear out default measures by moving them from the right
Select new WorkSheet side to the left side (using << icon). On left, highlight those
measures you want to be available as worksheets.
- For the baseline forecasts we will work with will be titled
Forecast of Shipment History-Shipped Items:Shipped
Date. Select that and click on the > button
- Product select AS66311, CM66321,CM66326 and
click on the > button
- Time Select 2005 and all the Qtr;s and Months for 2005
- Geography Select Computer Services and Rentals
and AT&T Universal Card and click on the > button
- Ship from Locoation Select M1 and click on the >
button
Worksheet should appear with the Baseline Forecast
displayed in Quantity. And it should look like this.
Page 44
Page 45
Page 46

Process/Procedures
Save Worksheet Click on Save as icon Save the Document as XXWSMGR
on the document toolbar
Logout and Log back in Click on the XXODPPLAN

as MFG1/welcome
Demand Planner Self-
Service
(First icon) on the h the document toolbar and select Time
Select new WorkSheet side to the left side (using << icon). On left, highlight 2005
and all the Qtr;s and Months for 2005 and click on the >
button
- Geography Select Computer Services and Rentals
Verify the results matches with previous step.
Save Worksheet Click on Save as icon Save the Document as XXWS001

Page 47
Page 48

Process/Procedures
as MFG2/welcome
Service
(First icon) on the h the document toolbar and select Time
Select new WorkSheet side to the left side (using << icon). On left, highlight 2005
and all the Qtr;s and Months for 2005 and click on the >
button
- Geography Select AT&T Universal Card and click on
the > button
Verify the results matches with previous step.

Page 49
Page 50

Process/Procedures
Change forecast values. Click in the cell Apr-2005 for Item AS66311 and enter the
At this point the Demand value 3000.and then click on Modify Selected Data then
Plan has been sent to the click on Fill and then click on the cancel button.
Demand Planners
Personal databases for
review/adjustment by the
Demand Planners.
Demand Planners can
update the baseline
forecast that has been
created based on
information the planner
has.
Page 51
Page 52

Process/Procedures
as MFG1/welcome
Service
Double click on the worksheet XXWS001
Change the Forecast quantity for the following Dates from
1786.51 to 2000, Please review the quantity for the month =
50,022.32.
14-FEB-2005 15-FEB-2005 (FEB or the current
month)
21-FEB-2005 22-FEB-2005
16-FEB-2005 17-FEB-2005
23-FEB-2005 24-FEB-2005
After the change the Forecast Quantity for the Month of Feb =
51,730.24 = (50,022.32 +(213.49 * 8))
Page 53
Page 54

Process/Procedures
as MFG1/welcome
Responsibility = Demand Planning worrksheet window appears. Double click
Demand Planner Self- on the worksheet.
Service
Click on the Tools icon in the Navigation toolbar then
CollaborateSend Measures
Select the Forecasr of Shipment History Shipped Item:
Shipped Date and click on the >
Send Option select Send entire assignment scope of

measure(s) radio button
Click Ok
Repeat this procedure of user MFG2.

as MFG/welcome
Demand Plan Manager on the worksheet.

CollaborateReceive Measures
Click Ok
Page 55

Process/Procedures
Verify that the following forcast quantities are visible in the
cells
1) Geography = Computer and Service Rentals
FEB-2005 = 51,730.23
2) ) Geography = AT&T Universal Card
APR-2005 = 3000.00
The Manager knows that there is Promotional demand for

AS66311 from AT&T Universal Card in the months of MAY
and JUNE 2005 for 8000 and 10000 respectively. So he
decides to update the forecast quantity.
May 2005 = 8000

June 2005 = 10000
Save the worksheet

CollaborateSend Measures
Page 56
Page 57
Page 58

Process/Procedures
as MFG2/welcome
Demand Planner Self- on the worksheet.
Service
CollaborateReceive Measures
Click Ok
Double click on the worksheet XXWS002
Click on Tools Submit Measures
Repeat this procedure of user MFG1.
Page 59
Page 60
Page 61

Process/Procedures
Logout and Log back in Demand Plan Click on the XXODPPLAN
as mfg/welcome Administration
Responsibility =
Demand Planning
Highlight the plane name Select Collect Data from Planners radio button
at top of the Demand
Plan Navigator Click apply
Upload Measures to Highlight the plane name Select Upload Measures to Planning Server radio button
Planning server at top of the Demand
Plan Navigator Click apply
Page 62
Advanced Supply Chain Plan Create and Launch Plan

Process/Procedures
Logout and Log back in Supply Chain Name = XXASCPPLAN
as mfg/welcome PlanNames Description = XX Test ASCP Plan
Responsibility =
Advanced Supply Chain Plan Options
Planner 1) Main Tab
Planned Items = Demand Schedule Items only
2) Organization Tab
Organization = TST:M!
Demand Schedule = SKTESTODP
Ship To Consumption Level = Customer
Launch the Plan
Log in the Planners and

the review the forecast
for the updates periods.
Page 63
Page 64
Page 65
Page 66
Page 67
Hierarchies used in the seeded Vision Demand Plans

Thanks to David Dosland for the following flowchart showing to Hierarchies used in the seeded Vision Demand Plan.
The document can be found at
http://globalxchange.oraclecorp.com/pls/gxchange/docs/PAGE/ROOTCORNER/KNOWLEDGEAREAS1/KNOWLEDGEAREAS/EBUSINESS_SUITE/EBSUITE/5101417088792818908
35/EBS_ADS_DEMO_SCRIPTS/ADS DEMODOCS_11510/DD_COREPRODUCTS_10/DD_SCP_10/ODP-HIERARCHIES 11510R1.10.
Page 68
Page 69
Page 70
Page 71
Page 72
Page 73
Page 74
Page 75
Page 76
Page 77
Page 78
Page 79
Page 80
Page 81
Page 82
Page 83
Page 84
Page 85
Page 86
Page 87
Page 88
Glossary
Aggregation - In Oracle Demand Planning, the consolidation of data for lower level dimension values into parent values.
Data is often collected at the lowest available level of detail and is aggregated into higher level totals for analysis. For
example, units sold in various cities might be aggregated into total units sold for all cities in a region. The aggregation rule
might be add, in which case the values are added, or there might be an alternate aggregation rule such as average.
Aggregation level In Oracle Demand Planning, the position in a dimension hierarchy at which data can be viewed or
manipulated. For example, aggregation levels for a Geography dimension might include City, County, State, Region, and
so forth.
Consensus forecast - Forecast generation by consultation among or consolidation of individual forecasts issued by
different groups within an organization.
Dimension - In Oracle Demand Planning, a list of categories for data. A dimension acts as an index for identifying the
values of a variable. Examples of dimensions are Product, Geography, and Time.
Dimension value - In Oracle Demand Planning, an element in the list that makes up a dimension. For example,
dimension values in the Geography dimension might include Boston, Chicago, and New York.
Hierarch - In Oracle Demand Planning, a means of organizing and structuring data within a dimension. A hierarchy exists
when values within a dimension are arranged in levels, with each level representing the aggregated total of the data from
the below. For example, a Geography dimension might have a hierarchy that includes levels for Account, City, State, and
Region.
Level - In Oracle Demand Planning, a position in a dimension hierarchy. Each level above the base level represents the
aggregated total of the data from the level below. For example a Geography dimension might have ascending levels such
as Customer, City, State, and Region. Within a dimension hierarchy, a dimension value at one level has a family
relationship with the dimension values at the levels above and below that level.
Measure In Oracle Demand Planning, a data variable that is a placeholder for storing or calculating data values for all
levels of all dimensions.
Page 89
OLAP - Abbreviation for Online Analytical Processing.
Personal database - In Oracle Demand Planning, the database to which a demand planner has modification rights. A
demand planner works in his or her personal database and submits final forecasts to the shared database.
Scenario - In Oracle Demand Planning, forecasts can be generated from multiple sources such as sales, management,
marketing, budget, constrained, and unconstrained.Forecasts from each source can also differ in scope, certainty,
expectation (for example, optimist versus pessimistic), aggregation level, time horizon, attributes, and so forth. Each
unique situation or function represents a scenario. Scenarios are set up and associated with a demand plan in the
Demand Planning Server. Planners submit a forecast for each scenario in the demand plan.
statistical forecast - Historical data are used to generate statistical forecasts in Oracle Demand Planning.The resultant
forecasts include an estimate of the forecast error.
Time dimension - In Oracle Demand Planning, a dimension whose values represent time periods. For example, values in
the time dimension could include the following:
Years such as 2003 and 2004
Quarters such as Quarter 1 - 2003 and Quarter 2 - 2003
Months such as February 2003 and March 2003
Page 90

Forecast 2 Plano DP 3

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Forecast 2 Plano DP 3

Transféré par

Droits d'auteur :

Formats disponibles

Oracle Advanced Supply Chain Planning R11i (Release 11.5.

FORECAST TO PLAN USING ORACLE

Prepared by Oracle Applications Manufacturing BDE

Copyright 2002 Oracle Corporation

You are using 11.5.10 version of Oracle Application.

Oracle Demand Planning Data Loader Steps

Step 1 Populate the MSD_ST_LEVEL_VALUES worksheet

1) All levels, 1 - 33 must be present with values.

Instance_id can be extracted from MSC_APPS_INSTANCES as follows

Level ID relating to Product Hierarchy

Level ID relating to Ship To Relationships

Level IDs relating to Sales Reps

Level IDs Relating to Sales Groups

Level IDs Relating to Sales Channel

LEVEL_ID LEVEL NAME SCRIPT TO EXTRACT SR_LEVEL_PK

Inventory > Setup > Organizations > Organizations

Inventory > Setup > Organizations > Organizations

Inventory > Setup > Organizations > Organizations

Since the primary key for this level value is not

Since the primary key for this level value is not

In this paper we will be using following information

Primary level key for level_id =3 (Item)

Primary level key for level_id =2 (Product Category)

Primary level key for level_id =3 (Product Family)

The worksheet entry would be as follows

Instance Level Id Level Value Sr Level PK

Step 2 Populate the MSD_ST_LEVEL_ASSOCIATIONS worksheet

The worksheet entry would look as follows

Level Value Parent Level Parent Level

Step 3 Populate the MSD_ST_SHIPMENT_DATA and/or MSD_ST_BOOKING_DATA worksheet

Instance = Instance_id from MSC_APPS_INSTANCES

Step 4 Populate the MSD_ST_PRICE_LIST to define the prices

Key for the worksheet

At this time we are not going to populate the MSD_ST_PRICE_LIST.

1. ftp the following files from the ODP.zip to the unix

2. Rename the following files

$ tr -d '\r' < msd_st_level_values.csv1 > msd_st_level_values.csv

4. Execute the following commands to populate the staging tables.

$ sqlplus apps/apps @refresh_stage.sql

Method II 11.5.10 Collect Flat File Data Self Service

To load data files using Self Service user interface:

To perform flat file loads:

Field Name Description

Field Name Description

Field Name Description

Add these three files to a zip file named as (Xxodptst.zip).

The following request are launched by this process

Oracle Demand Planning Running Data Pull

col INSTANCE format A4

select * from MSD_SHIPMENT_DATA;

Oracle Demand Planning Define Demand Plan

Oracle Navigation Path Specific step

This will list all the Demand Plans available.

Dimension User Dimension

Oracle Navigation Path Specific step

Dimension User Dimension

Input Parameters Tab Type = Shipmet History Shipped Items

Oracle Navigation Path Specific step

Verify the Lowest Time level for Manufacturing is Day

Oracle Navigation Path Specific step

With this process completed we have built the Demand Plan.

Oracle Demand Planning Generate Sales Forecast

Oracle Navigation Path Specific step