Results for “unique_key_sequence”

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

Overview

AK_UNIQUE_KEY_COLUMNS is a table in the AK (Common Modules-AK) schema of Oracle E-Business Suite, present and valid in both 12.1.1 and 12.2.2. It links an attribute to a unique key. Within the Oracle EBS application object library and the AK (Attribute / Key) framework, this table serves as the association layer that records which descriptive-flexfield-style attribute columns participate in a named unique key, and in what order. The table is owned by AK and contains 26 documented columns.

From a Data Vault modeling perspective, the heuristic classification mined from the foreign key structure is satellite-leaning. This suggests the table captures descriptive detail that describes the parent unique key entity (held in AK_UNIQUE_KEYS) rather than acting as a pure hub or link. Readers should treat this as a design suggestion only; the object is a standard Oracle EBS relational table, not part of an implemented Data Vault warehouse.

Key Information Stored

The primary key of the table is AK_UNIQUE_KEY_COLUMNS_PK, defined on the combination (UNIQUE_KEY_NAME, ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID). This composite key is the surrogate/business key that guarantees each attribute is represented only once within a given unique key.

• UNIQUE_KEY_NAME — the name of the unique key to which the attribute belongs; also the foreign key column referencing AK_UNIQUE_KEYS.UNIQUE_KEY_NAME.
• UNIQUE_KEY_SEQUENCE — the ordinal position of the attribute within the unique key, governing the column order of the key definition.
• ATTRIBUTE_CODE — the code identifying the attribute (typically an application-flexfield attribute or descriptive-flexfield column code) that is linked to the key.
• ATTRIBUTE_APPLICATION_ID — the application identifier that qualifies the attribute code, allowing the same code to be scoped per application.
• ATTRIBUTE_CATEGORY — the descriptive-flexfield category under which the attribute is contextualized, where applicable.
• ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive-flexfield attribute columns, providing 15 free-form segments associated with the row.
• ZD_EDITION_NAME — the edition name used by Oracle's edition-based redefinition (EBR) to support online patching in 12.2.x.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN record who created and last modified each row and when.

Two unique indexes are documented: AK_UNIQUE_KEY_COLUMNS_U1 on (UNIQUE_KEY_NAME, ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID, ZD_EDITION_NAME), which extends the primary key with the edition column, and AK_UNIQUE_KEY_COLUMNS_U2 on (UNIQUE_KEY_NAME, UNIQUE_KEY_SEQUENCE, ZD_EDITION_NAME), which enforces uniqueness of attribute ordering within a key.

Common Use Cases and Queries

Typical use cases include resolving the ordered list of attributes that compose a registered unique key, auditing key definitions for data-integrity projects, and confirming which attributes are functionally treated as unique combinations by EBS flexfield logic. A representative query joins the table to its parent key:

• List attributes of a key: SELECT ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID, UNIQUE_KEY_SEQUENCE FROM AK.AK_UNIQUE_KEY_COLUMNS WHERE UNIQUE_KEY_NAME = :key ORDER BY UNIQUE_KEY_SEQUENCE;
• Find all keys using an attribute: filter on ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID to see which unique keys reference a given attribute.
• Join to parent keys: SELECT k.UNIQUE_KEY_NAME, c.ATTRIBUTE_CODE FROM AK_UNIQUE_KEYS k JOIN AK_UNIQUE_KEY_COLUMNS c ON k.UNIQUE_KEY_NAME = c.UNIQUE_KEY_NAME; In 12.2.x, include ZD_EDITION_NAME in predicates when edition-aware results are required.

Related Objects

• AK_UNIQUE_KEYS — parent table; joined on AK_UNIQUE_KEY_COLUMNS.UNIQUE_KEY_NAME = AK_UNIQUE_KEYS.UNIQUE_KEY_NAME.
• AK_ATTRIBUTES / AK_ATTRIBUTE_COLUMNS — define the attributes referenced by ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID.
• AK_UNIQUE_KEY_COLUMNS_PK — primary key constraint (UNIQUE_KEY_NAME, ATTRIBUTE_CODE, ATTRIBUTE_APPLICATION_ID).
• AK_UNIQUE_KEY_COLUMNS_U1 / _U2 — unique indexes enforcing business-key and sequence uniqueness, including ZD_EDITION_NAME.
• Application-flexfield and descriptive-flexfield registration logic — consumes this metadata via the AK framework to validate and sequence unique key attributes at runtime.