Search Results pa_work_types_v




Overview
Explore in AI Chat

Overview

PA_WORK_TYPES_V is an Oracle Applications (APPS) view owned by the Projects (PA) product module in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes implementation-defined work types — the classifications used to describe the nature of work performed on projects — together with their associated attributes, utilization settings, and descriptive flexfield data. Work types drive several business processes in Projects, including expenditure categorization, utilization calculations for resources and organizations, and the treatment of billable or capitalizable effort.

Because the view is defined over the multi-language base view PA_WORK_TYPES_VL, it automatically resolves translated Name and Description values for the current session language. This makes it suitable both for application reporting against the operational Projects schema and for integration interfaces that must retrieve work type reference data with translated descriptions. The view presents current and historical work type definitions governed by START_DATE_ACTIVE and END_DATE_ACTIVE, and it therefore supports queries against both active and expired work types.

Underlying Base Objects

The documented base object is APPS.PA_WORK_TYPES_VL, itself a multi-language view. In ETRM 12.2.2 metadata, PA_WORK_TYPES_VL is the sole referenced base object. The view text shows a simple projection of columns from PA_WORK_TYPES_VL aliased as W, with no joins or filters applied, so PA_WORK_TYPES_V inherits the language-resolution behavior of the VL layer. This means the descriptive columns (NAME and DESCRIPTION) come from translation tables keyed to the work type, while the non-translatable attributes originate from the underlying work type definition. The view carries a VALID status in the APPS schema and is therefore considered a supported reference for query purposes within the standard Projects data model.

Key Columns

  • WORK_TYPE_ID — Primary identifier of the work type; the join key to expenditure and work type assignment tables.
  • NAME / DESCRIPTION — Language-resolved work type name and description from the VL layer.
  • BILLABLE_CAPITALIZABLE_FLAG — Indicates whether work of this type is treated as billable or capitalizable.
  • REDUCE_CAPACITY_FLAG — Controls whether the work type consumes capacity in utilization calculations.
  • RES_UTILIZATION_PERCENTAGE — The percentage of a resource's time counted toward utilization for this work type.
  • ORG_UTILIZATION_PERCENTAGE — The percentage counted toward organization-level utilization.
  • RES_UTIL_CATEGORY_ID — Identifier of the utilization category applied to resources for this work type. This is the column most closely associated with the term res_util_category_id; it links the work type to the resource utilization categorization used in utilization reporting.
  • ORG_UTIL_CATEGORY_ID — The corresponding utilization category for organization-level utilization.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — Effective date range bounding the work type's active period.
  • TRAINING_FLAG, TP_AMT_TYPE_CODE, UNASSIGNED_FLAG — Supplemental attributes indicating training work types, transfer price amount type, and default unassigned handling.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — Descriptive flexfield context and segment values.
  • Standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include retrieving active work types for a list of values, reporting utilization configuration by resource utilization category, and integrating work type reference data into external systems. A common pattern is to filter on the effective dates and, where utilization is the focus, to select the resource utilization category column:

  • Active work types:
    SELECT work_type_id, name, description FROM pa_work_types_v WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) ORDER BY name;
  • Utilization configuration:
    SELECT work_type_id, name, res_utilization_percentage, org_utilization_percentage, res_util_category_id, org_util_category_id FROM pa_work_types_v;
  • Locate a work type by resource utilization category:
    SELECT work_type_id, name FROM pa_work_types_v WHERE res_util_category_id = :p_category_id;
  • Descriptive flexfield extraction:
    SELECT work_type_id, attribute_category, attribute1, attribute2 FROM pa_work_types_v WHERE attribute_category IS NOT NULL;

These queries are read-only and rely entirely on the supported view definition over PA_WORK_TYPES_VL.