Results for “vehicle_allocation_id”

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

Overview

PQP_VEHICLE_ALLOCATIONS_F is a dated (effective-dated) table in the Oracle E-Business Suite HR schema, owned by the PQP – Public Sector Payroll product. Its documented purpose is to keep track of the association of a vehicle to an assignment. In practice, this object holds the payroll-relevant attributes that describe how a specific vehicle, sourced from the vehicle repository, is allocated to a specific assignment within a business group, and how the associated taxable benefit, contribution, and usage characteristics are to be treated. Because PQP supports public sector payroll processing, this table underpins vehicle benefit-in-kind and related earnings or deduction calculations.

The table is a _F (date-tracked) entity: it carries EFFECTIVE_START_DATE and EFFECTIVE_END_DATE as part of its primary key, enabling historical tracking of vehicle-to-assignment associations over time. The documented primary key, PQP_VEHICLE_ALLOCATIONS_F_PK, comprises VEHICLE_ALLOCATION_ID, EFFECTIVE_START_DATE, and EFFECTIVE_END_DATE; a second documented key, PQP_VEHICLE_ALLOCATIONS_PK, repeats the same column set. The ETRM metadata classifies the object heuristically as standalone within a Data Vault model, suggesting it is not a natural child-link but a discrete, self-contained satellite-like record keyed by its own identifier and effective dating. It contains 69 documented columns.

Key Information Stored

• VEHICLE_ALLOCATION_ID — surrogate identifier and the leading column of the primary key; uniquely identifies the allocation record across its effective dates.
• EFFECTIVE_START_DATE / EFFECTIVE_END_DATE — the date-tracked validity of the allocation; complete the primary key and drive as-of-date reporting.
• ASSIGNMENT_ID — the assignment to which the vehicle is allocated; the core business relationship of the row.
• BUSINESS_GROUP_ID — the business group the allocation belongs to; a standard multi-tenancy partition key in HR.
• VEHICLE_REPOSITORY_ID — references the vehicle being allocated from the vehicle repository.
• ACROSS_ASSIGNMENTS — indicates whether the vehicle allocation spans more than one assignment.
• USAGE_TYPE — categorizes how the vehicle is used for benefit calculations.
• CAPITAL_CONTRIBUTION / PRIVATE_CONTRIBUTION — the contribution amounts used in the benefit valuation.
• DEFAULT_VEHICLE / PRIVATE_USE_FLAG — flags marking default allocations and private use of the vehicle.
• FUEL_CARD / FUEL_CARD_NUMBER / FUEL_BENEFIT — fuel card details and the associated taxable fuel benefit.
• CALCULATION_METHOD / RATES_TABLE_ID / ELEMENT_TYPE_ID — the calculation method and the rates table and payroll element type used to value the benefit.
• INSURANCE_NUMBER / INSURANCE_EXPIRY_DATE / SLIDING_RATES_INFO — insurance reference data and sliding-scale rate information.
• VAL_ATTRIBUTE_CATEGORY / VAL_ATTRIBUTE1–20 / VAL_INFORMATION_CATEGORY / VAL_INFORMATION1–20 — developer descriptive flexfields for customer-specific vehicle data.
• CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, OBJECT_VERSION_NUMBER — standard WHO audit columns and optimistic-locking version.

The surrogate key is VEHICLE_ALLOCATION_ID; the date-tracked business grain is VEHICLE_ALLOCATION_ID combined with the two effective dates. No separate unique business-key index beyond the documented primary keys is indicated.

Common Use Cases and Queries

Typical reporting separates current allocations from historical ones by filtering on the effective dates. A point-in-time query pattern is:

• SELECT vehicle_allocation_id, assignment_id, vehicle_repository_id, usage_type, fuel_benefit FROM pqp_vehicle_allocations_f WHERE assignment_id = :assignment_id AND TRUNC(SYSDATE) BETWEEN effective_start_date AND effective_end_date;
• Join to the vehicle repository by vehicle_repository_id to resolve registration and vehicle details.
• Aggregate capital and private contributions by business group and period for benefit-in-kind reporting.
• Extract fuel card and fuel benefit data for taxable-benefit reconciliation.
• Audit allocation changes over time by ordering by effective_start_date per vehicle_allocation_id.

Related Objects

• Vehicle repository table — joined via VEHICLE_REPOSITORY_ID to resolve the allocated vehicle.
• Assignment table (PER_ALL_ASSIGNMENTS_F) — joined via ASSIGNMENT_ID to link the allocation to the employee assignment.
• Business group table (PER_BUSINESS_GROUPS) — joined via BUSINESS_GROUP_ID.
• Payroll element types — referenced via ELEMENT_TYPE_ID for benefit valuation.
• Rates tables — referenced via RATES_TABLE_ID for calculation rates.

These relationships are inferred from the documented column names; the FK structure is classified as standalone, so no enforced foreign keys are documented within the ETRM metadata.