Results for “date_projected_start”

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

Overview

PER_ABSENCE_ATTENDANCES_V is an APPS-owned database view within the PER (Human Resources) product family of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It presents employee periods of absence, consolidating transactional absence records with their defining absence types, reasons, person details, and legislative statutory-sick-pay attributes. The view is not a standalone table; it is a denormalized read layer over the core absence schema, exposing the fully joined result set required by HRMS absence reporting, absence analytics, and integration interfaces. Because it carries person identifiers, absence dates, hour and day quantities, and absence categorization, it is the standard access point for both seeded and custom reports that must reproduce absence data without navigating the individual base entities. The view text selects from the absence attendance entity and joins across absence types, input values, lookup meanings, people records, and maternity records. It also exposes the descriptive flexfield segment ABS_INFORMATION_CATEGORY and segments ABS_INFORMATION1 through ABS_INFORMATIONn, which is directly relevant to searches targeting ABS_INFORMATION9 and the related context segment. The presence of ROWID, OBJECT_VERSION_NUMBER, and the WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) confirms the view is defined against an editable base and can be used for both query and controlled DML scenarios.

Underlying Base Objects

The documented base objects referenced by PER_ABSENCE_ATTENDANCES_V are PER_ABSENCE_ATTENDANCES, PER_ABS_ATTENDANCE_REASONS, PER_ABS_ATTENDANCE_TYPES_VL, PER_ALL_PEOPLE_F, HR_LOOKUPS, PAY_INPUT_VALUES_F and its translation table, SSP_MATERNITIES, and the HR_API package. PER_ABSENCE_ATTENDANCES is the driving table holding each absence occurrence; the view aliases it as ABA. PER_ABS_ATTENDANCE_TYPES_VL supplies the absence type name, category, input value identifier, and the HOURS_OR_DAYS and INCREASING_OR_DECREASING_FLAG controls. PER_ABS_ATTENDANCE_REASONS provides the absence reason description. PER_ALL_PEOPLE_F is joined twice — once for the person and once for the authorizing person — returning the full name and either the employee number or, where absent, the NPW_NUMBER. HR_LOOKUPS resolves the meaning of the absence category. PAY_INPUT_VALUES_F and its multilingual table supply the element type and unit of measure, while SSP_MATERNITIES supplies the maternity due date. HR_API is the business logic package associated with the underlying absence API. All non-view base names are exposed as APPS synonyms.

Key Columns

• ABSENCE_ATTENDANCE_ID — primary identifier of the absence record; used for joins and DML.
• PERSON_ID / FULL_NAME / EMPLOYEE_NUMBER — the absent person, with NPW_NUMBER fallback for non-payroll workers.
• DATE_START, DATE_END, TIME_START, TIME_END — actual absence period; projected start and end dates are also exposed for in-progress absences.
• DATE_NOTIFICATION, ACCEPT_LATE_NOTIFICATION_FLAG, REASON_FOR_NOTIFICATION_DELAY — sickness notification handling.
• ABSENCE_DAYS, ABSENCE_HOURS — duration in the unit governed by HOURS_OR_DAYS.
• ABSENCE_ATTENDANCE_TYPE_ID, NAME, ABSENCE_CATEGORY, CATEGORY_MEANING — type and category context.
• AUTHORISING_PERSON_ID, PEP2.FULL_NAME — the approving person.
• SICKNESS_START_DATE, SICKNESS_END_DATE, LINKED_ABSENCE_ID, SSP1_ISSUED, PREGNANCY_RELATED_ILLNESS, MATERNITY_ID, DUE_DATE — statutory sick pay and maternity linkage.
• ABS_INFORMATION_CATEGORY, ABS_INFORMATION1 … ABS_INFORMATIONn — descriptive flexfield context and segments, including the ABS_INFORMATION9 segment commonly queried for customer-defined absence attributes.
• OBJECT_VERSION_NUMBER, ROWID, WHO columns — concurrency and audit support.

Common Use Cases and Queries

Typical uses include absence registers, sickness monitoring against SSP thresholds, maternity tracking, and extracting flexfield segments for downstream systems. A representative query retrieves current absences for a person with type and category context and surfaces the ninth flexfield segment:

• SELECT absence_attendance_id, person_id, full_name, date_start, date_end, absence_days, absence_hours, name absence_type, category_meaning, abs_information_category, abs_information9 FROM apps.per_absence_attendances_v WHERE person_id = :p_person_id AND date_start >= :p_from AND date_start < :p_to ORDER BY date_start;

Other patterns filter by absence category or type to isolate sickness events, join to PER_ALL_PEOPLE_F in the calling query when additional assignment attributes are required, or restrict by abs_information_category when flexfield context must match a specific setup before reading abs_information9. Because the view joins multiple effective-dated and translated objects, queries should constrain dates and person scope to avoid redundant row expansion from the _F and _VL sources.