Now that we understand the difference in Marking and Reservations, we know master planning will create planned orders based on un-reserved demand. Master planning will create a pegging reference for each Planned Order. The pegging is the specific demand from which the planned order was created. So for example, a planned purchase order may be pegged against a sales order line for the same item and quantity as the planned order. Master planning created the planned order to cover the requirement for the sales order line.
When any planned order is firmed (or turned into a real order), the Update Marking value set on the parameters is used to determine how Marking and Reservations get set on the firmed order lines. If Update Marking is set to a value of either “Standard” or “Extended” the purchase order in our example will now be marked against the sales order it was pegged against during the planned order phase, and the sales order transaction will now be in status “Reserve Ordered” and reserved against the purchase order that was just firmed. This is how master planning can update the reservations of demand orders or transactions.
Now we’re going to move on to how reservations work with R3 Warehouse Management functionality, we’ll start with the setup of Warehouses. In the Warehouse Management section there is a field called “Reserve when orders are released by a batch job”. This field is used only by the WMS functionality and only applicable for warehouse that are setup to use the warehouse management process. This field will allow Dynamics AX to automatically perform the reservation of orders when they are released to the warehouse for picking. But only if that release to warehouse process is done via a batch job located in the Warehouse Management module.
The post Transactions in Dynamics AX – Master Planning and Warehouses appeared first on I.B.I.S., Inc..
This post first appeared on Microsoft Dynamics AX & CRM Partner, Atlanta, GA -, please read the originial post: here