Edit Data Integrity Check: Query s tmp check combined Boarding Loc and TransferReadyDtTm

Are you logged on?

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: CCMDB_legit.

Summary (what is the check, one-liner):
links to related pages:
Firmness (is this a warning only (soft check) or will it stop sending (hard check) - applicable only in CCMDB.accdb app):	None/unknown hard check soft check
Timing (does this query run for all records or only complete ones):	None/unknown complete always
Name of the function or query this is implemented as:	query s_tmp_check_combined_Boarding_Loc_and_TransferReadyDtTm
Implementation date:
Implementation Status:
L_Problem (are false positive special cases addressed in table L_Problems - applicable only in CFE):	None/unknown Yes No
App:
Backlogged (is this query cleaned up to date or backlogged? Applicable only in CFE):

Free text:

{{DT| * This doesn't catch duplicate [[Transfer Ready DtTm tmp entry]] for [[Boarding Loc]] on incompletes. That is probably fine since we don't use the incompletes, but it could be added the next time the check is worked on anyway. }} == Log == 2021-03-31 implemented == Log == * 2021-04-07 - changed query to also accept a null as match; for profiles where there is more than one pair, [[query s_tmp_check_Boarding_Loc_and_TransferReadyDtTm_pairs]] will flag those. * 2021-04-01 - initial implementation had mistake and lots of false-positives, fixed * 2021-03-31 - initial implementation == Related articles == {{Related Articles}} [[Category:Tmp check]]

Explain your edit, if you think it needs explanation (e.g. "as discussed with ...", or "content moved to ...", or "duplicate content, see ..."):

This is a minor edit

Watch this page

Cancel