Search Results ak_flow_pages_tl




Overview
Explore in AI Chat

Overview

The AK_FLOW_PAGES_TL table is a core repository for translated text within the Oracle E-Business Suite (EBS) framework, specifically for the AK (Common Modules-AK) product. It functions as a translation table (denoted by the "_TL" suffix) for the base table AK_FLOW_PAGES. This table's primary role is to store multilingual versions of descriptive content associated with application flow pages, enabling the EBS user interface to display page labels, prompts, and other translatable elements in a user's preferred language (NLS). Its existence is fundamental to the internationalization and localization capabilities of the Oracle Applications Framework (OAF) and other AK module components, ensuring a consistent user experience across global deployments in versions 12.1.1 and 12.2.2.

Key Information Stored

The table stores language-specific translations for attributes of a flow page. Its structure is defined by a composite primary key that uniquely identifies a translation record. This key consists of the flow and page identifiers from the base table, coupled with the language code. The critical columns are:

  • FLOW_CODE, FLOW_APPLICATION_ID, PAGE_CODE, PAGE_APPLICATION_ID: These columns form the foreign key link to the base AK_FLOW_PAGES table, identifying the specific flow and page whose attributes are being translated.
  • LANGUAGE: The ISO code for the language of the translated text (e.g., 'US' for American English, 'KO' for Korean).
  • Translated Descriptive Columns: While the provided metadata does not list them explicitly, typical "_TL" tables contain columns like PAGE_NAME, PAGE_DESCRIPTION, or other user-facing text attributes from the base table, replicated here for each supported language.

Common Use Cases and Queries

This table is primarily accessed by the EBS application runtime to render the UI in the session language. Common technical use cases include extracting translation sets for migration or reporting, and diagnosing missing translations. A typical query retrieves all translations for a specific flow and page to verify language coverage:

SELECT language, page_name
FROM ak_flow_pages_tl
WHERE flow_application_id = 660
AND flow_code = 'XX_CUST_FLOW'
AND page_application_id = 660
AND page_code = 'MAIN_PG'
ORDER BY language;

Another frequent pattern is a join with the base table to find pages lacking a translation in a target language, which is crucial for localization projects:

SELECT b.flow_code, b.page_code
FROM ak_flow_pages b
WHERE NOT EXISTS (
SELECT 1 FROM ak_flow_pages_tl t
WHERE t.flow_application_id = b.flow_application_id
AND t.flow_code = b.flow_code
AND t.page_application_id = b.page_application_id
AND t.page_code = b.page_code
AND t.language = 'DE'
);

Related Objects

The AK_FLOW_PAGES_TL table has a direct and singular foreign key relationship with its parent base table. This relationship is essential for maintaining data integrity between the core definition and its translations.

  • AK_FLOW_PAGES: This is the primary related table. The foreign key in AK_FLOW_PAGES_TL references the primary key of AK_FLOW_PAGES on the columns (FLOW_CODE, FLOW_APPLICATION_ID, PAGE_CODE, PAGE_APPLICATION_ID). All translation records are child records of a single parent record in this base table.