Results for “pay_pre_payments_v”

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

Overview

The APPS.PAY_PRE_PAYMENTS_V view is an Oracle E-Business Suite Payroll (PAY) product object supplied by the APPS schema. Its ETRM-reported status is VALID, and its documented purpose is to support the Payroll user interface rather than to serve as a standalone reporting entity. The view consolidates pre-payment records generated by the payroll run process with the descriptive attributes required to render them intelligibly to the user: organization payment method names, payment type names, currency codes, payment source meanings, priorities, business group identifiers, and a dynamically derived payment status.

Because the view participates in a UNION ALL construct, it presents the same logical shape from two branches, which allows the Payroll payment and prepayment pages to retrieve rows in a single result set regardless of whether the record originates from the payroll action's organization payment method or from an individual's personal payment method. The view is therefore best understood as a presentation-layer flattening of the PAY_PRE_PAYMENTS transaction table joined to the payment method, payment type, lookup, and payroll action reference data needed for display.

Underlying Base Objects

The ETRM 12.2.2 metadata lists the following referenced base objects: PAY_PRE_PAYMENTS (synonym), PAY_ASSIGNMENT_ACTIONS (synonym), PAY_PAYROLL_ACTIONS (synonym), PAY_PERSONAL_PAYMENT_METHODS_F (synonym), PAY_ORG_PAYMENT_METHODS_F (synonym), PAY_ORG_PAYMENT_METHODS_F_TL (synonym), PAY_PAYMENT_TYPES (synonym), PAY_PAYMENT_TYPES_TL (synonym), HR_LOOKUPS (view), HR_API (package), and PAY_ASSIGNMENT_ACTIONS_PKG (package).

• PAY_PRE_PAYMENTS is the driving table; PPP.PRE_PAYMENT_ID and PPP.ASSIGNMENT_ACTION_ID anchor each row.
• PAY_ASSIGNMENT_ACTIONS and PAY_PAYROLL_ACTIONS provide the assignment action and payroll action context, including the effective date used to select the correct dated payment method row.
• PAY_ORG_PAYMENT_METHODS_F and its _TL translation table supply the organization payment method definition and its language-specific name, filtered by USERENV('LANG').
• PAY_PAYMENT_TYPES and PAY_PAYMENT_TYPES_TL supply the payment type and its translated name, also language-filtered.
• PAY_PERSONAL_PAYMENT_METHODS_F is outer-joined to allow personal payment methods to be optional (the (+) on PPP.PERSONAL_PAYMENT_METHOD_ID).
• HR_LOOKUPS (view) resolves the PAYMENT_SOURCE lookup meaning for the decoded source value (D, P, or O).
• HR_API and PAY_ASSIGNMENT_ACTIONS_PKG are referenced program units; the latter supplies the GET_PAYMENT_STATUS function.

Key Columns

• PRE_PAYMENT_ID — primary identifier of the pre-payment record.
• ASSIGNMENT_ACTION_ID / PREPAY_ACTION_ID / PREPAYMENT_ACTION_ID — linkage to the assignment action and prepayment action context.
• ORG_PAYMENT_METHOD_NAME — translated organization payment method name.
• PAYMENT_TYPE_NAME — translated payment type name.
• PRIORITY — priority from the personal payment method.
• SOURCE — decoded PAYMENT_SOURCE meaning ('D' direct, 'P' personal, 'O' organization) derived via DECODE logic.
• CURRENCY_CODE — currency of the organization payment method.
• VALUE — the pre-payment amount.
• STATUS — computed at runtime by PAY_ASSIGNMENT_ACTIONS_PKG.GET_PAYMENT_STATUS(ASSIGNMENT_ACTION_ID, PRE_PAYMENT_ID).
• BUSINESS_GROUP_ID — business group identifier, expressed as OPM.BUSINESS_GROUP_ID + 0.

Common Use Cases and Queries

The view is typically queried to inspect prepayment rows for a payroll action, to reconcile prepayment amounts against assignment actions, or to present payment method and status information for a given assignment. A representative query follows:

• SELECT pre_payment_id, assignment_action_id, org_payment_method_name, payment_type_name, source, currency_code, value, status FROM apps.pay_pre_payments_v WHERE assignment_action_id = :p_assignment_action_id;
• SELECT pre_payment_id, source, currency_code, value, status FROM apps.pay_pre_payments_v WHERE business_group_id = :p_business_group_id ORDER BY pre_payment_id;

Because STATUS is generated by a PL/SQL function call, filtering or ordering on STATUS can be costly; restricting the driving predicates on ASSIGNMENT_ACTION_ID, BUSINESS_GROUP_ID, or PRE_PAYMENT_ID first is advisable. The view should be treated as a UI-support object, and direct updates are not supported.