Search Results okr_classification_codes

Overview

OKR_IP_CLSFS_DV is a database view historically shipped with the Oracle E-Business Suite module OKR — Contracts for Rights. In the 12.1.1 and 12.2.2 release streams this module is classified as obsolete, and the view itself is documented as "Not implemented in this database" within the ETRM metadata. Consequently, OKR_IP_CLSFS_DV should be regarded as a legacy dictionary object rather than an active runtime component in current installations.

The view was designed to present a denormalized, report-ready projection of intellectual property (IP) records combined with their classification assignments. It joins the IP master table to its translation table, to a classification detail table, and twice to FND_LOOKUPS in order to resolve lookup codes into their user-facing meanings. The primary reporting value is that a single SELECT returns the IP identifier, descriptive text, and both the raw and translated classification values, eliminating the need for downstream consumers to perform the lookup joins themselves.

For a user searching on the term ip_identifier, this view is relevant because it exposes the IP_IDENTIFIER column, which carries the business-facing identifier of the intellectual property record. That column originates from OKR_IP_COMMON_B and is surfaced directly, without transformation, through the view's SELECT list.

Underlying Base Objects

The view text defines a join across five physical objects. The driving table is OKR_IP_COMMON_B, aliased IPYBB, which stores the base (non-translated) attributes of each IP record. Its translation counterpart, OKR_IP_COMMON_TL (alias IPYBT), supplies language-dependent descriptive columns and is restricted to the session language via the condition IPYBT.LANGUAGE = USERENV('LANG'). Classification assignments are held in OKR_IP_CLASSIFICATIONS (alias PCN), joined to the IP master on IP_ID.

Two instances of FND_LOOKUPS resolve coded values into readable meanings. The alias CSFT resolves CLSF_TYPE against lookup type OKR_CLASSIFICATION_TYPES, while CSFC resolves CLSF_CODE against lookup type OKR_CLASSIFICATION_CODES. Notably, the ETRM 12.2.2 metadata records the owner as blank and lists no documented base objects, which is consistent with the view's obsolete status; the join logic must therefore be read directly from the stored view text.

Key Columns

• ID / ROW_ID — Surrogate row identifier from OKR_IP_CLASSIFICATIONS and the Oracle rowid of that classification row.
• IP_ID — Primary key linking the classification row to the IP master record.
• IP_IDENTIFIER — The business identifier of the intellectual property, sourced from OKR_IP_COMMON_B; the column most commonly targeted when searching by IP reference.
• CLSF_TYPE / CLSF_TYPE_MEANING — The raw classification type code and its FND_LOOKUPS meaning.
• CLSF_CODE / CLSF_CODE_MEANING — The raw classification code and its resolved meaning.
• NAME, SUBJECT, DESCRIPTION, KEYWORD_TEXT — Language-dependent descriptive attributes from OKR_IP_COMMON_TL.
• IP_TYPE, COUNTRY_OF_ORIGIN, IP_LANG_CODE — Core IP attributes from the base table.
• DATE_OF_CREATION, ORIG_CPRGT_DATE, START_DATE_ACTIVE, END_DATE_ACTIVE — Date attributes governing creation, original copyright, and effective activity windows.
• OWN_CPRGT, ASSET_ID, REFERENCE_PROPERTY — Ownership, asset linkage, and reference property attributes.

Common Use Cases and Queries

The principal use case was reporting on IP records together with their classification hierarchy, presenting resolved lookup meanings alongside the stored codes. A typical query locating a record by its IP identifier would be:

SELECT ip_identifier, name, clsf_type_meaning, clsf_code_meaning FROM okr_ip_clsfs_dv WHERE ip_identifier = :ip_identifier;

A second scenario enumerated all classifications for a given IP type or country of origin, supporting portfolio analysis and rights audits. Because the view performs the FND_LOOKUPS resolution internally, reports built on it avoided duplicate lookup joins and produced consistent terminology.

Given the obsolete classification of OKR and the documented absence of implementation, any query against OKR_IP_CLSFS_DV in a 12.1.1 or 12.2.2 environment should first be validated against the data dictionary; if the view is absent, equivalent results must be assembled directly from OKR_IP_COMMON_B, OKR_IP_COMMON_TL, OKR_IP_CLASSIFICATIONS, and FND_LOOKUPS.