Query check no consecutive same BL or Service: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
No edit summary
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
{{Data Integrity Check
{{Data Integrity Check
| DIC_summary = Check that there are no identical Boarding Locs or Services without a different one with a time stamp in between those two.  
|DIC_summary=Check that there are no two identical Boarding Locs or Services without a different one with a time stamp in between those two.
| DIC_related_concepts = Boarding Loc; Service tmp entry
|DIC_related_concepts=Boarding Loc; Service tmp entry
| DIC_firmness = hard check
|DIC_firmness=hard check
| DIC_timing = always
|DIC_timing=always
| DIC_app = CCMDB.accdb
|DIC_coding=query check_no_consecutive_same_BL_or_Service
| DIC_coding = query check_no_consecutive_same_BL_or_Service
|DIC_implementation_date=2022-12-01
| DIC_status = ready to implement
|DIC_status=implemented
| DIC_implementation_date = date change was rolled out / first applied
|DIC_app=CCMDB.accdb
|DIC_backlogged=No
}}
}}
== Log ==
* 2022-12-01 - implemented query


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

Latest revision as of 11:56, 1 December 2022

Data Integrity Checks
Summary: Check that there are no two identical Boarding Locs or Services without a different one with a time stamp in between those two.
Related: Boarding Loc, Service tmp entry
Firmness: hard check
Timing: always
App: CCMDB.accdb
Coding: query check_no_consecutive_same_BL_or_Service
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: 2022-12-01
Backlogged: No
  • Cargo


  • SMW


  • Categories:  
  • form:

Log

  • 2022-12-01 - implemented query

Related articles

Related articles: