BR-008 Claim not found on aggravation-rights retrieve¶
Field
Value
Statement
A "Claim Not Found" error is raised when the aggravation-rights stored-procedure retrieve returns no rows.
Trigger
Stored-procedure retrieve returned no rows.
Enforcement
AfterRetrieve in clsAggRightDates.vb; the same identifier (clsAggRightDates01) is reused in clsITimelinessOfFirstPayment.vb's AfterRetrieve, an ID collision.*
Outcome
Error message added to the object; caller sees a failed retrieve.
Insert, update, and delete operations must affect exactly one row (RowsAffected <> 1 or = 0) or a DB-contention error (clsConstants.Messages.DBContentionError) is raised.
Trigger
RowsAffected mismatch after an insert/update/delete against a UPDATE_NUM-versioned row.
Enforcement
After* hooks (UpdateError / InsertError / DeleteError) across the persistent classes.
Outcome
Optimistic-concurrency failure surfaced to the caller.
The weeks-per-month conversion factor used for monthly wages depends on the injury date: injuries before 01-Oct-1973 use the historical factor, later injuries use the current factor.
For hourly or daily workers injured before the 1995 effective date, the days-worked-per-week used in the calculation is floored at three days, even when the worker actually worked fewer days.
Every execution path — validation failure or successful calculation — returns exactly one row containing a wage and an error message; failures are reported as data, not as raised exceptions.
No rules are recorded for sp82046_CalcAggRightDates, sp82067_TimelinessOf1stPayment, or sp82289_medicallystationarydt — these three are not-found-by-cli and no procedure body was retrieved for them.
cls1502Transfer01 is used as the rule ID for two distinct rules (BR-001, BR-002), which is likely a copy/paste defect.*
clsAggRightDates01 is reused across clsAggRightDates.vb and clsITimelinessOfFirstPayment.vb, which is likely a copy/paste defect and could make broken-rule messages ambiguous.**
Several classes (clsActiveBenefitSchedule, clsAwardBenefitPayment, clsFederalAwardStatus, clsWorkerInjuredBodyPart) contain commented-out Rules.AddRule templates only; these are not live rules and are excluded from this page.
SQL-048 (setting an award to Pending) has no UPDATE_NUM predicate in its WHERE clause and is therefore not protected by the optimistic-concurrency check described in BR-012.*
Note: Statements marked with * were inferred from code structure, naming
conventions, or contextual evidence where direct confirmation was not available
in source artifacts. Statements marked with ** could not be confirmed; treat
as unknown until verified.