Search Results okr_classification_types

Overview

OKR_CLSF_TYPES_DV is a database view within the Oracle E-Business Suite (EBS) module OKR — Contracts for Rights, a component historically associated with intellectual property and rights management. In EBS releases 12.1.1 and 12.2.2 this module is classified as obsolete, meaning it is no longer actively supported or extended, yet the underlying schema objects may persist in legacy installations that were upgraded from earlier releases.

The view presents a denormalized, reporting-friendly representation of classification type records. Rather than forcing consumers to join code values against lookup tables manually, OKR_CLSF_TYPES_DV resolves the stored classification code into a human-readable meaning and description through calls to the OKR_UTIL_PUB utility package. This makes the view suitable for inquiry screens, concurrent report output, and integration extracts where descriptive labels are required rather than internal codes.

The ETRM documentation for this object notes that it is not implemented in the reference database from which the metadata was generated, indicating that the object exists only where the OKR schema has been fully installed or where legacy OKR objects were retained.

Underlying Base Objects

The view is defined over a single base table, OKR_CLSF_TYPES, aliased as PCTB in the defining query. The ETRM metadata documents no additional referenced base objects, and the view's structure confirms this: all persistent columns are selected directly from OKR_CLSF_TYPES, with the two descriptive columns derived at runtime through PL/SQL function calls.

The relationship is strictly one-to-one. Every row returned by the view corresponds to exactly one row in OKR_CLSF_TYPES. The view exposes the base table's ROWID as ROW_ID, preserving the ability to identify the source row for update or navigation purposes. Because the descriptive columns are computed via OKR_UTIL_PUB.GET_LU_MEANING and OKR_UTIL_PUB.GET_LU_DESCRIPTION against the lookup type OKR_CLASSIFICATION_TYPES, the view's output depends on the current state of that lookup, not solely on the base table.

Key Columns

• ROW_ID — The ROWID of the underlying OKR_CLSF_TYPES row, useful for direct row identification.
• IP_TYPE — The intellectual property type to which the classification applies, forming part of the classification's context.
• CLSF_TYPE — The stored classification code value.
• CLSF_TYPE_MEANING — The lookup meaning resolved from OKR_CLASSIFICATION_TYPES for the stored code.
• CLSF_TYPE_DESCRIPTION — The lookup description resolved from OKR_CLASSIFICATION_TYPES.
• OBJECT_VERSION_NUMBER — Optimistic locking version stamp, used by the framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE — Standard WHO columns recording the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns recording the most recent modification user, timestamp, and login.

Common Use Cases and Queries

The view is typically used to populate list of values (LOVs) and inquiry reports where classification types must be displayed with their descriptive labels rather than raw codes. A representative query retrieving all classification types with their meanings is shown below:

• SELECT clsf_type, clsf_type_meaning, clsf_type_description FROM okr_clsf_types_dv ORDER BY clsf_type_meaning;
• SELECT clsf_type, clsf_type_meaning FROM okr_clsf_types_dv WHERE ip_type = :ip_type;
• SELECT row_id, clsf_type, clsf_type_meaning FROM okr_clsf_types_dv WHERE clsf_type_meaning LIKE :search_text;

Because the descriptive columns are resolved by package function calls, queries that filter or sort on CLSF_TYPE_MEANING or CLSF_TYPE_DESCRIPTION cannot leverage indexes on the base table and may perform full scans with per-row PL/SQL invocation. For high-volume processing, joining OKR_CLSF_TYPES directly against FND_LOOKUP_VALUES on the OKR_CLASSIFICATION_TYPES lookup type is generally more efficient. Given the obsolete status of the OKR module, use of this view should be confined to legacy reporting and migration activities, and any new development should avoid dependencies on it.