Query s tmp Borrow sensible DtTm vs no borrow

Revision as of 18:07, 22 January 2019 by Ttenbergen (talk | contribs) (Created page with "{{Data Integrity Check |DIC_summary=Checks that data for Project Borrow arrive follows that project's |DIC_related_concepts=Project Borrow arrive |DIC_firmness=hard check...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Data Integrity Checks
Summary: Checks that data for Project Borrow arrive follows that project's
Related: Project Borrow arrive
Firmness: hard check
Timing: complete
App: CCMDB.mdb
Coding: not entered
Uses L Problem table: not relevant for this app
Status: ready to implement
Implementation Date: not entered
Backlogged: true
  • Cargo


  • SMW
"CCMDB.mdb" is not in the list (SAP, not entered, Centralized data front end.accdb, DSM Labs Consistency check.accdb, CCMDB.accdb, TISS28.accdb) of allowed values for the "DICApp" property. 
  • Categories:  
  • form:

query s_tmp_Borrow_duplicates

query s_tmp_Borrow_sensible_DtTm_vs_no_borrow


Sensible DtTm vs no borrow

(start_dt, start_tm) outside of admission time

If

or

then give a hard error. This can't be.

has to either have location and time or "no borrow" checked

all in header...

can't have "no borrow" in item but have (start_dt, start_tm)

Related articles

Related articles: