5031-ASCP Training Manual v1.2

8/17/2019 5031-ASCP Training Manual v1.2

1/87

Created by Ranvijay

ASCP Training Manual

Author: Ranvijay

Oracle Apps Functional

Accenture


2/87

Page 2

Table of Contents

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

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

Source Data Setups ......................................................................................... 6 Setup inventory item attributes .................................................................................. 6 MPS/MRP planning attributes ................................................................................. 10 Lead times attributes ................................................................................................ 16 Shipping, Receiving, Carrier, and Supplier Capacity Calendars ............................. 17 Workday Calendar ................................................................................................... 18 Setup resource and department ................................................................................ 18 Setup routing ............................................................................................................ 18

Setup supply chain ................................................................................................... 19 Order management ................................................................................................... 27

Data Collection ............................................................................................. 27 Scope of data collection ........................................................................................... 27 Data collection methods ........................................................................................... 27 Run data collection .................................................................................................. 29

Define an ASCP plan .................................................................................... 32 ASCP plan classes.................................................................................................... 32 ASCP plan types ...................................................................................................... 33 Define a plan name .................................................................................................. 34 Set plan options ........................................................................................................ 34 Launch a plan ........................................................................................................... 46 Copy a plan .............................................................................................................. 46

Planner Workbench ....................................................................................... 47 Plan Navigator ......................................................................................................... 48 Supply chain structure.............................................................................................. 49 Supply chain plan result analysis ............................................................................. 55 Supply chain plan executions................................................................................... 64 Personal and public queries ..................................................................................... 66

Simulation net change re-plan ...................................................................... 67 Simulate changes ..................................................................................................... 67

Simulation modes..................................................................................................... 70 Running net change replan simulations ............................................................ 70


3/87

Page 3

Reports .......................................................................................................... 75 Plan comparison report ............................................................................................ 75 Plan detail report ...................................................................................................... 75 Audit information reports ........................................................................................ 75

Practicing labs ............................................................................................... 76 FAQ ............................................................................................................... 76

1. What calendar quarterly type does ASCP support? ............................................. 76 2. How are planning buckets and horizon calculated? ............................................. 76 3. How do I know which days are workdays, which day is week start date andwhich is period start date? ........................................................................................ 77 4. What lead-times can you define in Oracle Applications? .................................... 78 5. What lead times may be used by ASCP? ............................................................. 80 6. How are lead times used by ASCP in planned order date calculation? ............... 80 7. How does ASCP calculate supply dates?............................................................. 83 8. How can I release sales order from ASCP workbench? ...................................... 83 9. Why do the Supply window and Resource Requirements window show different

start and end date/time of a planned order? ............................................................. 83 Appendix Constraint based planning ............................................................ 84 Constraint types ....................................................................................................... 85 Set constraints for different plan types .................................................................... 86 Rules used in constrained plans ............................................................................... 86


4/87

Page 4

Introduction

Intended audience

This document is prepared as an introductory training material for the end users ofOracle APPS 11i. It covers the basic skills needed for using Oracle Advanced SupplyChain 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 isdiscussed 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


5/87

Page 5

3. Choose Advanced Supply Chain Planner responsibility (you may have acustomized responsibility with a different name assigned to you. Check withyour 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 OracleAdvanced Planning and the rest of Oracle Applications.


6/87

Page 6

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 woulduse 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/87

Page 7

Or

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

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

Attribute Validvalues

Purpose Comment Setup

Make or Buy Make,Buy

Determinewhether theitem ismanufacturedinternally or

purchased

You cannot change this value if openorders exist for the item.

Planner Planner Id Assignmaterial

planner to plan this item

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

InventoryPlanningMethod

NotPlanned,Min-Max,ReorderPoint

Assign planningmethod to theitem

Min-Max : define a minimum quantity onhand. Reorder when this quantity isreached. Also define a maximum on – handquantity that you do not want to exceed.

Reorder point: reorder point is calculated

based on the planning information youdefine for this item. Min-MaxMinimumQuantity

Enter thequantityminimum formin – max

planning.

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

Min-MaxMaximumQuantity

Enter thequantitymaximum formin – max

planning.

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


8/87

Page 8



OrderQuantityMinimum

Enter theminimumorder quantityor repetitiverate. Use this

to define anorder quantity below whichit isunprofitableto build or

purchase theitem.

Planning uses this to modify plannedorder quantities or repetitive daily rates.For discrete items, when net requirementsfall short of the minimum order quantity,

planning suggests the minimum order

quantity.

OrderQuantityMaximum

Enter themaximumorder quantityor repetitiverate of the

item.

Planning uses this to modify the size of planned order quantities or repetitivedaily rates. For discrete items, when netrequirements exceed the maximum orderquantity, planning suggests the maximum

order quantity.

Cost Order Enter thefixed costassociatedwith placingan order ofany quantity.

CostCarrying %

Enter the percentageused tocalculate theannualcarrying cost.

This is the percentage of the unit cost thatrepresents internal cost to stock one unitfor one year.

Source Type Inventory,Supplier,SubInventory

Assignreplenishmentsource type

Inventory : Fill requests by creatinginternal requisitions that become internalsales orders, pulling stock from existinginventory.Supplier : Fill requests by creating

purchase requisitions that become purchase orders, procuring the item froma supplier.Subinventory : Fill requests by creatingmove order requisitions that becomemove orders, pulling stock from anexisting sub inventory.If you are using Supplier Scheduling, it isgenerally recommended that this field beleft blank. Otherwise, it could overrideyour sourcing rules.

SourceOrganization

Optionallyenter theorganizationfrom whichan internalrequisitiondraws theitem.

This applies only when Inventory is thereplenishment source type.


9/87

Page 9



SourceSubinventory

Enter the subinventorywithin thesourceorganization

from whichan internalrequisitiondraws theitem.

This applies only when Inventory orSubinventory is the replenishment source,and only when you specify a sourceorganization.

Safety StockMethod

Select anoption to planuse of fixedordynamicallycalculatedsafety stockquantities.

Used to direct safety stock calculationmethod when Oracle InventoryOptimization is NOT activated.For MRP/MPS planned items, you mustset the Inventory Planning Methodattribute to Not planned , then choose the

MRP planned percent option here.

Safety StockBucket Days

Enter thenumber ofdays todynamicallycalculatesafety stockquantities.

The planning process multiplies the SafetyStock Percent bythe average gross requirements anddivides by the number of days you enterhere.Used by planning modules only.

Safety StockPercent

Enter the percent todynamicallycalculatesafety stockquantities forthe item.

The planning multiplies this percent bythe average gross requirements anddivides by the Safety Stock Bucket Days .The planning process uses this attributewhen you set Safety Stock to MRP

planned percent .Used by planning modules only.

Fixed OrderQuantity

Enter thequantity usedto modify thesize of

planned orderquantities orrepetitivedaily rates.

When net requirements fall short of thefixed order quantity, the planningsuggests the fixed order quantity. Whennet requirements exceed the fixed orderquantity, the planning suggests multipleorders with the fixed order quantity. Fordiscrete items, use this attribute to definea fixed production or purchasing quantity.Used by planning modules only.

Fixed DaysSupply

Enter thenumber ofdays used tomodify thesize andtiming of

planned orderquantities.

The planning suggests planned orderquantities that cover net requirements forthe period defined by this value. The

planning suggests one planned order foreach period.Used by planning modules only.

Fixed LotMultiplier

Enter thefixed lotmultiplequantity orrepetitive rate(units perday).

Planning uses this to modify the size of planned order quantities or repetitivedaily rates. When net requirements fallshort of the fixed lot size multiplierquantity, planning suggests a single orderfor the fixed lot size multiplier quantity.When net requirements exceed the fixedlot size multiplier quantity, planningsuggests a single order that is a multipleof the fixed lot size multiplier.


10/87

Page 10

MPS/MRP planning attributes






11/87

Page 11



PlanningMethod

NotPlanned,MRP

planning,MPS

planning,MRP/DRPPlanned,MPS/DRPPlanned ,DRPPlanned

Select the optionthat Planninguses to decidewhen to plan theitem

Not Planned : The item does notrequire long – term planning ofmaterial requirements. Choose thisoption for high volume and/or lowcost items that do not warrant the

administrative overhead of planning; typically dependentdemand items. You cannot use thisoption unless the Pick Componentsattribute is checked.

MRP planning : Choose this optionfor non – critical items that do notrequire manual planning control,typically dependent demand items.

MPS planning : You masterschedule the item and requiremanual planning control. Choosethis option for items with

independent demand, items that arecritical to your business, or itemsthat control critical resources.

MRP/DRP Planned : Choose thisoption when you want both MRPand DRP planning for the item.

MPS/DRP Planned : Choose thisoption when you want both MRPand DRP planning for the item.

DRP Planned : Choose this optionwhen you have multipleorganizations for which you doDistribution Requirements

Planning for the item.ForecastControl

Consume, Consumeand derive,

None

Select an optionto determine thetypes of demandyou place for theitem. This guidesthe key processesof two – levelmasterscheduling:forecastexplosion,forecastconsumption,

planning, production relief,and shipmentrelief.

This is appropriate only for itemsthat are models, option classes,options, or mandatory componentsof models and option classes.Consume: forecast demanddirectly, rather than by explodingforecast demand.Consume and derive : forecastdemand directly, explode forecastdemand, or use a combination of

both methods. None : place sales order demand but do not forecast demand.


12/87

Page 12



Exception Set Enter the nameof the planningexception set thatgroups togetherthe sensitivity

controls andexception time periods for item – level planningexceptions forthe item.

The item – level planningexceptions include:overcommitted, shortage, excess,and repetitive variance. The

planning process uses this attribute

to decide when to raise planningexceptions for the item.

CreateSupply

Indicates ifsupply can besuggested for thisitem.

CriticalComponent

If selected, flagsthe item as acritical

component forMPS and DRP

planning.

This allows you to plan masterscheduled items with respect toonly critical component and their

material resource constraints.

Pegging SoftPegging, EndAssemblyPegging, EndAssembly/SoftPegging,HardPegging, EndAssembly/HardPegging,

None

Enter the peggingoption.

Soft Pegging: allocates supply todemand based on the ReservationLevel option set in the Planoptions.

End Assembly Pegging: traces theend assembly the item is pegged toat the top of the bill of material.Even if you do not select endassembly pegging, you can stillcalculate and view end assemblieson – line.

End Assembly/ Soft Pegging:Choose this option for both soft

pegging and end assembly pegging. Hard Pegging: allocates supply todemand based on the ReservationLevel option set in the Planoptions. This pegs supply todemand and demand to supply by

project at all levels of a bill ofmaterial. This allows you to pre – allocate supply to demand andgenerate planned orders based onthe plan level options.

End Assembly/ Hard Pegging: Choose this option for both hard

pegging and end assembly pegging. None : disables project materialallocation, end assembly pegging,and full pegging.

PlannedInventoryPoint

Indicates if theitem is anInventory Pointitem.

This means that material can bestored at the item level withoutlosing materials or qualitycharacteristics. Inventory Pointsgenerally point to major stocking

phases in the manufacturing cycle.


13/87

Page 13



ShrinkageRate

Enter a factorthat representsthe averageamount ofmaterial expected

to lose duringmanufacturing orin storage.

The planning process inflatesdemand to compensate for thisexpected loss.

Round OrderQuantities 1

Indicate whetherthe planning

process usesdecimal or wholenumber valueswhen calculating

planned orderquantities orrepetitive rates.

When this option is checked,decimal values round up (neverdown) to the next whole number.The planning process carries anyexcess quantities and rates forwardinto subsequent periods asadditional supply.

Acceptable

Early Days 2

Enter the number

of days beforewhich the

planning processwill notrescheduleorders.

The planning process only

suggests rescheduling out if thenew calculated order date is laterthan the original order due date

plus the acceptable early days; thenew calculated order does notviolate the order of currentscheduled receipts.This applies to discrete items only.

CalculateATP 3

Indicate whetherto calculate and

print available to promise (ATP)on the PlanningDetail Report.

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

Reduce MPS4

None, PastDue,DemandTime Fence,Planningtime Fence

Decide when toreduce master

productionschedule (MPS)quantities tozero.

None : Do not reduce orderquantities on the MPS.

Past Due : Reduce order quantitieson MPS entries to zero when theentry is past due.

Demand Time Fence : Reduce orderquantities on MPS entries to zerowhen the due date moves inside thedemand time fence.

Planning time Fence : Reduce orderquantities on MPS entries to zerowhen the due date moves inside the

planning time fence.


14/87

Page 14



PlanningTime FenceDays 5

Cumulativemfg. leadtime,Cumulativetotal lead

time, Totallead time,User – defined

Determine a point in timeinside whichcertainrestrictions on

planningrecommendationsapply.

Planning calculates the planningtime fence as the plan date (or thenext workday if the plan isgenerated on a non workday) plusthe value entered here.

Cumulative mfg. lead time: Thecumulative manufacturing leadtime for the item.Cumulative total lead time: Thetotal manufacturing lead time forthe item. Total lead time: The total lead timefor the item.User – defined: The value you enterfor Planning Time Fence

Days . DemandTime Fence

Days

Cumulativemfg. lead

time,Cumulativetotal leadtime, Totallead time,User – defined

Determine a point in time

inside which the planning processignores forecastdemand andconsiders onlysales orderdemand whencalculating grossrequirements.

Used to reduce the risk of carryingexcess inventory.

Planning also uses the demandtime fence when loading masterschedules. The demand time fenceis calculated as the start date of themaster schedule load plus the valueentered.Calculate the demand time fence asthe plan date (or the next workdayif the plan is generated on a nonworkday) plus:Cumulative mfg. lead time: Thecumulative manufacturing leadtime for the item.

Cumulative total lead time: Thetotal manufacturing lead time forthe item. Total lead time: The total lead timefor the item.User – defined: The value you enterfor Planning Time Fence

Days .


15/87

Page 15



Release TimeFence Days 6

Cumulativemfg. leadtime,Cumulativetotal lead

time, Totallead time,User – defined, Donot auto – release, Donot release(Kanban)

Determine a point in timeinside which

planned ordersfor discretely

planned items areautomaticallyreleased as WIP

jobs or purchaserequisitions.

No material availability check is performed before WIP jobs arereleased.Calculate the release time fence asthe plan date (or the next workday

if the plan is generated on a nonworkday) plus the value enteredhere.Cumulative mfg. lead time: Thecumulative manufacturing leadtime for the item.Cumulative total lead time: Thetotal manufacturing lead time forthe item. Total lead time: The total lead timefor the item.User – defined: The value you enterfor Planning Time Fence

Days . Do not auto – release: The itemcannot be auto – released.

Do not release (Kanban): ForKanban items prevent release of

planned orders manually orautomatically.

SubstitutionWindow

Cumulativemfg. lead time Cumulativetotal lead time Total leadtime User-defined

Calculates untilwhat time asubstitute can beconsidered for anitem.

Cumulative mfg. lead time: Thecumulative manufacturing lead timefor the item. Cumulative total lead time: The totalmanufacturing lead time for the item.Total lead time: The total lead time forthe 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 toschedule resource utilization for assembly. For assembly, when Round Order Quantityis checked, it means one resource unit can only work on one unit of the assemblyitem. For instance,

Work order quantity: 8Assigned resource units: 3Resource usage: 1 hour/unit item

Job duration: 3 hours (Round Order Quantity checked)2 and 2/3 hours (Round Order Quantityunchecked)

2. Set this attribute to reduce plan nervousness and eliminate minor reschedulerecommendations, especially when it is cheaper to build and carry excess inventoryfor a short time than it is to reschedule an order.3. ATP calculated by the planning process is not related to ATP informationcalculated and maintained by Oracle Inventory. As such, planning ATP does notconsider 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 Informationwindow 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


16/87

Page 16

order. In this case, you would typically set this attribute to None . If you do not haveautomatic production relief, you may select one of the options to reduce MPSquantities and avoid overstating your supply.5. This feature reduces short-term fluctuations in the plan output. The planning timefence (PTF) helps Oracle ASCP generate a stable supply chain plan for manufacturingshops and helps companies to honor contractual commitments with external suppliers.

PTF is a time parameter associated with an organization-item. ASCP functionalityassociated with PTF can be summarized as follows:

Oracle ASCP does not create any new planned orders with start dates withinPTF.

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



17/87

Page 17


Attribute Purpose Comment SetupPreprocessing Enter the days you must add to

purchasing or manufacturing leadtime to place an order.

Processing Enter the days required to procureor manufacture an item.

For manufactured assemblies, processing days equalsmanufacturing lead time.

Postprocessing Enter the days required to receivea purchased item into inventoryfrom the initial supplier receipt.

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

Fixed Enter the days required to make anassembly independent of orderquantity, such as setup orteardown time.

Variable Enter the time to produce oneadditional unit of an assembly.

Total lead time is variable leadtime multiplied by orderquantity, plus fixed lead time.

CumulativeManufacturing

Enter the manufacturing lead timeof an assembly (in days) plus thelargest adjusted cumulativemanufacturing lead time of itscomponents.

Purchased items have nocumulative manufacturing leadtime.This attribute can be calculatedand updated by rolling upcumulative lead times withOracle Bills of Material.

CumulativeTotal

Enter the total lead time of theassembly plus the largest adjustedcumulative total lead time of itscomponents

This attribute can be calculatedand updated by rolling upcumulative lead times withOracle Bills of Material.

Lead Time LotSize

Enter the quantity used to compute processing lead time (as well as

fixed and variable lead times).

The default value is the ite m’sstandard lot size or, if a standard

lot size is not defined, the defaultis 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 receivegoods only on specific days. Oracle ASCP plans each type of supply or demandconsidering 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 CalendarThe shipping calendar indicates the valid working days for shipment activitiesoriginating from suppliers and organizations. The planning engine does notrecommend 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 whengenerating recommended transfers as part of the planning process.


18/87

Page 18

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 validship date (dock date - intransit lead time) after the planning and scheduling processcompletes.

Receiving CalendarThe receiving calendar governs the receiving activities at the organizations orcustomer sites that receive goods. The planning engine allows organizations to receiveshipments 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 thereceipt of the shipment until the next (or previous) working day.

When generating planned transfers between these two facilities, the planning engineassigns dock dates on these planned transfers based on the receiving calendar of theorganization.

Receiving calendars can also vary by combination of carrier and service level. Youneed to specify valid receiving calendars for organizations and customers at thecarrier and service levels.

Carrier CalendarThe carrier calendar indicates the working and non-working days and times formaterial that is intransit using different means of transport. For example, certainmethods of shipment such as parcel carriers may not work on weekends. This maycause the transit time to be stretched over the weekends. The planning engine needs toconsider 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. Itdoes not indicate the pickup or delivery dates of the carrier.

Supplier Capacity CalendarThe supplier capacity calendar governs how supplier capacity is accumulated over a

period of time. Supplier capacity is only accumulated on the working days accordingto the supplier capacity calendar. The supplier capacity calendar also governs how thesupplier 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.


19/87

Page 19

Setup supply chain

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

Approved Supplier ListApproved supplier list is a controlled repository of information that links items andcommodities to suppliers and supplier sites that provide them to a specific ship-toorganization 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.


Comment Setup

Status Approved,Debarred,

New

ASCP only consider Approved and notDisabled suppliers

DisabledGlobal? Yes, No ASCP only plans PO for suppliers withGlobal = Yes

Supplier planning constraintsEnhance sourcing provides the ability to model flexible supplier capacity.

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


20/87

Page 20


Attribute Comment SetupProcessingLeadTime

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

SupplierCapacityCalendar 1

Planning adjusts planned order release date so thatdeliveries occur on the valid delivery date that coincideswith the due date or the closest valid delivery date thatoccurs prior to the due date. This calendar is independent

of your workday calendar.OrderModifiers

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

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

ToleranceFence 2

Use the Tolerance% and Days Advance Notice attributestogether to state by what percentage a supplier can changecapacity 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 capacityallowed with different days of advance notices.

Delivery calendarSet 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, andorganization. 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 deliveryto your dock to occur on a valid delivery day.


21/87

Page 21

If no delivery calendar is defined and assigned to the supplier-item, planning willassume 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 networksShipping networks define transportation links form on organization to otherorganizations. 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 eachdirection. ASCP uses transportation capacity entered on the Shipping Networks formfor each inter-organization link as transportation constraint.

Navigation path: Inventory>Setup>Organization>Shipping Networks


22/87

Page 22

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 networksUse 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 shippingmethod 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 externalsites and inventory organizations. If you use the Inter-Location Transit Times form toenter transit times and transportation capacities between inventory organizations inyour enterprise, ASCP will ignore that information.


23/87

Page 23

Sourcing rulesSupply chain complexity is modeled by sourcing rules, bills of distribution, andassignment sets. Taken together, these forms specify how material is supplied,manufactured, and transferred across the supply chain. But they will not model wherethe 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 specifiedanywhere on the definition forms. These are only descriptions of the means HOWitems are replenished. The defined sourcing rules and bills of distribution can later beassigned to any items or group of items. Assignment sets are used to associate itemswith sourcing rules and bills of distribution.

Note: Sourcing rules and BODs can be defined at the source instances or at the APSinstance, or at both places. The Assignment Set of a specific plan will govern whichrules are used by that plan. However, sourcing rules and bills of distribution that crossinstances must be set up on the APS instance.

Navigation path: Supply Chain Planner>Sourcing>Sourcing Rules



Comment Setup

Type TransferFrom,Make At,Buy From

Transfer From : Transfer between internal organizations,enter source organization in the Org column. When it isselected, Supplier and Supplier Site are disabled.

Make At : Make at an internal organization, entermanufacturing organization in the Org column. When itis selected, Supplier and Supplier Site are disabled.

Buy From : Purchase from an external enterprise, enterSupplier and Supplier Site. When it is selected, the Orgcolumn is disabled.

Allocation%1

The total allocation percentage for all sources within arank must add up to exactly 100. Planned order is splitamong the sources according to their allocation

percentages.


24/87

Page 24


Comment Setup

Rank 1 The sources with the highest rank (lowest number) havethe highest priority in allocations. When sources of thehighest rank have no more capacity, allocation goes tosources 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 theallocation percentages equals 100.

All Orgs Checked,unchecked

Checked: This sourcing rule can apply to allorganizations.

Org Checked,unchecked

Checked: This sourcing rule can apply to oneorganization.

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 thehighest priority in allocation. Time – phasing in a sourcing rule determines when eachgroup of shipping method – ship org combinations is in effect.

Assignment setsOnce you have defined your sourcing rules, you must assign them to particular itemsand/or organizations to make them functional. These assignments are groupedtogether in assignment sets. This is where various sourcing strategies define a

particular supply chain network. Each assignment set represents a selection oforganizations and/or items you want planned. To influence the planning process, youmust 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 aspecific item. In the preceding list of assignment levels, the levels are listed fromspecific to general. Specific sourcing assignment overrides general assignment, i.e.,rows above override rows below. For instance, Item-Organization overrides Item.

Navigation path: Supply Chain Planner>Sourcing>Assign Sourcing Rule/BOD


25/87

Page 25

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 anassignment set.

Assignment HierarchyThe assignment hierarchy of sourcing rules and bills distribution is listed in thefollowing table, rows below override rows above them. Columns on the right overridecolumns on the left.


26/87

Page 26

Note : A global sourcing rule has an unspecified receiving organization. Billsof distribution are global.Since not all assignment types are valid for both sourcing rules and bills ofdistribution, the effect of the Sourcing Rules vs. Bill of DistributionAssignments 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 sourcingrelationships. 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


27/87

Page 27

create another rule to source from Supplier B and assign this rule to that specificfastener. The detail-to-general hierarchy directs the specific fastener to be sourcedfrom Supplier B, while all other fasteners still from Supplier A.

Create the minimum number of sourcing rules and keep the assignment sets as simpleas possible. Rather than create and assign a rule to each item, you can assign a defaultrule to an organization, another default rule to a category. Assign a rule to anindividual item/organization only to deal with exceptions.

Order management

Most modules in Oracle Manufacturing do not interact directly with Oracle OrderManagement. These modules use sales order information through the supply/demand

portion of Oracle Inventory . In Oracle Applications 11i, sales orders are visible to thesupply/demand portion of Oracle Inventory only after they are scheduled. Use theSchedule Order process to create sales order information in Inventory. The scheduledsales 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. Datacollection programs capture a snapshot of the source data, and copy that snapshot tothe planning instance. The planning engine then performs multi-organization planningand scheduling calculations. The results of the planning process, such as plannedorders, 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, Productfamilies, 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 costsMRP/Supply Chain

PlanningForecasts, 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 isdirectly 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. Thereare three collection methods:


28/87

Page 28

The Complete Refresh method clears all transaction data for all businessentities from the planning server (for the source instance being collected),and then copies over information about the user-selected entities. Thismethod 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 supportedmainly 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 theentity information over from the transaction instance. Information aboutnon-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 anautomated process of data collection that efficiently synchronizes the dataon the planning server by looking up the sources. If you opt for continuous

collections, the system automatically determines the type of collection thatneeds to be run on entities selected by you. The continuous collections process collects data from the sources with the least user intervention. TheContinuous Collections concurrent program performs continuouscollections. Continuous collections is not covered in this training.

Use Complete Refresh the first time you perform collections from a source instance tothe planning server. You may also wish to use complete refresh collections after asignificant 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. UseComplete Refresh only when it is necessary.

Use Net Change Refresh if you would like to update the supply and demand pictureon the planning server as quickly as possible, and the incremental changes to supplyand demand in the source instance since the last collection have not been extensiverelative to the existing (already collected) body of supply and demand information. Inthis 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 instanceonly 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 categoryof supply and demand entities supported by Net Change Refresh. For example, toupdate the planning server with a newly rebuilt manufacturing calendar, you wouldrun Targeted Refresh collections for just the calendar business entity. Data on the

planning server about all other business entities would remain unaffected by thiscollection. Also use Targeted Refresh (in lieu of Net Change Refresh) to bring overthe latest picture of supply and demand to the planning server in cases when theincremental changes to supply and demand on the source instance since the lastcollection are very extensive. In this case, the update mechanism employed byTargeted Refresh collections (wholesale deletion followed by rebuilding of data onthe planning server) is faster than the mechanism employed by Net Change Refresh

collections (incremental insertions into existing data on the planning server).


29/87

Page 29

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


30/87

Page 30

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 organization Number of Workers 1 One or greater. Increase this number to increase the number of

computational resources devoted to the Planning Data Pull process.This allows you to specify the number of workers for the Data Pull,

which can now be different from the number of workers specified forthe ODS load process.

Timeout (Minutes) 1 The maximum amount of time you would like to allocate to thePlanning Data Pull process. If the Planning Data Pull process has notcompleted within this amount of time, it will be terminated with anerror.

Purge Previously CollectedData

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

Collection Method 2 Complete Refresh/Targeted Refresh/Net ChangeRefresh. See the explanation in the Data collection methods section ofthis manual


31/87

Page 31

Parameter ValuesAnalyze 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 thesubsequent Planning ODS Load process.

Business objects The remaining parameters in the Planning Data Pull Parameters are alist of business objects. Selecting Yes for an entity means collectingthe information for that entity over from the source instance. Selecting

No for an entity means collecting no information for that entity overfrom the source instance. This is useful when you know there are onlychanges 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 whenreally 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 notcompleted within this amount of time, it will be terminated with anerror.

Number of Workers 1 One or greater. Increase this number to increase the number ofcomputational 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 forthe ODS load process.

Recalculate ResourceAvailability

This defaults to the value (Yes or No) that you set for the ResourcesAvailability business entity in the Planning Data Pull Parameterswindow. The value that you set here is the one that actually determineswhether resources availability is collected or not.


32/87

Page 32

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 whethersourcing history is collected or not. If you select Yes, then ASCP willcollect all new sourcing history not already on the planning server inthe time range [(today - x months) through (today)] from the source

transaction system. The number x is given by the value that you set forthe profile option MSC: Sourcing History Start Date Offset (inmonths). During planning, ASCP will use the total cumulativesourcing history on the planning server in addition to the plannedsourcing in the plan to determine whether sourcing percentages insourcing rules are being respected or not.

Purge Sourcing History Valid values are Yes and No (default). If you select Yes, then allsourcing history present on the planning server will be deleted beforethe collection process commences.

Note: 1. Consult with your system administrator and DBA on the values ofthese 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 PlanningHorizon

Goals Scenario

Unconstrained Long TermFuture

How much resource capacityand material availability do Ineed to arrange in order tosatisfy all anticipated demand ina timely manner?

Decisions can be made onResource acquisition/dispositionand supplier sourcing to addressthe exceptions.

ResourceConstrained

Long TermFuture

How much material availabilitydo I need to arrange in order tosatisfy all anticipated demand ina timely manner?

Difficult to change resourcecapacity, but increasedoutsourcing is an option.Decisions can be made on suppliersourcing to address the exceptions.

MaterialConstrained

Long TermFuture

How much resource capacity doI need to arrange in order tosatisfy all anticipated demand ina timely manner?

Difficult to change materialavailability but internal resourceacquisition/disposition is anoption. Decisions can be made onResource acquisition/dispositionto address the exceptions.


33/87

Page 33

Plan Class PlanningHorizon

Goals Scenario

Material andResourceConstrained

Near TermFuture

Generate a feasible plan thatrespects material, resource,distribution, and transportationconstraints.

Impossible to overcome materialand resource constraints andtherefore must respect them inorder to generate a feasible supplychain plan.

Optimized Near TermFuture

Generate an optimized andexecutable plan based on planobjectives and material,resource, and transportationconstraints.

Impossible to overcome materialand resource constraints andtherefore must respect them inorder to generate a feasible supplychain plan.

Note:

Oracle ASCP lets you prioritize how you enforce Capacity Constraints or DemandDue Dates. Whichever constraint takes precedence over the other is the hardconstraint; and the other is the soft constraint. You must choose one and only one typeof constraint.

If you choose to enforce Demand Due Dates (setting Demand Due Dates as a hardconstraint), then primary resources are used and loaded to capacity to satisfy demanddue dates. The system also evaluates alternate resources if additional capacity isrequired. If there is insufficient capacity to meet demand due dates, the primaryresource is overloaded. The choice of whether to use an alternate resource or overloadcapacity depends on cost considerations if optimization is selected. Oracle ASCPreturns exception messages if capacity is overloaded.

If you choose to enforce Capacity Constraints (setting Capacity Constraints as a hardconstraint), 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 latereplenishment exception messages.

ASCP plan types

There three types of ASCP plans.

Production Plan, equivalent to traditional MPS Manufacturing Plan, equivalent to traditional MRP Master Plan

Each creates time-phased planned orders that satisfy independent and dependentdemand while seeking to respect material and resource constraints. These three typesof plans need to be used in conjunction with the MPS/MRP Planning Type itemattribute 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 itemsincluded depend upon the plan type and the it em’s the MRP Planning Type attribute.


34/87

Page 34

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, plannedorders can be automatically released within their release time fence .

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

6. Select a Plan Type. Valid values are Manufacturing Plan, Production Plan, andMaster Plan. This setting interacts with the MPS/MRP Planning method itemattribute to determine which subset of the items that pass the conditionimposed 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 options

Navigation path: Advanced Supply Chain Planner>Supply Chain Plan>Names >PlanOptions (B)


35/87

Page 35

Main tab

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

Parameter Description Comment SetupAssignmentSet

The assignment set that holds the sourcingrules and bills of distribution that define therules for material flow within your supplychain.

DemandPriority Rule When ASCP does detailed scheduling, itschedules demands one by one. The rulespecified here dictates the order in whichdemands will be considered during detailedscheduling, and thus which demands willget the first opportunities to take upavailable materials and resource capacities.

Overwrite 1 Overwrite planned orders.AppendPlannedOrders 1

Appends new planned orders to current plan.

PlannedItems 2

This parameter and the next one, PlanningMethod, control the items that are planned

in the supply chain plan. An item mustsatisfy conditions imposed by both

parameters before being included in thesupply chain plan.

MaterialSchedulingMethod

Choose from Operation Start Date or OrderStart Date scheduling methods. If youchoose Operation Start Date, material isscheduled to arrive at the start of theoperation for which it is required. If youchoose Order Start Date, material isscheduled to arrive at the start of the orderfor which it is required.

Order State Date isusually an earlier datethan the OperationStart Date andtherefore thisselection representsthe more conservative

planning logic of thetwo options.


36/87

Page 36

Parameter Description Comment SetupEnd ItemSubstitutionSet

If Decision Rules tabbed region > Use EndItem Substitutions selected, select asubstitution set. These are defined in thePlanning Details - Substitute windowdiscussed. You can use a set of substitutionrelationships to be effective for a given plan

by selecting the substitution set as an optionfor the plan. This allows you to runsimulations of possible substitutions andevaluate performance indicators given

possible future substitutions.Schedule By Set this option to instruct the planning

engine to:Plan supplies based on sales order linerequest, promise, or schedule dates foreither ship or arrivalConsume forecasts based on sales order linerequest, promise, or schedule dates. Youmust provide forecast dates that match your

choice of this plan option; for example, ifyou select Promise Ship date for this planoption, make sure your forecast dates are interms of promise ship dates.If you do not specify plan option DemandPriority Rule and have not specified adefault demand priority rule (in the DefinePriority Ruled form), the planning engineuses the value of this plan option as thedemand priority rule.

Select one of thefollowing sales orderline dates:Schedule Ship DateSchedule Arrival DateRequest Ship DateRequest Arrival DatePromise Ship Date

Promise Arrival DateThe default isSchedule Ship Date.

DemandClass

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

This field is activeonly for a ProductionPlan/MPS schedule.

Move Jobs toPIP

Check this option if you want to generate planned order supply even in the absence ofdemand in order to ensure that inventory isheld on the manufacturing floor only foritems designated as Planned InventoryPoints.

Display KeyPerformanceIndicators

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

DemandTime FenceControl

Check this option to enforce demand timefence control.

Demand time fence isan item attribute

PlanningTime FenceControl

Check this option to enforce planning timefence control.

Planning time fence isan item attribute

Lot for Lot Check this option to force the creation of aseparate supply for each demand. This

prevents the creation of aggregate suppliesthat satisfy multiple demands.

Order quantitymodifiers such asMinimum Lot Sizeand Fixed LotMultiple override thisoption

IncludeCriticalComponents

Select this plan option to instruct the planning engine to plan considering criticalcomponents. Depending on the plan typeand the planning item types, the planningengine may plan critical components andnot plan other components or componentsof those components.

To mark an item as acritical component,select its itemattribute CriticalComponent.


37/87


38/87

Page 38

Parameter Description Comment SetupPegging – ReservationLevel

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

Do not use

Pegging – Hard PeggingLevel

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

Do not use

ForecastConsumptionBackwardDays

If you are bringing in unconsumed forecastscenarios from Oracle Demand Planning asdemand schedules into Oracle ASCP andwould like to do forecast consumptioninside ASCP (as opposed to bringing in pre-consumed forecasts contained in masterdemand schedules as demand schedules intoOracle ASCP), then set the forecastsconsumption backward days parameterhere. This parameter allows a sales orderdemand to consume forecast demand evenif the forecast demand is up to the specifiednumber of days earlier than the sales order

demand. This parameter applies only toOracle Demand Planning scenarios that areused as demand schedules in Oracle ASCP

plans.ForecastConsumptionForwardDays

This parameter allows a sales order demandto consume forecast demand even if theforecast demand is up to the specifiednumber of days later than the sales orderdemand.

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 tomeet 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 thetable below for more information.

Overwrite AppendPlanned 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 plannedorders. It does, however, overwrite any suggested plannedorders that are not firm.

Outside planning timefence

The planning process overwrites all entries from the current plan, planned and firm planned, outside the planning timefence, and overwrites only planned orders inside the planningtime fence. It does not overwrite any firm planned orders withinthe planning time fence. The planning time fence can bedifferent for each item, so the planning process looks at the

planning time fence for each item when choosing what todelete. Planning time fence is an item attribute defined inInventory

Unchecked The planning process does not append any planned orders to thecurrent plan. Additional demand does not cause planned orderrecommendations. Instead, the projected quantity on hand maygo negative in response to demand that was not met by a

suggested planned order.


39/87

Page 39

Overwrite AppendPlanned Orders

Effects

Checked The planning process appends additional planned orders afterthe last entry on the current material plan to meet any additionaldemand. The Overwrite and Append Planned Orders optionswork 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 andfirm planned orders while regenerating new planned orders.You can use this combination the first time you run your planor if you want your plan to reflect all sources of new demand.

Outside planning timefence

Checked This option allows you to create an extension to the currentmaterial requirements plan, delete planned and firm plannedorders outside the planning time fence and delete all plannedentries 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 overwritingafter the planning time fence, you are also appending new

planned orders after that date. Use this combination to stabilizethe short – term plan and allow the long – term plan to react to

new sources of demand. If an item has no time fence specifiedand this option is chosen, all planned and firm planned ordersare overwritten. The effect is the same as Overwrite All andAppend Planned Orders checked.

None Checked When you choose not to overwrite an existing plan, the planning process does not overwrite existing firm plannedorders, 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 sectionsof your material requirements plan. You can extend the planhorizon without altering existing firm planned orders.

None Unchecked The planning process does not overwrite existing firm plannedentries, but deletes any suggested planned orders. In addition, itdoes 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, andallows you to solve these problems by manipulating the planmanually. In this case, the projected quantity on hand would gonegative since no planned orders were suggested to meet theadditional demand. The material planner can use on – lineinquiries and reports with exception messages to identifymaterial shortages. This gives maximum control to the material

planner.

Note: 2. Planned Items, Planning Method and Item’s attribute MRP/MPS Planningmethod work together to select items in the plan. The following table lists the threecontrols that together determine which items are planned in a supply chain plan, andthe possible values for each control.

Planned Itemsvalue

Plan type Planned Items in the plan

All planned items Master Plan All items in the planned organizations having MRP/MPSPlanning Method attribute value ofMPP planningMRP and MPP planningMPS and MPP planningPlus:MRP planned and MPS planned items that are in betweenthe above items in the bills of material.All items in the input schedules.


40/87

Page 40

Planned Itemsvalue


All planned items Production Plan All items in the planned organizations having MRP/MPSPlanning Method attribute value ofMPS 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 havingMRP/MPS Planning Method of Not Planned

Demand scheduleitems only

Master Plan All items in the input demand schedules, and allcomponents of these items that have MRP/MPS PlanningMethod 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 materialDemand scheduleitems only

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

Demand scheduleitems only

Manufacturing Plan All items in the input demand schedules, and allcomponents of these items that have MRP/MPS PlanningMethod attribute code of:MRP planningMRP and MPP planning

Supply scheduleitems only

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


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


Manufacturing Plan All items in the input supply schedules, and all componentsof these items that have MRP/MPS Planning Methodattribute code of:MPS planningMPS and MPP planning

Demand andSupply scheduleitems

Master Plan All items in the input demand and supply schedules, and allcomponents of these items that have MRP/MPS PlanningMethod attribute code of:MPP planningMRP and MPP planningMPS and MPP planningPlus:MPS and MRP planned items that are in between the aboveitems in the bills of material


41/87

Page 41

Planned Itemsvalue



Production Plan All items in the input demand and supply schedules, and allcomponents of these items that have MRP/MPS PlanningMethod attribute code of:MPS planningMPS and MPP planning

Plus:MPS and MRP planned items that are in between the aboveitems in the bills of material


Manufacturing Plan All items in the input demand and supply schedules, and allcomponents of these items that have MRP/MPS PlanningMethod attribute code of:MRP planningMRP and MPP planning

Aggregation tab

Use the information in the following table to specify parameters on the Aggregationtab.

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 thesystem date.

End Date Shows the calculated end date for your plan. This is a view-onlyfield, 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 resourceslevel.

MinutesBucket

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

HoursBucket Size

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

Days BucketSize

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


42/87

Page 42

Organization tab

Use the information in the following table to set parameters on the Organizations tab.

Parameter Description Note SetupGlobalDemandSchedules

Select the names of Oracle DemandPlanning scenarios that drive this

plan. You can select demandplanning scenarios that do notreference an organization(organization dimension set to AllOrganization).

Ship ToConsumptionLevel

Select a forecast consumption levelfor the Oracle Demand Planningscenario. The global forecasting

process consumes forecast entriesthat have Ship To value the same asthis plan option.

You can select:- Customer- Customer Site- Zone- Customer Zone- Demand Class- ItemThe choices in the list ofvalues changes dependingon the published level of thescenario.

Org The plan’s organization.Description Description of the owningorganization.

Net WIP Select to consider discrete jobs andother production orders as supply inthe planning demand/supply netting

process. NetReservations

If checked, ASCP generates peggingof on-hand supply to sales ordersthat matches the reservationsrecorded in the source transactionsystem.


43/87

Page 43

Parameter Description Note Setup Net Purchasing Select to consider purchase orders,

purchase requisitions, in-transitshipments and other non-productionorder scheduled receipts as supply inthe planning demand/supply netting

process. This option covers all

scheduled receipts not covered bythe Net WIP option.Plan SafetyStock

Select to consider plan safety stockdemand and supply in the planningdemand/supply netting process.

Include SalesOrder 1

Select to invoke forecastconsumption within ASCP for theselected organization. Check this ifthe demand schedules for theorganization are unconsumedforecasts. Uncheck this if thedemand schedules for theorganization are consumed forecasts

plus sales orders in the form ofmaster demand schedules

Bill ofResource

Select Bill of Resources from the listof values if one of the Routings isset to BOR on Aggregation tab.

Simulation Set Select a Simulation Set from the listof values. A simulation set is a set ofadjustments to the base availabilitycalendar of a resource, and isdefined via the Oracle Bills ofMaterials Department Resourcesform. You can define differentsimulation sets to model differentavailability scenarios (for example,the base availability calendar couldreflect 5-day operations; simulationset 1 could reflect working 6days/week for a certain period;simulation set 2 could reflectworking 7 days/week for a certain

period). The simulation set that youselect is applied to all resourceswithin the organization.

DemandSchedules 2

Select the name of your demandschedule/forecast/plan.

Ship ToConsumptionLevel

See above See above

Interplant If selected, the planning engine usesonly interorganization orders anddemands from interorganization

planned orders. If cleared, the planning engine uses demands fromall planned orders.

SupplySchedules

Select the name of your supplyschedule for each organization.

Subinventory Netting

Opens the Subinventory Nettingwindow.


44/87

Page 44

Note : 1. Users can collect forecasts into the APS planning server. Optionally, they canchoose to consume forecasts by sales orders when they run ASCP plans. Forecasts areconsumed if the Include Sales Order check box in the Organizations tab of the PlanOptions window is checked. For multilevel ATO items, forecasts are consumed at alllevels if the forecast explosion has occurred in the source instance prior to thecollection. If you are not using forecast, uncheck this check box .

2. The plan for one organization can be used as a demand (or demand schedule)for the plan of another organization.

Constraint tab

Use the information in the following table to specify parameters on the Constraintstab.

Parameter Description SetupConstrainedPlan

If selected, Enforce Demand Due Dates is selected, all fields inthe tabbed region are updateable with all constraints defaulted toYes. The default is cleared. You cannot set all ResourceConstraints and Material Constraints to No. If you set anyResource Constraints to Yes, you cannot clear CalculateResource Requirements.

EnforceDemand DueDates

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

EnforceCapacityConstraints

Check this option if you want material and resource capacityconstraints to be respected in lieu of demand due dateconstraints.

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

Select Yes to consider resource constraints for the bucket.

SupplierCapacityConstraints

Select Yes to consider supplier capacity constraints.


45/87

Page 45

Parameter Description SetupEnforcePurchasingLead-timeConstraints

Select this plan option to instruct the planning engine toconstrain the plan by purchased item lead times (item attributesor approved supplier list).Clear it to instruct the planning engine never to miss a demanddue date because of a purchased item lead time.

Scheduling Specify whether to enable detailed scheduling.

MinutesBucket Size(inDays)

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

Hours BucketSize (inDays)

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

Days BucketSize (inDays)

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

CalculateResourceRequirements

If selected, the program will calculate resource capacityutilization.

PlannedResources

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

BottleneckResourceGroup

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

Decision Rules tab

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

Parameter Description SetupUse End ItemSubstitution

If selected, use end item substitute prior to creating new plannedorders. If cleared, use only the demanded item. Enter the End ItemSubstitution Set in the Main tabbed region.

Use AlternateResources

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

UseSubstituteComponents

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


46/87

Page 46

Parameter Description SetupUse AlternateBOM/Routing

If selected, use primary routings and use alternates only ifnecessary. If cleared, use only primary bills of material androutings.

Use AlternateSources

If selected, use primary sources and use alternate sources only ifnecessary. If cleared, use primary sources only. The planningengine 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 onOK then submit the request.

Copy a plan

Navigation path: Advanced Supply Chain Planner>Supply Chain Plan>Names>CopyPlan (B)


47/87

Page 47

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 andactions 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


48/87

Page 48

Plans tab displays the entities associated with the plan in a hierarchical fashion (usercan 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 althoughdefined in one organization could still be a multi-org plan)

View Plans byo Actionso Organizationso Itemo Resourceso Projectso Suppliers

Var iety of “Right -Click” navigations possible from each node (or use ofShortcut buttons at the bottom of the navigator)

List of Item Categories displayed is based on Tools à Preferences à Other àCategory Set


49/87

Page 49

Supply chain structure

Supply Chain Structure – Items and Item Details Right Click on Item (in Navigator) > Items Key data displayed include Lead Times and Order Quantities Variety of other planning related item attributes available for display through

Folder functionality Items window is a launching pad to more detailed structural information on

the item Supply Chain Bill

o Displays Sourcing and BOM structure for the 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 issourced 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 to Where Used: The items in the next level up in the bill of material that use this

item as a component


50/87


51/87

Page 51

Components:

Routing Operations and Resources:


52/87

Page 52

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 planningtime bucket level

o Detail: Shows the shift level capacity for the selected day. Also allowsfor update of resource availability


53/87

Page 53

Gantt Chart – Shows graphical view of activities planned on the resource Requirements – Shows Forms based view of activities planned on the resource

Gantt Chart:

Avai

Documents

5031-ASCP Training Manual v1.2