Listware Online:NCOALink Equivalent Result Codes: Difference between revisions
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
{{CustomTOC}} | {{CustomTOC}} | ||
==Equivalent Result Codes== | |||
The table below is useful for Listware Classic or Mailers+4 Desktop users that have transitioned to Listware Online for NCOA<sup>Link</sup> processing and want to obtain the equivalent '''Mail Score''' result codes in Listware Online - NCOA<sup>Link</sup>. | The table below is useful for Listware Classic or Mailers+4 Desktop users that have transitioned to Listware Online for NCOA<sup>Link</sup> processing and want to obtain the equivalent '''Mail Score''' result codes in Listware Online - NCOA<sup>Link</sup>. | ||
Line 56: | Line 57: | ||
|AEXX Result Codes will have an address error associated with it. | |AEXX Result Codes will have an address error associated with it. | ||
|- | |- | ||
|colspan="2"|CM02 to CM21 is comparable to Return/Nixie codes that will get a Mailscore of 7. | |colspan="2"|'''CM02 to CM21''' is comparable to Return/Nixie codes that will get a Mailscore of 7. | ||
|- | |- | ||
|CM02 | |CM02 |
Revision as of 00:29, 9 July 2022
Equivalent Result Codes
The table below is useful for Listware Classic or Mailers+4 Desktop users that have transitioned to Listware Online for NCOALink processing and want to obtain the equivalent Mail Score result codes in Listware Online - NCOALink.
For a complete list of current SmartMover result codes, please see the SmartMover V3 Result Code List.
Listware Classic & Mailers+4 Desktop Mail Score Result Codes |
Listware Online Equivalent Result Codes returned in the md_Results field.
| ||
---|---|---|---|
Code | Description | Code | Description |
1 | NCOA move found and supplied a new mailing address which also matches DPV. | CS01 | Move with New Address The record is a 'move' and a new 'moved to' address was provided. |
2 | This is a newly supplied address based off of Return Codes 91 and 92. The address is accurate enough to match DPV and supplied a new mailing address which also matches DPV.
Return Code: 91 – Secondary Number dropped from COA. The input record matched to a master file record. The master file record had a secondary number and the input address did not. Please Note: This return code is derived from Individual matching logic only. If this return code is achieved then no other matching attempts are permitted regardless of the PROCESSING mode. Return Code: 92 – Secondary Number dropped from Input Address The input record matched to a master file record, but the input address had a secondary number and the master file record did not. The record is a ZIP + 4 street level match. Please Note: This return code is derived from individual matching logic only. If this return code is achieved then no other matching attempts are permitted regardless of the PROCESSING mode. |
CM22 | Input Missing Suite Input address missing suite data. Can still be matched. |
CM23 | Secondary Dropped from Input The secondary number was dropped from the input address. | ||
3 | Submitted record is not a move but was standardized. | CS02 | Standardized Address The record is not a 'move' but was standardized. |
4 | Not currently coded in updated score system. | ||
5 | Not currently coded in updated score system. | ||
6 | Not currently coded in updated score system. | ||
7 | Serious problems prevent the address from matching Delivery Point Validation (DPV) and ZIP+4. Or Possible Canadian/Foreign Address, Record Not Processed and usually flagged with an ADDERR or a poor Return Code. | AEXX | AEXX Result Codes will have an address error associated with it. |
CM02 to CM21 is comparable to Return/Nixie codes that will get a Mailscore of 7. | |||
CM02 | Foreign Move A COA was found for a Foreign Move. No forwarding address was provided. | ||
CM03 | Moved no Forwarding A COA was found. The customer moved and left no forwarding address (MLNA). | ||
CM04 | Box Closed A COA was found. The Post Box was closed with no order filed by the customer (BCNO). | ||
CM05 | Cannot Match Secondary The COA could not be matched because the street address does not match with the secondary number. | ||
CM06 | DPBC Ambiguous The COA could not be converted to a deliverable address because the 11-digit zip code represents more than one delivery point. | ||
CM07 | Conflicting Middle Name The COA could not be matched because there is more than one COA record for the match and the middle names or initials on the COAs are different. | ||
CM08 | Conflicting Gender The COA could not be matched because there is more than one COA record for the match and the genders of the names on the COAs are different. | ||
CM09 | Conflicting Instructions The COA could not be matched because two potential matches were compared and had differences in the new addresses. | ||
CM10 | Cannot Match High-rise Default The COA could not be matched because the input record is a potential match to a family COA record from a multi-unit building, but the address zip + 4 coded to the building default. This requires individual name matching logic to obtain a match and the individual names did not match. | ||
CM11 | Cannot Match Rural Default The COA could not be matched because the input record is a potential match to a family COA record from a Rural Route or Highway Contract Route address. This requires individual name matching logic to obtain a match and the individual names did not match. | ||
CM12 | Insufficient Name The COA could not be matched because there is a COA record with the same surname and address but there is insufficient first/middle name information on the COA record to product a match using individual matching logic. | ||
CM13 | Middle Name Test Failed The COA could not be matched because the input name contains a conflict with the middle name or initials on the COA record. | ||
CM14 | Gender Conflict The COA could not be matched because the gender of the name on the input record conflicts with the gender of the name on the COA record. | ||
CM15 | Cannot Convert Address The COA was found but the new address would not convert at run time. | ||
CM16 | Individual Name Insufficient The COA could not be matched because the input middle initial/name is missing or does not equal the middle initial/name on the potential COA match. | ||
CM17 | Secondary Discrepancy The COA could not be matched because there is conflicting secondary information on the input and COA record or the input record contained secondary information and matched to a family record that does not contain secondary information. | ||
CM18 | Other Insufficient Name The COA could not be matched because the input middle initial/name is missing or different from the middle name on the COA. A match cannot be made because the first name on the COA was truncated and the middle names must be equal in order to make this match. | ||
CM19 | Cannot Match General Delivery The COA could not be matched for general delivery. | ||
CM20 | No ZIP + 4, Not Confirmable, or Temporary The COA was found but the new address either: does not have a ZIP+4 coded and therefore there is no 11-digit DPBC, the primary number cannot be confirmed on DPV, or is temporary. | ||
CM21 | Conflicting Directions The address could not be updated due to multiple matches. |