Search Results pay_personal_payment_methods




Overview
Explore in AI Chat

Overview

PAY_PERSONAL_PAYMENT_METHODS is a date-effective view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the PAY (Payroll) product family. Its role is to expose the currently effective personal payment method records for a given session, rather than every historical or future-dated row stored in the underlying table. This is achieved through a filter on the EFFECTIVE_START_DATE and EFFECTIVE_END_DATE columns against the effective date held in FND_SESSIONS for the active session.

Because personal payment methods determine how a payee's net pay is disbursed — the organization payment method used, the external bank account, and the split of amounts or percentages — the view is central to payroll disbursement processing, payment method validation, and any reporting or integration that must reflect the payment instructions in force at a point in time. It is documented as VALID and is available in both EBS 12.1.1 and 12.2.2 environments. In reporting and integration contexts the view presents a session-aware, single-version snapshot, sparing the consumer from manually applying date-effectivity logic.

Underlying Base Objects

The view is defined directly over PAY_PERSONAL_PAYMENT_METHODS_F, the date-effective ("_F") table that stores personal payment method definitions with their effective start and end dates. All columns listed in the view text originate from that base table; the view adds no derived values of its own. The second referenced object is FND_SESSIONS, accessed as a synonym, which supplies the effective date used in the WHERE predicate. Two scalar subqueries read FND_SESSIONS keyed on USERENV('SESSIONID'), requiring that EFFECTIVE_START_DATE be less than or equal to the session effective date and EFFECTIVE_END_DATE be greater than or equal to it.

Consequently, the view always returns the rows effective for the current application session. Rows whose effectivity window does not contain the session effective date are excluded, and because the underlying table may hold multiple dated versions of the same payment method, only the version(s) covering that date are surfaced. This relationship means the view is appropriate for transactional and session-driven use, while historical analysis of all versions must query the base table directly.

The base object is referenced through a synonym, and the view inherits the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) plus OBJECT_VERSION_NUMBER for optimistic locking.

Key Columns

  • PERSONAL_PAYMENT_METHOD_ID — Primary identifier for the personal payment method record.
  • EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — The date-effectivity window used by the view filter; critical for understanding which version is returned.
  • BUSINESS_GROUP_ID — Business group that owns the record, supporting multi-organization segregation.
  • PERSON_ID / PAYEE_ID / PAYEE_TYPE — Identify the person or payee to whom the payment method belongs.
  • ASSIGNMENT_ID — Assignment associated with the payment method, tying it to a specific employment assignment.
  • ORG_PAYMENT_METHOD_ID — Reference to the organization payment method that defines the payment mechanism.
  • EXTERNAL_ACCOUNT_ID — The external bank account used for disbursement.
  • AMOUNT, PERCENTAGE, PRIORITY — Control how net pay is allocated across multiple payment methods, by fixed amount, percentage split, or priority order.
  • RUN_TYPE_ID — Optional run type restricting the payment method to particular payroll runs.
  • COMMENT_ID — Reference to associated comment text.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — Descriptive flexfield segments for customer-defined data.
  • OBJECT_VERSION_NUMBER and WHO columns — Concurrency control and audit information.

Common Use Cases and Queries

The view is typically used to report or validate the payment methods currently in effect for employees, for example during payroll reconciliation, bank file review, or interfaces building payment instructions. A representative query listing effective payment methods for a person is:

SELECT personal_payment_method_id, person_id, assignment_id, org_payment_method_id, external_account_id, amount, percentage, priority FROM apps.pay_personal_payment_methods WHERE person_id = :p_person_id ORDER BY priority;

To examine splits for a specific organization payment method:

SELECT ppm.personal_payment_method_id, ppm.person_id, ppm.percentage, ppm.amount FROM apps.pay_personal_payment_methods ppm WHERE ppm.org_payment_method_id = :p_org_payment_method_id;

Because results depend on the session effective date, queries executed through a standard EBS session return only currently effective rows. Analysts needing full history, including future-dated or expired versions, should query PAY_PERSONAL_PAYMENT_METHODS_F and apply their own date criteria. Integrations should treat the view as read-only and rely on the base table for any dated maintenance operations.