Previous  Next          Contents  Index  Navigation  Glossary  Library

Uses of Dynamic Lead Time Offsetting

Oracle Manufacturing functions whose processing performance is most critical use dynamic lead time offsetting while other functions that schedule exact operation and resource start and end times use detailed scheduling.

For example, Master Scheduling/MRP generates MRP plans as quickly as possible, so it schedules planned order start dates using dynamic lead time offsetting. Work in Process, however, uses detailed scheduling to schedule jobs since it schedules resource usages in departments with exact start date, end dates and times, not scheduling a resource when one is not available.

Results from detailed scheduling and dynamic lead time offsetting may differ. The more resource availability exceptions and capacity modifications from the workday calendar you have, the more detailed scheduling results differ from dynamic lead time offsetting results. Assigning preprocessing lead time to manufactured items can also produce different results; detailed scheduling does not use lead times in its calculations while dynamic lead time offsetting does.

Material Requirement Dates

Master Scheduling/MRP computes component requirement dates for planned orders using the offset percentage for the operation where each component is used. Master Scheduling/MRP multiplies the operation offset percentage times the planned order lead time to get offset days, and then finds the workday that is the number of days past the planned order start date.

Resource Load by Department / Date for Planned Orders

Oracle Capacity offsets resource requirement dates the same way that Master Scheduling/MRP offsets component requirement dates, except it uses resource offset percentages. Oracle Capacity computes resource offset days as the planned order lead time multiplied by the resource offset percentage. Oracle Capacity then finds the workday that is the number of days past the work order start date to find the resource start date and time.

Component Requirement Dates for ATP Checks

Oracle Inventory lets you check component available to promise (ATP) for assemble to order (ATO) and Pick to Order (PTO) items. Oracle Bills of Material allows you to specify the components of an ATO or PTO product that must be promised using ATP. When you check ATP for a product having such components, Inventory determines the requirement date for components by first computing the manufacturing lead time for that product using the dynamic lead time calculation and then finding the date that is the number of workdays before the requested ship date. Inventory assumes that all ATO product components are required at the beginning of the ATO job.

See Also

Material Requirements Planning

Overview of Capacity Planning

Overview of On-hand and Availability


         Previous  Next          Contents  Index  Navigation  Glossary  Library