My Oracle Support Banner

Rapid Planning Is Not Pegging Past Due Supply To Past Due Demand In A FIFO Manner (Doc ID 2520912.1)

Last updated on OCTOBER 19, 2019

Applies to:

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

Symptoms

On : 12.2.6.1 version, Planning Engine in PROD

Users are on 12.2.6 and have applied patch 25074533 12.2.6.1

Key RP Files

engine.zip 120.134.12020000.136
RPAdmin.zip 120.5
RPUIDomainTemplate.zip 120.0.12020000.2
ui.zip 120.206.12020000.141

Users are running an unconstrained MRP Plan 550 days - All Planned Items - Overwrite = All - many orgs attached. They have past due demands and past due supplies and it appears that RP is not using the oldest due date supply to peg to the oldest start date of the next assembly demand. Example data

Item = 033402 - End item 033402
Item = 031968 - component
Org code = TST:M1

The end item 033402 has the following past due start dates all qty = 1
5-Jul-18
11-Jul-18
16-Jul-18
20-Jul-18
25-Jul-18
27-Jul-18
1-Aug-18
2-Aug-18

The component has on hand and work orders with the following old due dates
8/16/2018 - on hand
8/16/2018 - on hand
8/10/2018 - Work order
8/13/2018 - Work order
8/15/2018 - Work order
8/16/2018 - Work order
8/17/2018 - Work order
8/20/2018 - Work order

The expectation was that the oldest end item demand would get the on hand first and then use the old due date of the work orders to peg too. However the pegging appears to be random. It would also be okay if the component supplies were used in the following order

8/10/2018 - Work order
8/13/2018 - Work order
8/15/2018 - Work order
8/16/2018 - on hand
8/16/2018 - on hand
8/16/2018 - Work order
8/17/2018 - Work order
8/20/2018 - Work order

Per Bug 13351636 THE PAST DUE PURCHASE ORDERS ARE BEING PICKED IN RANDOM ORDER - this looks like it should work

EXPECTED BEHAVIOR
-----------------------
Expect the oldest past due supplies to be pegged to the oldest past due start date demand

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run RP Plan
2. Review supply demand output and pegging
3. Find past due supplies assigned to demands appears to be random

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.