[fusion_builder_container hundred_percent=”no” equal_height_columns=”no” hide_on_mobile=”small-visibility,medium-visibility,large-visibility” background_position=”center center” background_repeat=”no-repeat” fade=”no” background_parallax=”none” enable_mobile=”no” parallax_speed=”0.3″ video_aspect_ratio=”16:9″ video_loop=”yes” video_mute=”yes” border_style=”solid” padding_top=”20px” padding_bottom=”20px”][fusion_builder_row][fusion_builder_column type=”1_1″ layout=”1_1″ spacing=”” center_content=”no” hover_type=”none” link=”” min_height=”” hide_on_mobile=”small-visibility,medium-visibility,large-visibility” class=”” id=”” background_color=”” background_image=”” background_position=”left top” background_repeat=”no-repeat” border_size=”0″ border_color=”” border_style=”solid” border_position=”all” padding=”” dimension_margin=”” animation_type=”” animation_direction=”left” animation_speed=”0.3″ animation_offset=”” last=”no”][fusion_text]
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.
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 time is 22 calendar days, the system will also calculate a delivery date of 12/3/2016.
When I want to use purchasing lead times in working days in Master Planning, I have to put a calendar on the Coverage group, Warehouse or Vendor. Note that the search hierarchy for a calendar is the 1) Coverage group, 2) Warehouse, and 3) Vendor.
If I have purchase lead times in calendar days, but want to avoid delivery dates on non-working days, I also have to put a calendar on either Coverage group, Warehouse or Vendor.
Dynamics AX calendars – purchase orders
When using purchase lead time in working days, I can only get the correct delivery date by putting a calendar on the vendor.
When I use purchase lead time in calendar days, and I want to avoid delivery dates on non-working days, I can put a calendar on any of the three: Coverage group, Warehouse or Vendor.
Here too, the search hierarchy is Coverage group, Warehouse, Vendor.
Note on the vendor calendar
On the vendor, the purchase calendar is under Purchase order defaults.
It does not copy to a similar field on the Purchase order header. The delivery date on the PO line checks the Purchase calendar on the vendor directly.
[/fusion_text][/fusion_builder_column][/fusion_builder_row][/fusion_builder_container]
