Results for “absence_points”

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

Overview

HXT_ADD_ELEM_INFO_F is a date-tracked (datetrack) table owned by the HXT schema within the Oracle Time and Labor (OTL) module of Oracle E-Business Suite. Its documented purpose is to hold details of time information associated with elements — that is, the intersection between Oracle Payroll elements and the time-related attributes that drive how those elements behave during time collection, calculation, and payroll transfer. In EBS 12.1.1 and 12.2.2 this table surfaces as the storage vehicle behind the "Additional Element Information" setup for elements that participate in time entry flows, allowing an element to carry earning categorizations, absence classification, premium treatment, and expenditure mapping.

The heuristic Data Vault classification mined from the foreign-key structure is standalone. In data-vault modeling terms, this suggests treating the object as a self-contained entity without strict parent/child link semantics — a practical modeling suggestion rather than a normative rule. Because it lacks dependent child tables in the documented relationship data, it can be modeled as an independent entity keyed on its own business-key surrogate, rather than as a hub joined through dedicated link tables.

Key Information Stored

The table is uniquely identified by the HXT_AEIF_HRW_PK component combination (ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE), which also serves as the business-key candidate. The ID column is the surrogate identifier; the two effective-date columns implement row-level date tracking so historical and future-dated element setup can coexist.

The most significant business columns include ELEMENT_TYPE_ID, which links each row to the payroll element being configured; EARNING_CATEGORY, which classifies the earning bucket used for reporting and costing; ABSENCE_TYPE and ABSENCE_POINTS, which describe absence accounting behavior; PREMIUM_TYPE and PREMIUM_AMOUNT, defining premium pay treatment; and PROCESSING_ORDER, which controls sequencing during element processing. EXPENDITURE_TYPE carries project/expenditure mapping where time is costed to projects. POINTS_ASSIGNED and EXCLUDE_FROM_EXPLOSION govern accrual point allocation and whether the element is excluded from time explosion logic during the OTL-to-BEE transfer.

Common Use Cases and Queries

Typical uses center on auditing element setup, generating element configuration reports, and troubleshooting date-tracked changes. A representative query resolving the current effective row for a given element is:

• SELECT id, element_type_id, earning_category, premium_type, processing_order FROM hxt.hxt_add_elem_info_f WHERE element_type_id = :p_element AND sysdate BETWEEN effective_start_date AND effective_end_date;
• Date-track range reporting: filter on effective_start_date >= :from AND effective_end_date <= :to to reconstruct historical configuration.
• Premium/absence audits: WHERE premium_type IS NOT NULL OR absence_type IS NOT NULL to review non-standard element behavior.
• Explosion diagnostics: WHERE exclude_from_explosion = 'Y' to isolate elements excluded from time explosion, useful when reconciling OTL transfer results.

Related Objects

The strongest documented relationship is to ELEMENT_TYPE_ID, which references the payroll element definition (PAY_ELEMENT_TYPES_F). From an OTL integration standpoint, this table is consumed by the time-explosion and calculation engine and links conceptually to foundational OTL objects.

• PAY_ELEMENT_TYPES_F — joined via ELEMENT_TYPE_ID = ELEMENT_TYPE_ID.
• HXT_AEIF_HRW_PK — the primary/unique index enforcing the business key.
• Time and Labor retrieval/calculation APIs (HXC/BEE) that read additional element information during preprocessing.
• PAY_ELEMENT_CLASSIFICATIONS — for validating earning category and element classification context.
• OTL time collection and transfer reports that join back to ELEMENT_TYPE_ID for element-level time reporting.