Search Results class_code_id

Overview

PA_PROJECTS_ERP_OCV is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Projects (PA) product family and functions as an "Open Cable View" (OCV), a naming convention Oracle uses for views that expose code, identifiers, and cached language information for downstream consumption by reporting tools, integration layers, and Oracle Application Framework (OAF) components. Specifically, this view consolidates lookup-style reference data that a user interface or external system needs when a project or task is created or queried — including classification categories, classification codes, project types, and task types.

The view's role in EBS reporting and integration is to provide a single, flat source for the descriptive text and identifiers of these reference values. Because it applies USERENV('LANG') in each of its constituent queries, the returned LANGUAGE column reflects the session language, aligning multilingual display with the user's environment. This makes the view suitable for upstream form or page population and for ad hoc reporting that must remain language-aware.

Underlying Base Objects

The view is a UNION ALL of four distinct SELECT statements, each reading from a synonym that resolves to a base table in the PA module. The documented referenced base objects are PA_CLASS_CATEGORIES, PA_CLASS_CODES, PA_PROJECT_TYPES, and PA_TASK_TYPES, all registered as synonyms in the APPS schema. Each branch filters or projects a specific subset: PA_CLASS_CATEGORIES is restricted to OBJECT_TYPE = 'PA_PROJECTS', ensuring only categories that apply to projects are returned; the remaining three selections draw from the full set of class codes, project types, and task types.

The view is a non-updatable, defining-query style view. There are no joins between the four sources; the union aligns on column position rather than relational keys. This design means the view does not enforce referential relationships between project types and task types; it merely aggregates the available reference rows.

Key Columns

The view exposes exactly three columns, and their semantics are defined by the UNION ALL construction rather than by an explicit CREATE VIEW column list:

• CODE — A synthetic identifier formed by concatenating a literal prefix with the primary key of the source row. The prefixes are 'CLASS_CATEGORY:', 'CLASS_CODE:', 'PROJECT_TYPE:', and 'TASK_TYPE:', each followed by the corresponding numeric ID. This prefix scheme allows consumers to disambiguate the origin of each row and to parse the underlying ID when needed.
• MEANING — The descriptive or display name of the reference value, sourced from CLASS_CATEGORY, CLASS_CODE, PROJECT_TYPE, or TASK_TYPE respectively. This column is the user-facing label for the coded value.
• LANGUAGE — The session language code returned by USERENV('LANG'). Because the same base tables can hold translated names, this column lets a client filter or group results by the active language context, which is particularly relevant in multilingual implementations.

Because the union aligns by position, the prefixes in CODE are the only mechanism distinguishing the four categories of reference data at the row level.

Common Use Cases and Queries

The view is used whenever an application must present a combined dropdown or control of project and task reference values, or when an integration must map external task or project type codes to EBS identifiers. A typical query to retrieve all task types is:

• SELECT CODE, MEANING FROM APPS.PA_PROJECTS_ERP_OCV WHERE CODE LIKE 'TASK_TYPE:%';
• SELECT CODE, MEANING FROM APPS.PA_PROJECTS_ERP_OCV WHERE CODE LIKE 'PROJECT_TYPE:%';
• SELECT * FROM APPS.PA_PROJECTS_ERP_OCV WHERE MEANING = :p_meaning AND LANGUAGE = USERENV('LANG');

A search for task_type against this object will most commonly surface the 'TASK_TYPE:' row set. Note that the view does not expose the raw numeric ID in a separate column; to obtain it, the application must parse the CODE value after the colon, or query PA_TASK_TYPES directly. For reporting performance, callers should apply the prefix filter on CODE rather than relying on a substring match across the full union.