Results for “pqp_veh_alloc_extra_info”

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

Overview

PQP_VEH_ALLOC_EXTRA_INFO is a Public Sector Payroll (PQP) table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores supplemental or "extra" information attached to a Vehicle Allocation record, functioning as a descriptive intersection between PQP_VEHICLE_ALLOCATION_F and PQP_VEH_ALLOC_INFO_TYPES. Rather than holding a fixed set of vehicle-assignment attributes, it captures user-defined and flexfield-based detail that is categorized by an information type, allowing organizations to attach an arbitrary number of labeled data elements to a single allocation without altering the base allocation table. The object is registered as VALID in the ETRM repository and documents 65 physical columns.

The supplied relationship metadata classifies this object heuristically as standalone under a Data Vault model. That classification is a modeling suggestion only; a stricter reading of its structure — a surrogate key, a foreign key to the parent allocation, and a set of descriptive attributes — is consistent with a satellite or link pattern. Because the documented key structure exposes only a single-column primary key with no additional unique constraints, no natural business key is enforced at the database level.

Key Information Stored

The primary key is PQP_VEH_ALLOC_EXTRA_INFO_PK, defined on the VEH_ALLOC_EXTRA_INFO_ID surrogate column. This is the only documented unique index, so it is the sole candidate for a business key, and it is generated rather than meaningful. The two structural columns that carry business meaning are VEHICLE_ALLOCATION_ID, which points back to the owning allocation, and INFORMATION_TYPE, which points to the applicable information type definition.

• VEH_ALLOC_EXTRA_INFO_ID — Surrogate primary key, populated from the PQP_VEH_ALLOC_EXTRA_INFO_PK sequence.
• VEHICLE_ALLOCATION_ID — Foreign key linking the row to a single vehicle allocation record.
• INFORMATION_TYPE — Identifier of the information type that gives meaning to the row.
• VAEI_INFORMATION_CATEGORY / VAEI_INFORMATION1–30 — Descriptive flexfield segments holding the actual extra data values.
• VAEI_ATTRIBUTE_CATEGORY / VAEI_ATTRIBUTE1–20 — Context-sensitive descriptive flexfield attributes.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the concurrent framework.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — Standard WHO audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — Concurrent program traceability columns.

Common Use Cases and Queries

The most frequent access pattern is retrieval of all extra information for a given allocation, typically joining to the type definition to obtain labels. Reporting queries commonly filter on INFORMATION_TYPE to isolate a specific data element across allocations.

• Listing extra details for one allocation: SELECT * FROM pqp_veh_alloc_extra_info WHERE vehicle_allocation_id = :p_alloc_id;
• Joining to types for readable output: SELECT e.vehicle_allocation_id, t.information_type, e.vaei_information1 FROM pqp_veh_alloc_extra_info e, pqp_veh_alloc_info_types t WHERE e.information_type = t.information_type;
• Auditing changes: filtering on last_update_date and last_updated_by to trace modifications.
• Bulk extraction: driving from request_id or program_id to identify rows created by a specific payroll process.

Related Objects

• PQP_VEHICLE_ALLOCATION_F — Parent allocation entity; joined on VEHICLE_ALLOCATION_ID.
• PQP_VEH_ALLOC_INFO_TYPES — Information type definitions; joined on INFORMATION_TYPE.
• FND_DESCR_FLEX_COL_USAGE_VL / FND_DESCRIPTIVE_FLEXS — Flexfield metadata for VAEI_INFORMATION and VAEI_ATTRIBUTE segments.
• FND_FLEX_VALUES_VL — Value sets referenced by the descriptive flexfield segments.
• Standard WHO audit views and the PQP vehicle allocation concurrent programs that populate the REQUEST_ID and PROGRAM_ID columns.