ASCP - Oracle Advanced Supply Chain Planning Training Manual
ASCP - Oracle Advanced Supply Chain Planning Training Manual
Table of Contents
Introduction ...................................................................................................................... 3
Intended audience ................................................................................................................................... 3
List of attendees ....................................................................................................................................... 3
Related training materials ...................................................................................................................... 3
Log onto Oracle Applications ................................................................................................................ 3
Reports ............................................................................................................................. 74
Plan comparison report ........................................................................................................................ 74
Plan detail report ................................................................................................................................... 75
Audit information reports .................................................................................................................... 75
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
3. Choose Advanced Supply Chain Planner responsibility (you may have a customized
responsibility with a different name assigned to you. Check with your instructor about
which responsibility you should use)
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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
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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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
Disabled
Global? Yes, No ASCP only plans PO for suppliers with
Global = Yes
Supplier planning constraints
Enhance sourcing provides the ability to model flexible supplier capacity.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
Refer to the table below for the setup of attributes relevant to planning.
Attribute Comment Setup
Processing This supplier-item attribute overrides the organization
Lead Time item attribute for processing lead time
Supplier Planning adjusts planned order release date so that
Capacity deliveries occur on the valid delivery date that
Calendar 1 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.
Order These supplier-item attributes override the
Modifiers organization item attributes for order modifiers.
Capacity This supplier-item attribute represents supplier item
daily capacity in the purchasing UOM.
Tolerance Use the Tolerance% and Days Advance Notice
Fence 2 attributes together to state by 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
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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.
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 assigned to any items or group
of items. Assignment sets are used to associate items with sourcing rules and bills of
distribution.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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
From, organizations, enter source organization in the Org
Make At, column. When it is selected, Supplier and Supplier
Buy From Site are disabled.
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
1 a 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
Active unchecked distribution (make them Planning Active) until the
sum of the allocation percentages equals 100.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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: 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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
Note: If Oracle Demand Planning is installed and integrated with ASCP, its output is directly
visible to ASCP as planning inputs.
Data collection methods
Collecting data can take a significant amount of time compared to the time for the overall
planning cycle. Choose the collection method best suit for you needs. There are three collection
methods:
The Complete Refresh method clears all transaction data for all business entities from
the planning server (for the source instance being collected), and then copies over
information about the user-selected entities. This method can be time consuming.
The Net Change Refresh method copies only incremental changes to business entities
to the planning server (and is thus faster), but is supported mainly for demand and
supply business entities.
The Targeted Refresh method clears transaction data for only the user-selected
business entities from the planning server, and then copies the entity information over
from the transaction instance. Information about non-selected entities remains intact
on the planning server. All planning business entities are supported by Targeted
Refresh collections.
Continuous collections process: The continuous collections process is an automated
process of data collection that efficiently synchronizes the data on the planning server
by looking up the sources. If you opt for continuous collections, the system
automatically determines the type of collection that needs to be run on entities
selected by you. The continuous collections process collects data from the sources
with the least user intervention. The Continuous Collections concurrent program
performs continuous collections. Continuous collections is not covered in this training.
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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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).
Run data collection
Navigation path: Advanced Supply Chain Planner>Collections>Oracle Systems> Standard
Collection
1. Tab to the Parameters field, Planning Data Pull Parameters form appears
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
Parameter Values
Purge Previously Collected Yes (default) or No. Setting this to Yes wipes out all data in the
Data 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.
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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
Parameter Values
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
Availability Resources Availability business entity in the Planning Data Pull
Parameters window. The value that you set here is the one that
actually determines whether resources availability is collected or
not.
Recalculate Sourcing This defaults to the value (Yes or No) that you set for the Sourcing
History 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
Define an ASCP plan
ASCP plan classes
Oracle ASCP offers the following plan classes.
Unconstrained
Resource Constrained
Material Constrained
Material and Resource Constrained
Optimized
These classes are discusses in the table below.
Plan Class Planning Goals Scenario
Horizon
Unconstrained Long Term How much resource capacity Decisions can be made on
Future and material availability do I Resource
need to arrange in order to acquisition/disposition and
satisfy all anticipated demand supplier sourcing to address the
in a timely manner? exceptions.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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
Each ASCP plan type will include a subset of items in its planning process. The items included
depend upon the plan type and the item’s the MRP Planning Type attribute.
Define a plan name
Navigation path: Advanced Supply Chain Planner>Supply Chain Plan>Names
Main tab
Use the information in the following table to specify parameters on the Main tab.
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 Effects
Planned 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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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 Master Plan All items in the planned organizations having
items 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 Production Plan All items in the planned organizations having
items 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 Manufacturing All items in the planned organizations except those
items Plan having MRP/MPS Planning Method of Not Planned
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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
Schedules drive this plan. You can select
demand-planning scenarios that
do not reference an organization
(organization dimension set to All
Organization).
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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
Plan 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.
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
Constraints date 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
Lead-time attributes 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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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
Substitution planned 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
Resources only if 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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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)
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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:
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
Components:
Supply Chain:
Gantt Chart:
Availability:
Requirements:
Can have all exception groups pre-expanded (Tools > Preferences > Other)
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
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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
Order View:
Resource View:
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
Note:
User changes are shown in pink color
Supplies that are changed after batch/online replan are shown in blue color
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
9. Save
Note: when you manually create supply, the order type is Planned Order and the order is Firm.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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
Note: It is recommended that the online planner be stopped as soon as a series of simulations is
complete. An active online planner could consume a lot of system resource (CPU/memory).
Viewing Undo Summary
The Undo Summary window lists the users and timestamps for every action/change made to
the plan. It includes online planning changes, sorted by user.
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
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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.
Plan detail report
The Planning Detail Report provides a simple and consolidated report that shows the output of
the advanced supply chain planning process. The report gives detailed information to help you
understand and analyze the supply chain planning results by presenting the data selectively and
coherently. For a given Supply Chain Plan, the report includes the relevant details about items,
resources, gross requirements, scheduled receipts, planned orders, plan constraints, and
exceptions in separate worksheets.
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.
Audit information reports
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
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
Calendar
Code
Non-workdays
are dimmed
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
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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).
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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.
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.
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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
Suggested Order Date: Planned order Start Date - Preprocessing. It is the date on which
you should place the order.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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?
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88
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.
ASCP - Oracle Advanced Supply Chain Planning Training Manual OracleApps88