Results for “hxt_hour_deduction_rules”

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

Overview

HXT_HOUR_DEDUCTION_RULES is a Time and Labor (HXT) configuration table that stores the details of user-defined hour deduction rules. In Oracle EBS 12.1.1 and 12.2.2, hour deduction rules drive the process by which eligible hours are subtracted from a worker's reported, payable, or assigned time — for example, to account for meal breaks, union-mandated rest periods, paid absences, or policy-driven reductions applied during time entry and approval. Each row defines a deduction rule assigned to a deduction policy, together with the effective-dated quantity of hours to deduct and the time period over which that deduction applies.

The table is effective-dated, meaning multiple versions of the same rule can coexist, each bounded by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE. This date-effective pattern allows administrators to amend deduction rules without losing historical configuration, preserving accurate retroactive recalculation and auditability. From a heuristic Data Vault modeling perspective, the mined FK structure classifies this object as satellite-leaning: its grain and effective-dated attributes suggest it behaves as a descriptive satellite attached to the HXT_HOUR_DEDUCT_POLICIES parent, rather than as an independent hub or a transactional link.

Key Information Stored

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

• HDP_ID — Foreign key to HXT_HOUR_DEDUCT_POLICIES; identifies the parent hour deduction policy to which the rule belongs. This is the primary grouping attribute for the rule set.
• FCL_DEDUCTION_TYPE — The user-defined deduction type (for example, a lookup-based classification such as meal, break, or absence) that characterizes the rule.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date-effective range that establishes the rule's validity window and supports historical versioning.
• HOURS — The numeric quantity of hours to be deducted when the rule applies.
• TIME_PERIOD — The unit or reference period (for example, per shift, per day, or per week) against which the HOURS value is interpreted.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns providing audit and concurrency tracking.

The surrogate primary key is implemented by HXT_HOUR_DEDUCTION_RULES_PK, defined over the composite of HDP_ID, FCL_DEDUCTION_TYPE, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. Because this unique index spans the policy, the deduction type, and the full date range, it also serves as the business-key candidate: it enforces that no two overlapping versions of the same deduction type exist within a single policy's validity window.

Common Use Cases and Queries

Typical scenarios include auditing which deduction rules are active for a policy on a given date, reconciling configured deduction hours against payroll or timecard outcomes, and migrating deduction rule setups between environments. A representative query resolves the currently effective rules for a policy:

• SELECT hdp_id, fcl_deduction_type, hours, time_period FROM hxt_hour_deduction_rules WHERE hdp_id = :p_hdp_id AND :p_as_of_date BETWEEN effective_start_date AND effective_end_date;
• Reporting rules by deduction type: group and sum HOURS across policies to quantify total configured deductions per FCL_DEDUCTION_TYPE.
• Change-history analysis: order rows by EFFECTIVE_START_DATE to reconstruct the evolution of a policy's deduction rules.
• Exception checks: identify policies with overlapping or zero-length effective ranges that could yield ambiguous deduction behavior.

Because the table is configuration rather than transactional data, queries are typically low-volume and are frequently embedded in setup validation reports or data-conversion scripts.

Related Objects

The most significant related objects are:

• HXT_HOUR_DEDUCT_POLICIES — The parent table; join on HXT_HOUR_DEDUCTION_RULES.HDP_ID = HXT_HOUR_DEDUCT_POLICIES.HDP_ID. This is the definitive FK relationship documented in the schema.
• HXT_HOUR_DEDUCTION_RULES_PK — The unique index enforcing the composite business key (HDP_ID, FCL_DEDUCTION_TYPE, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE).
• HXT timecard and rule processing entities — Time and Labor retrieval and rule processing modules consume the deduction policy and rule configuration at runtime to compute deductions against reported time.
• FCL deduction type lookups — The FCL_DEDUCTION_TYPE values typically resolve against FastFormula/Common Lookup (FND_LOOKUP_VALUES) definitions that constrain valid deduction categories.

Administrators and developers should treat HXT_HOUR_DEDUCT_POLICIES as the mandatory join path; all rule configuration is meaningless without its governing policy.