Search Results hxt_shift_differential_policy

Overview

APPS.HXT_PER_AEI_DDF_V is a validity-tracked database view owned by the APPS schema within the Oracle E-Business Suite HRMS/Time and Labor (ETRM) module. Its name reflects its function: it exposes "Additional Employee Information" (AEI) carrying a "DateTracked Definition File" (DDF) structure keyed by assignment. In Oracle EBS 12.1.1 and 12.2.2, the object is registered as an FND Design Data entity (HXT.HXT_PER_AEI_DDF_V) and carries a status of VALID. The view is flagged as Internal/View Type Internal, and Oracle explicitly restricts access to it outside standard Oracle Applications programs, meaning supported usage flows through seeded ETRM concurrent programs and forms rather than ad-hoc reporting.

Its practical role is to present, per assignment, the set of policy pointers that govern how time is generated, earned, and deducted. These include the rotation plan, earning policy, shift differential policy, and hour deduction policy, together with DateTrack effective dating. The view therefore serves as the assignment-level configuration lookup that downstream time processing logic reads when building timecards and daily hours records.

Underlying Base Objects

The documented metadata establishes that APPS.HXT_PER_AEI_DDF_V is defined over a single referenced base object: the synonym HXT_ADD_ASSIGN_INFO_F (the "Additional Assignment Information" function). This function supplies the AEI policy columns and the DateTracked effective date range that the view projects to callers. Because the view inherits the DateTrack semantics of its base function, callers can resolve the policy configuration that was in force on a given date by filtering on EFFECTIVE_START_DATE and EFFECTIVE_END_DATE rather than relying on a single current-row assumption.

The view is not a leaf object. Within the APPS schema it is referenced by several dependent objects, including HXT_DAILY_HOURS_WORKED_V, HXT_EMP_ASGN_INFO_V, HXT_TIM_SUMMARY_FMV, and the program units HXT_TIMECARD_INFO, HXT_TIME_CLOCK, HXT_TIME_COLLECTION, HXT_TIME_DETAIL, HXT_TIME_GEN, HXT_TIME_SUMMARY, HXT_TIM_COL_UTIL, and HXT_UTIL. This dependency chain confirms that the view is a foundational configuration source consumed by the broader time collection, generation, and summarization framework.

Key Columns

• ASSIGNMENT_ID (NUMBER, 10) — The assignment this policy set applies to; the primary join key to PER_ALL_ASSIGNMENTS_F.
• HXT_AUTOGEN_HOURS_YN (VARCHAR2) — Flag controlling whether hours are automatically generated for the assignment.
• HXT_ROTATION_PLAN (NUMBER, 15) — Identifier of the rotation plan governing shift patterns.
• HXT_EARNING_POLICY (NUMBER, 15) — Earning policy applied when time is earned and accrual is calculated.
• HXT_SHIFT_DIFFERENTIAL_POLICY (NUMBER, 15) — Policy that determines shift differential treatment.
• HXT_HOUR_DEDUCTION_POLICY (NUMBER, 15) — The hour deduction policy linked to the assignment, driving which deductions apply to recorded or generated hours.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE (DATE) — DateTrack effective range defining when this policy combination is valid.

Common Use Cases and Queries

The view is principally used to resolve the deduction, earning, and shift policies in effect for an assignment on a given date. A representative query retrieves the current policy set for an assignment:

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

Analysts investigating unexpected hour deductions typically link this view to HXT_DAILY_HOURS_WORKED_V or HXT_TIME_SUMMARY to confirm which HXT_HOUR_DEDUCTION_POLICY was active when the deduction was generated. Because the object is designated Oracle Internal Use Only, direct SQL should be confined to diagnostic and support contexts; production logic should invoke the view through the seeded ETRM programs that already depend on it.