Query check tmp generate allowed: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
{{Data Integrity Check
{{Data Integrity Check
| DIC_summary = check that [[:Category:Project|tmp]] project/item combo exists for this location in [[Overstay]]
| DIC_summary = check that [[:Category:Project|tmp]] project/item combo exists for this location in [[Overstay]]
| DIC_related_concepts = Overstay
| DIC_related_concepts = Overstay, Overstay Predictor Project
| DIC_firmness = hard check  
| DIC_firmness = hard check  
| DIC_timing =
| DIC_timing =

Revision as of 22:38, 2 January 2019

Data Integrity Checks
Summary: check that tmp project/item combo exists for this location in Overstay
Related: Overstay, Overstay Predictor Project
Firmness: hard check
Timing:
App: CCMDB.mdb
Coding: query check tmp generate allowed, Sub GenerUpdate_tmp_entry
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: date change was rolled out / first applied
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:

Related articles

Related articles:

called by Sub GenerUpdate_tmp_entry which is used by the overstay project to generate colour entries in tmp.