Search Results ak_custom_region_items_u1

Overview

AK.AK_CUSTOM_REGION_ITEMS is a transactional configuration table in the Oracle E-Business Suite AK (Application Object Library/Attribute Knowledge) schema. It stores property-level customizations applied to the items (attributes) of a region within a specific customization context. In other words, when a customer personalizes or extends an EBS region — adjusting a specific attribute's behavior or presentation — the resulting property overrides are persisted as rows in this table, keyed by the combination of region, customization, attribute, and property.

Functionally, the table sits at the intersection of three identification axes: the region (where the item lives), the customization (the personalization context or layer in which the change is defined), and the attribute/property pair (what aspect of the item is being modified). This makes it a shared, metadata-driven repository used by the AK personalization framework rather than a business-data fact table.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. This suggests a modeling approach that treats the table as an independent reference/satellite-style store rather than a dependent hub or link, since no explicit parent-child FK relationships were identified in the documented metadata. The absence of discovered FKs should be treated as a modeling suggestion only; the columns themselves carry enough identifying context (application IDs, codes) to reconstruct relationships logically.

Key Information Stored

The table contains 16 documented columns. The most operationally significant are:

• CUSTOMIZATION_APPLICATION_ID and CUSTOMIZATION_CODE — identify the customization context in which the override applies.
• REGION_APPLICATION_ID and REGION_CODE — identify the region whose item is being customized.
• ATTRIBUTE_APPLICATION_ID and ATTRIBUTE_CODE — identify the specific attribute (region item) being modified.
• PROPERTY_NAME — the name of the property being customized (e.g., a visibility, label, or behavior flag).
• PROPERTY_VARCHAR2_VALUE (4000 chars), PROPERTY_NUMBER_VALUE, and PROPERTY_DATE_VALUE — typed value columns that hold the override depending on the property's datatype.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

The documented primary key is AK_CUSTOM_REGION_ITEMS_PK (ATTRIBUTE_APPLICATION_ID, CUSTOMIZATION_CODE, ATTRIBUTE_CODE, CUSTOMIZATION_APPLICATION_ID, PROPERTY_NAME, REGION_CODE, REGION_APPLICATION_ID). The unique index AK_CUSTOM_REGION_ITEMS_U1 — the object the user searched for — spans REGION_CODE, REGION_APPLICATION_ID, CUSTOMIZATION_CODE, CUSTOMIZATION_APPLICATION_ID, ATTRIBUTE_APPLICATION_ID, ATTRIBUTE_CODE, PROPERTY_NAME, and ZD_EDITION_NAME. This confirms the business key: one row per region/customization/attribute/property combination, with ZD_EDITION_NAME participating in the uniqueness constraint (a hallmark of the Editioning/EBR model in R12.2.x). Storage is in APPS_TS_TX_DATA with the index in APPS_TS_TX_IDX.

Common Use Cases and Queries

A recurring query pattern retrieves all property overrides for a given region and customization, typically joining application IDs to FND_APPLICATION for readable names:

• Customization inventory — list all rows for a region to understand what has been personalized.
• Value resolution — resolve the effective property value by selecting the appropriate typed column.
• Audit reporting — surface WHO columns to identify who changed a customization and when.
• Migration/EDR troubleshooting — inspect ZD_EDITION_NAME to confirm which edition a row belongs to.

A representative SQL statement:

SELECT r.REGION_CODE, r.CUSTOMIZATION_CODE, r.ATTRIBUTE_CODE, r.PROPERTY_NAME, r.PROPERTY_VARCHAR2_VALUE, r.PROPERTY_NUMBER_VALUE, r.PROPERTY_DATE_VALUE FROM AK.AK_CUSTOM_REGION_ITEMS r WHERE r.REGION_CODE = :region AND r.CUSTOMIZATION_CODE = :customization;

Because the unique index is region-first, filters on REGION_CODE and REGION_APPLICATION_ID are the most index-efficient access path.

Related Objects

The documented metadata shows no FK-discovered parents, consistent with the standalone classification. Logical relationships, however, connect this table to the broader AK personalization model:

• AK_CUSTOM_REGIONS — the region-level customization header; join on REGION_CODE, REGION_APPLICATION_ID, CUSTOMIZATION_CODE, and CUSTOMIZATION_APPLICATION_ID.
• AK_REGION_ITEMS — the base (uncustomized) region item definitions; join on ATTRIBUTE_APPLICATION_ID and ATTRIBUTE_CODE to compare base versus override.
• AK_REGIONS — region master; join on REGION_CODE and REGION_APPLICATION_ID.
• FND_APPLICATION — resolves the three application ID columns to application names.
• AK_ATTRIBUTES / AK_ATTRIBUTE_PROPERTIES — define which PROPERTY_NAME values are valid for a given attribute.
• AK_CUSTOM_REGION_ITEMS_U1 — the unique index enforcing the business key, including ZD_EDITION_NAME.

These joins allow administrators and developers to trace a personalization from its region header down to the individual property override stored in AK_CUSTOM_REGION_ITEMS.