Results for “hr_org_classifications”

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

Overview

APPS.PQP_VEHICLE_TEMPLATE_V is a supplementary Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as PQP.PQP_VEHICLE_TEMPLATE_V. It exposes vehicle template definitions that are stored against Oracle Payroll element types, allowing a vehicle-type element to be presented as a reusable template with an associated classification, legislation, and effective dating. The object is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and the metadata is identical across those releases. The view is classified as a supplementary view used to simplify forms coding, and Oracle explicitly warns that it should not be queried or altered directly, since its definition may change dramatically in subsequent minor or major releases. Its practical role is therefore presentation-layer: it supports the Oracle Payroll vehicle-related forms and any downstream reporting that must reconcile vehicle element definitions with HR organization classifications. Because the view is referenced publicly as PUBLIC.PQP_VEHICLE_TEMPLATE_V, it can be selected from PL/SQL and BI Publisher reports, but consumers should treat the column list as unstable and guard against changes during patching.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through synonyms in the APPS schema:

• PAY_ELEMENT_TYPES_F — the core Payroll element type definition table, supplying ELEMENT_TYPE_ID, BUSINESS_GROUP_ID, LEGISLATION_CODE, ELEMENT_NAME, REPORTING_NAME, and the effective date range.
• PAY_ELEMENT_TYPE_EXTRA_INFO — the attribute/extra-information table that stores vehicle-specific detail such as VEHICLE_TYPE and the CLASSIFICATION_ID link.
• FND_SESSIONS — the session table used to restrict rows to the current Business Group and session context, a standard pattern in Oracle HRMS forms-support views.

The view does not itself store data; it derives its rows by joining the element type definition with its extra information and filtering on the active FND session. Any insert, update, or delete attempted against the view is unsupported, and changes must be made through the underlying Payroll element APIs and the corresponding vehicle template form.

Key Columns

The view exposes fifteen columns. The structural identifiers are ELEMENT_TYPE_ID (primary key of the base element type) and BUSINESS_GROUP_ID, which is the foreign key to HR_ALL_ORGANIZATION_UNITS and scopes the template to a specific Business Group. CLASSIFICATION_ID is the foreign key to HR_ORG_CLASSIFICATIONS — this is the column that answers the common search for "hr_org_classifications" in the context of this view, linking the vehicle template to an organization classification used for reporting and grouping. LEGISLATION_CODE holds the legislation under which the element is defined. Descriptive columns include ELEMENT_NAME, DESCRIPTION, REPORTING_NAME, and VEHICLE_TYPE, the latter describing the vehicle classification recorded on the template. EFFECTIVE_START_DATE and EFFECTIVE_END_DATE provide the date-tracked validity of the template, while LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, and CREATION_DATE are the standard WHO audit columns.

Common Use Cases and Queries

Typical usage includes auditing which vehicle templates exist per Business Group and legislation, reconciling templates against HR organization classifications, and feeding vehicle-related cost reporting. A representative query listing active templates with their classification is:

• SELECT element_name, vehicle_type, classification_id, legislation_code, effective_start_date, effective_end_date FROM apps.pqp_vehicle_template_v WHERE business_group_id = :p_bg_id AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
• SELECT v.element_name, v.vehicle_type, c.classification_name FROM apps.pqp_vehicle_template_v v, hr_org_classifications c WHERE v.classification_id = c.classification_id ORDER BY v.element_name;

Reports should join CLASSIFICATION_ID to HR_ORG_CLASSIFICATIONS rather than querying HR_ALL_ORGANIZATION_UNITS directly, and should always filter on BUSINESS_GROUP_ID to respect multi-organization security. Given the documented instability warning, production code should encapsulate these queries in a wrapper view or PL/SQL package so that any redefinition of PQP_VEHICLE_TEMPLATE_V in a future release can be absorbed without impacting downstream consumers.