Results for “pay_paymix_line_insert”
28 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
APPS.PAY_PDT_BATCH_LINES is a supplementary database view registered in the Oracle E-Business Suite Applications (APPS) schema. In the ETRM metadata its status is recorded as VALID, and its FND Design Data reference is PAY.PAY_PDT_BATCH_LINES. The view is classified as a supplementary view used to simplify Forms coding, and Oracle explicitly warns that customers should not query or alter data through this object, since its definition may change dramatically in subsequent minor or major releases of the application.
The view exposes detail lines belonging to payroll batch processing activity, including adjustments, element-level entries, rates, hours, cost center information, and effective-date values. For the search term "pay_effective_date," the relevant column is PAY_EFFECTIVE_DATE, a DATE column on the view. In the context of Oracle EBS 12.1.1 and 12.2.2, this column represents the date on which a payroll line entry, rate change, adjustment, or salary-related action takes effect. It is used for date-driven processing logic and for reconciling retroactive versus prospective payroll changes, and it participates in the viewed result set rather than being stored as a standalone transactional field.
Underlying Base Objects
The documented ETRM metadata for the 12.2.2 release lists the referenced base objects for APPS.PAY_PDT_BATCH_LINES as:
- FND_NUMBER (PACKAGE)
- HR_API (PACKAGE)
- HR_LOOKUPS (VIEW)
- PAY_PDT_BATCH_LINES_V3 (VIEW)
The presence of FND_NUMBER and HR_API indicates that the view enriches the underlying batch line records with derived or formatted values generated through packaged APIs, notably number formatting and HR-related lookup resolution. HR_LOOKUPS supplies decodable lookup meanings for various coded columns, such as adjustment type, line status, rate preference, and shift type. PAY_PDT_BATCH_LINES_V3 is the primary underlying view that supplies the batch line records themselves. As a supplementary view, APPS.PAY_PDT_BATCH_LINES should be treated as an internal application-layer object, not a stable public interface, and any dependency built upon it carries a documented change risk.
Key Columns
The view exposes a broad set of columns that describe payroll batch processing lines. Notable columns include:
- BATCH_ID and LINE_ID — identifiers for the parent batch and the individual line.
- PAY_EFFECTIVE_DATE (DATE) — the effective date associated with the payroll line entry; central to date-sensitive processing and to the user search term.
- FROM_DATE and TO_DATE — the date range for which the line entry applies.
- ASSIGNMENT_NUMBER, ELEMENT_NAME, AMOUNT, HOURS_WORKED, HOURLY_RATE, RATE_MULTIPLE, NEW_SALARY, and PCNT_INCREASE — the compensation and quantity metrics of the line.
- ADJUSTMENT_TYPE_CODE, LINE_STATUS, RATE_CODE, RATING_CODE, SHIFT_TYPE, STATE_WORKED, and LOCALITY_WORKED — coded values that are typically decoded through HR_LOOKUPS.
- COST_CENTER_CODE, LABOR_DIST_CODE, COST_ALLOCATION_KEYFLEX_ID, CONCATENATED_SEGMENTS, and SEGMENT1 through SEGMENT18 — cost allocation and key flexfield segment data.
Common Use Cases and Queries
Because Oracle warns against querying the view directly, the principal practical use case is investigative or diagnostic: reviewing the underlying data and understanding how the application derives payroll batch line values, including PAY_EFFECTIVE_DATE. In a controlled, read-only environment such a test instance this view can be used to inspect effective-date behavior without altering data. A representative query is:
SELECT batch_id, line_id, assignment_number, element_name, amount, pay_effective_date, line_status FROM apps.pay_pdt_batch_lines WHERE pay_effective_date BETWEEN :start_date AND :end_date AND line_status = :status;
A second scenario joins the view to HR_LOOKUPS to resolve coded values:
SELECT l.line_id, l.pay_effective_date, l.adjustment_type_code, k.meaning FROM apps.pay_pdt_batch_lines l, apps.hr_lookups k WHERE l.adjustment_type_code = k.lookup_code AND k.lookup_type = :lookup_type;
Where a supported, long-term interface is required, the underlying base objects and public APIs must be used instead of APPS.PAY_PDT_BATCH_LINES, and any solution depending on this view must be revalidated against each 12.1.1 or 12.2.2 patch level in accordance with Oracle's stated change warning.
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
SYNONYM: APPS.FND_SESSIONS 12.1.1
-
SYNONYM: APPS.FND_SESSIONS 12.2.2
-
VIEW: APPS.HR_LOCATIONS 12.1.1
-
VIEW: APPS.HR_LOCATIONS 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.
-
eTRM - PER Tables and Views 12.1.1
Table to store NQF Training info for a person
-
eTRM - PAY Tables and Views 12.1.1
Temporary table used to hold invalid location addresses.