As a Broker developer, I need to ensure that attempts to correct/delete non-existent records don't create new published data

Description

Background:
Currently, when an agency submits a correction/deletion record to FABS and the Broker can't locate an existing record with the same unique key, FABS is publishing the correction record in the database. Instead, it needs to trigger a hard error on that row, and publish nothing related to it if the submission housing it is published.

A/C
When CorrectionLateDeleteIndicator = "C" and/or "D", a hard error should trigger if FABS can't locate the unique combination of FAIN, URI, AwardModificationAmendmentNumber and AwardingSubTierAgencyCode present in that correction record row.

  • If it does locate a previously published record with that key, there is no hard error, and if published the row should correct the record in the database sharing that unique key (no change from current practice.

  • If it does not locate a previously published record with that key, it triggers a hard error for that row. This error should have a FABS label and be printed in the error file attached to the submission.

Done

Assignee

Alisa Burdeyny

Reporter

Ross Williford

Labels

None

Service Desk Ticket Link

None

Story Points

1

Epic Link

Sprint

None

Priority

Medium