As a regulated company, controls like receipt and issue flow rules dealing with transaction and inventory status relationships have been identified by our quality unit as high risk/high criticality functionality. As such, any new product categories must be treated as configurations rather than master data. Any changes to existing product categories or creation of new product categories have to be validated. However, when creating new product categories, we often use the same issue and receipt rule configurations for new categories.
If sets of issue and receipt flow rules could be maintained independently and then assigned to the product category, the risk and criticality could be reduced to allow product categories to be treated like products and product-sites, reducing the need for validation.
corey milbert
