Results for “pay_personal_payment_methods_f”

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

Overview

PAY_PERSONAL_PAYMENT_METHODS_F is the Oracle HRMS Payroll (PAY) datetable that stores the personal payment method definitions assigned to individual employees, contingent workers, and other payees. Each row describes how a specific payee elects to receive net pay, and it is the seat of the business rules that determine how a payroll run distributes a net payment across one or more payment methods. The table resides in the HR schema and is date-tracked: it is a "_F" (date-effective / "F" for full datetrack) entity, meaning every logical personal payment method may be represented by multiple rows partitioned by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.

Its role in Oracle EBS is to bridge the payroll assignment and the external payment instrument (bank account, cheque, or third-party account). It is referenced throughout the payroll run, prepayments, and electronic funds transfer (EFT) payment processes, and it is the source of truth for percentage/amount splits and payment priority at the person level. In Oracle EBS 12.1.1 and 12.2.2, the object retains the same transactional and datetrack semantics; the 12.2.2 documented schema exposes 73 columns, confirming the addition of descriptive flexfield (PPM_INFORMATION1–30) and object-versioning columns required for the Oracle Fusion/ADF-compatible data model.

From a Data Vault modeling perspective, the mined relationship data classifies this table as a link. This is a heuristic suggestion: the presence of foreign keys to HR_ALL_ORGANIZATION_UNITS and PAY_EXTERNAL_ACCOUNTS, together with an association to ASSIGNMENT_ID, indicates a many-to-many junction between the payee, the payment instrument, and the employing organization. A Data Vault model would consequently treat PAY_PERSONAL_PAYMENT_METHODS_F as a link table with satellites for the datetracked attributes.

Key Information Stored

The table's surrogate primary key is PAY_PERSONAL_PAYMENT_METHO_PK, defined over the composite of PERSONAL_PAYMENT_METHOD_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE. Because the PK includes the datetrack columns, PERSONAL_PAYMENT_METHOD_ID alone is not unique; the same surrogate identifier recurs for each version of the record. The unique index documented for this object is the primary key itself, so the effective-dated triple is the business-key candidate.

• PERSONAL_PAYMENT_METHOD_ID – surrogate identifier for the logical personal payment method; the leading column of the primary key.
• PERSONAL_PAYMENT_ID-equivalent datetrack columns: EFFECTIVE_START_DATE and EFFECTIVE_END_DATE delimit validity relative to the payroll period being processed.
• BUSINESS_GROUP_ID – foreign key to HR_ALL_ORGANIZATION_UNITS, identifying the payroll business group (enterprise) that owns the record.
• EXTERNAL_ACCOUNT_ID – foreign key to PAY_EXTERNAL_ACCOUNTS, pointing to the payee's bank or third-party account used to receive the payment.
• ASSIGNMENT_ID – the payroll assignment to which the personal payment method is attached.
• ORG_PAYMENT_METHOD_ID – the organization-level payment method template from which the personal method is derived.
• PAYEE_ID and PAYEE_TYPE – identify the recipient and distinguish employees, applicants, or other payees.
• PERSON_ID – the person record associated with the payee.
• AMOUNT and PERCENTAGE – define the fixed amount and/or proportional split of net pay directed to this method.
• PRIORITY – sequence in which multiple methods are funded (for example, primary account before a secondary split account).
• RUN_TYPE_ID – identifies the payroll run type the method applies to.
• PPM_INFORMATION_CATEGORY and PPM_INFORMATION1–30 – the developer descriptive flexfield context and attribute segments.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, and CREATION_DATE – standard Oracle who-audit and optimistic-locking columns.

Common Use Cases and Queries

The most common requirement is to resolve, as of a given date, the active payment method(s) for a person or assignment. Because the table is date-effective, all queries must filter on SYSDATE (or the payroll period's effective date) against the datetrack windows:

• Active methods for an assignment: select PERSONAL_PAYMENT_METHOD_ID, EXTERNAL_ACCOUNT_ID, PERCENTAGE, AMOUNT, PRIORITY from PAY_PERSONAL_PAYMENT_METHODS_F where ASSIGNMENT_ID = :p_assignment and SYSDATE between EFFECTIVE_START_DATE and EFFECTIVE_END_DATE.
• Payment distribution reporting: group PERCENTAGE by PERSON_ID to verify employees whose percentages sum to 100, and flag records where PERCENTAGE and AMOUNT are both populated (a validation conflict).
• Bank account audit: join to PAY_EXTERNAL_ACCOUNTS on EXTERNAL_ACCOUNT_ID = EXTERNAL_ACCOUNT_ID to reconcile payment methods against account numbers and account types.
• Multi-method payees: filter on PRIORITY > 1 to isolate split-payment configurations used for direct deposit remainder accounts.
• DFF extraction: query PPM_INFORMATION_CATEGORY and the PPM_INFORMATIONn segments when a client has configured descriptive flexfields for region- or bank-specific attributes.

Standard HRMS security (security profiles) and the PAY_PAYMENT_METHODS / PAY_PERSONAL_PAYMENT_METHODS form and API layer are the normal interfaces; direct DML should be avoided because datetrack consistency is maintained by the HR_PAY_PERSONAL_PAYMENT_METHODS_API.

Related Objects

• HR_ALL_ORGANIZATION_UNITS – joined on BUSINESS_GROUP_ID = ORGANIZATION_ID; supplies the payroll business group owning the method.
• PAY_EXTERNAL_ACCOUNTS – joined on EXTERNAL_ACCOUNT_ID = EXTERNAL_ACCOUNT_ID; the external bank or third-party account receiving the payment.
• PAY_PERSONAL_PAYMENT_METHODS – the non-datetrack "view-equivalent" / API view layer typically used for simplified access to current rows.
• PAY_ORG_PAYMENT_METHODS_F – organization-level payment method definitions referenced through ORG_PAYMENT_METHOD_ID.
• PAY_ASSIGNMENT_ACTIONS and PER_ALL_ASSIGNMENTS_F – assignments referenced through ASSIGNMENT_ID and PERSON_ID.
• PAY_PAYROLL_ACTIONS and PAY_RUN_RESULTS – payroll run objects that consume the method during net-pay calculation and payment.
• PAY_PAYMENT_TYPES – resolves the payment category (bank transfer, cheque, etc.) used by the method.
• HR_PAY_PERSONAL_PAYMENT_METHODS_API – the supported PL/SQL API for inserting, updating, and datetracking rows in this table.