Material flow modules
Refactoring of stock areas
- stock areas will now be in fact: locations
- a location will have two types:
- control point
- warehouse - its also a control point but of a special type, here we keep track of resources
So we have to replace everywhere the term stock area by location.
Separations to modules
Influences
- what to do when transferring from simple control point to warehouse ? null warehouse attributes in batch ?
- functions that require resources must always filter out simple control points in their lookup and have validators that do not allow them
- resources cannot be created for control points
- change the term stock area to location in GUI (and in data model if we have time)