In the recently released CU10 update we are introducing a few new replenishment features that will increase warehouse productivity and save effort and time. This blog post will take you through the details of feature and for which scenarios it is aimed for.
In this blog we will cover following:
In Microsoft Dynamics AX 2012 R3, min/max replenishment and demand replenishment did not recognize one another, and both types of replenishment did not recognize existing replenishment work that was in progress or not started yet. Sales demand and existing replenishment work generated for the demand, did not know each other’s status.
That resulted in the following 3 problems and possible obsolete replenishment work transactions and waste of time in the warehouse facility:
All of the above was potentially creating noise and unnecessary open work transactions, overload of the items on the target replenishment locations, or a huge manual workload to synchronize demand and open replenishment work. For any warehouse facility with large number of locations that are either being replenished with min/max or/and demand replenishment, the above challenges are not acceptable.
In the new CU10 update, the replenishment setup for both demand and min/max replenishment, we have added the ability to define if the replenishment template, from generated work, will allow unreserved quantities to be used and deducted from by new demand quantity.
In the same setup we have added the ability, to define if the replenishment work should be cancelled if the demand has been cancelled (please note that if there is any existing work that is related to that replenishment work it will not be cancelled).
In the above setup all of the replenishment work generated and not processed will include new demands if the unreserved quantity allows. After all is used and deducted, new replenishment work will be created if needed.
In same way, if there is a min/max replenishment template that is configured to allow demand to use unreserved quantities, and has generated work, even if demand replenishment method is enabled it will first see if any of the quantity from existing work can be used.
This minimizes amount of the work lines created, where quantities can be deducted from existing replenishment work.
Please note that setup is template centric, which means that we can allow deduction and cancellation on one, but not the other template.
In CU10, we have also enabled configuration of the directive code for replenishment work order type.
Before the CU10 update, having several sequence lines in the Replenishment template lines where first one could not solve the demand, system was not continuing to another line sequence. This only counts if PUT location could not be resolved due to a location failure or stocking limits.
Now if the first sequence line fails to resolve put location and fulfil replenishment, next line in sequence will be processed.
Please note: In order to proceed to another replenishment template line, you need to setup Location directive failures to stop work on Replenishment failures, as shown below. If not set, it will end with an empty put location, and will not proceed to next sequence line in Replenishment template.
This feature is useful if we e.g. have stocking limits on a locations or locations fail for some reason due to other restrictions or setup. In that case system will proceed to another template and use put from location directives connected, that could be as for example an overflow location.