An Interview with Microsoft Dynamics AX MVP Scott Hamilton

March 5 2012

If you didn't hear much from Microsoft Dynamics AX manufacturing guru Scott Hamilton for the last year, it's probably because he was hard at work on his latest book, Food Products Manufacturing using Microsoft Dynamics AX 2012. The book has been available for pre-order for a while, but it begins shipping this week and has been seeing rave reviews so far (all eight Amazon reviews are five stars as of publishing this article).

About Jason Gumpert

As the editor of, Jason oversees all editorial content on the site and at our events, as well as providing site management and strategy. He can be reached at

Prior to co-founding, Jason was a Principal Software Consultant at Parametric Technology Corporation (PTC), where he implemented solutions, trained customers, managed software development, and spent some time in the pre-sales engineering organization. He has also held consulting positions at CSC Consulting and Monitor Group.

More about Jason Gumpert


mkattelm's picture

We have a situation where we are trying to set up the system to allow an item to be sold at the case level or at the each level. As far as I can tell this is specific to food distribution. I purchased this book, but did not see a reference to this topic. Ideally, we would have a pack conversion on the case level indicating how many eaches were in a case. for instance, we might have four eaches to a case. If an each is sold, we would decrement 1 case, and increment three eaches. The cost of the each would be the cost of the case divided by the number of eaches in the case. We have explored using variants to accomplish this, but they get us only part way there. We would appreciate any direction in this area. Thank you.

ScottHamiltonPhD's picture

The question concerning "splittable items on a sales order line" involves several related questions that will shape the potential solution approach within AX. As the question and its solution are currently written (by MKattelm), the desired functionality would require a customization to AX. First, is there a separate item number corresponding to "each" (which would be a component of the item number representing a "case")? The BOM for the "case" item would reflect a component quantity of four for the "each" item, and also the packaging material. This approach allows you to calculate the cost of the "each" item and the "case" item. The two different items often have a different UPC code. Second, assuming a single item number, have you defined the UM conversion between a case and each? Also, have you defined different sales prices for these two UM? Or is the sales price proportional to the UM conversion? A proposed solution approach would be based on the answers to these questions. about .