Exclude Shipment Orders from PMRP/MRP Planning

Hi,

There is an option to remove supply demand for Remote Warehouse for Shipment Order. On the remote warehouse you have a default Part Availability Control ID. If that Part Availability Control ID has the Part Supply Control setting as Not Nettable, then the shipment order is excluded from all supply demand views. This is useful for instance if you have service vans represented as remote warehouses and don’t want the material in those vans to be plannable. Not sure if this will help in you scenario?

Best Regards

Fredrik 

Hi ​@Fredrik Johansson LKP ,

I tried that option. Let me add the data set up.

1. Created a remote warehouse and defined a default part availability control with supply option not nettable

I defind my demand in the project as a misc demand. Lets assume I have stock with in the warehouse as project inventory. Then I create a shipment order to move the material from the central warehouse to the remote warehouse.

IPAP recognize this shipment order as a new demand. and IPAP shows as a demand as well.

When I run the MRP, system create supply for the shipment order demand as well. Ideally i want the shipment order just to transfer the stock not to raise a new demand. A Duplicate Demand.

Is there anyway to avoid this.

Thanks,

Chamath

Hi,

Ok, I get it. It feels like there should be some supply code handling on the Project Misc Demand. In the task material line we have introduced the possibility to source from sites / remote warehouses creating pegged shipment order (in same company) or pegged distribution order (in different company). We also consider the supply / demand aspect to avoid it to be doubled. So the task could be intended at the service / installation site and is represented by a remote warehouse, and then the shipment order is used to deliver, at receipt the material gets reserved to the task material line and you can do issue / picking.

I am not an expert on Project Misc Demand and your solution. Are you planning to have a one to one between the Project Misc Demand and the Shipment Order? Or could the Shipment Order refill more to have some stock in the remote warehouse? I don’t see any out of the box solution from core. Perhaps a solution in core would be something like setting demand code Project Misc on the shipment order and exclude those from the planning? Then change logic in the SHIP_ORD_LINE_SUPP_DEMAND_BASE view which is the view contributing to supply / demands for Shipment Order. Perhaps a small change in this view could be done as a customization?

Best Regards

Fredrik

Hi  ​@Fredrik Johansson LKP 
Did you find any solution, I have quite a “similar issue” trying to transfer a part from the site to remote warehouse.

When the shipment order is release meaning that the part is in transit, if I re run the PRMRP, system is generating a new demand and is not considering the transfer between site and remotre warehouse. 

Thanks for you help,

Hi ​@mmoulie,

When I do the Cursor-assisted code/functional search for your issue, received little bit different reasoning for this duplication. I hope these insights are beneficial.

What the code actually does

• Shipment Orders with Project/Activity are excluded from MRP snapshot (activity_seq IS NULL filter in Get_Mrp_Ship_Ord_Supp_Demand).

• PMRP never snapshots Shipment Orders at all — PmrpPlanSnapshot.Snap_Part_Supply_Demand has no Snapshot_Shipment_Order__ call.

• So PMRP-created PRs (requisitioner PMRP, demand code PI) come from Project Deliverables demand, not from the Shipment Order as a planning source.

Most likely cause of duplicate PRs

PMRP is probably seeing two separate PMRP demands for the same material:

A Shipment Plan is skipped (because of the exclusion logic) only when the parent deliverable item (demand_parent_item_no) has Supply Created = TRUE.

That exclusion often fails when:

1. Supply Created is still FALSE on the material item when PMRP runs (Shipment Order/Plan already exists, but PMRP has not yet marked supply as created).
2. demand_parent_item_no on the Shipment Plan does not point to the material item that received supply — the supply_created check looks at the wrong item.
3. Both a Material Plan and a Shipment Plan exist on the same deliverable line with Supply Option = PMRP (Shipment Plan inherits PMRP from the deliverable structure).

The Shipment Order is the execution/movement step; the duplicate PR is typically triggered by the Shipment Plan still counting as PMRP demand, not by the Shipment Order line itself.

Please go through this reasoning, then we can try to find out a way to stop creating duplicate PRs.

regards,

Piyal