Results for “region_description”

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

Overview

The view AK_FLOW_PAGE_REGION_ITEMS_V is an APPS-owned database view registered in the Oracle E-Business Suite environment as VALID. It belongs to the AK (Common Modules – AK) product family, which provides the extensibility and personalization framework underlying most EBS application modules. Because that framework is technically shared across applications, the AK schema is present in every EBS installation, though this particular view is documented in the ETRM metadata as 10SC ONLY, indicating it is not a general-purpose, cross-application interface object.

Functionally, the view presents a fully denormalized, language-resolved representation of configuration data held in the flow page/region item tables. Each row describes a single flow page region item: which flow and page it belongs to, which region it references, which attribute it targets, and where the item navigates to. The view joins the base transaction table to multiple translation tables and resolves the translated names and descriptions of the page, region, attribute, and destination page using the session language (USERENV('LANG')). This makes it a convenient read-only construct for reporting, diagnostics, and integration scenarios that need human-readable flow configuration rather than coded identifiers.

Underlying Base Objects

According to the documented ETRM metadata, the view is defined over four base objects, each referenced through an APPS synonym:

• AK_FLOW_PAGE_REGION_ITEMS — the driving transactional table (AP alias), holding the flow, page, region, attribute, and destination-to-page references along with the 15 descriptive flexfield columns and standard audit columns.
• AK_FLOW_PAGES_TL — referenced twice. The APT1 instance resolves the current page name and description; the APT2 instance is outer-joined to resolve the destination (TO_) page name and description where a destination page exists.
• AK_REGIONS_TL — joined on region application ID and region code to supply the region name and description.
• AK_ATTRIBUTES_TL — referenced twice. The AAT1 instance resolves the targeted attribute name and description; AAT2 resolves the destination URL attribute name and description.

All translation joins are constrained with LANGUAGE = USERENV('LANG'), so the view returns text in the language of the querying session. The translation joins for the destination page and destination URL attribute are expressed as outer joins (indicated by the (+) operator), reflecting the fact that a flow page region item need not always define a navigation target.

Key Columns

• ROW_ID — the ROWID of the underlying AK_FLOW_PAGE_REGION_ITEMS row, exposed for update-style addressing.
• FLOW_APPLICATION_ID, FLOW_CODE — identify the owning flow.
• PAGE_APPLICATION_ID, PAGE_CODE, PAGE_NAME, PAGE_DESCRIPTION — identify and describe the page containing the region item.
• REGION_APPLICATION_ID, REGION_CODE, REGION_NAME, REGION_DESCRIPTION — identify and describe the target region.
• ATTRIBUTE_APPLICATION_ID, ATTRIBUTE_CODE, ATTRIBUTE_NAME, ATTRIBUTE_DESCRIPTION — identify and describe the attribute the item operates on.
• TO_PAGE_APPL_ID, TO_PAGE_CODE, TO_PAGE_NAME, TO_PAGE_DESCRIPTION — the destination page of the item, if any.
• TO_URL_ATTRIBUTE_APPL_ID, TO_URL_ATTRIBUTE_CODE, TO_ATTRIBUTE_NAME, TO_ATTRIBUTE_DESCRIPTION — the attribute supplying the destination URL.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segment values.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.

Common Use Cases and Queries

The most frequent scenario is locating every region item associated with a particular flow page, using the PAGE_CODE column as the search predicate. A representative query is:

• SELECT flow_code, page_code, page_name, region_code, region_name, attribute_code, attribute_name, to_page_code, to_page_name FROM apps.ak_flow_page_region_items_v WHERE flow_code = :flow_code AND page_code = :page_code ORDER BY region_code, attribute_code;

An alternative form resolves the same information by application identifier rather than flow code, which is useful when the flow code is not known in advance:

• SELECT flow_application_id, flow_code, page_code, region_name, attribute_name, to_page_name FROM apps.ak_flow_page_region_items_v WHERE flow_application_id = :app_id AND page_application_id = :page_app_id AND page_code = :page_code;

Because the view already resolves names and descriptions for four distinct base entities, integration and reporting programs can avoid writing their own translation-aware join logic. Typical consumers include diagnostics scripts that inspect personalized flow configuration, migration utilities that extract flow metadata between environments, and audit reports that track creation and last-update information for flow page region items. Note that the view is described as 10SC ONLY, so its use should be validated against the specific EBS release in scope—12.1.1 and 12.2.2 installations include the AK schema, but the presence and content of 10SC-specific rows should be confirmed before relying on the view for a given requirement.