Search Results okr_ip_clsf_types

Overview

OKR_CLSF_TYPES_V is a database view belonging to the OKR — Contracts for Rights product family within Oracle E-Business Suite. OKR was the historical module used to manage intellectual property and rights-based contracts, and it is now classified as obsolete in the ETRM documentation set covering releases 12.1.1 and 12.2.2. The view functions as a thin projection layer over the underlying classification type table, presenting a stable, read-only interface for concurrent programs, forms, and external integrations that need to enumerate valid classification type combinations without touching the base table directly.

Because the object is documented as "Not implemented in this database" in the reference metadata, the view should be treated as a legacy artifact. Its presence in a given environment depends on whether OKR was ever installed and whether the underlying table OKR_CLSF_TYPES exists in that instance. In reporting contexts, the view is typically referenced when auditing the historical setup of rights classification, or when migrating data out of an obsolete OKR implementation.

Underlying Base Objects

The view is defined exclusively over the table OKR_CLSF_TYPES, aliased as PCTB in the view text. No joins, unions, or subordinate views are involved, and no additional base objects are documented. Every column in the SELECT list is a direct pass-through of a corresponding column from that table, with the sole exception of ROW_ID, which is derived from the base table's ROWID pseudocolumn. This simple one-to-one construction means the view carries no transformation logic, no filtering predicate, and no aggregation; it exists purely to expose a named interface over the physical table.

Despite the naming convention, the view is not a classified "V" variant of multiple tables and does not consolidate OKR_IP_CLSF_TYPES or any other object. The description in the metadata states that it is the view for table OKR_IP_CLSF_TYPES, which is consistent with the single-table definition shown in the view text. Implementers should verify the actual data dictionary definition in their instance using DBA_VIEWS or DBA_DEPENDENCIES before relying on assumptions drawn from the name alone.

Key Columns

The columns exposed by the view map directly to the base table and include both business and audit attributes:

• ROW_ID — The ROWID of the underlying OKR_CLSF_TYPES row, useful for row-level identification and de-duplication in ad hoc extracts.
• IP_TYPE — The intellectual property type. This is the column referenced by the user search term "ip_type" and represents the primary discriminator for the classification record.
• CLSF_TYPE — The classification type associated with the IP type, completing the composite business key of the table.
• OBJECT_VERSION_NUMBER — The optimistic locking version counter used by the Oracle Application Framework (OAF) and forms layers to detect concurrent updates.
• CREATED_BY, CREATION_DATE — Standard WHO columns recording the user and timestamp of row creation.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns capturing the most recent modification, the responsible user, and the login session that performed it.

The presence of OBJECT_VERSION_NUMBER and the full WHO audit set indicates the table was maintained through the standard EBS DML framework rather than by direct SQL loads.

Common Use Cases and Queries

The principal use case is enumeration and validation of classification types for rights contracts. A typical query lists all valid combinations and their maintenance history:

• SELECT ip_type, clsf_type FROM okr_clsf_types_v ORDER BY ip_type, clsf_type;
• SELECT ip_type, clsf_type, last_updated_by, last_update_date FROM okr_clsf_types_v WHERE ip_type = :p_ip_type;
• SELECT COUNT(*) FROM okr_clsf_types_v WHERE clsf_type IS NULL; — a data-quality check for orphaned classification entries.

Because the view is a direct projection with no filters, it can also serve as a lightweight extraction source during decommissioning of an OKR installation, and as a reference for mapping legacy IP_TYPE values into a replacement contract management system. Given that OKR is obsolete, these queries are best reserved for historical analysis rather than new development.