End of mainstream support for Microsoft Dynamics AX 2009, 2012, and 2012Mainstream support for Dynamics AX 2009 Service Pack 1 (SP1), Dynamics AX 2012, and Dynamics AX 2012 R2 ended Oct. 9, 2018. After that date, only security hotfixes will be provided for these three versions through the extended support period that until Oct. 12, 2021. Read more
Dynamics 365 2019 release wave 2 plan Discover the latest updates to Dynamics 365.Release Plan | Weekly Deployment Notes
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants.Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements.
ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Talent TechTalks
We run the auto release to warehouse job (according to wave template below). We have no quantity available on the locations that are included in the location directive action query, so no pick work should be created.
When we run the Auto release to warehouse job, a shipment and load line is created, a wave is created, but no work is created. The shipment is not connected to the wave.
It is correct that no work is created, but the problem is that a shipment is created and remains in status Open.
When we later increase the on-hand quantity on a valid location we want to re-release the order line. The problem is that we first need to manually either delete the shipment before running the auto release to warehouse job again OR we need to add the shipment to the wave and process the wave.
This involves manual steps and is very inefficient.
Anybody who knows how we can avoid the shipment staying in status open when no valid pick location exists? (I.e not creating the shipment or keeping it as waved)
Should you maybe instead modify your setup, so that the created wave is not automatically processed when you release to warehouse?
This way a shipment will be created, will be in status Open and on the wave.
When you get the desired on-hand levels, you will process the wave, creating the picking work based on the updated on-hand levels?
Or, even better, not release the order to warehouse unless the desired on hand is available (based on fulfillment rate setup, for example)?
Thanks for your input. However, the business requirement that we have is for certain orders ("emergency orders") the pick work must be "automatically" released for pick, which we have solved with batch jobs for auto release to warehouse and process Waves job.
If you process the wave without finding a pick location the shipment will be removed from the wave, but will remain in status open. This creates a situation where you manually have to go in and delete the shipment.
The functionality shouldn't be that if no location is found you have to perform a manual operation before you can release or process again.
Also, the fulfilment rate (as I understand) is how much of the order that needs to be resevred before releaseing to warehouse. In our situation we want to reserve for picking as soon as anything is available in the dedicated pick locations.
Any more thoughts?
Well, another 2 suggestions:
- Have you considered setting up wave-based replenishment, so that if the on-hand is actually there, but in another location in the warehouse, the work will be created for picking sales, but will be blocked until replenished from wherever the items actually are.
- Have you thought about enabling "Fail on location directive failures" for Sales orders? This way, the auto release job will fail the release of the order where there's insufficient on hand, and will (because it is run in batch) add the error about it to the batch job log. Somebody could be monitoring that log (because you need to somehow figure out that there is insufficient on hand in the pick locations). The auto release job will keep trying to release that order based on the batch job schedule, so when the on-hand gets into the right location, it will be automatically released.
We have thought about setting up replenishment as you mention, but we would prefer not setting it up, since the other locations are not always bulk locations. They are sometimes on an un-pack location (near the inbound dock) where we don't want picking to occur.
We have also thought about working with different inventory statuses, but we do not want to complicate things too much.
We have setup fail on location directives failures. Without the fail a work is created with an empty location, but with the fail there is no work created, however the orer line is still released and the quantity on the load line is not decremented (like it is when short picking for example).
Or is there any parameter that will decrement load line upon release failure?
No, there is no setting like that, I am afraid
I have talked to the guy, who was working on the auto-release feature, and he suggests you log a request for changing this functionality a bit, to better accommodate your flow, as this is going to be a common request.
Specifically, enhance the auto-release (and manual release) process to handle those "stray" shipments that are not part of any wave yet.
Is there any update on this? Thanks
Wondering the same. Any updates?
We ended up modifying AX to automatically delete the shipment if its related work was not created.
Hi Robert and Ivan,
Do you know if there was an update on this issue?
We have found the same issue especially for some shipment lines that were being created but with no Work. Was then creating a shipment line with 0 work qty and then when trying to release to WH when backorder items come onsite there was issues with work being created, or as in above the shipment needed to be deleted and started again.
Seems to me to be a bug in that a Shipment line shouldn't be created on the shipment if no work qty. If other items have stock then work is created for them but not the unreserved items. Realistically they are not included in the release?
I have been looking for a solution / hotfix for this issue, but can't find any.
Did you already have a solution available ?
Any news on this? We're facing the same issue. I'm thinking of a modification that would delete the shipment and the wave but in that case I would also like to have the information in the log for the batch job.
Is there any further update or work around to this issue? We are facing the same issue. Thanks.
Using parameter "reserved physical" on the auto release SO to warehouse batch job instead of "all" did the trick for us.
Business Applications communities