The frontmatter lists a proof scenario or finding for every required rule and records each applicable category. Scenario coverage describes what to check; bindings identify the assertions that already exist, and execution results remain unverified. Simultaneous product and setup transactions, every lock reduction, all hidden availability fields through list status writes and derived-value input require dedicated proof. Workflow edges not named by a scenario remain in this finding rather than gaining a binding from shared workflow membership.
Catalogue corrections and accounting use separate saved versions. A product has a setup, a valid grid and an independently read version for each record. Retire and reactivate it, replace the grid at the latest product version, then update the setup using its unchanged setup version. The grid and lifecycle use the product version; the independent setup save succeeds without overwriting the product.
Coverage
Rulecovered
Transitioncovered
Validationcovered
Permissioncovered
Edgegap: FND-ACC-PRD-053
Failurecovered
Boundarycovered
Concurrencycovered
Invariantgap: FND-ACC-PRD-053
Interactioncovered
Test Scenarios
11 scenarios proving CAP-ACC-PRD-004; 8 bound to an existing test.
01Stale corrections preserve the latest versionconcurrencyapinegativetest