Results for “pji_work_types_v”

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

Overview

PJI_WORK_TYPES_V is a view in the Oracle E-Business Suite Project Intelligence (PJI) module, historically delivered with EBS 12.1.1 and carried forward into 12.2.2. The Product/Module designation in the ETRM repository marks PJI as "Project Intelligence (Obsolete)," indicating that the module has been superseded by later Oracle project analytics and reporting offerings. The view itself is described in the documentation as an "internal summarization view," which signals that it was not intended as a public integration interface but rather as a supporting construct for PJI's internal reporting and summarization routines.

Functionally, PJI_WORK_TYPES_V exposes a simplified, flat projection of work type data stored in the PA (Projects) schema. Its role in reporting is to join project work types to their associated resource and organization utilization categories, allowing PJI summarization processes to group effort and cost data by those categories without repeatedly navigating the PA_WORK_TYPES_VL and base PA tables. Because it is an internal summarization view, its column list is deliberately narrow, and its primary audience is the set of PJI programs and reports that depend on it.

Underlying Base Objects

According to the documented view text, PJI_WORK_TYPES_V is defined entirely over a single base object:

• PA_WORK_TYPES_VL — the translated (VL, "view with language") view of the PA_WORK_TYPES table, which supplies the work type identifier, name, and the resource and organization utilization category identifiers.

The view definition is:

SELECT WORK_TYPE_ID, NAME, RES_UTIL_CATEGORY_ID, ORG_UTIL_CATEGORY_ID FROM PA_WORK_TYPES_VL

Because PA_WORK_TYPES_VL is itself a view over the underlying PA_WORK_TYPES_B (base) and PA_WORK_TYPES_TL (translation) tables, PJI_WORK_TYPES_V is effectively a three-level abstraction. No other referenced base objects are documented in the ETRM metadata, and the owner field is blank in the documented metadata for 12.2.2. The fact that PA_WORK_TYPES_VL is the sole documented dependency means that any change to the PA work type data model directly propagates to this view; there is no independent persistence layer.

Key Columns

• WORK_TYPE_ID — The surrogate primary key identifying a specific work type defined in Oracle Projects. This is the join key used throughout PA and PJI schemas.
• NAME — The user-facing, translated work type name as maintained in PA_WORK_TYPES_VL. Because the source is a VL view, the value respects the session's language setting.
• RES_UTIL_CATEGORY_ID — The resource utilization category identifier associated with the work type. This column is the specific target of the user's search for res_util_category_id; it links the work type to a resource utilization category used in PJI capacity, utilization, and effort summarization.
• ORG_UTIL_CATEGORY_ID — The organization utilization category identifier associated with the work type, used when summarizing utilization at the organization level.

The two utilization category columns do not carry denormalized descriptions; callers must join to the appropriate category views (for example, PA_RES_UTIL_CATEGORIES_VL or PA_ORG_UTIL_CATEGORIES_VL) to obtain names.

Common Use Cases and Queries

Although PJI_WORK_TYPES_V is an internal summarization view and is documented as "Not implemented in this database" in the source metadata, it remains a useful reference point for understanding how work types map to utilization categories in the PA data model. Typical usage patterns include:

• Resolving a work type to its resource and organization utilization categories for reporting joins.
• Populating PJI-style summaries of utilization by category.
• Investigating the relationship between work types and utilization categories during upgrade or data-migration analysis from 12.1.1 to 12.2.2.

Sample query:

SELECT v.WORK_TYPE_ID, v.NAME, v.RES_UTIL_CATEGORY_ID, v.ORG_UTIL_CATEGORY_ID
FROM PJI_WORK_TYPES_V v
WHERE v.RES_UTIL_CATEGORY_ID IS NOT NULL;

To obtain the category names, extend the query with a join to the PA resource utilization category view. Because the object is marked obsolete and may not be deployed in all environments, applications should prefer the documented PA_WORK_TYPES_VL view directly for new development.