10
We currently have problems in accurately reserving stock and therefore can’t deliver as per what we promised the customer.
The main problem is for when it comes to back orders (of which we have a lot, since we don’t stock a lot of our items, but order them based on demand).
In standard D365, the ways to reserve back orders are as follows:
Manually
OR
Combination of Batch jobs
- Automatic Release of Sales Orders
- Automatic Release of Transfer Orders
- Production status update (we set the parameter to reserve at “Estimate” status)
Problems we have with this are:
- We can’t do it manually, as we are dealing with over 5,000 back order lines at any point in time
- We had to break up the Automatic Release of Sales Orders into 11 separate batch jobs for our main warehouse in Australia because of performance reasons, as it is far too much data for the system to chew through (this was done like that on advice of Microsoft when we raised a support request, as no other solution was available)
- When running separate jobs for Sales Orders (including before mentioned split jobs for back orders), Transfer Orders and Production Orders, it all depends on which job runs first after we receive the stock in and therefore gets the stock reservation: i.e. I could have promised stock to the customer on a sales order, but because the production job ran first, it might have reserved the stock for a newer production order rather than the older sales order
- We can’t reserve for forward dated sales orders and transfer orders, as they would be released to the warehouse for picking which we don’t want.
- When investigating what other companies do in this space, we found that most have some bespoke functions to do this.
We have designed (and are currently building) a bespoke solution that in principle would do the following:
- Read all “On Order” transactions for sales orders, transfer orders and production orders combined in date sequence.
- For each of these transactions, invokes the functionality that sits behind the “Reserve Lot” button on the inventory reservation screen.
The main problem is for when it comes to back orders (of which we have a lot, since we don’t stock a lot of our items, but order them based on demand).
In standard D365, the ways to reserve back orders are as follows:
Manually
OR
Combination of Batch jobs
- Automatic Release of Sales Orders
- Automatic Release of Transfer Orders
- Production status update (we set the parameter to reserve at “Estimate” status)
Problems we have with this are:
- We can’t do it manually, as we are dealing with over 5,000 back order lines at any point in time
- We had to break up the Automatic Release of Sales Orders into 11 separate batch jobs for our main warehouse in Australia because of performance reasons, as it is far too much data for the system to chew through (this was done like that on advice of Microsoft when we raised a support request, as no other solution was available)
- When running separate jobs for Sales Orders (including before mentioned split jobs for back orders), Transfer Orders and Production Orders, it all depends on which job runs first after we receive the stock in and therefore gets the stock reservation: i.e. I could have promised stock to the customer on a sales order, but because the production job ran first, it might have reserved the stock for a newer production order rather than the older sales order
- We can’t reserve for forward dated sales orders and transfer orders, as they would be released to the warehouse for picking which we don’t want.
- When investigating what other companies do in this space, we found that most have some bespoke functions to do this.
We have designed (and are currently building) a bespoke solution that in principle would do the following:
- Read all “On Order” transactions for sales orders, transfer orders and production orders combined in date sequence.
- For each of these transactions, invokes the functionality that sits behind the “Reserve Lot” button on the inventory reservation screen.
STATUS DETAILS
Needs Votes
Comments
Every customer develops a reservation batch one way or another...
Category: Inventory