ASCP Training Manual v1.2

ASCP Training Manual

Author:Creation Date:Last Updated:Document Ref:Version:

Approvals:

Document Control

Change Record

Date Author Version

Change Reference

Reviewers

Name Position

Distribution

Copy No.

Name Location

1

234

2 MSAT Internal Page 7

Table of Contents

Document Control......................................................................................2Introduction................................................................................................5

Intended audience.......................................................................................................5List of attendees.........................................................................................................5Related training materials...........................................................................................5Log onto Oracle Applications....................................................................................5

Overview of Oracle Advanced Planning....................................................6APS data flow............................................................................................................6Planning cycle............................................................................................................7

Source Data Setups.....................................................................................7Setup inventory item attributes..................................................................................7MPS/MRP planning attributes.................................................................................11Lead times attributes................................................................................................17Shipping, Receiving, Carrier, and Supplier Capacity Calendars.............................18Workday Calendar....................................................................................................20Setup resource and department................................................................................20Setup routing............................................................................................................20Setup supply chain...................................................................................................20Order management...................................................................................................28

Data Collection.........................................................................................28Scope of data collection...........................................................................................28Data collection methods...........................................................................................29Run data collection...................................................................................................30

Define an ASCP plan................................................................................33ASCP plan classes....................................................................................................33ASCP plan types......................................................................................................34Define a plan name...................................................................................................35Set plan options........................................................................................................35Launch a plan...........................................................................................................47Copy a plan..............................................................................................................47

Planner Workbench..................................................................................48Plan Navigator..........................................................................................................49Supply chain structure..............................................................................................50Supply chain plan result analysis.............................................................................56Supply chain plan executions...................................................................................65Personal and public queries......................................................................................67

Simulation net change re-plan..................................................................68Simulate changes......................................................................................................68Simulation modes.....................................................................................................71


Running net change replan simulations...................................................71Reports......................................................................................................76

Plan comparison report............................................................................................76Plan detail report......................................................................................................76Audit information reports.........................................................................................76

Practicing labs..........................................................................................77FAQ..........................................................................................................77

1. What calendar quarterly type does ASCP support?.............................................772. How are planning buckets and horizon calculated?.............................................773. How do I know which days are workdays, which day is week start date and which is period start date?........................................................................................784. What lead-times can you define in Oracle Applications?....................................795. What lead times may be used by ASCP?.............................................................816. How are lead times used by ASCP in planned order date calculation?...............817. How does ASCP calculate supply dates?.............................................................838. How can I release sales order from ASCP workbench?.......................................849. Why do the Supply window and Resource Requirements window show different start and end date/time of a planned order?..............................................................84

Appendix Constraint based planning........................................................85Constraint types........................................................................................................86Set constraints for different plan types.....................................................................87Rules used in constrained plans...............................................................................87


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

Related training materials

Inventory management and material transaction in discrete manufacturing is discussed in Inventory Training Manual

Product manufacturing process is covered in Routing Training Manual Product structure is covered in BOM Training Manual For discrete jobs, please refer to WIP Training Manual For sourcing and supplier constraint setups, please refer to Purchasing Training

Manual

Log onto Oracle Applications

1. Enter URL of Oracle Applications home page to your browser: http://2. Enter in your user ID and password


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)

Overview of Oracle Advanced Planning

APS data flow

The diagram below illustrates major information flows between the components of the Oracle Advanced Planning and the rest of Oracle Applications.


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.

For item setup in general, please refer to Inventory Training Manual.

Navigation path: Inventory>Items>Master Items>General Planning (T)

7 MSAT Internal

Or

Inventory>Items>Organization Items>General Planning (T)

Refer to the table below for the setup of each attribute.

Attribute Valid values

Purpose Comment Setup

Make or Buy

Make, Buy

Determine whether the item is manufactured internally or purchased

You cannot change this value if open orders exist for the item.

Planner Planner Id

Assign material planner to plan this item

If an item is vendor managed, you must enter a planner for the item.

Inventory Planning Method

Not Planned, Min-Max, Reorder Point

Assign planning method to the item

Min-Max: define a minimum quantity on hand. Reorder when this quantity is reached. Also define a maximum on–hand quantity that you do not want to exceed.Reorder point: reorder point is calculated based on the planning information you define for this item.

Min-Max Minimum Quantity

Enter the quantity minimum for min–max planning.

If an item is min–max planned, the Min–Max Planning Report suggests a new order when quantity drops to the min–max minimum.

Min-Max Maximum Quantity

Enter the quantity maximum for min–max planning.

If an item is min–max planned, the Min–Max Planning Report suggests an order that brings on–hand up to the min–max maximum.




Order Quantity Minimum

Enter the minimum order quantity or repetitive rate. Use this to define an order quantity below which it is unprofitable to build or purchase the item.

Planning uses this to modify planned order quantities or repetitive daily rates. For discrete items, when net requirements fall short of the minimum order quantity, planning suggests the minimum order quantity.

Order Quantity Maximum

Enter the maximum order quantity or repetitive rate of the item.

Planning uses this to modify the size of planned order quantities or repetitive daily rates. For discrete items, when net requirements exceed the maximum order quantity, planning suggests the maximum order quantity.

Cost Order Enter the fixed cost associated with placing an order of any quantity.

Cost Carrying %

Enter the percentage used to calculate the annual carrying cost.

This is the percentage of the unit cost that represents internal cost to stock one unit for one year.

Source Type Inventory, Supplier, Sub Inventory

Assign replenishment source type

Inventory: Fill requests by creating internal requisitions that become internal sales orders, pulling stock from existing inventory.Supplier: Fill requests by creating purchase requisitions that become purchase orders, procuring the item from a supplier.Subinventory: Fill requests by creating move order requisitions that become move orders, pulling stock from an existing sub inventory.If you are using Supplier Scheduling, it is generally recommended that this field be left blank. Otherwise, it could override your sourcing rules.

Source Organization

Optionally enter the organization from which an internal requisition draws the item.

This applies only when Inventory is the replenishment source type.




Source Subinventory

Enter the sub inventory within the source organization from which an internal requisition draws the item.

This applies only when Inventory or Subinventory is the replenishment source, and only when you specify a source organization.

Safety Stock Method

Select an option to plan use of fixed or dynamically calculated safety stock quantities.

Used to direct safety stock calculation method when Oracle Inventory Optimization is NOT activated.For MRP/MPS planned items, you must set the Inventory Planning Method attribute to Not planned, then choose the MRP planned percent option here.

Safety Stock Bucket Days

Enter the number of days to dynamically calculate safety stock quantities.

The planning process multiplies the Safety Stock Percent bythe average gross requirements and divides by the number of days you enter here. Used by planning modules only.

Safety Stock Percent

Enter the percent to dynamically calculate safety stock quantities for the item.

The planning multiplies this percent by the average gross requirements and divides by the Safety Stock Bucket Days.The planning process uses this attribute when you set Safety Stock to MRP planned percent.Used by planning modules only.

Fixed Order Quantity

Enter the quantity used to modify the size of planned order quantities or repetitive daily rates.

When net requirements fall short of the fixed order quantity, the planning suggests the fixed order quantity. When net requirements exceed the fixed order quantity, the planning suggests multiple orders with the fixed order quantity. For discrete items, use this attribute to define a fixed production or purchasing quantity. Used by planning modules only.

Fixed Days Supply

Enter the number of days used to modify the size and timing of planned order quantities.

The planning suggests planned order quantities that cover net requirements for the period defined by this value. The planning suggests one planned order for each period. Used by planning modules only.




Fixed Lot Multiplier

Enter the fixed lot multiple quantity or repetitive rate (units per day).

Planning uses this to modify the size of planned order quantities or repetitive daily rates. When net requirements fall short of the fixed lot size multiplier quantity, planning suggests a single order for the fixed lot size multiplier quantity. When net requirements exceed the fixed lot size multiplier quantity, planning suggests a single order that is a multiple of the fixed lot size multiplier.

MPS/MRP planning attributes






Planning Method

Not Planned, MRP planning, MPS planning, MRP/DRP Planned, MPS/DRP Planned, DRP Planned

Select the option that Planning uses to decide when to plan the item

Not Planned: The item does not require long–term planning of material requirements. Choose this option for high volume and/or low cost items that do not warrant the administrative overhead of planning; typically dependent demand items. You cannot use this option unless the Pick Components attribute is checked.MRP planning: Choose this option for non–critical items that do not require manual planning control, typically dependent demand items.MPS planning: You master schedule the item and require manual planning control. Choose this option for items with independent demand, items that are critical to your business, or items that control critical resources.MRP/DRP Planned: Choose this option when you want both MRP and DRP planning for the item.MPS/DRP Planned: Choose this option when you want both MRP and DRP planning for the item.DRP Planned: Choose this option when you have multiple organizations for which you do Distribution Requirements Planning for the item.

Forecast Control

Consume,Consume and derive, None

Select an option to determine the types of demand you place for the item. This guides the key processes of two–level master scheduling: forecast explosion, forecast consumption, planning, production relief, and shipment relief.

This is appropriate only for items that are models, option classes, options, or mandatory components of models and option classes.Consume: forecast demand directly, rather than by exploding forecast demand.Consume and derive: forecast demand directly, explode forecast demand, or use a combination of both methods.None: place sales order demand but do not forecast demand.




Exception Set Enter the name of the planning exception set that groups together the sensitivity controls and exception time periods for item–level planning exceptions for the item.

The item–level planning exceptions include: overcommitted, shortage, excess, and repetitive variance. The planning process uses this attribute to decide when to raise planning exceptions for the item.

Create Supply

Indicates if supply can be suggested for this item.

Critical Component

If selected, flags the item as a critical component for MPS and DRP planning.

This allows you to plan master scheduled items with respect to only critical component and their material resource constraints.

Pegging Soft Pegging,End Assembly Pegging,End Assembly/ Soft Pegging,Hard Pegging,End Assembly/ Hard Pegging,None

Enter the pegging option.

Soft Pegging: allocates supply to demand based on the Reservation Level option set in the Plan options.End Assembly Pegging: traces the end assembly the item is pegged to at the top of the bill of material. Even if you do not select end assembly pegging, you can still calculate and view end assemblies on–line.End Assembly/ Soft Pegging: Choose this option for both soft pegging and end assembly pegging.Hard Pegging: allocates supply to demand based on the Reservation Level option set in the Plan options. This pegs supply to demand and demand to supply by project at all levels of a bill of material. This allows you to pre–allocate supply to demand and generate planned orders based on the plan level options.End Assembly/ Hard Pegging: Choose this option for both hard pegging and end assembly pegging.None: disables project material allocation, end assembly pegging, and full pegging.

Planned Inventory Point

Indicates if the item is an Inventory Point item.

This means that material can be stored at the item level without losing materials or quality characteristics. Inventory Points generally point to major stocking phases in the manufacturing cycle.




Shrinkage Rate

Enter a factor that represents the average amount of material expected to lose during manufacturing or in storage.

The planning process inflates demand to compensate for this expected loss.

Round Order Quantities 1

Indicate whether the planning process uses decimal or whole number values when calculating planned order quantities or repetitive rates.

When this option is checked, decimal values round up (never down) to the next whole number. The planning process carries any excess quantities and rates forward into subsequent periods as additional supply.

Acceptable Early Days 2

Enter the number of days before which the planning process will not reschedule orders.

The planning process only suggests rescheduling out if the new calculated order date is later than the original order due date plus the acceptable early days; the new calculated order does not violate the order of current scheduled receipts.This applies to discrete items only.

Calculate ATP 3

Indicate whether to calculate and print available to promise (ATP) on the Planning Detail Report.

On the Planning Detail Report, ATP is calculated asATP = Planned production – committed demand

Reduce MPS 4

None, Past Due, Demand Time Fence, Planning time Fence

Decide when to reduce master production schedule (MPS) quantities to zero.

None: Do not reduce order quantities on the MPS.Past Due: Reduce order quantities on MPS entries to zero when the entry is past due.Demand Time Fence: Reduce order quantities on MPS entries to zero when the due date moves inside the demand time fence.Planning time Fence: Reduce order quantities on MPS entries to zero when the due date moves inside the planning time fence.




Planning Time Fence Days 5

Cumulative mfg. lead time, Cumulative total lead time, Total lead time, User–defined

Determine a point in time inside which certain restrictions on planning recommendations apply.

Planning calculates the planning time fence as the plan date (or the next workday if the plan is generated on a non workday) plus the value entered here.Cumulative mfg. lead time: The cumulative manufacturing lead time for the item.Cumulative total lead time: The total manufacturing lead time for the item.Total lead time: The total lead time for the item.User–defined: The value you enter for Planning Time FenceDays.

Demand Time Fence Days

Cumulative mfg. lead time, Cumulative total lead time, Total lead time, User–defined

Determine a point in time inside which the planning process ignores forecast demand and considers only sales order demand when calculating gross requirements.

Used to reduce the risk of carrying excess inventory.Planning also uses the demand time fence when loading master schedules. The demand time fence is calculated as the start date of the master schedule load plus the value entered.Calculate the demand time fence as the plan date (or the next workday if the plan is generated on a non workday) plus:Cumulative mfg. lead time: The cumulative manufacturing lead time for the item.Cumulative total lead time: The total manufacturing lead time for the item.Total lead time: The total lead time for the item.User–defined: The value you enter for Planning Time FenceDays.




Release Time Fence Days 6

Cumulative mfg. lead time, Cumulative total lead time, Total lead time, User–defined, Do not auto–release, Do not release (Kanban)

Determine a point in time inside which planned orders for discretely planned items are automatically released as WIP jobs or purchase requisitions.

No material availability check is performed before WIP jobs are released.Calculate the release time fence as the plan date (or the next workday if the plan is generated on a non workday) plus the value entered here.Cumulative mfg. lead time: The cumulative manufacturing lead time for the item.Cumulative total lead time: The total manufacturing lead time for the item.Total lead time: The total lead time for the item.User–defined: The value you enter for Planning Time FenceDays.Do not auto–release: The item cannot be auto–released.Do not release (Kanban): For Kanban items prevent release of planned orders manually or automatically.

Substitution Window

Cumulative mfg. lead timeCumulative total lead timeTotal lead timeUser-defined

Calculates until what time a substitute can be considered for an item.

Cumulative mfg. lead time: The cumulative manufacturing lead time for the item.Cumulative total lead time: The total manufacturing lead time for the item.Total lead time: The total lead time for the item.User-defined: The value you enter.

Note: 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: 8Assigned resource units: 3Resource usage: 1 hour/unit itemJob 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

Lead times attributes




Attribute Purpose Comment SetupPreprocessing Enter the days you must add to

purchasing or manufacturing lead time to place an order.

Processing Enter the days required to procure or manufacture an item.

For manufactured assemblies, processing days equals manufacturing lead time.

Postprocessing

Enter the days required to receive a purchased item into inventory from the initial supplier receipt.

Cannot enter a value if the Make or Buy attribute is set to Make.

Fixed Enter the days required to make an assembly independent of order quantity, such as setup or teardown time.

Variable Enter the time to produce one additional unit of an assembly.

Total lead time is variable lead time multiplied by order quantity, plus fixed lead time.

Cumulative Manufacturing

Enter the manufacturing lead time of an assembly (in days) plus the largest adjusted cumulative manufacturing lead time of its components.

Purchased items have no cumulative manufacturing lead time.This attribute can be calculated and updated by rolling up cumulative lead times with Oracle Bills of Material.

Cumulative Total

Enter the total lead time of the assembly plus the largest adjusted cumulative total lead time of its components

This attribute can be calculated and updated by rolling up cumulative lead times with Oracle Bills of Material.

Lead Time Lot Size

Enter the quantity used to compute processing lead time (as well as fixed and variable lead times).

The default value is the item’s standard lot size or, if a standard lot size is not defined, the default is 1.

Shipping, Receiving, Carrier, and Supplier Capacity Calendars

Oracle ASCP plans supply chain activities according to various calendars. Manufacturing, supplier, and customer facilities may be able to make, ship or receive


goods only on specific days. Oracle ASCP plans each type of supply or demand considering the working and non working days in the appropriate set of calendars.

It considers the following calendars while planning and scheduling: Organization-Supplier shipping calendar Organization-Customer receiving calendar Carrier calendar Supplier capacity calendar Manufacturing Calendar

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.


Supplier Capacity Calendar

The supplier capacity calendar governs how supplier capacity is accumulated over a period of time. Supplier capacity is only accumulated on the working days according to the supplier capacity calendar. The supplier capacity calendar also governs how the supplier processing lead time is calculated.

Workday Calendar

Please refer to Routing Training Manual for workday calendar setups.

Setup resource and department

Please refer to Routing Training Manual for resource and department setups.

Setup routing

Please refer to Routing Training Manual for routing setups.

Setup supply chain

For more information on supplier base setups, please refer to the Purchasing Training Manual.

Approved Supplier List

Approved supplier list is a controlled repository of information that links items and commodities to suppliers and supplier sites that provide them to a specific ship-to organization or to the entire enterprise.

Navigation path: Purchasing>Supply Base>Approved Supplier List


Refer to the table below for the setup of attributes relevant to planning.

Attribute

Valid values

Comment Setup

Status Approved, Debarred, New

ASCP only consider Approved and not Disabled suppliers

DisabledGlobal? Yes, No ASCP only plans PO for suppliers with

Global = Yes

Supplier planning constraints

Enhance sourcing provides the ability to model flexible supplier capacity.

Navigation path: Purchasing>Supply Base>Approved Supplier List>Attributes (B)> Planning Constraints (T)


Attribute Comment SetupProcessing Lead Time

This supplier-item attribute overrides the organization item attribute for processing lead time

Supplier Capacity Calendar 1

Planning adjusts planned order release date so that deliveries occur on the valid delivery date that coincides with the due date or the closest valid delivery date that occurs prior to the due date. This calendar is independent of your workday calendar.

Order Modifiers

These supplier-item attributes override the organization item attributes for order modifiers.

Capacity This supplier-item attribute represents supplier item daily capacity in the purchasing UOM.

Tolerance Fence 2

Use the Tolerance% and Days Advance Notice attributes together to state by what percentage a supplier can change capacity if given a number of days advance notice.


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 MethodsThis form is used to set up a valid list of values for shipping method field.

Inter-organizations shipping networks

Shipping networks define transportation links form on organization to other organizations. If traffic flows in both directions, from organization A to organization B, and from organization B to organization A, you need to define one entry for each direction. ASCP uses transportation capacity entered on the Shipping Networks form for each inter-organization link as transportation constraint.

Navigation path: Inventory>Setup>Organization>Shipping Networks


Assign shipping methods to shipping network:

Navigation path: Inventory>Setup>Organization>Shipping Networks>Tools (M) >Shipping Methods

Use this window to enter transportation capacity, too.

Inter-location shipping networks

Use the Inter-Location Transit Times form to model shipping networks and capacities between supplier locations and inventory organizations, and between inventory organizations and customer locations. You can also designate a particular shipping method as default method in a shipping network.

Navigation path: Inventory>Setup>Organization>Inter-Location Transit Times


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.

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




Comment Setup

Type Transfer From, Make At, Buy From

Transfer From: Transfer between internal organizations, enter source organization in the Org column. When it is selected, Supplier and Supplier 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% 1

The total allocation percentage for all sources within 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 Active

Checked, unchecked

You cannot apply sourcing rules and bills of distribution (make them Planning Active) until the sum of the allocation percentages equals 100.

All Orgs Checked, unchecked

Checked: This sourcing rule can apply to all organizations.

Org Checked, unchecked

Checked: This sourcing rule can apply to one 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

1. Enter an assignment set name and description.2. Select an Assigned To type See: Assignment Hierarchy3. Enter an organization name, if the Assigned To type requires one. 4. Enter the name of the customer to which you want to assign a sourcing rule or

bill of distribution. 5. Enter the specific site to which you want to assign a sourcing rule or bill of

distribution.


6. Enter an Item/Category if you selected Item or Item-Org as the Assign To type.

7. Enter the sourcing rule or bill of distribution as the Type.8. Enter the name of the sourcing rule or bill of distribution

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 Planning

Forecasts, Master demand schedules, Sourcing rules/Bills if distributions, Assignment sets, Delivery schedules

Note: If Oracle Demand Planning is installed and integrated with ASCP, its output is directly visible to ASCP as planning inputs.

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.

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

2. Select individual parameter as explained in the table below, then click on OK

Parameter ValuesInstance Source instance code from list of values.Collection Group You can decide to collect data from All enabled organizations or

only form the current organizationNumber 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 Data

Yes (default) or No. Setting this to Yes wipes out all data in the APS planning server operational data store associated with the selected source instance as the first step in the collections process. If you set this to Yes, the only allowable collection method is Complete Refresh. If you set this to No, the allowable collection methods are Targeted Refresh and Net Change.


Parameter ValuesCollection 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

4. Select individual parameter as explained in the table below, then click on OK

Parameter ValuesInstance 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 Availability

This defaults to the value (Yes or No) that you set for the Resources Availability business entity in the Planning Data Pull Parameters window. The value that you set here is the one that actually determines whether resources availability is collected or not.


Parameter ValuesRecalculate 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

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 Horizon

Goals Scenario

Unconstrained

Long Term Future

How much resource capacity and material availability do I need to arrange in order to satisfy all anticipated demand in a timely manner?

Decisions can be made on Resource acquisition/disposition and supplier sourcing to address the exceptions.

Resource Constrained

Long Term Future

How much material availability do I need to arrange in order to satisfy all anticipated demand in a timely manner?

Difficult to change resource capacity, but increased outsourcing is an option. Decisions can be made on supplier sourcing to address the exceptions.

Material Constrained

Long Term Future

How much resource capacity do I need to arrange in order to satisfy all anticipated demand in a timely manner?

Difficult to change material availability but internal resource acquisition/disposition is an option. Decisions can be made on Resource acquisition/disposition to address the exceptions.


Plan Class Planning Horizon

Goals Scenario

Material and Resource Constrained

Near Term Future

Generate a feasible plan that respects material, resource, distribution, and transportation constraints.

Impossible to overcome material and resource constraints and therefore must respect them in order to generate a feasible supply chain plan.

Optimized Near Term Future

Generate an optimized and executable plan based on plan objectives and material, resource, and transportation constraints.

Impossible to overcome material and resource constraints and therefore must respect them in order to generate a feasible supply chain plan.

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.

ASCP plan types

There three types of ASCP plans.

Production Plan, equivalent to traditional MPS (master production plan)

Manufacturing Plan, equivalent to traditional MRP (Materila requirement plan)

Master Plan – MPP (Master Production scheduler)

Each creates time-phased planned orders that satisfy independent and dependent demand while seeking to respect material and resource constraints. These three types of plans need to be used in conjunction with the MPS/MRP Planning Type item attribute that is set for each item. Possible values for this attribute are:

MRP Planning

MPS Planning

MRP/MPP Planned

MPS/MPP Planned

MPP Planned

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

1. Enter a unique plan name.

2. Enter Description for the plan.

3. Check ATP if this plan is used for global order promising.

4. Check Production if it is a production plan. In a production plan, planned orders can be automatically released within their release time fence.

5. Check Notifications. If this is checked, exception message notifications workflow for the plan is enabled.

6. Select a Plan Type. Valid values are Manufacturing Plan, Production Plan, and Master Plan. This setting interacts with the MPS/MRP Planning method item attribute to determine which subset of the items that pass the condition imposed by the Planned Items parameter are planned.

7. If you want to make this plan not visible as input into other plans, or want to purge the plan enter an Inactive Date.Set plan optionsNavigation path: Advanced Supply Chain Planner>Supply Chain Plan>Names >Plan Options (B)Main tab


Use the information in the following table to specify parameters on the Main tab.

Parameter Description Comment SetupAssignment Set

The assignment set that holds the sourcing rules and bills of distribution that define the rules for material flow within your supply chain.

Demand Priority Rule

When ASCP does detailed scheduling, it schedules demands one by one. The rule specified here dictates the order in which demands will be considered during detailed scheduling, and thus which demands will get the first opportunities to take up available materials and resource capacities.

Overwrite1 Overwrite planned orders.Append Planned Orders1

Appends new planned orders to current plan.

Planned Items2

This parameter and the next one, Planning Method, control the items that are planned in the supply chain plan. An item must satisfy conditions imposed by both parameters before being included in the supply chain plan.

Material Scheduling Method

Choose from Operation Start Date or Order Start Date scheduling methods. If you choose Operation Start Date, material is scheduled to arrive at the start of the operation for which it is required. If you choose Order Start Date, material is scheduled to arrive at the start of the order for which it is required.

Order State Date is usually an earlier date than the Operation Start Date and therefore this selection represents the more conservative planning logic of the two options.


Parameter Description Comment SetupEnd Item Substitution Set

If Decision Rules tabbed region > Use End Item Substitutions selected, select a substitution set. These are defined in the Planning Details - Substitute window discussed. You can use a set of substitution relationships to be effective for a given plan by selecting the substitution set as an option for the plan. This allows you to run simulations of possible substitutions and evaluate performance indicators given possible future substitutions.

Schedule By Set this option to instruct the planning engine to:Plan supplies based on sales order line request, promise, or schedule dates for either ship or arrivalConsume forecasts based on sales order line request, promise, or schedule dates. You must provide forecast dates that match your choice of this plan option; for example, if you select Promise Ship date for this plan option, make sure your forecast dates are in terms of promise ship dates.If you do not specify plan option Demand Priority Rule and have not specified a default demand priority rule (in the Define Priority Ruled form), the planning engine uses the value of this plan option as the demand priority rule.

Select one of the following sales order line dates:Schedule Ship DateSchedule Arrival DateRequest Ship DateRequest Arrival DatePromise Ship DatePromise Arrival DateThe default is Schedule Ship Date.

Demand Class

If you want to limit a production plan to a demand class, enter it.

This field is active only for a Production Plan/MPS schedule.

Move Jobs to PIP

Check this option if you want to generate 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 PerformanceIndicators

Check this option to calculate key performance indicators for the plan.

Demand Time Fence Control

Check this option to enforce demand time fence control.

Demand time fence is an item attribute

Planning Time Fence Control

Check this option to enforce planning time fence control.

Planning time fence is an item attribute

Lot for Lot Check this option to force the creation of a separate supply for each demand. This prevents the creation of aggregate supplies that satisfy multiple demands.

Order quantity modifiers such as Minimum Lot Size and Fixed Lot Multiple override this option


Parameter Description Comment SetupInclude CriticalComponents

Select this plan option to instruct the planning engine to plan considering critical components. Depending on the plan type and the planning item types, the planning engine may plan critical components and not plan other components or components of those components.

To mark an item as a critical component, select its item attribute Critical Component.

Do Not Spread Forecast

The planning engine should use forecast entries as they exist for planning.

Spread Forecast Evenly

The planning engine should spread aggregate forecast demand evenly across the daily buckets from the workday calendar.

Forecast DistributionAssignment Set

Select a forecast distribution assignment set for the global forecasting process. The forecast distribution assignment set contains global sourcing rules used to distribute global forecasts over multiple inventory organizations:

The rules to distribute sales orders are in plan option Assignment Set.

Consume by ForecastBucket

The forecast consumption process does not search outside of the consumption bucket for forecasts and sales orders except in daily buckets.

Explode Forecast

Select this plan option to instruct the planning engine to explode forecasts as follows during the consumption process:- Product family forecasts to product family member item forecasts- Model forecasts to other model, option class, and item forecasts.This option applies to forecasts with forecast control Consume and derive.

Clear this plan option if you have arranged for this explosion to occur in the source instance or in Oracle Demand Planning before the planning run.

Backward Days

If you are bringing in unconsumed forecast scenarios from Oracle Demand Planning as demand schedules into Oracle ASCP and would like to do forecast consumption inside ASCP (as opposed to bringing in 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.


Parameter Description Comment SetupEnable Pegging

Check this option to calculate pegging information. Oracle ASCP traces supply information for an item to its corresponding end demand details, which you can then view in a graphical display.

Peg Supplies by Demand Priority

Check this option to calculate pegging so that on-hand and firm supplies are pegged to demands in demand priority order (as defined by you in a priority rule) within the time period set by the profile option MSO: Firm Supply Allocation Window (days).

Do not check it. Instead, set profile option MSC: Use FIFO Pegging to Yes.

Pegging – Reservation Level

Choose a reservation level: Planning Group, Project, Project-Task, or None.

Do not use

Pegging – Hard Pegging Level

Choose a hard pegging level: Project, Project-Task, or None.

Do not use

Forecast Consumption Backward Days

If you are bringing in unconsumed forecast scenarios from Oracle Demand Planning as demand schedules into Oracle ASCP and would like to do forecast consumption inside ASCP (as opposed to bringing in 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 Consumption 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.

Do not use

Note: 1. Overwrite and Append Planned Orders work together to limit how the planning process reacts to firm planned orders and to stabilize the short-term material plan. When you launch the planning process, you generate new planned orders to meet your net requirements. Since you can firm DRP, MPS, or MRP planned orders, you may not want the planning process to overwrite any firm planned orders. See the table below for more information.

Overwrite Append Planned Orders

Effects

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 Orders

Effects

Outside planning time fence

The planning process overwrites all entries from the current plan, planned and firm planned, outside the planning time fence, and overwrites only planned orders inside the planning time fence. It does not overwrite any firm planned orders within the planning time fence. The planning time fence can be different for each item, so the planning process looks at the planning time fence for each item when choosing what to delete. Planning time fence is an item attribute defined in Inventory

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 planning time fence

Checked This option allows you to create an extension to the current material requirements plan, delete planned and firm planned orders outside the planning time fence and delete all planned entries inside the planning time fence for each item. The planning process creates (appends) new planned orders after the planning time fence date. In this case, since you are overwriting after the planning time fence, you are also appending new planned orders after that date. Use this combination to stabilize the 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.

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 value

Plan type Planned Items in the plan

All planned items Master Plan All items in the planned organizations having MRP/MPS Planning Method attribute value of MPP planningMRP and MPP planningMPS and MPP planningPlus: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 planningMPS and MPP planningPlus: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 items only

Master Plan All items in the input demand schedules, and all components of these items that have MRP/MPS Planning Method attribute code of:MPP planningMRP and MPP planningMPS and MPP planningPlus:MPS and MRP planned items that are in between the above items in the bills of material


Production Plan All items in the input demand schedules, and all components of these items that have MRP/MPS Planning Method attribute code of:MPS planningMPS and MPP planning


Manufacturing Plan

All items in the input demand schedules, and all components of these items that have MRP/MPS Planning Method attribute code of:MRP planningMRP and MPP planning

Supply schedule items only

Master Plan All items in the input supply schedules, and all components of these items that have MRP/MPS Planning Method attribute code of:MPP planningMRP and MPP planningMPS and MPP planningPlus:MPS and MRP planned items that are in between the above items in the bills of material


Production Plan All items in the input supply schedules, and all components of these items that have MRP/MPS Planning Method attribute code of:MRP planningMRP and MPP planning


Planned Items value

Plan type Planned Items in the plan


Manufacturing Plan

All items in the input supply schedules, and all components of these items that have MRP/MPS Planning Method attribute code of:MPS planningMPS and MPP planning

Demand and Supply schedule items

Master Plan All items in the input demand and supply schedules, and all components of these items that have MRP/MPS Planning Method attribute code of:MPP planningMRP and MPP planningMPS and MPP planningPlus:MPS and MRP planned items that are in between the above items in the bills of material


Production Plan All items in the input demand and supply schedules, and all components of these items that have MRP/MPS Planning Method attribute code of:MPS planningMPS and MPP planningPlus:MPS and MRP planned items that are in between the above items in the bills of material


Manufacturing Plan

All items in the input demand and supply schedules, and all components of these items that have MRP/MPS Planning Method attribute code of:MRP planningMRP and MPP planning

Aggregation tab

Use the information in the following table to specify parameters on the Aggregation tab.Parameter Description SetupStart Date This is a view-only field, whose value equals the start date of the

plan if the plan has already been run. Otherwise, it defaults to the system date.

End Date Shows the calculated end date for your plan. This is a view-only field, calculated based on the bucket sizes you specify

Bucket Size Specify bucket size in days, weeks, and periods.Items Choose aggregation at item level or product family level.Resources Choose resource aggregation at individual level or aggregate

level.Routings Choose aggregation level at individual routing or bill of resources

level.


Parameter Description SetupMinutes Bucket

Size Specify the bucket size in minutes for the Days planning period.

Hours Bucket Size

Specify the bucket size in hours for the Days planning period.

Days Bucket Size

Specify the bucket size in days for the Days planning period.

Organization tab

Use the information in the following table to set parameters on the Organizations tab.Parameter Description Note SetupGlobal DemandSchedules

Select the names of Oracle Demand Planning scenarios that drive this plan. You can select demand-planning scenarios that do not reference an organization (organization dimension set to All Organization).

Ship To Consumption Level

Select a forecast consumption level for the Oracle Demand Planning scenario. The global forecasting process consumes forecast entries that have Ship To value the same as this plan option.

You can select:- Customer- Customer Site- Zone- Customer Zone- Demand Class- ItemThe 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 SetupNet Reservations

If checked, ASCP generates pegging 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 Stock

Select to consider plan safety stock demand and supply in the planning demand/supply netting process.

Include Sales Order1

Select to invoke forecast consumption within ASCP for the selected organization. Check this if the demand schedules for the organization are unconsumed forecasts. Uncheck this if the demand schedules for the organization are consumed forecasts plus sales orders in the form of master demand schedules

Bill of Resource

Select Bill of Resources from the list 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 Schedules2

Select the name of your demand schedule/forecast/plan.

Ship To Consumption Level

See above See above

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.


Parameter Description Note SetupSupply Schedules

Select the name of your supply schedule for each organization.

Subinventory Netting

Opens the Subinventory 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.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 SetupConstrained Plan

If selected, Enforce Demand Due Dates is selected, all fields in the tabbed region are updateable with all constraints defaulted to Yes. The default is cleared. You cannot set all Resource Constraints and Material Constraints to No. If you set any Resource Constraints to Yes, you cannot clear Calculate Resource Requirements.

Enforce Demand Due Dates

Check this option if you want demand due dates to be your hard constraint (that is, respected in lieu of material and resource capacity constraints, if there is conflict).

Enforce CapacityConstraints

Check this option if you want material and resource capacity constraints to be respected in lieu of demand due date constraints.

Start Date Displays the start date for each bucket type.Buckets Displays the number of buckets of this bucket type.Resource Constraints

Select Yes to consider resource constraints for the bucket.


Parameter Description SetupSupplier CapacityConstraints

Select Yes to consider supplier capacity constraints.

Enforce PurchasingLead-time Constraints

Select this plan option to instruct the planning engine to constrain the plan by purchased item lead times (item attributes or approved supplier list).Clear it to instruct the planning engine never to miss a demand due date because of a purchased item lead time.

Scheduling Specify whether to enable detailed scheduling.Minutes Bucket Size (inDays)

Size Specify the bucket size in minutes for the Days planning period.

Hours Bucket Size (inDays)

Specify the bucket size in hours for the Days planning period.

Days Bucket Size (inDays)

Specify the bucket size in days for the Days planning period.

Calculate ResourceRequirements

If selected, the program will calculate resource capacity utilization.

Planned Resources

Select All Resources or Bottleneck Resources. If you have defined bottleneck resource groups in Oracle Bills of Material and you want to detail schedule only the bottleneck resources, selectBottleneck Resources and enter a Bottleneck Resource Group.

Bottleneck ResourceGroup

If you have defined bottleneck resource groups in Oracle Bills of Material and you want to detail schedule only the bottleneck resources, select its name.

Decision Rules tab

Use the information in the following table to specify parameters on the Decision Rules tab.

Parameter Description SetupUse End ItemSubstitution

If selected, use end item substitute prior to creating new planned orders. If cleared, use only the demanded item. Enter the End Item Substitution Set in the Main tabbed region.


Parameter Description SetupUse AlternateResources

If selected, use primary resource and use alternate resource only if necessary. If cleared, use only primary resources.

Use SubstituteComponents

If selected, use primary components and use substitute components only if necessary. If cleared, use only primary components only.

Use AlternateBOM/Routing

If selected, use primary routings and use alternates only if necessary. If cleared, use only primary bills of material and routings.

Use Alternate Sources

If selected, use primary sources and use alternate sources only if necessary. If cleared, use primary sources only. The planning engine does not use alternate sources (rank 2 or higher) as a sources of supply.

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)


1. Enter a Name for the new plan2. Enter Description, optionally3. Select or clear ATP, Production, and Notification as you would if you are

creating a new plan on the Plan Names form.4. If you want to copy only the plan options from one plan to another of a

different plan type, select Copy Plan Options Only5. Plan Type defaults to the plan type of the source plan and you cannot change it

if you want to copy all plan information.6. Click on OK

Planner WorkbenchThe Planner Workbench is the primary “work area” for analysis of the plan and actions taken based on plan recommendations

Multi-window format Ability to have several screen open at the same time Strong navigational interactions between different workbench windows Context passed between windows using right clicks or buttons Ability to see data at detailed and summary levels and drill down/up from one

to the other

Navigation path: Advanced Supply Chain Planner>Supply Chain Plan>Workbench


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 byo Actionso Organizationso Itemo Resourceso Projectso 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 structureSupply Chain Structure – Items and Item DetailsRight 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 itemSupply Chain Billo Displays Sourcing and BOM structure for the itemo 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 rankso Supplier Information: Lead Times, Costs, time varying capacities and

flex fences Destinations

o Displays Destinations (other orgs) to which this item is shipped toWhere 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 resourceRequirements – Shows Forms based view of activities planned on the resource

Gantt Chart:

Availability:

Avail


ability > Details:

Requirements:

Supply chain plan result analysisOpen Planner workbench

Review KPIs Review Exceptions From the context of an exception analyze planning results Make changes to the plan Re-run the plan with the user changes Review results Select orders for release to execution system Release orders Create simulation plans to simulate what-if scenariosSupply Chain Planning

Results – Exceptions SummaryRight Click Exceptions > Summary (sensitive to the level in the tree at which right click is performed)

Displays Exceptions as various types classified into groups Shows the count of exceptions by group, type Can Save a version of the Exception messages prior to running a simulation

re-plan Can have all exception groups pre-expanded (Tools > Preferences > Other)


Supply Chain Planning Results – Exceptions Details

Double Click on any exception type to open up Exception DetailsShow details of the planning exception

Example: Late Replenishment for Forecast. Key informationo Itemo Orgo Order Numbero Customero Demand Due Dateo Days Late

Folder/Find and Sort capability Navigation to related entities: Items and Supply/Demand Navigation to cause analysis

o Related Exceptionso Gantt Chart

Action Taken: Mark the exception once action is taken


Supply Chain Planning Results – Related Exceptions

Right Click From Exception Details > Related Exceptions Certain Classes of Planning Exceptions have “Related Exceptions” (when the

Related Exceptions pop up menu enabled)o Late Replenishment for Sales Orders/Forecastso Sales Order / Forecast at Risko Sales Order / Forecast at Risk due to Resource/Material Shortage

Related exceptions point to root causes Show the cause – effect across multiple levels in the supply chain structure Root causes could be

o Resource capacity shortageso Material capacity shortages Lead Times

Supply Chain Planning Results – Horizontal PlanThere are 4 types of Horizontal PlansMaterial Plan: Classical Planner spreadsheet showing supplies and demands and projected available balances at the planning bucket level

1. Resource Capacity: View of Resource hours available versus used along with capacity utilization % information

2. Supplier Capacity: Shows Supplier capacity (available versus used) by planning time bucket and tracks the cumulative available at any point in time


3. 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

Users can control via preference setso The rows that are displayed / not displayedo The default view of the time buckets (days, weeks, periods)o Display factor and Decimal placeso Display of graph

When invoking the horizontal plan user can choose the preference set that will control the display (e.g. default, summary, detailed)

Right Click on Save Settings will control Column and row widths Time scale display

o Can expand from Periods / Weeks / Dayso Can only expand up to the planning bucket granularityExport

Capability Select and copy the contents of the horizontal plan into an Excel sheetSupply Chain Planning Results – Horizontal Plan (Material)Shows time phased view of supply, demand and inventory for an item/org (multi-select also possible)

Drill downs from demand and supply rows to Supply/Demand Window (discussed later)

Can optionally display a grapho Graph up to maximum of 3 rows at a timeo Select number of buckets / chart type

Right Click on Enterprise Plan, Shows the supplies and demands summarized across time

Supply Chain Planning Results – Horizontal Plan (Resource)Shows time phased view of Required hours, available hours and capacity utilization % for selected resource(s)


Drill downs to Resource Requirement details from a given planning time bucket (discussed later)

o Can optionally display a grapho Graph up to maximum of 3 rows at a timeo Select number of buckets / chart type

Supply Chain Planning Results – Horizontal Plan (Supplier Capacity)

Shows time phased view of Available Capacity, Required capacity, net available (in that bucket) and cumulative available (running total across buckets) for Supplier/Supplier Site/Item combination

Unlike Resource capacity, supplier capacity accumulates over time Drill downs to Supply/Demand window for the purchased item Can optionally display a graph

o Graph up to maximum of 3 rows at a time


o Select number of buckets / chart type

Supply Chain Planning Results – Vertical PlanShows vertical listing of Supplies and Demands for an Item/Org

Not often used. Most people use Horizontal Plan or Supply/Demand Window

Supply Chain Planning Results – Supply/Demand Window

Displays Supplies and Demands generated by the plan Can be in the context of an entire plan, an org, an item across orgs or for an

item org Key information

o Planned Dateso Sources (organizations and suppliers)


o Quantitieso Customer informationo BOM/Routing informationo Ship Methods usedo Order Type and Numbero Action status: Indicates what the planner should do with this ordero Hundreds of other pieces of information that planners can use for

analysis of plan results Folder / Find capabilities for storing favorites

Supply Chain Planning Results – Supply/Demand Window - CalendarRight click on any Supply or Demand > Calendar

Sub menu lists out the various calendars that have influenced the timing of this order

The grayed out options are not applicable to this order type The Calendar window show the working non working days as well as shift

timings if applicable for that calendar It also shows the inheritance level for the calendar


Supply Chain Planning Results – Supply/Demand Window - Pegging

Pegging establishes relationships between supplies and demands across multiple levels in the supply chain

Pegging can be from a Supply or a Demand and could be up or down the supply chain

Used extensively by ASCP customers to evaluate impacts of supply shortages at lower levels in the supply chain bill on end customer demand

Optionso Navigate backwards and forwardso Refresh the supply/demand window when parked on a specific node in

the pegging treeo Peg up or downo Hide Dependent demandso Hide Operations and Resources

Right Click on Properties provides information additional to what is shown in the pegging tree


Supply Chain Planning Results – Gantt Chart

Navigate from any supply, demand, resource, and resource requirement Only active in constrained plans Graphical views of

o Supplies, operations and resource requirements shown in the context of a pegging tree (Orders View)

o Late demands and the reasons why they are late (Late Demand View), only available for late demands.

o Resources and activities planned on them (Resource View) Late Demand View

o One late demand at a timeo Analyze critical patho Analyze key bottlenecko Analyze minimum lead times and earliest/latest dates

Navigate to Orders view or Resource view to make changes and firm orders

Late Demand View:


Order View:

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 Dateo New Quantity

Optionally entero New sourcing informationo 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 plano 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)

Refer to Simulation and net change re-plan of this text.

Note: User changes are shown in pink color Supplies that are changed after batch/online replan are shown in blue

colorSupply Chain Planning Actions – Releasing OrdersReleasing orders means having planned orders in ASCP get converted into Work Orders, Purchase Orders, Internal Requisitions etc. in the ERP system

Supply/Demand window is used for releasing orders Typical use case

o Use Find window to specify criteria for releasing orderso Once results are shown in the window do Plan (Top Menu) > Select

All for Releaseo Do Plan > Release


Selective releaseo Select a specific order for release using the “Release” checkboxo Select the “Release Properties” tabo Fill in details for the “Implement As *” columns as appropriate (there

are several Implement columns that are hidden)o Hit the Save button (or Ctrl + S)o Right click “Release” or Plan > Release

A summary window will provide information on which orders were released successfully and which orders were not

Personal and public queries

Provides a window to the plan that does not involve drill down through the plan name

Accessed using the Queries tab on the planner workbench Query is a stored set of business criteria that are used to generate results that

serve as starting point for plan analysis Queries can be Public (available to all users) or Private (only available to the

user who has defined the query) Queries are available for

o Itemso Resourceso Supplierso Exceptions

Define Query Name > Specify Criteria > Execute Query > View Results > Navigate to the Planner workbench for more analysis


Click Save to save the query Click Save As to save it under another name Click Delete to delete it Click Execute to run the query

Simulation net change re-planNet change re-plan simulation is ASCP’s What-If analysis feature that lets you update a plan by planning only the items you have changed in the Planner Workbench. Re-planning is based on the snapshot data gathered during the original planning run and the changes you have made through the Planner Workbench.

Simulate changes

What changes can you simulate?

Supplier capacity: To simulate item supply changes, you can add new supplier capacity and adjust a supplier’s capacity over a specified time frame.

Resource availability: You can add new resource availability and modify how many resources are available over user defined time frame. Resource constraints include available machine hours, available worker hours, and adding or removing shifts.

Supplies: Add new planned orders. Firm planned orders, discrete jobs, and purchase orders. Modify quantities, dates, sources, and alternates

Demands: Alter demand priority of any demand. Modify quantities and due dates for independent demand (MDS entries). Add new Manual MDS.

Change supplier capacity

1. Query the item for which you want to change supplier capacity2. Click on the Sources button


3. Click on Supplier Capacity button

Change resource availability

1. Find the resource2. Click on Availability button3. Click on Details button4. Under update resource, make capacity changes5. Click Apply

Change supply

1. Open the Supply/Demand window2. Click on the New button on the toolbar3. Enter Org code4. Enter Item code5. Select Planned Order as Order Type6. Enter New Date as the supply due date7. Enter New Qty as the supply quantity8. 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.

Change demand

1. Open the Supply/Demand window2. Click on the New button on the toolbar3. Enter Org code4. Enter Item code5. Select Manual MDS as Order Type6. Enter New Date as the supply due date7. Enter New Qty as the supply quantity8. 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.

4A. Run Batch Replan Make desired changes to the plan Save changes Submit batch replan concurrent program, choose Plan > Batch Replan

Verify the concurrent program completes successfully Re-query the plan to review the changes If the results are not satisfactory, repeat the above steps


4B. Running Online Replan Start Online Planner

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

When the replanning completes, review the plan results Repeat these steps as needed Stop online planner session, Choose Plan > Stop Online Planner. Click OK to

confirm your choice.


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.

Select Plan > Undo Summary

The Undo Summary window appears


Create Undo Bookmark

You can create save points (Undo Bookmark) for undoing online planner actions. Subsequently, you can undo only those online planner actions made after the bookmark.

Select Plan > Add Undo Bookmark

Or click Add Bookmark on the Undo Summary window.

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.


You cannot undo other users’ changes.

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.

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

Practicing labsTo 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

Week start dates. Note that the week of May 1 starts on May 4. Why?

Non-workdays are dimmed

4. What lead-times can you define in Oracle Applications?

The following lead times are organization-item attributes: Preprocessing: The time required to place a purchase order or create a

discrete job or schedule. This is usually the paperwork or planning time you spend on processing an order.

Fixed: The time required to complete the tasks to make an assembly that are independent of order quantity, for example, setup, fixed run


Period start date. Note June 2006 is a five-week period.

time, staging, or teardown times. Oracle Bills of Material concurrent processes calculate fixed lead time based on scheduled lot-based resource usages.

Variable: The time required to complete the tasks to make an assembly that is proportional to the order quantity, for example, operation time. Oracle Bills of Material concurrent processes calculate this variable lead time based on scheduled item-based resource usages.

Processing: The time required for a supplier or your transfer from facility to deliver an item to your receiving dock or for you to manufacture an item. For make items, this is also known as manufacturing lead-time. For buy and transfer items, it includes in-transit time to your facility.

Postprocessing: The time required to receive a buy or transfer item from the receiving dock to inventory.

Cumulative Manufacturing: For make items, the time required to make the item if you have all of the buy items in stock and have to make all subassemblies if any and the item itself.

Cumulative Total: For make items, the time required to make the item if you have to purchase all of the buy items, make all subassemblies, and make the item itself.

Lead Time Lot Size: The typical quantity of order size of the item that you buy, make or transfer. The default value is item attribute Standard Lot Size (set by Oracle Cost Management). Oracle Bills of Material concurrent process Calculate Manufacturing Lead Time uses this value to compute variable lead time.

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:

Type of lead time Used? CommentOrg-item lead times Yes ASCP uses preprocessing, processing,

post processing lead time for buy items.It uses variable and fixed lead times for make item planning.

Subinventory-item lead times

No ASCP plans at organization level. Thus, subinventory-item attributes are ignored.

Kanban pull sequence lead time

No ASCP does not plan Kanban. Thus, Kanban attributes are ignored.

Item-supplier-supplier site lead time

Yes ASCP uses it to calculate supplier specific lead time for buy items

Inter-location transit time

Depends ASCP uses transit time between your organization and customer site to calculate outbound shipping (sales order) scheduled ship date and scheduled arrival date. It does not use transit time between your organization and supplier site to calculate inbound shipping (purchase order) scheduled ship date, for the supplier shipping date is not under your control unless you are using Oracle Supplier Scheduling. In Oracle Supplier Scheduling, transit time is used to calculate the scheduled ship date.

Shipping network intransit time

Yes ASCP uses it for transfer orders between your organizations.

Note: currently, Region level sourcing rules and transit lead times are respected by Global Order Promising (GATP) only for sale order scheduling, but not by Advanced Supply Chain Planning and Inventory.

6. How are lead times used by ASCP in planned order date calculation?

For purchased supply:

The starting point is need by date.


Need by Date: Date that the material is required to satisfy demand.Suggested Due Date:

Unconstrained plans: Need by Date Constrained plans: The available date of the supply by forward

schedulingSuggested Dock Date:

Unconstrained plans: Due Date - Postprocessing Constrained plans: The latest delivery day for which the capacity is

available and the material is needed If the purchased supply item has an Approved Supplier List delivery

calendar: The planning engine verifies that the Suggested Dock Date is a work day on the delivery calendar. If it is not, the planning engine changes Suggested Due Date to the next earliest working day of the delivery calendar.

Suggested Ship Date: Dock Date - Production durationProduction Duration:

If the purchased supply item has an Approved Supplier List Supplier Processing lead-time: Approved Supplier List Supplier Processing lead-time

If the purchased supply item does not have an Approved Supplier List Supplier Processing lead-time: Item attribute Processing lead time

Suggested Start Date: Ship DateSuggested Order Date: Start Date - Preprocessing.

Note: the transit time defined at inter-location transit time is not used by ASCP for purchased item.

For transferred supply:

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 - PostprocessingSuggested 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.

For Manufactured Supplies

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: BlankSuggested Start Date: Suggested Due Date - Production duration. This is the day that you should begin shop floor operations. Production Duration:

Unconstrained plans: Fixed + (Variable * Order quantity) Constrained plans: Calculated resource and material duration. If the

item does not have a routing, the planning engine uses the unconstrained calculation.

Suggested Order Date: Planned order Start Date - Preprocessing. It is the date on which you should place the order.

7. How does ASCP calculate supply dates?


ASCP schedules planned orders and scheduled receipts based on Demand Due Date of the demand that the supply is pegged to. If a supply is pegged to multiple demands, it uses the earliest Demand Due Date. It calculates the other dates as follows:Need By Date: It is the earliest demand due date of all demands pegged to a supply.Suggested Due Date: The date by which the supply is available for use by its demand.

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.

Suggested Dock Date: For buy or transfer orders, it is the date when the order is expected to arrive on your receiving dock.Suggested Ship Date: For transfer orders, the date of departure from the source organization of the last transport used for the transfer. Suggested Start Date: The date that you, your supplier, or your transfer from organization should begin work on the order.Suggested Order Date: The date on which you need to place the order. For a scheduled receipt, this field displays the date the date that the order was created.

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.

Appendix Constraint based planningConstraint-based planning and scheduling takes into account constraints at the enterprise and plant levels. Material and capacity constraints are considered


simultaneously. Capacity constraints include factory, distribution, and transportation resources and their respective availabilities. You can specify different constraints and different levels of granularity in the different periods of the planning horizon.

Constraint types

You can generate plans using the following scenarios for each planning bucket type (days, weeks, and periods):

Material constraints only

Resource constraints only

Material and resource constraints

Oracle ASCP lets you prioritize how you enforce Capacity Constraints or Demand Due Dates. Whichever constraint takes precedence over the other is the hard constraint; the other is the soft constraint. You must choose one and only one type of constraint.

Enforce Demand Due Dates (on the Options tab) is checked, Plan Capacity (on the Aggregation tab) is unchecked. This is an unconstrained plan. This type of plan is the traditional MRP plan with multiple organization planning functionality.

Enforce Demand Due Dates (on the Options tab) is checked; Plan Capacity (on the Aggregation tab) is checked. Due dates are hard constraints and capacity is soft constraint. Primary resources are used and loaded to capacity to satisfy demand due dates. The system also evaluates alternate resources if additional capacity is required. If there is insufficient capacity to meet demand due dates, the primary resource is overloaded. The choice of whether to use an alternate resource or overload capacity depends on cost considerations if optimization is selected. Oracle ASCP returns exception messages if capacity is overloaded.

Enforce Capacity Constraints (on the Options tab) is checked. In this type of plans, capacity is hard constraint and due dates become soft constraints. Resources are loaded to their limit to satisfy demand (if required). Unsatisfied demand is pushed into the future. In this case, Oracle ASCP returns late replenishment exception messages.

The information needed to run a constraint-based plan is listed below:

Items: BOM effectivities (process effectivity), ECOs, by-products, safety stocks, order modifiers, supplier-specific order modifiers, supplier-specific lead times, pegging restrictions

Manufacturing Resources: routing effectivities, alternate resources, resource capacities, line rates, workday calendar

Transportation Resources: carrier capacities, shipment and delivery calendars

Sourcing Constraints: sourcing effectivities, sourcing ranks, allocation percentages, supplier capacity

Suppliers: supplier capacity, supplier rank, supplier calendar, flex fences, supplier order modifier


Demands: sales orders/forecasts, demand priority, demand priority rules

These data should have been set up correctly in the transaction instances.

Set constraints for different plan types

The following table describes how to set constraints for various plan types:

Plan Type Options tab setting Aggregation tab settingUnconstrained Check Enforce

Demand Due DatesUncheck Plan Capacity.

UnconstrainedBut calculate resource requirements

Check Enforce Demand Due Dates

Check Plan Capacity. All Resource Constraints fields are set to No. All Material Constraints fields are set to No.

Hard constraint: Demand Due Dates.Soft constraint: Capacity – Material Constrained


Check Plan Capacity. All Resource Constraints fields are set to No. At least one Material Constraints field is set to Yes.

Hard constraint: Demand Due Dates. Soft constraint: Capacity – Resource Constrained


Check Plan Capacity. All Material Constraints fields are set to No.At least one Resource Constraints field is set to Yes.

Hard constraint: Demand Due Dates. Soft constraint: Capacity – Resource and Material Constrained


Check Plan Capacity. At least one Resource Constraints field is set to Yes.At least one Material Constraints field is set to Yes.

Hard constraint: Capacity – Material Constrained.Soft constraint: Demand Due Dates.

Check Enforce Capacity Constraints

Check Plan Capacity. All Resource Constraints fields are set to No. At least one Material Constraints field is set to Yes.

Hard constraint: Capacity – Resource Constrained.Soft constraint: Demand Due Dates


Check Plan Capacity. At least one Resource Constraints field is set to Yes. All Material Constraints fields are set to No.

Hard constraint: Capacity – Material and Resource Constrained.Soft constraint: Demand Due Dates


Check Plan Capacity. At least one Resource Constraints field is set to Yes. At least one Material Constraints field is set to Yes.

Rules used in constrained plans

When running a constrained but not optimized plan, the following rules are used:

Demand Priorities are respected

Alternate bills of material will not be considered

Alternate routings will not be considered

Substitute items will not be considered


Alternate resources in the primary routings will be considered

Note: When Demand Priorities are not specified, the default priorities of the various demand types are (in order): sales order, forecast, and safety stock.


ASCP Training Manual v1.2

Documents

Transcript of ASCP Training Manual v1.2