Function Validate Transfer Ready DtTm: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m Text replacement - "cross checks" to "cross checks" |
||
| Line 10: | Line 10: | ||
}} | }} | ||
Retired with the [[Transfer Ready DtTm]], see [[Transfer Ready DtTm tmp entry]] for new collection scheme and any applicable cross | Retired with the [[Transfer Ready DtTm]], see [[Transfer Ready DtTm tmp entry]] for new collection scheme and any applicable [[cross check]]s. | ||
== Related articles == | == Related articles == | ||
{{Related Articles}} | {{Related Articles}} | ||
[[Category:Registry checks]] | [[Category:Registry checks]] | ||
Latest revision as of 14:27, 20 June 2025
| 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 |
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: |