Using calendars in Microsoft Dynamics AX for purchasing
You might call this an orphan topic for companies managing purchasing schedules with Microsoft Dynamics AX 2012 and Dynamics 365 for Operations (AX7), but it is nonetheless quite important. Miscalculating delivery dates on your purchases always is, particularly in make-to-order and just-in-time manufacturing and distribution.
Some unexpected behavior exists in Dynamics AX with calendars and purchase orders, which I discovered this at a recent engagement with a distributor.
When working with resource groups and resources in Dynamics AX, the calendar is a mandatory field. But in purchasing where calendars certainly have an impact, they don't seem to be mandatory anywhere.
It is time to find out how calendars work when working with (planned) purchase orders.
Planned purchase orders
EXAMPLES:
- SITUATION 1: I have a standard calendar (5 working days of 8 hours each) in one of the three places shown in the table: Coverage group, Warehouse or Vendor.
Today is 11/11/2016. When my Purchase lead time is 22 working days, the system will calculate a delivery date of 12/13/2016 (forward scheduled).
When my Purchase lead time is 22 calendar days, the system will calculate a delivery date of 12/5/2015. (Note that 11/11/2016 + 22 days is 12/3/2016, but the system moves to the first working day of 12/5/2016).
- SITUATION 2: I have no calendar in any of the three places, just a calendar in the Master Planning parameters.
Today is 11/11/2016. When my purchase lead time is 22 working days, the system will calculate a delivery date of 12/3/2016.
When my purchase lead ...
FREE Membership Required to View Full Content:
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us hereor login