Edit Data Integrity Check: Query Check BL TR combiner null

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 check_BL_TR_combiner_null
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:

Checks that all [[Boarding Loc]]s and [[Transfer Ready DtTm tmp entry]]s have non-null combiners. [[Query check transfer ready tmp for each Boarding Loc]] checks that they are paired, but it turns out a common null also satisfies that check, but would later cause problems with the data. ==Log== * 2022-07-13 - implemented == Related Articles == {{Related Articles}} [[Category:Admit/Discharge]] [[Category:Transfer Ready]]

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