Function Validate Transfer Ready DtTm: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m (Ttenbergen moved page Function Validate Validate Transfer Ready DtTm to Function Validate Transfer Ready DtTm without leaving a redirect)
mNo edit summary
 
(3 intermediate revisions by the same user not shown)
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 = [[Transfer_Ready_DtTm]], [[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
| DIC_app = CCMDB.mdb
| DIC_app = CCMDB.accdb
| DIC_coding = function ''Validate Dispo''
| DIC_coding = function ''Validate_Transfer_Ready_DtTm''
| DIC_status = implemented
| DIC_status = retired
| DIC_implementation_date = 2016-05-01
| DIC_implementation_date = 2016-05-01
}}
}}
Retired with the [[Transfer Ready DtTm]], see [[Transfer Ready DtTm tmp entry]] for new collection scheme and any applicable cross checks.


== Related articles ==
== Related articles ==
{{Related Articles}}
{{Related Articles}}
[[Category:Registry checks]]

Latest revision as of 23:21, 2020 October 15

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.accdb
Coding: function Validate_Transfer_Ready_DtTm
Uses L Problem table: not relevant for this app
Status: retired
Implementation Date: 2016-05-01
Backlogged: true
  • Cargo


  • SMW


  • Categories: 
  • form:

Retired with the Transfer Ready DtTm, see Transfer Ready DtTm tmp entry for new collection scheme and any applicable cross checks.

Related articles

Related articles: