WIP Scheduling : Rounding of Resource Usage is calculating unexpected WIP Job duration
(Doc ID 1625228.1)
Last updated on SEPTEMBER 30, 2024
Applies to:
Oracle Work in Process - Version 12.1.3 and laterInformation in this document applies to any platform.
Goal
You have defined very precise timings for Operation Resource Usage (see below), so why are WIP Jobs not being scheduled as expected?
- Routing Setup
Item: TEST_assembly01
Operation:10 Department:MT_DEP1
Operation Resource:
Seq:10
Resource:RES127
UOM:sec (Second)
Amount:0.5
- Profile Setup
BOM: Time Unit of Measure Class = Time
BOM: Hour UOM = hr
WIP: Round Off Resource Usage to Minutes in Lead Time Calculations = No
- UOM Setup
Class: Time/ Base Unit: Minutes
Second (sec)
1 sec = 0.0166666666 Minutes
Hour(hr)
1 hr = 60 Minutes
With the above settings, you expect that if you create a WIP job for 3840 qty, it should have a duration of 32 minutes. (0.5 Sec * 3840 = 1920 sec)
However in this case you will find that the WIP Job is actually scheduled longer than expected (33 minutes in this case).
WIP job12702
Assembly Item:TEST_assembly01
Quantity:3840
Start Date:01/27/2014 00:00:00
Completion date:01/27/2014 00:33:00 (1980 sec)
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |