Parameter |
Description |
---|---|
Option.PerformUSProcessing |
Specifies whether to process U.S. addresses. If you enable U.S. address processing ValidateAddress will attempt to validate U.S. addresses. If you disable U.S. address processing, U.S. addresses will fail, meaning they are returned with an "F" in the Status output field. The output field Status.Code will say "DisabledCoder." If you are not licensed for U.S. address processing you must disable U.S. address processing in order for your jobs to complete successfully, regardless of whether or not they contain U.S. addresses. Note: You must have a valid license for U.S. address
processing to successfully process U.S. addresses. If you enable
U.S. address processing but are not licensed for this feature,
or your license has expired, you will receive an error.
|
Option.Database.US |
Specifies which database to use for validating U.S. addresses. Only databases that have been defined in the US Database Resources panel in the Management Console are available. |
Option.PerformLOT |
Enhanced Line of Travel (eLOT) processing assigns a Line of Travel sequence code to your addresses. Note that addresses are not sorted into eLOT sequence but they are assigned a Line of Travel sequence code that allows you to sort addresses into eLOT sequence. To perform eLOT processing you must have the eLOT database installed.
For a listing of the output fields returned by this option, see Enhanced Line of Travel Output. |
Option.PerformRDI |
Residential Delivery Indicator (RDI™) processing checks if an address is a residential address (not a business address). To perform RDI™ processing, you must have the RDI™ database installed. If you enable both DPV® and RDI™ processing, RDI™ information is only returned if the address is a valid delivery point. If DPV® does not validate the address no RDI™ data is returned.
|
Option.PerformESM |
Enhanced Street Matching (ESM) applies additional matching logic to correct misspelled or complex street names and obtain a match. ESM enables more addresses to be validated but it reduces performance. You cannot perform ESM when ASM is enabled.
|
Option.PerformASM |
All Street Matching (ASM) applies ESM processing as well as additional matching logic to correct errors in street names and obtain a match. It is effective at matching streets when the first letter of the street is incorrect. ASM provides the best address validation but reduces performance.
|
Option.PerformDPV |
Delivery Point Validation (DPV®) validates that a specific address exists, as opposed to validating that a specific address is within a range of valid addresses. CMRA processing checks if an address is for a mailbox rented from a private company, referred to as a Commercial Mail Receiving Agent (CMRA). To perform DPV and CMRA processing, you must have the DPV database installed. The DPV database contains both DPV and CMRA data.
For a listing of the output fields returned by this option, see DPV and CMRA Output. |
Option.PerformLACSLink |
The USPS® Locatable Address Conversion System (LACS) allows you to correct addresses that have changed as a result of a rural route address converting to street-style address, a PO Box renumbering, or a street-style address changing. When enabled, LACSLink processing is attempted for addresses that could not be validated, or addresses were validated and flagged for LACSLink conversion. To perform LACSLink processing, you must have the LACSLink database installed.
For a listing of the output fields returned by this option, see LACSLink Output |
Option.PerformEWS |
The Early Warning System (EWS) uses the USPS® EWS File to validate addresses that are not in the ZIP + 4® database. To perform EWS processing, you must have the EWS database installed. If an input address matches an address in the EWS file, the following record-level result indicators are returned:
|
Option.ExtractFirm |
Specifies whether to extract the firm name from AddressLine1 through AddressLine4 and place it in the FirmName output field. This option works in cases where the input record's FirmName field is blank and there is more than one address line.
To identify firm names in address lines, the address lines are scanned for keywords and patterns that identify which fields are address lines and which are FirmName lines. Since this is done based on patterns, fields may be misidentified. The following tips can help ensure optimal firm extraction:
Here are some examples of firm name extraction:
|
Option.ExtractUrb |
Specifies whether to extract the urbanization name from AddressLine1 through AddressLine4 and place it in the USUrbanName output field. This option works in cases where the input record's USUrbanName field is blank and there is more than one address line.
To identify urbanization names, the address lines are scanned for keywords and patterns that identify which fields are address lines and which are urbanization name lines. Since this is done based on patterns, it is possible for fields to be incorrectly identified. To help ensure optimal urbanization extraction, place the primary address elements in AddressLine1, the secondary elements in AddressLine2, Urbanization in AddressLine3, and firm in AddressLine4, if possible. For example,
|
Option.PerformSuiteLink |
Specifies whether to perform SuiteLink™ processing. SuiteLink corrects secondary address information for U.S. business addresses whose secondary address information could not be validated. If SuiteLink processing is enabled, the firm name is matched to a database of known firm names and their secondary address information. For example,
Firm Name: Precisely In this case, SuiteLink processing would provide the correct suite number:
Firm Name: Precisely
To perform SuiteLink™ processing, you must have the SuiteLink™ database installed. This option takes one of the following values:
For a listing of fields returned by this option, see SuiteLink Output. |
Option.OutputPreferredAlias |
Specifies whether to use a street's preferred alias in the output. Street name aliases in the United States are alternative names given to sections of a street. There are four types of street name aliases:
The non-alias version of the street name is called the base street name. If the preferred alias is used in the input then the preferred alias will be the street name in the output regardless of whether you enable this option. This is one of three options that control how ValidateAddress handles street name aliases. The other two are Option.OutputStreetNameAlias and Option.OutputAbbreviatedAlias. In most cases, if you select both Option.OutputPreferredAlias and Option.OutputAbbreviatedAlias, and ValidateAddress finds both a preferred and an abbreviated alias in the postal database, the abbreviated alias will be used in the output. The exception to this rule is if the input street name is a preferred alias. In this case, the preferred alias will be used in the output.
Note: If the input address contains a street name alias of type "changed" the output address will always contain the base street name regardless of the options you specify.
|
Option.OutputAbbreviatedAlias |
Specifies whether to use a street's abbreviated alias in the output if the output address line is longer than 31 characters. This is one of three options that control how ValidateAddress handles street name aliases. The other two are Option.OutputStreetNameAlias and Option.OutputPreferredAlias. Note: If a preferred alias is specified in the input, the output street name will always be the preferred alias, even if you enable abbreviated street name alias processing.
Note: If the input address contains a street name alias of type "changed" the output address will always contain the base street name regardless of the options you specify.
|
Option.DPVDetermineNoStat |
Determines the "no stat" status of an address. An address is considered "no stat" if it exists but cannot receive mail, and therefore is not counted as a delivery statistic on a carrier's route (hence the term "no stat"). Examples include buildings under construction or those that the letter carrier has identified as not likely to receive mail.
Note: You must enable DPV processing to use this option.
The result is returned in the DPVNoStat field. For more information see LACSLink Output |
Option.DPVDetermineVacancy |
Determines if the location has been unoccupied for at least 90 days.
Note: You must enable DPV processing to use this option.
The result is returned in the DPVVacant field. For more information see LACSLink Output |
Option.ReturnVerimove |
Returns VeriMove detail data in output.
|
Option.SuppressZplusPhantomCarrierR777 |
Specifies whether to supress addresses with Carrier Route R777. These addresses are
phantom routes and are not eligible for street delivery. Since
these addresses are assigned a ZIP + 4® code by the USPS®,
Validate Address marks these addresses as deliverable. Select
this option if you do not want addresses with Carrier Route R777
marked as deliverable. This will cause the following actions:
|
Option.StreetMatchingStrictness |
Specifies the algorithm to use when determining if an input address matches an address in the postal database. One of the following:
|
Option.FirmMatchingStrictness |
Specifies the algorithm to use when determining if an input address matches an address in the postal database. One of the following:
|
Option.DirectionalMatchingStrictness |
Specifies the algorithm to use when determining if an input address matches an address in the postal database. One of the following:
|
Option.DPVSuccessfulStatusCondition |
Select the match condition where a DPV result does NOT cause a record to fail.
Note: You must enable DPV processing to use this option.
|
Option.FailOnCMRAMatch |
Treat Commercial Mail Receiving Agency (CMRA) matches as failures?
Note: You must enable DPV processing to use this option.
|
Option.StandardAddressPMBLine |
Specifies where Private Mailbox (PMB) information is placed.
|
Option.PreferredCity |
Specifies whether the preferred last line city name should be stored.
|
Option.DPVDoorNoAccessible |
Perform DPV Door Not Accessible (DNA) processing. Use the DNA Table to identify
delivery addresses where carriers cannot knock on the door for mail delivery or
where carriers cannot physically access a residence/building such as rural/highway
contract route (HCR), long driveway, or gated community.
|
Option.DPVThrowback |
Perform DPV P.O. Box Throwback processing. Use the P.O. Box Throwback Table to
identify a delivery point that is a street address where mail is not delivered.
Instead, delivery is made to the customer’s P.O. Box address. Return the P.O.
Box.
|
Option.DPVNoSecureLoc |
Perform DPV No Secure Location (NSL) processing. Use the NSL table to identify
delivery locations that are not secure. For example, a carrier can access a door
but cannot leave a package due to security concerns. The NSL designation alerts
mailers to locations where businesses are closed on certain days and locations
without mail receptacles (for example, a storefront). Return the NSL result to the
output.
|
Option.DPVNonDeliveryDays |
Specifies whether this address was found in the Non-Delivery Days (NDD) table.
Determines if the package was non-deliverable.
|
Option.DPVNoStatReason |
Perform DPV No-Stat processing. Use the No-Stat table to identify deliveries that are not valid for Computerized Delivery Sequence (CDS) pre-processing. Return the proper No-Stat code to the output.
|
Option.DPVDrop |
Perform DPV DROP lookup.
|