Search Results ak_attribute_code

Overview

ICX_POR_REALMS_FORM_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the ICX (Oracle iProcurement) product family. It is a simple, non-materialized join view whose purpose is to expose the realm definitions used by the iProcurement and Oracle Internet Procurement "realms" security model in a form suitable for form-based lookups and attribute administration. In the iProcurement architecture, a "realm" is a named grouping of catalog content and purchasing functionality that is assigned to users or responsibility-based access rules. The view therefore acts as a thin presentation layer over the realm header and translation tables, flattening the base data into a single denormalized row per realm and providing the internal attribute code that drives form-level and AK (Application Kit) attribute definitions.

The view's status is VALID in both Oracle EBS 12.1.1 and 12.2.2, and its structure is unchanged between those releases. It is referenced by iProcurement form and lookup infrastructure rather than by end-user pages directly, so it typically appears in form personalization, attribute registration, and ad hoc reporting rather than in standard concurrent programs.

Underlying Base Objects

The view is defined over two base objects, both referenced through APPS synonyms:

• ICX_POR_REALMS (synonym) — the primary realm definition table, supplying the ROWID, the REALM_ID, and the AK_ATTRIBUTE_CODE. This is the base-table row that carries the realm's internal identity and its associated AK attribute mapping.
• ICX_POR_REALMS_TL (synonym) — the translated (_TL) table, supplying the language-specific REALM_NAME and REALM_DESCRIPTION. Because it is a _TL table, it holds one row per realm per installed language and resolves the correct text for the session language via the standard language pattern.

The join condition is WHERE IPR.REALM_ID = IPRT.REALM_ID. The view does not aggregate or filter beyond this equijoin, so it preserves one logical row per realm per language and inherits the standard behavior of a _TL-based view. Both underlying objects are exposed to the APPS schema through synonyms, which is why the view can be created and queried entirely within APPS without qualifying the base schema.

Key Columns

• ROW_ID — the ROWID of the ICX_POR_REALMS row (aliased IPR.ROWID). Used by forms infrastructure for row-level identification and optimistic locking.
• REALM_ID — the unique numeric identifier of the realm; the primary join key between the base table and its translation table.
• AK_ATTRIBUTE_CODE — the attribute code that associates the realm with an AK (Oracle Application Kit) attribute definition. This is the column most directly relevant to searches for "ak_attribute_code", since it makes the attribute mapping queryable through a simple SELECT.
• REALM_NAME — the translated display name of the realm as presented to users and administrators.
• REALM_DESCRIPTION — the translated description providing the functional purpose of the realm.

Common Use Cases and Queries

Typical uses include confirming which AK attribute code is bound to a given realm, validating that realm names have been translated for the session language, and driving form personalization or LOV queries that resolve REALM_ID to a user-friendly name. A representative query listing all realms with their attribute codes is:

• SELECT realm_id, ak_attribute_code, realm_name, realm_description FROM apps.icx_por_realms_form_v ORDER BY realm_name;
• SELECT ak_attribute_code FROM apps.icx_por_realms_form_v WHERE realm_id = :realm_id;
• SELECT v.realm_name, v.ak_attribute_code FROM apps.icx_por_realms_form_v v WHERE v.realm_name LIKE :search_criteria;

Because the view is a straight join with no aggregation, it performs well for form LOVs and reporting extracts, and it can be joined to other iProcurement objects on REALM_ID when building customized queries.