Edit Data Integrity Check: PL 2Phin Fake or Blank

Are you logged on?

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: CCMDB_legit.

Summary (what is the check, one-liner):
links to related pages:
Firmness (is this a warning only (soft check) or will it stop sending (hard check) - applicable only in CCMDB.accdb app):	None/unknown hard check soft check
Timing (does this query run for all records or only complete ones):	None/unknown complete always
Name of the function or query this is implemented as:	query ''PL_2Phin_Fake_or_Blank''
Implementation date:
Implementation Status:
L_Problem (are false positive special cases addressed in table L_Problems - applicable only in CFE):	None/unknown yes no
App:
Backlogged (is this query cleaned up to date or backlogged? Applicable only in CFE):

Free text:

=== [["cannot open any more tables" in Access]] === See [["cannot open any more tables" in Access]] === 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 [[PseudoPHIN]]s. So, this query needs to include incompletes, even if they won't ''usually'' need to be acted on. == Related articles == {{Related Articles}} [[Category:Registry checks]] [[Category:PL queries]] [[Category:Data Processing]]

Explain your edit, if you think it needs explanation (e.g. "as discussed with ...", or "content moved to ...", or "duplicate content, see ..."):

This is a minor edit

Watch this page

Cancel

Edit Data Integrity Check: PL 2Phin Fake or Blank

Navigation menu

Search