Search Results ak_custom_region_items_pk

Overview

AK_CUSTOM_REGION_ITEMS is a table in the AK (Common Modules-AK) product schema of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It stores region item property customizations—that is, the personalized attribute and property values that administrators or users apply to individual items within a custom region definition. In the Oracle EBS extensibility framework, custom regions organize applications' items into logical groups, and this table captures the property-level overrides that tailor how those items behave at runtime.

The ETRM metadata classifies the object, heuristically, as standalone under the Data Vault modeling convention. This suggests that AK_CUSTOM_REGION_ITEMS functions as an independent reference or descriptive table rather than as a hub or link, with no mined foreign-key dependencies to parent hub structures. The primary key, AK_CUSTOM_REGION_ITEMS_PK, is a composite spanning seven columns: ATTRIBUTE_APPLICATION_ID, CUSTOMIZATION_CODE, ATTRIBUTE_CODE, CUSTOMIZATION_APPLICATION_ID, PROPERTY_NAME, REGION_CODE, and REGION_APPLICATION_ID. The table contains 16 documented columns in the 12.2.2 physical schema.

Key Information Stored

The table's key columns fall into three functional groups: identity and scoping, property definition, and property value.

• CUSTOMIZATION_APPLICATION_ID and CUSTOMIZATION_CODE — Identify the customization context that owns the region item override, pairing the owning application with the customization identifier.
• REGION_APPLICATION_ID and REGION_CODE — Scope the row to a specific custom region, distinguishing the region's defining application from the region identifier.
• ATTRIBUTE_APPLICATION_ID and ATTRIBUTE_CODE — Identify the individual region item (attribute) whose property is being customized.
• PROPERTY_NAME — Names the property being set on the item, such as a display flag, prompt, or behavioral setting.
• PROPERTY_VARCHAR2_VALUE, PROPERTY_NUMBER_VALUE, and PROPERTY_DATE_VALUE — Typed value columns holding the actual customization value; exactly one is populated based on the property's declared data type.
• ZD_EDITION_NAME — Editioning column used in 12.2 online patching, separating rows by edition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording who created and last modified each customization row.

The seven-column composite primary key is the surrogate identity, while AK_CUSTOM_REGION_ITEMS_U1 — spanning the same business columns plus ZD_EDITION_NAME — is the documented unique (business-key) index. This confirms that the combination of region, customization, attribute, and property is unique per edition.

Common Use Cases and Queries

Typical use cases center on inspecting and validating how regions are customized. One common pattern retrieves all properties defined for a given region and customization:

• Region property listing: SELECT attribute_code, property_name, property_varchar2_value FROM ak.ak_custom_region_items WHERE region_code = :region AND region_application_id = :app AND customization_code = :cust;
• Attribute-level lookup: Filter on ATTRIBUTE_CODE and PROPERTY_NAME to retrieve the effective value for a single item property, useful for troubleshooting why an item displays or behaves unexpectedly.
• Audit and change reporting: Query LAST_UPDATED_BY and LAST_UPDATE_DATE to identify recent customization changes or to trace who modified a property.
• Edition-aware queries: In 12.2, include ZD_EDITION_NAME (or query the editioning view) to isolate customizations to the active edition during patching cycles.
• Type-aware value extraction: Use CASE logic across the three typed value columns to render the correct value regardless of property data type.

Related Objects

The metadata marks AK_CUSTOM_REGION_ITEMS as standalone, with no mined foreign-key dependencies. Its logical relationships are nonetheless defined through the columns shared with the broader AK customization model:

• AK_CUSTOM_REGIONS — The parent region definition, joined on REGION_CODE and REGION_APPLICATION_ID.
• AK_CUSTOM_REGION_ITEM_ATTRS — Item/attribute definitions for a region, joined on ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID.
• AK_REGION_ITEMS — The seeded (non-customized) region item definitions against which overrides are compared.
• AK_ATTRIBUTES — Attribute metadata, joined on ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID.
• AK_CUSTOMIZATION tables (customization headers) — Joined on CUSTOMIZATION_CODE and CUSTOMIZATION_APPLICATION_ID.
• FND_APPLICATION — Resolves the application ID columns to application names and short names.

Sampling or updating this table directly is not recommended; customizations should be maintained through the supported AK configuration and personalization interfaces, with this table treated as the underlying persistence layer.