Results for “hxt_add_assign_info_x”

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

Overview

The HXT_ADD_ASSIGN_INFO_X view is a public, APPS-owned database object within the Oracle E-Business Suite Time and Labor (HXT) module. It exposes date-effective supplemental assignment information that governs how hours are generated and how earnings, shift differentials, and hour deductions are applied to a worker's assignment. The view serves as the runtime, "effective-dated" presentation layer over the underlying table, returning only the rows that are currently in force as of the current system date.

In the context of the search term earning_policy, this view is significant because it surfaces the EARNING_POLICY attribute alongside related policy columns such as SHIFT_DIFFERENTIAL_POLICY and HOUR_DEDUCTION_POLICY. Together these attributes drive how Time and Labor translates recorded time and generated hours into payable earnings. Report writers, integrations, and fast formulas frequently query this view to resolve the currently effective earning policy for a given assignment without needing to manage effective-date logic themselves.

Because the view is a thin filter over the base table rather than an aggregation or join-heavy object, it is inexpensive to query and is well suited to concurrent program data sources, Oracle Reports, BI Publisher datasets, and outbound integration extracts. Its status is VALID in the documented environment, confirming it is a supported, compiled object in the APPS schema.

Underlying Base Objects

Per the documented metadata, the view references a single base object: HXT_ADD_ASSIGN_INFO_F, referenced through a synonym. The suffix _F denotes a date-tracked ("F" for the date-effective) entity whose rows carry EFFECTIVE_START_DATE and EFFECTIVE_END_DATE bookends. The _X suffix on the view is the conventional Oracle naming pattern for a date-tracked entity's runtime view, distinguishing it from an _ALL view that would return every historical row.

The view definition is a straightforward projection with an effective-date predicate:

• SELECT clause: enumerates the identifier, effective dates, assignment reference, policy attributes, audit columns, and thirty descriptive flexfield (DFF) attribute columns.
• FROM clause: selects from HXT_ADD_ASSIGN_INFO_F.
• WHERE clause: EFFECTIVE_START_DATE <= TRUNC(SYSDATE) AND EFFECTIVE_END_DATE >= TRUNC(SYSDATE), restricting output to the rows effective today.

This means the view and the base table share an identical column list; the view adds no derived columns. Any Data Definition Language change, column addition, or DFF context change occurs on the base table and propagates automatically to the view.

Key Columns

The columns most relevant to reporting and integration include:

• ID — Primary identifier for the supplemental assignment information row.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — Effective-dating bookends that define the validity window.
• ASSIGNMENT_ID — Foreign key to the assignment (typically PER_ASSIGNMENTS_F) to which the policies apply.
• AUTOGEN_HOURS_YN — Flag indicating whether hours are automatically generated for the assignment.
• ROTATION_PLAN — Reference to the rotation plan governing shift scheduling.
• EARNING_POLICY — The earning policy applied to generated time, central to pay computation.
• SHIFT_DIFFERENTIAL_POLICY — The policy that governs shift differential pay treatment.
• HOUR_DEDUCTION_POLICY — The policy controlling deduction of hours (for example, for breaks or meal periods).
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — Descriptive flexfield columns available for client-specific extensions.

Common Use Cases and Queries

The view is most commonly used to resolve the currently effective earning policy for an assignment, to validate supplemental assignment configuration, and to feed pay-related integrations.

Retrieve the effective earning policy for a specific assignment:

SELECT a.ASSIGNMENT_ID,
       a.EARNING_POLICY,
       a.SHIFT_DIFFERENTIAL_POLICY,
       a.HOUR_DEDUCTION_POLICY
FROM   APPS.HXT_ADD_ASSIGN_INFO_X a
WHERE  a.ASSIGNMENT_ID = :p_assignment_id;

List all assignments currently configured with automatic hour generation:

SELECT a.ASSIGNMENT_ID,
       a.AUTOGEN_HOURS_YN,
       a.ROTATION_PLAN,
       a.EARNING_POLICY
FROM   APPS.HXT_ADD_ASSIGN_INFO_X a
WHERE  a.AUTOGEN_HOURS_YN = 'Y';

Extract a dated snapshot for integration into a payroll or time collection system:

SELECT a.ASSIGNMENT_ID,
       a.EFFECTIVE_START_DATE,
       a.EFFECTIVE_END_DATE,
       a.EARNING_POLICY,
       a.ATTRIBUTE1
FROM   APPS.HXT_ADD_ASSIGN_INFO_X a
WHERE  a.EFFECTIVE_START_DATE BETWEEN :p_from_date AND :p_to_date;

Because the view already filters to today's effective rows, queries that require historical or future-dated policy data must target the base table HXT_ADD_ASSIGN_INFO_F directly and apply their own date predicates. For current-state reporting, however, the view remains the preferred and simplest access path.