My Oracle Support Banner

OPM Collections Code Passing 0 for Maximum Offset When the Max Delay in OPM is Actually Null (Doc ID 2577194.1)

Last updated on AUGUST 14, 2019

Applies to:

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

Symptoms

On : 12.1.3 version, APS Collections

ACTUAL BEHAVIOR
---------------
Customer reports that after applying <patch 26620795:R12.MSC.B>, and also fix for <patch 26667332:R12.GMP.B>, PS cannot solve the schedule.

Specifically, <patch 26620795:R12.MSC.B> treats 0 and Null for offsets differently.

In <patch 26667332>, OPM started passing 0 to Planning for the Maximum Offset when the Max Delay in OPM was actually Null. This caused planning and scheduling to be incorrect.


EXPECTED BEHAVIOR
-----------------------
Collect 0 as 0 and Null as Null for Standard Delay and Max Delay


BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, PS is unable to solve the schedule and does not work at all.

Changes

 

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!


In this Document
Symptoms
Changes
Cause
Solution
References


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