Beruflich Dokumente
Kultur Dokumente
Introduction .................................................................................................. 3
Intended audience............................................................................................................................... 3
Log onto Oracle Applications ........................................................................................................... 3
Overview of Oracle Advanced Planning ................................................. 3
APS data flow ...................................................................................................................................... 3
Planning cycle ...................................................................................................................................... 3
Source Data Setups ...................................................................................... 4
Setup inventory item attributes ........................................................................................................ 4
MPS/MRP planning attributes ......................................................................................................... 7
Lead times attributes ........................................................................................................................ 14
Shipping, Receiving, Carrier, and Supplier Capacity Calendars ............................................... 15
Workday Calendar............................................................................................................................ 16
Setup resource and department ...................................................................................................... 16
Setup routing ..................................................................................................................................... 16
Setup supply chain ........................................................................................................................... 16
Order management ........................................................................................................................... 23
Data Collection ........................................................................................... 23
Scope of data collection .................................................................................................................... 23
Data collection methods ................................................................................................................... 24
Run data collection ........................................................................................................................... 25
Define an ASCP plan ................................................................................. 28
ASCP plan classes ............................................................................................................................. 28
ASCP plan types................................................................................................................................ 29
Define a plan name ........................................................................................................................... 29
Set plan options ................................................................................................................................. 30
Launch a plan .................................................................................................................................... 43
Copy a plan ........................................................................................................................................ 44
Planner Workbench ................................................................................... 45
Plan Navigator................................................................................................................................... 45
Supply chain structure ..................................................................................................................... 46
Supply chain plan result analysis ................................................................................................... 51
Supply chain plan executions.......................................................................................................... 60
Personal and public queries ............................................................................................................ 62
Simulation net change re-plan ................................................................. 63
Simulate changes ............................................................................................................................... 63
Simulation modes ............................................................................................................................. 65
Running net change replan simulations ........................................................................................ 65
Reports ......................................................................................................... 69
Plan comparison report .................................................................................................................... 69
Plan detail report............................................................................................................................... 70
Audit information reports ............................................................................................................... 70
Practicing labs............................................................................................. 70
FAQ .............................................................................................................. 70
1. What calendar quarterly type does ASCP support? ................................................................ 70
2. How are planning buckets and horizon calculated? ............................................................... 70
3. How do I know which days are workdays, which day is week start date and which is
period start date?............................................................................................................................... 71
4. What lead-times can you define in Oracle Applications? ....................................................... 72
5. What lead times may be used by ASCP? ................................................................................... 73
6. How are lead times used by ASCP in planned order date calculation? ............................... 74
7. How does ASCP calculate supply dates? .................................................................................. 76
8. How can I release sales order from ASCP workbench? .......................................................... 76
9. Why do the Supply window and Resource Requirements window show different start
and end date/time of a planned order? ........................................................................................ 77
Appendix Constraint based planning .................................................... 78
Constraint types ................................................................................................................................ 78
Set constraints for different plan types .......................................................................................... 78
Rules used in constrained plans ..................................................................................................... 79
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.
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.
Source Data Setups
Setup inventory item attributes
There are several item attributes especially important to planning. Set them up properly to ensure
desired planning results.
Note:
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 auto–release criteria:
The new due date lies within the auto–release 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 Memory–based Planning Engine
Shipping Calendar
The shipping calendar indicates the valid working days for shipment activities originating from
suppliers and organizations. The planning engine does not recommend a shipment out from those
facilities if the date is a non-working day. The planning engine adjusts the shipment date if the current
shipment date is a non-working day. The planning engine considers the working days and times when
generating recommended transfers as part of the planning process.
The planning engine uses processing lead time to calculate the dock date during the planning and
scheduling process. Then it uses shipping calendars to calculate valid ship date (dock date - intransit
lead time) after the planning and scheduling process completes.
Receiving Calendar
The receiving calendar governs the receiving activities at the organizations or customer sites that
receive goods. The planning engine allows organizations to receive shipments only on a working day.
If the current shipment arrival date is a non-working day according to the receiving calendar, the
planning engine defers the receipt of the shipment until the next (or previous) working day.
When generating planned transfers between these two facilities, the planning engine assigns dock
dates on these planned transfers based on the receiving calendar of the organization.
Receiving calendars can also vary by combination of carrier and service level. You need to specify
valid receiving calendars for organizations and customers at the carrier and service levels.
Carrier Calendar
The carrier calendar indicates the working and non-working days and times for material that is
intransit using different means of transport. For example, certain methods of shipment such as parcel
carriers may not work on weekends. This may cause the transit time to be stretched over the
weekends. The planning engine needs to consider these non-working times of various transportation
modes that are modeled in the supply chain.
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.
Workday Calendar
Please refer to Routing Training Manual for workday calendar setups.
Setup routing
Please refer to Routing Training Manual for routing setups.
Refer to the table below for the setup of attributes relevant to planning.
Attribute Valid Comment Setup
values
Status Approved, ASCP only consider Approved and not
Debarred, Disabled suppliers
New
Attribute Valid Comment Setup
values
Disabled
Global? Yes, No ASCP only plans PO for suppliers with
Global = Yes
Refer to the table below for the setup of attributes relevant to planning.
Attribute Comment Setup
Processing This supplier-item attribute overrides the organization item attribute for
Lead Time processing lead time
Supplier Planning adjusts planned order release date so that deliveries occur on the
Capacity valid delivery date that coincides with the due date or the closest valid
Calendar 1 delivery date that occurs prior to the due date. This calendar is independent
of your workday calendar.
Order These supplier-item attributes override the organization item attributes for
Modifiers order modifiers.
Capacity This supplier-item attribute represents supplier item daily capacity in the
purchasing UOM.
Tolerance Use the Tolerance% and Days Advance Notice attributes together to state by
Fence 2 what percentage a supplier can change capacity if given a number of days
advance notice.
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.
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 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 Valid Comment Setup
values
Type Transfer Transfer From: Transfer between internal organizations,
From, enter source organization in the Org column. When it is
Make At, selected, Supplier and Supplier Site are disabled.
Buy From Make At: Make at an internal organization, enter
manufacturing organization in the Org column. When it
is selected, Supplier and Supplier Site are disabled.
Buy From: Purchase from an external enterprise, enter
Supplier and Supplier Site. When it is selected, the Org
column is disabled.
Allocation% The total allocation percentage for all sources within a
1 rank must add up to exactly 100. Planned order is split
among the sources according to their allocation
percentages.
Rank 1 The sources with the highest rank (lowest number) have
the highest priority in allocations. When sources of the
highest rank have no more capacity, allocation goes to
sources in the next highest rank, and so on.
Planning Checked, You cannot apply sourcing rules and bills of distribution
Active unchecked (make them Planning Active) until the sum of the
allocation percentages equals 100.
All Orgs Checked, Checked: This sourcing rule can apply to all
unchecked organizations.
Org Checked, Checked: This sourcing rule can apply to one
unchecked organization.
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. Time–phasing 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
Note: 1 not every item in a bill of material needs to be listed in an assignment set. Items that are made
and consumed at same organization need not to be assigned to an assignment set.
Assignment Hierarchy
The assignment hierarchy of sourcing rules and bills distribution is listed in the following table, rows
below override rows above them. Columns on the right override columns on the left.
Note: A global sourcing rule has an unspecified receiving organization. Bills of distribution are
global.
Since not all assignment types are valid for both sourcing rules and bills of distribution, the
effect of the Sourcing Rules vs. Bill of Distribution Assignments table is illustrated in a linear
hierarchy in the following table. The rows below override rows above them.
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
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 Data to be Collected
Order Management Sales order demands, Customers, Price lists
Purchasing Approved supplier list, Supplier capacity, Scheduled PO receipts
Inventory Operating units, Sub inventories, Organizations, Planners, Buyers, Product
families, Items, On hand quantities
Bills of material Bills of material, Resources, Routings, Operations, Workday calendars
Work in Process Scheduled work orders, Material transactions, Resource transactions
Cost Standard costs
MRP/Supply Chain Forecasts, Master demand schedules, Sourcing rules/Bills if distributions,
Planning 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.
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).
1. Tab to the Parameters field, Planning Data Pull Parameters form appears
2. Select individual parameter as explained in the table below, then click on OK
Parameter Values
Instance Source instance code from list of values.
Collection Group You can decide to collect data from All enabled organizations or only
form the current organization
Number of Workers 1 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.
Timeout (Minutes) 1 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 Yes (default) or No. Setting this to Yes wipes out all data in the APS
Data 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.
Parameter Values
Collection Method 2 Complete Refresh/Targeted Refresh/Net Change
Refresh. See the explanation in the Data collection methods section of
this manual
Analyze Staging Tables 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.
Business objects 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
Parameter Values
Instance Source instance code from list of values.
Timeout (Minutes) 1 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.
Number of Workers 1 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.
Recalculate Resource This defaults to the value (Yes or No) that you set for the Resources
Availability 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.
Parameter Values
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.
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
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.
Use the information in the following table to specify parameters on the Main tab.
Parameter Description Comment Setup
Assignment The assignment set that holds the sourcing
Set rules and bills of distribution that define the
rules for material flow within your supply
chain.
Demand When ASCP does detailed scheduling, it
Priority Rule 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.
Overwrite1 Overwrite planned orders.
Append Appends new planned orders to current
Planned plan.
Orders1
Planned This parameter and the next one, Planning
Items2 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.
Material Choose from Operation Start Date or Order Order State Date is
Scheduling Start Date scheduling methods. If you usually an earlier date
Method choose Operation Start Date, material is than the Operation
scheduled to arrive at the start of the Start Date and
operation for which it is required. If you therefore this
choose Order Start Date, material is selection represents
scheduled to arrive at the start of the order the more conservative
for which it is required. planning logic of the
two options.
End Item If Decision Rules tabbed region > Use End
Substitution Item Substitutions selected, select a
Set 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.
Parameter Description Comment Setup
Schedule By Set this option to instruct the planning Select one of the
engine to: following sales order
Plan supplies based on sales order line line dates:
request, promise, or schedule dates for Schedule Ship Date
either ship or arrival Schedule Arrival Date
Consume forecasts based on sales order line Request Ship Date
request, promise, or schedule dates. You Request Arrival Date
must provide forecast dates that match Promise Ship Date
your choice of this plan option; for example, Promise Arrival Date
if you select Promise Ship date for this plan The default is
option, make sure your forecast dates are in Schedule Ship Date.
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.
Demand If you want to limit a production plan to a This field is active
Class demand class, enter it. only for a Production
Plan/MPS schedule.
Move Jobs to Check this option if you want to generate
PIP planned order supply even in the absence
of demand in order to ensure that inventory
is held on the manufacturing floor only for
items designated as Planned Inventory
Points.
Display Key Check this option to calculate key
Performance performance indicators for the plan.
Indicators
Demand Time Check this option to enforce demand time Demand time fence is
Fence Control fence control. an item attribute
Planning Check this option to enforce planning time Planning time fence is
Time Fence fence control. an item attribute
Control
Lot for Lot Check this option to force the creation of a Order quantity
separate supply for each demand. This modifiers such as
prevents the creation of aggregate supplies Minimum Lot Size
that satisfy multiple demands. and Fixed Lot
Multiple override this
option
Include Select this plan option to instruct the To mark an item as a
Critical planning engine to plan considering critical critical component,
Components components. Depending on the plan type select its item
and the planning item types, the planning attribute Critical
engine may plan critical components and Component.
not plan other components or components
of those components.
Do Not The planning engine should use forecast
Spread entries as they exist for planning.
Forecast
Parameter Description Comment Setup
Spread The planning engine should spread
Forecast aggregate forecast demand evenly across
Evenly the daily buckets from the workday
calendar.
Forecast Select a forecast distribution assignment set The rules to distribute
Distribution for the global forecasting process. The sales orders are in
Assignment forecast distribution assignment set plan option
Set contains global sourcing rules used to Assignment Set.
distribute global forecasts over multiple
inventory organizations:
Consume by The forecast consumption process does not
Forecast search outside of the consumption bucket
Bucket for forecasts and sales orders except in daily
buckets.
Explode Select this plan option to instruct the Clear this plan option
Forecast planning engine to explode forecasts as if you have arranged
follows during the consumption process: for this explosion to
- Product family forecasts to product family occur in the source
member item forecasts instance or in Oracle
- Model forecasts to other model, option Demand Planning
class, and item forecasts. before the planning
This option applies to forecasts with run.
forecast control Consume and derive.
Backward If you are bringing in unconsumed forecast
Days 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 pre-
consumed 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.
Forward Days 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.
Enable Check this option to calculate pegging
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.
Parameter Description Comment Setup
Peg Supplies Check this option to calculate pegging so Do not check it.
by Demand that on-hand and firm supplies are pegged Instead, set profile
Priority to demands in demand priority order (as option MSC: Use
defined by you in a priority rule) within the FIFO Pegging to Yes.
time period set by the profile option MSO:
Firm Supply Allocation Window (days).
Pegging – Choose a reservation level: Planning Group, Do not use
Reservation Project, Project-Task, or None.
Level
Pegging – Choose a hard pegging level: Project, Do not use
Hard Pegging Project-Task, or None.
Level
Forecast If you are bringing in unconsumed forecast
Consumption scenarios from Oracle Demand Planning as
Backward demand schedules into Oracle ASCP and
Days would like to do forecast consumption
inside ASCP (as opposed to bringing in pre-
consumed 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.
Forecast This parameter allows a sales order Do not use
Consumption demand to consume forecast demand even
Forward Days if the forecast demand is up to the specified
number of days later than the sales order
demand.
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 Effects
Orders
All The planning process overwrites all entries, planned and firm
planned, from the current material plan.
None The planning process does not overwrite any firm planned
orders. It does, however, overwrite any suggested planned
orders that are not firm.
Overwrite Append Planned Effects
Orders
Outside The planning process overwrites all entries from the current
planning time plan, planned and firm planned, outside the planning time
fence 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
Unchecked 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.
Checked 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.
All Checked 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.
Outside Checked This option allows you to create an extension to the current
planning time material requirements plan, delete planned and firm planned
fence 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 short–term plan and allow the
long–term 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.
None 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 short–term
sections of your material requirements plan. You can extend
the plan horizon without altering existing firm planned orders.
Overwrite Append Planned Effects
Orders
None Unchecked 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 on–line 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 Item’s 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 Plan type Planned Items in the plan
value
All planned items Master Plan All items in the planned organizations having MRP/MPS
Planning Method attribute value of
MPP planning
MRP and MPP planning
MPS and MPP planning
Plus:
MRP planned and MPS planned items that are in between
the above items in the bills of material.
All items in the input schedules.
All planned items Production Plan All items in the planned organizations having MRP/MPS
Planning Method attribute value of
MPS planning
MPS and MPP planning
Plus:
MRP planned and MRP/MPP planned items that are in
between the above items in the bills of material.
All items in the input schedules.
All planned items Manufacturing Plan All items in the planned organizations except those having
MRP/MPS Planning Method of Not Planned
Demand schedule Master Plan All items in the input demand schedules, and all
items only components of these items that have MRP/MPS Planning
Method attribute code of:
MPP planning
MRP and MPP planning
MPS and MPP planning
Plus:
MPS and MRP planned items that are in between the
above items in the bills of material
Planned Items Plan type Planned Items in the plan
value
Demand schedule Production Plan All items in the input demand schedules, and all
items only components of these items that have MRP/MPS Planning
Method attribute code of:
MPS planning
MPS and MPP planning
Demand schedule Manufacturing Plan All items in the input demand schedules, and all
items only components of these items that have MRP/MPS Planning
Method attribute code of:
MRP planning
MRP and MPP planning
Supply schedule Master Plan All items in the input supply schedules, and all
items only components of these items that have MRP/MPS Planning
Method attribute code of:
MPP planning
MRP and MPP planning
MPS and MPP planning
Plus:
MPS and MRP planned items that are in between the
above items in the bills of material
Supply schedule Production Plan All items in the input supply schedules, and all
items only components of these items that have MRP/MPS Planning
Method attribute code of:
MRP planning
MRP and MPP planning
Supply schedule Manufacturing Plan All items in the input supply schedules, and all
items only components of these items that have MRP/MPS Planning
Method attribute code of:
MPS planning
MPS and MPP planning
Demand and Master Plan All items in the input demand and supply schedules, and
Supply schedule all components of these items that have MRP/MPS
items Planning Method attribute code of:
MPP planning
MRP and MPP planning
MPS and MPP planning
Plus:
MPS and MRP planned items that are in between the
above items in the bills of material
Demand and Production Plan All items in the input demand and supply schedules, and
Supply schedule all components of these items that have MRP/MPS
items 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
Planned Items Plan type Planned Items in the plan
value
Demand and Manufacturing Plan All items in the input demand and supply schedules, and
Supply schedule all components of these items that have MRP/MPS
items 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.
Use the information in the following table to set parameters on the Organizations tab.
Parameter Description Note Setup
Global Select the names of Oracle Demand
Demand Planning scenarios that drive this
Schedules plan. You can select demand-
planning scenarios that do not
reference an organization
(organization dimension set to All
Organization).
Ship To Select a forecast consumption level You can select:
Consumption for the Oracle Demand Planning - Customer
Level scenario. The global forecasting - Customer Site
process consumes forecast entries - Zone
that have Ship To value the same as - Customer Zone
this plan option. - Demand Class
- Item
The choices in the list of
values changes depending
on the published level of the
scenario.
Org The plan’s organization.
Description Description of the owning
organization.
Net WIP Select to consider discrete jobs and
other production orders as supply in
the planning demand/supply
netting process.
Parameter Description Note Setup
Net If checked, ASCP generates pegging
Reservations of on-hand supply to sales orders
that matches the reservations
recorded in the source transaction
system.
Net Purchasing 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.
Plan Safety Select to consider plan safety stock
Stock demand and supply in the planning
demand/supply netting process.
Include Sales Select to invoke forecast
Order1 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
Bill of Select Bill of Resources from the list
Resource of values if one of the Routings is set
to BOR on Aggregation tab.
Simulation Set 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.
Demand Select the name of your demand
Schedules2 schedule/forecast/plan.
Parameter Description Note Setup
Ship To See above See above
Consumption
Level
Interplant If selected, the planning engine uses
only interorganization orders and
demands from interorganization
planned orders. If cleared, the
planning engine uses demands from
all planned orders.
Supply Select the name of your supply
Schedules schedule for each organization.
Subinventory Opens the Subinventory Netting
Netting window.
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 Description Setup
Constrained If selected, Enforce Demand Due Dates is selected, all fields in
Plan 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.
Parameter Description Setup
Enforce Check this option if you want demand due dates to be your
Demand Due hard constraint (that is, respected in lieu of material and
Dates resource capacity constraints, if there is conflict).
Enforce Check this option if you want material and resource capacity
Capacity constraints to be respected in lieu of demand due date
Constraints constraints.
Start Date Displays the start date for each bucket type.
Buckets Displays the number of buckets of this bucket type.
Resource Select Yes to consider resource constraints for the bucket.
Constraints
Supplier Select Yes to consider supplier capacity constraints.
Capacity
Constraints
Enforce Select this plan option to instruct the planning engine to
Purchasing constrain the plan by purchased item lead times (item attributes
Lead-time or approved supplier list).
Constraints Clear it to instruct the planning engine never to miss a demand
due date because of a purchased item lead time.
Scheduling Specify whether to enable detailed scheduling.
Minutes Size Specify the bucket size in minutes for the Days planning
Bucket Size period.
(in
Days)
Hours Bucket Specify the bucket size in hours for the Days planning period.
Size (in
Days)
Days Bucket Specify the bucket size in days for the Days planning period.
Size (in
Days)
Calculate If selected, the program will calculate resource capacity
Resource utilization.
Requirements
Planned Select All Resources or Bottleneck Resources. If you have
Resources 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.
Bottleneck If you have defined bottleneck resource groups in Oracle Bills of
Resource Material and you want to detail schedule only the bottleneck
Group resources, select its name.
Decision Rules tab
Use the information in the following table to specify parameters on the Decision Rules tab.
Parameter Description Setup
Use End Item If selected, use end item substitute prior to creating new planned
Substitution orders. If cleared, use only the demanded item. Enter the End
Item Substitution Set in the Main tabbed region.
Use Alternate If selected, use primary resource and use alternate resource only if
Resources necessary. If cleared, use only primary resources.
Use Substitute If selected, use primary components and use substitute
Components components only if necessary. If cleared, use only primary
components only.
Use Alternate If selected, use primary routings and use alternates only if
BOM/Routing necessary. If cleared, use only primary bills of material and
routings.
Use Alternate If selected, use primary sources and use alternate sources only if
Sources necessary. If cleared, use primary sources only. The planning
engine does not use alternate sources (rank 2 or higher) as a
sources of supply.
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)
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
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
Supply chain structure
Supply Chain Structure – Items and Item Details
Right Click on Item (in Navigator) > Items
Key data displayed include Lead Times and Order Quantities
Variety of other planning related item attributes available for display through Folder
functionality
Items window is a launching pad to more detailed structural information on the item
Supply Chain Bill
o Displays Sourcing and BOM structure for the item
o Can also show the “Reverse BOM” I.e. the end items where a component is used
Sources
o Displays Sourcing (other orgs or Suppliers) from which the Item is sourced from
o Shows relative allocation percentages or ranks
o Supplier Information: Lead Times, Costs, time varying capacities and flex fences
Destinations
o Displays Destinations (other orgs) to which this item is shipped to
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 item’s 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:
Components:
Routing Operations and Resources:
Supply Chain:
Supply Chain Structure – Resources
Right Click on Resource (in Navigator) > Resources
Displays information about the resource – Department, Type, Cost etc.
Items – Shows the items made on this resource Availability
o Summary: Displays summary of resource availability at the planning time bucket level
o Detail: Shows the shift level capacity for the selected day. Also allows for update of
resource availability
Gantt Chart – Shows graphical view of activities planned on the resource
Requirements – Shows Forms based view of activities planned on the resource
Gantt Chart:
Availability:
1. Material Plan: Classical Planner spreadsheet showing supplies and demands and projected
available balances at the planning bucket level
2. Resource Capacity: View of Resource hours available versus used along with capacity
utilization % information
3. Supplier Capacity: Shows Supplier capacity (available versus used) by planning time bucket
and tracks the cumulative available at any point in time
4. Transportation Capacity: Shows the capacity available versus used for transportation resources
Navigation to the horizontal plan is possible either from the navigator tree or from other windows
where the relevant context is available such as Item, Resource or Supplier
Resource View:
Supply chain plan executions
Supply Chain Planning Actions – Firming Orders in Supply/Demand Window
Gantt Chart allows firming of specific resource activities
Entire orders (supplies) can be firmed using the Supply/Demand window
Select “Firm” checkbox
Enter
o New Date
o New Quantity
Optionally enter
o New sourcing information
o New BOM/Routing information
When ASCP runs again (“Overwrite” option should be set appropriately) it will retain this
planned order (all non firm planned orders are wiped out and regenerated)
Can also enter new supplies and demands in the Supply/demand Window
Supply Chain Planning Actions – Rerunning the Plan
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 re-planned (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)
Note:
User changes are shown in pink color
Supplies that are changed after batch/online replan are shown in blue color
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
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.
Running net change replan simulations
1. Before running net change replan simulation, save and make a copy of your baseline plan before
running replan and make modifications only to the copy (“current”).
2. Click Plan on the Menu, select Save Actions. This will save a new version of the plan.
You may save as many versions as you need.
3. Go to the left pane of the Workbench, change to View By Actions and highlight the “Current”
version.
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
On the Add Bookmark window, enter a Bookmark Name, then click OK.
Undo action
On the Undo Summary window, select a change you initiated in the online planner. Click Undo.
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.
You can invoke the report from a menu and print the worksheets selectively. No additional change or
set up in the application is required in order to generate the report. You can select the plan,
organizations, items, resources, projects, and many other parameters to filter the information to
display in the report and you can change these parameters at any time.
To run the Plan Detail Report, it must set up and configured in Oracle Discoverer.
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.
2. How are planning buckets and horizon calculated?
You can assign x days + y weeks + z periods planning buckets. The planning horizon is
approximately the total days covered by these buckets. However, the weekly buckets must
start on a week start date, and the same is true that the period buckets must start on a period
start date. Consequently, the planning horizon may usually longer than that calculated from x
days + y weeks + z periods. See the illustration below:
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 buckets—regardless 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 16-JUL-2006 is 31-JUL-2006. From 31-
JUL-2006 on, the 8th periods ends on 01-APR-2007. The plan horizon is therefore between 20-
MAR-2006 and 01-APR-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
Period start date. Note
June 2006 is a five-
week period.
The lead times below can be defined on subinventory-item level. Their meanings are the same
as those defined on organization level.
Preprocessing
Processing
Postprocessing
You can define item-supplier-supplier site specific processing lead time, too. Since
preprocessing and postprocessing are controlled by your organization and it does not make
sense to set them at supplier-supplier site level.
When you define Kanban pull sequence, you can give a lead time as transfer time between two
pulling points.
When defining shipping network, you can specify Intransit lead times between two
organizations for different shipping methods.
When defining inter-location transit time, you can specify inbound Intransit lead times
between supplier and your organization for different shipping methods, and outbound
Intransit lead times between your organization and customer site for different shipping
methods.
On a transfer from or buy from sourcing rule, you may designate shipping methods and
intransit lead times (the shipping methods and intransit lead times must already be defined in
shipping network for transfer from and in inter-location transit time for buy from).
5. What lead times may be used by ASCP?
See the table below for the lead times used by ASCP:
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.
6. How are lead times used by ASCP in planned order date calculation?
For purchased supply:
Note: the transit time defined at inter-location transit time is not used by ASCP for purchased
item.
Need By Date (receiving organization calendar): Date material is required to satisfy demand.
Demand Due Date (receiving organization calendar):
Unconstrained plans: Need By Date
Constrained plans: Forward scheduling from the constraint.
Suggested Dock Date (receiving organization calendar): Due Date - Postprocessing
Suggested Ship Date (shipping organization calendar):
Unconstrained plans: Dock Date - Intransit Time
Constrained plans: Dock Date - Intransit Time, considering constrained transportation
duration. The planning engine considers transportation constraint maximum transfer
quantity per day. Intransit Time is calendar days.
Suggested Start Date (shipping organization calendar):
Unconstrained plans: Ship Date - Processing
Constrained plans: Ship Date. The planning engine does not consider a build time
because the supply may be on-hand.
Suggested Order Date (receiving organization calendar):
Unconstrained plans: Planned order Start Date - Preprocessing
Constrained plans: Ship date in the receiving organization, if the shipping organization
is a planned organization. The constrained plan uses material and resource constraints
in the shipping organization.
The diagram shows calculated dates for transfer supplies in an unconstrained plan.
Note: the intransit lead time defined on shipping network is used by ASCP.
Old Due Date, Old Dock Date, and Original Need By Date are the original dates from the
source system for scheduled receipts.
8. How can I release sales order from ASCP workbench?
In a constrained plan, ASCP may suggest rescheduling sale order. It may select a different
sources based on global supply availability and constraints that you may have in the supply
chain. These changes can be published to OM.
Navigate to Supply Chain Plan > Workbench > Tools > Preferences > Other tab.
Select the Include Sales Orders check box.
Select the Release check box for each sales order or the Select all for release menu
option to release the recommendations to update the sales orders.
You can manually change the Implement Date in the Release Properties window to
override the plan recommendations. When the sales order is released, the Implement
Date is populated to the Schedule Ship Date on the sales order line in Oracle Order
Management.
9. Why do the Supply window and Resource Requirements window show different start and end
date/time of a planned order?
On example shown below you can see the planned order start date is 29-DEC-2007 23:59:00
and it due date is 26-JAN-2007 23:59:00 from the Supply 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.