Results for “payment_date”

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

Overview

PAY_ZA_EXTERNAL_ACCOUNTS_V is an APPS-owned database view in the Oracle E-Business Suite Payroll (PAY) product family. It is classified as VALID and is registered against the ETRM 12.2.2 object inventory, with equivalent existence under 12.1.1. As its description states, the view presents a list of payments together with their associated bank details, specifically for the South African (ZA) localization. The "ZA" prefix in the object name confirms that the underlying external account and branch lookups are driven by the PAY_ZA_BRANCH_CDV_DETAILS table, which supplies the localized bank and branch code information.

The view serves as a denormalized reporting surface that joins payment amounts, payment dates, payment methods, and bank account attributes into a single, query-ready result set. Because it consolidates data that would otherwise require multiple joins across payment, payroll action, and external account tables, it is typically consumed by custom reports, extracts, and bank reconciliation or payment-reconciliation processes rather than by seeded Oracle forms.

Underlying Base Objects

The view is defined over seven referenced base objects, all exposed through APPS synonyms:

• PAY_ASSIGNMENT_ACTIONS — provides ASSIGNMENT_ACTION_ID and the PAYROLL_ACTION_ID link.
• PAY_PAYROLL_ACTIONS — supplies ACTION_TYPE and EFFECTIVE_DATE, and is the source of PAYMENT_DATE.
• PAY_PRE_PAYMENTS — supplies PAYMENT_AMOUNT and the ASSIGNMENT_ACTION_ID and personal/org payment method identifiers.
• PAY_PERSONAL_PAYMENT_METHODS_F — the personal payment method, joined to the payroll action effective date range.
• PAY_ORG_PAYMENT_METHODS_F — the organization-level payment method, source of PAYMENT_METHOD.
• PAY_EXTERNAL_ACCOUNTS — the external bank account.
• PAY_ZA_BRANCH_CDV_DETAILS — the South African branch/bank code detail table, source of BANK.

Joins to PAY_PERSONAL_PAYMENT_METHODS_F and PAY_EXTERNAL_ACCOUNTS are outer joins, which means payments without a linked personal external account are still returned. The PAYP_ACTION_TYPE filter restricts rows to action types 'P' (payment) and 'U' (unclaimed/used in reversal contexts), scoping the view to actual payment actions.

Key Columns

• ROW_ID — the ROWID of the underlying PAY_ASSIGNMENT_ACTIONS row.
• ASSIGNMENT_ACTION_ID — the assignment action identifier, linking the payment back to the payroll run.
• PAYMENT_METHOD — the first 30 characters of ORG_PAYMENT_METHOD_NAME.
• BANK — the bank name from PAY_ZA_BRANCH_CDV_DETAILS.
• BRANCH_CODE — SEGMENT1 of the external account, representing the branch code.
• ACCOUNT_NO — SEGMENT3 of the external account, representing the account number.
• PAYMENT_AMOUNT — the payment value from PPP.VALUE.
• PAYMENT_DATE — the DATE_EARNED value from PAY_PAYROLL_ACTIONS.

The PAYMENT_DATE column is the field most frequently targeted by consumers, since it provides the effective payment date for downstream reconciliations and date-bounded extracts.

Common Use Cases and Queries

The primary use is reporting on payments with bank details, especially filtered by payment date:

SELECT assignment_action_id, payment_method, bank, branch_code,
       account_no, payment_amount, payment_date
FROM   apps.pay_za_external_accounts_v
WHERE  payment_date BETWEEN :start_date AND :end_date
ORDER  BY payment_date;

SELECT bank, payment_method, SUM(payment_amount) total_paid
FROM   apps.pay_za_external_accounts_v
WHERE  payment_date = :payment_date
GROUP  BY bank, payment_method;

Because the view is a simple projection with no bind variables or PL/SQL logic, it can be queried directly at the SQL prompt, within Oracle Reports or BI Publisher data models, or as the source for interface and bank reconciliation extracts. When performance is a concern, adding predicates on PAYMENT_DATE and PAYMENT_METHOD allows the optimizer to push filters into the underlying PAY_PAYROLL_ACTIONS and PAY_PRE_PAYMENTS tables.