Search Results name_14




Overview
Explore in AI Chat

Overview

APPS.PAY_PDT_BATCH_LINES_V3 is a compatibility and normalization view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 Payroll product schema. It is the third iteration of a view family designed to present payroll batch line data in a horizontally pivoted format, exposing the legacy fixed-column layout of the PAY_PDT_BATCH_LINES table while the underlying storage has been migrated to a vertical (name/value pair) model. The view flattens indexed attribute pairs such as NAME_1 through NAME_15 and VALUE_1 through VALUE_15 into discrete, semantically named columns such as AMT_AMOUNT, AMT_PERCENTAGE, AMT_NET_AMOUNT, AMT_PAY_VALUE, AMT_REPLACE_AMT, and AMT_ADDL_AMT.

Its role is primarily backward compatibility. Applications, reports, and integration routines written against the original wide table definition can continue to query the same column names without modification, even though the physical data is now held in a normalized structure. This shields downstream consumers from schema changes introduced during ETRM and payroll batch processing upgrades.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view is owned by APPS and is defined over a single referenced base object: PAY_PDT_BATCH_LINES_V2 (VIEW). This direct dependency establishes a versioned chain in which V3 layers additional decoding logic on top of V2. V3 does not reference the PAY_PDT_BATCH_LINES base table directly; instead it inherits the row source and joins from V2 and then applies its own DECODE-based projection.

The governing SELECT carries the inline comment "Map value_1..value_15 to specific columns dependent on the input value name. Select further NULL columns so that the view definition matches the old table definition of pay_pdt_batch_lines." This confirms the view is deliberately engineered to satisfy the legacy interface contract of the former base table, adding NULL placeholders such as ADJUSTMENT_TYPE_CODE to preserve column parity.

Key Columns

  • BATCH_ID — Identifier of the parent payroll batch.
  • LINE_ID — Alias of BATCH_LINE_ID, the individual line within the batch.
  • ASSIGNMENT_NUMBER — The assignment (employee) reference associated with the line.
  • ADJUSTMENT_TYPE_CODE — Exposed as NULL, retained solely to match the legacy table shape.
  • AMT_AMOUNT — Decoded from the value whose NAME_n equals 'Amount'.
  • AMT_PERCENTAGE — Decoded from the value whose NAME_n equals 'Percentage'.
  • AMT_NET_AMOUNT — Decoded from the value whose NAME_n equals 'Net Amount'.
  • AMT_PAY_VALUE — Decoded from the value whose NAME_n equals 'Pay Value'.
  • AMT_REPLACE_AMT — Decoded from the value whose NAME_n equals 'Replace Amt'.
  • AMT_ADDL_AMT — Decoded from the value whose NAME_n equals 'Addl Amt'.

Each amount column is produced by a fifteen-branch DECODE over NAME_1 through NAME_15; when no name matches, the expression returns NULL. This mechanism directly explains why a search for "value_15" surfaces this object: the fifteenth value slot, VALUE_15, is the last element in every DECODE list.

Common Use Cases and Queries

Typical scenarios include batch entry validation, payroll costing extracts, and reconciliation reports that previously read the legacy table. A basic projection follows:

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

Consumers may also query PAY_PDT_BATCH_LINES_V2 or the original base table where V3's additional decoding is unnecessary. Because V3 relies on DECODE over fifteen attributes, queries filtering on NAME/VALUE semantics should target the V2 layer, while anything expecting the legacy wide-row contract should use V3.