Typically includes that part of address up to, but not including, the locality "last line". The word order, i.e. the position of the address components, should be the normal word order used in your data population. These should be passed in one field. Depending on table design, your application may need to concatenate these attributes into one field before calling SSA-NAME3. For example, in the US, a typical string to pass would comprise of:

Care-of + Building Name + Street Number + Street Name + Street Type + Apartment Details

Matching on

Address_Part1

uses methods and options designed specifically for addresses. It has its own Edit-List whose rules can be overridden by the Population Override Manager or Edit RuleWizard.

It is also possible to supply the entire address in the

Address_Part1

field for matching.

The application may pass multiple addresses (such as a residential address and a postal address) in the one call to SSA-NAME3. Refer to the

API REFERENCE

manual for more details.

See the

Key Fields

section for more details on

Address_Part1

.

Typically includes the "locality" line in an address. For example, in the US, a typical string to pass would comprise of:

City + State + Zip (+ Country)

Matching on

Address_Part2

uses methods and options designed specifically for addresses. It uses the same Edit-List as

Address_Part1

. The rules in this Edit-List can be overridden by the Population Override Manager or Edit RuleWizard.

The

Date

field is used for matching any type of date (e.g. date of birth, expiry date, date of contract, date of change, creation date, etc).

It expects the date to be passed in

Day+Month+Year

order. It supports the use or absence of delimiters between the date components.

Matching on dates uses methods and options designed specifically for dates. It overcomes the typical error and variation found in this data type.

It uses a string matching algorithm that compensates for transpositions and missing characters or digits. It also has its own Edit-List whose rules can be overridden by the Population Override Manager or Edit RuleWizard.

Used to match the names of organizations. These could be company names, business names, institution names, department names, agency names, trading names, etc.

This field supports matching on a single name, or a compound name (such as a legal name and its trading style). It has its own Edit-List whose rules can be overridden by the Population Override Manager or Edit RuleWizard.

The application may also pass multiple names (e.g. a legal name and a trading style) in the one call to SSA-NAME3. Refer to the

API REFERENCE

manual for more details.

See the

Key Fields

section for more details on

Organization_Name

.

Used to match the names of people. An application should pass the full person name. The word order, i.e. the position of the first name, middle names and family names, should be the normal word order used in your data population. For example, in English speaking countries, the normal word order would be:

First Name + Middle Name(s) + Family Name(s)

Depending on table design, your application may have to concatenate these separate fields into one field before calling SSA-NAME3.

This field supports matching on a single name, or an account name (such as JOHN & MARY SMITH).

The application may also pass multiple names (e.g. a married name and a former name) in the one call to SSA-NAME3. Refer to the

API REFERENCE

manual for more details.

It has its own Edit-List whose rules can be overridden by the Population Override Manager or Edit RuleWizard.

See the

Key Fields

section for more details on

Person_Name

.

The

Postal_Area

field can be used to place more emphasis on the postal code than if it were included in the

Address_Part2

field. It is used for all types of postal codes, including Zip codes.

It uses a string matching algorithm that compensates for transpositions and missing characters or digits. It also has its own Edit-List whose rules can be overridden by the Population Override Manager or Edit RuleWizard.

The

Telephone_Number

field is used to match telephone numbers.

It uses a string matching algorithm that compensates for transpositions and missing digits or area codes. It also has its own Edit-List whose rules can be overridden by the Population Override Manager or Edit RuleWizard.