Search Results pay_mx_expiry_support

Overview

PAY_MX_EXPIRY_SUPPORT is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema, classified under the ETRM (E-Business Suite Technical Reference Manual) as an "OTHER" API type. It is a Mexican localization utility within the Oracle Payroll (PAY) module. Its purpose is to support expiry-related processing for Mexican payroll statutory requirements, notably the handling of date-driven expirations such as those tied to the Registro Federal de Contribuyentes (RFC) and other fiscal identifiers or obligations that the Mexican tax authority (SAT) requires employers to validate and expire on a defined schedule.

The package operates as a thin technical support layer, delegating common date manipulation to the HR_UTILITY shared package and grouping its own logic under a single clearly-named date function. It is not a general-purpose payroll API and is not referenced by any other database object, indicating it is invoked internally or by a narrow set of localization call sites rather than exposed as a reusable public interface.

Key Procedures and Functions

The documented metadata lists two program units. The function DATE_EC is the core date utility provided by this package. Based on its naming convention and the Mexican (MX) localization context, it supplies expiry-oriented date evaluation — most plausibly comparing or normalizing a date relative to the current payroll period or the effective date of payroll action processing, so that callers can determine whether a given fiscal attribute has lapsed. No parameter list is documented in the ETRM metadata, and none is asserted here.

The second unit is the package body itself, whose status is VALID and whose dependency list confirms it references HR_UTILITY, a foundation package that provides shared date arithmetic, period start/end derivation, and calendar conversions. The body therefore depends on HR_UTILITY routines rather than reimplementing date logic, which is consistent with Oracle's localization design practice. Precise signatures must be obtained from the live source via PAY_MX_EXPIRY_SUPPORT in the database rather than inferred from the ETRM excerpt.

Tables Accessed

The only documented table referenced through APPS synonyms is PAY_PAYROLL_ACTIONS, the payroll run action table. Each row in this table represents a payroll process action (such as a payroll run, reversal, or costing action) together with its action status and effective dates. PAY_MX_EXPIRY_SUPPORT reads this table to align expiry evaluation with the state of the current payroll action — for example, to determine whether the action in scope is live, pending, or complete before performing date comparisons. The dependency listing shows a read-oriented relationship; no insert, update, or delete against PAY_PAYROLL_ACTIONS is documented, which is appropriate for a support/validation package. The package does not reference any AP or HR localization tables directly, reinforcing its narrow scope.

Usage Notes

PAY_MX_EXPIRY_SUPPORT is an internal localization support package rather than a public API. The ETRM explicitly states that it "is not referenced by any database object," meaning no other package, view, trigger, or form binds to it at the schema level. Consequently, it is typically invoked from within the Mexican payroll localization code path — for example, during payroll run date validation or during expiry checks triggered as part of a payroll action lifecycle — rather than from a concurrent program executable or a standard Oracle Forms event. Because it touches PAY_PAYROLL_ACTIONS, any custom code calling DATE_EC should do so within the context of an active payroll action to ensure meaningful results. Implementers performing upgrades from 12.1.1 to 12.2.2 should confirm the package remains VALID and unchanged, and should treat it as Oracle-owned: customization is unsupported, and behaviour should be verified against the online payroll action state rather than modified in place.