Query check CCI Component unfilled: 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 = [[CCI Component]] entry with missing [[Px_Type]], [[Px_Count]], [[Px_Date]] if acquired
| DIC_summary = [[CCI Component]] entry with missing px, [[Px_Type]] or [[Px_Count]]
| DIC_related_concepts = [[CCI Picklist]], [[Px Type]], [[Px_Date]], [[Px_Count]]
| DIC_related_concepts = [[CCI Component]], [[Px Type]], [[Px_Count]]
| DIC_firmness = hard check  
| DIC_firmness = hard check  
| DIC_timing = complete
| DIC_timing = complete
Line 9: Line 9:
| DIC_implementation_date =  
| DIC_implementation_date =  
}}
}}
This check is the counterpart of [[Query check CCI Picklist unfilled]].


== Related articles ==
== Related articles ==

Revision as of 16:46, 14 October 2018

Data Integrity Checks
Summary: CCI Component entry with missing px, Px_Type or Px_Count
Related: [[CCI Component, Px Type, Px_Count]]
Firmness: hard check
Timing: complete
App: CCMDB.mdb
Coding: query check CCI_Component_unfilled
Uses L Problem table: not relevant for this app
Status: ready to implement
Implementation Date:
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. Property "DICRelatedConcepts" (as page type) with input value "CCI Component]], Px Type, [[Px_Count" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Categories:  
  • form:

This check is the counterpart of Query check CCI Picklist unfilled.

Related articles

Related articles: