/AWS1/CL_ERNSCHEMAINPUTATTR

A configuration object for defining input data fields in Entity Resolution. The SchemaInputAttribute specifies how individual fields in your input data should be processed and matched.

CONSTRUCTOR

IMPORTING

Required arguments:

iv_fieldname TYPE /AWS1/ERNATTRIBUTENAME /AWS1/ERNATTRIBUTENAME

A string containing the field name.

iv_type TYPE /AWS1/ERNSCHEMAATTRIBUTETYPE /AWS1/ERNSCHEMAATTRIBUTETYPE

The type of the attribute, selected from a list of values.

LiveRamp supports: NAME | NAME_FIRST | NAME_MIDDLE | NAME_LAST | ADDRESS | ADDRESS_STREET1 | ADDRESS_STREET2 | ADDRESS_STREET3 | ADDRESS_CITY | ADDRESS_STATE | ADDRESS_COUNTRY | ADDRESS_POSTALCODE | PHONE | PHONE_NUMBER | EMAIL_ADDRESS | UNIQUE_ID | PROVIDER_ID

TransUnion supports: NAME | NAME_FIRST | NAME_LAST | ADDRESS | ADDRESS_CITY | ADDRESS_STATE | ADDRESS_COUNTRY | ADDRESS_POSTALCODE | PHONE_NUMBER | EMAIL_ADDRESS | UNIQUE_ID | IPV4 | IPV6 | MAID

Unified ID 2.0 supports: PHONE_NUMBER | EMAIL_ADDRESS | UNIQUE_ID

Normalization is only supported for NAME, ADDRESS, PHONE, and EMAIL_ADDRESS.

If you want to normalize NAME_FIRST, NAME_MIDDLE, and NAME_LAST, you must group them by assigning them to the NAME groupName.

If you want to normalize ADDRESS_STREET1, ADDRESS_STREET2, ADDRESS_STREET3, ADDRESS_CITY, ADDRESS_STATE, ADDRESS_COUNTRY, and ADDRESS_POSTALCODE, you must group them by assigning them to the ADDRESS groupName.

If you want to normalize PHONE_NUMBER and PHONE_COUNTRYCODE, you must group them by assigning them to the PHONE groupName.

Optional arguments:

iv_groupname TYPE /AWS1/ERNATTRIBUTENAME /AWS1/ERNATTRIBUTENAME

A string that instructs Entity Resolution to combine several columns into a unified column with the identical attribute type.

For example, when working with columns such as NAME_FIRST, NAME_MIDDLE, and NAME_LAST, assigning them a common groupName will prompt Entity Resolution to concatenate them into a single value.

iv_matchkey TYPE /AWS1/ERNATTRIBUTENAME /AWS1/ERNATTRIBUTENAME

A key that allows grouping of multiple input attributes into a unified matching group.

For example, consider a scenario where the source table contains various addresses, such as business_address and shipping_address. By assigning a matchKey called address to both attributes, Entity Resolution will match records across these fields to create a consolidated matching group.

If no matchKey is specified for a column, it won't be utilized for matching purposes but will still be included in the output table.

iv_subtype TYPE /AWS1/ERNATTRIBUTENAME /AWS1/ERNATTRIBUTENAME

The subtype of the attribute, selected from a list of values.

iv_hashed TYPE /AWS1/ERNBOOLEAN /AWS1/ERNBOOLEAN

Indicates if the column values are hashed in the schema input.

If the value is set to TRUE, the column values are hashed.

If the value is set to FALSE, the column values are cleartext.

---

Queryable Attributes

fieldName

A string containing the field name.

Accessible with the following methods

Method	Description
GET_FIELDNAME()	Getter for FIELDNAME, with configurable default
ASK_FIELDNAME()	Getter for FIELDNAME w/ exceptions if field has no value
HAS_FIELDNAME()	Determine if FIELDNAME has a value

type

The type of the attribute, selected from a list of values.

LiveRamp supports: NAME | NAME_FIRST | NAME_MIDDLE | NAME_LAST | ADDRESS | ADDRESS_STREET1 | ADDRESS_STREET2 | ADDRESS_STREET3 | ADDRESS_CITY | ADDRESS_STATE | ADDRESS_COUNTRY | ADDRESS_POSTALCODE | PHONE | PHONE_NUMBER | EMAIL_ADDRESS | UNIQUE_ID | PROVIDER_ID

TransUnion supports: NAME | NAME_FIRST | NAME_LAST | ADDRESS | ADDRESS_CITY | ADDRESS_STATE | ADDRESS_COUNTRY | ADDRESS_POSTALCODE | PHONE_NUMBER | EMAIL_ADDRESS | UNIQUE_ID | IPV4 | IPV6 | MAID

Unified ID 2.0 supports: PHONE_NUMBER | EMAIL_ADDRESS | UNIQUE_ID

Normalization is only supported for NAME, ADDRESS, PHONE, and EMAIL_ADDRESS.

If you want to normalize NAME_FIRST, NAME_MIDDLE, and NAME_LAST, you must group them by assigning them to the NAME groupName.

If you want to normalize ADDRESS_STREET1, ADDRESS_STREET2, ADDRESS_STREET3, ADDRESS_CITY, ADDRESS_STATE, ADDRESS_COUNTRY, and ADDRESS_POSTALCODE, you must group them by assigning them to the ADDRESS groupName.

If you want to normalize PHONE_NUMBER and PHONE_COUNTRYCODE, you must group them by assigning them to the PHONE groupName.

Accessible with the following methods

Method	Description
GET_TYPE()	Getter for TYPE, with configurable default
ASK_TYPE()	Getter for TYPE w/ exceptions if field has no value
HAS_TYPE()	Determine if TYPE has a value

groupName

A string that instructs Entity Resolution to combine several columns into a unified column with the identical attribute type.

For example, when working with columns such as NAME_FIRST, NAME_MIDDLE, and NAME_LAST, assigning them a common groupName will prompt Entity Resolution to concatenate them into a single value.

Accessible with the following methods

Method	Description
GET_GROUPNAME()	Getter for GROUPNAME, with configurable default
ASK_GROUPNAME()	Getter for GROUPNAME w/ exceptions if field has no value
HAS_GROUPNAME()	Determine if GROUPNAME has a value

matchKey

A key that allows grouping of multiple input attributes into a unified matching group.

For example, consider a scenario where the source table contains various addresses, such as business_address and shipping_address. By assigning a matchKey called address to both attributes, Entity Resolution will match records across these fields to create a consolidated matching group.

If no matchKey is specified for a column, it won't be utilized for matching purposes but will still be included in the output table.

Accessible with the following methods

Method	Description
GET_MATCHKEY()	Getter for MATCHKEY, with configurable default
ASK_MATCHKEY()	Getter for MATCHKEY w/ exceptions if field has no value
HAS_MATCHKEY()	Determine if MATCHKEY has a value

subType

The subtype of the attribute, selected from a list of values.

Accessible with the following methods

Method	Description
GET_SUBTYPE()	Getter for SUBTYPE, with configurable default
ASK_SUBTYPE()	Getter for SUBTYPE w/ exceptions if field has no value
HAS_SUBTYPE()	Determine if SUBTYPE has a value

hashed

Indicates if the column values are hashed in the schema input.

If the value is set to TRUE, the column values are hashed.

If the value is set to FALSE, the column values are cleartext.

Accessible with the following methods

Method	Description
GET_HASHED()	Getter for HASHED, with configurable default
ASK_HASHED()	Getter for HASHED w/ exceptions if field has no value
HAS_HASHED()	Determine if HASHED has a value

Public Local Types In This Class

Internal table types, representing arrays and maps of this class, are defined as local types:

TT_SCHEMAINPUTATTRIBUTES

TYPES TT_SCHEMAINPUTATTRIBUTES TYPE STANDARD TABLE OF REF TO /AWS1/CL_ERNSCHEMAINPUTATTR WITH DEFAULT KEY
.