Search Results pay_pdt_batch_lines_v1
Overview
PAY_PDT_BATCH_LINES_V1 is a read-only database view owned by the APPS schema in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It belongs to the PAY — Payroll product family and is registered as VALID in the ETRM object repository. The view presents a flattened, query-friendly projection of payroll batch lines by joining element input values to the batch line records that consume them. Its primary purpose is to expose, in a single relational structure, the fifteen generic input value slots (VALUE_1 through VALUE_15) that Oracle Payroll stores against a batch line, alongside the descriptive input value name and the parent element type.
The view text carries an explicit inline comment — designated as a "FIRST CREATE A VIEW" construct — indicating that it was designed to display an element's input values in the same positional order as they are held in PAY_BATCH_LINES, i.e. VALUE_1 to VALUE_15. This makes the view particularly useful where positional alignment between the input value definition and the stored value column must be preserved. It is principally consumed by reporting, extracts, and integration interfaces that need element-type context for each payroll batch line without directly navigating the underlying transactional tables.
Underlying Base Objects
The ETRM metadata documents that PAY_PDT_BATCH_LINES_V1 is defined over the following referenced base objects, all of which are accessed through APPS schema synonyms except where noted:
- PAY_BATCH_HEADERS (SYNONYM) — supplies the business group and batch-level context.
- PAY_BATCH_LINES (SYNONYM) — the central transactional table holding each payroll batch line, including the VALUE_1 through VALUE_15 slots, segment columns, cost allocation keyflex, entry type, and status.
- PAY_ELEMENT_TYPES_F (SYNONYM) — provides element type metadata, including the element name, element type ID, and legislation code.
- PAY_INPUT_VALUES_F (SYNONYM) — provides the input value name and definition associated with each element type.
- PER_BUSINESS_GROUPS (VIEW) — resolves the business group identifier into its descriptive form.
The view text shows an inner query that selects from element types, input values, batch headers, and batch lines, and an outer query that applies a ROWNUM-based sequence calculation (ROWNUM minus a correlated minimum rownum, plus one) to derive an input value sequence column (IV_SEQ). This sequencing ensures each batch line's input values are numbered consistently.
Key Columns
The view exposes a broad column set drawn from the joined base objects. Significant columns include:
- IV_SEQ — the derived input value sequence number, computed from ROWNUM arithmetic to preserve positional order.
- NAME — the input value name from PAY_INPUT_VALUES_F.
- ELEMENT_NAME / ELEMENT_TYPE_ID — identifies the payroll element to which the batch line belongs.
- LEGISLATION_CODE — the legislative context of the element type.
- BATCH_LINE_ID / BATCH_ID — primary and foreign keys linking to the batch structure.
- ASSIGNMENT_ID / ASSIGNMENT_NUMBER — the assignment to which the line applies.
- BATCH_LINE_STATUS, BATCH_SEQUENCE, ENTRY_TYPE, REASON — line state and processing attributes.
- EFFECTIVE_DATE, CONCATENATED_SEGMENTS, COST_ALLOCATION_KEYFLEX_ID — date-effective and costing context.
- SEGMENT1–SEGMENT30 — the element's segment columns.
- VALUE_1–VALUE_15 — the generic input value slots held positionally on the batch line.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE20 — descriptive flexfield context and values.
Common Use Cases and Queries
Typical use cases include payroll batch reconciliation reports, input value validation extracts, and integration feeds that require element and assignment context for each batch line. A representative query might retrieve all input values for a given batch, ordered by the derived sequence:
- Filtering by BATCH_ID to review all lines and their input values for a single payroll batch.
- Joining to PAY_BATCH_HEADERS on BATCH_ID to attach batch status and business group details.
- Grouping by ELEMENT_NAME and NAME to analyse how a particular input value is populated across assignments.
Example SQL:
SELECT batch_line_id, element_name, name, iv_seq, value_1, value_2, value_3
FROM apps.pay_pdt_batch_lines_v1
WHERE batch_id = :p_batch_id
ORDER BY batch_line_id, iv_seq;
Because the view is owned by APPS and marked VALID, it can be referenced directly in custom concurrent programs, BI Publisher data templates, and OBIEE/OTBI integrations with the standard APPS credentials, subject to the appropriate grants.
-
View: PAY_PDT_BATCH_LINES_V1
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_PDT_BATCH_LINES_V1, object_name:PAY_PDT_BATCH_LINES_V1, status:VALID, product: PAY - Payroll , implementation_dba_data: APPS.PAY_PDT_BATCH_LINES_V1 ,
-
View: PAY_PDT_BATCH_LINES_V1
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_PDT_BATCH_LINES_V1, object_name:PAY_PDT_BATCH_LINES_V1, status:VALID, product: PAY - Payroll , implementation_dba_data: APPS.PAY_PDT_BATCH_LINES_V1 ,
-
SYNONYM: PUBLIC.PAY_PDT_BATCH_LINES_V1
12.1.1
owner:PUBLIC, object_type:SYNONYM, object_name:PAY_PDT_BATCH_LINES_V1, status:VALID,
-
SYNONYM: APPS.PAY_BATCH_LINES
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PAY_BATCH_LINES, status:VALID,
-
VIEW: APPS.PAY_PDT_BATCH_LINES_V2
12.1.1
-
SYNONYM: APPS.PAY_BATCH_LINES
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PAY_BATCH_LINES, status:VALID,
-
VIEW: APPS.PAY_PDT_BATCH_LINES_V1
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_PDT_BATCH_LINES_V1, object_name:PAY_PDT_BATCH_LINES_V1, status:VALID,
-
SYNONYM: APPS.PAY_BATCH_HEADERS
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PAY_BATCH_HEADERS, status:VALID,
-
VIEW: APPS.PAY_PDT_BATCH_LINES_V2
12.2.2
-
SYNONYM: APPS.PAY_BATCH_HEADERS
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PAY_BATCH_HEADERS, status:VALID,
-
View: PAY_PDT_BATCH_LINES_V2
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_PDT_BATCH_LINES_V2, object_name:PAY_PDT_BATCH_LINES_V2, status:VALID, product: PAY - Payroll , implementation_dba_data: APPS.PAY_PDT_BATCH_LINES_V2 ,
-
View: PAY_PDT_BATCH_LINES_V2
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_PDT_BATCH_LINES_V2, object_name:PAY_PDT_BATCH_LINES_V2, status:VALID, product: PAY - Payroll , implementation_dba_data: APPS.PAY_PDT_BATCH_LINES_V2 ,
-
VIEW: APPS.PAY_PDT_BATCH_LINES_V2
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_PDT_BATCH_LINES_V2, object_name:PAY_PDT_BATCH_LINES_V2, status:VALID,
-
VIEW: APPS.PAY_PDT_BATCH_LINES_V2
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_PDT_BATCH_LINES_V2, object_name:PAY_PDT_BATCH_LINES_V2, status:VALID,
-
VIEW: APPS.PAY_PDT_BATCH_LINES_V1
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PAY.PAY_PDT_BATCH_LINES_V1, object_name:PAY_PDT_BATCH_LINES_V1, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
12.2.2 DBA Data
12.2.2
-
12.2.2 FND Design Data
12.2.2
-
12.1.1 FND Design Data
12.1.1
-
12.1.1 DBA Data
12.1.1
-
SYNONYM: APPS.PAY_INPUT_VALUES_F
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PAY_INPUT_VALUES_F, status:VALID,
-
SYNONYM: APPS.PAY_INPUT_VALUES_F
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PAY_INPUT_VALUES_F, status:VALID,
-
SYNONYM: APPS.PAY_ELEMENT_TYPES_F
12.1.1
owner:APPS, object_type:SYNONYM, object_name:PAY_ELEMENT_TYPES_F, status:VALID,
-
SYNONYM: APPS.PAY_ELEMENT_TYPES_F
12.2.2
owner:APPS, object_type:SYNONYM, object_name:PAY_ELEMENT_TYPES_F, status:VALID,
-
VIEW: APPS.PER_BUSINESS_GROUPS
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:PER.PER_BUSINESS_GROUPS, object_name:PER_BUSINESS_GROUPS, status:VALID,
-
VIEW: APPS.PER_BUSINESS_GROUPS
12.2.2
owner:APPS, object_type:VIEW, fnd_design_data:PER.PER_BUSINESS_GROUPS, object_name:PER_BUSINESS_GROUPS, status:VALID,
-
eTRM - PAY Tables and Views
12.1.1
description: Temporary table used to hold invalid location addresses. ,
-
12.2.2 DBA Data
12.2.2
-
12.1.1 DBA Data
12.1.1
-
eTRM - PAY Tables and Views
12.2.2
description: Temporary table used to hold invalid location addresses. ,
-
eTRM - PER Tables and Views
12.1.1
description: Table to store NQF Training info for a person ,
-
eTRM - PAY Tables and Views
12.1.1
description: Temporary table used to hold invalid location addresses. ,
-
eTRM - PAY Tables and Views
12.2.2
description: Temporary table used to hold invalid location addresses. ,
-
eTRM - PER Tables and Views
12.1.1
description: Table to store NQF Training info for a person ,