You can find the original blog post here:
Tutorial: Location directive failures - Common mistake #1 - Multi SKU
Common mistake #2 - Batch enabled location directive lineVery often when new people start working with the Advanced warehousing solution, they struggle to notice the little check-box on the location directive lines called Batch enabled. However, it is very important when dealing with batch-tracked items in outbound flows like Sales order processing.
Here's the typical scenario when users try to set up the location directives for the first time:
They created all the necessary Pick and Put directives, decided how they want to go about the lines and different units of measure, and now they are defining the actions, which in turn means defining the query for locations to consider for pick-up/put-down.
Here's a typical and valid location directive configuration:
|Valid location directive setup without Batch enabled set|
|Release to warehouse failed for batch-tracked item P0004|
But the reason is - the location directive action was not considered a match, because only ones with Batch enabled were considered for this item.
So let's change that and try again.
|Valid location directive setup with Batch enabled set|
|Defining the location directive action query for batch enabled action line|
|Release to warehouse succeeded for batch-tracked item P0004|
|Work created for picking sales order 000785|
What this means for your configuration
What this virtually means is:
- If you do not track batches on your items in the selected warehouse, you can ignore this setting completely
- However, if you do track batch numbers, you will most probably want to have 2 action lines for the same location directive line every single time, one for batch-tracked and one for non-batch tracked.
- That might be exactly what you want if you want to keep track of your batch-tracked items (perishable goods) separately from non-perishables.
- If not, however, then it gets pretty inconvenient, and I have no knowledge of why the original implementation was done this way (Maybe somebody from BHS can answer in the comments), but we do not have any plans to change this in the near future.
Note, that for inbound flows this check-box is not considered and is not even enabled in setup.
In the next blog post of this series we'll talk about Disposition code and how that impacts the receipt flow