Results for “customization_level_id”

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

Overview

AK_CUSTOM_REGISTRY is a registry table residing in the AK (Common Modules-AK) schema of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. Its stated purpose is to serve as a registry for customizations, recording which customization properties have been defined at which customization level within the EBS application framework. The table is owned by Oracle's proprietary AK product layer, which supplies shared application infrastructure used across many EBS modules.

The documented physical schema contains nine columns. The Primary Key, AK_CUSTOM_REGISTRY_PK, is a composite key defined on CUSTOM_LEVEL and PROPERTY_NAME. A unique index, AK_CUSTOM_REGISTRY_U1, is also defined on the same two columns (CUSTOM_LEVEL, PROPERTY_NAME), confirming that this pair is the business-key candidate enforcing uniqueness of each registry entry within its level. The PK therefore functions as a natural/composite surrogate key rather than a single numeric sequence identifier.

From a Data Vault modeling perspective, the mined relationship data classifies this object heuristically as standalone, meaning it has no documented foreign key dependencies within the extracted FK structure. In modeling terms, that suggests it is best treated as a reference or lookup table rather than a link or a dependent satellite.

Key Information Stored

The columns documented in the ETRM metadata are:

• CUSTOM_LEVEL — part of the composite primary key and the U1 unique index; identifies the level at which the customization is registered.
• PROPERTY_NAME — the second component of the composite PK and U1; the name of the customization property being registered.
• CUSTOMIZATION_LEVEL_ID — a supporting identifier associated with the customization level.
• TRANSLATABLE — flag indicating whether the registered property is translatable.
• CREATED_BY, CREATION_DATE — standard audit columns capturing who created the registry entry and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns capturing the last modifier and modification timestamp.
• LAST_UPDATE_LOGIN — session/login identifier associated with the last update.

The surrogate-versus-business-key distinction is straightforward here: no numeric surrogate is documented, so the composite of CUSTOM_LEVEL and PROPERTY_NAME acts as the effective business key, backed by both the primary key and unique index.

Common Use Cases and Queries

Typical uses involve auditing which properties have been registered as customizable at each level, validating that a customization does not collide with an existing registry entry, and reporting on translatable versus non-translatable properties. A representative query enumerating registry entries by level is:

• SELECT CUSTOM_LEVEL, PROPERTY_NAME, TRANSLATABLE FROM AK.AK_CUSTOM_REGISTRY ORDER BY CUSTOM_LEVEL, PROPERTY_NAME;
• SELECT CUSTOM_LEVEL, COUNT(*) FROM AK.AK_CUSTOM_REGISTRY GROUP BY CUSTOM_LEVEL; — footprint of registrations per customization level.
• SELECT * FROM AK.AK_CUSTOM_REGISTRY WHERE PROPERTY_NAME = :prop; — locate all levels registering a given property.
• SELECT PROPERTY_NAME FROM AK.AK_CUSTOM_REGISTRY WHERE TRANSLATABLE = 'Y'; — identify translatable customization properties.
• Audit query joining CREATED_BY / LAST_UPDATED_BY to FND_USER for change attribution.

Because the object is standalone with no mined FK relationships, reporting joins should generally be driven by value-based predicates on CUSTOM_LEVEL and PROPERTY_NAME rather than relational navigation from this table.

Related Objects

The ETRM metadata for this object documents no foreign key relationships and confirms the standalone Data Vault classification. Consequently, related objects are conceptual context rather than documented referential dependencies:

• AK_CUSTOM_REGISTRY_PK — the primary key constraint enforcing uniqueness of (CUSTOM_LEVEL, PROPERTY_NAME).
• AK_CUSTOM_REGISTRY_U1 — the unique index on the same column pair, serving as the business-key candidate.
• FND_USER — referenced logically for resolving CREATED_BY and LAST_UPDATED_BY to user names in audit reporting.
• AK_CUSTOM_REGISTRY (AK schema siblings) — other AK customization metadata tables that share the AK product layer and may reference the same customization levels.
• AK_CUSTOM_REGISTRY diagnostics — Oracle's own metadata and DBA verification queries used during upgrade analysis to confirm registry validity across 12.1.1 and 12.2.2.

Unless additional FK metadata is mined, AK_CUSTOM_REGISTRY should be treated as an independent reference table within the AK schema, joined by value rather than by documented key relationships.