My Oracle Support Banner

Rapid Planning Appears To Schedule Material Based On Operation Start Date and Not Work Order/WIP Start Date (Doc ID 2361296.1)

Last updated on FEBRUARY 14, 2018

Applies to:

Oracle Rapid Planning - Version 12.2.5 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.5 version, Planning Engine in Test

Users are on 12.2.5 and have applied patch 22493520 - Mandatory 12.2.5 VCP Consolidated Patch 2 for R12.SCP_PF.C.Delta.6 - Users are running a Constrained Rapid Plan. They notice the component due date on a particular Work Order/WIP job is not due until several days after the Start Date of this job.
 
BOM in Org = JBP:111
=====
PM41833-002
  - Chassis000048 - 1 per

There's an unfirm work order for item = PM41833-002 qty = 1 with sugg start date = 16-FEB-2018 and sugg due date = 23-FEB-2018. The component = Chassis000048 which goes into the next assembly shows planned order qty = 1 with sugg due date = 19-FEB-2018. The issue here is the planned order was expected to be due at the start of the next assembly which in this case is 16-FEB-2018 for the wip job. Instead it is due 3 days late on 19-FEB-2018.

EXPECTED BEHAVIOR
-----------------------
Expect direct component items to be due at the start date of the next higher assembly wip job

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create WIP jobs
2. Run data collections and constrained RP plan
3. Find the component item is due 3 days later than the start of the work order

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
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.