Results for “ak_region_items_u1”

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

Overview

AK.AK_REGION_ITEMS is a foundational metadata table within the Oracle E-Business Suite Application Object Library (AK) schema. It defines the individual items—attributes or object attributes—that appear on a given region within the AK metadata framework that underpins Oracle Application Framework (OAF) pages, forms, and other declarative UI constructs. Each row represents a single attribute assigned to a region, and the table captures the complete set of formatting, behavioral, and defaulting properties required to render that item correctly at runtime.

The table is implemented on the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, and is classified in the ETRM 12.2.2 repository as VALID. Based on the FK topology—where the table references AK_REGIONS, AK_ATTRIBUTES, and FND_MENUS, and is itself referenced by AK_CATEGORY_USAGES, AK_FLOW_PAGE_REGION_ITEMS, and AK_REGION_ITEMS_TL—the heuristic Data Vault classification suggests a satellite-leaning entity. This reflects its role as a property container attached to a central region-attribute combination rather than as an independent hub.

Key Information Stored

AK_REGION_ITEMS contains 93 documented columns. The most operationally significant are:

• REGION_CODE / REGION_APPLICATION_ID — Identify the owning region and its product-team application context.
• ATTRIBUTE_CODE / ATTRIBUTE_APPLICATION_ID — Identify the attribute or object attribute placed on the region.
• DISPLAY_SEQUENCE — Controls the visual ordering of the item within the region.
• OBJECT_ATTRIBUTE_FLAG — Distinguishes a plain attribute from an object attribute.
• ATTRIBUTE_LABEL_LENGTH, BOLD, ITALIC, VERTICAL_ALIGNMENT, HORIZONTAL_ALIGNMENT, ITEM_STYLE — Formatting properties applied at render time.
• UPDATE_FLAG, REQUIRED_FLAG, DISPLAY_VALUE_LENGTH — Behavioral constraints governing editability and display width.
• LOV_REGION_CODE, LOV_ATTRIBUTE_CODE, LOV_FOREIGN_KEY_NAME, LOV_DEFAULT_FLAG — List-of-values wiring.
• REGION_DEFAULTING_API_PKG, REGION_DEFAULTING_API_PROC, REGION_VALIDATION_API_PKG, REGION_VALIDATION_API_PROC — PL/SQL hooks invoked for defaulting and validation.
• NESTED_REGION_CODE / NESTED_REGION_APPLICATION_ID — Embeds a sub-region within the current region.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — Standard audit columns.

The physical surrogate primary key is AK_REGION_ITEMS_PK, covering REGION_CODE, REGION_APPLICATION_ID, ATTRIBUTE_CODE, and ATTRIBUTE_APPLICATION_ID. Two business-key candidates exist as unique indexes: AK_REGION_ITEMS_U1 (the PK columns plus ZD_EDITION_NAME) and AK_REGION_ITEMS_U2 (REGION_CODE, REGION_APPLICATION_ID, DISPLAY_SEQUENCE, ZD_EDITION_NAME), the latter enforcing uniqueness of display ordering per region.

Common Use Cases and Queries

Typical use cases include auditing region layouts, diagnosing display ordering errors, tracing LOV wiring, and reporting on customization coverage. A representative query listing items for a region:

• SELECT attribute_code, attribute_application_id, display_sequence, item_style, required_flag FROM ak.ak_region_items WHERE region_code = :p_region AND region_application_id = :p_appid ORDER BY display_sequence;
• Join to AK_ATTRIBUTES to resolve attribute labels: SELECT i.region_code, a.attribute_name, i.display_sequence FROM ak.ak_region_items i, ak.ak_attributes a WHERE i.attribute_code = a.attribute_code AND i.attribute_application_id = a.attribute_application_id;
• Detect LOV usage: SELECT region_code, lov_region_code, lov_foreign_key_name FROM ak.ak_region_items WHERE lov_region_code IS NOT NULL;
• Trace defaulting APIs: SELECT region_code, region_defaulting_api_pkg, region_defaulting_api_proc FROM ak.ak_region_items WHERE region_defaulting_api_pkg IS NOT NULL;

Reporting usage monitors user-customizable (USER_CUSTOMIZABLE) versus administratively customizable (ADMIN_CUSTOMIZABLE) items, and inspects CSS_CLASS_NAME, TIP_TYPE, and TIP_MESSAGE_NAME for UI tuning.

Related Objects

• AK.AK_REGIONS — Parent region definition; joined via REGION_CODE.
• AK.AK_ATTRIBUTES — Master attribute list; joined via ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID.
• FND.FND_MENUS — Referenced through MENU_NAME and MENU_ID for menu-attached items.
• AK.AK_REGION_ITEMS_TL — Translation table keyed on REGION_CODE for language-specific labels.
• AK.AK_CATEGORY_USAGES — References REGION_CODE to associate regions with metadata categories.
• AK.AK_FLOW_PAGE_REGION_ITEMS — References REGION_CODE to place region items on flow pages.
• AK.AK_REGION_ITEMS_N1 through N7 — Supporting non-unique indexes aiding lookups by region, view usage, attribute, LOV, and nested region.