Search Results pa_project_types_v




Overview
Explore in AI Chat

Overview

PA_PROJECT_TYPES_V is a reporting view in the Oracle E-Business Suite Projects (PA) module, owned by the APPS schema and defined over the project type setup tables. It presents a denormalized, user-friendly projection of project type definitions together with their classification, allowing reporting tools, concurrent programs, and integration interfaces to retrieve project type information through a single, stable object. The view joins the PA_PROJECT_TYPES table with the PA_LOOKUPS view so that the stored class code is translated into its descriptive lookup meaning, which is essential because project type classes (for example, contract, indirect, and capital) drive downstream behavior such as costing, billing, and revenue recognition rules.

The ETRM documentation records this object with the description "10SC Only," indicating that the definition is associated with a specific release or localized variant of the 10SC documentation set rather than the fully documented core view inventory. The object itself is status VALID and is a documented part of the APPS layer in the 12.1.1 and 12.2.2 environments represented in the metadata. Because the view encapsulates the join to PA_LOOKUPS and the internal call to the PA_INSTALL package, it also absorbs licensing behavior that would otherwise have to be replicated in every reporting query.

Underlying Base Objects

The documented referenced base objects are PA_PROJECT_TYPES, PA_LOOKUPS, and the PA_INSTALL package.

  • PA_PROJECT_TYPES — exposed in the definition as a synonym; it is the primary setup table that stores the project type identifier, name, description, class code, effective dates, and the cross-charge provider flag.
  • PA_LOOKUPS — exposed as a view; it supplies the descriptive MEANING for the LOOKUP_TYPE 'PROJECT TYPE CLASS' so that the view returns a translatable classification label rather than only the coded value.
  • PA_INSTALL — exposed as a package; its IS_BILLING_LICENSED function is invoked inside the WHERE clause to control which predefined lookup rows are visible, depending on whether the billing license is installed.

The join condition equates the project type class code to the lookup code and restricts lookup type to the project type class set. The PREDEFINED_FLAG predicate evaluates PA_INSTALL.IS_BILLING_LICENSED(); when billing is not licensed, the predicate resolves so that only user-defined (non-predefined, 'C') classification rows are returned, effectively tailoring the visible rows to the installed applications.

Key Columns

  • ORG_ID — operating unit identifier, enabling multi-organization security and reporting.
  • PROJECT_TYPE_ID — the internal primary key of the project type; used as a foreign key throughout the Projects schema.
  • PROJECT_TYPE — the user-facing name of the project type, typically the value displayed in lists of values.
  • DESCRIPTION — free-form descriptive text attached to the project type.
  • PROJECT_TYPE_CLASS_CODE — the coded classification value stored on the project type record.
  • PROJECT_TYPE_CLASS_M — the translated lookup meaning for the class code, derived from PA_LOOKUPS.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range governing when the project type may be assigned.
  • CC_PRVDR_FLAG — indicates whether the project type is enabled as a cross-charge provider, relevant to inter-project and inter-organization costing setups.

Common Use Cases and Queries

Typical uses include validating or listing project types in reporting extracts, populating concurrent program parameters, and supporting integrations that must resolve a project type name to its identifier and class. A simple listing query is:

SELECT project_type_id, project_type, project_type_class_m, start_date_active, end_date_active FROM apps.pa_project_types_v WHERE org_id = :p_org_id AND (end_date_active IS NULL OR end_date_active >= SYSDATE) ORDER BY project_type;

For integrations mapping project types to their class code, the following returns both coded and descriptive values:

SELECT pt.project_type_id, pt.project_type, pt.project_type_class_code, pt.project_type_class_m, pt.cc_prvdr_flag FROM apps.pa_project_types_v pt WHERE pt.project_type_class_code = :p_class_code;

Because visibility of predefined classification rows depends on PA_INSTALL.IS_BILLING_LICENSED(), reports that compare row counts against the base table may observe differences when the billing license is absent. Integrations requiring the raw, unfiltered set of classifications should query PA_PROJECT_TYPES directly and resolve the meaning separately from PA_LOOKUPS.