Results for “pqp_veh_alloc_info_types”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
PQP_VEH_ALLOC_INFO_TYPES is an Oracle E-Business Suite configuration table owned by the HR schema and belonging to the PQP (Public Sector Payroll) product family. It serves as the reference entity that defines the categories of supplementary information collected for vehicle allocation records. In public sector deployments, employees assigned a government vehicle must report additional attributes — such as odometer readings, fuel card data, or commuting declarations — and this table enumerates the permitted information types those supplemental records may carry.
The table is a low-volume, setup-style reference object rather than a transactional one. Rows are typically seeded or maintained by the implementation team during configuration and change infrequently thereafter. The ACTIVE_INACTIVE_FLAG and MULTIPLE_OCCURENCES_FLAG columns give administrators runtime control over which information types are available and whether a given allocation may hold more than one value of that type.
Metadata mining of the foreign-key structure classifies this object as standalone under the heuristic Data Vault model — that is, it behaves as an independent reference hub of information types rather than as a dependent satellite or a resolving link. This classification is a modeling suggestion only; in relational terms the table is a simple lookup keyed by INFORMATION_TYPE.
Key Information Stored
The documented physical schema comprises twelve columns. The most significant are:
INFORMATION_TYPE— the business identifier and part of the composite primary key; the coded name of the extra-information category.ZD_EDITION_NAME— the editioning discriminator, also part of the primary key (PQP_VEH_ALLOC_INFO_TYPES_PK), supporting Oracle EBS online patching in 12.2.2.ACTIVE_INACTIVE_FLAG— controls whether the information type is selectable on vehicle allocation screens.MULTIPLE_OCCURENCES_FLAG— determines whether an allocation may record more than one instance of this information type.DESCRIPTION— the user-facing label displayed in forms and reports.LEGISLATION_CODE— restricts the information type to a specific legislative context, enabling country-specific configuration.OBJECT_VERSION_NUMBER— optimistic locking column used by the Oracle Applications Framework (OAF) to detect concurrent updates.LAST_UPDATE_DATE,LAST_UPDATED_BY,LAST_UPDATE_LOGIN,CREATED_BY,CREATION_DATE— the standard WHO audit columns tracking row provenance.
The surrogate primary key is defined on the composite of INFORMATION_TYPE and ZD_EDITION_NAME; there is no separate numeric surrogate. The unique index PQP_VEH_ALLOC_INFO_TYPES_PK therefore doubles as the business-key candidate, enforcing uniqueness of each information type per edition.
Common Use Cases and Queries
Configuration reporting is the primary use case: listing active information types, auditing legislative coverage, or identifying types that permit multiple occurrences.
A typical validation query returns the lookup set for a given legislation:
SELECT information_type, description FROM hr.pqp_veh_alloc_info_types WHERE active_inactive_flag = 'Y' AND legislation_code = :p_leg ORDER BY information_type;
Administrators frequently audit for duplicates or stale rows across editions:
SELECT information_type, zd_edition_name, last_update_date FROM hr.pqp_veh_alloc_info_types WHERE zd_edition_name = 'ORA$BASE' ORDER BY 1;
The MULTIPLE_OCCURENCES_FLAG is commonly extracted into control logic that governs whether the dependent allocation-detail form permits one or many entries per vehicle. Reporting tools join this table to vehicle allocation transaction tables to render friendly descriptions in place of the raw INFORMATION_TYPE code.
Related Objects
The mined relationship data classifies this table as standalone, so no foreign keys are documented from it. Child tables that consume the information types logically include:
PQP_VEH_ALLOC_INFO(vehicle allocation extra information records) — joins onINFORMATION_TYPEandZD_EDITION_NAMEto retrieve permitted values.- Vehicle allocation headers
PQP_VEHICLE_ALLOCATIONS— the parent transaction to which information types apply. FND_LOOKUP_VALUES— frequently cross-referenced where flags or legislation codes are stored as lookup meanings.HR_LEGAL_ENTITIES/FND_TERRITORIES— used to validate or displayLEGISLATION_CODE.FND_APPLICATION— resolves the PQP application identity for access and menu configuration.
Because the table is edition-enabled, DML should always include ZD_EDITION_NAME in predicates to avoid selecting rows from superseded editions during online patching.
-
Entity used to store the information types for vehicle allocation extra information.
-
Entity used to store the information types for vehicle allocation extra information.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 FND Design Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
View: PER_INFO_TYPES_V 12.1.1
Used to support user interface
APPS.PER_INFO_TYPES_V·↳ BEN_ABR_INFO_TYPES·↳ BEN_ELP_INFO_TYPES·↳ BEN_LER_INFO_TYPES·Explore PER module →
-
12.1.1 DBA Data 12.1.1
-
View: PER_INFO_TYPES_V 12.2.2
Used to support user interface
APPS.PER_INFO_TYPES_V·↳ BEN_ABR_INFO_TYPES·↳ BEN_ELP_INFO_TYPES·↳ BEN_LER_INFO_TYPES·Explore PER module →
-
VIEW: APPS.PER_INFO_TYPES_V 12.2.2
-
VIEW: APPS.PER_INFO_TYPES_V 12.2.2
-
VIEW: APPS.PER_INFO_TYPES_V 12.1.1
-
VIEW: APPS.PER_INFO_TYPES_V 12.1.1
-
This entity is used to store any extra information regarding a Vehicle Allocation. This is an intersection table between PQP_VEHICLE_ALLOCATION_F and PQP_VEH_ALLOC_INFO_TYPES.