Results for “assignment_rowid”

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

Overview

PAY_AU_SELFP_VALUES_V is an Australian localisation view owned by the APPS schema within the PAY (Payroll) product family of Oracle E-Business Suite, and it is documented as VALID in release 12.2.2 (and available in 12.1.1). The view exposes the data captured and archived by the Australian Self Payment (SELFP) processes, notably the payment summary information submitted to the Australian Taxation Office (ATO) and the supplier/registered employer details held against a payroll action.

Functionally, the view acts as a flattened presentation layer over payroll assignment actions and payroll actions. Rather than storing data itself, it derives most of its columns at query time by invoking the PL/SQL functions PAY_AU_PAYMENT_SUMMARY.GET_ARCHIVE_VALUE and PAY_CORE_UTILS.GET_PARAMETER. This makes the view a convenient, reusable interface for reports, concurrent programs, extracts, and integrations that need Australian payment summary and supplier reporting content keyed by assignment action and payroll action.

Underlying Base Objects

The ETRM metadata documents the following referenced objects (as APPS synonyms over the base application tables and packages):

• PAY_ACTION_INTERLOCKS (SYNONYM)
• PAY_ASSIGNMENT_ACTIONS (SYNONYM)
• PAY_AU_PAYMENT_SUMMARY (PACKAGE)
• PAY_CORE_UTILS (PACKAGE)
• PAY_PAYROLL_ACTIONS (SYNONYM)
• PER_ALL_ASSIGNMENTS_F (SYNONYM)

PAY_ASSIGNMENT_ACTIONS (aliased PAC in the view text) supplies the ASSIGNMENT_ACTION_ID and ASSIGNMENT_ID driving keys, and PAY_PAYROLL_ACTIONS (aliased PPA) supplies the PAYROLL_ACTION_ID and the LEGISLATIVE_PARAMETERS string. PER_ALL_ASSIGNMENTS_F (aliased PAA) contributes the ASSIGNMENT_ROWID, allowing the view to be joined back to the assignment. PAY_CORE_UTILS.GET_PARAMETER decodes values from the legislative parameters (for example FINANCIAL_YEAR and REGISTERED_EMPLOYER), while PAY_AU_PAYMENT_SUMMARY.GET_ARCHIVE_VALUE retrieves the archived reporting attributes stored against each assignment action. PAY_ACTION_INTERLOCKS is referenced as part of this Australian localisation data model. The view therefore has no physical storage; it is a runtime projection assembled from these tables and packages.

Key Columns

• ASSIGNMENT_ROWID, ASSIGNMENT_ID, ASSIGNMENT_ACTION_ID — identifiers linking each row to the assignment and the assignment action.
• PAYROLL_ACTION_ID — the parent payroll action for the row.
• FINANCIAL_YEAR, REGISTERED_EMPLOYER — Australian legislative parameters retrieved via PAY_CORE_UTILS.GET_PARAMETER.
• X_REPORTING_FLAG, X_CURR_TERM_0_BAL_FLAG — archive flags indicating reporting status and zero-balance current-term treatment.
• X_REPORT_END_DATE — the reporting period end date held in the archive.
• X_SUPPLIER_NUMBER, X_SUPPLIER_NAME, X_SUPPLIER_CONTACT_NAME, X_SUPPLIER_CONTACT_TELEPHONE — supplier (registered employer/payee) identification and contact details.
• X_SUPPLIER_ADDRESS_1, X_SUPPLIER_ADDRESS_2, X_SUPPLIER_ADDRESS_3, X_SUPPLIER_SUBURB, X_SUPPLIER_STATE, X_SUPPLIER_POSTCODE, X_SUPPLIER_COUNTRY — supplier address components used in Australian payment summary reporting.

Common Use Cases and Queries

Typical uses include ATO payment summary reporting, supplier/registered employer extracts, reconciliation of archived values against payroll actions, and diagnostic checks on the Australian localisation archive. Because the view is function-driven, restrict queries by ASSIGNMENT_ACTION_ID or PAYROLL_ACTION_ID to avoid full scans.

Sample query joining back to the assignment and limiting by payroll action:

• SELECT v.ASSIGNMENT_ACTION_ID, v.ASSIGNMENT_ID, v.FINANCIAL_YEAR, v.REGISTERED_EMPLOYER, v.X_SUPPLIER_NAME, v.X_REPORT_END_DATE FROM apps.pay_au_selfp_values_v v WHERE v.PAYROLL_ACTION_ID = :p_payroll_action_id;
• SELECT v.ASSIGNMENT_ACTION_ID, v.X_REPORTING_FLAG, v.X_SUPPLIER_NUMBER, v.X_SUPPLIER_STATE, v.X_SUPPLIER_POSTCODE FROM apps.pay_au_selfp_values_v v WHERE v.ASSIGNMENT_ACTION_ID = :p_assignment_action_id;

For reporting extracts, join the view to PER_ALL_ASSIGNMENTS_F via ASSIGNMENT_ID to resolve person and assignment attributes, and always test performance with representative volumes since each archived attribute is resolved through a separate function call.