MRP Plan Run Hangs On MRCNSP And MRCMON With All Other Requests In Pending Standby

A.  Profile Option Concurrent:Active User Limit or Concurrent:Active Request Limit (short name for sql above is CONC_REQUEST_LIMIT) has a value other than NULL.  This can stop MRP concurrent requests from processing if this is set to too small of a number.  We recommend this profile be set to NULL

B.  There are not enough Standard Manager processes defined.  This is the one we typically run into the most often when MRP concurrent requests are not running or continue to run.  The Standard Manager is a concurrent manager which can be viewed in System Administrator/Concurrent/Manager/Administer.  We recommend the number of processes for this manager based on the following formula:

(2 x <Value for Profile Option MRP: Snapshot Workers>) + 6

So in the example above, if the value of profile option MRP: Snapshot Workers = 5, the formula would be as follows:

(2 x 5) + 6 = 16

To set the number of processes for the Standard Manager navigate System Administrator/Concurrent/Manager/Define - query the Standard Manager - select Workshifts button - set the number of processes - save. Bounce the Standard Manager.  16 would be the minimum to set for the processes on the Standard Manager.  Usually you can add a few more processes to this but generally you would not want to go above 20 - 25. 

Typically the value for profile option MRP: Snapshot Workers is set with 3, 4 or 5 - This enables the Memory Based Snapshot to offload work to the workers to help improve MRP plan performance.

C.  The MRP Manager and/or the Planning Manager are not running (Only for old MRP Planning module.  This does not affect ASCP plans).  If the plan has never been run successfully before and users have loaded demand/supply data into the system without these two being run, then the plan tries to do the Planning Manager work itself if profile MRP:Perform Planning Manager Functions in Loads = Yes while the following profiles are set incorrectly:

MRP:Planning Manager Batch Size = Null
MRP:Planning Manager Max Workers = 10 

Perform the following:

1. Set the following profiles

MRP:Planning Manager Batch Size = 10000
MRP:Planning Manager Max Workers = 0

Save

2. Bounce/Start the MRP Manager in System Administrator/Concurrent/Manager/Administer - find the MRP Manager and start it up. Make sure it comes online with only 1 target/actual process. This manager only runs the Planning Manager and should never be set to more than 1 process. If you have more than one process, change the processes back to 1

3. Start the Planning Manager - Material Planner/Setup/Planning Manager - pick any organization as it doesn't matter. select the Start button.

4. The planning manager has a lot of work to do since it's not been running so it may run for a significant amount of time. When you start to see multiple start messages in the Planning Manager form, this means it's cycling and done with it's work

5. Then run the MRP plan after the Plannning Manager has begun to cycle

D. MRP Manager set to more than 1 process.  As noted above, this Manager should NEVER have more than 1 process.  It's only job is to run the planning manager.  When more than 1 process is setup for this Manager it will then allow multiple Planning Manager concurrent requests.  These requests can then contend with MRP plan concurrent requests and cause them to hang.

1.  Shut down the Planning Manager and MRP Manager

2.  System Administrator/Concurrent/Manager/Define - query MRP Manager - select Specialization Rules button - there should only be 1 row here for the Planning Manager.  If other rows are defined you must move them to a different concurrent manager. 

3.  Then select the Workshifts button - change the processes = 1 - save

4.  Start the MRP Manager and the Planning Manager

5.  Rerun the MRP Plan

set up OPM so that the ASCP Planned Orders are for a fixed quantity

In order for ASCP to generate planned orders in a fixed quantity dependent on the recipe that is being used for the planned order then the Oracle Inventory Organization Item 'Order Modifiers' of Fix Lot Multiple, Fixed Order Quantity and Order Quantity Minimum and Maximum should be NULL for the product.

The Recipe Validity Rule

Process Engineer / Recipes (GMDRCPED)

should be established such that Standard, Minimum and Maximum Quantities are the same and reflect the desired planned order quantity.

This can then be seen in the Collection Workbench Process Effectivity

Advanced Supply Chain Planning/ Advanced Supply Chain Planning/ Collections/ View Collected Data (select the OPM organization), View By Items, Drill down Plans / Collections/ Category, click on the item, right click/ Bom/Routing/ Process Effectivity

as the Minimum and Maximum quantity

and in the Planner Workbench, Supply/Demand in the resultant planned order quantities

This only applies to ASCP Constrained Plans.