Results for “ax_id_hash_results”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AX_ID_HASH_RESULTS is a table in the AX (Global Accounting Engine) product of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2 environments. Its documented purpose is to store hash values for numeric identifiers. The Global Accounting Engine relies on this structure to persist pre-computed hash values associated with specific numeric identifiers, allowing the application to detect changes, validate integrity, or accelerate lookups against identifier-based processing without repeatedly recalculating the hash. The table is owned by the AX schema and is marked VALID in the referenced ETRM metadata.

From a heuristic Data Vault modeling perspective, AX_ID_HASH_RESULTS is classified as a standalone object—neither a classic hub, link, nor satellite in the mined FK structure. This classification is a suggestion only: the table holds business keys (identifier type plus identifier) along with its own hash payload and audit columns, and it does not participate in documented foreign-key relationships to other AX tables. It functions effectively as a reference or cache-style table keyed on the numeric identifier.

Key Information Stored

The documented physical schema contains 12 columns. The most significant are:

• IDENTIFIER_TYPE — categorizes the kind of numeric identifier being hashed; part of the composite primary key.
• IDENTIFIER — the numeric identifier itself; the second component of the composite primary key.
• HASH_VALUE — the computed hash result for the identifier/type combination, which is the primary payload of the row.
• CREATED_BY, CREATION_DATE — standard WHO columns recording row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — standard WHO columns recording the most recent modification.
• LAST_UPDATE_LOGIN — the login session associated with the last change.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent program context identifying the request and program that inserted or refreshed the row.

The surrogate-style primary key is AX_ID_HASH_RESULTS_PK, defined on (IDENTIFIER_TYPE, IDENTIFIER). A unique index, AX_ID_HASH_RESULTS_U1, also exists on the same two columns (IDENTIFIER_TYPE, IDENTIFIER), making that pair the business-key candidate for the table. The remaining columns are descriptive, audit, or context fields.

Common Use Cases and Queries

Typical usage involves looking up or validating a hash for a specific identifier during Global Accounting Engine processing, and reporting on stale or missing hash entries.

• Retrieve the hash for a given identifier and type:
  SELECT HASH_VALUE FROM AX.AX_ID_HASH_RESULTS WHERE IDENTIFIER_TYPE = :type AND IDENTIFIER = :id;
• List all identifiers of a given type:
  SELECT IDENTIFIER, HASH_VALUE FROM AX.AX_ID_HASH_RESULTS WHERE IDENTIFIER_TYPE = :type ORDER BY IDENTIFIER;
• Identify rows refreshed by a specific concurrent request:
  SELECT IDENTIFIER_TYPE, IDENTIFIER, REQUEST_ID FROM AX.AX_ID_HASH_RESULTS WHERE REQUEST_ID = :req_id;
• Audit recently modified hash entries:
  SELECT IDENTIFIER_TYPE, IDENTIFIER, HASH_VALUE, LAST_UPDATE_DATE FROM AX.AX_ID_HASH_RESULTS WHERE LAST_UPDATE_DATE > SYSDATE - 7;

Because the table is standalone, queries do not require joins to resolve its content; it can be used directly as a lookup source or reconciliation target.

Related Objects

The ETRM metadata classifies AX_ID_HASH_RESULTS as standalone, meaning no documented foreign-key relationships tie it to other tables. Consequently there are no authoritative join columns to other AX objects. Its principal related objects are the objects that define and manage it:

• AX_ID_HASH_RESULTS_PK — the primary key constraint enforcing uniqueness on (IDENTIFIER_TYPE, IDENTIFIER).
• AX_ID_HASH_RESULTS_U1 — the unique index on (IDENTIFIER_TYPE, IDENTIFIER), the business-key candidate.
• Global Accounting Engine concurrent programs referenced by PROGRAM_APPLICATION_ID, PROGRAM_ID, and REQUEST_ID, which populate and refresh the rows.
• AX schema objects that consume identifier hash values during accounting engine processing.

Any integration with this table should rely on the (IDENTIFIER_TYPE, IDENTIFIER) key and treat HASH_VALUE as the primary payload.