Query check no consecutive same BL or Service: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
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 |
Revision as of 12:28, 23 March 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: | needs review |
Implementation Date: | not entered |
Backlogged: | No |
|
Related articles
Related articles: |