Search Results attach_file_id




Overview
Explore in AI Chat

Overview

OKR_IP_COMMON_V is a database view belonging to the Oracle E-Business Suite product OKR — Contracts for Rights (Obsolete). Its documented purpose is to serve as a consolidated, language-aware read interface over the intellectual property base table OKR_INTELL_PROPS_B. The view joins the base table to its translation table, OKR_IP_COMMON_TL, so that callers obtain a single row per intellectual property record with the descriptive attributes resolved for the session's language.

Because the OKR module is marked obsolete, this object is not implemented in current 12.1.1 or 12.2.2 installations; the ETRM metadata records "Not implemented in this database." In historical releases where the module was active, the view functioned as a reporting and integration surface, shielding callers from the underlying multilingual table structure and from the row-level access rules encoded in the OKR_UTIL_PUB package. Its presence in the data dictionary is therefore mainly of interest for upgrade, retrofitting, or historical data-migration analysis.

Underlying Base Objects

The view text references two objects:

  • OKR_IP_COMMON_B (aliased IPYBB) — the base table holding intellectual property records, including identifiers, dates, asset references, descriptive flexfield columns, and WHO audit columns.
  • OKR_IP_COMMON_TL (aliased IPYBT) — the translation table supplying language-specific descriptive text such as NAME, SUBJECT, DESCRIPTION, KEYWORD_TEXT, and SFWT_FLAG.

The two are joined on IP_ID, with the additional predicate IPYBT.LANGUAGE = USERENV('LANG') restricting returned translation rows to the caller's session language. Although the metadata header describes the view under the title OKR_IP_COMMON_V with a note referencing OKR_INTELL_PROPS_B, the authoritative view text draws from OKR_IP_COMMON_B and OKR_IP_COMMON_TL; no other documented base objects are listed. A further WHERE clause applies OKR_UTIL_PUB.GET_PROP_ACCESS_LEVEL(IPYBB.IP_ID,'R') != 'N', so that records for which the caller lacks read access are excluded entirely. The function is also invoked in the SELECT list to expose the computed access level.

Key Columns

The view projects the full column list of the base table plus descriptive columns from the translation table:

Common Use Cases and Queries

In an environment where the OKR module is active, the view is typically queried to list or search intellectual property records in the user's language, applying the built-in access filter automatically. A typical lookup by keyword text is shown below.

  • Keyword and description searches: SELECT ip_id, name, keyword_text FROM okr_ip_common_v WHERE UPPER(keyword_text) LIKE '%PATENT%';
  • Language-resolved listings of active properties: SELECT ip_id, ip_type, name, start_date_active, end_date_active FROM okr_ip_common_v WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);
  • Audit and change tracking: SELECT ip_id, last_updated_by, last_update_date FROM okr_ip_common_v ORDER BY last_update_date DESC;
  • Integration extracts joining to assets or attachments via ASSET_ID and ATTACH_FILE_ID.

Because ACCESS_LEVEL is evaluated per row by a PL/SQL function, queries returning large result sets can incur performance overhead; filtering on IP_ID or other indexed base columns is advisable. Implementers should also confirm object availability before relying on the view, since the module is documented as obsolete and the view is not implemented in the current 12.1.1 and 12.2.2 data models.