Comments
To build on this, it would also be nice if CSU deployment to Production could follow the notion of F&O, where we could take the resultant state of deployments to tier 2+ environments (where you may have deployed x # of ISV packages and a customer extension package), and take that whole set along with the Platform version as one deployment to Production (to help us ensure we only run code in production that has run together in lower environments, and ideally even tested!).
REMARK: Example: Sampling method and legal entity and/or user sample selection for:
-Production orders on quantity quality assurance and/or approved testing releases (e.g. finished goods, BOMs, routes, scraps, batches, quantities, operators, production lines, floor releases).
-Projects (e.g. vendors and customer within a production order).
-Customers (e.g. customer production order).
-Vendors (e.g. vendors applied or incurred in a production order).
-Warehouse stored items (e.g. Items already stored, purpose of preventions)
-Quarantine items (e.g. Items in progress... purpose of prevention o purpose of efficient authorized receipts)
NOTE:
Not featuring an inclusion of preventions, we may not easily foresee the potential future or future potential problems preventions, including at time of purchase order receipts. (receipt conditions at warehouse, or on quarantine).