My Oracle Support Banner

WIP Scheduling : Rounding of Resource Usage is calculating unexpected WIP Job duration (Doc ID 1625228.1)

Last updated on FEBRUARY 14, 2019

Applies to:

Oracle Work in Process - Version 12.1.3 and later
Information in this document applies to any platform.


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:
      UOM:sec (Second)

- 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

     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

 Start Date:01/27/2014 00:00:00
 Completion date:01/27/2014 00:33:00 (1980 sec)


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.