Query s tmp project item consistent: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m Text replacement - "DIC_timing = complete always" to "DIC_timing ="
mNo edit summary
Line 1: Line 1:
{{Data Integrity Check
{{Data Integrity Check
| DIC_summary = Checks that tmp project entries only contain combinations of project and item that are allowed.  
| DIC_summary = Checks that tmp project entries only contain combinations of project and item that are allowed.  
| DIC_related_concepts = [[Tmp Project Collection]]
| DIC_related_concepts = Tmp Project Collection
| DIC_firmness = hard check
| DIC_firmness = hard check
| DIC_timing =
| DIC_timing =
Line 15: Line 15:


[[Category:TmpV2]]
[[Category:TmpV2]]
[[Category:Tmp check]]

Revision as of 13:54, 28 October 2018

Data Integrity Checks
Summary: Checks that tmp project entries only contain combinations of project and item that are allowed.
Related: Tmp Project Collection
Firmness: hard check
Timing:
App: CCMDB.mdb
Coding: function TmpChecker, query s tmp project item consistent
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: 2014-01-01
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:

approximate implementation date; this woudl have been implemented when we first went to the tmp coding we do now.

Related articles

Related articles: