Вы находитесь на странице: 1из 41

Pak

SOP.10
STANDARD
OPERATING PROCEDURE
Avtec Ltd
Advanced
Planning
Creation Date
Last Updated
Document Name
Version

:
:
:

Supply

Chain

Mar 30, 2007


Standard Operating Procedures ASCP
:
1.0

Document Control
Change Record

Date

Author

Ver
sio
n

Change Reference

30-Mar05

P.Venkatesh Prabu

1.0

No previous document

Reviewers

Name

Position

Senthilkumar.C
Srinivas Maddipati
Saurabh Garg
Amit Gupta
L Ramanathan
Anand Aluru

Deputy Manager Machine Shop Avtec Ltd.


Manager Assembly Shop Avtec Ltd.
Deputy Manager Machine Shop Avtec Ltd.
Deputy Project Manager Avtec Ltd.
Project Manager Avtec Ltd.
Project Manager Birlasoft Ltd.

Copy
No.

Name

Location

Library Master
Anand Aluru

Project Library
Project Manager

Distribution

Contents

DOCUMENT CONTROL.........................................................................................................................2
1. INTRODUCTION............................................................................................................................4
1.1. Purpose....................................................................................................................................4
1.2. Overview..................................................................................................................................4
1.3. Planning Setup Activities.........................................................................................................5
1.4. Common Planning Transactions..............................................................................................5
2. PLANNING SETUP ACTIVITIES......................................................................................................6
2.1. Purpose....................................................................................................................................6
2.2. Overview..................................................................................................................................6
2.2.1 Sourcing Rules.......................................................................................................................6
2.2.2 To copy shipping organizations from an existing sourcing rule:............................................8
2.2.3 Create Assignment sets..........................................................................................................8
2.2.4 Viewing Sourcing Rules.........................................................................................................9
2.2.5 Displaying an Indented Where Used....................................................................................11
2.2.6 Setting Up Planner Workbench............................................................................................13
2.2.7 Start the Planning Manager.................................................................................................14
2.2.8 Define Planners...................................................................................................................17
3. COMMON PLANNING TRANSACTIONS.........................................................................................23
3.1. Purpose..................................................................................................................................23
3.2. Overview................................................................................................................................23
3.2.1 Planning Transactions.........................................................................................................23
3.2.2 Define Forecast...................................................................................................................23
3.2.3 Copying/Merging Forecasts.................................................................................................26
3.2.4 Forecast Consumption.........................................................................................................27
3.2.5 Master Demand Scheduling (MDS).....................................................................................28
3.2.6 Defining Schedule Entries Manually...................................................................................29
3.2.7 Loading a Master Schedule.................................................................................................30
3.2.8 Running Data Collections ...................................................................................................31
3.2.9 Defining ASCP name ..........................................................................................................32
3.2.10 Define ASCP plan Options ................................................................................................33
3.2.11 Launch ASCP.....................................................................................................................34
3.2.12 Review Plan from Planners workbench ............................................................................37
3.2.13 Launch Planning Detail Report ........................................................................................39
3.2.14............................................................................................................................................41
3.2.15............................................................................................................................................43
3.2.16............................................................................................................................................44
3.2.17............................................................................................................................................44
3.2.18 ...........................................................................................................................................45
3.2.19............................................................................................................................................47
3.2.20............................................................................................................................................48

1. Introduction
1.1. Purpose
This document is aimed towards providing the operating procedures for carrying out
Planning operations in AVTEC using Oracle Planning and helping AVTEC use Oracle
Planning for efficient transaction processing and information retrieval for meaningful
analysis of data.

1.2. Overview
The Planning process flows for various Planning transactions have already been discussed
and detailed in the BP.080 Oracle Planning document, right from inception to conclusion
of each process, highlighting the control aspects at each stage of the process for the
following Planning operations:

Forecast definition

Master demand schedule

Launch Data Collections

Launch Advance supply Chain Planning Process

Review of the ASCP plan from Planners Work Bench

Launch Planning Detail report

This document attempts to provide step-by step guidelines on how the same processes
will be carried out in Planning module. For each of the processes, Overview is provided,
followed by Process Prerequisites. Subsequently, the various activities that need to be
carried out for the process are covered in detail along with navigation path, relevant
screenshots and general information / guidance for the process under Transaction
Details. In addition, this document also provides a list of relevant reports along with brief
report functionality at the end of each section.
In addition to the above, this document also outlines critical setup activities carried out in
Oracle Planning.
This document has to be read in conjunction with Oracle Planning User Guide and BP.080
Oracle Planning submitted as part of the Implementation. Oracle Planning User Guide
provides the details on standard functionality as available in Oracle Planning. The BP.080
Oracle Planning document provides the details of the standard Oracle Planning
functionality as relevant to and used by AVTEC & MD.050 provides additional functionality
(through custom development) with reference to the Business Processes.
The various setup activities and Planning transactions carried out in AVTEC have been
classified into:

Setup Activities

Common Planning Transactions

In addition, this document also covers common processes that will be followed for
Planning management in AVTEC.

1.3. Planning Setup Activities


The following setup activities are covered later in the document:

Define Source Lists


Create your Assignment Sets
Define your Sourcing Rules
Start the Planning Manager

1.4. Common Planning Transactions


The Planning transactions, which are performed at Plant:

Define your Forecast Sets

Define your MDS Names

Load MDS

Launch Data Collections

Define an ASCP name

Define ASCP Plan Options

2. Planning Setup Activities


2.1. Purpose
This section provides the details on critical Oracle Planning setup activities as outlined
earlier.

2.2. Overview

Define your Sourcing Rules

Create your Assignment Sets

Define Source lists

Setting Up Planner Workbench

Start the Planning Manager

Define Planners

2.2.1 Sourcing Rules


NavigationSupply chain planningSourcingSourcing rules

You can define sourcing rules that specify how to replenish items in an organization, such
as purchased items in plants. Sourcing rules can also specify how to replenish all
organizations, as when the entire enterprise gets a subassembly from a particular
organization.

Navigate to the Sourcing Rule window.


Enter a unique sourcing rule name.
Indicate whether this sourcing rule is used for all organizations (global) or a single
organization (local).
If the sourcing rule is local, you must enter an organization name; otherwise, your
current organization will be the receiving organization.
Choose Copy From to copy the effectivity dates and shipping organization from
another sourcing rule into this one.
Enter effectivity dates. You must enter a start date, but entering an end date is
optional. For each range of effectivity dates, you can include multiple shipping
organizations. For each shipping organization you want to include, select a
sourcing type to specify whether you make, buy, or internally transfer the item.
You can also copy a list of shipping organizations from an existing sourcing rule.
If you enter a customer organization as the receiving organization, then you
cannot select a supplier organization as the shipping organization.
Enter an allocation percentage for each shipping organization. Allocation
percentage includes the number of planned orders issued to the part for the entire
the planning horizon. Your total allocation may not exceed 100.
If the allocation percentage for all the shipping organizations included within a
range of effectivity dates equals 100, Planning Active is checked. If the sourcing
rule is not planning active, the planning process will not use the rule to assign
planned orders.

Note: You cannot set the allocation percentage to less than or greater than 100
for sourcing rules that are already assigned in assignment sets.

Enter a numeric rank value to prioritize each sourcing type.


Select a shipping method
Save your work.

2.2.2 To Copy Shipping Organizations from an Existing


Sourcing rule:
NavigationSupply chain planningSourcingSourcing rules

This feature allows you to include long, previously defined lists of shipping
organizations without manual entry.
Select a sourcing type to specify whether you make, buy, or internally transfer the
item.
Choose Copy Shipping Orgs From.
In the Find window, select a sourcing rule that includes the shipping organizations
you want to duplicate in this new sourcing rule.
Choose OK.

2.2.3 Create Assignment sets


Once you have defined your sourcing rules, you must assign them to particular items
and/or organizations. These assignments are grouped together in assignment sets. This is
where your various sourcing strategies define a particular supply chain network. Each
assignment set to represents selection of organizations and/or items you want planned.
To influence the planning process, you must include an assignment set in your plan
options.
In an assignment set can assign your sourcing rules at different levels, as follows:

An item across all organizations


A single item in an inventory organization
All items in an inventory organization
Categories of items
Categories of items in an inventory organization

All organizations

NavigationSupply chain planningsourcingassign sourcing rule /BOD

Navigate to the Sourcing Rule/Bill of Distribution Assignments window.


Enter an assignment set name and description.
Select an Assigned To type
Enter an organization name, if the Assigned To type requires one.
Enter the name of the customer to which you want to assign a sourcing rule or
bill of distribution.
Enter the specific site to which you want to assign a sourcing rule or bill of
distribution.
Enter an Item/Category if you selected Item or ItemOrg as the Assign To type.
Enter the sourcing rule or bill of distribution as the Type.
Enter the name of the sourcing rule or bill of distribution.
Save your work.

2.2.4 Viewing Sourcing Rules


You can quickly and easily retrieve sourcing rules for reference. After retrieving a sourcing
rule, you can display it in a convenient, hierarchical representation, or you can locate the
assignment sets in

which it is assigned.

NavigationSupply chain planningsourcingview sourcing rules

Navigate to the View Sourcing Rule or Sourcing Rule window


Place your cursor in the Name or Description field and select Find or Find All from
the Query menu.
Choose View to launch the Object Navigator and display the graphical view of your
sourcing rule.

With the Object Navigator, you can display your sourcing rule in a visual hierarchy. Each
element in the sourcing rule is displayed in a rectangular node, with connecting lines that
depict the nodes
relationships to each another (known as the data flow). The nodes are also colorcoded
for easy identification, and other aspects of the data flow can be changed to meet
specific requirements.

2.2.5 Displaying an Indented Where Used


To display an indented where used information for an item:
NavigationSupply chain planningsourcingassign sourcing rule /BOD
Navigate to the View Supply Chain Bill window.

Enter the name of an assignment set.


Enter an organization.
Enter an item and date.
Choose View Indented Where Used to launch the Object Navigator and display the
graphical view of items indented where used information.

Viewing the Sourcing Assignment Hierarchy


Use this window to display all the assignment levels and identify the active assignment
level.

Navigate to the View Supply Chain Bill window.


Enter the name of an assignment set.
Enter an organization.
Enter an item and date.
Choose View Sourcing Hierarchy.

2.2.6 Setting Up Planner Workbench


Defining Display Preferences

Display preferences control what horizontal material planning data, horizontal capacity
planning data, and supply/demand detail are displayed for each item.
NavigationSupply chain planningMPSWorkbench
Go to the tool bar and then click on Preferences

Navigate to the Preferences window from the Tools menu.


Choose the Horizontal Material Plan tabbed region.
Enter Display Bucket Type, Display Factor, Decimal Places, Field Width,
Independent Demand Type, and, optionally, Source List to define the way data is
displayed in the Horizontal Material Plan window.
Check each type of plan information you want displayed in your horizontal plan.
Choose the Horizontal Capacity Planning tabbed region.
Check each type of plan information you want displayed in your horizontal
capacity plan.
Choose the Supply/Demand tabbed region.
In the Supply/Demand tabbed region, enter a Cutoff Date, and Default Job Status.
When the Planner Workbench creates discrete jobs from implemented planned
orders, it assigns the job status you enter in the Preferences window.
Select a Default Job Class. When the Planner Workbench creates discrete jobs from
implemented planned orders, it assigns the job class you enter in the Preferences
window.
Select a Requisition Load By default. When the Planner Workbench creates
purchase requisitions from implemented planned orders, it assigns the requisition
load group you enter in the Preferences window.
Choose Save to use and save your preference selections for current and
subsequent sessions.
Choose Apply to use your preference selections for the current session only.

Choose Reset to use your previously saved selections.

2.2.7 Start the Planning Manager


The Planning Manager controls a continuous background process that periodically
activates for all organizations. It differs from a normal process in that you need to start it
only once. This process is activated based on the processing interval you define.
Once activated, the Planning Manager executes several maintenance tasks. For example,
the Planning Manager performs forecast consumption, MDS shipment relief, MPS schedule
relief, and forecast and master schedule imports.
Attention: You should activate the Planning Manager and leave it running. The Planning
Manager performs maintenance tasks vital to the proper operation of Oracle Master
Scheduling/MRP and Supply Chain Planning.
Suggestion: When it operates, the Planning Manager may run for a very short time only,
making it difficult to determine whether it is running. To be sure, examine the log file for
the concurrent request of the Planning Manager to verify that it is active.
NavigationSupply chain planningSetupPlanning manager

Navigate to the Planning Manager window.


Enter the Processing Interval for the Planning Manager. Once you start the
Planning Manager, maintenance tasks are executed based on this interval.
Choose Start to start the Planning Manager for all organizations by issuing a
request to the concurrent manager.
The Planning Manager executes tasks periodically, based on the Processing
Interval you entered.
Review the date and time you sent the request to the concurrent manager to start
the Planning Manager.

If an error occurs during the Planning Manager maintenance tasks, the date and
time of the error is displayed.
Review the Planning Manager Message associated with the date:
Started: The Planning Manager is started. The processing interval and request
identifier sent to the concurrent manager to start the Planning Manager are
displayed.
Error: An error occurred during one of the Planning Manager maintenance tasks.
Use the error message information, along with your system administrator or
Oracle Customer Support, to help
diagnose the error. After you have diagnosed and corrected the error, you must
restart the Planning Manager.
Launched: The Planning Manager launched the daily cleanup worker.

2.2.8 Define Planners


You can define and update material planners or planning entities for the current
organization and assign them to inventory items at the organization level.
NavigationIndia InventorySetupPlanners

To define and update material planners or planning entities:

Navigate to the Planners window.


Enter a unique planner name.
A planner can be a person or an entity, such as a department or a division.
Enter the electronic mail address of the planner. Optionally, enter a date on which
the planner becomes inactive.
From this date on, you cannot assign this planner to an inventory item.
Save your work.

3. Common Planning Transactions


3.1. Purpose
This section provides the details of common Planning transactions in AVTEC.

3.2. Overview

Define your Forecast Sets


Define your MDS Names
Load MDS

Define Instances

Run Collection Plans

Define Your ASCP Name

Run ASCP

Run Planning Detail report

3.2.1 Planning Transactions


Planning Data Collection in Work in Process
Plannings integration with other modules like Inventory, BoM, WIP, Purchasing and Order
management enables you to collect vital data for Materials planning purposes and
Production scheduling.

3.2.2 Define Forecast


Forecasts and Sets: Forecast sets consist of one or more forecasts. Sets group
complimenting forecasts into a meaningful whole.
Forecast Set Defaults: Each forecast inherits the forecast level, consumption options,
and other defaults defined for the set. You can override these defaults for each forecast in
a set.
Time Buckets: You can forecast with daily buckets in the short term, weekly buckets in
the midterm, and periodic buckets in the longer term.
Entry Options: You can define a forecast for a particular item by entering a single date
and quantity. You can also specify a start and end date, and a quantity.
Alternate Bills: You can associate alternate bills of material to multiple forecasts for the
same item, exploding different components, usages, and planning percentages.
Consumption: You can manually or automatically consume forecasted demand with
sales order (actual) demand.

Consume by Demand Class: You can define demand classes that represent groupings
of similar
customers or order types. This allows you to consume forecasts by sales orders of a
specific demand class, for example.
Copy: To help manage and consolidate your forecast information, you can create new
forecasts from existing forecasts or forecast sets. You can copy forecasts from your own
organization or from any other organization.
Modify for Simulation: You can use modification factors and/or carry forward days to
modify existing forecasts. This allows you to quickly generate forecasts, for simulation
purposes, for the same collection of items using modified forecast dates and quantities.
Deleting Forecasts and Forecast Sets: You can delete forecast and forecast sets.
Before you can delete forecast sets, you must delete all forecasts contained within the
set.
Attention: Deleting removes the forecasts, forecast sets, and all related information
from the database. You cannot view or report on forecasts and forecast sets once you
delete them.
Defining a Forecast Manually
NavigationSupply chain planningForecastSets

Navigate to the Forecast Sets window.


Enter a unique name.
Select a bucket type to group forecast entries by days, weeks, or accounting
periods.
Select the level that determines how forecasts in the set are defined and
consumed.
ShipTo: Item, customer, and shipping identifier
BillTo: Item, customer, and billing identifier
Customer: Item and customer

Item: This is the only option available if you are not using Oracle Order
Management or Oracle Receivables.
Select consumption options. If you turn consumption on, sales orders you create
consume forecast entries in this set.
The outlier update is the maximum percentage of a forecast entry that a single
sales order can consume.
Forward and backward days describe the number of work dates from the sales
order schedule date that forecast consumption looks backward or forward for a
forecast entry to consume. Nonworkdays are not counted in these calculations.
Save your work.
o
Attention: All the items within a forecast set are shown including over
consumption when this window is accessed in the view mode through the Inquiry
menu. However, only over consumed items are shown when you access the
Forecast Set Items window through the Forecast Sets window.
To disable a forecast set:

Enter a disable date. After this date, you can no longer define a forecast name for
the set. You can view disabled forecasts but not modify them.

To define a forecast:
NavigationSupply chain planningForecastSets and then press on the Forecast
items on the above form.

Choose the Forecast Items button to open the Forecast Items window.
Enter an item.
Choose the Detail button to open the Forecast Entries window.
Select a bucket type of days, weeks, or accounting periods.

Enter a date. This is typically the date you expect to ship the item or the
beginning of the week or period that you expect to ship the item.
Enter an optional end Date. This creates forecast entries of the same quantity for
each day, week, or period until the end date. A forecast entry without an end date
is valid just for the date and time bucket specified.
Enter a current quantity. This also becomes the original quantity and the total.
Forecast consumption reduces the current quantity.
Forecast consumption plus the current quantity equals the total.
Enter an optional confidence percentage that the forecasted item will become
actual demand. Oracle Master Scheduling/MRP and Supply Chain Planning multiply
this percentage by the forecast quantity when you load it into a master schedule.
Save your work.

3.2.3 Copying/Merging Forecasts


You can copy forecasts from within your own organization, from any other organization, or
from any focus or statistical forecast.
You can modify existing forecasts while merging them into new ones. This allows you to
forecast (for simulation purposes) the same collection of items, but with altered forecast
rates and percentages,
using a series of modification factors and/or carry forward days.
NavigationSupply chain planningForecastCopy

Navigate to the Copy/Merge Forecast window.


In the Parameters window, select a destination forecast and source type:

Forecast Source List: A source list defined in the Source Lists window.
Specific Forecast: One of your forecasts.
Select the forecast organization.
Select the forecast/load source list. Select either one of your source lists or one of
your forecasts, according to the source type you selected above.
Select an Overwrite option:
All Entries: Deletes everything on the forecast before merging new information.
No: Deletes nothing and adds new entries to existing entries during the merge.
Schedule entries are not combined. You can get multiple forecast entries for the
same item on the same day.
Same Source Only: Deletes the entries that have the same source as those you
merge. You can replace entries on the forecast that were previously loaded from
the same source without affecting other entries on the forecast.
Enter the start and cutoff dates for the forecast merge. Forecast entries are
merged from the start date to the cutoff date. If you specify carry forward days,
the number of days is subtracted from the cutoff date so that all merged entries
have dates before the cutoff date.
Select the explode option.
Select the quantity type:
Current: The current forecast quantity is the original forecast quantity minus any
consumption quantities. When you choose this option, you cannot choose to
consume the forecast since the forecast quantities already reflect sales order
demand that has been placed.
Original: This is the quantity of the forecast without any consumption. When you
choose this option, you should choose to consume the forecast if you intend to
generate a master schedule using forecasts and sales orders. Consuming the
original forecast ensures that demand is not overstated by balancing the forecast
and sales order demand.
Select the consume option.
Select the modification percent.
Enter the number of carry forward days.
Choose OK.
In the Copy/Merge Forecast window, choose Submit.

3.2.4 Forecast Consumption


Forecast consumption replaces forecasted demand with actual sales order demand. Each
time you create a sales order line, you create actual demand. If the actual demand is
already forecasted, the forecast demand must be decremented by the sales order
quantity to avoid counting the same demand twice.
The Planning Manager is a background concurrent process that performs automatic
forecast consumption as you create sales orders.
Forecast consumption relieves forecast items based on the sales order line schedule date.
When an exact date match is found, consumption decrements the forecast entry by the
sales orders quantity. Other factors that may affect the forecast consumption process are
backward and forward consumption days and forecast bucket type.

3.2.5 Master Demand Scheduling (MDS)


The MDS is a statement of demand and contains details of the anticipated shipment
schedule. You can consolidate all sources of demand into a master demand schedule to
represent a statement of
total anticipated shipments. The master demand schedule provides an extra level of
control that allows you to view and modify your statement of demand before creating a
detailed production schedule.
You can use the timephased master demand schedule as input to the master production
scheduling process or the material requirements planning process.
NavigationSupply chain planningMDSNames

Navigate to the Master Demand Schedules or Master Production


Schedules window (MDS Names and MPS Names in the menu).
Enter a name and description. Optionally, select a demand class.
Save your work.
You can now define a master schedule manually, or load a schedule from another
source, with the name(s) you created.
Check Relieve to relieve schedule entries.
For master demand schedules, all sales order shipments relieve the appropriate
schedule entries (shipment relief). For master production schedules, when you
create discrete jobs, flow schedules, purchase orders, or purchase requisitions,
you relieve schedule entries (production relief).
If you associate a demand class with your schedule, the relief process updates
those schedule entries whose demand class matches a sales order, discrete job,
flow schedule, purchase order, or purchase requisition.
Save your work.

To disable a schedule name:


Note: You can view disabled schedules but not modify them.

Navigate to the Master Demand Schedules or Master Production Schedules


window.
Query a schedule name.
Enter an inactiveon date.
Save your work.

3.2.6 Defining Schedule Entries Manually


A schedule entry is a unique relationship between an item, date, and quantity on a
master schedule. You define schedule entries by adding items to schedule names, then
defining detailed date and quantity information for each item.
NavigationSupply chain planningMDSItems

Navigate to the Master Demand Schedules or Master Production


Schedules window (MDS Names or MPS Names in the menu).
Select a schedule name.
Choose Items to open the Master Demand Schedule Items or Master Production
Schedule Items window.
Enter an item with an MRP planning method of MPS Planning.
Enter a different MPS explosion level, if you want to change the default.
Choose Detail to open the Master Demand Schedule Entries window or Master
Production Schedule Entries window.
Enter a date.
For MDS, this is the date of shipment. For an MPS, this is the completion date of
production.
Enter a current quantity.
This also becomes the original quantity and the total. Schedule relief reduces the
current quantity. Schedule relief plus the current quantity equals the total.

Check Relief if you want this entry to be decremented when you create purchase
orders, purchase requisitions or discrete jobswhether you define the purchase
requisitions or jobs manually or load them with the Planner Workbench.
Save your work.

3.2.7 Loading a Master Schedule


NavigationSupply chain planningMDSLoad/Copy/Merge

Navigate to the Load/Copy/Merge Master Demand Schedule or Load/Copy/Merge


Master Production Schedule window.
In the Parameters window, enter a destination schedule.
Select a source type
Select a source organization.
Select source name.
Select whether to include sales orders or not
Select the Demand class if required (based on the requirement)
Select a start date and a cutoff date.
Select from a number of load options.
Choose Submit Request.

3.2.8 Running Data Collections


Define Instances from the Advance Planning Administrator menu
Navigation Advance Supply Chain PlannerCollections Oracle Systems
Standard Collections

The above window shows you that the collections process consists of two
sequentially executed concurrent programs.
The first program, Planning Data Pull, copies information from the source instance
into the APS staging tables on the planning server.
The second program, Planning ODS Load, copies information from the APS staging
tables into the operation data store on the planning server, where it becomes
available for use during planning
Data Collection is a pre-requisite process for Plan Launch/execution.
Data Collection takes a snapshot of demand/Supply/transaction/Setup data from
ERP system and stores that in planning system.
Data collection has to be launched before plan run to get the latest picture of
Demand/Supply

There are three collection methods:

The Complete Refresh method clears all transaction data for all business entities
from the planning server (for the source instance being collected), and then copies
over information about the user-selected entities. This method can be time
consuming.
The Net Change Refresh method copies only incremental changes to business
entities to the planning server (and is thus faster), but is supported mainly for
demand and supply business entities only.
The Targeted Refresh method clears transaction data for only the user-selected
business entities from the planning server, and then copies the entity information
over from the transaction instance. Information about non-selected entities
remains intact on the planning server. All planning business entities are supported
by Targeted Refresh collections

When To Use Each Collection Method

You should use Complete Refresh the first time you perform collections from a
source instance to the planning server. You may also wish to use complete refresh
collections after a significant proportion of the setup data in your transaction
system has been altered, and you would like to make a fresh copy of all source
instance business entities (items, bills of material, sourcing rules, resources, and
so on) on the planning server. You typically collect all business entities in a
Complete Refresh Collection.

You should use Net Change Refresh if you would like to update the supply and
demand picture on the planning server as quickly as possible, and the incremental
changes to supply and demand in the source instance since the last collection
have not been extensive relative to the existing (already collected) body of supply
and demand information. In this case, Net Change Refresh is the fastest way to
achieve the desired update of the planning server operational data store, because
it copies over from the source instance only the incremental changes in supply
and demand since the last collection.

You should use Targeted Refresh if you would like to update the planning server
information for some (but not all) business entities, and some of these entities fall
outside the category of supply and demand entities supported by Net Change
Refresh. For example, to update the planning server with a newly rebuilt
manufacturing calendar, you would run Targeted Refresh collections for just the
calendar business entity. Data on the planning server about all other business
entities would remain unaffected by this collection.

You would also use Targeted Refresh (in lieu of Net Change Refresh) to bring
over the latest picture of supply and demand to the planning server in cases when
the incremental changes to supply and demand on the source instance since the
last collection are very extensive. In this case, the update mechanism employed
by Targeted Refresh collections (wholesale deletion followed by rebuilding of data
on the planning server) is faster than the mechanism employed by Net Change
Refresh collections (incremental insertions into existing data on the planning
server)

Select the Parameters field for the Planning Data Pull Program

Parameters
Instance: Source instance code from list of values.
Number of Workers: One or greater. Increase this number to increase the
amount of computational resources to devote to the Planning Data Pull process.
This allows you to specify the number of workers for the Data Pull, which can now
be different from the number of workers specified for the ODS load process.
Timeout (Minutes): The maximum amount of time you would like to allocate to
the Planning Data Pull process. If the Planning Data Pull process has not
completed within this amount of time, it will be terminated with an error.
Purge Previously Collected Data Yes (default) or No. Setting this to Yes wipes
out all data in the APS planning server operational data store associated with the
selected source instance as the first step in the collections process. If you set this
to
Yes, the only allowable collection method is Complete Refresh. If you set this to
No, the allowable collection methods are Targeted Replacement and Net Change.
Collection Method Complete: Refresh/Targeted Refresh/Net Change Refresh.
Analyze Staging Tables: Yes or No (default). Set this to Yes periodically to
recompute database access statistics on the APS staging tables. This speeds up
the subsequent Planning ODS Load process.
The remaining parameters in the Planning Data Pull Parameters are a list of
business entities. Selecting Yes for an entity means collect the information for that
entity over from the source instance. Selecting No for an entity means don't
collect the information for that entity over from the source instance

Select OK

Select the Parameters field for the Planning ODS Load program

Following parameters should be selected

Instance: Source instance code


Timeout (Minutes): Number of minutes before the concurrent program will end.
Number of Workers: One or greater. Increase this number to increase the
amount of computational resources to devote to the Planning ODS Load process.
Recalculate Resource Availability: This defaults to the value (Yes or No) that
you set for the Resources Availability business entity in the Planning Data Pull
Parameters window. The value that you set here is the one that actually
determines whether resources availability is collected or not.
Recalculate Sourcing History: This defaults to the value (Yes or No) that you
set for the Sourcing History business entity in the Planning Data Pull Parameters
window. The value that you set here is the one that actually determines whether
sourcing history is collected or not. If you select Yes, then ASCP will collect all new
sourcing history not already on the planning server in the time range [(today - x
months) through (today)] from the source transaction system. The number x is
given by the value that you set for the profile option MSC: Sourcing History Start
Date Offset (in months). During planning, ASCP will use the total cumulative
sourcing history on the planning server in addition to the planned sourcing in the
plan to determine whether sourcing percentages in sourcing rules are being
respected or not.
Purge Sourcing History: Valid values are Yes and No (default). If you select Yes,
then all sourcing history present on the planning server will be deleted before the
collection process commences.
Select OK.

Select Submit in the Planning Data Collection window to run collections


immediately, or select Schedule to schedule collections for some later time.
Viewing the Collected data: We can view the collected data in Data Collection
Workbench

3.2.9 Define ASCP Name


Navigation Advance Supply Chain PlannerSupply Chain Plan Names

Name: Define a plan name.


Description: Define a plan description.
ATP: If this is checked, this means that this plan will be used for availability check.
Production: If this is checked, this means that this is a product plan. Planned
orders will be automatically released within their Release time fence (set on item
Master).
Plan Type: Valid values are Manufacturing Plan, Production Plan, and Distribution
Plan. This setting interacts with the Planning Method item attribute to determine
which subset of the items that pass the condition imposed by the Planned Items
parameter will in fact be planned. Select Production Plan if you want to enable
Auto release of Planned orders and planned requisitions
Attached here the XL sheet for the combination rule for the plan type
and the plan option

C:\Documents and
Settings\erp\Desktop\ASCP plan Options Imp.xls

3.2.10 Define ASCP Plan Options


Navigation Advance
Supply Chain PlannerSupply Chain Plan
NamesPlan Options
This section describes how to set plan options. In the plan options forms, plan options are
organized as follows:
Main
Aggregation

Organizations
We are not including Constraints, Optimization and Decision rules

Main

Main Tab region:

Planned Items: This parameter and the Plan Type field in the Supply Chain
Names window, control the items that are planned in the Supply chain plan. An
item must satisfy conditions imposed by both parameters before being included in
the supply chain plan.
Material scheduling Method: Choose from Operation Start Date or Order Start
Date scheduling methods. If you choose Operation Start Date, material is
scheduled to arrive at the start of the operation for which it is required. If you
choose Order Start Date, material is scheduled to arrive at the start of the order
for which it is required. Order State Date is usually an earlier date than the
Operation Start Date and therefore this selection represents the more
conservative planning logic of the two options.
Assignment Set: The assignment set that holds the sourcing rules and bills of
distribution that define the rules for material flow within your supply chain.
Demand Priority Rule: When ASCP does detailed scheduling, it schedules
demands one by one. The rule specified here dictates the order in which demands
will be considered during detailed scheduling, and thus which demands will get
the first opportunities to take up available materials and resource capacities. You
can set up different Priority rules in the setup based scheduled date/Request
date/promise date/Gross margins.
Overwrite: Overwrite planned orders.

Append Planned Orders: Appends new planned orders to current plan. Various
combination of Overwrite and Append Planned orders and its impact is discussed
separately at the end of the section
Demand Class: If you are creating a Production Plan, enter the appropriate
demand class. This field is active only for a Production Plan.
Demand Time Fence control: Check this option to enforce demand time fence
control.
Planning Time Fence Control: Check this option to enforce planning time fence
control.
Lot for Lot: Check this option to force the creation of a separate supply for each
demand. This prevents the creation of aggregate supplies that satisfy multiple
demands, and overrides order quantity modifiers such as Minimum Lot Size and
Fixed Lot Multiple. It is not advisable, as it will create multiple planned orders
ignoring economies of scale
Enable Pegging: Check this option to calculate pegging information. Oracle ASCP
traces supply information for an item to its corresponding end demand details,
which you can then view in a graphical display. This field is checked by default.
Peg Supplies by Demand by Demand Priority: Priority Check this option to
calculate pegging so that supplies are pegged to demands in demand priority
order (as defined by you in a priority rule) within the time period set by the profile
option MSO: Firm Supply Allocation Window (days).
Pegging Reservation Level: None
Pegging-Hard Pegging level: None

Aggregation Tab

Plan Start date: This is a view-only field, whose value equals the start date of
the plan if the plan has already been run. Otherwise, it defaults to the system
date.
Plan End Date: Shows the calculated end date for your plan. This is a view-only
field, calculated based on the bucket sizes you specify.
Bucket Start dates: These are calculated based the numbers you enter for Daily
bucket/Weekly Bucket/Period Bucket

Item: Choose to plan at either the Item level or Product Family level. If you select
Items in the first bucket, the other buckets can be set to either Items or Product
Family. However, if you select Product Family in the first bucket, the remaining
buckets are set to Product Family by default. Choose Item.
Resource: Choose to plan at either the Individual level or Aggregate level. You
should select Resource if capacity planning needs to be done.
Routing: Choose to plan at either the Routings or BOR (Bill of Resource) level.
Routing should be selected if operation level scheduling needs to be done

Organization Tab

Organization: Select the Inventory Organization, which you want to consider


for planning. You can select more that one organization
Demand Schedules: Select one or more demand Schedules as a source of
demand for the Plan
Supply Schedule: You can also include MPS (Master Production Schedule) as
a Demand.
Sub inventory Netting: This will include all the nettable sub inventories in
the organization. You can check/Uncheck few sub-inventories for plan level
control
Net WIP: Select to consider discrete jobs and other production orders as
supply in the planning demand/supply netting process.
Net Reservations: If checked, ASCP generates pegging of on-hand supply to
sales orders that matches the reservations recorded in the source transaction
system.

Net Purchases: Select to consider purchase orders, purchase requisitions, intransit shipments and other nonproduction order scheduled receipts as supply
in the planning demand/supply netting process. This option covers all
scheduled receipts not covered by the Net WIP option.
Plan Safety Stock: Check if the planning for Safety stock is to be done
Include Sales Order: Select to invoke forecast consumption within ASCP for
the selected organization. Check this if the demand schedules for the
organization are unconsumed forecasts.

3.2.11 Launching the Advanced Supply Chain Planning


Process
Navigation Advance Supply Chain PlannerSupply Chain Plan
NamesLaunch Plan

Launching a supply chain plan is relatively a simple process once you finish Data
collection and setup plan options as per Business requirement. Frequency of
launching a plan is a business decision. Many businesses run a plan daily to
capture daily changes in the supply and demand across the Supply Chain.
To Launch the Plan
Go to Supply Chain Plan> Launch Plan. Following Request window will open.
Click OK>Submit to launch the plan.
Running of Plan may take some time depending upon the volume of data and
nature of plan. Once the plan run is finished, you can view the plan results in
Planner Workbench

3.2.12 Review Plan From Planners Workbench


Navigation Advance Supply Chain PlannerSupply Chain Plan Workbench

The above figure represents the workbench information and the


recommendations for the discrete jobs

How the Supply demand widow opened for the releases to get created or in
the bottom we have one more tab Marked to call supply demand window

Supply and demand Window

When Planned Orders Released

Orders Released from workbench

Shortages and Excess related exceptions

Items with a shortage : This exception shows an item whose quantity on hand is less than the sum
of the requirements plus safety stock, within the exception time fence defined by the items planning
exception set,Generation: On some days, the item may have more demand than it
has supply. Therefore, you cannot satisfy all the demand on those days. To
determine if this exception exists, the planning process performs the gross-to-net
explosion. The planning process does not issue this exception if it has solved the
shortage by recommending creating new orders,Action/Resolution: Usually, this
exception occurs within a planning time fence (and lead time in a constrained
plan); you should consider reviewing and correcting supply/demand imbalances
inside the planning time fence.

Items below safety stock :This exception shows an item for which demand, less supply, brings the
projected quantity on hand to a negative level or below safety stock. This exception is different from
the Items with a shortage exception because the Planning Exception Set is not involved in the
generation of this exception.Generation: On some days, the item has less
inventory than the specified safety stock level. If the quantity remains constant for
a period of days, then there will be a date range provided for this exception
message,Action/Resolution: You should consider expediting scheduled receipts.

Items with excess inventory : This exception shows an item whose quantity on
hand exceeds (as defined in excess quantity items planning exception set) the
total requirements against the item, within the exception time fence defined by
the items planning exception set.Generation: On some days, the item has more
inventories than it needs to satisfy demand. If the quantity remains constant for a
period of days then there will be a date range provided for this exception
message.Action/Resolution: You should consider canceling unneeded scheduled
receipts or transferring the material to another facility.

Reschedules Recommendations

Past due orders: This exception shows an item with planned orders, discrete
jobs, and purchase orders that are past due.Generation: For discrete material
only, the planning process has found at least one planned order for an item in
which both the needed start date and the needed due date are in the past. The
planning process recommends the planned order to start and be due on the date
that the planning process is executed (planning start date).Action/Resolution:
For discrete material planning only, you should consider checking the demand that
resulted in this planned order and either arrange to change the demand and
supply due dates or prepare to expedite the scheduled receipt that you create
from this planned order.

Orders to be rescheduled out :This exception shows an item with work orders
that is recommended to be rescheduled to a later date by the planning
process.Generation: For discrete material only, the planning process found a
scheduled receipt for an item for which the suggested due date is greater than the
due date of the order. It suggest new due date for the work
order.Action/Resolution: For discrete material planning only, you should
consider reviewing the recommendations for this item. The Planning system
assumes that the recommendation/action will be taken. You can implement this
from planning workbench by releasing it.

Orders to be cancelled :This exception shows an item with orders that is


recommended to be cancelled by the planning process. Generation: For discrete
material only, the planning process found a scheduled receipt for an item for
which it does not have demands.Action/Resolution: For discrete material
planning only, you should consider reviewing the recommendations for this item.
The Planning system assumes that the recommendation/action will be taken. You
can cancel these orders as suggested by a plan.

Orders to be rescheduled in :This exception shows an item with orders that is


recommended to be rescheduled to an earlier date by the planning
process.Generation: For discrete material only, the planning process found a
scheduled receipt for an item for which the suggested due date is prior to the due
date of the order.Action/Resolution: For discrete material planning only, you
should consider reviewing the recommendations for this item. The Planning
system assumes that the recommendation/action will be taken. You can
implement this by releasing it from workbench

Orders with compression days:This exception shows an item with planned


orders, discrete jobs, and purchase orders that have compression days and need
to be expedited.Generation: For discrete material, the planning process found a
planned order/supply for an item for which the suggested order date is in the past.
That is, items lead-time is being violated. The planning process recommends the
planned order/supply to start (order date) on the date that the planning process is
executed (SYSDATE). It assigns one compression day for each workday between
the suggested order date and the date that the planning process is executed and
then issues this exception. For example, if a planned order due date is Friday, the
lead time offset for this item is three days (Thursday, Wednesday, and Tuesday),
and the planning process executes on Wednesday, the planning process suggests
that the order date should be on Wednesday with one compression
day.Action/Resolution: For discrete material planning only, you should consider
reviewing the recommendations for this item and possibly moving out the demand
to eliminate or alleviate the compression days. The Planning system assumes that
the recommendation/action will be taken