Keep case revision in every batch row
Synthetic batch B45 prepares joining J45/R1, move M45/R2 and departure L45/R1. At the supplied issuing checkpoint J45 is stillR1, M45 nowR3 and L45 stillR1. Local rule issues unchanged rows and holds changed ones for regeneration. No action has yet been dispatched.
| Case | Prepared/current | Decision |
|---|---|---|
| J45 | R1/R1 | Issue |
| M45 | R2/R3 | Hold/regenerate |
| L45 | R1/R1 | Issue |
Compare at the issuing checkpoint
- Read source revisions at checkpoint
- Match by case identity
- Release J45/L45 prepared rows
- Regenerate M45 from R3
Do not merely relabel M45’s R2 payload as R3; regenerate its actual administration contents.
How many prepared rows may issue and must be regenerated?
Show the worked answer
Two may issue and one, M45, must be regenerated. Approval of a batch name does not make an outdated row current.
Regenerate changed rows only
| Case | Action or result | Evidence boundary |
|---|---|---|
| Relabel R2 asR3 | Reject | Contents not regenerated |
| Hold only M45 | Matches local rule | Other two sources unchanged |
Record what actually issued with its case revision. A later source change needs its own administration follow-up, not a rewrite of the completed batch history.