Planned Orders Being Created For Phantom Items Unexpectedly For Constrained Without Detailed Scheduling (SCO) Plan (Doc ID 1664151.1)

Last updated on MAY 02, 2023

Applies to:

Symptoms

On : 12.2.3 version, Constrained planning

Users are on 12.2.3 (R12.SCP_PF.C.3) and have applied no one offs for MBP or snapshot. They're using 64 bit Linux MBP using MSONWL64.ppc 120.15.12020000.8 - They're also using 64 bit Linux Snapshot MSCNPL64.ppc 120.11.12020000.6

Background:
===========
We've told users at a certain patching level in 11.5.10.2, 12.0, 12.1 and 12.1.3 to set the following ASCP profiles:

A. Always set MSC: New Planner Backward Compatibility = Yes

B. Control whether phantoms show as planned items in ASCP workbench with profile

MRP_NEW_PLANNER_BACK_COMPATIBILITY

-Yes - Phantom items show up in ASCP workbench
-No - Phantom items Do Not show up in ASCP workbench

C. This is backed up by
Note 1505011.1
Note 1326194.1

Now customer runs an SCO EDD Constrained Without Detailed Scheduling plan on 12.2.3. It doesn't appear that setting the MRP profile actually controls the behavior of phantoms showing up or not in the ASCP workbench based on the following 4 test cases with this type of plan:

Test 1
MRP_NEW_PLANNER_BACK_COMPATIBILITY = Yes
MSC: New Planner Backward Compatibility = Yes
This shows the phantom planned ordes in ASCP workbench (expected)

Test 2
MRP_NEW_PLANNER_BACK_COMPATIBILITY = No
MSC: New Planner Backward Compatibility = Yes
This shows the phantom planned ordes in ASCP workbench (NOT expected)

Test 3
MRP_NEW_PLANNER_BACK_COMPATIBILITY = No
MSC: New Planner Backward Compatibility = No
This Does NOT show phantom planned orders in the ASCP workbench (almost like MSC profile is controlling phantom to show up or not)

Test 4
MRP_NEW_PLANNER_BACK_COMPATIBILITY = Yes
MSC: New Planner Backward Compatibility = No
This shows the phantom planned orders in ASCP workbench (expected)

D. Support can duplicate with same type of plan in 12.2.3 environment

E. Customer example data:

End item = JMake
2 direct phantom components JPhantom and JPhantom1
Profiles were set as follows:

MRP_NEW_PLANNER_BACK_COMPATIBILITY = No
MSC: New Planner Backward Compatibility = Yes

After ASCP plan was run, the 2 component items showed planned orders in the ASCP workbench.



So this boils down to what does SCO want to have set for these two profiles when running SCO plans?

EXPECTED BEHAVIOR
-----------------------
Expected for 12.2.3 to have to set the MSC profile = Yes and use the MRP profile to control whether phantom items are shown in the ASCP workbench as part of planning or not

Changes

Cause

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