Results for “row_id”

50+ results




Overview
Explore in AI Chat

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

Overview

The view PAY_NZ_ASG_LEAVE_TAKEN_V is a read-only, denormalized reporting object owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) product. Its name and column structure identify it as a New Zealand (NZ) localization view that consolidates leave or absence taken at the assignment level. The original ETRM metadata lists the object status as VALID in both Oracle EBS 12.1.1 and 12.2.2, confirming that it is a supported, shipped database object in the APPS schema.

Functionally, the view presents one row per leave-taking event, exposing the assignment, the associated time period, the element reporting name under which the absence was processed, the leave start and end dates, the calculated absence duration, and the payment amount. This makes the object well suited to statutory reporting, payroll reconciliation, leave liability analysis, and any downstream integration requiring a flattened, query-ready representation of New Zealand leave data.

Underlying Base Objects

The documented ETRM metadata identifies four referenced base objects, all of which are themselves views in the APPS schema:

The view text confirms this directly. It is defined as the union of the four component views, projecting an identical set of nine columns from each. Notably, the SQL uses UNION to combine the first three components and UNION ALL to append the fourth:

SELECT ... FROM PAY_NZ_ASG_LEAVE_TAKEN_V1
UNION
SELECT ... FROM PAY_NZ_ASG_LEAVE_TAKEN_V2
UNION
SELECT ... FROM PAY_NZ_ASG_LEAVE_TAKEN_V3
UNION ALL
SELECT ... FROM PAY_NZ_ASG_LEAVE_TAKEN_V4

The distinction is material to query planning and results. The UNION operators enforce duplicate elimination and an implicit sort across the V1–V3 result set, while the final UNION ALL permits rows from V4 to be appended without deduplication. Consumers should therefore expect the possibility of duplicate-looking rows originating from the V4 branch and should not assume global uniqueness across the combined set.

Key Columns

The view exposes the following columns, identical in name and order across all four union branches:

  • ROW_ID — Identifier for the underlying source row, used for traceability back to the component view.
  • ASSIGNMENT_ID — Foreign key to the assignment (PER_ALL_ASSIGNMENTS_F) on which the leave was taken; the primary grouping key for most reporting.
  • TIME_PERIOD_ID — Identifier of the payroll time period to which the leave event is attributed.
  • ELEMENT_REPORTING_NAME — The reporting name of the payroll element representing the leave, allowing classification of leave type without joining to element definitions.
  • START_DATE / END_DATE — The effective boundaries of the absence.
  • ABSENCE_DURATION — The quantified duration of the leave, expressed in the unit defined by the underlying element.
  • PAYMENT — The monetary amount associated with the leave for the period.
  • DATE_EARNED — The date on which the leave entitlement was accrued or earned, useful for distinguishing accrual periods from utilization periods.

Common Use Cases and Queries

Typical applications include statutory leave balance reporting, reconciliation of leave payments against payroll run results, and extraction of NZ leave data into external HR or finance systems. A representative query aggregates absence and payment by assignment:

SELECT assignment_id,
       element_reporting_name,
       SUM(absence_duration) AS total_duration,
       SUM(payment) AS total_payment
FROM   apps.pay_nz_asg_leave_taken_v
WHERE  start_date BETWEEN :p_start AND :p_end
GROUP  BY assignment_id, element_reporting_name;

Because the object is a view over other views, no DML is possible; access should be granted through the standard APPS read-only privileges. When joining to assignment or person tables, the ASSIGNMENT_ID column provides the linking key, while TIME_PERIOD_ID supports correlation with payroll period definitions.