PL 2Phin Fake or Blank: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
{{Data Integrity Check | {{Data Integrity Check | ||
|DIC_summary=Finds blank [[PHIN]]s and those entered to meet [[function Validate_PHIN]] so [[Data Processor]] can apply [[PseudoPHIN]]. | |DIC_summary=Finds blank [[PHIN]]s and those entered to meet [[function Validate_PHIN]] so [[Data Processor]] can apply [[PseudoPHIN]] via [[Generating PseudoPHINs]]. | ||
|DIC_related_concepts=PHIN field | |DIC_related_concepts=PHIN field | ||
|DIC_firmness=hard check | |DIC_firmness=hard check | ||
Revision as of 01:07, 27 October 2018
| Data Integrity Checks | |
| Summary: | Finds blank PHINs and those entered to meet function Validate_PHIN so Data Processor can apply PseudoPHIN via Generating PseudoPHINs. |
| Related: | PHIN field |
| Firmness: | hard check |
| Timing: | always |
| App: | Centralized data front end.accdb |
| Coding: | query PL_2Phin_Fake_or_Blank |
| Uses L Problem table: | not entered |
| Status: | implemented |
| Implementation Date: | not entered |
| Backlogged: | true |
Related articles
| Related articles: |