Query s tmp Borrow duplicates: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
m No duplicates: the fact that there can;t be duplicate start Dttms already implies that there can't be duplicate complete-twins, so taking that requirement out.
Line 11: Line 11:


== No duplicates ==
== No duplicates ==
=== can't have two entries that are exactly the same ===
=== can't have two different entries that have same (start_dt, start_tm)===
Can't have two identical entries.  
Can't have two different entries in item with same (start_dt, start_tm) per D_ID.


=== can't have two different entries that have same (start_dt, start_tm)===
Can't have two different entries in item with same (start_dt, start_tm) per D_ID.
== Related articles ==
== Related articles ==
{{Related Articles}}
{{Related Articles}}


[[Category:Tmp check‎‎‎]]
[[Category:Tmp check‎‎‎]]

Revision as of 08:05, 24 January 2019

Data Integrity Checks
Summary: Checks that data for Project Borrow arrive follows that project's
Related: Project Borrow arrive
Firmness: hard check
Timing: complete
App: CCMDB.mdb
Coding: query s_tmp_Borrow_duplicates
Uses L Problem table: not relevant for this app
Status: ready to implement
Implementation Date: not entered
Backlogged: true
  • Cargo


  • SMW
"CCMDB.mdb" is not in the list (SAP, not entered, Centralized data front end.accdb, DSM Labs Consistency check.accdb, CCMDB.accdb, TISS28.accdb) of allowed values for the "DICApp" property. 
  • Categories:  
  • form:

No duplicates

can't have two different entries that have same (start_dt, start_tm)

Can't have two different entries in item with same (start_dt, start_tm) per D_ID.

Related articles

Related articles: