Search Results ak_unique_key_columns




Overview
Explore in AI Chat

Overview

The AK_UNIQUE_KEY_COLUMNS table is a core metadata repository within the Oracle E-Business Suite (EBS) architecture, specifically under the AK (Common Modules-AK) product. It functions as a critical junction table that defines the composition of unique keys within the EBS framework. Its primary role is to link individual application attributes (data elements) to specific unique key definitions. This table is fundamental to the Application Object Library's (AOL) underlying data model, enabling the system to enforce and manage business rule constraints at the metadata level, ensuring data integrity across the complex, integrated modules of EBS releases 12.1.1 and 12.2.2.

Key Information Stored

The table stores the mapping between a unique key and its constituent columns. Its structure is defined by a primary key and a foreign key relationship. The primary key, AK_UNIQUE_KEY_COLUMNS_PK, is a composite key consisting of three columns: UNIQUE_KEY_NAME, ATTRIBUTE_CODE, and ATTRIBUTE_APPLICATION_ID. This design ensures that a specific attribute can only be associated with a given unique key once. The UNIQUE_KEY_NAME identifies the unique key definition itself. The ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID together uniquely identify a specific attribute within the EBS system, linking to the broader AOL attribute registry. The table maintains a foreign key relationship (AK_UNIQUE_KEY_COLUMNS.UNIQUE_KEY_NAME) to the parent AK_UNIQUE_KEYS table, which holds the master definition of the unique key.

Common Use Cases and Queries

This table is primarily accessed for metadata analysis, system diagnostics, and customization impact assessments. Common use cases include identifying all attributes that form a specific unique key constraint, understanding the data model for a custom object, or verifying key definitions before data migration. A typical query would join this table with AK_UNIQUE_KEYS and related attribute tables to get a readable description of a key's composition.

  • Sample Query: To list all columns for a unique key:
    SELECT ukc.unique_key_name, ukc.attribute_code, ukc.attribute_application_id FROM ak.ak_unique_key_columns ukc WHERE ukc.unique_key_name = '&KEY_NAME';
  • Reporting Use Case: Generating a data dictionary report that documents all unique constraints defined for a set of application objects, detailing their component attributes.

Related Objects

The AK_UNIQUE_KEY_COLUMNS table is part of a tightly integrated metadata group within the AK schema. Its most direct relationship is with the AK_UNIQUE_KEYS table, which is its parent table via a foreign key constraint. The attributes referenced by ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID are typically defined within the AOL's core metadata tables, such as FND_COLUMNS or related AK_ATTRIBUTES tables, depending on the specific EBS implementation. Developers and DBAs interacting with this table will also frequently reference the AK_CUSTOM_REGIONS and AK_OBJECTS tables to understand the full context of the object to which the unique key belongs.