Search Results from_ip_id

Overview

OKR_IP_RELATIONS_V is a reporting view in the Oracle E-Business Suite that belongs to the OKR product family, which is designated in the ETRM metadata as "Contracts for Rights (Obsolete)". It presents intellectual property (IP) relationship data held in the underlying base table OKR_IP_RELATIONS_B, joined with its translation table OKR_IP_RELATIONS_TL to supply language-specific descriptive content such as notes. The view functions as a read-only presentation layer, exposing the attributes of a relationship between intellectual property entities—principally the originating and target IP identifiers—together with validity dates, relationship classification, descriptive text, and the standard EBS audit and descriptive flexfield columns. Because the OKR module is obsolete in the documented releases (12.1.1 and 12.2.2), the view is retained primarily for backward compatibility, historical reporting, and any remaining custom integrations that reference the legacy IP relationship model. The ETRM record indicates the view is "Not implemented in this database," meaning no physical instance was created in the documented environment, though the view text and column definitions remain part of the shipped metadata. The user search term to_ip_id corresponds directly to the TO_IP_ID column, which identifies the target or destination intellectual property record in each relationship, making this view the natural retrieval point for that attribute.

Underlying Base Objects

The view is defined over two documented base objects:

• OKR_IP_RELATIONS_B — the base (non-translated) table holding the core relationship rows, aliased IPRB in the view definition.
• OKR_IP_RELATIONS_TL — the translation table providing language-dependent columns, aliased IPRT.

The join condition is IPRB.IPR_ID = IPRT.IPR_ID combined with the session language filter IPRT.LANGUAGE = USERENV('LANG'). This structure follows the standard Oracle EBS MLS (Multi-Lingual Support) pattern: transactional and keyed attributes reside in the _B table, while translatable text such as NOTE resides in the _TL table filtered by the current language environment. As a consequence, each base relationship row yields exactly one view row for the active user language, and queries return text in the session's language rather than all installed languages. No additional documented base objects are referenced in the ETRM metadata; the view does not resolve the IP identifiers to their master descriptions, so downstream joins to the IP master entity are required when descriptive names are needed.

Key Columns

• ROW_ID — the ROWID of the underlying base row, enabling direct addressing of OKR_IP_RELATIONS_B.
• IPR_ID — primary key of the IP relationship record.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework.
• TO_IP_ID — identifier of the target IP entity in the relationship; the column directly associated with the search term "to_ip_id".
• FROM_IP_ID — identifier of the source IP entity.
• IP_REL_TYPE — classification of the relationship between the two IP entities.
• KHR_ID — reference to the associated rights/know-how record.
• START_DATE / END_DATE — effective period during which the relationship is valid.
• SFWT_FLAG — translation-table flag exposed for the current language row.
• NOTE — language-specific descriptive text sourced from the _TL table.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield segments for extensibility.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns maintained by the EBS who-column framework.

Common Use Cases and Queries

Typical use cases include historical reporting of IP rights relationships, resolving the target IP for a given source IP, and auditing relationship validity windows. A common pattern retrieves all relationships originating from a specific IP and resolves the counterpart via TO_IP_ID:

SELECT ipr_id,
       from_ip_id,
       to_ip_id,
       ip_rel_type,
       start_date,
       end_date
  FROM okr_ip_relations_v
 WHERE from_ip_id = :p_from_ip_id
   AND (end_date IS NULL OR end_date >= SYSDATE)
 ORDER BY start_date;

A second scenario filters by relationship type and returns the translated note:

SELECT ipr_id,
       to_ip_id,
       ip_rel_type,
       note
  FROM okr_ip_relations_v
 WHERE ip_rel_type = :p_rel_type
   AND start_date >= :p_start_date;

Because the view resolves the session language through USERENV('LANG'), note text is returned only for the language of the connecting session; multilingual reporting must set NLS appropriately or query the base _TL table directly. Given the obsolete status of OKR, new development should not depend on this view; existing reports and integrations should be assessed for migration to current rights-management objects where available. The view remains useful solely for preserving continuity of legacy logic that references TO_IP_ID and related IP relationship attributes.