Results for “absence_overlap_flag”

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

Overview

PER_ABS_ATTENDANCE_TYPES_VL is an APPS-owned, VALID database view within the PER (Human Resources) product family in Oracle EBS 12.1.1 and 12.2.2. It presents absence attendance type information in the language of the current user session. The "_VL" suffix denotes a "view with language," a standard Oracle EBS construct that joins the base transactional table to its translation table so that the descriptive name of each absence attendance type is returned in the session’s language rather than in a fixed language.

The view plays a central role in absence management reporting and integration. Absence attendance types define the categories of absence that employees can record, such as vacation, sickness, or other leave. Because the view resolves the translated name automatically via the USERENV('LANG') construct, consumers of the view—reporting tools, concurrent programs, APIs, and external integrations—receive a fully localized description without needing to perform their own joins to the translation table. This makes PER_ABS_ATTENDANCE_TYPES_VL the preferred access path for retrieving absence type definitions in the user’s language.

Underlying Base Objects

The view is defined over two referenced base objects, both exposed as synonyms in the APPS schema:

• PER_ABSENCE_ATTENDANCE_TYPES — the primary table holding the absence attendance type definition, including the identifier, business group, dates, category, and the INCREASING_OR_DECREASING_FLAG.
• PER_ABS_ATTENDANCE_TYPES_TL — the translation table holding the language-specific NAME for each absence attendance type, keyed by ABSENCE_ATTENDANCE_TYPE_ID and LANGUAGE.

The view joins these two objects on ABSENCE_ATTENDANCE_TYPE_ID and restricts the translation rows to those matching the current session language, so that each absence type appears once with its name rendered in the appropriate language. The alias B refers to the base table and TL refers to the translation table within the view text, and the ROW_ID column is derived from the base table’s ROWID.

Key Columns

The view exposes a broad set of columns, of which the following are most significant:

• ROW_ID — the ROWID of the underlying base table row.
• ABSENCE_ATTENDANCE_TYPE_ID — the primary key identifying the absence attendance type.
• BUSINESS_GROUP_ID — the business group that owns the absence type.
• INPUT_VALUE_ID — reference to the input value used to name the absence type.
• DATE_EFFECTIVE / DATE_END — the effective date range during which the absence type is valid.
• ABSENCE_CATEGORY — the category classification of the absence.
• HOURS_OR_DAYS — indicates whether the absence is measured in hours or days.
• INCREASING_OR_DECREASING_FLAG — indicates whether the absence type increases or decreases the associated accrual or balance; this is the column most directly relevant to the user’s search term.
• NAME — the translated name of the absence attendance type, sourced from the translation table.
• INFORMATION_CATEGORY / INFORMATION1–INFORMATION20 and ATTRIBUTE_CATEGORY / ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield and developer extensibility columns.
• Standard WHO columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER, and the concurrent program columns REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

The view is typically queried to enumerate the absence types available to a business group, to report on accrual direction, or to drive absence entry forms and integrations. A straightforward listing of absence types with their names and direction indicator might be written as:

SELECT absence_attendance_type_id, name, absence_category, hours_or_days, increasing_or_decreasing_flag, date_effective, date_end FROM per_abs_attendance_types_vl WHERE business_group_id = :p_business_group_id ORDER BY name;

Because the view automatically filters the translation table by USERENV('LANG'), queries against it return localized names with no additional join. Typical uses include validating that an absence type exists for a business group, determining whether an absence type increases or decreases a balance before processing an absence entry, and populating list-of-values or lookup selectors. Developers should note that the view is read-only and that the primary key is ABSENCE_ATTENDANCE_TYPE_ID; joins to absence records or accrual data should be performed on that identifier.