Results for “projected_end_date”

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

Overview

HRFV_ABSENCES is a business view template owned by the APPS schema, residing in the PER (Human Resources) product module of Oracle E-Business Suite. It is not an end-user-facing operational object in its own right; rather, it serves as the source template from which the corresponding flexfield (key flexfield) view is generated. This generation process is driven by the Flexfield View Generator architecture, and the presence of the embedded token strings _DF:PER:PER_ABSENCE_ATTENDANCES:ATT and _DF:PER:PER_ABSENCE_ATTENDANCE_TYPES:TYP within the view text confirms that the object is designed to be dynamically rewritten at runtime, substituting descriptive flexfield (DFF) columns in place of the token placeholders. Status is VALID, meaning the compiled view definition resolves successfully against its dependencies in both 12.1.1 and 12.2.2.

Functionally, HRFV_ABSENCES presents a denormalized, human-readable projection of employee absence records, joining attendance events to people, assignments, absence types, reasons, authorization and replacement persons, and organizational context (organization, job, position, grade, location). Because it flattens numerous master-detail relationships into a single row per absence attendance, it is well suited for ad hoc reporting, OBIEE/BI Publisher extracts, and integration interfaces that must expose absence data without replicating the full join logic.

Underlying Base Objects

The documented base objects over which HRFV_ABSENCES is defined include synonym-backed tables such as PER_ABSENCE_ATTENDANCES, PER_ABSENCE_ATTENDANCE_TYPES, PER_ABS_ATTENDANCE_REASONS, PER_ALL_PEOPLE_F, PER_ASSIGNMENTS_F (itself a view), PER_JOBS_TL, PER_GRADES_TL, HR_ALL_ORGANIZATION_UNITS_TL, HR_ALL_POSITIONS_F_TL, and HR_LOCATIONS_ALL_TL. The view relies on the HR_BIS package, specifically the public function HR_BIS.BIS_DECODE_LOOKUP, to translate the raw lookup codes stored on absence records into their displayed meanings. Two additional packages, HR_GENERAL and HR_SECURITY, are referenced because the generated view is typically embedded inside a security predicate (the Business Group / security profile enforcement), which constrains rows according to the querying user's security profile via HR_SECURITY.

The core driving table is PER_ABSENCE_ATTENDANCES (alias ATT), joined to PER_ALL_PEOPLE_F (PPF) on PERSON_ID with the effective-dated BETWEEN predicate; to PER_ABSENCE_ATTENDANCE_TYPES (TYP) on the type identifier; and to PER_ABS_ATTENDANCE_REASONS (REA) with an outer join (+). Authorizing and replacement persons are joined as outer joins to two additional PER_ALL_PEOPLE_F instances (AUT and REP).

Key Columns

• ABSENCE_ATTENDANCE_ID – Primary key of the underlying attendance record; used for drill-down and joins.
• PERSON_NAME / EMPLOYEE_NUMBER – Employee identification, sourced from PER_ALL_PEOPLE_F.
• DATE_START, TIME_START, DATE_END, TIME_END – The absence period boundaries.
• ABSENCE_DAYS, ABSENCE_HOURS – Duration measures, the primary quantitative fields for absence reporting.
• ABSENCE_TYPE – Descriptive name of the attendance type from PER_ABSENCE_ATTENDANCE_TYPES.
• ABSENCE_REASON – Decoded via HR_BIS.BIS_DECODE_LOOKUP('ABSENCE_REASON', ...).
• ABSENCE_CATEGORY – Decoded via HR_BIS.BIS_DECODE_LOOKUP('ABSENCE_CATEGORY', TYP.ABSENCE_CATEGORY), mapping the lookup code to a meaningful label. This is the column most commonly sought when users search for "absence_category."
• AUTHORISING_PERSON_NAME / REPLACEMENT_PERSON_NAME – Workflow-relevant persons.
• ASSIGNMENT_NUMBER, ORGANIZATION_NAME, JOB_NAME, POSITION_NAME, GRADE_NAME, LOCATION_NAME – Assignment and organizational descriptors.
• BUSINESS_GROUP_NAME, BUSINESS_GROUP_ID – Multi-tenant and security context.

Common Use Cases and Queries

HRFV_ABSENCES is frequently used to build absence analytics, feeding dashboards and extracts. A representative query retrieving absence category alongside durations follows:

SELECT person_name, employee_number, absence_type, absence_category, date_start, date_end, absence_days, absence_hours, organization_name, job_name, grade_name FROM apps.hrfv_absences WHERE business_group_id = :p_bg_id ORDER BY person_name, date_start;

Other scenarios include: aggregating total absence days per grade or organization for HR reporting; producing audit listings of absences with authorizing and replacement person names; and integrating absence data into external systems where the flattened join structure of HRFV_ABSENCES saves substantial development effort. Because the view is a generated flexfield template, teams should remember that direct modifications to the view text are not supported — the flexfield view generator regenerates it. Where DFF values are needed, the generated downstream view (with the tokens substituted) should be queried instead of the template.