Search Results per_grades_tl




Overview
Explore in AI Chat

Overview

PER_GRADES_TL is the translated (language-specific) child table of PER_GRADES in the Oracle E-Business Suite Human Resources (PER) module, owned by the HR schema. In Oracle EBS 12.1.1 and 12.2.2, grade definitions are stored in the base table PER_GRADES, while the user-visible, translatable text attributes of a grade — most notably its name — are stored one row per installed language in PER_GRADES_TL. This multilanguage design (TL) allows the same grade, identified by a single GRADE_ID, to display different names depending on the session language, supporting global, multilingual deployments without duplicating the grade's business definition.

The object is documented as VALID in the HR schema, with a primary key named PER_GRADES_TL_PK on the column pair (GRADE_ID, LANGUAGE). Under a heuristic Data Vault classification mined from the foreign-key structure, PER_GRADES_TL is modeled as standalone; the appropriate Data Vault treatment of a table of this shape is a satellite hanging off the grade hub, keyed by GRADE_ID, with LANGUAGE treated as a descriptive or multi-active attribute. This is offered as a modeling suggestion only — the operational EBS schema does not itself implement Data Vault structures.

Key Information Stored

The table contains nine documented columns. The most significant are:

  • GRADE_ID — the foreign-key surrogate identifier pointing to the base PER_GRADES definition; it is also the first component of the primary key.
  • LANGUAGE — the language code identifying the translation; it is the second component of the primary key. Together, (GRADE_ID, LANGUAGE) constitute the composite unique business key enforced by PER_GRADES_TL_PK.
  • SOURCE_LANG — the language from which the translated row was derived; used by the multilanguage framework to track the origin language of a translation.
  • NAME — the translated grade name; this is the primary user-facing attribute retrieved from this table.
  • CREATED_BY, CREATION_DATE — standard WHO-column audit attributes capturing the creating user and timestamp.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit attributes capturing the last modification user, timestamp, and login session.

The surrogate key is GRADE_ID (foreign key to PER_GRADES), while the business-key candidate is the unique index PER_GRADES_TL_PK over (GRADE_ID, LANGUAGE). Note that the table carries no independent surrogate primary key of its own beyond this composite.

Common Use Cases and Queries

Typical usage centers on retrieving a grade's display name in the correct language and on maintaining translations. A common reporting join selects the translated name alongside base grade attributes:

  • Joining to the base table: SELECT g.grade_id, t.name, t.language FROM per_grades g, per_grades_tl t WHERE g.grade_id = t.grade_id AND t.language = USERENV('LANG');
  • Verifying translation coverage: SELECT grade_id, COUNT(*) FROM per_grades_tl GROUP BY grade_id to find grades missing a given language row.
  • Auditing recent changes: filtering on LAST_UPDATE_DATE, LAST_UPDATED_BY to trace translation maintenance.
  • Bilingual validation: comparing SOURCE_LANG against LANGUAGE to confirm translations were derived from the expected source.

Because the table is a TL table, reports in a multilingual environment should always constrain LANGUAGE or supply a language-specific view rather than query the table unqualified.

Related Objects

The most significant related objects, based on the documented PK/FK relationship data, are:

  • PER_GRADES — the base table; join on GRADE_ID = PER_GRADES.GRADE_ID. This is the primary parent and the source of the foreign-key relationship.
  • PER_GRADES_TL_PK — the unique index/constraint enforcing (GRADE_ID, LANGUAGE).
  • HR schema TL views and APIs — grade definition concurrent programs and forms that read and write translation rows through the multilanguage framework.
  • Grade-related HR objects — grade rate and grade-step definitions (e.g., PER_GRADE_RATES) that depend on the grade identity established by PER_GRADES and displayed via this translation table.

Writers should treat PER_GRADES_TL strictly as the translation satellite of the grade entity and reference it through its composite key when resolving display names.