Search Results ak_lookup_codes_u1

Overview

The AK.AK_LOOKUP_CODES table is a foundational reference data object within the Oracle E-Business Suite Applications Object Library (AK) schema. It stores the extensible lookup code definitions used throughout the EBS application stack, providing the enumerated values that populate flexfields, list of values (LOVs), and application-specific validation sets. Each row represents a single lookup code within a named lookup type, retained in the language to which its translatable description has been translated. The table resides in the APPS_TS_TX_DATA tablespace, with its unique index spanning APPS_TS_TX_IDX, reflecting its role as high-volume, read-intensive reference data rather than transactional data.

From a Data Vault modeling perspective, the metadata classifies this object heuristically as a standalone structure. It can reasonably be modeled as a reference satellite (or a hub with a descriptive satellite), since it holds stable, code-centric business keys (LOOKUP_TYPE, LOOKUP_CODE, LANGUAGE) alongside descriptive attributes such as DESCRIPTION and SOURCE_LANG. It does not reference any other database object, confirming its self-contained, lookup-only nature.

Key Information Stored

The table's business identity is anchored by three columns that together form the primary key AK_LOOKUP_CODES_PK: LOOKUP_CODE, LOOKUP_TYPE, and LANGUAGE. A separate unique index, AK_LOOKUP_CODES_U1, covers LOOKUP_TYPE, LOOKUP_CODE, and LANGUAGE (with ZD_EDITION_NAME in the 12.2.2 documented schema), representing the principal business-key candidate used for edition-aware validation.

• LOOKUP_CODE (VARCHAR2 25) — The individual code value within a lookup type; part of the composite primary key.
• LOOKUP_TYPE (VARCHAR2 30) — The category or grouping that defines the type of lookup code; also part of the primary key.
• DESCRIPTION (VARCHAR2 80) — User-friendly description of the lookup code, subject to translation.
• LANGUAGE (VARCHAR2) — Language code indicating the language into which translatable fields are rendered; part of the primary key.
• SOURCE_LANG (VARCHAR2) — Original language in which translatable column values were initially entered.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing modification history.
• CREATION_DATE, CREATED_BY — Standard WHO audit columns capturing record creation metadata.
• ZD_EDITION_NAME — Editioning column introduced in the 12.2.x schema, supporting Edition-Based Redefinition.

The primary key is defined on (LOOKUP_CODE, LOOKUP_TYPE, LANGUAGE); the unique index adds ZD_EDITION_NAME as the business-key candidate in the 12.2.2 documented schema.

Common Use Cases and Queries

Typical usage involves resolving code values into human-readable descriptions and validating incoming data against defined lookup types. Reporting queries frequently filter by a specific LOOKUP_TYPE and restrict LANGUAGE to the session language.

• Retrieve all active codes for a given lookup type, such as SELECT LOOKUP_CODE, DESCRIPTION FROM AK.AK_LOOKUP_CODES WHERE LOOKUP_TYPE = :type AND LANGUAGE = USERENV('LANG').
• Validate that a supplied code exists before inserting transactional data.
• Populate concurrent program parameters and LOVs dynamically.
• Extract translated descriptions for multilingual reporting or data migration.
• Audit recent changes via LAST_UPDATE_DATE and LAST_UPDATED_BY.

Because the table is read-intensive and edition-aware, queries should generally include a LANGUAGE predicate and, in 12.2.x environments, respect editioning filters.

Related Objects

The table references no other database object, but it is referenced by the APPS synonym AK_LOOKUP_CODES, which exposes it to the application schema. The most significant related objects and join patterns include:

• APPS.AK_LOOKUP_CODES — Synonym resolving to AK.AK_LOOKUP_CODES used by forms, concurrent programs, and reports.
• AK.AK_LOOKUP_TYPES — Parent lookup-type definitions; join on LOOKUP_TYPE.
• AK.AK_LOOKUP_CODES_TL — Translation table joined on LOOKUP_TYPE, LOOKUP_CODE, and LANGUAGE.
• FND_LOOKUP_VALUES / FND_LOOKUP_TYPES — Application-wide lookup infrastructure that frequently mirrors or complements AK lookup definitions.
• FND_FLEX_VALIDATION — Flexfield value sets that may source values from lookup codes.

These objects are joined primarily on LOOKUP_TYPE and LOOKUP_CODE, making the composite key the principal linkage point across the EBS reference data model.