Edit Data Integrity Check: Query check tmp service or location duplicate

Summary (what is the check, one-liner):
links to related pages:	Service tmp entryBoarding Loc (Boarding_Loc) ×Service tmp entry ×Boarding Loc (Boarding_Loc)
Firmness (is this a warning only (soft check) or will it stop sending (hard check) - applicable only in CCMDB.accdb app):	None/unknown  hard check  soft check
Timing (does this query run for all records or only complete ones):	None/unknown  complete  always
Name of the function or query this is implemented as:	query ''check_tmp_service_or_location_duplicate''
Implementation date:
Implementation Status:	needs reviewready to implementimplementednot enterednot feasibledeclinedretired
L_Problem (are false positive special cases addressed in table L_Problems - applicable only in CFE):	None/unknown  yes  no
App:	CCMDB.accdbCentralized data front end.accdbTISS28.accdbSAPDSM Labs Consistency check.accdb
Backlogged (is this query cleaned up to date or backlogged? Applicable only in CFE):

Free text:

This is similar to [[query check_tmp_2_BL_TR_S_same_tm]]. == Log == * 2022-03-09 - confirmed that this will also catch when there are two different boarding loc entries with the same dttm * 2021-09-02 - removed "item" from listing since we don't allow duplicates even if the item is different, and removed the exclusion of ER records from check * 2021-05-04 - changed query to catch a scenario I had not thought of earlier * 2021-01-15 - check implemented == Related articles == {{Related Articles}} [[Category:Tmp check]]

Save page Show preview Show changes Cancel