Query Check BL TR combiner null

From CCMDB Wiki
Revision as of 09:17, 13 July 2022 by Ttenbergen (talk | contribs) (Created page with "{{Data Integrity Check |DIC_summary=Checks that all Boarding Loc / Transfer Ready DtTm tmp entry pairs have a non-null combiner integer. |DIC_related_concepts= Transfer Ready DtTm tmp entry; Boarding Loc |DIC_firmness=hard check |DIC_coding=Query check_BL_TR_combiner_null |DIC_status=ready to program |DIC_app=CCMDB.accdb |DIC_backlogged=No }} Checks that all Boarding Locs and Transfer Ready DtTm tmp entrys have non-null combiners. Query check transfer...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
Data Integrity Checks
Summary: Checks that all Boarding Loc / Transfer Ready DtTm tmp entry pairs have a non-null combiner integer.
Related: Transfer Ready DtTm tmp entry, Boarding Loc
Firmness: hard check
Timing: always
App: CCMDB.accdb
Coding: Query check_BL_TR_combiner_null
Uses L Problem table: not relevant for this app
Status: ready to program
Implementation Date: not entered
Backlogged: No
  • Cargo


  • SMW

"ready to program" is not in the list (needs review, ready to implement, implemented, not entered, not feasible, declined, retired) of allowed values for the "DICStatus" property.

  • Categories:  
  • form:

Checks that all Boarding Locs and Transfer Ready DtTm tmp entrys 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 - working on

Related Articles

Related articles: