Search Results ak_lookup_codes




Overview
Explore in AI Chat

Overview

AK_LOOKUP_CODES is a reference data table owned by the AK (Common Modules - Application Object Library extensions) schema in Oracle E-Business Suite. As documented in the ETRM repository for releases 12.1.1 and 12.2.2, the table "Defines the lookup codes, type and description that are used within the AK system." It functions as the extensibility lookup repository consumed by the AK framework, which underpins several internal EBS services such as the Oracle Application Framework (OAF) personalization layer, region and attribute metadata resolution, and diagnostic utilities. Lookup semantics in this table are type-scoped: a code is meaningful only within its parent LOOKUP_TYPE, mirroring the pattern used by the more widely known FND_LOOKUP_VALUES in the Application Object Library. The ETRM metadata classifies AK_LOOKUP_CODES heuristically as standalone, meaning the FK-mining process found no inbound or outbound foreign key constraints. In Data Vault terms, this object is best modeled as a satellite attached to a lookup-type hub (approximately LOOKUP_TYPE) with a degenerate composite key, rather than as an independent hub or link. The 12.2.2 physical schema lists eleven columns and one primary key, AK_LOOKUP_CODES_PK, on (LOOKUP_CODE, LOOKUP_TYPE, LANGUAGE).

Key Information Stored

The three primary-key columns form the natural access path for every runtime lookup: LOOKUP_CODE (the enumerator value), LOOKUP_TYPE (the category or domain that scopes the code), and LANGUAGE (the installation language used for multilingual descriptions). DESCRIPTION carries the translatable, user-facing meaning of the code and is the column most typically projected into reports and UI prompts. SOURCE_LANG identifies the language the description originated in, enabling the standard EBS "translation row" pattern where the primary-key language differs from SOURCE_LANG for non-base languages. The standard WHO audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN — record row provenance and modification history, supporting audit and reconciliation queries. ZD_EDITION_NAME is the 12.2 online-patching editioning column, present because the table is edition-enabled in the AD/Zd framework. A documented unique index, AK_LOOKUP_CODES_U1, covers (LOOKUP_TYPE, LOOKUP_CODE, LANGUAGE, ZD_EDITION_NAME), making it the strongest business-key candidate for downstream modeling. Note that the primary key does not include ZD_EDITION_NAME, so the unique index rather than the PK is the reliable business-key surrogate.

Common Use Cases and Queries

Typical workloads include joining lookup codes to consuming AK metadata columns, populating OAF list-of-values (LOV) definitions, and auditing lookup drift between environments. A representative query enumerates active codes for a type:

  • SELECT lookup_code, description FROM ak.ak_lookup_codes WHERE lookup_type = :type AND language = USERENV('LANG') ORDER BY lookup_code;
  • Translation reconciliation: SELECT lookup_type, lookup_code, language, source_lang, description FROM ak.ak_lookup_codes WHERE lookup_type = :type ORDER BY lookup_code, language;
  • Change audit: SELECT lookup_type, lookup_code, last_update_date, last_updated_by FROM ak.ak_lookup_codes WHERE last_update_date > SYSDATE - 7;
  • Environment diff via a full outer join on (lookup_type, lookup_code, language) to detect missing or renamed descriptions between a source and target instance.

Because the table has no enforced FKs, reporting joins must be constructed against the consuming object's code column rather than relying on constraint metadata.

Related Objects

Although the ETRM vault classification reports no FK relationships, the following objects are the most significant consumers or siblings of AK_LOOKUP_CODES in practice:

  • FND_LOOKUP_VALUES / FND_LOOKUP_TYPES — the AOL equivalents; joined on lookup_type and lookup_code for cross-reference validation.
  • AK_REGIONS and AK_REGION_ITEMS — AK framework region metadata that resolves attribute lookup_type against this table.
  • AK_ATTRIBUTES — attribute definitions whose lookup_type column references codes here.
  • AK_OBJECT_ATTRIBUTES — object-to-attribute mappings that inherit lookup behavior.
  • FND_LANGUAGES — joined on language/source_lang to render translated descriptions.
  • FND_APPLICATION and FND_PRODUCT_INSTALLATIONS — used to scope AK lookups by owning product.
  • AK_LOOKUP_CODES_U1 and AK_LOOKUP_CODES_PK — the unique index and constraint that enforce code uniqueness per type/language and provide the join keys above.