Results for “high_range_factor”

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

Overview

PAY_MX_EARN_EXEMPTION_RULES_F is a Payroll (PAY) module table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the earnings exemption rules used for Mexican payroll statutory processing, defining the thresholds, ranges, and factors that determine how much of a given earnings element is exempt from taxation at the state level. The table is date-effectivity enabled, so each rule is versioned by effective start and end dates rather than overwritten in place. This allows payroll runs to resolve the correct rule that was in force on any given pay or tax date.

The metadata classifies this object heuristically as satellite-leaning. In Data Vault modeling terms this is a reasonable suggestion: the table is not a hub of independent business entities, and it is not a pure link between two hubs. Rather, it functions as a descriptive satellite attached to an earnings classification, carrying the changing exemption attributes that apply to it over time. The effective-dated business key and the mutable factor columns reinforce this characterization.

Key Information Stored

Each row captures one effectivity-dated exemption rule for a specific earnings classification and state. The columns of greatest significance are:

• EXEMPTION_RULE_ID — the surrogate identifier and part of the primary key, uniquely naming each rule instance.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-effectivity bounds that define when the rule is valid; both participate in the primary key and the unique key.
• ELEMENT_CLASSIFICATION_ID — foreign key to PAY_ELEMENT_CLASSIFICATIONS, tying the rule to the earnings element classification it governs.
• STATE_CODE — identifies the Mexican state whose exemption treatment applies, part of the unique business key.
• TAX_TYPE — distinguishes the tax regime the exemption applies under.
• CALC_RULE — the calculation rule driving how the exemption is computed.
• LOW_EXEMPT_FACTOR, LOW_RANGE_FACTOR, LOW_RANGE_BASIS — the lower-tier exemption factor, range factor, and range basis values.
• HIGH_RANGE_FACTOR, HIGH_EXEMPT_FACTOR, HIGH_RANGE_BASIS — the corresponding upper-tier factors and basis.
• DESCRIPTION — free-text description of the rule.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE — standard audit columns.

The primary key PAY_MX_EARN_EXEMPTION_RULES_PK is defined on EXEMPTION_RULE_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE (with ZD_EDITION_NAME in the 12.2.2 physical schema). The unique business key PAY_MX_EARN_EXEMPTION_RULES_UK is defined on ELEMENT_CLASSIFICATION_ID, STATE_CODE, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE, preventing duplicate overlapping rules for the same classification and state.

Common Use Cases and Queries

The table is consumed during Mexican payroll tax calculation, where the payroll engine resolves the applicable rule for a classification and state as of the pay period date. Typical reporting includes exemption rule configuration extracts and effectivity audits.

A point-in-time rule lookup joins on the classification and state while constraining effectivity dates:

• SELECT exemption_rule_id, tax_type, low_exempt_factor, high_exempt_factor FROM pay_mx_earn_exemption_rules_f WHERE element_classification_id = :p_classification_id AND state_code = :p_state AND :p_effective_date BETWEEN effective_start_date AND effective_end_date;

A configuration report lists all active rules with their classification and state context:

• SELECT e.element_classification_id, e.state_code, e.tax_type, e.calc_rule, e.description FROM pay_mx_earn_exemption_rules_f e WHERE TRUNC(SYSDATE) BETWEEN e.effective_start_date AND e.effective_end_date ORDER BY e.state_code, e.element_classification_id;

Effectivity auditing identifies any overlapping or gapped records for a classification and state.

Related Objects

The most significant relationship is the foreign key from ELEMENT_CLASSIFICATION_ID to PAY_ELEMENT_CLASSIFICATIONS, which anchors each rule to the earnings classification it governs and is the primary join in most queries. The unique key columns ELEMENT_CLASSIFICATION_ID and STATE_CODE also imply logical reference to state-level payroll configuration used in Mexican localization processing. Surrounding date-effectivity and localization logic is generally implemented through the Mexican payroll statutory rule set and the payroll engine that reads these records at runtime, alongside the standard audit columns supplied by the EBS WHO columns mechanism. Additional related objects include the element classification hierarchy, the payroll element definitions that ultimately use these classifications, and the localization rule tables that share the state and tax-type dimensions.