Results for “per_absence_attendances_v2”

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

Overview

PER_ABSENCE_ATTENDANCES_V2 is a reporting view owned by the APPS schema within the PER (Human Resources) product of Oracle E-Business Suite. In both 12.1.1 and 12.2.2, the object is shipped in VALID status and is documented in ETRM as providing a "list of employees by absence type." Rather than storing data, the view flattens the relationship between an employee's absence records and the absence types they are associated with, exposing the person's name and employee number alongside each absence entry. This makes it a convenient read-layer for reports, concurrent programs, and integrations that need employee-level absence detail without re-implementing the multi-table joins across the absence, absence type, and person entities.

The view is especially relevant to the user search term "employee_name," since EMPLOYEE_NAME is the first projected column and is drawn directly from the person's full name via the PER_PEOPLE_F designation. Report authors searching for an absence view that already surfaces the employee name can join or query this object directly instead of resolving the person name separately.

Underlying Base Objects

The documented view text defines PER_ABSENCE_ATTENDANCES_V2 over three primary sources joined on their key identifiers:

• PER_ABSENCE_ATTENDANCES AA — the transactional absence/attendance records. Joined to the type and person via ABSENCE_ATTENDANCE_TYPE_ID and PERSON_ID respectively.
• PER_ABSENCE_ATTENDANCE_TYPES AAT — supplies ABSENCE_TYPE (AAT.NAME) and ABSENCE_CATEGORY. In ETRM documentation this is realized through PER_ABS_ATTENDANCE_TYPES_VL.
• PER_PEOPLE_F PEO — the effective-dated person record providing EMPLOYEE_NAME (FULL_NAME) and EMPLOYEE_NUMBER.

The ETRM "referenced base objects" list for 12.2.2 also records HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages, plus SYNONYM and VIEW wrappers (PER_PEOPLE_F as a view and PER_ABSENCE_ATTENDANCES / PER_ALL_PEOPLE_F as synonyms). This reflects the effective-dating and security logic layered onto the underlying tables: HR_SECURITY governs row-level access to person data, while HR_PERSON_NAME and HR_GENERAL support name derivation and business-group handling. The date-join predicate in the view aligns the absence start date to the person's effective date range, with a MAX(EFFECTIVE_START_DATE) fallback when no start date exists.

Key Columns

The columns exposed by the view fall into identity, type, and audit groupings:

• EMPLOYEE_NAME — the person's full name; the column most commonly searched for in absence reporting.
• EMPLOYEE_NUMBER — the system-assigned employee number for the person.
• ABSENCE_TYPE and ABSENCE_CATEGORY — the descriptive name and category of the absence type (e.g., sickness, vacation).
• DATE_START and DATE_END — the absence period boundaries.
• ABSENCE_ATTENDANCE_ID, PERSON_ID, ABSENCE_ATTENDANCE_TYPE_ID, BUSINESS_GROUP_ID — surrogate and foreign keys enabling joins to other PER objects.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns inherited from the base table.

Common Use Cases and Queries

Typical uses include absence registers sorted by employee name, absence-by-type summaries, and integrations exporting absence detail to external systems. A representative query filters by absence category and orders by name:

• SELECT employee_name, employee_number, absence_type, date_start, date_end FROM apps.per_absence_attendances_v2 WHERE absence_category = 'SICKNESS' ORDER BY employee_name;
• SELECT employee_name, absence_type, COUNT(*) FROM apps.per_absence_attendances_v2 GROUP BY employee_name, absence_type;

Because HR_SECURITY is referenced, results remain subject to the querying user's security profile, so the view is suitable for secured self-service and reporting use in 12.1.1 and 12.2.2 alike.