Search Results check_ppm

Overview

APPS.HR_PAYMENTS is an Oracle E-Business Suite payroll validation package that governs payment method configuration within the Oracle Payroll module. Originally authored by Oracle Corporation (UK) Ltd in 1992 and carried forward into EBS 12.1.1 and 12.2.2, the package encapsulates the pre-payment validation logic that protects the integrity of payment type, payment method, and pre-payment records across organizations and individuals. Its header comment identifies its scope as "Pre-payments validation procedures. Deals with DDL on" the core payment configuration tables, and its declared procedures and functions are invoked primarily as validation hooks from Oracle Forms and from internal payroll processing routines.

The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the invoking session rather than the definer. It is classified as "OTHER" in ETRM and is referenced by six other packages, confirming its role as a shared validation utility rather than an isolated component.

Key Procedures and Functions

• PPT_BRUI — the package's original entry point, providing Before-Update/Insert validation for payment type records. It evaluates default allowance, category, pre-validation requirements, validation days, and validation value.
• MATCH_CURRENCY — reconciles currency between a payment type, organizational payment method currency, and default balance.
• CHECK_ACCOUNT — validates an external account against a payment type.
• CHECK_CURRENCY — boolean validation of currency consistency for a given type.
• GEN_BALANCE — returns a numeric balance value derived from a leg code.
• CHECK_PREPAY — validates a pre-payment record against an organizational payment method and validity start date.
• CHECK_PPM — validates personal payment method data against an organizational payment method and validity start date.
• CHECK_DEFAULT — determines whether a given organizational payment method may serve as the default.
• CHECK_AMT — reconciles percentage and fixed amount values.
• MT_CHECKS — performs multi-table checks across organizational payment method, validity date, and account.
• UNIQUE_PRIORITY — enforces uniqueness of payment method priority.
• CHECK_PP — validates personal payment records.

Tables Accessed

The package reads and writes configuration and transactional payment data through APPS synonyms. Payment type and method definitions reside in PAY_PAYMENT_TYPES, PAY_ORG_PAYMENT_METHODS_F, PAY_ORG_PAY_METHOD_USAGES, and PAY_PERSONAL_PAYMENT_METHODS_F. Pre-payment and account validation draw on PAY_PRE_PAYMENTS and PAY_EXTERNAL_ACCOUNTS. Balance and dimension logic references PAY_BALANCE_TYPES, PAY_BALANCE_DIMENSIONS, and PAY_DEFINED_BALANCES. Payroll run and assignment context is supplied by PAY_PAYROLL_ACTIONS, PAY_ASSIGNMENT_ACTIONS, and PAY_PSS_TRANSACTION_STEPS, with DUAL used for singleton evaluations.

Usage Notes

HR_PAYMENTS is normally invoked indirectly. Oracle Forms such as the Payment Methods and Payment Types maintenance windows call its validation functions on insert and update. Payroll concurrent processes invoke CHECK_PREPAY, CHECK_PPM, and MT_CHECKS during pre-payment and payment method generation. Because the package is AUTHID CURRENT_USER and referenced by six other packages, custom code should call it only after the payment configuration tables are in a consistent state. The reference to BPAY CSR Australia is not part of the documented package behavior; HR_PAYMENTS contains no BPAY-specific logic, and Australian BPAY processing is handled through separate localized payment method configuration and external payment formats rather than through this validation package.