Oracle ASCP

Fundamentals

Oracle Applications Competency

Agenda of discussion
How do ASCP and ERP instances collaborate? What is the ASCP and ERP instance architecture? MULTI-ORG PLANNING - Defining Sourcing Rules and Assignment Sets Defining Forecast Sets as demand source Data Collections Setting up an ASCP plan
Multi-Org planning Constrained Planning

Releasing Planned Orders ASCP scheduling concept Unconstrained Plan output Difference between constrained and unconstrained plans

ASCP and transaction instance collaboration

OM

DEMAND PLANNER

DEMAND

ERP

COLLECTIONS

ADVANCE SUPPLY CHAIN PLANNER (ASCP)

DATABASE LINK

PO WIP

PURCHASE ORDER

WIP

DATABASE LINK DATABASE LINK

WORK ORDER

SOURCE INSTANCE

PLANNING INSTANCE

Implementation hardware architecture

Single Machine Architecture Two-machine architecture

Centralized Planning

Decentralized Planning

Single machine same instance and same server Two/multiple machines ASCP, DP and express are different instances and are on

different servers
Database links are setup between source and destination instances for data flow

between ERP and ASCP/DP and back to ERP in two/multi-instance planning

Multi Instance Planning

M1 M2
collections

M1 M2

M1 M2

M1 M2

ODS
Planning

Release

ODS - Operational Data Store PDS - Planning Data Store

PDS

Multi-Org Planning
Planned Order (WIP) through Routing Operation

Planned Order through Transfer From Sourcing Rule

S1 S2

(IR) M1 ISO

M2 ASCP

Cus

Planned Order (PR) through Buy From Sourcing Rule

Multi-Org Planning - Defining Sourcing Rules

Navigation: Purchasing > Supply Base > Sourcing Rules

- BUY FROM

Multi-Org Planning - Defining Sourcing Rules

Navigation: Purchasing > Supply Base > Sourcing Rules

- TRANSFER FROM

Multi-Org Planning - Defining Assignment Sets

Navigation: Purchasing > Supply Base > Assign Sourcing Rules

Defining Assignment Sets contd

Defining Forecast and Forecast Sets

Navigation: Supply Chain Planner > Forecast > Sets

Defining Forecast and Forecast Sets .. Contd

Click on Forecast Items > Detail Date is the Forecast Date

Setting up Data Collections

Data Collections brings all the transaction data to ASCP

Setting up Data Collections contd

Collection Method is Complete Refresh All transaction data needs to be set to Yes

Complete Refresh Net Change Refresh

Setting up Data Collections contd

Types of Data Collections

Net Change Refresh
Collect only the incremental change

Complete Refresh
Purges all previously Collected data and collects all data corresponding to all entities afresh For the first time need to run complete collection

Collection Workbench
View the collected data

Viewing the Collected Data

Navigation: ASCP > Collections > View Collected Data

Viewing the Collected Data contd

Viewing the Collected Data contd

Setting up the Plan Options

Navigation: ASCP > Supply Chain Plan > Names Click on Plan Options

Setting up the Plan Options Aggregation Tab

Choosing daily bucket and 30 days planning horizon

Setting up the Plan Options Organizations Tab

For the main org M1 choose WIP, Purchases and SO as demand and supply

Setting up the Plan Options Organizations tab .. Contd

For the distribution org M2, choose Forecast Set and Purchases as the

sources of demand and supply

Note WIP is not a part of the distribution org M2

Executing the Supply Chain Plan

Navigation: ASCP > Supply Chain Plan > Names Click on the Launch Plan button

Executing the Supply Chain Plan

Accept all defaults and click on OK

Planning stages
Snapshot Monitor Memory Based Snapshot Worker Memory Based Planner Snapshot Delete Worker Snapshot Loader Worker

Flat File MBSW

Deletes existing data from MSC base tables (PDS)

MBP

SDW SLW

Takes data from Flat Files and loads new data onto base MSC base tables (PDS)

PDS

Releasing Planning Recommendations

Navigation: ASCP > Supply Chain Plan > Workbench Choose the plan, in this case the plan name is Enditem Navigate to Enditem > Supply/Demand > Supply/Demand

Releasing Planning Recommendations contd

Search by assembly item and component items respectively Search by assembly item

Releasing Planning Recommendations .. Contd

Navigate to the Planned Orders Check the For Release checkbox

Releasing Planning Recommendations contd

Click on the Release Properties tab to check the quantity and type of Planned Order

Releasing Planning Recommendations .. Contd

Release the Planned Order

Release Planning Recommendations contd

The Release screen will show the 1 Discrete job being created

Releasing Planning Recommendations contd

Navigate to View -> Requests to see details Choose the request WIP Mass Load and click on View Output

Releasing Planning Recommendations contd

View the output for the WO/job details Job is always in Unreleased state

Releasing Planning Recommendations contd

Search by component item

Releasing Planning Recommendations .. Contd

Check the For Release checkbox for the Planned Order Click on the Release Properties tab to check the Quantity and type of planned

order

Releasing Planning Recommendations .. Contd

Release the Planned Order The Release screen shows 1 New Requisition created

Releasing Planning Recommendations contd

Navigate to View -> Requests Navigate to Requisition Import Click on View Output to view the output file

Releasing Planning Recommendations contd

View the output file to check if the Requisition has been generated correctly Requisition will always be generated in Approved status

Releasing Planning Recommendations contd

Check for the Requisition in Purchasing

responsibility

Navigation: Purchasing > Requisitions >

Requisitions Summary OK

Choose Import Source as MSC and click Click on Find

Releasing Planning Recommendations contd

The Requisition at the top is the one that was released Click on Lines to confirm other details

Releasing Planning Recommendations contd

Check item, quantity etc.

Demand transition in Multi-Org planning (unconstrained)

Demand Supply netting off

ASCP Scheduling Look-Ahead Heuristic

Scheduling adjusting demand as per capacity constraints Demand is scheduled with due date as priority Backward scheduling
Lower priority demands are scheduled first Higher priority demands are scheduled next

Forward scheduling
If backward scheduling generates due dates in the past, then all demands are right justified

from the current date

Scheduling buckets
Days Hours Minutes

ASCP Scheduling organization setup

Organizations tab
Single organization scheduling Sales Order is the only source of demand

ASCP Scheduling constraints setup

Constraints tab
Constrained Plan Resource Capacity is constrained Scheduling is in minutes bucket

ASCP Scheduling contd

Workday calendar defines only one shift from 9:00 to 17:00 hours Plan is run on 30th June Sales Order Request Date 30/6/2006 Quantity = 100 (SO1) Sales Order Request Date 07/07/2006 Quantity = 140 (SO2) As per Look Ahead Heuristic scheduling, SO1 has higher priority than SO2 In the planner workbench the planned order dates and quantities look as follows-

ASCP Scheduling - logic

The foll: diagram explains the minutes scheduling logic (note: 6 items per hour

is the resource capacity in the routing)

Demand for SO1 in hours = 100/6 = 16 hours 40 mins Demand for SO2 in hours = 140/6 = 23 hours 20 mins

Backward Scheduling 26 27 28 29 30 03 05 06 07 10 11 12

16 hrs 40 mins

23 hrs 20 mins

Priority 1 Scheduled second

Priority 2 Scheduled first

5 pm on 10th July

9:40 am on 6th July Forward Scheduling (right justification) 27 28 29 26 30 03 05 06 07 10 11 12

16 hrs 40 mins

23 hrs 20 mins

Unconstrained Plan - setup

The Constrained Plan checkbox should be Unchecked

Unconstrained Plan - output

There is NO resource constraint of 6 items per hour as per routing setup
The Planned Order against each SO demand is generated fully the very

next day

Difference between Constrained plans and Unconstrained plans

Constrained plans
Resource capacity can be constrained Supplier capacity can be constrained Scheduling is possible in days/hours/minutes buckets Time stamp indicates the exact shift time of planned orders for

hour/minutes scheduling
Time stamp indicates 23:59 for days bucket (end-of day in a 24 hour

cycle) scheduling
Optimization is possible

Unconstrained plans
No resource or supplier capacity constraints No scheduling or optimization possible Time stamp is not relevant for planned orders Time stamp always shows 0:00 in unconstrained plans

Thank you