Results for “safety_category_code”

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

Overview

The GR_SAFETY_CATEGORIES_TL table is a translation table within the Oracle E-Business Suite Process Manufacturing Regulatory Management module (GR). It stores the safety category code in multiple languages, providing the multilingual descriptive text associated with each safety category used in regulatory and safety compliance workflows. The "_TL" suffix is the standard EBS convention for translation tables, indicating that each row represents a language-specific rendition of a base (non-translated) entity.

In Oracle EBS 12.1.1 and 12.2.2, this table is owned by the GR schema and is documented as VALID. Its heuristic Data Vault classification, mined from the foreign key structure, is standalone. As a modeling suggestion rather than a documented fact, this classification indicates that GR_SAFETY_CATEGORIES_TL does not participate as a dependent link in a larger hub-and-satellite network; rather, it behaves as an independent reference object whose language-dependent attribute text supports safety category lookup and reporting.

Key Information Stored

The table contains nine documented columns. The primary key and the most significant data-bearing columns are:

• SAFETY_CATEGORY_CODE — The business identifier for the safety category; together with LANGUAGE it forms the GR_SAFETY_CATEGORIES_TL_PK.
• LANGUAGE — The ISO/native language indicator that qualifies each translated row; the second component of the composite primary key.
• SAFETY_CATEGORY_DESCRIPTION — The translated, language-specific description of the safety category, which is the primary user-facing text returned by this table.
• SOURCE_LANG — Identifies the source language from which the translation was derived, supporting localization workflows.
• CREATED_BY, CREATION_DATE — Standard EBS WHO-column audit fields recording which user created the translation row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard audit fields capturing the most recent modification context for each translated row.

The surrogate primary key GR_SAFETY_CATEGORIES_TL_PK is defined on (SAFETY_CATEGORY_CODE, LANGUAGE), which is also the documented unique index and the business-key candidate. No separate numeric surrogate identifier is documented; the composite business key serves as the row identity.

Common Use Cases and Queries

Because it is a translation table, GR_SAFETY_CATEGORIES_TL is typically joined to its base table on SAFETY_CATEGORY_CODE and filtered by the session or reporting language. A common pattern retrieves the description in a specific language:

• Look up the English description for all safety categories: SELECT safety_category_code, safety_category_description FROM gr_safety_categories_tl WHERE language = 'US';
• Join to the base safety categories table to validate that every base row has a translation: SELECT b.safety_category_code FROM gr_safety_categories_b b LEFT JOIN gr_safety_categories_tl t ON b.safety_category_code = t.safety_category_code AND t.language = USERENV('LANG');
• Detect missing or stale translations by comparing SOURCE_LANG and LAST_UPDATE_DATE across languages.
• Regulatory reporting extracts that require localized safety category names for multi-country submissions.

Report developers frequently build language-specific LOVs and descriptive flexfield reporting queries from this table.

Related Objects

• GR_SAFETY_CATEGORIES_B — The base (non-translated) safety categories table; joined on SAFETY_CATEGORY_CODE.
• GR_SAFETY_CATEGORIES_VL — The multilingual view unioning base and translation data.
• GR_SAFETY_CATEGORIES_TL_PK — The primary key constraint/index enforcing uniqueness of (SAFETY_CATEGORY_CODE, LANGUAGE).
• FND_LANGUAGES — The language reference validating LANGUAGE values.
• GR_SAFETY_CATEGORIES_B_UK — The base-table unique key on SAFETY_CATEGORY_CODE, referenced by the translation join.