Search Results driver_type




Overview
Explore in AI Chat

Overview

APPS.PA_EXT_DRIVERS_V is a consolidated extension driver view in Oracle EBS Projects (PA). It presents the set of driver values that downstream costing, budgeting, and integration processes use to determine which cost or rate rules apply to a given transaction. Rather than maintaining separate lookups for each driver family, the view unions four distinct driver dimensions into a single, uniform result set keyed by a DRIVER_TYPE discriminator column. Each row carries a driver type, a human-readable driver name, a numeric driver identifier, and a description.

Because it normalizes heterogeneous sources into one shape, the view is well suited for reporting on and validating the driver values that populate Projects setup. It is commonly referenced by external systems, interfaces, and discovery queries that need to enumerate available class categories, class codes, task types, and project types through a single database object. The view is owned by APPS and is documented under ETRM for both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined as a four-way UNION ALL-style union over the following documented base objects:

The referenced objects list also notes PA_INSTALL (package). Because the driver set is installation-sensitive, this package supplies the installation context used to constrain the driver values returned. Each union branch selects a literal string as DRIVER_TYPE, a name or concatenation as DRIVER_NAME, the corresponding primary key as DRIVER_ID, and the source DESCRIPTION column.

Key Columns

  • DRIVER_TYPE — Character literal identifying the driver family. Documented values are 'CLASS_CATEGORY', 'CLASS_CODE', 'TASK_TYPE', and 'PROJECT_TYPE'. This is the column most relevant to the search term, since it is the discriminator users filter on.
  • DRIVER_NAME — Display name of the driver. For class codes, the value is composed by concatenating the class category and class code (for example, CATEGORY-CODE); for other branches it mirrors the underlying source name.
  • DRIVER_ID — Numeric identifier of the driver. It maps to CLASS_CATEGORY_ID, CLASS_CODE_ID, TASK_TYPE_ID, or PROJECT_TYPE_ID depending on the driver type.
  • DESCRIPTION — Descriptive text inherited from the respective base object.

Common Use Cases and Queries

Typical uses include validating driver configuration ahead of a costing run, feeding pick lists in external applications, and reconciling driver IDs against transactions. Because DRIVER_ID is only unique within a driver type, joins must filter on both columns.

  • List all driver families: SELECT DISTINCT driver_type FROM pa_ext_drivers_v;
  • Retrieve class codes only: SELECT driver_id, driver_name, description FROM pa_ext_drivers_v WHERE driver_type = 'CLASS_CODE' ORDER BY driver_name;
  • Look up a specific driver: SELECT driver_type, driver_name FROM pa_ext_drivers_v WHERE driver_id = :id AND driver_type = :type;
  • Count drivers by family for a setup audit: SELECT driver_type, COUNT(*) FROM pa_ext_drivers_v GROUP BY driver_type;