Results for “to_page_code”

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

Overview

AK_FLOW_PAGE_REGION_ITEMS is a table in the AK (Common Modules-AK) schema of Oracle E-Business Suite. Its documented purpose is to link a region item to a region, making it an association or junction table within the Oracle EBS personalization and extensibility framework (also referred to as the "AK" or Application Object Library-adjacent metadata infrastructure). The table participates in defining the flow of pages and regions across forms and self-service UI constructs, associating attributes (region items) with the regions in which they appear.

Mined from its foreign key structure, the Data Vault classification heuristic suggests this object is best modeled as a link table. This is a modeling suggestion rather than a prescriptive label: the table exists primarily to resolve many-to-many relationships between flow/page/region definitions and region items (attributes), rather than to store descriptive state about an independent business entity.

Key Information Stored

The physical schema in 12.2.2 documents 34 columns. The principal columns are:

• FLOW_CODE and FLOW_APPLICATION_ID — identify the flow (with its owning application) to which the page and region belong.
• PAGE_CODE and PAGE_APPLICATION_ID — identify the page within the flow.
• REGION_CODE and REGION_APPLICATION_ID — identify the region belonging to the page.
• ATTRIBUTE_CODE and ATTRIBUTE_APPLICATION_ID — identify the region item (attribute) linked to that region.
• TO_PAGE_CODE and TO_PAGE_APPL_ID — target page reference, used when the region item navigates to another page.
• TO_URL_ATTRIBUTE_CODE and TO_URL_ATTRIBUTE_APPL_ID — target URL attribute reference for navigation semantics.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns, available for customer-defined context and segment storage.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS "WHO" audit columns.
• ZD_EDITION_NAME — the editioning column supporting Online Patching (adop) in 12.2.x, also present in the unique index.

Two constraints define the keys. The primary key, AK_FLOW_PAGE_REGION_ITEMS_PK, is composed of the eight business identifiers: FLOW_CODE, FLOW_APPLICATION_ID, PAGE_CODE, PAGE_APPLICATION_ID, REGION_CODE, REGION_APPLICATION_ID, ATTRIBUTE_CODE, and ATTRIBUTE_APPLICATION_ID. A unique index, AK_FLOW_PAGE_REGION_ITEMS_U1, replicates the same eight columns plus ZD_EDITION_NAME. Because these columns are the documented business-key candidates rather than a generated surrogate identifier, the design uses a natural composite key throughout; there is no separately documented system-generated surrogate column.

Common Use Cases and Queries

This table is most commonly queried to determine which region items appear on a given page or region, or to trace navigation targets configured for a region item. Typical reporting patterns include:

• Listing all region items for a specific flow/page/region combination by filtering on the composite business key.
• Resolving navigation targets by inspecting TO_PAGE_CODE / TO_URL_ATTRIBUTE_CODE, useful when auditing page flow configuration.
• Joining to AK_REGION_ITEMS to obtain the descriptive name or properties of an attribute, and to AK_FLOW_PAGE_REGIONS to obtain region-level context.

A representative query joining the parent region definition to the linked region items:

SELECT r.FLOW_CODE, r.PAGE_CODE, r.REGION_CODE, i.ATTRIBUTE_CODE, i.TO_PAGE_CODE
FROM AK.AK_FLOW_PAGE_REGION_ITEMS i,
AK.AK_FLOW_PAGE_REGIONS r
WHERE i.FLOW_APPLICATION_ID = r.FLOW_APPLICATION_ID
AND i.FLOW_CODE = r.FLOW_CODE
AND i.PAGE_CODE = r.PAGE_CODE
AND i.REGION_CODE = r.REGION_CODE;

Because the table uses natural composite keys and carries the ZD_EDITION_NAME column, queries under 12.2.x Online Patching should remain edition-aware, and any custom data manipulation should respect the editioning view rather than accessing the base table directly.

Related Objects

The foreign key relationships documented for AK_FLOW_PAGE_REGION_ITEMS establish its closest dependencies:

• AK_FLOW_PAGE_REGIONS — parent flow/page/region definition. Joined on FLOW_APPLICATION_ID, FLOW_CODE, PAGE_CODE, and REGION_CODE.
• AK_REGION_ITEMS — the region item (attribute) master. Joined on REGION_CODE, REGION_APPLICATION_ID, ATTRIBUTE_CODE, and ATTRIBUTE_APPLICATION_ID.

Beyond these documented parent tables, related objects in the AK framework typically include AK_FLOW_PAGES (defining pages within flows) and the AK_ATTRIBUTES / attribute definition tables underlying AK_REGION_ITEMS, all of which participate in the flow, page, and region metadata model. Collectively, these objects supply the configuration that drives Oracle EBS personalization, page navigation, and attribute placement within the common AK module.