Search Results value_2




Overview
Explore in AI Chat

Overview

The PAY_PDT_BATCH_LINES_V3 view is a payroll dictionary object owned by the APPS schema within the Oracle E-Business Suite Payroll (PAY) module. It resides in the payroll batch processing area associated with the Payroll Batch Element (PDT) framework, which is used to define batch element entries and their associated input values for bulk payroll processing. The view presents batch line information in a legacy-compatible layout, exposing batch and batch line identifiers alongside assignment references and a set of descriptive amount columns. Its primary architectural purpose is to reconcile a normalised input-value model to the older, denormalised column-based table definition of PAY_PDT_BATCH_LINES, thereby preserving backward compatibility for dependent forms, reports, and interfaces.

The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. The presence of the user search term value_1 is consistent with the view's internal construction: VALUE_1 through VALUE_15 are the positional input value columns that hold the actual batch line data, which are then mapped to specific logical columns according to the input name held in NAME_1 through NAME_15.

Underlying Base Objects

According to the documented view metadata, PAY_PDT_BATCH_LINES_V3 is defined over a single referenced base object: PAY_PDT_BATCH_LINES_V2, itself a view. This declared dependency indicates that V3 is a thin formatting and mapping layer that refines the row set produced by V2. In the layered EBS payroll dictionary design, the V2 layer typically handles the pivot or normalisation of the PDT batch line input values, while V3 applies the explicit NAME-to-VALUE decode logic and supplies null placeholders so that the exposed projection exactly matches the historical PAY_PDT_BATCH_LINES table definition. Downstream consumers therefore reference V3 without requiring changes to their column expectations, regardless of the underlying normalisation changes.

Key Columns

The view exposes a stable set of columns that carry both identity and decoded payroll amounts:

  • BATCH_ID — Identifier of the parent payroll batch to which the line belongs.
  • LINE_ID — Exposed as the batch line identifier; note the view aliases BATCH_LINE_ID to LINE_ID.
  • ASSIGNMENT_NUMBER — The assignment number of the employee or applicant to whom the batch line applies.
  • ADJUSTMENT_TYPE_CODE — Always null in this view, retained only for legacy layout compatibility.
  • AMT_AMOUNT — Decoded amount when the input name equals 'AMOUNT'.
  • AMT_PERCENTAGE — Decoded value when the input name equals 'PERCENTAGE'.
  • AMT_NET_AMOUNT — Decoded value when the input name equals 'NET AMOUNT'.
  • AMT_PAY_VALUE — Decoded value when the input name equals 'PAY VALUE'.
  • AMT_REPLACE_AMT — Decoded value when the input name equals 'REPLACE AMT'.

Each amount column is produced by a DECODE expression that scans NAME_1 through NAME_15, returning the matching VALUE_n (including VALUE_1) or null. Because the mapping is name-driven and positional, a given line can populate at most one of these amount columns, mirroring the original single-purpose column table.

Common Use Cases and Queries

This view is typically used to extract payroll batch element lines for reconciliation, data conversion, and custom reporting, especially where legacy SQL still references the old PAY_PDT_BATCH_LINES column set. A representative query selecting batch lines with their effective amount is shown below.

  • Reconciling batch element entries against processed payroll run results.
  • Feeding custom interfaces or extracts that expect the legacy amount column structure.
  • Auditing which input name supplied each amount for a given batch and assignment.

SELECT batch_id, line_id, assignment_number,
       amt_amount, amt_percentage, amt_net_amount,
       amt_pay_value, amt_replace_amt
 FROM apps.pay_pdt_batch_lines_v3
 WHERE batch_id = :p_batch_id
 ORDER BY line_id;

Because ADJUSTMENT_TYPE_CODE is permanently null, queries should not rely on it for filtering. Restricting by BATCH_ID or ASSIGNMENT_NUMBER is the most reliable and performant access path.