Results for “subline_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

PSPBV_PAYROLL_SUB_LINES is a read-only Oracle EBS view belonging to the PSP (Labor Distribution) product family. According to the ETRM metadata, it "displays information about Oracle sublines or non-Oracle payroll sublines." In the context of Oracle EBS 12.1.1 and 12.2.2, the view acts as a reporting and integration surface that exposes the payroll subline detail underlying Labor Distribution processing. A payroll line typically represents a consolidated payroll run or assignment-level transaction, while each subline captures the granular component — a specific period, rate, salary figure, or employment segment — that contributes to the parent line.

The view is particularly relevant to users searching on current_salary. It exposes a CURRENT_SALARY column that carries the salary value in effect for the subline segment, which is fundamental to labor cost allocation, effort reporting, and reconciliation of distributed payroll charges. Because the view is defined WITH READ ONLY, it is intended strictly for query, reporting, and downstream integration rather than for transactional updates.

Underlying Base Objects

The documented view text shows that PSPBV_PAYROLL_SUB_LINES is defined over a single base table, PSP_PAYROLL_SUB_LINES (aliased PPS). Every column in the SELECT list maps directly to a column on that table, with no joins, unions, or aggregations. The metadata records "Referenced base objects: none documented," and the ETRM note states the view is "Not implemented in this database," meaning it is a seeded, shipped definition whose runtime availability depends on the PSP schema being installed and licensed.

The WHERE clause is notable: it applies a security filter, '_SEC:PPS.ORGANIZATION_ID' IS NOT NULL. This construct enforces organization-level (business group / HR security) row filtering, so results are restricted to organizations the querying user is authorized to see. A WITH READ ONLY clause reinforces that no DML is permitted. Additionally, the reason code column is decorated with a lookup translation directive referencing PSP_LOOKUPS (lookup type PSP_SUBLINE_REASONS) so that a meaning is derived from the stored lookup code.

Key Columns

• SUBLINE_ID / PAYROLL_SUB_LINE_ID — Primary identifier for each payroll subline record.
• SUBLINE_START_DATE / SUBLINE_END_DATE — The effective date span the subline covers.
• CURRENT_SALARY — The salary in effect for the subline, central to salary-based cost distribution and the column most relevant to the "current_salary" search.
• SUBLINE_SALARY_AMOUNT (SALARY_USED) — The salary amount applied when distributing the payroll cost.
• SUBLINE_AMOUNT (PAY_AMOUNT) — The monetary value of the subline.
• SUBLINE_DAILY_RATE (DAILY_RATE) — The daily rate used in proration calculations.
• FULL_TIME_EQUIVALENT (FTE) — FTE fraction used to apportion costs.
• REASON_CODE — Lookup-driven code (PSP_SUBLINE_REASONS) explaining the subline.
• EMPLOYMENT_BEGIN/END_DATE, EMPLOYMENT_STATUS_ACTIVE/INACTIVE_DATE — Employment lifecycle dates used to validate charge periods.
• ASSIGNMENT_BEGIN/END_DATE — Assignment effective dates.
• ORGANIZATION_ID, JOB_ID, POSITION_ID — Organizational and assignment attributes; ORGANIZATION_ID drives security.
• PAYROLL_LINE_ID — Links the subline to its parent payroll line.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE.

Common Use Cases and Queries

Typical uses include reconciling distributed labor costs, auditing salary rates applied during a payroll period, and extracting subline detail to a data warehouse. A representative query retrieving salary-relevant sublines is:

SELECT subline_id, subline_start_date, subline_end_date,
       current_salary, subline_salary_amount, full_time_equivalent,
       organization_id, job_id, position_id, payroll_line_id
FROM   pspbv_payroll_sub_lines
WHERE  organization_id = :org_id
AND    subline_start_date >= :from_date
ORDER BY subline_start_date;

Because ORGANIZATION_ID is security-filtered, callers need not add explicit org predicates for row-level security, though adding them improves performance. To trace a subline back to its line, join on PAYROLL_LINE_ID. All access should remain read-only, consistent with the view's WITH READ ONLY definition.