Search Results per_absence_attendances_efc_pk




Overview

The HR.PER_ABSENCE_ATTENDANCES_EFC table is a specialized audit and historical data table within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Human Resources (HR) module. Its primary role is to support the Euro Functional Currency (EFC) conversion process. This table stores a historical snapshot of specific National Currency Unit (NCU) and currency code values from the base absence attendance records prior to their conversion during an EFC event. It is a critical component for maintaining financial and regulatory compliance, as it preserves the original currency data for audit trails and historical reporting after the system's primary transactional currency has been converted to the Euro. As documented, this table is exclusively maintained by the automated EFC process and is not intended for manual data entry or direct transactional use.

Key Information Stored

The table contains a subset of columns from its base table, focusing on the currency-related flexfield segments. The structure is defined by two key identifiers and several descriptive flexfield (DFF) columns. The mandatory ABSENCE_ATTENDANCE_ID links the record back to the original absence entry in the base table. The EFC_ACTION_ID is a foreign key to HR_EFC_ACTIONS, identifying the specific EFC conversion event that created this snapshot record. The primary data preserved are the original NCU values stored in the DFF columns: ABS_INFORMATION7, ABS_INFORMATION8, ABS_INFORMATION9, ABS_INFORMATION11, ABS_INFORMATION13, and ABS_INFORMATION15. The exact business meaning of these columns is determined by the site-specific flexfield configuration for absences.

Common Use Cases and Queries

The principal use case is auditing and reconciling absence-related financial data post-Euro conversion. Reports may need to compare converted Euro values in the main transaction tables against the original NCU values stored here. A typical query involves joining this table to the main absence table and the EFC actions table to provide context. The standard query pattern, as indicated by the ETRM, is:

  • SELECT ABSENCE_ATTENDANCE_ID, EFC_ACTION_ID, ABS_INFORMATION7, ABS_INFORMATION8, ABS_INFORMATION9, ABS_INFORMATION11, ABS_INFORMATION13, ABS_INFORMATION15 FROM HR.PER_ABSENCE_ATTENDANCES_EFC;

For a more functional report, a developer would extend this to join with HR.PER_ABSENCE_ATTENDANCES on ABSENCE_ATTENDANCE_ID and with HR.HR_EFC_ACTIONS on EFC_ACTION_ID to include details like the conversion date and original transaction data.

Related Objects

The table has defined relationships with other core EBS objects, primarily through its primary and foreign keys. The PER_ABSENCE_ATTENDANCES_EFC_PK primary key uniquely identifies each historical snapshot by the composite of ABSENCE_ATTENDANCE_ID and EFC_ACTION_ID. The table has one documented foreign key dependency:

  • TABLE: HR.HR_EFC_ACTIONS: The EFC_ACTION_ID column in PER_ABSENCE_ATTENDANCES_EFC references the HR_EFC_ACTIONS table. This links each snapshot to the master record of the EFC conversion process that generated it.

While the ETRM notes no objects reference this table, it is intrinsically related to the base transaction table HR.PER_ABSENCE_ATTENDANCES via the ABSENCE_ATTENDANCE_ID column, which is the foundational relationship for any audit query.