Search Results hxt_add_assign_info_f




Overview
Explore in AI Chat

Overview

HXT_ADD_ASSIGN_INFO_F is a Time and Labor (HXT) table that stores the details of time information associated with a person's assignments. Each row captures the assignment-level configuration that governs how time is collected, generated, and processed for an employee, contingent worker, or applicant assignment within Oracle EBS 12.1.1 and 12.2.2. The table is date-tracked through effective start and end dates, allowing the assignment's time rules to change over time while retaining historical records.

In Data Vault modeling terms, the mined foreign-key structure suggests this object behaves as a link table — it connects an assignment to the set of Time and Labor policies that apply to it (earning policy, shift differential policy, hour deduction policy, and rotation plan). This classification is a modeling heuristic rather than a declarative statement in the ETRM metadata, but it aligns with the table's role as an associative record between assignments and policy definitions.

Key Information Stored

The table contains 45 documented columns. The most significant are:

The surrogate primary key HXT_AAIF_HRW_PK (ID, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE) is also the documented unique index and represents the business-key candidate for this entity.

Common Use Cases and Queries

Typical scenarios include auditing which policies apply to an assignment on a given date, verifying that all assignments have a valid rotation or earning policy configured, and reporting on assignments with automatic hour generation enabled.

A query returning the current effective policy configuration for a specific assignment:

  • SELECT assignment_id, earning_policy, shift_differential_policy, hour_deduction_policy, rotation_plan FROM hxt_add_assign_info_f WHERE assignment_id = :p_assignment_id AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;

An audit query listing assignments with autogenerated hours:

  • SELECT assignment_id, effective_start_date, effective_end_date FROM hxt_add_assign_info_f WHERE autogen_hours_yn = 'Y' AND effective_end_date = TO_DATE('4712-12-31','YYYY-MM-DD');

Reporting use cases include policy utilization summaries, date-tracked change history for an assignment, and validation extracts ensuring no assignment lacks a required earning or hour deduction policy.

Related Objects

The following tables are referenced through foreign keys and are the most significant related objects:

  • HXT_EARNING_POLICIES — joined on HXT_ADD_ASSIGN_INFO_F.EARNING_POLICY.
  • HXT_HOUR_DEDUCT_POLICIES — joined on HXT_ADD_ASSIGN_INFO_F.HOUR_DEDUCTION_POLICY.
  • HXT_ROTATION_PLANS — joined on HXT_ADD_ASSIGN_INFO_F.ROTATION_PLAN.
  • HXT_SHIFT_DIFF_POLICIES — joined on HXT_ADD_ASSIGN_INFO_F.SHIFT_DIFFERENTIAL_POLICY.

Because ASSIGNMENT_ID is not documented as a formal foreign key in the ETRM metadata, assignment details are typically retrieved by joining to the HR assignment tables through ASSIGNMENT_ID where integration requirements demand it. Time and Labor retrieval and processing processes consume this table's configuration when generating and validating timecard data.