Input fields must be correctly mapped to the URAC transform for generating correct output. Fields from the input source can be mapped to URAC in pure multiline format (MULTILINE 1- 12 fields), discrete format (ADDRESS_LINE, LASTLINE, etc fields) or a combination of multiline and discrete fields which is also known as hybrid format (see image below). The output generated by the URAC transform for most part does not depend on the input format as long as all required fields are correctly mapped. If neither SuiteLink nor NCOALink options are enabled, the minimum required input would be address, locality, region and postcode information entered in discrete, multiline or hybrid fields. The SuiteLink option also requires firm to be mapped as input and the NCOALink option also requires either firm or name fields to be mapped as input.
After processing an address, the URAC transform populates results in the applicable output fields. In certain cases, some output fields not be populated. Specifically:
- If an input address is not matched to USPS reference data, it is considered unassigned and certain fields like POSTCODE2 are not populated.
- If a particular option is not enabled, all output fields relevant to that option will be blank. For example, if the DPV option is not enabled. all the DPV fields in the image below would be blank.
- Standardization options could potentially cause some fields to be blank. For example, an option to combine fields could result in blanking an output line field that would otherwise be populated.
Brief description of some attributes of URAC output fields:
- The Field Class for a field is populated based on details of how an address was processed. For example, Move_Updated components are only populated when the NCOALink option is being used and an NCOALink match is found. Correct components are populated any time an address is matched to reference data (assigned).
- Field Address Class differentiates between 3 different types of output addresses (Delivery, Dual and Official).
- The Field Category of Standardized indicates when a corresponding field was mapped from the input schema.
All major URAC option groups are depicted in the image above. There are several predefined URAC configurations that cover most common use-cases like CASS or NCOALink compliant processing. Users need to configure the Reference Files section to provide the location to reference data required by URAC transform. Certain options in the USPS License Information block are also required when running with options like DPV or LACSLink. URAC will produce a verification error when options or fields are not setup correctly for successful job execution. Required options and fields may differ based on which options are enabled or the provider level specificied for the NCOALink option. To enable regulatory features such as DPV, LACSLink, SuiteLink, etc, set the corresponding option in the "Assignment Options" group to "YES".
URAC needs reference data for successful address processing. SAP provides reference data for all address assignment features supported by URAC except NCOALink and DSF2.