I have a question: When running the planning worksheets in BC for the MRP using the demand forecast, and then accepting the action messages for creating new PO’s - the PO is created successfully but filled with different SKUs, different qty’s, and different receipt dates all in one PO (see screenshot below).
The demand forecast is created by the sales item type and not component.
I believe this would require a modification. I somewhat recall doing something along these lines a year or so ago. If I can track down my notes from that, I’ll try to post more information here.
Out-of-the-box there is nothing that auto-splits the POs into single line Purchase Orders.
However, if you filter your results by “Order Date” it will give you what needs to be created today or this week (depending on how you filter). This way you aren’t creating a PO for six months out and the Vendor ignores the date and ships the product early.
P.S. If you haven’t noticed, the system is generating POs with multiple Locations on the same PO, so be sure to filter by Location prior to Carrying Out Actions.
The process is fairly simple. You need to sort the requisition lines to group them my the fields on which you want to split the purchase orders. Then keep track of you “Break Field” values. Triggering a new PO when those values change.
The events you need are in Codeunit “Req. Wksh.-Make Order”
To set the sort order, subscribe to “OnBeforeSetReqLineSortingKey”
To track the field values and when they change, subscribe to “OnBeforeCheckInsertFinalizePurchaseOrderHeader”. Setting “CheckInsert” to TRUE in this subscription will trigger a new PO.
Subscribe to “OnAfterInsertPurchOrderHeader” to update fields on PO
Use “OnFinalizeOrderHeaderOnAfterSetFiltersForNonRecurringReqLine” to filter the requisition lines to be included.
Thank you for the reply! Just asked around, and it turns out we cant do any modifications to our BC, since we don’t have any developers inhouse to do this.
