Results for “ak_flow_page_regions”

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

Overview

AK_FLOW_PAGE_REGIONS is a table in the AK (Common Modules-AK) schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It is a configuration repository that links a region to a page within the Oracle EBS "flow" framework — the metadata-driven infrastructure that defines how self-service pages, regions, and their constituent items are assembled at runtime. Each row binds a specific AK_REGIONS definition to a specific AK_FLOW_PAGES definition for a given flow, effectively describing the composition of a page: which regions appear on it, in what order, using what layout, and how regions nest through parent-child relationships.

Because the table records associations between independently defined entities (pages, regions, flows) rather than holding descriptive attributes of any single subject, the heuristic Data Vault classification of the mined relationship structure is hub-leaning, with link-like characteristics. This suggests a modeling approach in which AK_FLOW_PAGE_REGIONS is treated as the resolved intersection of page, region, and flow hubs, with its descriptive columns (display sequence, region style, layout attributes) carried as link-level context.

Key Information Stored

The physical schema in 12.2.2 documents 34 columns. The primary key, AK_FLOW_PAGE_REGIONS_PK, is a composite surrogate spanning FLOW_APPLICATION_ID, PAGE_CODE, PAGE_APPLICATION_ID, REGION_CODE, FLOW_CODE, and REGION_APPLICATION_ID — the full set of foreign-key coordinates that uniquely identify a page-region assignment. The unique index AK_FLOW_PAGE_REGIONS_U1 covers the same business columns plus ZD_EDITION_NAME, reflecting the multi-tenant editioning column used in 12.2.2.

• FLOW_CODE / FLOW_APPLICATION_ID — the flow to which the page and region belong.
• PAGE_CODE / PAGE_APPLICATION_ID — the page being composed.
• REGION_CODE / REGION_APPLICATION_ID — the region assigned to the page.
• PARENT_REGION_CODE / PARENT_REGION_APPLICATION_ID — self-referencing columns enabling nested (child) region hierarchies.
• DISPLAY_SEQUENCE — ordering of the region within the page.
• REGION_STYLE — rendering style applied to the region.
• NUM_COLUMNS — column layout for the region container.
• ICX_CUSTOM_CALL — custom call hook for self-service customization.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) context and segments.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — audit columns maintained by EBS.
• ZD_EDITION_NAME — editioning discriminator introduced in 12.2.2.

Common Use Cases and Queries

Typical scenarios include tracing page composition during personalization or form-function diagnostics, auditing region display order, and reporting on region reuse across pages.

To list regions on a specific page in display order:

• SELECT REGION_CODE, DISPLAY_SEQUENCE, PARENT_REGION_CODE FROM AK.AK_FLOW_PAGE_REGIONS WHERE PAGE_CODE = :page AND PAGE_APPLICATION_ID = :app ORDER BY DISPLAY_SEQUENCE;

To find all pages using a given region:

• SELECT FLOW_CODE, PAGE_CODE, REGION_CODE FROM AK.AK_FLOW_PAGE_REGIONS WHERE REGION_CODE = :region;

Nested-region analysis uses the self-join on PARENT_REGION_CODE / PARENT_REGION_APPLICATION_ID to reconstruct the region tree for a page.

Related Objects

• AK_FLOW_PAGES — joined via FLOW_CODE, FLOW_APPLICATION_ID, PAGE_CODE, PAGE_APPLICATION_ID; supplies page header data and the PRIMARY_REGION reference.
• AK_REGIONS — joined via REGION_CODE and REGION_APPLICATION_ID; defines the region's own attributes.
• AK_FLOW_PAGE_REGION_ITEMS — child table referencing this object's full composite key; holds items belonging to each page-region assignment.
• AK_FLOW_REGION_RELATIONS — references this table via FLOW_APPLICATION_ID, FROM_PAGE_CODE, FROM_REGION_CODE, and related columns, capturing navigation between regions.
• AK_FLOW_PAGE_REGIONS — self-referencing through PARENT_REGION_CODE/PARENT_REGION_APPLICATION_ID for hierarchy queries.