Using Approved Planned Orders in Microsoft Dynamics AX 2012

February 18 2014

Approved planned orders in Microsoft Dynamics AX 2012 can be a key tool for production in many S&OP scenarios.  These approved planned orders will be treated as if they have been scheduled for the specified quantity and due date, and they will not be automatically deleted by master scheduling logic or the Delete Plan task.  In addition, master scheduling logic recognizes planned changes to bill of material (BOM) components within the BOM version for an approved planned order, whereas actual orders have an order-dependent BOM and route.  The approved planned

About Scott Hamilton

Scott Hamilton has consulted globally with several hundred manufacturing/distribution companies on SCM and ERP issues. His publications include multiple books about SCM using Dynamics 365FO/AX, two textbooks about SCM/ERP, and 100+ articles in Scott has been a frequent speaker at Microsoft and user group conferences around the world, and a 10-time winner of the rarely given Microsoft MVP award.

Series of Essential Guides

More about Scott Hamilton


Julieta Arenoso's picture

Hi. Regarding the approved planned batch order, I'm facing the same exact scenario you are describing and therefore this is the way we are working in AX. However, we're having some trouble with the BOM updates. I understand you say that when working with planned work order, changes to the BOM components could be easily incorporated until the last minute. This is what we are expecting now but it's not happening. Please let me give an example to state my point: We create a Planned WO for July 2014 (we approve it) with BOM Version #1 that consists of: Item 1A Qty 1 Item 2A Qty 1. Later on, BOM Version #| is updated as follows: Item 1A Qty 1 ends 30/06/2014. Item 1B Qty 1 Item 2A Qty 1 We run MRP and notice the approved planned order's related requirements are not updated with the changes made to the BOM Version #1. Instead, Planned WO is still requiring: Item 1A Qty 1 Item 2A Qty 1. Are we missing something? Could you please help us? Thanks a lot!!

ScottHamiltonPhD's picture

The use of an "approved planned order" (for a production/batch order) within AX currently supports (1) locking the scheduled date and quantity and (2) preventing deletion of the planned order by master scheduling logic. However, it also (3) locks the BOM and route information so that planned changes in the item's BOM/route version are not recognized by master scheduling logic. This runs counter to the APICS viewpoint of a "firm planned order", which should support a floating BOM and routing in order to recognize the planned changes. As one workaround, you could delete the original approved planned order, create a new planned order and then approve it.

janek's picture

I am relatively new to AX, we are working with 2012 Master Scheduling. Our business model requires a two part replenishment review. We intend to run master scheduling nightly to generate TOs and POs for inventory replenishment from a main warehouse to multiple sites. Static Plan, with regeneration nightly. Site managers must review and approve (via firming) Planned Transfer Orders generated to replenish inventory and fulfill backordered sales order lines. Planned POs are generated to replenish inventory at the main warehouse (and cover TOs). My question is - are changes made to a planned TO (prior to firming) or firmed TO - rippled back to the Planned PO that may have been created to meet the requirement OR are the planned POs only updated when Master Scheduling is re-run? We have a situation where a planned site replenishment TO may be created for inventory (based on coverage) and the site may decide to downward revise the quantities. If the TO triggers a purchase need at the main site, a Planned PO is created but the downward revision in qty is not carried thru to the PO.

ScottHamiltonPhD's picture

I believe that you should run the master scheduling task in order to recognize the changes that you described. One alternative idea is to run the "net change explosion" for the relevant item (e.g., from the Net Requirements form), but this may not account for all impacts on the supply chain.