Calculating Dates in ASCP

Calculating Planned Order Demand Due Date
The planning process takes into account the actual requirement date and the lead-times for
calculating the planned order demand due dates. This provides more accurate lead-time offsets in
aggregate planning time buckets.
It allows you to plan at aggregate time bucket levels like periods and weeks. It provides you easy
identification of aggregate supply/demand mismatches and helps you make strategic decisions
related to equipment and labor acquisition, sourcing etc. without generating needless details.
The planning process calculates the planned order demand due dates for dependent demands
based on the actual requirement date with respect to lead-time. It saves the calculated
requirement date based on the lead-time value for subsequent calculation.
Then, it aligns all dates to the ends of time buckets. You can get more accurate dates by first
performing dependent demand explosion followed by alignment.
Example
Consider an organization with an assembly A, which has components B and C.
Assembly
The quantity per assembly for components B and C is 1.
The lead-time for assembly A = 4

The lead-time for sub-assembly B = 3
The lead-time for component C = 4
The organization follows a weekly planning bucket and working days are Monday through
Friday.
An order quantity of 1 is placed for item A on Friday February 28.
The planning process generates the following planned order demands:
Planned Order Demand Due Date Calculation
Explanation:
 Calculated requirement date for B
= Demand Due Date for A - LT
= February 28 - 4 days
= February 24 (Monday)
 Demand Due Date for B
= Calculated requirement date for B after bucketing into planning bucket
= February 28 (weekly demands are bucketed into Friday)
 Calculated requirement date for C
= Calculated requirement for B - LT

= February 24 - 4 days
= February 18 (Monday)
 Demand Due Date for C
= Calculated requirement date for C after bucketing into planning bucket
= February 21 (weekly demands are bucketed into Friday)
Date Calculations for Manufactured Supplies
The planning process uses work days from the manufacturing calendar to calculate dates for
manufactured supplies, unless otherwise indicated.
Need By Date: The date that the material should ship or be in inventory for a next-higher level
assembly. The earliest demand due date that the supply is pegged to.
Suggested Due Date: In an Unconstrained or Constrained - Enforce demand due dates plan this is
the same as Need By Date. In a Constrained - Enforce capacity constraints plan this is the
scheduled availability date of the supply. If the supply is constrained, the planning process
forward schedules from the constraint.
Suggested Dock Date: Demand Due Date. Dock Date is the day by which all shop floor
operations are complete.
Suggested Ship Date: Blank
Suggested Start Date: Suggested Due Date - Production duration. The day that you should begin
shop floor operations.
Lead-time offsetting begins only on a workday of the workday calendar. For example:
 The workday calendar shows the week of 15 January as 5 workdays (Monday 15 January
to Friday 19 January) followed by 2 non-workdays (Saturday 20 January to Sunday 21
January).
 The planning process creates a planned order against item A for quantity 45 with
suggested ship date 20 January. Processing lead-time for item A is 5 days.
 Since 20 January is a non-workday, the planning process moves to 19 January to begin
lead-time offsetting and calculates Suggested Start Date 12 January.
Sunday 21 January (non-workday)
Monday 20 January (non-workday) > Suggested Ship Date
Friday 19 January > Beginning of lead-time offsetting

Thursday 18 January > -1
Wednesday 17 January > -2
Tuesday 16 January > -3
Monday 15-January > -4
Sunday 14 January (non-workday)
Saturday 13 January (non-workday)
Friday 12 January > -5 and Suggested Start Date
Thursday 11 January
Production Duration:
 Unconstrained plans: Fixed + (Variable * Order quantity)

 Constrained plans: Calculated resource and material duration. If the item does not have a
routing, the planning process uses the unconstrained calculation.
Suggested Order Date: Planned order Start Date - Preprocessing. The date on which you should
place the order. For a scheduled receipt, this field displays the date the date that it was created.
This diagram shows dates calculated for manufacturing supplies.
Dates Calculated for Manufacturing Supplies
Date Calculations for Manufactured Supply Components
The planning process calculates the component due dates of a manufacturing supply order
according to your setting of the plan option Material Scheduling Method.
For value Order Start Date, the component due date is the supply Start Date.
For value Operation Start Date:

 Unconstrained plans: The planning process determines the operation that uses the
component. It begins with the supply Start Date and increases it by lead-time % of that
operation.
 Constrained plans: Operation Start Date for the operation which uses it
Purchased Supply Lead-times and Approved Supplier Lists
If the item of the purchased supply has an Approved Supplier List, the planning process uses:
 Uses its Processing Lead-time value instead of the item attribute Processing lead-time
 Adjusts Dock Date to conform to its Delivery Calendar value
You can view Approved Supplier List planning attributes among the items information.
Date Calculations for Purchased Supplies
The planning process uses work days from the receiving organization calendar to calculate dates
for purchased supplies, unless otherwise indicated.
Need by Date: Date that the material is required to satisfy demand.
Suggested Due Date:
 Unconstrained plans: Need by Date

 Constrained plans: The available date of the supply by forward scheduling
Suggested Dock Date:
 Unconstrained plans: Due Date - Postprocessing

 Constrained plans: The latest delivery day for which the capacity is available and the
material is needed
 If the purchased supply item has an Approved Supplier List delivery calendar: The
planning process verifies that the Suggested Dock Date is a work day on the delivery
calendar. If it is not, the planning solver changes Suggested Due Date to the next earliest
working day of the delivery calendar.
Suggested Ship Date: Dock Date - Production duration
Production Duration:
 If the purchased supply item has an Approved Supplier List Supplier Processing lead-
time: Approved Supplier List Supplier Processing lead-time
 If the purchased supply item does not have an Approved Supplier List Supplier
Processing lead-time: Item attribute Processing
Suggested Start Date: Ship Date

Suggested Order Date: Start Date - Preprocessing. For a scheduled receipt, this field displays the
date the date that it was created. For collected information, purchase order create date. The
planning process calculates this date using the organization manufacturing calendar.
This diagram shows the calculations for purchased supplies.
Calculated Dates for Purchased Supplies
Date Calculations for Transfer Supplies
The planning process uses work days from the receiving organization calendar and shipping
organization calendar to calculate dates for transfer supplies.
Need By Date (receiving organization calendar): Date material is required to satisfy demand.
Demand Due Date (receiving organization calendar):
 Unconstrained plans: Need By Date

 Constrained plans: Forward scheduling from the constraint.
Suggested Dock Date (receiving organization calendar): Due Date - Postprocessing
Suggested Ship Date (shipping organization calendar):
 Unconstrained plans: Dock Date - Intransit Time

 Constrained plans: Dock Date - Intransit Time, considering constrained transportation
duration. The planning process considers transportation constraint maximum transfer
quantity per day
Intransit Time is calendar days.
Suggested Start Date (shipping organization calendar):
 Unconstrained plans: Ship Date - Processing

 Constrained plans: Ship Date. The planning process does not consider a build time
because the supply may be on-hand.
Suggested Order Date (receiving organization calendar):
 Unconstrained plans: Planned order Start Date - Preprocessing

 Constrained plans: Ship date in the receiving organization, if the shipping organization is
a planned organization. The constrained plan uses material and resource constraints in the
shipping organization.
For a scheduled receipt, this field displays the date the date that it was created.
This diagram shows calculated dates for transfer supplies in an unconstrained plan. The planning
process calculates production duration differently for the source organization and the destination
organizations; therefore, the dates in your plan may not line up as accurately as they appear in
this diagram. If material is scheduled inside of these lead-times, planners can determine what
action to take on the compression messages.
Calculated Dates for Transfer Supplies, Unconstrained Plan
This diagram shows that, in constrained plans, Need By Date and Demand Due Date in the
shipping organization should be the same as planned order Ship Date in the shipping
organization.
Calculated Dates for Transfer Supplies, Constrained Plan

Examples of Lead-time Calculations
Introduction
This topic shows examples of lead-time calculations for unconstrained and constrained plans.
Some examples show the effect of planning time fence control on lead-time calculations.
Constrained - Enforce demand due dates plans violate the planning time fence to meet the
demand due date. Since the lead-time calculations are similar between these and Constrained -
Enforce capacity constraints plans, there are no examples specifically for no specific examples
are provided for Constrained - Enforce demand due dates plans with planning time fence control.
Calendars
The lead-time examples use these three calendars. They refer to dates as days, for example, Day
1 and Day 2, rather than as specific dates such as September 1.
Each calendar covers multiple weeks, each row has seven days. Non-work days have the letters
NW after their day number; non-delivery days have the letters ND after their day number.
This is the organization calendar that organization ORG1, the receiving organization, uses. It
follows a 5 on - 2 off pattern.
Monday Tuesday Wednesday Thursday Friday Saturday Sunday
1 2 3 4 5 6NW 7NW
8 9 10 11 12 13NW 14NW
15 16 17 18 19 20NW 21NW
22 23 24 25 26 27NW 28NW
29 30 31 32 33 34NW 35NW
36 37 38 39 40 41NW 42NW
This is the organization calendar that organization ORG2, the shipping organization, uses. It
follows a 6 on - 1 off pattern.
1 2 3 4 5 6 7NW
8 9 10 11 12 13 14NW
15 16 17 18 19 20 21NW
22 23 24 25 26 27 28NW
29 30 31 32 33 34 35NW
36 37 38 39 40 41 42NW
This is the delivery calendar from the approved supplier list for the supplier that supplies the
purchased component.
1 2ND 3 4ND 5 6 7ND
8 9ND 10 11ND 12 13 14ND
15 16ND 17 18ND 19 20 21ND
22 23ND 24 25ND 26 27 28ND
29 30ND 31 32ND 33 34 35ND
36 37ND 38 39ND 40 41 42ND
Example 1: Manufactured Supply with Purchased Component
This example shows lead-time calculations for Item A manufactured supply using Item B
purchased component both in organization ORG1. Item B is used at the first operation of Item A
and its usage in Item A is 1.
lead-times:
 Item A: Fixed, 3 days; Variable, 0.5 days, Preprocessing, 1 day

 Item B: Processing, 2 days, Preprocessing, 1 day; Postprocessing, 1 day
Sourcing rules:
 Item A in ORG1: Type, Make at; Allocation, 100; Rank, 1

 Item B in ORG1: Type, Buy from; Allocation, 100; Rank, 1
There is a demand for 8 units of Item A due on day 19.

Scenario 1: Unconstrained Plan, No Planning Time Fence Control
These calculations are for an unconstrained plan. The calculations for a constrained plan are
similar, except that they consider detailed resource and material constraints.
See Example 1: Manufactured Supply with Purchased Component in this topic for setup
information.
Scenario 1: Calculations for Item A Supply
Need By Date: Day 19 (Demand Due Date)
Suggested Due Date: Day 19 (Need By Date)
Suggested Start Date: Day 10
 Use ORG1 organization calendar

 Suggested Due Date - ((Fixed + (Variable * Supply quantity)) = Day 19 - (3 days (0.5
days * 8) = Day 19 - 7 days
 Two non-work days: Days 13 and 14
Suggested Order Date: Day 9

 Suggested Start Date - Preprocessing = Day 10 - 1 day
Scenario 1: Calculation for Item B Demand
You use purchased component Item B to manufacture Item A. If you use Item B at Item A's first
operation (Material Scheduling Method of Order Start Date), Demand Due Date: Day 10 (Item A
Suggested Start Date).
Scenario 1: Calculations for Item B Supply
Suggested Dock Date: Day 8

 Suggested Due Date - Postprocessing Time = Day 10 - 1 day = Day 9
 Use ASL delivery calendar for supplier of Item B
 Day 9 is not a delivery work day. Move dock date to next earlier delivery work day.
Suggested Ship Date: Day 4

 Dock Date - Processing = Day 8 - 2 days
 Two non-workdays: Days 6 and 7
Suggested Start Date: Day 4 (Suggested Ship Date)

 Start Date - Preprocessing = Day 4 - 1 day
Scenario 1: Summary
This table summarizes the lead-times for Scenario 1: Unconstrained Plan, No Planning Time
Fence Control.
Suggested Due Suggested Suggested Suggested

Organization Item Order Type
Date Dock Date Start Date Order Date
ORG1 A Demand Day 19 n/a n/a n/a
ORG1 A Planned order Day 19 n/a Day 10 Day 9
ORG1 B Planned order Day 10 n/a n/a n/a

demand
ORG1 B Planned order Day 10 Day 8 Day 4 Day 3
Scenario 2: Unconstrained Plan, Assembly Planning Time Fence Control
information.
Item A, organization ORG1 Planning Time Fence Days: 15
Item A, organization ORG Planning Time Fence Date: Day 19

 Day 1 + Planning Time Fence Days = Day 1 + 15 days
 Four non-work days: Days 6, 7, 13, and 14
The planning engine cannot schedule a planned order until the day after Planning Time Fence
Date.

Suggested Due Date: Day 22
 Need By Date is Day 19

 Planning Time Fence Date is Day 19
 The planning engine cannot schedule planned order until Day 22 (Planning Time Fence
Date + 1) = Day 19 + 1 day
 Supply is due after Demand Due Date; issue shortage and late replenishment exception
messages



 Day 10 is delivery work day


Scenario 2: Summary
This table summarizes the lead-times for Scenario 2: Unconstrained Plan, Assembly Planning
Time Fence Control.


demand
Scenario 3: Constrained - Enforce Capacity Constraints Plan, Assembly

Planning Time Fence Control
Constrained plans perform detailed scheduling which considers resource and material
constraints. These examples assume no constraints and use lead-time offsets; the planning engine
would only do this if Item A has no routing.
information.

days * 8) = Day 19 - 7 days = Day 10
Date + 1) = Day 19 + 1 day

Recalculate Suggested Due Date by forward scheduling from Suggested Dock Date

 Suggested Dock Date + Postprocessing = Day 22 + 1 = Day 23
 Supply is due after Demand Due Date; issue shortage exception message

 Day 19 is delivery work day


Scenario 3: Summary
This table summarizes the lead-times for Scenario 3: Constrained - Enforce Capacity Constraints
Plan, Assembly Planning Time Fence Control.


demand
Example 2: Purchased Component
These examples are the same as the scenarios in Example 1 but purchased component Item B has
a planning time fence.
The scenarios in this example are similar to Scenario 1. In Scenario 1, neither assembly Item A
or purchased component Item B has a planning time fence. In this scenario, assembly Item A
does not have a planning time fence but purchased component Item B has a planning time fence.
Item B, organization ORG1 Planning Time Fence Days: 15
Item B, organization ORG Planning Time Fence Date: Day 19

Date.
Scenario 4: Unconstrained Plan, Purchased Component Planning Time Fence
Control
See Example 2: Purchased Component in this topic for setup information.
See Scenario 1: Unconstrained Plan, No Planning Time Fence Control in this topic for the
calculations of supply for Item A and demand for Item B. Item B has dependent demand due on
Day 10.
 Need By Date is Day 10

Date + 1) = Day 19 + 1 day
 Supply is due after Demand Due Date; issue shortage exception message. Do not
reschedule supply for Item A.

 Day 9 is a delivery work day


Scenario 4: Summary
This table summarizes the lead-times for Scenario 4: Unconstrained Plan, Purchased Component
Planning Time Fence Control.


demand
Scenario 5: Constrained - Enforce Capacity Constraints Plan, Purchased

Component Planning Time Fence Control
See Example 2: Purchased Component in this topic for setup information.
calculations of supply for Item A and demand for Item B. Item B has dependent demand due on
Day 10.

Date + 1) = Day 19 + 1 day
 Day 22 is a delivery work day


Recalculate Suggested Due Date by forward scheduling from Suggested Dock Date

 Suggested Dock Date + Postprocessing = Day 22 + 1= Day 23 + 7 days = Day 10
 Supply is due after Demand Due Date; issue shortage exception message. Reschedule
supply for Item A.
Scenario 5: Recalculations for Item A Supply
Suggested Start Date: Day 23 (Item B Suggested Due Date)

 Suggested Start Date + ((Fixed + (Variable * Supply quantity)) = Day 23 - (3 days + (0.5
days * 8) = Day 23 + 7 days = Day 32
 Supply is due after Demand Due Date; issue shortage exception message.

Scenario 5: Summary
Plan, Purchased Component Planning Time Fence Control.



demand
Example 3: Transfer Component
This example shows lead-time calculations for Item A manufactured supply using Item C
transfer component both in organization ORG1. ORG2 supplies Item C to organization ORG1.
Item C is used at the first operation of Item A and its usage in Item A is 1.
Lead-times:
 Item A in ORG1: Fixed, 3 days; Variable, 0.5 days, Preprocessing, 1 day

 Item C in ORG1: Processing, 2 days, Preprocessing, 1 day; Postprocessing, 1 day
 Item C in ORG2: Fixed, 4 days; Variable, 0.25 days, Preprocessing, 3 days
Sourcing rules:
 Item A in ORG1: Type, Make at; Allocation, 100; Rank, 1

 Item C in ORG1: Type, Transfer from; Allocation, 100; Rank, 1; Intransit Time, 2 days
 Item C in ORG2: Type, Make at; Allocation, 100; Rank, 1
There is a demand for 8 units of Item A due on day 33.
Scenario 6: Unconstrained Plan, No Planning Time Fence Control
These calculations are for an unconstrained plan. The calculations for a constrained plan are
similar, except that they consider detailed resource and material constraints.
See Example 3: Transfer Component in this topic for setup information.
Scenario 6: Calculations for Item A Supply (Make At, Receiving Organization)
 Use ORG1 receiving organization calendar


Scenario 6: Calculation for Item C Demand (Transfer From, Receiving

Organization)
You use purchased component Item C to manufacture Item A. If you use Item C at Item A's first
Scenario 6: Calculations for Item C Supply (Transfer From, Receiving

Organization)

 Suggested Due Date - Postprocessing = Day 24 - 1 day = Day 23

 Suggested Dock Date - Intransit Time [include non-workdays] = Day 23 - 2 days = Day
21
 Use ORG2 shipping organization calendar
 Day 21 is not a work day. Move suggested ship date to next earlier work day.

 Suggested Ship Date - ((Fixed + (Variable * Supply quantity)) [Fixed and Variable from
ORG2]= Day 20 - (4 days (0.25 days * 8) = Day 20 - 6 days
 One non-workday: Day 14

Scenario 6: Calculation for Item C Demand (Make At, Shipping Organization)
You transfer component Item C from ORG2 to ORG1. Demand Due Date: Day 20 (Item A at
ORG1 Suggested Ship Date).
Scenario 6: Calculations for Item C Supply (Make At, Shipping Organization)

 Suggested Due Date - ((Fixed + (Variable * Supply quantity)) = Day 20 - (4 days - (0.25
 One non-work day: Day 14

Scenario 6: Summary
Fence Control.
Suggested Suggested Suggested Suggested Suggested

Due Date Dock Date Ship Date Start Date Order Date
ORG1 A Demand Day 33 n/a n/a n/a n/a
ORG1 A Planned Day 33 n/a n/a Day 24 Day 23

order
ORG1 C Planned Day 24 n/a n/a n/a n/a

order
demand
ORG1 C Planned Day 24 Day 23 Day 20 Day 13 Day 12

order
order
demand
ORG2 C Planned Day 20 n/a n/a Day 13 Day 10

order

for Constrained Plan
In constrained plans, the planning engine does not schedule Start Date to include the estimated
processing time in the shipping org. This avoids pushing out a receiving order when the item
may be on-hand or in process.
Compare this table with the table for unconstrained plans in Scenario 6: Calculations for Item C
Supply (Make At, Shipping Organization) in this topic. Note the differences in the Suggested
Start Date and Suggested Order Date in the receiving organization ORG1.
Fence Control if you used a constrained plan.


order

order
demand

order

order
demand

order
Scenario 7: Unconstrained Plan, Purchased Component Planning Time Fence
Control
This scenario is the same as Scenario 6 but transfer component Item C has a planning time fence
in receiving organization ORG1.
In Scenario 6, neither assembly Item A or transfer component Item C has a planning time fence.
In this scenario, assembly Item A does not have a planning time fence but transfer component
Item C has a planning time fence.
Item C, organization ORG1 Planning Time Fence Days: 20
Item C, organization ORG1 Planning Time Fence Date: Day 26

 Six non-work days: Days 6, 7, 13, 14, 20, and 21
Date.
calculations of supply for Item A and demand for Item C at the receiving organization ORG1.
Item C in the receiving organization has dependent demand due on Day 24.

Organization)

 Need By Date: Day 24
Date + 1) = Day 26 + 1 day
 Supply is due after Demand Due Date; issue shortage exception message. Do not
reschedule any other supply order that requires this supply. However, supplies below this
one in the supply chain bill are delayed as the planning engine plans them.

 Suggested Due Date - Postprocessing = Day 29 - 1 day

24
 Day 24 is a work day

ORG2] = Day 24 - (4 days + (0.25 days * 8) = Day 24 - 6 days

You transfer component Item C from ORG2 to ORG1. Demand Due Date: Day 24 (Item A at
ORG1 Suggested Ship Date).


Scenario 7: Summary
This table summarizes the lead-times for Scenario 7: Unconstrained Plan, Purchased Component
Planning Time Fence Control


order

order
demand

order

order
demand

order
Scenario 8: Constrained - Enforce Capacity Constraints Plan, Transfer

Component Planning Time Fence Control
Constrained plans perform detailed scheduling which considers resource and material
constraints. These examples assume no constraints and use lead-time offsets; the planning engine
would only do this if Item A has no routing.
See Scenario 7: Unconstrained Plan, Purchased Component Planning Time Fence Control in this
topic for the calculation of Planning Time Fence Date for Item C in organization ORG1. Item C
organization ORG1 Planning Time Fence Date: Day 26. The planning engine cannot schedule a
planned order until the day after Planning Time Fence Date.
calculations of supply for Item A and demand for Item C at the receiving organization ORG1.
Item C in the receiving organization has dependent demand due on Day 24.

Organization)
Suggested Due Date: Day 24 (Need by Date)

 Suggested Due Date - Postprocessing = Day 24 - 1 day

21
 Day 21 is not a work day. Move suggested ship date to next earlier work day.

ORG2] = Day 24 - (4 days + (0.25 days * 8) = Day 20 - 6 days = Day 13
Date + 1) = Day 26 + 1 day = Day 27
 Day 27 is a workday in ORG2 shipping organization. It is a non-workday in ORG1
receiving organization.

Scenario 8: Recalculations for Item C Supply (Transfer From, Receiving

Organization)
Recalculate Suggested Ship Date, Suggested Dock Date, and Suggested Due Date by forward
scheduling from Suggested Start Date.

 Suggested Start Date + (Fixed + (Variable * Supply quantity)) [Fixed and Variable from
ORG2] = Day 27 + (4 days + (0.25 days * 8) = Day 27 + 6 days

 Suggested Ship Date + Intransit Time [include non-workdays] = Day 31 + 2 days = Day
33
 Day 33 is a work day.

 Suggested Dock Date + Postprocessing = Day 33 + 1 day
Scenario 8: Recalculation for Item A Supply (Make At, Receiving Organization)
Reschedule Item A supply Suggested Start Date and Suggested Due Date by forward scheduling
from Day 36 (Item C Suggested Due Date in ORG1 receiving organization)
Suggested Start Date: Day 36 (Item C Suggested Due Date)

 Suggested Start Date + ((Fixed + (Variable * Supply quantity)) = Day 36 + (3 days - (0.5
days * 8) = Day 36 + 7 days
Reschedule Item A supply Suggested Order Date by backward scheduling from Day 36 (Item C
Suggested Due Date in ORG1 receiving organization)


You transfer component Item C from ORG2 to ORG1. Demand Due Date: Day 31 (Item C
Suggested Ship Date at ORG1 receiving organization).


Scenario 8: Summary
Plan, Transfer Component Planning Time Fence Control.


order

order
demand

order
order
demand

order
Examples of Planning Time Fence Control
Manufacturing Work Order Scheduling
This topic explains the scheduling of manufacturing work orders. Although the examples use
Oracle Work in Process discrete jobs, they also apply to the scheduling of the primary path of
Oracle Shop Floor Manufacturing lot based jobs and Oracle Process Manufacturing work orders.
This diagram shows a plan with the following features:
 Run on May 5
 Planning time fence control enabled
 The profile options that create a natural time fence based on existing firmed supplies are
disabled.
 Planning Time Fence Date is based on the item attribute (User defined, 4 days) as May 9
and considers working days in the organization. The calendar for this organization has no
non-work days in the organization calendar.
This diagram shows the supplies for this item after the plan run. The supplies have the following
characteristics:
 Job 1: Completely scheduled in the past.

 Job 2: Operations scheduled in the past and completion date of May 6 is earlier than
Planning Time Fence Date.
 Job 3: Three operations scheduled to start prior to Planning Time Fence Date.
 Job 4 and 5: All operations scheduled to start after Planning Time Fence Date.
 Job 6: This job is firmed to complete on May 10.
This diagram shows the state of the collected discrete jobs.
State of Collected Discrete Jobs

Manufacturing Work Order Scheduling in Unconstrained Plans
In unconstrained plans, the planning engine schedules manufacturing work order completion
dates earlier than Planning Time Fence Date, as follows:
 Planned manufacturing orders and non-firm manufacturing work orders: Order Due Date
never scheduled earlier than the item's Planning Time Fence Date.
 Firm manufacturing work orders: Never cancel, reschedule, or change the Order Due
Date.
 Firm planned manufacturing orders: Retained based on the value of plan option
Overwrite. If None or Overwrite Outside Planning Time Fence, retain the order and
consider Order Due Date firm.
This diagram shows the same manufacturing work orders from topic Manufacturing Work Order
Scheduling scheduled in an unconstrained plan. The planning engine schedules Order Due Date
then offsets operations from Order Due Date according to Lead Time % on the manufacturing
work order routing. For operations scheduled prior to the plan run date, the planning engine
compresses them to start and complete on the plan run date:
 Job 1: is rescheduled out to meet its demand on time. Operation 10 would have been
scheduled to start and complete in the past. These dates are both updated to Start on Plan
Run Date. Operation 20 would have been scheduled to start in the past and is now
updated to Start of Plan Run Date
 Job 2: Order Due Date rescheduled out to meet its demand on time. Operation start and
completion dates offset with no compression.
 Job 3: Order Due Date rescheduled out to meet its demand on time. Operation start and
completion dates offset with no compression
 Job 4: Rescheduled in to meet demand on time because Order Due Date is later than the
Planning Tine Fence Date. All operations offset from this date.
 Job 5: Canceled because it has no pegged demand
 Job 6: A firm job, not rescheduled.
This diagram shows the effect of Planning Time Fence Date and firming on discrete job
scheduling in Unconstrained plans.
Discrete Job Scheduling with Planning Time Fence and Firming, Unconstrained Plan
Manufacturing Work Order Scheduling in Constrained - Enforce Capacity

Constraints Plans
For a Constrained - Enforce capacity constraints plan, the planning engine applies the following
planning time fence control rules based on the item's Planning Time Fence Date:
 Planned orders: Do not schedule the first operation to start earlier than Planning Time
Fence Date.
 Non-firm manufacturing work orders: If an order, operation, or resource has a start date
inside the planning time fence, do not rescheduled in. If the job a start date outside of the
planning time fence, only reschedule in up to Planning Time Fence Date.
 Firm manufacturing work orders: Never cancel or reschedule. Do not change the
completion date or reschedule the operations. Calculate firm work order resource
requirements and reduce resource availability by these requirements. Consider the
resource loads for firmed jobs prior to scheduling all other supplies.
 Firm planned manufacturing orders: Retained based on the value of plan option
Overwrite. If None or Overwrite Outside Planning Time Fence, retain the order and
consider Order Due Date firm. Consider the completion date firm; reschedule operations
as required. The operation rescheduling may cause compression or violate Planning Time
Fence Date because the supply is firmed.
In the operation detailed scheduling, the planning engine calculates Earliest Possible Start Date
for each operation. This is never earlier than Planning Time Fence Date, but it may be later.
Scheduling scheduled in an unconstrained plan:
 Jobs 1, 2, and 3: Rescheduled out based on the required demand dates. All of these jobs
had job and operation start dates earlier than Planning Time Fence Date, so their
operations would never be rescheduled in. Job 1 cannot be scheduled in time to meet its
required demand; the planning engine schedules the operations respecting their minimum
lead-time and the first operation cannot start prior to the plan run date. The planning
engine reschedules Jobs 2 and 3 to meet their demands on time. It schedules all
operations to minimize slack between resources except Operation 10 which is scheduled
earlier due to a capacity constraint
 Job 4: Rescheduled in based on its demand due date. Since the planning engine cannot
reschedule Start Date of the first operation earlier than Planning Time Fence Date, it
forward schedules from Planning Time Fence Date.
 Job 5: Canceled because it has no pegged demand and its start date is outside the
planning time fence.
 Job 6: Since the work order is firm, the planning engine never cancels it or reschedules its
completion date. It does not reschedule the operation start and end dates and loads the
resources are based on their requirements on the existing schedule dates.
scheduling in Constrained - Enforce capacity constraints plans.
Discrete Job Scheduling with Planning Time Fence and Firming, Constrained - Enforce
Capacity Constraints Plan
Manufacturing Work Order Scheduling in Constrained - Enforce Demand Due
Dates Plans
Constrained - Enforce demand due dates plans generally follow the same rules as Constrained -
Enforce capacity constraints plans. However, the planning engine may schedule supplies earlier
than Planning Time Fence Date to meet the demand. It may also compress operations.
Scheduling in Constrained - Enforce Capacity Constraints Plans scheduled in a Constrained -
Enforce demand due dates plan. The planning engine schedules all the supplies to meet the due
dates of their pegged demands even if it violates the planning time fence:
 Job 1: Rescheduled out to meet its demand on time. May overload or compress resources.
 Jobs 2 and 3: Rescheduled out to meet their demands on time with no resource overload
or compression
 Job 4: Rescheduled in to meet its demand on time. Operation 10 rescheduled in earlier
than Planning Time Fence Date.
 Job 5: Canceled because it has no pegged demand
 Job 6: Firm, not rescheduled
scheduling in Constrained - Enforce capacity constraints plans.
Discrete Job Scheduling with Planning Time Fence and Firming, Constrained - Enforce
Demand Due Dates Plan
Manufacturing Work Order Scheduling with Firm Operations and Orders
If you want to maintain the detailed schedule dates from a previous plan or that you have set, you
can direct the planning engine to consider operations within the planning time fence as firm.
In constrained plans only, set profile option MSO: Firm Operations/Orders Within Time Fence to
Yes at the site level. The planning engine:
 Consider operations with Start Date earlier than Planning Time Fence Date as firm
 Does not change their schedule dates and loads resources on these schedule dates
 Considers work orders with completion dates earlier then Planning Time Fence Date as
firmed
 Does not reschedule their the job completion dates or cancel them
Scheduling scheduled in a Constrained - Enforce capacity constraints plan. The scheduling in
Constrained - Enforce demand due dates plans is similar:
 Jobs 1 and 2: All operations are earlier than Planning Time Fence Date; do not
reschedule. Do not change Order Due Date. Compress the first two operations of Job 1 ad
the first three operations of Job 2 to occur on the plan run date because their schedule
dates occurred prior to the plan run date.
 Job 3: Operations 10, 20, and 30 have Start Date earlier than Planning Time Fence Date
(May 9); do not reschedule. Operation 40 starts after Planning Time Fence Date; schedule
out based on the required demand date. Reschedule out completion date.
 Job 4: All operations have Start Date after Planning Time Fence Date; reschedule them.
Reschedule the first operation up to Planning Time Fence Date. In a Constrained -
Enforce capacity constraints plan, do not violate the operation start date and forward
schedule the job; the job is late for its demand. In a Constrained - Enforce demand due
dates plan, schedule the operation prior to Planning Time Fence Date to meet the demand
on time.
 Job 5: Cancel because all operations scheduled to start after Planning Time Fence Date
 Job 6: Firm; do not reschedule job completion date and operation schedule dates
This diagram shows the effect of firm operations and orders on discrete job scheduling in
Constrained plans.
Discrete Job Scheduling with Firm Operations and Orders, Constrained Plans
Lead-time Calculation
Oracle Advanced Supply Chain Planning plans orders depending on the type of order as well as
the type of date on the order. The planning engine checks the working and non working days on
specific calendars after taking into consideration the lead-time for each type of order.
Lead-time offsetting begins only on a workday of the workday calendar.
For Make Orders

Refer the following figure for the calendars and lead-times that the planning engine takes into
account while processing make orders.
The processing time for make orders is calculated as follows:
 Routing specified: Manufacturing duration based on resource usages in the routing

 Routings not specified: Fixed + variable lead-time
In unconstrained plans, the value of fixed + variable lead-time is used regardless of

whether routings are specified or not.
For Buy Order
Refer the following figure for the calendars and lead-times that the planning engine takes into
account while processing buy orders.
The processing time for buy orders is calculated as follows:
 Supplier defined: Supplier processing lead-time (assumed to include transit lead-time)

 Supplier not defined: Item processing lead-time
The planning engine calculates the transit lead-time as follows:
 Planned order: The ship method on the sourcing rule that the planning engine selects
 Purchase order: The default ship method between the supplier and the receiving
organization
For Transfer Orders
Refer to the following figure for the calendars and lead-times that the planning engine takes into
account while processing transfer orders.
In case of transfer orders for constrained plans:
 Ship Date = Start Date
The intransit lead-time between the organizations is specific to the carrier used.
For Sales Orders and Forecast
Refer to the following figure for the calendars and lead-times that the planning engine takes into
account while processing sales orders and forecasts.
The intransit lead-time is specific to the carrier used and the location of the customer site.
Planned Order Suggested Dates
You may notice a difference between planned order suggested dates from the planning engine
and the theoretical offset calculation due to rounding. This example illustrates the reason.
Offset formulas:
 Efficiency Factor = Working Time / Total Time Available

 Requirement Duration = Operation Time/Efficiency Factor
Shifts for operation resource:
 1300h - 1710h
 1755h - 1900h
Resource qty/rate: 6 minutes or 10 per hour
Demand: 08-MAY, quantity 12
Constrained - Enforce demand due date plan. Plan options are:
 Aggregation tab, Days buckets = 30

 Constraints tab, Days Resource Constraints = Yes
 Constraints tab, Supplier Capacity Constraints = Yes
Supply, planned order in Planner Workbench:
 Sugg Start Date: 08-MAY 18:16:00

 Sugg Due Date: 08-MAY 23:59:00
 Requirement Duration = 5.62 hours or 343 min
Planned order offset calculations:
 Efficiency Factor = 0.21875 [5.25 hours / 24 hours]

 Requirement Duration = 5.48 hours [72 minutes/0.21875 = 329 minutes]
The difference between the Planner Workbench suggestion and the planned order offset
calculation is 8.4 minutes or 0.14 hours [(5.62 hours - 5.48 hours]. The explanation is:
 Profile option MSO: Floating Point Precision for Planning Bucket Efficiency = 100
 Efficiency Factor = 0.21 [5.25 hours / 24 hours = 0.21875]
 Requirement Duration = 5.62 hours or 343 minutes [72 minutes/0.21 = 342.85 minutes]

Calculating Dates in ASCP

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Calculating Dates in ASCP

Uploaded by

Copyright:

Available Formats

Calculating Planned Order Demand Due Date

Consider an organization with an assembly A, which has components B and C.

The quantity per assembly for components B and C is 1.

The lead-time for assembly A = 4

The lead-time for component C = 4

An order quantity of 1 is placed for item A on Friday February 28.

The planning process generates the following planned order demands:

Planned Order Demand Due Date Calculation

 Calculated requirement date for B

= Demand Due Date for A - LT

 Demand Due Date for B

= Calculated requirement date for B after bucketing into planning bucket

= February 28 (weekly demands are bucketed into Friday)

 Calculated requirement date for C

= Calculated requirement for B - LT

 Demand Due Date for C

= Calculated requirement date for C after bucketing into planning bucket

= February 21 (weekly demands are bucketed into Friday)

Date Calculations for Manufactured Supplies

Suggested Ship Date: Blank

Sunday 21 January (non-workday)

Monday 20 January (non-workday) > Suggested Ship Date

Friday 19 January > Beginning of lead-time offsetting

Wednesday 17 January > -2

Tuesday 16 January > -3

Monday 15-January > -4

Sunday 14 January (non-workday)

Saturday 13 January (non-workday)

Friday 12 January > -5 and Suggested Start Date

 Unconstrained plans: Fixed + (Variable * Order quantity)

This diagram shows dates calculated for manufacturing supplies.

Dates Calculated for Manufacturing Supplies

Date Calculations for Manufactured Supply Components

For value Operation Start Date:

Purchased Supply Lead-times and Approved Supplier Lists

Date Calculations for Purchased Supplies

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

Suggested Due Date:

 Unconstrained plans: Need by Date

Suggested Dock Date:

 Unconstrained plans: Due Date - Postprocessing

Suggested Ship Date: Dock Date - Production duration

Suggested Start Date: Ship Date

This diagram shows the calculations for purchased supplies.

Calculated Dates for Purchased Supplies

Date Calculations for Transfer Supplies

Demand Due Date (receiving organization calendar):

 Unconstrained plans: Need By Date

Suggested Dock Date (receiving organization calendar): Due Date - Postprocessing

Suggested Ship Date (shipping organization calendar):

 Unconstrained plans: Dock Date - Intransit Time

Intransit Time is calendar days.

Suggested Start Date (shipping organization calendar):

 Unconstrained plans: Ship Date - Processing

Suggested Order Date (receiving organization calendar):

 Unconstrained plans: Planned order Start Date - Preprocessing

Calculated Dates for Transfer Supplies, Unconstrained Plan

Calculated Dates for Transfer Supplies, Constrained Plan

Monday Tuesday Wednesday Thursday Friday Saturday Sunday

Monday Tuesday Wednesday Thursday Friday Saturday Sunday

Monday Tuesday Wednesday Thursday Friday Saturday Sunday

1 2ND 3 4ND 5 6 7ND

8 9ND 10 11ND 12 13 14ND