Check function location NE dispo: 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 = [[Service/Location field]] can't be same as [[Dispo field]]
|DIC_summary=[[Service/Location field]] can't be same as [[Dispo field]]
| DIC_related_concepts = Service/Location field; Dispo field
|DIC_related_concepts=Service/Location field; Dispo field
| DIC_firmness = hard check
|DIC_firmness=hard check
| DIC_timing = complete
|DIC_timing=complete
| DIC_app = CCMDB.mdb
|DIC_coding=location_NE_dispo()
| DIC_coding = location_NE_dispo()
|DIC_implementation_date=2016-12-31
| DIC_status = implemented
|DIC_status=implemented
| DIC_implementation_date = 2016-12-31
|DIC_LProblem=No
|DIC_app=CCMDB.mdb
}}
}}
== Log ==
== Log ==
2019-01-07
2019-01-07

Revision as of 14:07, 7 January 2019

Data Integrity Checks
Summary: Service/Location field can't be same as Dispo field
Related: Service/Location field, Dispo field
Firmness: hard check
Timing: complete
App: CCMDB.mdb
Coding: location_NE_dispo()
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: 2016-12-31
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:

Log

2019-01-07

  • updated so they will work with the workload sharing locations