DataFlux Data Management Studio 2.7: User Guide
Element status values give a detailed explanation of the outcome of the validation operation. They are meaningful only after a validation operation has been performed, even though some information is available after a parsing operation for the “ElementInputStatus” value.
Twenty address elements are covered in both, “ElementInputStatus” and “ElementResultStatus”. The former provides per element information on the matching of input elements to reference data, while the latter categorizes the result in more detail than the overview ProcessStatus values. These values are returned by setting an output type of DATAPARAMETER and a “Name” of “ElementInputStatus” and “ElementResultStatus”.
The element positions (from left to right) are, where level 0 pertains to the Item 1 status information, while level 1 summarizes the status information on Items 2-6 (see chapter 5.9 on address element items):
| Element Position | Status Information |
|---|---|
| 1 | PostalCode level 0 |
| 2 | PostalCode level 1 (e.g. ZIP+4 – Plus 4 addition) |
| 3 | Locality level 0 |
| 4 | Locality level 1 (e.g. Urbanisation, Dependent Locality) |
| 5 | Province level 0 |
| 6 | Province level 1 (e.g. Sub Province) |
| 7 | Street level 0 |
| 8 | Street level 1 (e.g. Dependent street) |
| 9 | Number level 0 |
| 10 | Number level 1 |
| 11 | Delivery service level 0 (e.g. PO Box, GPO, Packstation, Private Bags) |
| 12 | Delivery service level 1 |
| 13 | Building level 0 |
| 14 | Building level 1 |
| 15 | SubBuilding level 0 |
| 16 | SubBuilding level 1 |
| 17 | Organisation level 0 |
| 18 | Organisation level 1 |
| 19 | Country level 0 (Mother country) |
| 20 | Country level 1 (e.g. Territory) |
The possible values for validation are:
| Value | Status | Status Information |
|---|---|---|
| 0 | empty | |
| 1 | not found | |
| 2 | not checked (no reference data) | |
| 3 | wrong - Set by validation only | The reference database suggests that either Number or DeliveryService is out of valid number range. Input is copied, not corrected for batch mode. |
| 4 | matched with errors in this element | |
| 5 | matched with changes (inserts or deletes) |
For example:
|
| 6 | matched without errors |
For parsing, the following values are possible:
| Value | Parsing Status |
|---|---|
| 0 | empty |
| 1 | element had to be relocated |
| 2 | matched but needed to be normalized |
| 3 | matched and OK |
Is set only after validation as an indication whether verification (“verified”) or correction (“changed”) were possible or not, the potential values are (for all address elements apart from country):
| Value | Results Status |
|---|---|
| 0 | empty |
| 1 | not validated and not changed. Original is copied. |
| 2 | not validated but standardized. |
| 3 | validated but not changed due to invalid input, database suggests that number is out of valid ranges. Input is copied, not corrected – this status value is set only in batch mode. |
| 4 | validated but not changed due to lack of reference data. |
| 5 | validated but not changed due to multiple matches. Only set in batch mode, otherwise multiple suggestions that replace the input are marked as corrected (status value 7). |
| 6 | validated and changed by eliminating the input value |
| 7 | validated and changed due to correction based on reference data |
| 8 | validated and changed by adding value based on reference data |
| 9 | validated, not changed, but delivery status not clear (e.g. DPV value wrong; given number ranges that only partially match reference data). |
| C | validated, verified but changed due to outdated name |
| D | validated, verified but changed from exonym to official name |
| E | validated, verified but changed due to standardization based on casing or language. |
| Validation only sets this status if input fully matches a language alternative. | |
| F | validated, verified and not changed due to perfect match |
For Country (position 19 & 20), the following values are possible:
| Value | Status |
|---|---|
| 0 | empty |
| 1 | Country not recognized |
| 4 | Country recognized from DefaultCountryISO3 setting |
| 5 | Country not recognized - multiple matches |
| 6 | Country recognized from script |
| 7 | Country recognized from format |
| 8 | Country recognized from major town |
| 9 | Country recognized from province |
| C | Country recognized from territory |
| D | Country recognized from name with errors |
| E | Country recognized from name without errors |
| F | Country recognized from ForceCountryISO3 setting |
In addition to the element status values described previously, information is available on which of the address elements of the address processed are actually relevant from the local postal operator’s point of view. This is retrieved by adding an output type of DATAPARAMETER with a name of “ElementRelevance”. The possible values for each address element are “1” for relevant and “0” otherwise.
For any given address, all address elements with a value of “1” must be present for an output address to be deemed valid by the local postal authority. “ElementRelevance” may well vary from address to address for countries with different address types, e.g. rural versus metropolitan addressing. Furthermore, AddressElements that have actually been validated against reference data (i.e. with a ElementResultStatus of 7 and higher) may override the default ElementRelevance value defined for that AddressElement.
Please note that “ElementRelevance” is really meaningful only for a “ProcessStatus” value of Cx or Vx.
|
Documentation Feedback: yourturn@sas.com
|
Doc ID: dfDMStd_Task_World2_Element.html |