frdrckmitchell7 (10/31/2013)
Hi KoenThis is just an example that I have used of course. We want to replenish items (stock) at branches that are in other branches. Think of this as updating stock. If there is no/little stock at a branch then request it from another branch. If a customer request a certain item, for instance, at a branch and the branch don't have it, we want to know if it is available somewhere else.
We track our stock for a certain period, thus the two dates.
Kind regards
Fred
You might be describing more than 1 scenario, it you are shipping direct to the customer.
Replenish Stock (inter branch transfers), which might be subject to safety stock.
And Branch Preferences, in which if you have no stock in one branch, entering the order in the system to be sent to the customer, but you may want to base this on some other constraints. i.e. - distance / time / cost of delivery.
The other factor is when you say track our stock. This could be for strictly inventory value / costing, or due to inventory having an expiration date.
Tread a bit carefully - not sure if you are doing some kind of daily snapshot, but inventory and orders can change very often. Once you make a commitment, it should be reflected in the data if this is being done real time. If just for planning purposes, that might not be as critical.
Note that if you are doing daily snapshots - once a day frozen inventory, other trending becomes very simple.