My Oracle Support Banner

Master Production Schedule Entries form shows more Planned Order records then MPS Planner Workbench Supply form (Doc ID 1630345.1)

Last updated on AUGUST 19, 2021

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, MPS plan

After running the MPS Plan, find that the number of records shown in
Master Production Schedule Entries form and the number of Planned Order
records on MPS Planner Workbench Supply form is not in sync.

The number of records shown in Master Production Schedule Entries form
is more compared with the number of Planned Order records on MPS Planner Workbench Supply form.

This issue occurs when  MPS plan with overwrite option set as "Outside planning time fence".

EXPECTED BEHAVIOR
-----------------------
Expect the number of records shown in
Master Production Schedule Entries form and the number of Planned Order
records on MPS Planner Workbench Supply form is in sync after running MPS Plan.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Create Assembly Item

Inventory responsibility
(N)Item > Master

Item: YO-FIN-0206
Planning Time Fence : 2

2. Create component item

Inventory responsibility
(N)Item > Master

Item: YO-PO-0206

3. Set Item: YO-FIN-0205 with routing

Bills of Materials responsibility
(N)Routings > Routings

Item: YO-FIN-0206

4. Set Item: YO-FIN-0205 with BOM

Bills of Materials responsibility
(N)Bills > Bills

Item: YO-FIN-0206

NOTE: Set the operation number set in 3. and component : YO-PO-0206



5. Set MDS

MRP responsibility
(N)MDS > Names > Items(B) > Details

MDS name: yo_mds_07

Item: YO-FIN-0206

DATE           Current
-------------------------
02/07/2014    1
02/08/2014    1
02/09/2014    1
02/10/2014    1
02/11/2014    1

NOTE: 02/08/2014 and 02/09/2014 is workday



6. Set MPS

MRP responsibility
(N)MPS > Names > Options

MPS name : yo_mps_07
Overwrite : Outside planning time fence

NOTE: This MPS is a newly created MPS and no planned order are created at present.



7. After running MPS plan, check in MPS Planner Workbench  (Plan run date is 02/07/2014)

MRP responsibility
(N)MPS > Workbench > Supply(B)

Sugg Due Date    Qty/Rate
------------------------------
02/09/2014      3
02/10/2014      1
02/11/2014      1

Planning Time Fence Date : 02/08/2014
Therefore, Planned Order Sugg Due Date is from 02/09/2014

8. Check Master Production Schedule Entries form

MRP responsibility
(N)MPS > Names > Items(B) > Details(B)

Date           Current
-----------------------------
02/09/2014      3
02/10/2014      1
02/11/2014      1

9. Change the MPS manually so that the record with Date is within Planning Time Fence Date on Master Production Schedule Entries form

MRP responsibility
(N)MPS > Names > Items(B) > Details(B)

Date           Current
-----------------------------
02/07/2014      1 <========== ★
02/08/2014      1 <========== ★
02/09/2014      1 <========== ★
02/10/2014      1
02/11/2014      1

10. After running the MPS plan, check in MPS Planner Workbench

MRP responsibility
(N)MPS > Workbench > Supply(B)

Sugg Due Date    Qty/Rate
------------------------------
02/07/2014    1
02/08/2014    1
02/09/2014    1
02/10/2014    1
02/11/2014    1

11. Check Master Production Schedule Entries form

MRP responsibility
(N)MPS > Names > Items(B) > Details(B)

Sugg Due Date    Qty/Rate
------------------------------
02/07/2014    1
02/08/2014    1
02/09/2014    1
02/09/2014    1   <========== ★
02/10/2014    1
02/11/2014    1

We see that a new record for 02/09/2014 is additionally created which does not sync with
number of records for Planned Order shown in MPS Planner Workbench.

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.