Search Results vol_ded_proc_ovd




Overview
Explore in AI Chat

Overview

PAY_PDT_BATCH_LINES is an APPS-owned view in the Oracle E-Business Suite Payroll (PAY) module. It serves as a reporting and integration layer over payroll batch line data, exposing the contents of the underlying PAY_PDT_BATCH_LINES_V3 view alongside decoded lookup values and numerically converted attributes. In EBS 12.1.1 and 12.2.2 the view is registered as VALID in the APPS schema and is primarily consumed by payroll batch processing, element entry generation, and interface/reporting logic that must present batch line attributes in a normalized, query-friendly form.

The view exists because payroll batch lines store several attributes as developer-meaningful lookup codes and multiple alternative amount columns, which are impractical for direct reporting. PAY_PDT_BATCH_LINES resolves lookup meanings back into codes and collapses the several mutually exclusive amount columns into a single AMOUNT value, producing a stable projection for downstream consumers.

Underlying Base Objects

According to the documented 12.2.2 metadata, PAY_PDT_BATCH_LINES is defined over the following referenced base objects:

All HR_LOOKUPS joins are outer joins (indicated by the (+) syntax) and are constrained by lookup type, such as LOOKUP_TYPE = 'YES_NO' for the YES/NO flag columns.

Key Columns

Common Use Cases and Queries

The view is typically used to report or feed payroll batch activity, particularly to obtain hours worked, rates, and decoded flags without replicating the conversion logic. A representative query selecting hours-related data is:

  • SELECT batch_id, line_id, assignment_number, element_name, hours_worked, hourly_rate, amount, from_date, to_date FROM apps.pay_pdt_batch_lines WHERE hours_worked IS NOT NULL;
  • Filtering by batch: ... WHERE batch_id = :batch_id to retrieve all lines for a given payroll batch.
  • Flag decoding: selecting INC_ASC_BALANCE, SEPARATE_CHECK_FLAG, or TAX_SEPARATELY_FLAG to return the YES/NO lookup code rather than the stored meaning.
  • Costing extracts: selecting CONCATENATED_SEGMENTS and the SEGMENTn columns for cost allocation reporting.

Because HOURS_WORKED is exposed already canonicalized to a number, reports can aggregate directly, for example SUM(hours_worked) grouped by assignment_number or batch_id, without additional conversion.