Results for “personal_payment_method_id”

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

Overview

PAYBV_PRE_PAYMENTS_V is a read-only Oracle EBS view owned by the APPS schema and categorized under the PAY (Payroll) product family. It is a "BV" (business view / version) style reporting object and is documented as VALID in ETRM for both 12.1.1 and 12.2.2. The view exposes pre-payment information sourced from the Oracle Payroll pre-payments table, presenting payment processing data in a flattened, query-friendly shape suitable for reporting, extracts, and integration.

The view's principal design intent is to expose the internal identifier columns of a pre-payment record alongside its monetary amounts and the various foreign-key references that tie the pre-payment back to the source payroll action, the person's payment method, the organization's payment method, and the assignment action that generated it. This makes the view particularly useful where downstream logic needs to reconcile a pre-payment to its originating payroll run activity.

Underlying Base Objects

Per the documented ETRM metadata, PAYBV_PRE_PAYMENTS_V is defined over a single base object: the synonym PAY_PRE_PAYMENTS (aliased as PPP). The underlying physical table is PAY_PRE_PAYMENTS, part of the Oracle Payroll application schema. The view is defined with a WITH READ ONLY clause, meaning it is strictly non-updatable and is intended purely for query and reporting purposes.

Because the view projects selected columns from a single table with no joins, filtering, or aggregation, it behaves as a direct column-projection layer. This is characteristic of "BV" views that provide a stable, presentation-oriented interface separate from the physical table, allowing Oracle to evolve the base table without breaking dependent reports and integrations that reference the view.

Key Columns

The view exposes eight columns, listed in the view text as follows:

• VALUE — The pre-payment amount in the transaction/entry currency of the payment.
• BASE_CURRENCY_VALUE — The pre-payment amount converted into the base currency for the business group, enabling cross-currency comparison and reporting. This is the column most commonly targeted by users searching for "base_currency_value."
• PRE_PAYMENT_ID — Primary key identifying the pre-payment record.
• PERSONAL_PAYMENT_METHOD_ID — Foreign key to the person-level payment method used for the payment.
• ASSIGNMENT_ACTION_ID — Foreign key to the assignment action that generated the pre-payment, linking it to the payroll run activity for a specific assignment.
• ORG_PAYMENT_METHOD_ID — Foreign key to the organization-level (external) payment method definition.
• SOURCE_ACTION_ID — Identifier of the source action from which the pre-payment originated.
• PREPAYMENT_ACTION_ID — Identifier of the pre-payment action itself, used for action-level reconciliation.

Common Use Cases and Queries

Typical scenarios include reconciling pre-payment amounts against their source payroll actions, reporting amounts in the base currency for consolidation, and extracting payment method references for downstream treasury or banking integration. Because the view is read-only, it is safe to query in extract pipelines.

A representative query retrieving base-currency pre-payment amounts and their linkage to source actions:

• SELECT v.pre_payment_id, v.value, v.base_currency_value, v.assignment_action_id, v.source_action_id FROM apps.paybv_pre_payments_v v WHERE v.base_currency_value IS NOT NULL;
• SELECT v.personal_payment_method_id, SUM(v.base_currency_value) total_paid FROM apps.paybv_pre_payments_v v GROUP BY v.personal_payment_method_id;

Consult the Oracle Payroll data model and your localization requirements to confirm currency conversion context for BASE_CURRENCY_VALUE.