Check function previous NE Location: 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 = [[Previous Location field]] can't be same as [[Service/Location field]]
|DIC_summary=[[Previous Location field]] can't be same as [[Service/Location field]]
| DIC_related_concepts = Service/Location field; Previous Location field
|DIC_related_concepts=Service/Location field; Previous Location field
| DIC_firmness = hard check
|DIC_firmness=hard check
| DIC_timing = complete
|DIC_timing=complete
| DIC_app = CCMDB.mdb
|DIC_coding=function previous_NE_Location()
| DIC_coding = function previous_NE_Location()
|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, 2019 January 7

Data Integrity Checks
Summary: Previous Location field can't be same as Service/Location field
Related: Service/Location field, Previous Location field
Firmness: hard check
Timing: complete
App: CCMDB.mdb
Coding: function previous_NE_Location()
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 (CCMDB.accdb, Centralized data front end.accdb, TISS28.accdb, SAP, DSM Labs Consistency check.accdb, not entered) of allowed values for the "DICApp" property.
  • Categories: 
  • form:

Log

2019-01-07

  • updated so they will work with the workload sharing locations
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Check_function_previous_NE_Location&oldid=133676"