Two-tier Access Path

Two-tier access is used when the replacement row must be selected from within the translate table rows that match an incoming value. The translate table is accessed twice; tier-one access will search for the rows which match the incoming value, and tier-two access will determine how the replacement row is selected from within the rows which match the tier-one value.

The tier-one values must be contained within the translate table. All of the translate table rows which match the tier-one value will be available for tier-two replacement values.

If the tier-one value is not found in the translate table, the disguise failed action defined for the translate table will be executed for each field in tier-one, and access for tier-one will be retried with the value provided for access path failed. If access path fails on the second try, the access path failed option specified for the translate table will be applied to all replacement fields.

Two-tier access is repeatable when hash access is used for tier-two. It is not reversible and not unique.

For information on how to use a two-tier access path in a rule, see Translation Rule Actions - Search for Source Value Access Path. For information on how to create a two-tier access path, see Create Two-tier Access Path Definition.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*