Function Validate Transfer Ready DtTm: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Newer edit →
Created page with "{{Data Integrity Check | DIC_summary = doesn't allow violation of function Transfer_Ready_DtTm_vs_status | DIC_related_concepts = Dispo field, function Transfer_Read..."
 
mNo edit summary
Line 1: Line 1:
{{Data Integrity Check
{{Data Integrity Check
| DIC_summary = doesn't allow violation of [[function Transfer_Ready_DtTm_vs_status]]
| DIC_summary = doesn't allow violation of [[function Transfer_Ready_DtTm_vs_status]]
| DIC_related_concepts = [[Dispo field]], [[function Transfer_Ready_DtTm_vs_status]]
| DIC_related_concepts = [[Transfer_Ready_DtTm]], [[function Transfer_Ready_DtTm_vs_status]]
| DIC_firmness = hard check
| DIC_firmness = hard check
| DIC_timing = complete
| DIC_timing = complete

Revision as of 13:27, 2018 September 25

Data Integrity Checks
Summary: doesn't allow violation of function Transfer_Ready_DtTm_vs_status
Related: [[Transfer_Ready_DtTm, function Transfer_Ready_DtTm_vs_status]]
Firmness: hard check
Timing: complete
App: CCMDB.mdb
Coding: function Validate Dispo
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 (CCMDB.accdb, Centralized data front end.accdb, TISS28.accdb, SAP, DSM Labs Consistency check.accdb, not entered) of allowed values for the "DICApp" property. Property "DICRelatedConcepts" (as page type) with input value "Transfer_Ready_DtTm]], [[function Transfer_Ready_DtTm_vs_status" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Categories:  
  • form:

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Function_Validate_Transfer_Ready_DtTm&oldid=120152"