How to Resolve Planning Manager Interface Records Stuck With PROCESS_STATUS = 3 (Doc ID 2849658.1)

Last updated on DECEMBER 28, 2023

Applies to:

Goal

The Planning Manager is hanging and is not processing data. Records with PROCESS_STATUS = 2 are picked up by the Planning Manager and changed to PROCESS_STATUS = 3, but rather than continuing to be processed, the records remain stuck.
This issue can happen for any of the interface tables used by the Planning Manager:

MRP_FORECAST_INTERFACE
MRP_SCHEDULE_INTERFACE
MRP_RELIEF_INTEFACE
MRP_SALES_ORDER_UPDATES

PROCESS_STATUS Reference
1 = not used
2 = waiting to process
3 = in process
4 = error
5 = complete

It is important to note that the problem occurred in January 2022 (2022-01) and these are the records which are stuck that we are concerned with processing.

Use the following note for gathering diagnostic information regarding the above tables:

When Does The Planning Manager Need To Be Running? And A Diagnostic Check Script (Doc ID 790125.1)

Run the planning_manager_check2.sql script attached to the note and review Section '3. Checking count and process status on key tables that are processed by the Planning Manager'

Please find sample output below to help better explain the solution:

MRP_RELIEF_INTERFACE

3.1 - Checking count and process status in MRP_RELIEF_INTERFACE
RELIEF_TYPE: 1 = MDS relief / 2 = MPS relief
PROCESS_STATUS = 2 is valid if Relief_type = 2 and MRP: Consume MPS = No
OR
IF RELIEF_TYPE = 1 and MRP: Consume MDS = No
Otherwise records should get PROCESS_STATUS = 5

Solution

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