Results for “nz_bank”

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

Overview

APPS.PAY_NZ_ASG_PAYMENTS_V is a New Zealand localizations view in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It presents the payment instructions generated for assignment actions within the Oracle Payroll prepayment process, restricted to payroll actions of type 'P' (payroll run) and 'U' (retroactive or supplementary processing). The view is designed to expose one row per assignment action per payment, resolving details of the payment method, the external bank account held by the person, and the corresponding payment amount.

Its principal role is as a reporting and integration source for NZ payroll disbursements. Downstream processes, bank file formats, and reconciliation reports frequently select from this view rather than performing the multi-table join themselves. The view supplies the textual bank branch lookup meaning (based on the local lookup type NZ_BANK) and concatenated bank account segments in a single, denormalized shape suitable for output files or ad-hoc queries.

Underlying Base Objects

The view is defined over several synonym-referenced EBS tables and views, combined through a UNION. The documented base objects are: PAY_EXTERNAL_ACCOUNTS, PAY_PERSONAL_PAYMENT_METHODS_F, PAY_PRE_PAYMENTS, PAY_ASSIGNMENT_ACTIONS, PAY_PAYROLL_ACTIONS, PAY_ORG_PAYMENT_METHODS_F, HR_LOOKUPS, and the HR_API package.

• PAY_ASSIGNMENT_ACTIONS — joined to PAY_PAYROLL_ACTIONS to filter only payroll actions whose action_type is 'P' or 'U'.
• PAY_PRE_PAYMENTS — supplies the payment_amount (PP.VALUE) and links the assignment action to a personal or organizational payment method.
• PAY_PERSONAL_PAYMENT_METHODS_F — provides the person-level payment method, effective-dated against the payroll action effective date.
• PAY_ORG_PAYMENT_METHODS_F — supplies org_payment_method_name for both the personal-method branch and the org-only branch of the UNION.
• PAY_EXTERNAL_ACCOUNTS — outer-joined to the personal payment method on external_account_id, supplying the bank account segments.
• HR_LOOKUPS — outer-joined on SUBSET of segment1 and lookup_type 'NZ_BANK', supplying the bank branch meaning.

The second branch of the UNION covers payments for organizational payment methods where no personal payment method is assigned (personal_payment_method_id IS NULL); in that branch bank account, code, and reference columns are returned as NULL.

Key Columns

• ROW_ID — the ROWID of the assignment action, provided as a unique row identifier.
• ASSIGNMENT_ACTION_ID — identifier of the assignment action producing the payment.
• PAYMENT_METHOD — the organizational payment method name (truncated to 30 characters in the second UNION branch).
• MEANING — the bank branch description resolved from HR_LOOKUPS for lookup type NZ_BANK, matched against the first two characters of SEGMENT1.
• BANK_ACCOUNT — concatenation of SEGMENT1, SEGMENT2, and SEGMENT3 of the external account, representing bank, branch, and account number components separated by hyphens.
• CODE — SEGMENT4 of the external account, typically a suffix or account-type qualifier.
• REFERENCE — SEGMENT5 of the external account, typically a payment reference.
• PAYMENT_AMOUNT — the prepayment value, i.e. the amount payable for that assignment action and payment.

Common Use Cases and Queries

The view is most often consumed for New Zealand bank payment output and for verifying that prepayments carry valid bank details. A typical query returning payment instructions for a payroll run is:

SELECT assignment_action_id, payment_method, meaning, bank_account, code, reference, payment_amount FROM apps.pay_nz_asg_payments_v WHERE payment_amount IS NOT NULL;

To locate payment rows lacking a resolved bank branch lookup (potential setup gaps), filter on the meaning column:

SELECT assignment_action_id, bank_account, payment_amount FROM apps.pay_nz_asg_payments_v WHERE meaning IS NULL AND bank_account IS NOT NULL;

Because the view joins effective-dated rows, results should be interpreted in the context of the payroll action effective date to avoid duplication across payment method versions. Consumers requiring only row identity may use ROW_ID.