Using Demand Forecasts for S&OP in Microsoft Dynamics AX 2012: Part 2

January 10 2013

Demand forecasts - also termed sales forecasts - often provide a key element of the Sales and Operations Planning (S&OP) game plans for stocked products. Effective use of demand forecasts involves several interrelated issues, such as the relevant time increments and due dates, forecast consumption policies, and master scheduling logic. Many firms have struggled with these issues, and they experience problems in coordinating supply chain activities.    

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 AX as well as two textbooks about SCM/ERP, and his books have been translated into Portuguese, Russian, Chinese and Japanese. For more than 10 years, Scott has been a frequent speaker at Microsoft and AXUG conferences around the world, and a multi-year winner of the rarely given Microsoft MVP award for Dynamics AX. His regular column “The AX Solution Architect” is published in

Series of Essential Guides

More about Scott Hamilton


sean_gilbert's picture

This is a great article which has really helped me understand the forecast consumption options in AX. However, I am stuck dealing with past-due forecasts. I am using the Dynamics AX Generate statistical baseline forecast to generate a monthly forecast prediction. Once I review, publish and import my forecast changes from excel to AX the forecasts are imported on the first day of the forecast month. This is a simple distribution business which only wants to forecast sales by month with no further granularity. Sales orders are usually entered through EDI or manually 4-5 days before they ship. When running master scheduling on or after the first day of the month the forecast is now considered past due. As sales orders are created day after day for different customers MRP calculations are constantly creating planned orders for small quantities to account for the sales order being created as they are not consuming the past-due forecast. Is there some setup that can mitigate these past-due forecasts without creating more work for the planner? (ie they don't want to start managing weekly or daily forecast numbers.