Oracle_PS_Production_Scheduling_Integration.ppt

Integration Oracle Production Scheduling

1. Copyright © 2006, Oracle. All rights reserved.
EBS / PS Integration V1.0
Functional / Technical Deep Dive

2. Copyright © 2006, Oracle. All rights reserved.2
Purpose:
This document provides an overview of features and enhancements included in
Release 12.
  It is intended solely to help you assess the business benefits of upgrading
to Release 12.
Disclaimer:
This document in any form, software or printed matter, contains proprietary information
that is the exclusive property of Oracle.
  Your access to and use of this confidential
material is subject to the terms and conditions of your Oracle Software License and
Service Agreement, which has been executed and with which you agree to comply.
 
This document and information contained herein may not be disclosed, copied,
reproduced or distributed to anyone outside Oracle without prior written consent of
Oracle.
  This document is not part of your license agreement nor can it be incorporated
into any contractual agreement with Oracle or its subsidiaries or affiliates.  

This
document is for informational purposes only and is intended solely to assist you in
planning for the implementation and upgrade of the product features described.
  It is not
a commitment to deliver any material, code, or functionality, and should not be relied
upon in making purchasing decisions.
  The development, release, and timing of any
features or functionality described in this document remains at the sole discretion of
Oracle.  

Due to the nature of the product architecture, it may not be possible to safely
include all features described in this document without risking significant destabilization
of the code.

3. Copyright © 2006, Oracle. All rights reserved.3
Functional / Technical Deep Dive Agenda
•Integration Overview
•Technical Architecture Overview
•Implementation Setup, Considerations, Tips and Tricks
•Customization and Extensibility Options
•Troubleshooting
•Wrap Up/Q&A

4. Copyright © 2006, Oracle. All rights reserved.4
Functional / Technical Deep Dive Agenda
•Integration Overview
•Technical Architecture Overview
•Implementation Setup, Considerations, Tips and Tricks
•Customization and Extensibility Options
•Troubleshooting
•Wrap Up/Q&A

5. Copyright © 2006, Oracle. All rights reserved.5
EBS / PS Integration
•Business Problem: Detailed
production scheduling to drive shop floor
execution and material planning
•Major Features:
•Provides the ability to create a Production
Schedule for a given EBS Organization
•Uses EBS Items, Bills of Materials,
Routings, Resources etc. to construct a
PS model
•Schedules work orders/jobs/batches from
ERP and also planned orders from ASCP
•Release of the production schedule from
PS back to EBS
•Supports EBS Discrete (WIP), process
(OPM), OSFM manufacturing
environments

6. Copyright © 2006, Oracle. All rights reserved.6
•Seamless integration of manufacturing planning, scheduling and execution results
in
–Faster implementation cycles (most of the data needed to build the PS model is
already present in Oracle EBS)
–Closed loop planning and scheduling process results in an efficient supply chain
with low inventories and high customer service levels
•State-of-the-art production scheduling system improves resource utilization, order
fill rates and increases working efficiency of the scheduler
–Sophisticated feature rich solver algorithms
–Powerful easy to use interface for
— Advanced analytics
— Model visualization
—Multi- scenario comparisons
— Schedule manipulation
•Rapid solution times
Production Scheduling Integration
Benefits

7. Copyright © 2006, Oracle. All rights reserved.7
Collaborative Planning CP
Sales and Operations
Planning
From short-term to long-term
F
r
o
m

d
e
t
a
i
l

t
o

s
u
m
m
a
r
y
CPSC Exception Management
PSProduction Scheduling
ASCPDistribution Planning
GOPGlobal Order Promising
ASCPSupply Chain & Manufacturing Planning
IOInventory Optimization
DPDemand Planning
SCISupply Chain Intelligence
Develop
Market
Sell
Order
Plan
Procure
Make
Fulfill
Service
Maintain
Finance
HR
Projects
All Product,
Customer,
& Supplier
Information
SNONetwork Design
Oracle Advanced Planning
Complete E-Business Planning Solution

8. Copyright © 2006, Oracle. All rights reserved.8
Production Scheduling Integration
Description
Advanced Supply Chain Planning Production Scheduling
• Plan for multiple facilities
• Which plant makes what products
and when
• Pre-builds based on capacity shortages
• Alternate facilities, suppliers and
processes
• Schedule a single facility
• Sequence Production to meet
demands on this facility
• Account for detailed production
constraints and come up with an
executable schedule
Constrained dependent demands,
Independent Demands, Planned
Orders
Detailed Sequence of activities near term
to constrain the medium / long term plan

9. Copyright © 2006, Oracle. All rights reserved.9
Production Scheduling Integration
Description
Scope of ASCP – Planning the entire Supply Chain
Scope of PS – Scheduling a single Plant
DC1
DC2
Customer X
Customer Y
Customer Z
Plant 1
Plant 2
Plant 3
Supplier A
Supplier B
Supplier C

10. Copyright © 2006, Oracle. All rights reserved.10
Production Scheduling Integration
Description – Logical Information Flow
ASCP
Planned Orders
Planned Order Demands
Sales Orders
Forecasts
Production Scheduling
Source ERP
Work Order Reschedules
New Work Orders
Items
Bill of Materials
Routings
Resources
Work Order
Sales Orders
On Hand
.
.
.

11. Copyright © 2006, Oracle. All rights reserved.11
Production Scheduling Integration
Description – Logical Information Flow
ASCP
ERP
Production Scheduling
Work Orders
Planned Orders
New Work Orders Created
Work Order
Reschedules
Firm Work Orders
Planning Time Fence Release Time
Window
Time
Scheduling Horizon
Planning Time Fence
Planning Horizon

12. Copyright © 2006, Oracle. All rights reserved.12
Production Scheduling Integration
Description – Modes of Running PS
Running PS “Standalone”
Running PS with reference to an
ASCP Plan
Schedule work orders only
Schedule work orders and planned
orders
Forecast demands specified via
Demand schedules
Forecast demands come in via the
referenced ASCP plan
Inter-org demands included only
via internal sales orders
Inter-org demands also include
planned order demands from the
ASCP plan
Items to be included in PS
specified via specification of
category sets / categories
Items to be included in PS derived
from the items in the ASCP plan
No Forecast consumption
Forecast consumption performed in
ASCP is retained within PS

13. Copyright © 2006, Oracle. All rights reserved.13
Production Scheduling Integration
Description – System Information Flow
Client PC
Collections
PS
Browser
PS Model Files
Snapshot PS Data
From Planning Server
Oracle Applications
Login
Rescheduled / New
Discrete Jobs / Lot Based
Jobs / OPM Batches
Planning
Data
Repository
Define Schedule
names and Options
Invoke Data Snapshot
Open PS
Workbench
Publish Schedule from PS
(Release Process)
EBS
Source

14. Copyright © 2006, Oracle. All rights reserved.14
Functional / Technical Deep Dive Agenda
•Integration Overview
•Technical Architecture Overview
•Implementation Setup, Considerations, Tips and Tricks
•Customization and Extensibility Options
•Troubleshooting
•Wrap Up/Q&A

15. Copyright © 2006, Oracle. All rights reserved.15
Technical Highlights
•Desktop applications
•Integrated to ODS through collections
•Tightly coupled with EBS web interface
•XML integration to the desktop
•Makes use of temporary tables
•Profile and plan options modify integration

16. Copyright © 2006, Oracle. All rights reserved.16
Overview of the Integration

17. Copyright © 2006, Oracle. All rights reserved.17
Integration Details
Refresh Process Flow
•Environment setup based
on profile and plan options
•ODS Data Extraction
•Data transformation
•Serialization to XML
•XML Transferred to
Desktop
Publish Process Flow
•Publish optimized plan
•XML uploaded
•Data insertion into PDS

18. Copyright © 2006, Oracle. All rights reserved.18
Functional / Technical Deep Dive Agenda
•Integration Overview
•Technical Architecture Overview
•Implementation Setup, Considerations, Tips and Tricks
•Customization and Extensibility Options
•Troubleshooting
•Wrap Up/Q&A

19. Copyright © 2006, Oracle. All rights reserved.19
Functional / Technical Deep Dive Agenda
•Integration Overview
•Technical Architecture Overview
•Implementation Setup, Considerations, Tips and Tricks
•Customization and Extensibility Options
•Troubleshooting
•Wrap Up/Q&A

20. Copyright © 2006, Oracle. All rights reserved.20
Production Scheduling Integration
Dependencies and Interactions
The integration of PS to the E-Business Suite will require
patches on top of 11i.10.CU1 for the following modules
•Work In Process
•Bills of Material
•Oracle Shop floor Management
•Oracle Process Manufacturing
•Oracle ASCP - Engine
•Oracle ASCP - Collections
The README in the SNO and PS ARUs contains
information about the patch numbers and install sequence

21. Copyright © 2006, Oracle. All rights reserved.21
Run MRP Process to create
work orders or manually
create work order in EBS
Automated process
Production Scheduling Integration
Setup and Process
Setup data in Oracle
EBS including Items,
BOM, Routings,
Resources and other
elements required to
create a representative
scheduling model
SETUP PROCESS – Running PS without ASCP
Perform manual
adjustments to the
schedule. Use repair
based solves as
appropriate
Define a Schedule Name and
specify schedule options Approve the
schedule
Assign values to Profile
Options that influence
the creation of the PS
model
Launch the schedule and
open the PS workbench
Review the results of the
scheduling process
Publish the
scheduling results
back to EBS
Run Data Collections
to Collect data into
the Planning Server

22. Copyright © 2006, Oracle. All rights reserved.22
Run ASCP Plan. Release
planned orders from ASCP to
create work orders in EBS
Automated process
Production Scheduling Integration
Setup and Process
Setup data in Oracle
EBS including Items,
BOM, Routings,
Resources and other
elements required to
create a representative
scheduling model
SETUP PROCESS – Running PS with ASCP
Perform manual adjustments
to the schedule. Use repair
based solves as appropriate
Define a Schedule Name and
specify schedule options
(Optionally reference the
ASCP plan to schedule
planned orders)
Approve the schedule
Assign values to Profile
Options that influence
the creation of the PS
model
Launch the schedule and
open the PS workbench
Review the results of the
scheduling process
Publish the scheduling
results back to EBS
(existing work orders and
new work orders based on
the ASCP planned orders)
Run Data Collections
to Collect data into
the Planning Server

23. Copyright © 2006, Oracle. All rights reserved.23
Production Scheduling Integration
Setup – Set Key Profile Options
Profile Option Valid Values Description
MSC: PS/SNO Client
Install Path
Text (Default:
C:\)
The path where the Supply Chain Planning
Production Scheduling (PS) is installed.
PS is installed automatically the first time it
is accessed by the E-Business Suite.
MSO: Enforce
Resource Sequence
Contiguity
Yes, No (Default:
Yes)
If Yes, then activities within EBS
operations are modeled as PS operations
with S@E (Starts at End) constraints. If
No, the S>E (Starts After End) constraints
are used
For a complete listing of all applicable profile options please refer to the Technical TOI

24. Copyright © 2006, Oracle. All rights reserved.24
Production Scheduling Integration
Setup – Set Key Profile Options
Profile Option Valid Values Description
MSC: PS Consistent
Resource Assignment
Yes, No (Default:
No)
Yes – If multiple operations within a routing
have alternate resources defined, PS will
keep the choice of alternate resource
consistent between operations in a routing
when making offloading decisions
No – PS will not attempt to keep the choice
of alternate resource consistent across
operations in a routing
For a complete listing of all applicable profile options please refer to the Technical TOI

25. Copyright © 2006, Oracle. All rights reserved.25
Production Scheduling Integration
Description - Responsibility
A New Responsibility “Production Scheduler” is
available to access the PS application

26. Copyright © 2006, Oracle. All rights reserved.26
Production Scheduling Integration
Description – Menu Functions
Access the PS Workbench
Define Options for a PS
Schedule
Define a PS Schedule
Name
View the Schedule options in
a “Read Only” mode

27. Copyright © 2006, Oracle. All rights reserved.27
Production Scheduling Integration
Description – Schedule Names
Enter the name and description
for the production schedule
Select to access Schedule
options
Select to create a copy of this
schedule name and all of its
currently defined options

28. Copyright © 2006, Oracle. All rights reserved.28
Production Scheduling Integration
Description – Copy Schedule Options
Specify Name and Description for the
copy being created

29. Copyright © 2006, Oracle. All rights reserved.29
Production Scheduling Integration
Description – Schedule Options - Horizon
The length of the
scheduling horizon
A subset of the scheduling horizon
within which schedule results are
published back (released) to ERP
An offset relative to the system
date that marks the start date of
the schedule
A timestamp that is appended to
the start date of the schedule
Schedule start and end are derived
from the other inputs described

30. Copyright © 2006, Oracle. All rights reserved.30
Production Scheduling Integration
Description – Schedule Options - Scope
Set of categories within the specified
category set determine the set of items
in the PS schedule if no ASCP plan
reference is specified
If no ASCP Plan reference is
specified, demand schedules can
be specified as input to the PS
schedule
Number of days prior to schedule start date
within which to consider sales orders as valid
demands to PS
The ASCP Plan reference for this
PS Schedule
Behavior of the demand time
fence depends on whether ASCP
plan is referenced or not (see
Notes for Details)

31. Copyright © 2006, Oracle. All rights reserved.31
Production Scheduling Integration
Description – Schedule Options – Schedule Parameters
See Notes for details of each
schedule parameter

32. Copyright © 2006, Oracle. All rights reserved.32
Production Scheduling Integration
Description – Schedule Options – Display Parameters
Controls the display in the PS
user interface. Determines how
to create folders for Demands,
Supplies and Work Orders

33. Copyright © 2006, Oracle. All rights reserved.33
Production Scheduling Integration
Description – Schedule Options – Run Optimization
Parameters used to enable Run
Optimization in PS. See PS user
guide for more details on Run
Optimization and related
parameters

34. Production Scheduling Integration
Description - Calendars
One Calendar is created in PS
for every Resource with shifts
associated
The manufacturing Calendar of
the org being scheduled is
created in PS and assigned to 24
hour resources
A “Default” 24*7 calendar is created
always in a PS model

35. Copyright © 2006, Oracle. All rights reserved.35
Production Scheduling Integration
Description - Items
Set of items visible in PS
•If an ASCP plan is referenced when defining a PS
schedule for an Org, the set of items existing in that org
within the ASCP plan determines the set of items
visible in the PS schedule
•If an ASCP plan is not referenced when defining a PS
schedule for an Org, the list of item categories defined
as part of the schedule options determines the set of
items visible in the PS schedule

36. Copyright © 2006, Oracle. All rights reserved.36
Production Scheduling Integration
Description- Items
•Item Types in PS
–All items are marked as “Saleable” in PS
–Items with a valid manufacturing process as marked as “Manufactured”
–All other items are marked as “Purchased”
•Min and Max Levels in PS
–All items are represented with a min level of 0 and a maximum level of
10000. These represent inventory level constraints that the PS solver will
not violate
•On hand inventory for the item appears as a “Start Level” in PS
•The “precision” for the item is obtained from the global setting made in
the schedule options screen
–It represents the number of significant digits to the right of the decimal
for supplies and demands for this item
•Storage space and costs are not modeled as part of the standard
integration

37. Copyright © 2006, Oracle. All rights reserved.37
Production Scheduling Integration
Description – Safety Stocks
Without ASCP Plan Reference
A) Safety Stocks defined as time varying levels in Oracle Inventory are
supported
B) Safety stocks defined as MRP Planned % are not supported
With ASCP Plan Reference
C) Safety stock levels as calculated in the referenced ASCP plan are used
as is in PS which implies that both A) and B) above are supported

38. Copyright © 2006, Oracle. All rights reserved.38
Production Scheduling Integration
Description – Resources
Resource Units and Resource Instances
•Resources with 1 available unit are represented as “Single
Capacity” resources in PS
•Resources with more than 1 available unit that are NOT scheduled
to the instance level are represented as “Multi Capacity” resources
in PS
•Resources with more than 1 available unit that are scheduled to the
instance level are represented by modeling each instance of the
resource as a separate single capacity resource in PS

39. Copyright © 2006, Oracle. All rights reserved.39
Production Scheduling Integration
Description – Resources
Dynamic Capacity
•Shift specific capacity units and capacity changes modeled
using simulation sets are represented as dynamic capacity in
PS

40. Copyright © 2006, Oracle. All rights reserved.40
Production Scheduling Integration
Description – Resources
•Offload Threshold %
–A global value input in the Schedule options
•Pre-build Target (for Resource Offloading)
–A global value input in the Schedule options
•Relax Calendar and Capacity Constraints
–If a bottleneck resource group is specified by the user in the schedule
options, those resource not belonging to the bottleneck resource group will
have the checkbox “Relax Calendar and Capacity Constraints” checked
•Calendar (Availability)
–If a 24 resource, the org manufacturing calendar
–If a resources with shifts defined a unique calendar is created for this
resource with availability represented using specified shift timings
•Fixed Time Fence
–A global value input in the Schedule options which applies to all resources

41. Copyright © 2006, Oracle. All rights reserved.41
Production Scheduling Integration
Description – BOM / Routing / Operations
An operation in PS refers to an “activity” in EBS
Item FG1
10
10 20
20 10 20
EBS Representation
Routing
Operation
Activity
Item FG1
10:10 10:20 20:10 20:20
Routing
Operation
PS Representation

42. Copyright © 2006, Oracle. All rights reserved.42
Production Scheduling Integration
Description – BOM / Routing / Operations
A Routing in PS represents the combination of a BOM and a
Routing in EBS
EBS Representation PS Representation
Item FG1BOM
10 20Operation
Components
Item C1
Item C2
Item C3
Item FG1Routing
10 20Operation
Activities 10 20 10 20
MCH1 ASBLR1 MCH2ASBLR2
Item FG1Routing
10:10 10:20 20:10 20:20Operation
ResourcesMCH1ASBLR1 MCH2ASBLR2
Components
Item C1
Item C2
Item C3
Resources

43. Copyright © 2006, Oracle. All rights reserved.43
Production Scheduling Integration
Description – BOM / Routing / Operations
•OSFM Network Routings – The Item Routing in PS will only
represent the “primary” path in the network
–The item routing is only used to create “new orders” in PS
–If work orders refer to operations on the alternate path, a
separate routing will be created for them
EBS Representation of the
Item’s Routing
PS Representation of the
Item’s Routing
10
20
30
40
50
60
P
P
P
A A
A
10
20 40
60
P
P
P
P AOperation on the Primary pathOperation on the Alternate path

44. Copyright © 2006, Oracle. All rights reserved.44
Production Scheduling Integration
Description – BOM / Routing / Operations
•OPM Complex Routings – The Item Routing in PS will
represent OPM complex routing relationships
–Transfer Percents between operations influence step quantities
which in turn determine resource and component usages
–Standard / Max Delays between operations create various types
of Min/Max separation constraints in PS
EBS Representation of the
Item’s Routing
PS Representation of the
Item’s Routing
10
20
30
40
50
60
20%
50% 60%
80%
100%
100%
50%
70
40%
10
20
30
40
50
60
70
EBS Adjusts BOM / BOR Quantities for Work Orders

45. Copyright © 2006, Oracle. All rights reserved.45
Production Scheduling Integration
Description – BOM / Routing / Operations
Routing Step Dependencies in OPM
Min/Max Separation Constraints in PS

46. Copyright © 2006, Oracle. All rights reserved.46
Production Scheduling Integration
Description – BOM / Routing / Operations
•Co-Products defined in OPM and OSFM and by-products defined in WIP and
OPM are represented as part of the item routing in PS
•OSFM Lot Based Jobs with the co-product supply flag set to “Yes” will create
co-product supplies in PS. Those with the flag set to “No” will not
OPM Co Product Definition OSFM Co Product Definition

47. Copyright © 2006, Oracle. All rights reserved.47
Production Scheduling Integration
Description – BOM / Routing / Operations
Alternate BOM / Routings defined in EBS are represented in PS
Substitute components defined on a BOM in EBS are represented as item sets in PS
Primary Routing uses resource CHCFR
Alternate Routing uses resource CHCFR_NEW
Item Set and substitute components under
the Item set

48. Copyright © 2006, Oracle. All rights reserved.48
Production Scheduling Integration
Description – Alternate / Simultaneous Resources
•In EBS an activity can be setup to use one of several possible alternate groupings
of simultaneous resources
•Alternate groupings of resources are represented in PS as
–Resource Sets: If the activity in EBS is setup in a way that allows all possible
combinations of simultaneous resources
–Operation Sets: If the activity in EBS is setup in a way that disallows certain
combinations of simultaneous resources
— Operation sets are not permitted on PS Work Orders and offloading calculations are not
performed the same as Resource Sets
•If simultaneous resources are present, PS needs one resource to be marked as a
“Duration resource” to calculate the durations of operations
–The resource in EBS marked as a “Principal” resource will be the duration
resource in PS

49. Copyright © 2006, Oracle. All rights reserved.49
Production Scheduling Integration
Description – Alternate / Simultaneous Resources
+
Operator-1Line-1
+
Operator-1Line-2
+
Operator-2Line-1
+
Operator-2 Line-2
Resources for operation
“ASSEMBLE WIDGETS”
defined in EBS Representation of operation “ASSEMBLE WIDGETS” in PS
Resource Set

50. Copyright © 2006, Oracle. All rights reserved.50
Production Scheduling Integration
Description – Alternate / Simultaneous Resources
+
Operator-1Line-1
+
Operator-2 Line-2
Resources for operation
“ASSEMBLE WIDGETS”
defined in EBS
Representation of operation “ASSEMBLE WIDGETS” in PS
Operation Set representing
alternate operations

51. Copyright © 2006, Oracle. All rights reserved.51
Production Scheduling Integration
Description – Operation Lot Multiple in PS
•PS schedules instances of an operations (including Work Order Operations)
by breaking up an operation into several lot multiples
•All operations belonging to a single routing are subject to the same lot
multiple
Item FG1Routing
Operation 10
Operation 20
Operation 30
Lot multiple quantity

52. Copyright © 2006, Oracle. All rights reserved.52
Production Scheduling Integration
Description – Operation Lot Multiples in PS
EBS Modeling Construct PS Routing level lot multiple
1. The minimum of all “Charge quantities” for
resources within a routing (OPM Only)
2. The MTQ of the first operation of the routing
3. Fixed Order quantity of the primary item
produced by the routing
4. Fixed Lot multiple of the primary item
produced by the routing
5. Minimum Order quantity of the primary item
produced by the routing
6. Maximum Order quantity of the primary item
produced by the routing
7. Value of 1
It is strongly recommended to use logical or physical
lot multiples in PS due to the large number of
operation instances created as a result.
Lot Multiple really means – when is inventory
transferred to a next step
Defaulting
Order

53. Copyright © 2006, Oracle. All rights reserved.53
Production Scheduling Integration
Description – Changeover Rules (WIP)
Setup Types
WHITE
BLUE
BLACK
Resource Setup Types
Line-1 White
Line-1 Blue
Line-1 Black
Changeover
Times (Hr)
White Blue Black
WHITE 0 2 4
BLUE 5 0 3
BLACK 10 6 0
Item Routing Operation Resource Setup Type
Small White Widgets10 Line-1 WHITE
Large White Widgets10 Line-1 WHITE
Small Blue Widgets 10 Line-1 BLUE
Large Blue Widgets 10 Line-1 BLUE
Small Black Widgets10 Line-1 BLACK
Large Black Widgets10 Line-1 BLACK
Setup TypesResource / Setup Associations Changeovers
Routings
An example of data setup in EBS to represent sequence
dependent changeovers on a Resource called Line-1

54. Copyright © 2006, Oracle. All rights reserved.54
Production Scheduling Integration
Description – Changeover Rules (PS)
Operation Groups
WHITE
BLUE
BLACK
Machine From Operation (Group) From Operation (Group) Duration (Hr)
Line-1 WHITE WHITE 0
Line-1 WHITE BLUE 2
. . . .
Line-1 BLACK WHITE 10
Operation Group Operation Machine
WHITE Make Small White Widgets:10 Line-1
WHITE Make Large White Widgets:10 Line-1
BLUE Make Small Blue Widgets: 10 Line-1
BLUE Make Large Blue Widgets: 10 Line-1
BLACK Make Small Black Widgets: 10 Line-1
BLACK Make Large Black Widgets: 10 Line-1
Operation Groups Operations – Group Association
Changeover Editor
The EBS Data shown in the previous slide will be
represented within the PS model as shown below

55. Copyright © 2006, Oracle. All rights reserved.55
Production Scheduling Integration
Description – Changeover Rules (Process)
Class
WHITE
RED
Resource
PAINT
From
Operation
From Item
Class
To
Operation
From Item
Class
Setup
Time
PAINT WHITE PAINT RED 1 HR
PAINT RED PAINT WHITE 3 HR
ActivitySequence Dependency
Setup Y
Runtime N
Cleanup N
Item Classes Operations Sequence Dependent Setups
Operation - PAINT
Activity Resource Plan Type
Setup PAINT MC 1 Primary
PAINT MC 2 Secondary
Operation – PAINT :: Activity - Setup
Item Operation
Red Paint PAINT
White PaintPAINT
Routings
An example of data setup in EBS (OPM) to represent sequence
dependent changeovers on a PAINT operation that uses PAINT MC1 as a
primary resource and PAINT MC2 as an alternate resource

56. Copyright © 2006, Oracle. All rights reserved.56
Production Scheduling Integration
Description – Changeover Rules (PS)
Operation Groups
PAINT : WHITE
PAINT : RED
Machine From Operation (Group) From Operation (Group) Duration (Hr)
PAINT MC 1 PAINT : WHITE PAINT : RED 1
PAINT MC 1 PAINT : RED PAINT : WHITE 3
PAINT MC 2 PAINT : WHITE PAINT : RED 1
PAINT MC 2 PAINT : RED PAINT : WHITE 3
Operation Group Operation
PAINT : WHITE PAINT : White Paint
PAINT : RED PAINT : Red Paint
Operation Groups Operations – Group Association
Changeover Editor
A generic operation “PAINT” defined in OPM that is used to make two items White Paint and Red Paint
gets represented in PS as two distinct operations PAINT: White Paint and PAINT: Red Paint
Combination of “Operation” and “Item Class”
The EBS Data shown in the previous slide will be
represented within the PS model as shown below

57. Copyright © 2006, Oracle. All rights reserved.57
Production Scheduling Integration
Description – Work Orders
•A work order in PS is used to represent
–Work orders in Oracle ERP
—Discrete Jobs
—Lot Based Jobs
—OPM Batches
–Planned orders from an ASCP plan
•A work order refers to a routing. The routing is either an item
routing or a routing specific to that work order
–If all operations in the work order and their resource and material
associations match an existing item routing, then the item routing is
used for the work order
–If a match is not made, a work order specific routing is created and
used

58. Copyright © 2006, Oracle. All rights reserved.58
Production Scheduling Integration
Description – Work Orders
Work Orders from EBS
Planned orders from ASCP
For EBS Work Orders:
• Requested Completion Date ELSE
• Planned Completion Date
•For ASCP Planned Orders
• Suggested Due Date on the Supply in ASCP
Routing used by the work
order and the quantity

59. Copyright © 2006, Oracle. All rights reserved.59
Production Scheduling Integration
Description – Work Order Units of Effort
Controlled through
Schedule options
Item FG1Routing
Operation 10
Operation 20
Operation 30
Item FG1Routing
Operation 10
Operation 20
Operation 30
Item FG1Routing
Operation 10
Operation 20
Operation 30
Item FG1Routing
Operation 10
Operation 20
Operation 30
If MTQ is
specified this
flag appears
checked
If no MTQ is
specified this
flag appears
unchecked
SCHEDULE
PARMETERS
ROUTING
PROPERTIES
Scheduling behavior with flag checked
Scheduling behavior with flag unchecked

60. Copyright © 2006, Oracle. All rights reserved.60
Production Scheduling Integration
Description – Work Orders
•OSFM Work Orders containing operations not on the primary path
will always have a unique routing created for them since the Item
routing in PS only contains the primary path
•OSFM Work orders with
–Co Product Supply flag set to YES – Will refer to a PS routing that has
co-products attached
–Co-Product Supply flag set to NO – Will refer to a PS routing that does
not have co-products attached
•Upon release, an OSFM work order start quantity will be set to the
sum of quantities of all products and co-products produced by that
work order

61. Copyright © 2006, Oracle. All rights reserved.61
Production Scheduling Integration
Description – Purchase / Transfer Supplies
The role of PS is
•To constrain work order start dates based on availability of raw
materials within the purchasing lead time
The role of PS is not
•To be the source of truth for purchase order reschedules
•To be the avenue for releasing new purchase orders
•To consider the impacts of finite supplier capacity outside
purchasing lead time

62. Copyright © 2006, Oracle. All rights reserved.62
Production Scheduling Integration
Description – Purchase / Transfer Supplies
Purchasing Lead Time = { ITEM Pre-Processing Time + ITEM Processing Time +
ITEM Post Processing Time }
On Hand
Existing Purchase
Orders within Lead
Time constrain the
start time of the work
orders they feed
Supply of the purchased item is unconstrained
outside of the purchasing lead time. PS will generate
new supply as needed against the “Default Supplier”
(not releasable back to ERP)
Purchase orders (even if
present in ERP) are not
brought into PS outside
of Lead Time

63. Copyright © 2006, Oracle. All rights reserved.63
Production Scheduling Integration
Description – Purchase / Transfer Supplies
The earliest date is set
equal to the due date of the
purchase order to prevent
PS from rescheduling it to
an earlier date
The “Default Supplier” is
the one used to create new
supplies in PS (if required)
outside of the purchasing
lead time The PO and PO Shipments

64. Copyright © 2006, Oracle. All rights reserved.64
Production Scheduling Integration
Description – Demands
Without ASCP Plan Reference
With ASCP Plan Reference
Schedule
Start
Schedule
End
Demand Time Fence *
Sales Orders From
Collected Data
Unconsumed Forecasts From Demand Schedule
Schedule
Start
Schedule
End
Demand Time Fence *
Sales Orders From
Collected Data
Consumed Forecasts From ASCP Plan
Sales Orders From ASCP Plan
* From Schedule Options
No Forecast Consumption in PS
No Forecast Consumption in PS

65. Copyright © 2006, Oracle. All rights reserved.65
Production Scheduling Integration
Description – Demands
Hot Orders
1
2
3
4
5
Committed
1
2
3
4
5
Uncommitted
1
2
3
4
5
Sales Orders
1
.
.
.
n
Transfer Orders
Forecasts
Demands and their
Priorities in EBS / ASCP
Order Class / Demand Priority in PS
These priorities
reserved for manual
overrides in PS
Sales Order Priorities 1  n in
EBS / ASCP map to demand
priorities Committed::1
through Uncommitted::5 in PS
*Negative Inventory Demands map
to Committed P1

66. Copyright © 2006, Oracle. All rights reserved.66
Production Scheduling Integration
Description – Features Not Available in PS Integration v1
•Scheduling of maintenance work orders (Enterprise Asset Management - EAM)
•Scheduling “Batchable” resources
•Scheduling orders in a Project/Task environment
•Routings and BOMs specific
–Routing Assigned units > 1 for for a resource that is scheduled to the instance level
and has more than 1 instance defined
–Different MTQ / Charge quantity for each operation in a routing
–Support for lot basis activities outside of the realm of existing work orders
–Support for lot basis components outside of the realm of existing work orders
–Date effective Bill of Materials / Routings
–Shelf life constraints / Min-Max separation constraints across routings
–Modeling of a Resource Required to perform a changeover activity
–3 level construct: Routing  Operation  Activity

67. Copyright © 2006, Oracle. All rights reserved.67
Production Scheduling Integration
Description – Features Not Available in PS Integration v1
Display
•Filter controls in the Manufacturing Scheduler (WPS) Job Workbench do not
have exact parallels in PS
•Display of “shared” capacity between departments in Resource Hours
display
•Graphical Display of progress % within the operation bar in the Gantt Chart
•Configurable display of bar Text in the Resource view
•User defined item / resource folders in the display structure
Release
•Ability to select only certain orders for release
•Ability to release net new production from PS
Suppliers
•Supplier capacity and Item/Supplier specific lead times
•Ability to release Purchase order reschedules
•Modeling of receiving calendars

68. Copyright © 2006, Oracle. All rights reserved.68
Production Scheduling Integration
Description – Features Not Available in PS Integration Release 1
Work Orders
•Ability to firm an order in a way that causes overload
•“Priority” at the work order level
•Ability to schedule work orders only (no end demands)
•Support offloading decisions for alternate operations in work orders
Demands and Supplies
•Non uniform priority spread for forecasts and dependent demands coming
into PS
•Feeding a Supply Schedule into PS
•Feeding a PS schedule back to ASCP as a supply schedule
Scope
•Specifying a schedule start time for the PS schedule based on Collections
Start Time
•Support for multiple orgs in a single PS schedule
•Support for scheduling a single department within an org

69. Copyright © 2006, Oracle. All rights reserved.69
Production Scheduling Integration
Description – Features Not Available in PS Integration v1
PS Functionality not supported via EBS Integration 11i.10 v1
•Enabling via standard integration the Theory of Constraints (TOC)
functionality in PS
•Setting Run Optimization related flags on the resource and Min / Max
Run Lengths
•Status of last operation run on a resource
•Shared Storage constraints between items
•Pre-pegging of demands to specific work orders

70. Copyright © 2006, Oracle. All rights reserved.70
Tips and Tricks / Lessons Learned
• Work Order Units of Effort
•Ensure logical or physical Lot Multiples are setup on PS
operations via the mechanisms outlined in this presentation
to avoid an unnecessary amount of operations being
scheduled
–Potential performance problem.
•Procured Item Lead Time
•Sum of Pre-processing, Processing and Post-processing
lead times on an item needs to be populated.

71. Copyright © 2006, Oracle. All rights reserved.71
Work Orders with Non-Standard Routings
•If any of the following conditions exist, PS will
create what is referred to as an auto-
generated routing
–A given work order routing has missing or
additional Crews, Machines, Tools, Items
–A given work order routing has missing or
additional or operations when compared to the
standard PS routing
–Work Orders contain Operation Sets
•If these situations present themselves, you will
see an “Auto-Generated” routing in the PS
model workspace

72. Copyright © 2006, Oracle. All rights reserved.72
Offloading Calculation
Machine 1
Machine 2
Machine 3
Demand Due Date
If the utilization of the resource is > the Resource’s Offload
Threshold, it will offload to Machine 2.
Utilization is calculated from start of the horizon to the
end of the first operation required to meet a given
demand. The process repeats itself for every demand.
1-Jan-06 7-Jan-06
2 3 4 5 6
Op 20
Op 10

73. Copyright © 2006, Oracle. All rights reserved.73
Offloading Calculation
What is the problem with this?
•Since the offloading calculation is done from the start of the horizon, it may
be very difficult to effectively get the solve to offload
AND
May experience long manufacturing makespan (I.e. Prebuild) instead of
effectively offloading to alternates close to the demand due date.
Utilization does not exceed threshold!
Operations Pre-built on M1, buts lots of
Idle time on M2

74. Copyright © 2006, Oracle. All rights reserved.74
Offloading Calculation
How do we correct this?
•Use the “Prebuild Target” on the Resource.
•Load is spread on 2 resources and scheduled JIT

75. Copyright © 2006, Oracle. All rights reserved.75
Consistent Resource Assignment
Routing property which enforces consistent assignment when a resource appears
multiple times in a sets across different operations (Set up with via Profile Options)
•E.g. Multiple passes on a print press

76. Copyright © 2006, Oracle. All rights reserved.
Firming Work Orders

77. Copyright © 2006, Oracle. All rights reserved.77
Firming Work Orders
•A Firm Work Order will be represented within PS with each of it’s
underlying operations having:
–Earliest Start = Scheduled Start
–Latest End = Scheduled End
–Allow Offloading = No
•A Firm Planned Order will be represented within PS with its last operation
as Firm End (i.e. the last operation will have Latest End = Scheduled End
)

78. Copyright © 2006, Oracle. All rights reserved.78
Firming Work Orders
All Work Order Operations which fall within the Fixed Time
fence will be set to “Firm” by the integration

79. Copyright © 2006, Oracle. All rights reserved.79
Firming Work Orders
A Firm “Activity” (Gantt chart based firming in ASCP) will be represented within PS as an
operation that has:
Case 1: Firm All
Earliest Start = Scheduled Start
Latest End = Scheduled End
Allow Offloading = No
Case 2: Firm Start
Earliest Start = Scheduled Start
Case 3: Firm End
Latest End = Scheduled End
Case 4: Firm Resource
Allow Offloading = No
Case 5: Firm Start and Resource
Earliest Start = Scheduled Start
Allow Offloading = No
Case 6: Firm End and Resource
Latest End = Scheduled End
Allow Offloading = No
Case 7: Firm Start and End
Earliest Start = Scheduled Start
Latest End = Scheduled End

80. Copyright © 2006, Oracle. All rights reserved.80
Production Scheduling Integration
Process – Approve Schedule
You must approve the schedule
prior to publishing it back to the
source ERP

81. Copyright © 2006, Oracle. All rights reserved.81
Production Scheduling Integration
Process – Publish Schedule to ERP
Publish the schedule. Select the Publishing
Profile of “Release Schedule” to invoke the
release program that pushes the work order
reschedules and new work orders back to
source ERP

82. Copyright © 2006, Oracle. All rights reserved.82
Functional / Technical Deep Dive Agenda
•Integration Overview
•Technical Architecture Overview
•Implementation Setup, Considerations, Tips and Tricks
•Customization and Extensibility Options
•Troubleshooting
•Wrap Up/Q&A

83. Copyright © 2006, Oracle. All rights reserved.83
Customization and Extensibility Options
•Options are limited for version one
•Basic customization through profile options
•Advanced customization through manipulation of XML
files
–Ability to directly modify planning data
–Use TCL scripts and/or XSLT
–Runs on user’s desktop
•Manipulation of SQL extracts from ODS is not
supported
–Changes will be overwritten by updates

84. Copyright © 2006, Oracle. All rights reserved.84
Customization Using Profile Options
•Technical TOI has complete list of options

85. Copyright © 2006, Oracle. All rights reserved.85
Advanced Customization
•Need to modify the PS/SNO startup scripts that are downloaded to
user desktop each execution
–Copy existing scripts on server and modify to callout to custom
scripts
–The startup scripts are located on the server under $
{OA_HTML} directory
•TCL and XSLT interpreter are automatically installed with PS and
SNO to user’s desktop. They are accessible through the PS/SNO
connector executables.
•Profile options:
–MSC: PS Run Connector Script / MSC: SNO Run Connector
Script
–Can be defined per user
–Defaults are: runPsConnector.cmd / runSnoConnector.cmd

86. Copyright © 2006, Oracle. All rights reserved.86
Advanced Customization cont’d
•runPsConnector.cmd context:
@echo off
rem $Header: runPsConnector.cmd … $
set INSTALL_ROOT=%1
set DATA_STORE=%2
set PLAN_ID=%3
call \
%INSTALL_ROOT%\scp\8.11.2\common\start\run_PsConnector.bat \
%DATA_STORE%/%PLAN_ID%/psConnectorRefresh.tcl

87. Copyright © 2006, Oracle. All rights reserved.87
Functional / Technical Deep Dive Agenda
•Integration Overview
•Technical Architecture Overview
•Implementation Setup, Considerations, Tips and Tricks
•Customization and Extensibility Options
•Troubleshooting
•Wrap Up/Q&A

88. Copyright © 2006, Oracle. All rights reserved.88
Debug Mode
•Set the profile option MSC:SCP Debug Mode to YES
•Debug information will be logged in the request id log
files
–Includes details on SQL statement timings

89. Copyright © 2006, Oracle. All rights reserved.89
Data models not published/refreshed
successfully
•Verify correct ARU’s are installed from readme
•Verify profile option: MSC:PS/SNO Data Store Path
•Check log files for the request id
•Check local files on user’s desktop
–Get Plan ID from request id log file
–Navigate to PS/SNO data store on the client
—MSC:PS/SNO Client Install Path
–Check connector.err
Example:
Plan id is
1763,
MSC:PS/SNO Client Install Path =
d:/
Log
files will be in:
D:/scp/data_store/1763

90. Copyright © 2006, Oracle. All rights reserved.90
Planning Applications not Available on Desktop
•Verify profile option MSC:SCP Client Install Path
•Verify that sufficient disk space is available on local
hard drive
–For version one, the user is not notified if there is not
sufficient disk space to install SNO or PS

91. Copyright © 2006, Oracle. All rights reserved.91
Running SNO/PS Stand Alone
•Allows for working on a model off-line
•Easier to work with when debugging models
•Start scripts to launch applications are located in
–<SCP Client Install Path>/scp/8.11.2/common/start
Start-up commands for SNO:
run_sno_sno.bat: launches SNO
run_sno_connector.bat: runs the SNO connector manually
Start-up command for PS:
run_PS.bat: Launches PS
run_PsConnector.bat: Runs the SNO connector manually

92. Copyright © 2006, Oracle. All rights reserved.
Wrap Up/ Q&A

93. Copyright © 2006, Oracle. All rights reserved.
Thank You
Thank You