Search Results ak_custom_registry_u1

Overview

AK.AK_CUSTOM_REGISTRY is a reference and registry table within the Application Kit (AK) schema of Oracle E-Business Suite. Its documented function is to serve as a registry table for customizations, storing metadata that governs which configurable properties within a region or region item are translatable. This table underpins the EBS personalization framework by providing the definitional layer that the runtime customization engine consults when resolving translatable content across regions and their constituent items.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10 and is owned by the AK schema, with FND design data registered as AK.AK_CUSTOM_REGISTRY. It is classified as VALID in the ETRM documentation for both 12.1.1 and 12.2.2. The heuristic Data Vault classification mined from the foreign key structure is standalone, suggesting that the object can be modeled independently as a self-contained reference set without requiring hub, link, or satellite decomposition. In practice this reflects that the table carries its own business key and holds no dependency on other database objects, as confirmed by the dependency section stating it references no database object.

Key Information Stored

The table contains nine documented columns. The principal business-key candidates are CUSTOM_LEVEL and PROPERTY_NAME, which together form the primary key AK_CUSTOM_REGISTRY_PK and are also enforced by the unique index AK_CUSTOM_REGISTRY_U1, the object named in the user's search. Because both the primary key and the sole unique index cover the identical column pair, the surrogate identifier CUSTOMIZATION_LEVEL_ID (NUMBER(15)) functions as a numeric level identifier rather than as a strict substitute for the business key.

• CUSTOM_LEVEL (VARCHAR2(30)) — Accepts one of two values, "REGION" or "REGION_ITEM", indicating the granularity at which customization applies.
• PROPERTY_NAME (VARCHAR2(30)) — The name of the customizable property.
• CUSTOMIZATION_LEVEL_ID (NUMBER(15)) — Numeric level identifier for the customization.
• TRANSLATABLE (VARCHAR2) — Flag indicating whether the property is translatable.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking record creation and modification.

The unique index AK_CUSTOM_REGISTRY_U1 is housed in the APPS_TS_TX_IDX tablespace as a NORMAL unique index, providing the principal indexed access path for lookups by customization level and property name.

Common Use Cases and Queries

The most frequent use case is determining whether a given property at a given customization level is marked translatable, typically during personalization deployment or translation extraction routines. The canonical query retrieves all columns, but targeted lookups should filter on the business key.

• Retrieve translatable region-level properties: SELECT PROPERTY_NAME, TRANSLATABLE FROM AK.AK_CUSTOM_REGISTRY WHERE CUSTOM_LEVEL = 'REGION' AND TRANSLATABLE = 'Y';
• Resolve a single property: SELECT CUSTOMIZATION_LEVEL_ID, TRANSLATABLE FROM AK.AK_CUSTOM_REGISTRY WHERE CUSTOM_LEVEL = 'REGION_ITEM' AND PROPERTY_NAME = :property_name;
• Audit recent registry changes: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to trace who modified translatability flags.
• Reporting: join against AK region and region-item metadata to produce translatability matrices for a given application or personalization set.

Because the table is small and reference-oriented, queries should favor index access via AK_CUSTOM_REGISTRY_U1 rather than full scans.

Related Objects

ETRM documents that AK.AK_CUSTOM_REGISTRY references no database object; the standalone classification is therefore consistent with the absence of outgoing foreign keys. It is referenced, however, by the APPS synonym AK_CUSTOM_REGISTRY, which exposes the table to application code and concurrent programs under the APPS schema. Joins at the application layer are expected against the AK region and region-item definition tables (such as the AK_REGIONS family) and the personalization/customization metadata consulted by the AK runtime engine, using CUSTOM_LEVEL and PROPERTY_NAME as the correlation columns. DBA_IND_COLUMNS and DBA_INDEXES provide the authoritative definition of AK_CUSTOM_REGISTRY_U1 for index-validation and performance analysis.