Results for “ak_flows_tl”

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

Overview

AK_FLOWS_TL is the translation (language-specific) child table of AK_FLOWS within the Oracle E-Business Suite Common Modules (AK) schema. AK_FLOWS stores the definition of flows — named business processes or configurable workflow constructs used by Oracle's Application Object Library and related AK-dependent products — while AK_FLOWS_TL holds the translatable text attributes associated with each flow, most notably the display name and description shown to users in their session language. In Oracle EBS 12.1.1 and 12.2.2, this table participates in the standard multilingual (MLS) pattern: language-independent definition rows reside in the base table, and each localized row is keyed by a language code in the _TL companion.

From a Data Vault modeling perspective, the metadata's heuristic classification is satellite-leaning. That is, AK_FLOWS_TL behaves as a descriptive satellite attached to the AK_FLOWS business key (FLOW_CODE plus FLOW_APPLICATION_ID), carrying attributes that change with language rather than with the flow's structural identity. Language acts as an additional qualifier on that satellite relationship.

Key Information Stored

The table contains 12 documented columns. The most operationally significant are listed below.

• FLOW_CODE — Identifier of the flow; part of the primary key and the join to AK_FLOWS.
• FLOW_APPLICATION_ID — The application that owns the flow; the second component of the composite key and join.
• LANGUAGE — The NLS language code for the translated row; completes the primary key.
• NAME — The translated display name of the flow, presented to users in the selected language.
• DESCRIPTION — The translated descriptive text for the flow.
• SOURCE_LANG — The source language from which the translation was derived, used by the MLS translation framework.
• ZD_EDITION_NAME — The editioning column introduced for Oracle EBS 12.2 online patching; it distinguishes edition-specific data and participates in the U1 unique index.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns recording who created and last modified each row and when.

Primary key: AK_FLOWS_TL_PK, defined on (FLOW_CODE, FLOW_APPLICATION_ID, LANGUAGE). This is the surrogate/unique row identifier used by the translation framework.

Business-key candidate: the unique index AK_FLOWS_TL_U1 covers (FLOW_CODE, FLOW_APPLICATION_ID, LANGUAGE, ZD_EDITION_NAME), making the flow key plus language plus edition the effective business uniqueness constraint in a 12.2 environment.

Common Use Cases and Queries

Reporting and integration against this table almost always joins the base table to resolve the correct translated text. A representative query retrieves the localized flow name for a given language:

• SELECT f.flow_code, t.name, t.description FROM ak.ak_flows f, ak.ak_flows_tl t WHERE f.flow_code = t.flow_code AND f.application_id = t.flow_application_id AND t.language = USERENV('LANG');

Typical scenarios include building flows navigation menus and picklists that display translated names, troubleshooting missing or stale translations where a flow appears untranslated, auditing translation coverage across languages using a query grouped by LANGUAGE, and confirming edition-scoped data correctness during 12.2 patching cycles via ZD_EDITION_NAME. Administrators also use the table to verify that the SOURCE_LANG value matches the intended base language.

Related Objects

• AK_FLOWS — Parent definition table; joined on AK_FLOWS_TL.FLOW_CODE = AK_FLOWS.FLOW_CODE and FLOW_APPLICATION_ID. This is the documented foreign-key relationship.
• AK_FLOWS_TL_PK — Primary key constraint over (FLOW_CODE, FLOW_APPLICATION_ID, LANGUAGE).
• AK_FLOWS_TL_U1 — Unique index adding ZD_EDITION_NAME to the key.
• AK_FLOWS_B / AK_FLOWS_VL — MLS base and view layer typically exposed alongside the _TL table for translated access.
• AK_FLOW_STEPS / AK_FLOW_STEP_TL — Related flow-component and translation tables for step-level content.
• FND_APPLICATION (APPLICATION_ID) — Resolves the owning application referenced by FLOW_APPLICATION_ID.