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 APPS.PAY_AU_ASG_LEAVE_TAKEN_V view is a payroll reporting object delivered with the Oracle E-Business Suite Payroll (PAY) product, specifically supporting the Australian localization. It consolidates leave-taken information associated with employee assignments, exposing absence hours and the associated payment amounts recorded against payroll elements. The view is registered in the APPS schema with a status of VALID and is documented under ETRM 12.2.2, and its definition is unchanged between releases 12.1.1 and 12.2.2. Its role is to provide a flattened, query-ready presentation of Australian leave balances and payments so that reporting, reconciliation, and downstream integration tools can retrieve leave-taken data without reconstructing the multiple membership logic embedded in the constituent views.

Underlying Base Objects

The view is defined as a UNION of multiple component views rather than directly against base tables. The documented view text selects the same eight columns from PAY_AU_ASG_LEAVE_TAKEN_V1, PAY_AU_ASG_LEAVE_TAKEN_V2, and PAY_AU_ASG_LEAVE_TAKEN_V3 using UNION, and from PAY_AU_ASG_LEAVE_TAKEN_V4 and PAY_AU_ASG_LEAVE_TAKEN_V5 using UNION ALL. This distinction is significant: the UNION branches suppress duplicate rows across those sources, whereas the UNION ALL branches retain all qualifying rows, which is important when the same assignment and time period combinations legitimately appear more than once. The documented referenced base objects also list PAY_AU_ASG_LEAVE_TAKEN_V6, PAY_AU_ASG_LEAVE_TAKEN_V7, and the PAY_AU_SOE_PKG package, indicating that the component views are themselves dependent on further localized views and on the Australian Start of Year/End of Year processing package that populates and validates the statutory leave data.

Key Columns

The view exposes eight columns. ROW_ID is a unique surrogate identifier for each returned row and is typically used as the primary key when the view is consumed by Oracle Forms or by integration frameworks requiring a row identifier. ASSIGNMENT_ID identifies the assignment (the employee's placement in a position) against which the leave was taken; it is the principal join key to PAY_ASSIGNMENT_ACTIONS and per_all_assignments_f. TIME_PERIOD_ID links the row to a payroll time period, which is the column most commonly used in queries, since it allows filtering by period and joining to the PER_TIME_PERIODS table for period name, start date, and end date. ELEMENT_REPORTING_NAME holds the reporting name of the payroll element under which the absence or payment was recorded, distinguishing leave types such as annual leave, personal leave, or paid leave loading. START_DATE and END_DATE bound the absence interval, ABSENCE_HOURS quantifies the leave taken, and PAYMENT holds the monetary amount associated with the leave entry.

Common Use Cases and Queries

Typical usage includes reconciling leave taken against timecard entries, extracting leave and payment detail for statutory reporting, and supplying external systems with assignment-level absence data. Because TIME_PERIOD_ID is the column most often searched, a common query filters by a specific period and joins to the time period definition:

  • SELECT v.ASSIGNMENT_ID, v.ELEMENT_REPORTING_NAME, v.START_DATE, v.END_DATE, v.ABSENCE_HOURS, v.PAYMENT FROM APPS.PAY_AU_ASG_LEAVE_TAKEN_V v WHERE v.TIME_PERIOD_ID = :p_time_period_id ORDER BY v.ASSIGNMENT_ID, v.START_DATE;
  • Joining PER_TIME_PERIODS on TIME_PERIOD_ID to resolve the period name and payroll for a given reporting window.
  • Aggregating ABSENCE_HOURS and PAYMENT by ASSIGNMENT_ID and ELEMENT_REPORTING_NAME to produce leave-taken summaries per employee.
  • Filtering by START_DATE and END_DATE to isolate a date range of absences regardless of the period in which they were paid.

When querying, note that the UNION branches remove duplicates while the UNION ALL branches do not, so aggregation totals should account for potential repeated rows from the UNION ALL sources.