Results for “per_abs_attendance_types_v”

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

Overview

The PER_ABS_ATTENDANCE_TYPES_V view is a seeded, APPS-owned database object within the Oracle E-Business Suite PER – Human Resources product. It exposes user-defined absence types as configured in the Absence Management functionality, presenting them in a denormalized, reporting-friendly form. Where the underlying transactional table stores numeric identifiers and lookup codes, this view resolves those values into human-readable descriptions: translated absence type names, lookup meanings for category and directionality, and the associated payroll element details. This makes the view the canonical reference point for consumers who need absences classified by type without repeatedly coding joins to the translation, lookup, and payroll element tables themselves. Because the view is a read-only projection, it is suitable for reporting, extracts, integrations, and validation queries, but must never be used as a target for DML. In Oracle EBS 12.1.1 and 12.2.2 the view remains valid and is widely referenced by seed data queries, fast formulas support logic, and custom concurrent programs that reconcile absence entries against payroll inputs.

Underlying Base Objects

The view is defined over several APPS objects. The two principal base objects are PER_ABSENCE_ATTENDANCE_TYPES (the absence type definition table, aliased ABT) and PER_ABS_ATTENDANCE_TYPES_TL (its translation table, aliased ABTL), joined on the absence attendance type identifier. Supporting joins bring in payroll context: PAY_INPUT_VALUES_F and PAY_INPUT_VALUES_F_TL supply the input value and its translated name, while PAY_ELEMENT_TYPES_F and PAY_ELEMENT_TYPES_F_TL supply the element type name to which the absence input belongs. Three aliases of HR_LOOKUPS (LKP1, LKP2, LKP3) decode the lookup meanings for absence category and related classifications. All payroll joins are outer joins, so absence types not yet linked to a payroll element are still returned. The ETRM metadata also lists HR_API as a referenced base object, reflecting the HR security/utility package dependency carried by the object.

Key Columns

• ABSENCE_ATTENDANCE_TYPE_ID – Primary identifier of the absence type.
• BUSINESS_GROUP_ID – Owning business group, essential for multi-organization filtering and Row-Level Security.
• NAME – Translated user-defined absence type name from the TL table.
• HOURS_OR_DAYS – Indicates whether the absence type is measured in hours or days; this is the column referenced by the search term hours_or_days and is central to accrual and deduction calculations.
• ABSENCE_CATEGORY – Classification of the absence (for example, sickness or vacation), with a decoded MEANING supplied from HR_LOOKUPS.
• INCREASING_OR_DECREASING_FLAG – Directionality of the type, i.e. whether it accrues or depletes balances.
• INPUT_VALUE_ID, ELEMENT_TYPE_ID, ELEMENT_NAME, IPVTL.NAME, UOM – Payroll linkage identifying the input value, its unit of measure, and the parent element type.
• DATE_EFFECTIVE / DATE_END – Effective-dating range for the definition.
• ATTRIBUTE1–20 and INFORMATION1–20 – Descriptive flexfield and extra information segments available for client-specific extensions.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, CREATED_BY and related audit columns – Standard EBS concurrency and audit attributes.

Common Use Cases and Queries

Typical uses include reporting on configured absence types, driving eligibility logic, and validating that each type maps to the correct payroll element and unit of measure. A frequent requirement is the hours_or_days check before computing an entitlement.

SELECT absence_attendance_type_id,
       name,
       absence_category,
       hours_or_days,
       increasing_or_decreasing_flag,
       element_name,
       uom
FROM   apps.per_abs_attendance_types_v
WHERE  business_group_id = :p_business_group_id
AND    TRUNC(SYSDATE) BETWEEN NVL(date_effective, TRUNC(SYSDATE))
                         AND NVL(date_end, TRUNC(SYSDATE))
ORDER  BY name;

Integration and reconciliation queries join this view to absence entries to confirm the unit of measure applied to each recorded absence. Because the view already surfaces lookup meanings, it is preferred over direct table joins when building ad hoc reports or OBIEE/BI Publisher datasets, and it should be queried with a business group predicate to remain consistent with HR security policies.