MRP by Truckload


We have E1 TMS, but haven't turned it on yet and are still in test mode. One of our primary issues is that our products are dense and heavy so we would like to find a way for MRP to plan by full truckload. We have dozens of branch/plants representing our various physical locations, so a proliferation of branch/plants to try and use as a work around isn't feasible. Most sales order fulfillment is directed by the closest shipping physical location to the customer ship to/pick up location.

Any thoughts would be appreciated!


Well Known Member
Have you tried setting the Maximum Reorder Quantity to be equal to the Truckload Quantity. This will break out your purchase order suggestions for each Truckload.


Active Member
By setting the maximum makes possible to generate the PO less than your truckload. Suggests setting the Order Policy Code (OPC) = 2 and then have your truckload = Value Order Policy (OPV)


We have a very similar requirement. We are using MRP to order material for manufacturing work orders. We need to consolidate by truckload quantities when ordering multiple items. Example: cardboard boxes. We order about 3-4 truckloads a day. The boxes are different items - different sizes, print, etc. They come from the same supplier though. We can't use min/max or OPC/OPV - it will only consolidate by one item. We bring multiple items on the same truck. MRP gives say 20 messages for this supplier. The planner has to cherry-pick what will fit on first truck, then action messages, then close MRP screen. Consolidated order is generated only when the MRP messages screen is closed. I have opened a enhancement request with Oracle on this. Oracle came back with this: "Currently we don't have that functionality. You need to exit out from the messages program to generate a purchase order message. There is an existing enhancement request Bug 17837924 : GENERATING PO ON P3411 WITHOUT CLOSE THE APPLICATION that is entered to address your requirement".
That bug has been opened since 2013. :) I would think it is easy enough to make a row exit Generate Orders in P3411. If you can support this bug with Oracle: you could open a service ticket and ask Oracle to link you to this existing bug.