Escolar Documentos
Profissional Documentos
Cultura Documentos
Author:
Creation Date:
Last Updated:
Document Ref:
Version:
Approvals:
Document Control
Change Record
Date
Author
Versio
n
Change Reference
Reviewers
Name
Position
Distribution
Copy
No.
Name
Location
1
2
3
4
2 MSAT Internal
Page 7
Table of Contents
Document Control...........................................................................................
Introduction.....................................................................................................
Intended audience.......................................................................................................5
List of attendees.........................................................................................................5
Related training materials...........................................................................................5
Log onto Oracle Applications....................................................................................5
Data Collection..............................................................................................
Scope of data collection...........................................................................................28
Data collection methods...........................................................................................29
Run data collection...................................................................................................30
Planner Workbench.......................................................................................
Plan Navigator..........................................................................................................49
Supply chain structure..............................................................................................50
Supply chain plan result analysis.............................................................................56
Supply chain plan executions...................................................................................65
Personal and public queries......................................................................................67
3 MSAT Internal
Page 7
Reports..........................................................................................................
Plan comparison report............................................................................................76
Plan detail report......................................................................................................76
Audit information reports.........................................................................................76
Practicing labs...............................................................................................
FAQ...............................................................................................................
1. What calendar quarterly type does ASCP support?..............................................77
2. How are planning buckets and horizon calculated?.............................................77
3. How do I know which days are workdays, which day is week start date and
which is period start date?........................................................................................78
4. What lead-times can you define in Oracle Applications?....................................79
5. What lead times may be used by ASCP?.............................................................81
6. How are lead times used by ASCP in planned order date calculation?................81
7. How does ASCP calculate supply dates?.............................................................83
8. How can I release sales order from ASCP workbench?.......................................84
9. Why do the Supply window and Resource Requirements window show different
start and end date/time of a planned order?..............................................................84
4 MSAT Internal
Page 7
Introduction
Intended audience
This document is prepared as an introductory training material for the end users of
Oracle APPS 11i. It covers the basic skills needed for using Oracle Advanced Supply
Chain Planning. It is customized for the manufacturing environment.
Users whose role involves any of the following should attend this training.
Material planning
Capacity planning
Supply chain planning
Manufacturing execution
Oracle Applications support
List of attendees
Name
Org
Role
Date Trained
Date Certified
5 MSAT Internal
Page 7
6 MSAT Internal
Page 7
Planning cycle
The general process that occurs during a planning cycle is shown in the figure below.
The flow demonstrates the key features of Oracle ASCP that a typical planner would
use in the course of her/his work.
7 MSAT Internal
Page 7
Or
Inventory>Items>Organization Items>General Planning (T)
Valid
values
Make,
Buy
Planner
Planner Id
Inventory
Planning
Method
Not
Planned,
Min-Max,
Reorder
Point
Min-Max
Minimum
Quantity
Min-Max
Maximum
Quantity
Purpose
Comment
Determine
whether the
item is
manufactured
internally or
purchased
Assign
material
planner to
plan this item
Assign
planning
method to the
item
Enter the
quantity
minimum for
minmax
planning.
Enter the
quantity
maximum for
minmax
planning.
8 MSAT Internal
Page 7
Setup
Attribute
Valid
values
Order
Quantity
Minimum
Order
Quantity
Maximum
Cost Order
Cost
Carrying %
Source Type
Inventory,
Supplier,
Sub
Inventory
Source
Organization
Purpose
Comment
Enter the
minimum
order quantity
or repetitive
rate. Use this
to define an
order quantity
below which
it is
unprofitable
to build or
purchase the
item.
Enter the
maximum
order quantity
or repetitive
rate of the
item.
Enter the
fixed cost
associated
with placing
an order of
any quantity.
Enter the
percentage
used to
calculate the
annual
carrying cost.
Assign
replenishment
source type
Optionally
enter the
organization
from which
an internal
requisition
draws the
item.
9 MSAT Internal
Page 7
Setup
Attribute
Valid
values
Source
Subinventory
Safety Stock
Method
Safety Stock
Bucket Days
Safety Stock
Percent
Fixed Order
Quantity
Fixed Days
Supply
Fixed Lot
Multiplier
Purpose
Comment
Enter the
number of
days used to
modify the
size and
timing of
planned order
quantities.
Enter the
fixed lot
multiple
quantity or
repetitive rate
(units per
day).
10 MSAT Internal
Page 7
Setup
Valid values
Not
Planned,
MRP
planning,
MPS
planning,
MRP/DRP
Planned,
MPS/DRP
Planned,
DRP
Planned
Purpose
Select the option
that Planning
uses to decide
when to plan the
item
Comment
Not Planned: The item does not
require longterm planning of
material requirements. Choose this
option for high volume and/or low
cost items that do not warrant the
administrative overhead of
planning; typically dependent
demand items. You cannot use this
option unless the Pick Components
attribute is checked.
MRP planning: Choose this option
for noncritical items that do not
require manual planning control,
typically dependent demand items.
MPS planning: You master
schedule the item and require
manual planning control. Choose
this option for items with
independent demand, items that are
critical to your business, or items
that control critical resources.
MRP/DRP Planned: Choose this
option when you want both MRP
and DRP planning for the item.
MPS/DRP Planned: Choose this
option when you want both MRP
and DRP planning for the item.
DRP Planned: Choose this option
when you have multiple
organizations for which you do
Distribution Requirements
Planning for the item.
11 MSAT Internal
Page 7
Setup
Attribute
Forecast
Control
Valid values
Consume,
Consume
and derive,
None
Exception Set
Create
Supply
Critical
Component
Purpose
Select an option
to determine the
types of demand
you place for the
item. This guides
the key processes
of twolevel
master
scheduling:
forecast
explosion,
forecast
consumption,
planning,
production relief,
and shipment
relief.
Enter the name
of the planning
exception set that
groups together
the sensitivity
controls and
exception time
periods for item
level planning
exceptions for
the item.
Indicates if
supply can be
suggested for
this item.
If selected,
flags the item
as a critical
component
for MPS and
DRP planning.
Comment
This is appropriate only for items
that are models, option classes,
options, or mandatory components
of models and option classes.
Consume: forecast demand
directly, rather than by exploding
forecast demand.
Consume and derive: forecast
demand directly, explode forecast
demand, or use a combination of
both methods.
None: place sales order demand
but do not forecast demand.
12 MSAT Internal
Page 7
Setup
Attribute
Pegging
Valid values
Soft
Pegging,
End
Assembly
Pegging,
End
Assembly/
Soft
Pegging,
Hard
Pegging,
End
Assembly/
Hard
Pegging,
None
Purpose
Enter the pegging
option.
Planned
Inventory
Point
Indicates if the
item is an
Inventory Point
item.
Shrinkage
Rate
Enter a factor
that represents
the average
amount of
material expected
to lose during
manufacturing or
in storage.
Indicate whether
the planning
process uses
decimal or whole
number values
when calculating
planned order
quantities or
repetitive rates.
Round Order
Quantities 1
Comment
Soft Pegging: allocates supply to
demand based on the Reservation
Level option set in the Plan
options.
End Assembly Pegging: traces the
end assembly the item is pegged to
at the top of the bill of material.
Even if you do not select end
assembly pegging, you can still
calculate and view end assemblies
online.
End Assembly/ Soft Pegging:
Choose this option for both soft
pegging and end assembly
pegging.
Hard Pegging: allocates supply to
demand based on the Reservation
Level option set in the Plan
options. This pegs supply to
demand and demand to supply by
project at all levels of a bill of
material. This allows you to pre
allocate supply to demand and
generate planned orders based on
the plan level options.
End Assembly/ Hard Pegging:
Choose this option for both hard
pegging and end assembly
pegging.
None: disables project material
allocation, end assembly pegging,
and full pegging.
This means that material can be
stored at the item level without
losing materials or quality
characteristics. Inventory Points
generally point to major stocking
phases in the manufacturing cycle.
The planning process inflates
demand to compensate for this
expected loss.
13 MSAT Internal
Page 7
Setup
Attribute
Acceptable
Early Days 2
Valid values
Calculate
ATP 3
Reduce MPS
4
Planning
Time Fence
Days 5
None, Past
Due,
Demand
Time Fence,
Planning
time Fence
Cumulative
mfg. lead
time,
Cumulative
total lead
time, Total
lead time,
User
defined
Purpose
Enter the number
of days before
which the
planning process
will not
reschedule
orders.
Comment
The planning process only
suggests rescheduling out if the
new calculated order date is later
than the original order due date
plus the acceptable early days; the
new calculated order does not
violate the order of current
scheduled receipts.
This applies to discrete items only.
On the Planning Detail Report,
ATP is calculated as
ATP = Planned production
committed demand
Indicate whether
to calculate and
print available to
promise (ATP)
on the Planning
Detail Report.
Decide when to
reduce master
production
schedule (MPS)
quantities to
zero.
Determine a
point in time
inside which
certain
restrictions on
planning
recommendations
apply.
14 MSAT Internal
Page 7
Setup
Attribute
Demand
Time Fence
Days
Valid values
Cumulative
mfg. lead
time,
Cumulative
total lead
time, Total
lead time,
User
defined
Purpose
Determine a
point in time
inside which the
planning process
ignores forecast
demand and
considers only
sales order
demand when
calculating gross
requirements.
Release Time
Fence Days 6
Cumulative
mfg. lead
time,
Cumulative
total lead
time, Total
lead time,
User
defined, Do
not auto
release, Do
not release
(Kanban)
Determine a
point in time
inside which
planned orders
for discretely
planned items are
automatically
released as WIP
jobs or purchase
requisitions.
Substitution
Window
Cumulativ
e mfg. lead
time
Cumulativ
e total lead
time
Total lead
time
Userdefined
Calculates
until what
time a
substitute
can be
considered
for an item.
Comment
Used to reduce the risk of carrying
excess inventory.
Planning also uses the demand
time fence when loading master
schedules. The demand time fence
is calculated as the start date of the
master schedule load plus the value
entered.
Calculate the demand time fence as
the plan date (or the next workday
if the plan is generated on a non
workday) plus:
Cumulative mfg. lead time: The
cumulative manufacturing lead
time for the item.
Cumulative total lead time: The
total manufacturing lead time for
the item.
Total lead time: The total lead time
for the item.
Userdefined: The value you enter
for Planning Time Fence
Days.
No material availability check is
performed before WIP jobs are
released.
Calculate the release time fence as
the plan date (or the next workday
if the plan is generated on a non
workday) plus the value entered
here.
Cumulative mfg. lead time: The
cumulative manufacturing lead
time for the item.
Cumulative total lead time: The
total manufacturing lead time for
the item.
Total lead time: The total lead time
for the item.
Userdefined: The value you enter
for Planning Time Fence
Days.
Do not autorelease: The item
cannot be autoreleased.
Do not release (Kanban): For
Kanban items prevent release of
planned orders manually or
automatically.
Cumulative mfg. lead time:
The cumulative manufacturing
lead time for the item.
Cumulative total lead time:
The total manufacturing lead
time for the item.
Total lead time: The total lead
time for the item.
User-defined: The value you
enter.
Note:
15 MSAT Internal
Page 7
Setup
1. In ASCP, this flag is not only used to round planned order quantity, but also used to
schedule resource utilization for assembly. For assembly, when Round Order Quantity
is checked, it means one resource unit can only work on one unit of the assembly
item. For instance,
Work order quantity:
8
Assigned resource units:
3
Resource usage:
1 hour/unit item
Job duration:
3 hours (Round Order Quantity checked)
2 and 2/3 hours (Round Order Quantity
unchecked)
2. Set this attribute to reduce plan nervousness and eliminate minor reschedule
recommendations, especially when it is cheaper to build and carry excess inventory
for a short time than it is to reschedule an order.
3. ATP calculated by the planning process is not related to ATP information calculated
and maintained by Oracle Inventory. As such, planning ATP does not consider ATP
rules from the Available to Promise Rule window, and is not related to the ATP
information displayed in the View Item Available to Promise Information window in
Oracle Inventory module.
4. If Oracle Work in Process and Oracle Purchasing are installed, you get automatic
production relief when you create a discrete job, purchase requisition, or purchase
order. In this case, you would typically set this attribute to None. If you do not have
automatic production relief, you may select one of the options to reduce MPS
quantities and avoid overstating your supply.
5. This feature reduces short-term fluctuations in the plan output. The planning time
fence (PTF) helps Oracle ASCP generate a stable supply chain plan for manufacturing
shops and helps companies to honor contractual commitments with external suppliers.
PTF is a time parameter associated with an organization-item. ASCP functionality
associated with PTF can be summarized as follows:
Oracle ASCP does not create any new planned orders with start dates within
PTF.
Oracle ASCP does not Reschedule In any orders into the PTF.
Orders within PTF are Rescheduled Out based on a profile option setting.
Oracle ASCP does not suggest any changes for firm orders and orders pegged
to firm orders.
Excess and Shortage exceptions are generated within the time fence.
If you select the Enforce Demand Due Dates option, Oracle ASCP may violate the
PTF.
6. The planned orders must meet the following autorelease criteria:
The new due date lies within the autorelease time fence
The lead time is not compressed
The orders are for standard items (will not release models, option classes, and
planning items)
The orders are not for Kanban items
The orders are for DRP planned items in a DRP plan, MPS planned items in an
MPS plan, or MRP planned items in an MRP plan
The release time fence option is defined as anything other than Do not auto
release, Do not release (Kanban), or null
DRP, MPS, and MRP plans must be run with the Memorybased Planning
Engine
16 MSAT Internal
Page 7
Variable
Purpose
Enter the days you must add to
purchasing or manufacturing lead
time to place an order.
Enter the days required to procure
or manufacture an item.
Enter the days required to receive
a purchased item into inventory
from the initial supplier receipt.
Enter the days required to make an
assembly independent of order
quantity, such as setup or
teardown time.
Enter the time to produce one
additional unit of an assembly.
Cumulative
Manufacturing
Cumulative
Total
Comment
17 MSAT Internal
Page 7
Setup
18 MSAT Internal
Page 7
The carrier calendar indicates the operating calendar of the carrier or the service. It
does not indicate the pickup or delivery dates of the carrier.
Supplier Capacity Calendar
The supplier capacity calendar governs how supplier capacity is accumulated over a
period of time. Supplier capacity is only accumulated on the working days according
to the supplier capacity calendar. The supplier capacity calendar also governs how the
supplier processing lead time is calculated.
Workday Calendar
Please refer to Routing Training Manual for workday calendar setups.
Setup routing
Please refer to Routing Training Manual for routing setups.
19 MSAT Internal
Page 7
Refer to the table below for the setup of attributes relevant to planning.
Attribute
Status
Disabled
Global?
Valid
values
Approved,
Debarred,
New
Comment
Setup
Yes, No
20 MSAT Internal
Page 7
Refer to the table below for the setup of attributes relevant to planning.
Attribute
Processing
Lead Time
Supplier
Capacity
Calendar 1
Order
Modifiers
Capacity
Tolerance
Fence 2
Comment
This supplier-item attribute overrides the organization item
attribute for processing lead time
Planning adjusts planned order release date so that
deliveries occur on the valid delivery date that coincides
with the due date or the closest valid delivery date that
occurs prior to the due date. This calendar is independent
of your workday calendar.
These supplier-item attributes override the organization
item attributes for order modifiers.
This supplier-item attribute represents supplier item daily
capacity in the purchasing UOM.
Use the Tolerance% and Days Advance Notice attributes
together to state by what percentage a supplier can change
capacity if given a number of days advance notice.
Setup
Note:
1. If no calendar is defined and assigned to the supplier-item, planning will assume
all days are acceptable for receiving.
2. You can make multiple entries to represent the percentage change in capacity
allowed with different days of advance notices.
Delivery calendar
Set up delivery calendar the same way as setting up workday calendar.
Refer to Routing Training Manual on how to setup calendars.
The delivery calendar is used to establish valid delivery days by supplier, item, and
organization. ASCP will offset planned purchase order release dates by the number of
days in Processing Lead Time plus the number of days necessary to cause the delivery
to your dock to occur on a valid delivery day.
If no delivery calendar is defined and assigned to the supplier-item, planning will
assume all days are acceptable for receiving.
Shipping methods
Navigation path: Inventory>Setup>Organization>Shipping Methods
This form is used to set up a valid list of values for shipping method field.
21 MSAT Internal
Page 7
22 MSAT Internal
Page 7
Note: this form is used to model transportation time and capacities between external
sites and inventory organizations. If you use the Inter-Location Transit Times form to
enter transit times and transportation capacities between inventory organizations in
your enterprise, ASCP will ignore that information.
Sourcing rules
Supply chain complexity is modeled by sourcing rules, bills of distribution, and
assignment sets. Taken together, these forms specify how material is supplied,
manufactured, and transferred across the supply chain. But they will not model where
the materials will be sent. In this sense, bill of distribution is a misnomer.
When the sourcing rules and bills of distribution are created, items are not specified
anywhere on the definition forms. These are only descriptions of the means HOW
items are replenished. The defined sourcing rules and bills of distribution can later be
23 MSAT Internal
Page 7
assigned to any items or group of items. Assignment sets are used to associate items
with sourcing rules and bills of distribution.
Note: Sourcing rules and BODs can be defined at the source instances or at the APS
instance, or at both places. The Assignment Set of a specific plan will govern which
rules are used by that plan. However, sourcing rules and bills of distribution that cross
instances must be set up on the APS instance.
Navigation path: Supply Chain Planner>Sourcing>Sourcing Rules
Refer to the table below for the setup of attributes relevant to planning.
Attribute
Type
Valid
values
Transfer
From,
Make At,
Buy From
Allocation%
1
Rank 1
Planning
Active
Checked,
unchecked
All Orgs
Checked,
unchecked
Checked,
unchecked
Org
Comment
Setup
24 MSAT Internal
Page 7
Note: 1 in constraint based planning; sources with the highest rank have the highest
priority. In optimized planning, sources with the lowest penalty adjusted cost have the
highest priority in allocation. Timephasing in a sourcing rule determines when each
group of shipping method ship org combinations is in effect.
Assignment sets
Once you have defined your sourcing rules, you must assign them to particular items
and/or organizations to make them functional. These assignments are grouped
together in assignment sets. This is where various sourcing strategies define a
particular supply chain network. Each assignment set represents a 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, you can assign your sourcing rules at different levels, as follows:
Item-Instance-Organization
Category-Instance-Organization
Category-Instance
Item-Instance
Instance-Organization
Instance
These levels allow you to assign a replenishment rule to as many or as few items as
possible. For example, a category of items could be defined as packaging material,
and a sourcing rule that identifies the suppliers could be assigned to this category.
The planning uses a sourcing assignment hierarchy to determine the actual source of a
specific item. In the preceding list of assignment levels, the levels are listed from
specific to general. Specific sourcing assignment overrides general assignment, i.e.,
rows above override rows below. For instance, Item-Organization overrides Item.
Navigation path: Supply Chain Planner>Sourcing>Assign Sourcing Rule/BOD
25 MSAT Internal
Page 7
26 MSAT Internal
Page 7
Note: use assignment set hierarchy to simplify the modeling and maintaining sourcing
relationships. For example, when a plant buys all items belonging to a category such
as fasteners from Supplier A, create a sourcing rule and assign it to this item category.
At a later day, you decide to source one of the fasteners from Supplier B. You then
create another rule to source from Supplier B and assign this rule to that specific
fastener. The detail-to-general hierarchy directs the specific fastener to be sourced
from Supplier B, while all other fasteners still from Supplier A.
Create the minimum number of sourcing rules and keep the assignment sets as simple
as possible. Rather than create and assign a rule to each item, you can assign a default
rule to an organization, another default rule to a category. Assign a rule to an
individual item/organization only to deal with exceptions.
Order management
Most modules in Oracle Manufacturing do not interact directly with Oracle Order
Management. These modules use sales order information through the supply/demand
portion of Oracle Inventory. In Oracle Applications 11i, sales orders are visible to the
supply/demand portion of Oracle Inventory only after they are scheduled. Use the
Schedule Order process to create sales order information in Inventory. The scheduled
sales orders will become demand in supply chain planning.
Data Collection
Scope of data collection
27 MSAT Internal
Page 7
Oracle ASCP uses data maintained in the source (transactional) ERP modules. Data
collection programs capture a snapshot of the source data, and copy that snapshot to
the planning instance. The planning engine then performs multi-organization planning
and scheduling calculations. The results of the planning process, such as planned
orders, are published back to the transaction ERP modules for execution. The table
below summarizes the data collected into planning instance from the source instances.
Source Module
Order Management
Data to be Collected
Sales order demands, Customers, Price lists
Purchasing
Inventory
Bills of material
Work in Process
Cost
MRP/Supply Chain
Planning
Standard costs
Forecasts, Master demand schedules, Sourcing rules/Bills if distributions,
Assignment sets, Delivery schedules
Note: If Oracle Demand Planning is installed and integrated with ASCP, its output is
directly visible to ASCP as planning inputs.
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 Targeted Refresh method clears transaction data for only the userselected 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.
28 MSAT Internal
Page 7
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. Use
Complete Refresh only when it is necessary.
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.
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. 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).
29 MSAT Internal
Page 7
1. Tab to the Parameters field, Planning Data Pull Parameters form appears
Timeout (Minutes) 1
Values
Source instance code from list of values.
You can decide to collect data from All enabled organizations or only
form the current organization
One or greater. Increase this number to increase the number of
computational resources devoted 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.
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.
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
Refresh and Net Change.
30 MSAT Internal
Page 7
Parameter
Collection Method 2
Analyze Staging Tables
Business objects
Values
Complete Refresh/Targeted Refresh/Net Change
Refresh. See the explanation in the Data collection methods section of
this manual
Yes or No (default). Set this to Yes periodically to re-compute 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 objects. Selecting Yes for an entity means collecting the
information for that entity over from the source instance. Selecting No
for an entity means collecting no information for that entity over from
the source instance. This is useful when you know there are only
changes on limited objects.
Note:
1. Consult with your system administrator and DBA on the values of these
parameters, for they affect the performance of the data collection process.
2. Collecting information for Resource Availability and Sourcing History
takes a significant amount of time. Collect this information only when
really necessary.
3. Open the Parameters form for Planning ODS Load
Number of Workers 1
Recalculate Resource
Availability
Values
Source instance code from list of values.
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.
One or greater. Increase this number to increase the number of
computational resources devoted 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.
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.
31 MSAT Internal
Page 7
Parameter
Recalculate Sourcing History
Values
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.
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.
Note: 1. Consult with your system administrator and DBA on the values of
these parameters, for they affect the performance of the data collection
process.
5. Submit the data collection request set
Planning
Horizon
Long Term
Future
Resource
Constrained
Long Term
Future
Material
Constrained
Long Term
Future
Goals
Scenario
32 MSAT Internal
Page 7
Plan Class
Material and
Resource
Constrained
Optimized
Planning
Horizon
Near Term
Future
Goals
Scenario
Near Term
Future
Note:
Oracle ASCP lets you prioritize how you enforce Capacity Constraints or Demand
Due Dates. Whichever constraint takes precedence over the other is the hard
constraint; and the other is the soft constraint. You must choose one and only one type
of constraint.
If you choose to enforce Demand Due Dates (setting Demand Due Dates as a hard
constraint), then primary resources are used and loaded to capacity to satisfy demand
due dates. The system also evaluates alternate resources if additional capacity is
required. If there is insufficient capacity to meet demand due dates, the primary
resource is overloaded. The choice of whether to use an alternate resource or overload
capacity depends on cost considerations if optimization is selected. Oracle ASCP
returns exception messages if capacity is overloaded.
If you choose to enforce Capacity Constraints (setting Capacity Constraints as a hard
constraint), then resources are loaded to their limit to satisfy demand (if required).
Unsatisfied demand is pushed into the future. In this case, Oracle ASCP returns late
replenishment exception messages.
Each creates time-phased planned orders that satisfy independent and dependent
demand while seeking to respect material and resource constraints. These three types
of plans need to be used in conjunction with the MPS/MRP Planning Type item
attribute that is set for each item. Possible values for this attribute are:
MRP Planning
MPS Planning
MRP/MPP Planned
MPS/MPP Planned
MPP Planned
33 MSAT Internal
Page 7
Each ASCP plan type will include a subset of items in its planning process. The items
included depend upon the plan type and the items the MRP Planning Type attribute.
34 MSAT Internal
Page 7
Main tab
Use the information in the following table to specify parameters on the Main tab.
Parameter
Assignment
Set
Demand
Priority Rule
Overwrite1
Append
Planned
Orders1
Planned
Items2
Material
Scheduling
Method
Description
The assignment set that holds the sourcing
rules and bills of distribution that define the
rules for material flow within your supply
chain.
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.
Overwrite planned orders.
Appends new planned orders to current
plan.
This parameter and the next one, Planning
Method, 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.
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.
35 MSAT Internal
Page 7
Comment
Setup
Parameter
End Item
Substitution
Set
Schedule By
Demand
Class
Move Jobs to
PIP
Display Key
Performance
Indicators
Demand
Time Fence
Control
Planning
Time Fence
Control
Lot for Lot
Include
Critical
Components
Description
If Decision Rules tabbed region > Use End
Item Substitutions selected, select a
substitution set. These are defined in the
Planning Details - Substitute window
discussed. You can use a set of substitution
relationships to be effective for a given plan
by selecting the substitution set as an option
for the plan. This allows you to run
simulations of possible substitutions and
evaluate performance indicators given
possible future substitutions.
Set this option to instruct the planning
engine to:
Plan supplies based on sales order line
request, promise, or schedule dates for
either ship or arrival
Consume forecasts based on sales order line
request, promise, or schedule dates. You
must provide forecast dates that match your
choice of this plan option; for example, if
you select Promise Ship date for this plan
option, make sure your forecast dates are in
terms of promise ship dates.
If you do not specify plan option Demand
Priority Rule and have not specified a
default demand priority rule (in the Define
Priority Ruled form), the planning engine
uses the value of this plan option as the
demand priority rule.
If you want to limit a production plan to a
demand class, enter it.
Comment
Order quantity
modifiers such as
Minimum Lot Size
and Fixed Lot
Multiple override this
option
To mark an item as a
critical component,
select its item
attribute Critical
Component.
36 MSAT Internal
Page 7
Setup
Parameter
Do Not
Spread
Forecast
Spread
Forecast
Evenly
Forecast
Distribution
Assignment
Set
Consume by
Forecast
Bucket
Explode
Forecast
Backward
Days
Forward
Days
Enable
Pegging
Peg Supplies
by Demand
Priority
Description
The planning engine should use forecast
entries as they exist for planning.
The planning engine should spread
aggregate forecast demand evenly across
the daily buckets from the workday
calendar.
Select a forecast distribution assignment set
for the global forecasting process. The
forecast distribution assignment set contains
global sourcing rules used to distribute
global forecasts over multiple inventory
organizations:
The forecast consumption process does not
search outside of the consumption bucket
for forecasts and sales orders except in daily
buckets.
Select this plan option to instruct the
planning engine to explode forecasts as
follows during the consumption process:
- Product family forecasts to product family
member item forecasts
- Model forecasts to other model, option
class, and item forecasts.
This option applies to forecasts with
forecast control Consume and derive.
If you are bringing in unconsumed forecast
scenarios from Oracle Demand Planning as
demand schedules into Oracle ASCP and
would like to do forecast consumption
inside ASCP (as opposed to bringing in preconsumed forecasts contained in master
demand schedules as demand schedules into
Oracle ASCP), then set the forecasts
consumption backward days parameter
here. This parameter allows a sales order
demand to consume forecast demand even
if the forecast demand is up to the specified
number of days earlier than the sales order
demand. This parameter applies only to
Oracle Demand Planning scenarios that are
used as demand schedules in Oracle ASCP
plans.
This parameter allows a sales order demand
to consume forecast demand even if the
forecast demand is up to the specified
number of days later than the sales order
demand.
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.
Check this option to calculate pegging so
that on-hand and firm 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).
37 MSAT Internal
Page 7
Comment
Setup
Parameter
Pegging
Reservation
Level
Pegging
Hard Pegging
Level
Forecast
Consumption
Backward
Days
Forecast
Consumption
Forward
Days
Description
Choose a reservation level: Planning Group,
Project, Project-Task, or None.
Comment
Do not use
Do not use
Setup
Do not use
Note: 1. Overwrite and Append Planned Orders work together to limit how the
planning process reacts to firm planned orders and to stabilize the short-term material
plan. When you launch the planning process, you generate new planned orders to
meet your net requirements. Since you can firm DRP, MPS, or MRP planned orders,
you may not want the planning process to overwrite any firm planned orders. See the
table below for more information.
Overwrite
Append
Planned Orders
All
None
Outside
planning time
fence
Unchecked
Effects
The planning process overwrites all entries, planned and firm
planned, from the current material plan.
The planning process does not overwrite any firm planned
orders. It does, however, overwrite any suggested planned
orders that are not firm.
The planning process overwrites all entries from the current
plan, planned and firm planned, outside the planning time
fence, and overwrites only planned orders inside the planning
time fence. It does not overwrite any firm planned orders within
the planning time fence. The planning time fence can be
different for each item, so the planning process looks at the
planning time fence for each item when choosing what to
delete. Planning time fence is an item attribute defined in
Inventory
The planning process does not append any planned orders to the
current plan. Additional demand does not cause planned order
recommendations. Instead, the projected quantity on hand may
go negative in response to demand that was not met by a
suggested planned order.
38 MSAT Internal
Page 7
Overwrite
Append
Planned Orders
Checked
All
Checked
Outside
planning time
fence
Checked
None
Checked
None
Unchecked
Effects
The planning process appends additional planned orders after
the last entry on the current material plan to meet any additional
demand. The Overwrite and Append Planned Orders options
work in combinations, as described below.
Select this option to create a new material requirements plan for
the plan name you specify, deleting all previous planned and
firm planned orders while regenerating new planned orders.
You can use this combination the first time you run your plan or
if you want your plan to reflect all sources of new demand.
This option allows you to create an extension to the current
material requirements plan, delete planned and firm planned
orders outside the planning time fence and delete all planned
entries inside the planning time fence for each item. The
planning process creates (appends) new planned orders after the
planning time fence date. In this case, since you are overwriting
after the planning time fence, you are also appending new
planned orders after that date. Use this combination to stabilize
the shortterm plan and allow the longterm plan to react to
new sources of demand. If an item has no time fence specified
and this option is chosen, all planned and firm planned orders
are overwritten. The effect is the same as Overwrite All and
Append Planned Orders checked.
When you choose not to overwrite an existing plan, the
planning process does not overwrite existing firm planned
orders, but deletes any suggested planned orders. The planning
process then creates (appends) new planned orders after the
planning time fence date. Use this to firm shortterm sections of
your material requirements plan. You can extend the plan
horizon without altering existing firm planned orders.
The planning process does not overwrite existing firm planned
entries, but deletes any suggested planned orders. In addition, it
does not append additional demand to the end of the plan.
Instead, it reports the instances where the material requirements
plan is out of balance with the master demand schedule, and
allows you to solve these problems by manipulating the plan
manually. In this case, the projected quantity on hand would go
negative since no planned orders were suggested to meet the
additional demand. The material planner can use online
inquiries and reports with exception messages to identify
material shortages. This gives maximum control to the material
planner.
Note: 2. Planned Items, Planning Method and Items attribute MRP/MPS Planning
method work together to select items in the plan. The following table lists the three
controls that together determine which items are planned in a supply chain plan, and
the possible values for each control.
Planned Items
value
All planned items
Plan type
Master Plan
39 MSAT Internal
Page 7
Planned Items
value
All planned items
Plan type
Production Plan
Manufacturing Plan
Demand schedule
items only
Master Plan
Demand schedule
items only
Production Plan
Demand schedule
items only
Manufacturing Plan
Supply schedule
items only
Master Plan
Supply schedule
items only
Production Plan
Supply schedule
items only
Manufacturing Plan
Demand and
Supply schedule
items
Master Plan
40 MSAT Internal
Page 7
Planned Items
value
Demand and
Supply schedule
items
Plan type
Production Plan
Demand and
Supply schedule
items
Manufacturing Plan
All items in the input demand and supply schedules, and all
components of these items that have MRP/MPS Planning
Method attribute code of:
MPS planning
MPS and MPP planning
Plus:
MPS and MRP planned items that are in between the above
items in the bills of material
All items in the input demand and supply schedules, and all
components of these items that have MRP/MPS Planning
Method attribute code of:
MRP planning
MRP and MPP planning
Aggregation tab
Use the information in the following table to specify parameters on the Aggregation
tab.
Parameter
Start Date
End Date
Bucket Size
Items
Resources
Routings
Minutes
Bucket
Hours
Bucket Size
Days Bucket
Size
Description
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.
Shows the calculated end date for your plan. This is a view-only
field, calculated based on the bucket sizes you specify
Specify bucket size in days, weeks, and periods.
Choose aggregation at item level or product family level.
Choose resource aggregation at individual level or aggregate level.
Choose aggregation level at individual routing or bill of resources
level.
Size Specify the bucket size in minutes for the Days planning
period.
Specify the bucket size in hours for the Days planning period.
Specify the bucket size in days for the Days planning period.
41 MSAT Internal
Page 7
Setup
Organization tab
Use the information in the following table to set parameters on the Organizations tab.
Parameter
Global
Demand
Schedules
Ship To
Consumption
Level
Org
Description
Net WIP
Net
Reservations
Description
Select the names of Oracle Demand
Planning scenarios that drive this
plan. You can select demandplanning scenarios that do not
reference an organization
(organization dimension set to All
Organization).
Select a forecast consumption level
for the Oracle Demand Planning
scenario. The global forecasting
process consumes forecast entries
that have Ship To value the same as
this plan option.
Note
42 MSAT Internal
Page 7
Setup
Parameter
Net Purchasing
Plan Safety
Stock
Include Sales
Order1
Bill of
Resource
Simulation Set
Demand
Schedules2
Ship To
Consumption
Level
Interplant
Supply
Schedules
Subinventory
Netting
Description
Select to consider purchase orders,
purchase requisitions, in-transit
shipments and other non-production
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.
Select to consider plan safety stock
demand and supply in the planning
demand/supply netting process.
Select to invoke forecast
consumption within ASCP for the
selected organization. Check this if
the demand schedules for the
organization are unconsumed
forecasts. Uncheck this if the
demand schedules for the
organization are consumed forecasts
plus sales orders in the form of
master demand schedules
Select Bill of Resources from the list
of values if one of the Routings is
set to BOR on Aggregation tab.
Select a Simulation Set from the list
of values. A simulation set is a set of
adjustments to the base availability
calendar of a resource, and is
defined via the Oracle Bills of
Materials Department Resources
form. You can define different
simulation sets to model different
availability scenarios (for example,
the base availability calendar could
reflect 5-day operations; simulation
set 1 could reflect working 6
days/week for a certain period;
simulation set 2 could reflect
working 7 days/week for a certain
period). The simulation set that you
select is applied to all resources
within the organization.
Select the name of your demand
schedule/forecast/plan.
See above
Note
See above
43 MSAT Internal
Page 7
Setup
Note: 1. Users can collect forecasts into the APS planning server. Optionally, they can
choose to consume forecasts by sales orders when they run ASCP plans. Forecasts are
consumed if the Include Sales Order check box in the Organizations tab of the Plan
Options window is checked. For multilevel ATO items, forecasts are consumed at all
levels if the forecast explosion has occurred in the source instance prior to the
collection. If you are not using forecast, uncheck this check box.
2. The plan for one organization can be used as a demand (or demand schedule)
for the plan of another organization.
Constraint tab
Use the information in the following table to specify parameters on the Constraints
tab.
Parameter
Constrained
Plan
Enforce
Demand Due
Dates
Enforce
Capacity
Constraints
Start Date
Buckets
Resource
Constraints
Supplier
Capacity
Constraints
Description
If selected, Enforce Demand Due Dates is selected, all fields in
the tabbed region are updateable with all constraints defaulted to
Yes. The default is cleared. You cannot set all Resource
Constraints and Material Constraints to No. If you set any
Resource Constraints to Yes, you cannot clear Calculate
Resource Requirements.
Check this option if you want demand due dates to be your hard
constraint (that is, respected in lieu of material and resource
capacity constraints, if there is conflict).
Check this option if you want material and resource capacity
constraints to be respected in lieu of demand due date
constraints.
Displays the start date for each bucket type.
Displays the number of buckets of this bucket type.
Select Yes to consider resource constraints for the bucket.
Select Yes to consider supplier capacity constraints.
44 MSAT Internal
Page 7
Setup
Parameter
Enforce
Purchasing
Lead-time
Constraints
Scheduling
Minutes
Bucket Size
(in
Days)
Hours Bucket
Size (in
Days)
Days Bucket
Size (in
Days)
Calculate
Resource
Requirements
Planned
Resources
Bottleneck
Resource
Group
Description
Select this plan option to instruct the planning engine to
constrain the plan by purchased item lead times (item attributes
or approved supplier list).
Clear it to instruct the planning engine never to miss a demand
due date because of a purchased item lead time.
Specify whether to enable detailed scheduling.
Size Specify the bucket size in minutes for the Days planning
period.
Setup
Specify the bucket size in hours for the Days planning period.
Specify the bucket size in days for the Days planning period.
If selected, the program will calculate resource capacity
utilization.
Select All Resources or Bottleneck Resources. If you have
defined bottleneck resource groups in Oracle Bills of Material
and you want to detail schedule only the bottleneck resources,
select
Bottleneck Resources and enter a Bottleneck Resource Group.
If you have defined bottleneck resource groups in Oracle Bills of
Material and you want to detail schedule only the bottleneck
resources, select its name.
Use the information in the following table to specify parameters on the Decision
Rules tab.
Parameter
Use End Item
Substitution
Use Alternate
Resources
Use
Substitute
Components
Description
If selected, use end item substitute prior to creating new planned
orders. If cleared, use only the demanded item. Enter the End Item
Substitution Set in the Main tabbed region.
If selected, use primary resource and use alternate resource only if
necessary. If cleared, use only primary resources.
If selected, use primary components and use substitute
components only if necessary. If cleared, use only primary
components only.
45 MSAT Internal
Page 7
Setup
Parameter
Use Alternate
BOM/Routing
Use Alternate
Sources
Description
If selected, use primary routings and use alternates only if
necessary. If cleared, use only primary bills of material and
routings.
If selected, use primary sources and use alternate sources only if
necessary. If cleared, use primary sources only. The planning
engine does not use alternate sources (rank 2 or higher) as a
sources of supply.
Setup
Launch a plan
Navigation path: Advanced Supply Chain Planner>Supply Chain Plan>Names>
Launch Plan (B)
For an ASCP plan, accept the defaults on the request parameters form and click on
OK then submit the request.
Copy a plan
Navigation path: Advanced Supply Chain Planner>Supply Chain Plan>Names>Copy
Plan (B)
46 MSAT Internal
Page 7
Planner Workbench
The Planner Workbench is the primary work area for analysis of the plan and
actions taken based on plan recommendations
Multi-window format
Ability to have several screen open at the same time
Strong navigational interactions between different workbench windows
Context passed between windows using right clicks or buttons
Ability to see data at detailed and summary levels and drill down/up from one
to the other
47 MSAT Internal
Page 7
Plans tab displays the entities associated with the plan in a hierarchical fashion (user
can select the drill down hierarchy)
Queries tab displays only those entities within the plan that the user wants to focus on
(as pre-defined by the user)
Plan Navigator
Displays list of plans defined under the organization (Note: The plan although
defined in one organization could still be a multi-org plan)
View Plans by
o Actions
o Organizations
o Item
o Resources
o Projects
o Suppliers
Variety of Right-Click navigations possible from each node (or use of
Shortcut buttons at the bottom of the navigator)
List of Item Categories displayed is based on Tools Preferences Other
Category Set
48 MSAT Internal
Page 7
Where Used: The items in the next level up in the bill of material that use this
item as a component
Components: The components defined in this items bill of material (primary
and alternates)
Co-Products: If the process that produces this item also produces other
products, those are displayed here
Routing Operations: The operations within the routings (primary and
alternate) that are used to produce this item
Safety Stock: Prescribed safety stock targets for this item. This screen only
shows safety stock defined in the Source ERP as quantity (It does not show
safety stock input from IO or the target dynamically calculated by the plan
based on safety stock days of supply)
Substitutes: If this item is sold as an end item, the valid substitutes that can be
offered to a customer requesting this item
Inventory Levels: Not used by ASCP
Item:
Destination:
Where Used:
50 MSAT Internal
Page 7
Components:
51 MSAT Internal
Page 7
Supply Chain:
52 MSAT Internal
Page 7
Gantt Chart:
Availability:
53 MSAT Internal
Page 7
Requirements:
54 MSAT Internal
Page 7
Right Click Exceptions > Summary (sensitive to the level in the tree at which
right click is performed)
Displays Exceptions as various types classified into groups
Shows the count of exceptions by group, type
Can Save a version of the Exception messages prior to running a simulation
re-plan
Can have all exception groups pre-expanded (Tools > Preferences > Other)
55 MSAT Internal
Page 7
Lead Times
56 MSAT Internal
Page 7
57 MSAT Internal
Page 7
Shows time phased view of supply, demand and inventory for an item/org
(multi-select also possible)
Drill downs from demand and supply rows to Supply/Demand Window
(discussed later)
Can optionally display a graph
o Graph up to maximum of 3 rows at a time
o Select number of buckets / chart type
Right Click on Enterprise Plan, Shows the supplies and demands summarized
across time
58 MSAT Internal
Page 7
59 MSAT Internal
Page 7
60 MSAT Internal
Page 7
61 MSAT Internal
Page 7
62 MSAT Internal
Page 7
Order View:
Resource View:
63 MSAT Internal
Page 7
64 MSAT Internal
Page 7
When users make manual changes to the plan they would want to rerun the
plan so that the rest of the plan that they have not disturbed aligns with their
changes
There are several options to rerun the plan
o Launch New Plan: This will generate the plan from scratch. Firm
supplies will be retained based on the overwrite option but Gantt chart
based firming is ignored
o Batch Re-plan: ASCP will figure out what the user has changed and
mark a set of items that need to be re-planned. Only those items are replanned (effects of common components, resources are taken into
account)
o Online Replan: Similar to Batch replan but used for the mode where
the user wants to make several changes one after the other and rerun
the plan after each change. Also allows for Undo capability on the
changes (but not on the plan. The plan has to be rerun after undoing the
user change)
65 MSAT Internal
Page 7
for Release
Do Plan > Release
Selective release
o Select a specific order for release using the Release checkbox
o Select the Release Properties tab
o Fill in details for the Implement As * columns as appropriate (there
are several Implement columns that are hidden)
o Hit the Save button (or Ctrl + S)
o Right click Release or Plan > Release
A summary window will provide information on which orders were released
successfully and which orders were not
o
plan name
Accessed using the Queries tab on the planner workbench
Query is a stored set of business criteria that are used to generate results that
66 MSAT Internal
Page 7
Define Query Name > Specify Criteria > Execute Query > View Results >
Simulate changes
What changes can you simulate?
Supplier capacity: To simulate item supply changes, you can add new supplier
capacity and adjust a suppliers capacity over a specified time frame.
Resource availability: You can add new resource availability and modify how
many resources are available over user defined time frame. Resource
constraints include available machine hours, available worker hours, and
adding or removing shifts.
Supplies: Add new planned orders. Firm planned orders, discrete jobs, and
purchase orders. Modify quantities, dates, sources, and alternates
Demands: Alter demand priority of any demand. Modify quantities and due
dates for independent demand (MDS entries). Add new Manual MDS.
Change supplier capacity
1. Query the item for which you want to change supplier capacity
2. Click on the Sources button
67 MSAT Internal
Page 7
Change supply
1. Open the Supply/Demand window
2. Click on the New button on the toolbar
3. Enter Org code
4. Enter Item code
5. Select Planned Order as Order Type
6. Enter New Date as the supply due date
7. Enter New Qty as the supply quantity
8. Optionally, enter sourcing information under the Sourcing tab Source Org,
Source Supplier, Source Supplier Site
68 MSAT Internal
Page 7
9. Save
Note: when you manually create supply, the order type is Planned Order and the order
is Firm.
Change demand
1. Open the Supply/Demand window
2. Click on the New button on the toolbar
3. Enter Org code
4. Enter Item code
5. Select Manual MDS as Order Type
6. Enter New Date as the supply due date
7. Enter New Qty as the supply quantity
8. Enter Order Priority
69 MSAT Internal
Page 7
Note: when you manually create demand, the order type is Manual MDS and the
order is Firm by default.
Simulation modes
Batch Mode Planner: Replan at the back end, return the front end to user
immediately, and give other users access to the plan when you are performing
simulations.
Online Planner: It is more interactive; you can make changes and replan as many
times as necessary before release. It generates the full set of exception messages
following a replan. You are allowed to enter changes before and after, but not during
Online Replan session. The changes you made during an online session can be
undone. You are not allowed to start another Online Planner session nor are you
allowed to make changes to the plan when Online Replan is progressing.
70 MSAT Internal
Page 7
71 MSAT Internal
Page 7
Make the desired changes to your plan when the status window informs you
that the session is ready for planning
Save
Choose Plan > Online Replan
72 MSAT Internal
Page 7
Stop online planner session, Choose Plan > Stop Online Planner. Click OK to
confirm your choice.
73 MSAT Internal
Page 7
Undo action
On the Undo Summary window, select a change you initiated in the online planner.
Click Undo.
74 MSAT Internal
Page 7
Reports
Plan comparison report
The Plan Comparison Report compares two plans. To compare two plans:
Specify criteria for comparison attributes (preference sets) and the comparison
display (filtering criteria)
Select the plans to compare and view the comparison: You can drill down from
exception group comparison to exception type comparison to exception details
comparison.
75 MSAT Internal
Page 7
The planning process involves collecting and using source data to drive planning.
Data from source instances need to be accurate and need to be set up properly in order
for reliable planning output. Data from the source can be corrupt due to many reasons,
including: bad transactions, missing transactions, human error, improper formats,
conflicting and/or missing setups and profile options.
The Audit Statements Reports are self-explanatory reports that evaluate data setups. It
suggests remedies for the problems that are found.
Audit Collections Setup report
Used for auditing collected data integrity
Audit Planning Data report
Used for auditing the planning engine
Audit UI Data report
Used for auditing the user interface; for example, to check the validity of materialized
views and profile options that control the display of plan data
Practicing labs
To be added
FAQ
1. What calendar quarterly type does ASCP support?
Up to 11i.10, Oracle ASCP only supports 4/4/5 week pattern quarterly type
calendars. Calendars using other type of quarterly pattern may cause
unexpected planning and scheduling results. Check your workday calendars to
see if they are setup with the correct quarterly pattern. Note also, workday
calendars setup for manufacturing and planning is independent of financial
calendars.
76 MSAT Internal
Page 7
The 25 days daily bucket ends on 13-APR-2006, but the next week starts on
17-APR-2006 because weekly buckets can only start on a week beginning day
from the manufacturing calendar. If the daily horizon does not end on the day
before a week beginning day, the planning engine extends it to the next day
before a week beginning day. It plans the extended days in daily buckets
never minute or hourly bucketsregardless of any other settings. The 13
weeks weekly bucket ends on 16-JUL-2006. But the period bucket can only
start on a period beginning date. The nearest period beginning date after 16JUL-2006 is 31-JUL-2006. From 31-JUL-2006 on, the 8th periods ends on 01APR-2007. The plan horizon is therefore between 20-MAR-2006 and 01APR-2007.
Note: the days counted for the daily bucket include non-workdays.
3. How do I know which days are workdays, which day is week start
date and which is period start date?
From the Tools menu, choose Work Dates You can check workdays, week
start date, or period start date.
Calendar
Code
Non-workdays
are dimmed
77 MSAT Internal
Page 7
78 MSAT Internal
Page 7
79 MSAT Internal
Page 7
times must already be defined in shipping network for transfer from and in
inter-location transit time for buy from).
Subinventory-item lead
times
Kanban pull sequence
lead time
Item-supplier-supplier
site lead time
Inter-location transit
time
Shipping network
intransit time
Used?
Yes
Comment
ASCP uses preprocessing, processing,
post processing lead time for buy items.
It uses variable and fixed lead times for
make item planning.
No
ASCP plans at organization level. Thus,
subinventory-item attributes are ignored.
No
ASCP does not plan Kanban. Thus,
Kanban attributes are ignored.
Yes
ASCP uses it to calculate supplier
specific lead time for buy items
Depends ASCP uses transit time between your
organization and customer site to
calculate outbound shipping (sales
order) scheduled ship date and scheduled
arrival date. It does not use transit time
between your organization and supplier
site to calculate inbound shipping
(purchase order) scheduled ship date, for
the supplier shipping date is not under
your control unless you are using Oracle
Supplier Scheduling. In Oracle Supplier
Scheduling, transit time is used to
calculate the scheduled ship date.
Yes
ASCP uses it for transfer orders between
your organizations.
Note: currently, Region level sourcing rules and transit lead times are
respected by Global Order Promising (GATP) only for sale order scheduling,
but not by Advanced Supply Chain Planning and Inventory.
81 MSAT Internal
Page 7
ASCP uses work days from the manufacturing calendar to calculate dates for
manufactured supplies.
Need By Date: The date that the material should ship or be in inventory for a
next-higher level assembly. This is the earliest demand due date that the
supply is pegged to.
Suggested Due Date:
In an Unconstrained or Constrained - Enforce demand due dates plan
this is the same as Need By Date.
In a Constrained - Enforce capacity constraints plan this is the
scheduled availability date of the supply. If the supply is constrained,
the planning engine forward schedules from the constraint.
Suggested Dock Date: Demand Due Date. Dock Date is the day by which all
shop floor operations are complete.
Manufactured supplies do not have a Postprocessing lead-time.
Suggested Ship Date: Blank
Suggested Start Date: Suggested Due Date - Production duration. This is the
day that you should begin shop floor operations.
Production Duration:
Unconstrained plans: Fixed + (Variable * Order quantity)
Constrained plans: Calculated resource and material duration. If the
item does not have a routing, the planning engine uses the
unconstrained calculation.
Suggested Order Date: Planned order Start Date - Preprocessing. It is the date
on which you should place the order.
82 MSAT Internal
Page 7
window. But the resource requirements of the same order indicate the order
starts at 30-DEC-2007 13:38:00 and ends at 04-JAN-2007 13:59:00. Why?
The dates on the resource requirements are derived from the process of
backward or forward scheduling (using lead time offset) of the order
considering constraints as set by plan options. Once these dates are obtained, if
the order is in a weekly or period bucket, ASCP right-justify all the dates to
the last minute of the last workday of the bucket in which the dates fall in.
The period calendar is shown below.
The last work day of period DEC-2006 is 29-DEC-2006. The last work day of
period JAN-2007 is 26-JAN-2007.
Note: when the planned order as the one aforementioned is released from
planner workbench to WIP, WIP will use the Suggest Due Date as the
Completion Date and schedule the job accordingly if WIP is setup to use
unconstrained scheduling. The resource requirements scheduling from ASCP
is ignored.
84 MSAT Internal
Page 7
Constraint types
You can generate plans using the following scenarios for each planning bucket type
(days, weeks, and periods):
Material constraints only
Resource constraints only
Material and resource constraints
Oracle ASCP lets you prioritize how you enforce Capacity Constraints or Demand
Due Dates. Whichever constraint takes precedence over the other is the hard
constraint; the other is the soft constraint. You must choose one and only one type of
constraint.
Enforce Demand Due Dates (on the Options tab) is checked, Plan Capacity
(on the Aggregation tab) is unchecked. This is an unconstrained plan. This
type of plan is the traditional MRP plan with multiple organization
planning functionality.
Enforce Demand Due Dates (on the Options tab) is checked; Plan Capacity
(on the Aggregation tab) is checked. Due dates are hard constraints and
capacity is soft constraint. Primary resources are used and loaded to
capacity to satisfy demand due dates. The system also evaluates alternate
resources if additional capacity is required. If there is insufficient capacity
to meet demand due dates, the primary resource is overloaded. The choice
of whether to use an alternate resource or overload capacity depends on
cost considerations if optimization is selected. Oracle ASCP returns
exception messages if capacity is overloaded.
Enforce Capacity Constraints (on the Options tab) is checked. In this type
of plans, capacity is hard constraint and due dates become soft constraints.
Resources are loaded to their limit to satisfy demand (if required).
Unsatisfied demand is pushed into the future. In this case, Oracle ASCP
returns late replenishment exception messages.
The information needed to run a constraint-based plan is listed below:
Items: BOM effectivities (process effectivity), ECOs, by-products, safety
stocks, order modifiers, supplier-specific order modifiers, supplier-specific
lead times, pegging restrictions
Manufacturing Resources: routing effectivities, alternate resources,
resource capacities, line rates, workday calendar
Transportation Resources: carrier capacities, shipment and delivery
calendars
Sourcing Constraints: sourcing effectivities, sourcing ranks, allocation
percentages, supplier capacity
85 MSAT Internal
Page 7
Check Enforce
Capacity Constraints
Check Enforce
Capacity Constraints
Check Enforce
Capacity Constraints
86 MSAT Internal
Page 7
Note: When
Demand Priorities are not specified, the default priorities of the various
demand types are (in order): sales order, forecast, and safety stock.
87 MSAT Internal
Page 7