My Oracle Support Banner

WIP Scheduling : Resource Usage for Uom Sec Is Calculating Unexpected (Doc ID 2398151.1)

Last updated on MAY 14, 2018

Applies to:

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

Symptoms

Actual Behavior
Discrete jobs are created with following operation resources that use seconds UOM.
However, WIP Scheduling for the resources were unexpected.

Those resources have Usage:75000(sec) and 11400(sec), sum of them is 86400.
86400 seconds equals 1 day / 24 hours (86400/60/60).
However as the result of WIP Scheduling, when entering Completion date as 06/FEB/2018 23:59:00, then Start Date is set as 06/FEB/2018 23:59:00.

Expected Behavior
When sum of Usage is 86400(just 24 hours) in operation resources and entering Completion date, Start Date should be set the time as just before 24 hours.

Steps to Reproduce

  1. Profile Setting
    WIP: Round Off Resource Usage to Minutes in Lead Time Calculations = No
    BOM: Time Unit of Measure Class = Time
    BOM: Hour UOM = HR
  2. UOM Setting
    Unit Class = Conversion Base Unit
    Second Time .000277777777777 Hour
    Minute Time .016667 Hour
  3. Define Resource for Assembly
    Resource:A UOM:SEC
    Resource:B UOM:SEC
  4. Operation Resource in Routing:
    Operation Seq:10, Resource Seq:10
    Resource:A
    Basis: Lot
    UOM:SEC (Second)
    Usage:75000

    -Operation Seq:20, Resource Seq:10
    Resource: B
    Basis: Lot
    UOM:SEC (Second)
    Usage:11400

  5. Create new using the Assembly
    Qty:1
    Completion:08/FEB/2018 00:00:00
  6. After saving, Start Date is set as 06/FEB/2018 23:59:00.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


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