Results for “p_object_version_number”

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

Overview

PAY_PAYROLL_ACTIONS_V4 is a public Oracle E-Business Suite view owned by the APPS schema and classified under the PAY (Payroll) product family. In the ETRM metadata for 12.1.1 and 12.2.2 it is marked VALID, and its documented purpose is to support the Payroll user interface rather than to serve as a standalone transactional entity. Practically, this means the view is the presentation-layer projection that Oracle Payroll forms and self-service pages read from when displaying payroll run information, and it is equally the object that customers and integrators query when they need a denormalized, UI-ready view of payroll actions.

The view is filtered to payroll actions of type 'Q' (QuickPay), which is a critical scoping characteristic. Any reporting built on PAY_PAYROLL_ACTIONS_V4 will therefore return only QuickPay-related actions; standard payroll runs must be sourced from the underlying PAY_PAYROLL_ACTIONS table directly. This view is the natural answer to the common search term "consolidation_name," because it exposes CONSOLIDATION_NAME as a resolved, human-readable column, sparing the caller a manual join to PAY_CONSOLIDATION_SETS.

Underlying Base Objects

The view text shows an inner join between two base objects and an outer join to a third:

• PAY_PAYROLL_ACTIONS (SYNONYM) — aliased PAC, the driving table. All primary action attributes, including CONSOLIDATION_SET_ID, PAYROLL_ID, and ACTION_TYPE, originate here.
• PAY_ASSIGNMENT_ACTIONS (SYNONYM) — aliased AAC, joined on PAYROLL_ACTION_ID. The view restricts to AAC.SOURCE_ACTION_ID IS NULL, returning the parent assignment action rather than reversal or child rows.
• PAY_CONSOLIDATION_SETS (SYNONYM) — aliased PCS, outer-joined (PCS.CONSOLIDATION_SET_ID(+) = PAC.CONSOLIDATION_SET_ID). Because the join is outer, payroll actions with no consolidation set still appear, with CONSOLIDATION_NAME null.
• HR_PAYROLLS (PACKAGE) — referenced through the PL/SQL function HR_PAYROLLS.DISPLAY_PERIOD_NAME(PAC.PAYROLL_ACTION_ID), which resolves the PAID_PERIOD display value at query time.

The dependency on the HR_PAYROLLS package means the view executes a function call per row, which has performance implications for large extracts.

Key Columns

• PAYROLL_ACTION_ID — the primary identifier of the payroll action, used to join to other payroll objects.
• CONSOLIDATION_NAME — the resolved consolidation set name from PAY_CONSOLIDATION_SETS.CONSOLIDATION_SET_NAME, paired with CONSOLIDATION_SET_ID. This is the column most commonly used for grouping and reporting on consolidation sets.
• PAID_PERIOD — derived via HR_PAYROLLS.DISPLAY_PERIOD_NAME, presenting the period in user-facing display format.
• ACTION_POPULATION_STATUS and DB_ACTION_STATUS — the population status of the action and the assignment-level action status respectively.
• DB_DISPLAY_RUN_NUMBER — the internal display run number, renamed from DISPLAY_RUN_NUMBER to signal it is the raw database value.
• P_OBJECT_VERSION_NUMBER and A_OBJECT_VERSION_NUMBER — optimistic locking versions for the payroll action and assignment action rows.
• ASSIGNMENT_ACTION_ID, ASSIGNMENT_ID, ACTION_SEQUENCE — the assignment action context supporting drill-down from the payroll action.
• LAST_UPDATE_DATE, CREATED_BY, CREATION_DATE — standard WHO audit columns for change tracking.

Common Use Cases and Queries

Typical usage includes reporting on QuickPay runs by consolidation set, validating that consolidation names are correctly assigned before a payroll cycle, extracting a UI-equivalent dataset for reconciliation, and supporting custom OAF or BI Publisher pages that mimic the standard Payroll UI.

A representative query listing QuickPay actions with their consolidation set:

• SELECT payroll_action_id, effective_date, paid_period, consolidation_name, db_action_status FROM pay_payroll_actions_v4 WHERE business_group_id = :p_bg_id ORDER BY effective_date DESC;

To isolate actions lacking a consolidation set (a frequent data-cleansing check), filter on CONSOLIDATION_NAME IS NULL. When performance matters, prefer querying PAY_PAYROLL_ACTIONS with an explicit outer join to PAY_CONSOLIDATION_SETS rather than invoking the view, since the view's function call and inner join to PAY_ASSIGNMENT_ACTIONS add cost.