Query check no consecutive same BL or Service: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
No edit summary |
||
| Line 10: | Line 10: | ||
}} | }} | ||
{{Discuss | | {{Discuss | | ||
* Lisa, would there be a concern if I implemented this? [[User:Ttenbergen|Ttenbergen]] 13:27, 2022 March 23 (CDT) | * Lisa, would there be a concern if I implemented this? [[User:Ttenbergen|Ttenbergen]] 13:27, 2022 March 23 (CDT) | ||
*Should be fine, we'll hear about it if there are issues [[User:Lkaita|Lisa Kaita]] 12:50, 2022 April 13 (CDT) | |||
}} | }} | ||
Revision as of 11:50, 13 April 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: |