Function Transfer Ready DtTm vs status: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
{{Data Integrity Check
{{Data Integrity Check
| DIC_summary = If [[Transfer_Ready_DtTm]] is blank, [[TR_info_status]] must not be; if [[TR_info_status]] has content,  [[Transfer_Ready_DtTm]] must be blank.  
| DIC_summary = If [[Transfer_Ready_DtTm]] is blank, [[TR_info_status]] must not be; if [[TR_info_status]] has content,  [[Transfer_Ready_DtTm]] must be blank.  
| DIC_related_concepts = Transfer_Ready_DtTm; TR_info_status; function Transfer_Ready_DtTm_vs_status
| DIC_related_concepts = Transfer_Ready_DtTm; TR_info_status
| DIC_firmness = hard check
| DIC_firmness = hard check
| DIC_timing = complete
| DIC_timing = complete

Revision as of 21:16, 26 October 2018

Data Integrity Checks
Summary: If Transfer_Ready_DtTm is blank, TR_info_status must not be; if TR_info_status has content, Transfer_Ready_DtTm must be blank.
Related: Transfer_Ready_DtTm, TR_info_status
Firmness: hard check
Timing: complete
App: CCMDB.mdb
Coding: function Transfer_Ready_DtTm_vs_status
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: 2016-05-01
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:

Related articles

Related articles: