Query check transfer ready tmp for each Boarding Loc: Difference between revisions

Revision as of 11:11, 2021 March 31

Data Integrity Checks
Summary:	There should be a Transfer Ready DtTm tmp entry for each Boarding Loc entry of a profile
Related:	Transfer Ready DtTm tmp entry, Boarding Loc
Firmness:	hard
Timing:	complete
App:	CCMDB.accdb
Coding:	query check_transfer_ready_tmp_for_each_Boarding_Loc
Uses L Problem table:	not relevant for this app
Status:	retired
Implementation Date:	2021-02-04
Backlogged:	true

2021-03-31 - retired, replaced by query check_transfer_ready_tmp_one_per_Boarding_Loc
2021-02-04 - implemented after clarification of Transfer Ready DtTm tmp entry
2021-01-28 - defined

@@ Line 6: / Line 6: @@
 | DIC_app = CCMDB.accdb
 | DIC_coding = query ''check_transfer_ready_tmp_for_each_Boarding_Loc''
-| DIC_status = needs review
+| DIC_status = retired
 | DIC_implementation_date = 2021-02-04
 }}
-The count of [[Boarding Loc]] should be the same as the count of [[Transfer Ready DtTm tmp entry]]. This means there could be several undated transfer ready entries with check boxes/comments but no dates/times.
+Replaced by more comprehensive check [[query check_transfer_ready_tmp_one_per_Boarding_Loc]]
-A direct one-on-one match is not possible since there is nothing to identify the undated entries to a specific [[Boarding Loc]], so an identical count will be used as an approximation.
-{{TT | Once [[query check_transfer_ready_tmp_one_per_Boarding_Loc]] is implemented, this one can go away since it checks a subset of that. }}
 == Log ==
+* 2021-03-31 - retired, replaced by [[query check_transfer_ready_tmp_one_per_Boarding_Loc]]
 * 2021-02-04 - implemented after clarification of [[Transfer Ready DtTm tmp entry]]
 * 2021-01-28 - defined