The Min/Max Planning Report Backschedules OPM Batches, Creating Batches with Planned Start Dates in the Past (Doc ID 2004562.1)

Last updated on MARCH 08, 2017

Applies to:

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

Symptoms

On : 12.1.3 version, Min/Max Planning

ACTUAL BEHAVIOR
---------------
When the Inventory Min/Max Planning report creates OPM batches, the batch is currently backward scheduled. It appears that sysdate is passed to the create_batch API as the planned completion date, and the planned start date is then calculated in the past. This was changed for the creation of WIP jobs in <bug 13709690>, but it was not changed for creating OPM batches. In most planning, it makes sense to pass in the requirement date as the planned completion date, but the Min/Max Planning report seems to go off of sysdate, so it does not make sense to always create batches to start in the past.

EXPECTED BEHAVIOR
-----------------------
The functionality of the Min/Max Planning report should be consistent for creation of any kind of manufacturing order, whether discrete jobs or OPM batches. The date passed to the create_batch API should be the planned start date.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run the Min/Max Planning report for a manufactured item in a process-enabled org.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, batches are being scheduled in the past.

Cause

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 hundreds of Community platforms