tUniservRTPost (deprecated)
Improves the addresses quality, which is extremely important for CRM and e-business
as it is directly related to postage and advertising costs.
tUniservRTPost provides postal
validation and correction of addresses, which is critical to improving the quality of
addresses. This way, you will be more successful in personalized one-on-one marketing,
reducing costs and increasing the efficiency and cost-effectiveness of address
management in all the applications.
tUniservRTPost Standard properties
These properties are used to configure tUniservRTPost running in the Standard Job framework.
The Standard
tUniservRTPost component belongs to the Data Quality family.
Basic settings
Schema and Edit |
A schema is a row description. It defines the number of fields Click Edit
|
Host name |
Server host name between double quotation marks. |
Port |
Listening port number of the server between double quotation marks. |
Service |
The service name is |
Use rejects |
Select this check box to collect faulty addresses via the If this check box is not selected, the faulty addresses are output If the check box is selected but the rejects connection is not created, the faulty |
Use File for ambiguous results |
Select the check box to define a file for writing the selection When an address cannot be corrected unambiguously, a selection This list can be further processed via the AMBIGUITY connection. All potential candidate |
Advanced settings
Uniserv Parameters |
Select this check box to define the corresponding parameters. For |
tStatCatcher Statistics |
Select this check box to collect log data at the Job and the component levels. |
“Full address” selection list |
Select the check box Display to This option controls the content of the file for ambiguous |
Global Variables
Global Variables |
ERROR_MESSAGE: the error message generated by the A Flow variable functions during the execution of a component while an After variable To fill up a field or expression with a variable, press Ctrl + For further information about variables, see |
Usage
Usage rule |
tUniservRTPost requires an input |
Limitation |
To use tUniservRTPost, the |
Â
Checking and correcting the postal code, city and street
This scenario describes a batch job that checks and corrects the addresses and postal
codes from a file.
The input file for this scenario is already saved in the Repository, so that all schema metadata is available.
Procedure
-
In the Repository view, expand the Metadata node and the directory in which the file is
saved. Then drag this file into the design workspace.The dialog box below appears. -
Select tFileInputDelimited and click
OK to close the dialog box.The component is displayed in the workspace. The file used in this scenario is
called SampleAddresses. It contains address
data that comes with a country code. The street and house number are saved
together in the street field, while postal code and city are respectively saved
in separate fields. -
Drag the following components from the Palette into the design workspace: two tMap components, tUniservRTPost
and tFileOutputDelimited . -
Connect tMap with tUniservRTPost first.
Accept the schema from tUniservRTPost by
clicking Yes on the prompt window. -
Connect the other components via Row >
Main. -
Double-click tMap_1 to open the schema
mapping window. On the left is the structure of the input file and on the right
is the schema of tUniservRTPost. At the bottom
is displayed the Schema Editor, where you can
find the attributes of the individual columns and edit them. -
Assign the columns of the input file to the respective columns of tUniservRTPost. For this purpose, select a column of
the input source and drag it onto the appropriate column on the right side. If
fields from the input file are to be passed on to the output file, e.g. the
names or the IDs, additional fields must be defined.Note:When assigning the fields, note that street and house number can either be
saved together in the street column or respectively in separate fields. If
your data list does not have a country code but the addresses are from the
same country, the relevant ISO-country code should be manually entered
between double quotation marks in the column IN_COUNTRY. If you have an international data list without
country code, just leave the column IN_COUNTRY empty. For detailed information, please refer to
the Uniserv user manual International Postal
Framework. - Click OK to close the window.
-
Double-click tUniservRTPost and enter its
Advanced settings view. -
Change the parameters and field lengths if necessary and select the output
fields.Note:Make sure sufficient field length is defined. For detailed information,
please refer to the Uniserv user manual International Postal Framework. -
Double-click tMap_3 to open schema mapping
window. On the left is the schema of tUniservRTPost and on the right is the schema of the output
file. - Click OK to close the dialog box.
-
Double-click tFileOutputDelimited to enter
the details for the output file.
Checking and correcting the postal code, city and street, as well as
rejecting the unfeasible
addresses that cannot be assigned are written into a separate file for manual checking.
Additionally, to write ambiguous addresses in a separate file, the procedure is the same
as described here.
Procedure
- Create a job as described in the previous scenario.
-
Drag the following additional components from the Palette into the design workspace: tMap and tFileOutputDelimited.
-
Double-click tUniservRTPost to open its
Basic settings view. -
Select the Use rejects check box and enter
“5” in the field if
result class greater or equals to. This is the result class from
the check of postal codes in addresses, which contain too few or unfeasible
data. -
Connect tUniservRTPost with tMap_5 via Row >
Rejects. -
Connect tMap with tFileOutputDelimited via Row >
Main. - Define the fields for the output file in the mapping window.