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 4: | Line 4: | ||
|DIC_firmness=hard check | |DIC_firmness=hard check | ||
|DIC_coding=query ''PL_2Phin_Fake_or_Blank'' | |DIC_coding=query ''PL_2Phin_Fake_or_Blank'' | ||
|DIC_status= | |DIC_status=implemented | ||
|DIC_app=Centralized data front end.accdb | |DIC_app=Centralized data front end.accdb | ||
}} | }} | ||
Revision as of 14:36, 2021 July 15
| 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 |
.
Can't limit this to RecordStatus completes/sent
This query is used for Generating PseudoPHINs. One requirement there is to make sure that no PHINs are currently < 100000000, even incompletes, since having one of those would mess up our incrementing for PseudoPHINs. So, this query needs to include incompletes, even if they won't usually need to be acted on.
Related articles
| Related articles: |