Search Results ozf_worksheet_headers_tl




Overview
Explore in AI Chat

Overview

The OZF_WORKSHEET_HEADERS_TL table is a core data object within the Oracle Trade Management (OZF) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a translation table, specifically designed to store multilingual text for the descriptive attributes of worksheet headers. Its primary role is to support the global deployment of the Trade Management application by enabling the storage of user-facing content, such as names and descriptions, in multiple languages. This table is integral to the system's ability to present a localized user interface and reports based on the session language of the user. It operates in conjunction with its base table, OZF_WORKSHEET_HEADERS_B, which holds the non-translatable, structural data for worksheet headers.

Key Information Stored

The table's structure is characteristic of Oracle EBS translation tables. It stores language-specific textual data linked to a primary entity. The key columns, as defined by its primary key constraint (OZF_WORKSHEET_HEADERS_TL_PK), are WORKSHEET_HEADER_ID and LANGUAGE. The WORKSHEET_HEADER_ID is a foreign key that uniquely identifies the corresponding header record in the OZF_WORKSHEET_HEADERS_B base table. The LANGUAGE column holds the code (e.g., 'US', 'FR', 'DE') representing the language of the translated text. While the specific descriptive columns are not detailed in the provided metadata, typical translation tables in this context include columns such as WORKSHEET_HEADER_NAME and DESCRIPTION to hold the translated values for the header's name and descriptive text, respectively. The table also standardly includes SOURCE_LANG, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN columns for audit and synchronization purposes.

Common Use Cases and Queries

The primary use case for this table is retrieving worksheet header information in a user's preferred language for display in forms, reports, and online screens. A common reporting pattern involves joining this table with its base table and other related transactional tables. For instance, to generate a list of worksheet headers with their descriptions in the current session language, a query would typically filter on the LANGUAGE column using the userenv('LANG') function or a session variable. Sample SQL to join the translation table with its base table for a specific language would be:

  • SELECT b.worksheet_header_id, tl.name, tl.description, b.status_code
  • FROM ozf_worksheet_headers_b b,
  • ozf_worksheet_headers_tl tl
  • WHERE b.worksheet_header_id = tl.worksheet_header_id
  • AND tl.language = USERENV('LANG');

This table is also critical during the implementation of additional languages, where seed data or custom translations are populated into this table for each supported language.

Related Objects

The OZF_WORKSHEET_HEADERS_TL table has a direct and dependent relationship with the OZF_WORKSHEET_HEADERS_B table, which is its sole parent table as per the documented foreign key. The relationship is defined as:

  • Foreign Key Reference: OZF_WORKSHEET_HEADERS_TL.WORKSHEET_HEADER_ID → OZF_WORKSHEET_HEADERS_B (Presumably on the WORKSHEET_HEADER_ID column in the base table).

This structure indicates that for every record in the translation table, there must be a corresponding master record in OZF_WORKSHEET_HEADERS_B. The translation table is typically accessed via database views provided by Oracle, which automatically handle the language filtering. While not specified in the metadata, it is common for other transactional tables within the OZF schema, such as those storing worksheet lines or allocations, to ultimately join to OZF_WORKSHEET_HEADERS_B, indirectly relying on the translations stored in this TL table for user-facing labels and descriptions.