Marking in Microsoft Dynamics AX, Part 2: More advanced topics

February 18 2016

In part 1 of this article, we examined the basics of marking functionality Microsoft Dynamics AX, which dates back to the early releases of the product and remains much the same today. Here in part 2, we will explore more complex ways in which marking impacts firming planned orders, pegged supply, the production order cost sheet. We conclude with some thoughts on manual marking (and un-marking).

About Evert Bos

I am Evert J Bos, ERP consultant since 1986. I started in Europe with IMS7 (A Honeywell Bull Mainframe ERP system) and the BaaN ERP system. Since 1995 I have worked in the USA and since 2004 I have been working with Dynamics AX.  I work for Sikich and focus mostly on manufacturing companies that make complex, engineered products.

More about Evert Bos

Comments

jemrunner's picture

Great article as always Evert. Many thanks! One thought for another spin-off article on this topic - marking management for ETO/MTO manufacturers who use common sub-assemblies as core building blocks within their custom product structures - under Standard as well as FIFO/LIFO costing rules. Special consideration for this scenario under shifting build priorities where one build with a need date that is initially set later in time is shifted to fall ahead of other builds based on customer or management directives after BOM construction and production activities have already commenced - a common scenario we are both familiar with :-). Jack Moran

tlw00dy's picture

Hi Evert, Thank you for this well-written piece on marking. I would like to clarify one point. If you are an MTO/ETO that is also using the project module, then firming via the explosion with marking turned on and using pegged supply DO NOT give you the exact same functionality. If you use pegged supply and the top-level production order is a "project production order," then the resultant derived production order will have the same behavior as the top-level project. For example, you could have the cost of the components consume directly to the project at the point of picking list update. This is not the case with mere marking. Thank you again, Tom