Results for “flow_code”

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

Overview

AK_FLOWS is a configuration table within the AK (Common Modules-AK) product schema in Oracle E-Business Suite, present in both the 12.1.1 and 12.2.2 releases. Its documented purpose is to define a flow and associate a primary page to that flow. In practical EBS terms, AK_FLOWS acts as the registry of navigable flows used by the HTML-based framework underlying many EBS self-service and administrative pages. Each row identifies a flow by its code and the application that owns it, and it designates the default or entry-point page displayed when the flow is invoked.

The table is owned by the AK schema and is validated in the ETRM 12.2.2 physical schema with 26 columns. Under a heuristic Data Vault classification mined from the foreign-key structure, AK_FLOWS exhibits hub-leaning characteristics: its business key is the pair (FLOW_CODE, FLOW_APPLICATION_ID), which is stable and referenced by dependent tables. This classification is offered as a modeling suggestion rather than a documented property of the EBS data dictionary.

Key Information Stored

The most significant columns are the following:

• FLOW_CODE — the identifier of the flow; together with the application ID, it forms the business key.
• FLOW_APPLICATION_ID — the application owning the flow; the second component of the business key.
• PRIMARY_PAGE_CODE — the code of the page designated as the flow's primary (entry) page.
• PRIMARY_PAGE_APPL_ID — the application owning the primary page, allowing a flow to point to a page in another application.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS who-columns recording audit information.
• ZD_EDITION_NAME — the editioning column introduced for the online patching architecture in EBS 12.2.

The AK_FLOWS_PK primary key consists of FLOW_CODE and FLOW_APPLICATION_ID, making the surrogate/business key pair explicit. A unique index, AK_FLOWS_U1, extends this with ZD_EDITION_NAME (FLOW_CODE, FLOW_APPLICATION_ID, ZD_EDITION_NAME), which is the business-key candidate required for editioned data during online patching.

Common Use Cases and Queries

Administrators and developers query AK_FLOWS to identify which page is presented when a flow is launched, to audit the mapping between flows and pages, and to troubleshoot navigation failures where a flow's primary page is missing or disabled.

A typical lookup joins the flow to its primary page and translations:

• List flows with their primary page: SELECT f.FLOW_CODE, f.FLOW_APPLICATION_ID, f.PRIMARY_PAGE_CODE, f.PRIMARY_PAGE_APPL_ID FROM AK.AK_FLOWS f;
• Retrieve translated flow names: join AK_FLOWS_TL on FLOW_CODE and FLOW_APPLICATION_ID.
• Find pages belonging to a flow: join AK_FLOW_PAGES on FLOW_CODE and FLOW_APPLICATION_ID.

Reporting use cases include impact analysis when a primary page is retired, and verification of DFF attribute usage across flows. Because of the 12.2 editioning column, queries targeting the runtime edition should filter on the active ZD_EDITION_NAME, most commonly the run edition value.

Related Objects

AK_FLOWS participates in several documented foreign-key relationships:

• AK_FLOWS_TL — the translation table; references AK_FLOWS via FLOW_CODE and FLOW_APPLICATION_ID, providing language-specific flow names.
• AK_FLOW_PAGES — the pages associated with a flow; references AK_FLOWS via FLOW_CODE and FLOW_APPLICATION_ID. AK_FLOWS also references AK_FLOW_PAGES through FLOW_CODE in the documented foreign-key listing, reflecting the primary-page association.

These relationships make AK_FLOWS the hub record that ties a flow to its pages and its translations, and any application or page-level utilities that resolve flow navigation ultimately depend on its contents.