Function Validate Dispo: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Created page with "{{Data Integrity Check | DIC_summary = doesn't allow empty, or violation of function Transfer_Ready_DtTm_vs_status | DIC_related_concepts = Dispo field, function Tra..."
 
Line 1: Line 1:
{{Data Integrity Check
{{Data Integrity Check
| DIC_summary = doesn't allow empty, or violation of [[function Transfer_Ready_DtTm_vs_status]]
| DIC_summary = doesn't allow empty
| DIC_related_concepts = [[Dispo field]], [[function Transfer_Ready_DtTm_vs_status]]
| DIC_related_concepts = [[Dispo field]]
| DIC_firmness = hard check
| DIC_firmness = hard check
| DIC_timing = complete
| DIC_timing = complete
Line 9: Line 9:
| DIC_implementation_date = 2016-05-01
| DIC_implementation_date = 2016-05-01
}}
}}


== Related articles ==
== Related articles ==
{{Related Articles}}
{{Related Articles}}

Revision as of 13:29, 25 September 2018

Data Integrity Checks
Summary: doesn't allow empty
Related: [[Dispo field]]
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 (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: