Results for “pay_payment_types”

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

Overview

PAY_PAYMENT_TYPES is a foundational reference table in the Oracle EBS Payroll (PAY) module, owned by the HR schema. It defines the categories of payment that the payroll system is capable of processing, such as check, direct deposit, or wire transfer, and serves as the master lookup against which organizational payment methods and payroll action records are validated. The table is classified by status as VALID and, in the 12.2.2 documented schema, contains 18 physical columns.

From a modeling perspective, the heuristic Data Vault classification for PAY_PAYMENT_TYPES is hub-leaning. This suggests that the table behaves primarily as a business-key repository whose stable identifiers (payment type and territory) anchor related satellite and link structures elsewhere in the payroll data model, with transactional context layered on through dependent tables.

Key Information Stored

The table stores the definitional attributes required to drive payment processing logic and validation across the payroll engine. The most significant columns include:

• PAYMENT_TYPE_ID — the surrogate primary key, defined by unique index PAY_PAYMENT_TYPES_PK (with ZD_EDITION_NAME for editioning support).
• PAYMENT_TYPE_NAME and TERRITORY_CODE — the documented business-key candidates, enforced together by unique index PAY_PAYMENT_TYPES_UK2 (also including ZD_EDITION_NAME).
• CURRENCY_CODE — the currency in which the payment type is denominated.
• CATEGORY — the classification grouping for the payment type.
• ALLOW_AS_DEFAULT — a flag controlling whether the type may be selected as a default.
• DESCRIPTION — the human-readable explanation of the payment type.
• PRE_VALIDATION_REQUIRED, PROCEDURE_NAME, VALIDATION_DAYS, and VALIDATION_VALUE — parameters governing pre-payment validation behavior, including the PL/SQL procedure invoked and the timing/value thresholds applied.
• RECONCILIATION_FUNCTION — the function used to reconcile the payment.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE — standard WHO audit columns.
  
• ZD_EDITION_NAME — the editioning column supporting the 12.2 online patching architecture.

Common Use Cases and Queries

Typical reporting and integration scenarios include resolving payment type names for organizational payment methods, auditing validation configuration, and driving payroll action processing. A basic lookup might appear as:

SELECT payment_type_id, payment_type_name, territory_code, currency_code
FROM   pay_payment_types
WHERE  territory_code = :p_territory
AND    allow_as_default = 'Y';

Joining to organizational configuration supports reconciliation reporting:

SELECT om.org_payment_method_id, pt.payment_type_name, om.currency_code
FROM   pay_org_payment_methods_f om,
       pay_payment_types pt
WHERE  om.payment_type_id = pt.payment_type_id;

Validation auditing queries filter on PRE_VALIDATION_REQUIRED or examine PROCEDURE_NAME assignments to confirm that pre-payment checks are properly wired.

Related Objects

PAY_PAYMENT_TYPES is referenced by several dependent tables through the PAYMENT_TYPE_ID foreign key, reflecting its role as a shared reference hub:

• PAY_ORG_PAYMENT_METHODS_F — organizational payment methods, joined on PAYMENT_TYPE_ID.
• PAY_ORG_PAYMENT_METHODS_F_EFC — the corresponding editioning/date-tracked companion table.
• PAY_PAYROLL_ACTIONS — payroll action records consuming the payment type.
• PAY_PAYROLL_ACTIONS_EFC — its date-tracked counterpart.
• OKL_FEES_B — Oracle Lease Management fee records referencing the payment type.
• HR_S_PAYMENT_TYPES — the HR security/seed view or table referencing the payment type.

Together these objects demonstrate that PAY_PAYMENT_TYPES functions as a central, cross-module reference point for payment classification and processing in Oracle EBS.