My Oracle Support Banner

MRP Is Generating Circular "Items Allocated Across Projects/tasks" Exceptions (Doc ID 2454988.1)

Last updated on AUGUST 19, 2019

Applies to:

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

Symptoms

On :  12.1.3 version, Materials Requirements Plan in All instance:

Users are on 12.1.3 and are running a Supply Chain MRP plan (multi-org) with Project-Task and Project Mfg (PJM) installed.  They notice what they call circular exceptions in the plan output where the same exception = Items allocated across projects/tasks appears twice and appears to be circular.  The first exception is against the same project = 1004007MGD but task = 0-20-1 and the second exception is against the same project = 1004007MGD but task = 0-22-1.  The exceptions are against the same Project, Same PO, Same Promise Date, just different tasks.  Example data:

A.  First row exception
Org = MGD
Item = MAG-10627084
Exception = Items allocated across projects/tasks
Purchase Order = 813004788
From Project/Task = 1004007MGD/0-22-1
To Project/Task = 1004007MGD/0-20-1
Planning Group is Null
Qty = 1

B.  The second exception shows the exact same data as in A above, however the only difference is the From Project/Task and To Project/Task are reversed

From Project/Task = 1004007MGD/0-20-1
To Project/Task = 1004007MGD/0-22-1

When they check demand pegging against first row exception on the PO it shows Task 0-22-1 - the wip job it shows going into shows Task = 0-20-1 with sales order with task = 0-20-1.  When they check demand pegging against second row exception on the PO it shows task 0-20-1 - the wip job it shows going into shows Task = 0-22-1 with sales order with task = 0-22-1

C.  The PO has 2 lines

1.  Line 1 is for item = MAG-10627084 - Qty = 1 for task = 0-20-1 with need by date = 12-JUN-2018 and Promise Date = 26-JUN-2018

2.  Line 2 is for item = MAG-10627084 - Qty = 1 for task = 0-22-1 with need by date = 12-JUN-2018 and Promise Date = 26-JUN-2018

This appears to happen when the same project has demand for multiple tasks due on the same date.  Support duplicated this internally on 12.2.5 instance as code line with 12.1.3 should be identical

Created new make item = JMP2Make in Proj Mfg Org = P2
Created Sales order 80042 with 3 lines all qty = 1due 17-AUG-2017 with the same project = Test Engine but with different tasks = 3.0, 4.0 and 5.0
Created 3 wip job order numbers 277844, 277845, and 277846 for qty = 1 due 17-Aug-2017 with the same project = Test Engine but with different tasks = 3.0, 4.0 and 5.0
Created MDS name = JMP2MDS and loaded sales order into it
Created MRP name = JMP2MRP and attached MDS and key settings
Reservation Level = Planning Group
Hard Pegging Level = Project-Task
Ran plan and reviewed exceptions and see 2 circular exceptions called Items allocated across projects/tasks

This is the exact same issue as 11.5.9 Bug 5349738 - EXCEPTION MESSAGES ARE GIVING CIRCULAR REFERENCES - The solution to this bug was to set reservation level = Project-Task.  Apparently the problem is with the netting using Planning Group and so multiple demand/supply for the same project due on same date with different tasks can be netted differently everyday and hence cause the circular exceptions - However customer does not want to change the plan option and here's the business requirement:

Users do not have a Planning Group setup.  They want the exception messages to appear for Items allocated across projects/tasks because they need to see when common on hand or other supplies should be transferred to another project.  So many of the exceptions are correct.  It's when the same project with different tasks demand and supply fall on the same due date that these circular exceptions occur as duplicated internally.  If they change the reservation level it will not generate this message at all.  They want to see if this can be code fixed


EXPECTED BEHAVIOR
-----------------------
Expect the PO lines project-task to peg to the correct project-task and not create any circular exceptions

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run SCP plan with Project-task
2. Review exceptions
3. Find what appear to be circular exceptions for item/org called Items allocated across projects/tasks

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.