Results for “pspbv_labor_dist_element_types”

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

Overview

PSPBV_LABOR_DIST_ELEMENT_TYPES is a read-only database view belonging to the PSP (Labor Distribution) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents information about earnings elements that originate in Oracle Human Resources and Payroll (the PAY schema) and have been imported into Oracle Labor Distribution. Because Labor Distribution must reconcile costing, effort reporting, and payroll charges against the earnings elements that drive them, this view provides a consolidated, query-friendly projection of the element definitions recognized by Labor Distribution.

The view is explicitly defined WITH READ ONLY, confirming that it exists solely for reporting, inquiry, and integration extraction. It exposes a curated subset of columns drawn from the intersection of Labor Distribution's staging table and Oracle Payroll's element definition, making it a convenient source for reports, Oracle Discoverer/EBS data model queries, and downstream interfaces that need to know which earnings elements are active in the Labor Distribution context. When a user searches for "pay_element_types," this view is the Labor Distribution-side counterpart to the PAY_ELEMENT_TYPES table, joining the two so that payroll element definitions are filtered and validated against the elements actually loaded into Labor Distribution.

Underlying Base Objects

Per the documented view text, PSPBV_LABOR_DIST_ELEMENT_TYPES is defined over two base tables:

• PSP_ELEMENT_TYPES (alias PET) — the Labor Distribution table that stores element types imported into the PSP module, including the active date range and descriptive comments specific to Labor Distribution processing.
• PAY_ELEMENT_TYPES (alias PET1) — the Oracle Payroll element type definition table, supplying the core earnings element identity and its effective-dating boundaries.

The two tables are joined on ELEMENT_TYPE_ID, and the join is further qualified by a date predicate: PET.START_DATE_ACTIVE must fall between PET1.EFFECTIVE_START_DATE and PET1.EFFECTIVE_END_DATE. This date-aware join ensures that only element types whose Labor Distribution activation date is valid within the payroll element's effective period are returned. No additional base objects are documented in the ETRM metadata. In the environment examined, the view was reported as "Not implemented in this database," which is a common ETRM notation meaning the view text exists in the reference documentation but the object may not have been deployed in that particular instance, or the metadata crawl could not resolve it.

Key Columns

• ELEMENT_TYPE_ID — the primary identifier of the earnings element type; the common key shared by PSP_ELEMENT_TYPES and PAY_ELEMENT_TYPES.
• START_DATE_ACTIVE — the date on which the element becomes active for Labor Distribution purposes; also used in the effective-dating join predicate.
• END_DATE_ACTIVE — the date on which the element's active period ends, if applicable.
• COMMENTS — descriptive text associated with the Labor Distribution element type.
• LAST_UPDATE_DATE / LAST_UPDATED_BY — audit columns recording the most recent modification and the user responsible.
• CREATED_BY / CREATION_DATE — audit columns recording the original creation user and timestamp.

Notably, the view does not project the element's name or reporting name, so consumers requiring a human-readable label must join back to PAY_ELEMENT_TYPES or the element name/translation tables.

Common Use Cases and Queries

Typical uses include validating which earnings elements have been imported into Labor Distribution, driving element selection lists in custom reports, and reconciling payroll element effective dates against Labor Distribution activation dates. A representative query lists active imported elements:

• SELECT element_type_id, start_date_active, end_date_active, comments FROM pspbv_labor_dist_element_types WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE+1) ORDER BY element_type_id;
• SELECT a.element_type_id, b.element_name, a.start_date_active, a.end_date_active FROM pspbv_labor_dist_element_types a, pay_element_types_f b WHERE a.element_type_id = b.element_type_id;
• SELECT element_type_id, last_update_date, last_updated_by, created_by, creation_date FROM pspbv_labor_dist_element_types ORDER BY last_update_date DESC;

Because the view is read-only and joins two effective-dated sources, queries should account for date-range overlaps and null end dates when interpreting results.