Search Results adv_payment_skip_rule

Overview

PAY_NO_ADVANCE_PAY is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, declared with AUTHID CURRENT_USER so that its SQL executes under the privileges of the calling user rather than the package owner. It belongs to the Oracle Payroll (PAY) product family and is classified in the ETRM repository as an OTHER API, meaning it is a supporting utility rather than a full public business API with a published interface contract.

The package encapsulates the business rule that determines whether an advance payment line should be skipped during a payroll run. In payroll processing, advances and prepayments may be issued to employees ahead of the normal pay cycle; when the corresponding payroll action is processed, the application must decide whether the advance deduction or payment element entry is still applicable. PAY_NO_ADVANCE_PAY exposes this decision as a single callable function so that the payroll engine, element entry processing, or downstream validation logic can query the rule without embedding the decision logic in multiple places. The header comment identifies the source file as pynoapay.pkh, a Payroll module file, consistent with the PAY_ prefix naming convention used throughout Oracle Payroll packages.

Key Procedures and Functions

The ETRM metadata documents exactly one callable program unit in this package:

• ADV_PAYMENT_SKIP_RULE — A function returning VARCHAR2. Based on the documented signature in the package header, it accepts three input parameters: an element entry identifier (p_element_entry_id), a date earned (p_date_earned), and a payroll action identifier (p_payroll_action_id). The function evaluates these inputs against the advance payment rules and returns a character result indicating whether the associated advance payment should be skipped. Callers pass the specific element entry being evaluated, the date on which the earnings are attributed, and the payroll action under which processing is occurring, so the rule can be evaluated in the correct pay-period and run context. The return value is a VARCHAR2 rather than a Boolean, which allows the package to communicate a code or flag that the calling payroll logic can interpret.

No other procedures or functions are documented for this package in the ETRM repository. The package body is not exposed in the documented metadata, so the internal logic of the rule is not part of the published interface.

Tables Accessed

The ETRM metadata records two tables referenced through APPS synonyms:

• PAY_ELEMENT_ENTRIES_F — The core Payroll table storing element entry records for assignments. The function reads this table to resolve the element entry identified by p_element_entry_id, including its element type, assignment, and effective dates, which form the basis of the skip determination.
• PAY_PAYROLL_ACTIONS — The Payroll table describing payroll action instances, including action type, status, and date parameters. The function consults this table using p_payroll_action_id to establish the payroll run context in which the advance payment rule is being applied.

These two tables are the only documented data dependencies. Because the package is declared AUTHID CURRENT_USER, access to these objects is governed by the privileges of the invoking session.

Usage Notes

PAY_NO_ADVANCE_PAY is not referenced by any other documented package in the ETRM repository, indicating that it is invoked directly rather than through a package-to-package call chain. Typical invocation paths include Oracle Payroll element entry processing during a payroll run, where the payroll engine must determine whether an advance element entry should be skipped for a given assignment and pay period. It may also be called from custom PL/SQL code or from concurrent program logic that performs pre-payroll validation of advance payments.

Because the package is classified as OTHER rather than as a supported public API, Oracle does not guarantee interface stability across releases. Customizations and extensions that call ADV_PAYMENT_SKIP_RULE should be reviewed during upgrades between 12.1.1 and 12.2.2 and validated against the target environment, since the ETRM metadata reflects the 12.2.2 repository state. The package header carries a 2007 revision date, suggesting the interface has been stable for an extended period, but this does not remove the upgrade validation requirement for custom integrations.