Multidomain MDM
- Multidomain MDM 10.3 HotFix 3
- All Products
Informatica Address Verification 4 Process Status Value
| Informatica Address Verification 5 Process Status Value
| Description
|
---|---|---|
V
| -
| Verified. The input data is correct.
|
-
| V4
| Verified. The input data is correct. All relevant elements were checked and the input data matched the reference data.
|
-
| V3
| Verified. The input data is correct but some or all elements were standardized or the input contains outdated names or exonyms.
|
-
| V2
| Verified. The input data is correct but some elements could not be verified because of incomplete reference data.
|
-
| V1
| Verified. The input data is correct but incorrect element user standardization has deteriorated deliverability. For example, the postcode length chosen is too short. Not set by validation.
|
C
| -
| Corrected.
|
-
| C4
| Corrected. All relevant elements have been checked.
|
-
| C3
| Corrected. However, some elements could not be checked.
|
-
| C2
| Corrected. However, the delivery status is unclear due to a lack of reference data.
|
-
| C1
| Corrected. However, the delivery status is unclear because user standardization is incorrect. Not set by validation.
|
P3
| -
| Data cannot be corrected, but likely to be deliverable.
|
-
| I4
| Data could not be corrected, but is likely to be deliverable. An address element does not match the single reference value available. For example, the house number is incorrect and there is one house number in the reference data.
|
-
| I3
| Data could not be corrected, but is likely to be deliverable. An address element does not match the multiple reference values available. For example, the house number is incorrect and there is more than one house number in the reference data.
|
P2
| I2
| Data could not be corrected, but there is a slim chance that the address is deliverable.
|
P1
| I1
| Data cannot be corrected and unlikely to be deliverable.
|
-
| N5
| Validation Error. Validation was not performed because the reference database is too old. Contact
Informatica Address Verification to get updated reference data.
|
N4
| -
| Validation method not yet called after parsing operation.
|
-
| N4
| Validation Error. Validation was not performed because the reference database is corrupted or in the wrong format.
|
N3
| N3
| Validation Error. Validation was not performed because the country could not be unlocked.
|
N2
| N2
| Validation Error. Validation was not performed because the required reference database is not available.
|
N1
| N1
| Validation Error. Validation was not performed because the country was not recognized.
|
Q3
| Q3
| FastCompletion Status. The suggested address is complete.
|
Q2
| Q2
| FastCompletion Status. The suggested address is complete. However, elements were deleted or added from the input.
|
Q1
| Q1
| FastCompletion Status. The suggested address is not complete. Enter more information.
|
Q0
| Q0
| FastCompletion Status. Suggestions cannot be generated. The input data is insufficient.
|
-
| S4
| Parsed perfectly.
|
-
| S3
| Parsed with multiple results.
|
-
| S2
| Parsed with errors. Elements changed position.
|
-
| S1
| Parse error. Input format mismatch.
|
-
| RB
| Country recognized from abbreviation.
|
-
| RA
| Country recognized from ForceCountryISO3 setting.
|
-
| R9
| Country recognized from DefaultCountryISO3 setting.
|
-
| R8
| Country recognized from name without errors.
|
-
| R7
| Country recognized from name with errors.
|
-
| R6
| Country recognized from territory.
|
-
| R5
| Country recognized from province.
|
-
| R4
| Country recognized from major town.
|
-
| R3
| Country recognized from format.
|
-
| R2
| Country recognized from script.
|
-
| R1
| Country not recognized. Multiple matches.
|
-
| R0
| Country not recognized.
|