Search Results per_jobs_tl

Overview

PER_JOBS_TL is the translation table for jobs within the Oracle E-Business Suite Human Resources (PER) module. In Oracle EBS 12.1.1 and 12.2.2, the PER schema employs a multilingual (MLS) design pattern in which language-independent attributes are stored in a base table (PER_JOBS) and language-dependent, translatable attributes are stored in a corresponding _TL table. PER_JOBS_TL holds the translated text for each job definition, allowing the same job to display a localized name according to the user's session language. The object is owned by the HR schema and holds a VALID status in the documented environment.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is standalone. This suggests that PER_JOBS_TL may be modeled as an independent structure rather than as a conventional satellite tied to a parent hub through a defined FK chain. In practice, however, it functions logically as the descriptive, language-dependent companion to the PER_JOBS business entity, carrying translated attributes keyed by job and language.

Key Information Stored

The table contains nine documented columns. Its primary key, PER_JOBS_TL_PK, is composed of two columns: JOB_ID and LANGUAGE. Together these form the unique business-key candidate that identifies one translated row per job per language.

• JOB_ID — Surrogate identifier linking the translated row to its parent job in PER_JOBS; part of the composite primary key.
• LANGUAGE — The language code for the translated content; the second component of the composite primary key.
• SOURCE_LANG — The language in which the source text was originally entered, used by the MLS framework for translation tracking.
• NAME — The translated display name of the job, the primary user-facing translatable attribute.
• CREATED_BY — The user who created the translated row.
• CREATION_DATE — The date and time the translated row was created.
• LAST_UPDATED_BY — The user who most recently modified the row.
• LAST_UPDATE_DATE — The date and time of the most recent modification.
• LAST_UPDATE_LOGIN — The login session associated with the last update, used for audit purposes.

The audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) follow the standard EBS WHO column convention and support concurrency and traceability.

Common Use Cases and Queries

The most frequent scenario is joining PER_JOBS_TL to PER_JOBS to retrieve a localized job name while filtering by a specific language. A representative query pattern is:

• Localized job lookup: SELECT j.JOB_ID, jt.NAME FROM PER_JOBS j, PER_JOBS_TL jt WHERE j.JOB_ID = jt.JOB_ID AND jt.LANGUAGE = USERENV('LANG');
• Bilingual reporting: compare SOURCE_LANG against LANGUAGE to identify rows still pending translation or mismatched against the base language.
• Audit and change tracking: inspect LAST_UPDATED_BY and LAST_UPDATE_DATE to determine which translations were recently maintained.
• Integration and interface feeds: extract JOB_ID and NAME for extraction into downstream reporting or data warehouse layers, respecting the composite key to avoid duplicates.

Because translations are language-specific, queries must always constrain LANGUAGE to avoid returning multiple rows per job.

Related Objects

The following objects are most significant when working with PER_JOBS_TL:

• PER_JOBS — The base table holding language-independent job attributes; joined on JOB_ID.
• PER_JOBS_TL_PK — The unique index enforcing the composite primary key (JOB_ID, LANGUAGE).
• FND_LANGUAGES — Reference table resolving installed language codes used in LANGUAGE and SOURCE_LANG.
• PER_JOB_GROUPS — Job group definitions that reference jobs and benefit from translated names.
• PER_JOB_FAMILY_F — Job family associations linking jobs to families.
• PER_POSITIONS / PER_POSITION_DEFINITIONS — Position definitions that consume job data for organizational reporting.
• HR_JOBS_API — Public API used to create and maintain job definitions, which cascades to translation rows.

These relationships make PER_JOBS_TL essential for any multilingual reporting, localization, or integration effort involving job data in Oracle EBS.