Search Results per_abs_attendance_types_tl




Overview
Explore in AI Chat

Overview

PER_ABS_ATTENDANCE_TYPES_TL is a translation (TL) table in the HR schema of Oracle E-Business Suite, belonging to the PER (Human Resources) product family. It holds the language-specific, translated text attributes for Absence Types — the configuration entities that define categories of employee absence such as sickness, vacation, or statutory leave. In Oracle EBS, every seeded or user-defined lookup that requires multilingual display is stored in a pair of tables: a base table that carries the primary identifier and non-translatable attributes, and a companion "_TL" table that carries the translated name and description keyed by language. This table is the translated half of the Absence Attendance Types definition, enabling the same absence type to present a different display name depending on the session language of the user.

Heuristic Data Vault classification, mined from the foreign-key structure, identifies this object as standalone. As a modeling suggestion, this reflects the fact that the table holds descriptive, language-dependent attributes attached to a single parent entity rather than participating in a many-to-many relationship. Functionally it behaves like a satellite surrounding the absence-type identifier, carrying its translated descriptive columns and standard audit metadata. Because it is standalone with no outgoing business foreign keys, it should be joined to its parent via the shared identifier rather than treated as an independent hub.

Key Information Stored

The table is documented with nine physical columns in the ETRM 12.2.2 schema. The most significant are:

  • ABSENCE_ATTENDANCE_TYPE_ID — the surrogate identifier linking the row to its parent Absence Attendance Type. Combined with LANGUAGE it forms the composite primary key, so this column is both part of the surrogate PK and the effective business-key join column to the base table.
  • LANGUAGE — the NLS language code (for example US or FR) identifying which translation this row provides. Together with the identifier above it constitutes the full primary key PER_ABS_ATTENDANCE_TYPES_TL_PK, which is the only documented unique index and therefore the business-key candidate.
  • SOURCE_LANG — records the language in which the source (typically the base table) row was originally authored. Oracle uses SOURCE_LANG to determine whether a given translation has been updated relative to the source, and to decide fallback behavior when no translation exists for the requested language.
  • NAME — the translated display name of the absence type, presented to end users in forms, self-service pages, and reports in the selected session language.
  • CREATED_BY, CREATION_DATE — standard WHO audit columns capturing the user and timestamp of row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE — standard WHO audit columns capturing the most recent modification.
  • LAST_UPDATE_LOGIN — the login identifier associated with the last update, used for audit and concurrency tracking.

The surrogate primary key is the composite (ABSENCE_ATTENDANCE_TYPE_ID, LANGUAGE); there is no separate surrogate value in the documented column list, and the unique index on those two columns is the only documented business-key candidate.

Common Use Cases and Queries

The primary use case is multilingual reporting and user-interface generation. Applications and custom reports join this table to the base Absence Attendance Types table, filtering on the desired LANGUAGE to return the correctly translated NAME. A typical query pattern restricts the translation table to a single language, for example:

  • Selecting the translated name for a specific type: SELECT name FROM per_abs_attendance_types_tl WHERE absence_attendance_type_id = :p_id AND language = USERENV('LANG');
  • Listing all absence types in the session language by joining the base table to its translation on ABSENCE_ATTENDANCE_TYPE_ID with a LANGUAGE predicate.
  • Detecting untranslated or stale entries by comparing SOURCE_LANG against available LANGUAGE rows, useful during localization or upgrade validation.
  • Auditing configuration changes through the CREATED_BY and LAST_UPDATED_BY columns, for example identifying all absence-type translations created or modified after a given CREATION_DATE.

Because translations are frequently read at runtime, queries should always constrain LANGUAGE to avoid returning multiple rows per identifier, which would otherwise violate the intent of the composite key and produce duplicate output.

Related Objects

  • PER_ABS_ATTENDANCE_TYPES (base table) — the parent entity; joined on ABSENCE_ATTENDANCE_TYPE_ID.
  • PER_ABS_ATTENDANCE_TYPES_TL_PK — the composite primary key and unique index on (ABSENCE_ATTENDANCE_TYPE_ID, LANGUAGE).
  • PER_ABSENCE_ATTENDANCES — records individual employee absence instances referencing an absence type identifier.
  • PER_ABSENCE_ATTENDANCE_REASONS — reason codes associated with absence types, often defined alongside the translated type definition.
  • FND_LANGUAGES — the lookup of installed languages referenced by the LANGUAGE and SOURCE_LANG values.
  • HR_ABSENCE_API / Absence Type configuration PL/SQL APIs — programmatic entry points that read and maintain absence-type translations.
  • FND_TERRITORIES and related NLS views — supplementary localization objects commonly joined when presenting translated content.

These objects form the surrounding configuration and transactional context for absence management, with PER_ABS_ATTENDANCE_TYPES_TL supplying the translated presentation layer for the absence-type definition.