Search Results hxt_per_aei_ddf_v




Overview
Explore in AI Chat

Overview

The view APPS.HXT_PER_AEI_DDF_V is a reporting and integration object within the Oracle E-Business Suite Time and Labor (HXT) product family. It is registered in the APPS schema with a status of VALID and is classified as a VIEW. Its role is to expose a curated, denormalized projection of assignment-level automatic information used by Oracle Time and Labor to drive timecard generation, policy assignment, and rule evaluation.

The view derives its data from the Automatic Assignment Information entity, which stores the default attributes applied to an assignment when time is processed. By surfacing these attributes through a stable view name, HXT_PER_AEI_DDF_V provides a predictable interface for concurrent programs, FastFormula references, BI Publisher data definitions, and external integrations that query assignment defaults without directly joining the underlying transactional table. The naming convention ("PER_AEI_DDF") reflects a Personnel-oriented Automatic Employee Information Data Definition Framework projection, consistent with Oracle's practice of exposing validated read-only views for downstream consumption.

Underlying Base Objects

Per the documented ETRM metadata, HXT_PER_AEI_DDF_V is defined exclusively over the base object HXT_ADD_ASSIGN_INFO_F, which is referenced through a synonym. The underlying table is a date-tracked ("_F" suffix) entity, meaning it maintains effective start and end dates to support temporal, versioned record keeping.

The view text is a straightforward projection:

  • HXT_ADD_ASSIGN_INFO_F is the single source table.
  • No joins, unions, or aggregations are applied — the view is a column-level narrowing of the base table.
  • All rows and their effective-date ranges are passed through unchanged, so referential and temporal integrity inherited from the base table is preserved.

Key Columns

The view exposes the following columns, each mapping to an automatic assignment attribute:

Note that the view text aliases some columns using the base table's original names (for example, AUTOGEN_HOURS_YN), while the documented column list presents the HXT_-prefixed variants. Consumers should reference the documented column names when building queries.

Common Use Cases and Queries

Typical scenarios include auditing which assignments auto-generate hours, verifying policy assignments for a population of employees, and feeding timecard defaults into downstream processes.

Retrieve current automatic assignment information for a specific assignment:

  • SELECT assignment_id, hxt_autogen_hours_yn, hxt_rotation_plan, hxt_earning_policy, hxt_shift_differential_policy, hxt_hour_deduction_policy FROM apps.hxt_per_aei_ddf_v WHERE assignment_id = :p_assignment_id AND SYSDATE BETWEEN effective_start_date AND effective_end_date;

List all assignments configured for automatic hour generation:

  • SELECT assignment_id, effective_start_date, effective_end_date FROM apps.hxt_per_aei_ddf_v WHERE hxt_autogen_hours_yn = 'Y' ORDER BY assignment_id, effective_start_date;

Because the view inherits the date-tracked nature of HXT_ADD_ASSIGN_INFO_F, queries should generally constrain on EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to return only the currently effective row per assignment and avoid duplicate historical results.