Results for “pay_au_eoy_values_v”

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

Overview

PAY_AU_EOY_VALUES_V is an APPS-owned database view within the Oracle EBS Payroll (PAY) product, specifically scoped to Australian legislative reporting. It is a reporting and integration vehicle that exposes End-of-Year (EOY) payment summary data for Australian payroll processing. The view is classified as VALID in the ETRM repository and is defined in the APPS schema, making it accessible to standard EBS responsibilities that have been granted the appropriate privileges.

The view does not store data; rather it derives its result set dynamically. Its central purpose is to surface the reporting attributes required for Australian EOY payment summary generation, including financial year identifiers, registered employer details, supplier (payee) information, and reporting flags. These attributes are archived against individual assignment actions during payroll processing and are then re-exposed through this view to support reporting, reconciliation, and downstream integration.

Because it draws on both base payroll tables and packaged PL/SQL functions, the view acts as a bridge between transactional payroll data and the legislative parameters that govern Australian EOY obligations. This makes it a key object for consultants and developers building or troubleshooting EOY payment summary reports and extracts.

Underlying Base Objects

The documented ETRM metadata for 12.2.2 identifies the following base objects referenced by PAY_AU_EOY_VALUES_V:

• PAY_ASSIGNMENT_ACTIONS (synonym) — the transactional table holding assignment-level processing actions; the view selects ASSIGNMENT_ACTION_ID and ASSIGNMENT_ID from it.
• PAY_PAYROLL_ACTIONS (synonym) — the parent table for payroll run actions; the view draws PAYROLL_ACTION_ID and the LEGISLATIVE_PARAMETERS column from it.
• PER_ALL_ASSIGNMENTS_F (synonym) — the assignments table, used to obtain the ASSIGNMENT_ROWID.
• PAY_AU_PAYMENT_SUMMARY (package) — a PL/SQL package whose GET_ARCHIVE_VALUE function retrieves the archived EOY reporting values.
• PAY_CORE_UTILS (package) — a utility package whose GET_PARAMETER function extracts named legislative parameters.

The joins between assignment actions, payroll actions, and assignments establish the processing context, while the two packages supply the legislative and archived reporting attributes. Consequently, the view's output depends on both the correctness of the underlying transactional data and the availability of archived EOY values captured during payroll processing.

Key Columns

The view exposes a set of columns reflecting the archived EOY reporting attributes. Notable examples include:

• ASSIGNMENT_ROWID, ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID — identifiers linking the record to a specific assignment action and assignment.
• PAYROLL_ACTION_ID — the parent payroll action driving the EOY data.
• X_REPORTING_FLAG, X_CURR_TERM_0_BAL_FLAG — archived flags indicating reporting status and current-term zero-balance conditions.
• FINANCIAL_YEAR, REGISTERED_EMPLOYER — legislative parameters retrieved via GET_PARAMETER.
• X_REPORT_END_DATE — the archived reporting end date.
• X_SUPPLIER_* — a family of archived supplier (payee) attributes, including number, name, contact name, contact telephone, address lines, suburb, state, postcode, and country.

Common Use Cases and Queries

Typical scenarios include verifying archived EOY values for a payroll run, reconciling payment summary data, and extracting supplier details for reporting. A representative query follows:

SELECT assignment_action_id, assignment_id, financial_year, registered_employer, x_report_end_date, x_supplier_name, x_supplier_address_1, x_supplier_suburb, x_supplier_state, x_supplier_postcode FROM pay_au_eoy_values_v WHERE financial_year = :p_year ORDER BY assignment_id;

Consultants may also filter on X_REPORTING_FLAG to isolate records flagged for reporting, or join to PER_ALL_ASSIGNMENTS_F and PAY_PAYROLL_ACTIONS to enrich the extract with employee and payroll run context. Because the view relies on package functions, performance should be assessed against the volume of archived assignment actions.