Results for “gr_main_headings_tl”

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

Overview

GR_MAIN_HEADINGS_TL is the translation ("TL") table for Main Heading descriptions within the Process Manufacturing Regulatory Management (GR) module of Oracle E-Business Suite 12.1.1 and 12.2.2. The GR module supports the definition and maintenance of regulatory content — such as labels, safety text, and hazard statements — that must be presented in multiple languages. GR_MAIN_HEADINGS_TL stores the language-specific text that accompanies each Main Heading, allowing a single regulatory heading to carry translated descriptions across every installed language.

The table is owned by the GR schema and is documented as VALID in ETRM. In Oracle EBS, translation tables conventionally hold a composite primary key of the base entity identifier plus a LANGUAGE code, and GR_MAIN_HEADINGS_TL follows that convention: its business key is (MAIN_HEADING_CODE, LANGUAGE). The table therefore provides the multilingual layer over the base-language definitions held in GR_MAIN_HEADINGS_B. From a Data Vault modeling perspective, the metadata's heuristic classification is link; a modeler could treat the (MAIN_HEADING_CODE, LANGUAGE) pairing as a relationship linking a Main Heading to a Language, with the descriptive text as a dependent attribute.

Key Information Stored

GR_MAIN_HEADINGS_TL contains nine documented columns. The most significant are:

• MAIN_HEADING_CODE — the business identifier of the Main Heading; part of the composite primary key and the foreign key to GR_MAIN_HEADINGS_B.
• LANGUAGE — the language code for the translated row; part of the composite primary key and a foreign key to FND_LANGUAGES.
• MAIN_HEADING_DESCRIPTION — the translated text of the Main Heading, the table's principal payload.
• SOURCE_LANG — the language from which the translation originates; also a foreign key to FND_LANGUAGES, used to support the translation workflow.
• CREATED_BY, CREATION_DATE — audit columns recording who created the row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — audit columns recording the most recent change and its author.
• LAST_UPDATE_LOGIN — the login identifier associated with the last update.

The surrogate identity is not a single generated column but the composite primary key GR_MAIN_HEADINGS_TL_PK (MAIN_HEADING_CODE, LANGUAGE), which also serves as the unique business-key candidate. There is no separate documented unique index beyond this primary key.

Common Use Cases and Queries

The most frequent access pattern is retrieval of a translated heading for a given language, typically driven by a user's session language. A representative query joins the translation table to the base table:

• SELECT t.main_heading_code, t.main_heading_description FROM gr.gr_main_headings_tl t WHERE t.main_heading_code = :code AND t.language = USERENV('LANG');
• SELECT b.main_heading_code, t.language, t.main_heading_description FROM gr.gr_main_headings_b b, gr.gr_main_headings_tl t WHERE b.main_heading_code = t.main_heading_code ORDER BY b.main_heading_code, t.language;
• Translation coverage reporting, identifying headings lacking a row for a target language.
• Auditing recently changed translations using LAST_UPDATED_BY and LAST_UPDATE_DATE.
• Validating LANGUAGE and SOURCE_LANG values against FND_LANGUAGES.

Related Objects

• GR_MAIN_HEADINGS_B — the base (language-independent) table; joined on MAIN_HEADING_CODE.
• FND_LANGUAGES — referenced twice by foreign keys, on LANGUAGE and SOURCE_LANG.
• Other GR_%_TL tables — sibling translation tables in the GR module that follow the same composite key pattern.
• GR_MAIN_HEADINGS_TL_PK — the primary-key index enforcing the composite key.