Search Results iv_seq




Overview
Explore in AI Chat

Overview

PAY_PDT_BATCH_LINES_V2 is a VALID view owned by the APPS schema within the PAY (Payroll) product family of Oracle E-Business Suite, and it is documented against both EBS 12.1.1 and 12.2.2. The view serves as the presentation layer for batch line data used by the Payroll Batch Loader and related payroll processes. Its essential function, as stated in the embedded view comment, is to pivot the result set produced by its predecessor view so that all input value names belonging to each element are returned on a single row. Rather than emitting one row per input value, PAY_PDT_BATCH_LINES_V2 aggregates the value names into fixed, position-indexed columns, producing a wide, flat structure suitable for reporting, extract generation, and downstream integration.

Underlying Base Objects

ETRM 12.2.2 metadata records a single referenced base object for this view: PAY_PDT_BATCH_LINES_V1, itself a view. PAY_PDT_BATCH_LINES_V2 is therefore the second stage of a two-tier view chain, consuming the row-per-input-value output of V1 and applying a pivot transformation. The pivot is implemented with MAX(DECODE(IV_SEQ, n, NAME, NULL)) expressions, where IV_SEQ identifies the ordinal position of an input value and NAME carries the value name. This produces the derived columns NAME_1 through NAME_14, and the pattern extends further in the same manner. No base tables are referenced directly, so all object-level dependencies resolve through V1.

Key Columns

The view exposes a broad set of identifying, descriptive, and flexfield columns from the V1 result set, alongside the pivoted input value names.

Common Use Cases and Queries

Because the view returns one row per batch line with all element input names flattened into positional columns, it is well suited to reconciliation and extract reports that must display element inputs side by side. Typical scenarios include reviewing payroll batch loader entries before submission, exporting batch line content for third-party payroll interfaces, and validating that input names appear in the expected sequence positions.

A basic query returning the identity and status of each batch line, together with the first few input names, might read:

  • SELECT batch_id, batch_line_id, element_name, batch_line_status, name_1, name_2, name_3, value_1, value_2, value_3 FROM apps.pay_pdt_batch_lines_v2 WHERE batch_id = :p_batch_id;
  • SELECT batch_line_id, assignment_number, effective_date, entry_type, reason, concatenated_segments FROM apps.pay_pdt_batch_lines_v2 WHERE batch_line_status = :p_status AND legislation_code = :p_legislation ORDER BY batch_sequence;
  • SELECT element_name, COUNT(*) FROM apps.pay_pdt_batch_lines_v2 WHERE business_group_id = :p_bg GROUP BY element_name;

Queries should filter on BATCH_ID or BUSINESS_GROUP_ID where possible to constrain the result set, since the view's wide row shape and underlying pivot make full scans expensive on large payroll volumes.