Search Results date_ec

Overview

PAY_MX_EXPIRY_SUPPORT is a Mexico-specific payroll support package in Oracle E-Business Suite, shipped under the APPS schema and classified as an "OTHER" API within ETRM. Its business function is to supply country-specific balance expiry checking logic for payroll balances whose dimensions include a date component. In Oracle Payroll, balance expiry determines whether a balance accumulated in a prior payroll run remains valid for use in a subsequent run, and expiry rules vary by legislation. Oracle delivers generic expiry checking through the PAY_IP_EXPIRY_SUPPORT package; PAY_MX_EXPIRY_SUPPORT complements that generic infrastructure by implementing the Mexican statutory rules that apply specifically to date-related dimensions.

The package header comment identifies its scope precisely: it handles expiry checking for date-related dimensions involving Person, GRE (Government Reporting Entity), and Bi-Month. For all other dimensions, the expiry evaluation is delegated to functions delivered in PAY_IP_EXPIRY_SUPPORT. The package therefore acts as a legislative overlay rather than a full replacement for the generic expiry framework.

Key Procedures and Functions

The package exposes a single procedure name, DATE_EC, implemented as two overloaded declarations. Only the name and purpose are documented; parameter lists are not reproduced here.

• DATE_EC (first overload) — Performs the Mexico-specific expiry check across date-related dimensions and returns the expiry outcome as a numeric dimension expired flag. Its implementation notes state that it assumes the date portion of the dimension name is always positioned at the end of the name, since this suffix convention is used to identify many dimensions accurately.
• DATE_EC (second overload) — The overloaded form that returns the expiry result as a date value rather than a numeric flag. The header comment describes it as the variant that accommodates the requirements of the Balance Adjustment process, allowing the adjustment logic to reason about the exact expiry date of a dimension.

Both overloads accept the owner and user payroll action and assignment action identifiers together with their effective dates, plus the balance dimension name, enabling the procedure to compare the context in which a balance was created against the context of the current run and decide whether the balance has expired.

Tables Accessed

ETRM documents a single referenced table, accessed through an APPS synonym: PAY_PAYROLL_ACTIONS. This table stores payroll action records, including the run and assignment action identifiers and their effective dates that are passed into DATE_EC. The package reads this table to resolve the effective dates and action context needed to evaluate expiry for the owner balance versus the current run.

Usage Notes

PAY_MX_EXPIRY_SUPPORT is not intended for direct invocation by end users. It is invoked indirectly by the Oracle Payroll balance processing engine when expiry rules for Mexican date-related dimensions must be evaluated during payroll run processing and the balance adjustment process. Because it is an internal payroll support routine, it is most commonly triggered by concurrent payroll processes rather than from an application form. Custom code should avoid calling it directly in preference to supported payroll APIs; organizations that extend or troubleshoot Mexican balance expiry behavior should treat the package as a reference implementation of the localisation's expiry rules and verify behavior against the corresponding PAY_IP_EXPIRY_SUPPORT generic functions. No other packages are documented as referencing this package.