Search Results okr_ip_relations

Overview

OKR_IP_RELATIONS_TL is the translation (language-specific) table for the base table OKR_IP_RELATIONS within the Oracle E-Business Suite product OKR — Contracts for Rights. This module is documented as obsolete in the current release, meaning that the object may be present only in older or upgraded schemas and is not implemented in fresh installations. The "_TL" suffix is the standard Oracle EBS convention for a translation table, which stores the same logical rows as its base table but once per installed language. OKR_IP_RELATIONS_TL therefore holds the translated descriptive attributes of intellectual property relation records, while the base table OKR_IP_RELATIONS holds the language-independent business data.

From a heuristic Data Vault modeling perspective (mined from the foreign-key structure rather than from a formal design document), this object can be treated as a standalone entity. Because the metadata does not document a foreign-key link from OKR_IP_RELATIONS_TL to any parent hub, the translation row is best modeled as its own satellite or reference construct keyed by the base entity identifier plus a language discriminator. This is a modeling suggestion only; the authoritative design remains the Oracle EBS relational schema.

Key Information Stored

The documented structure of this table is deliberately narrow, consistent with the translation-table pattern. The columns explicitly identified in the ETRM metadata are:

• IPR_ID — The intellectual property relation identifier. This is the foreign-key column that links each translation row back to its parent record in OKR_IP_RELATIONS, and it is also the first component of the primary key.
• LANGUAGE — The language code identifying the locale of the translated text. This is the second component of the primary key and the discriminator that allows multiple rows per IPR_ID.
• Translated descriptive text columns — Although the metadata excerpt does not enumerate the individual text columns, a translation table of this type typically carries the language-specific name, description, and any other user-facing descriptive fields that are maintained per language.

The surrogate/technical primary key is the OKR_IP_RELATIONS_TL_PK, defined on the composite of (IPR_ID, LANGUAGE). The business-key candidate is the same column pair, since IPR_ID alone is not unique — each relation may exist once per installed language. There is no documented unique index beyond the primary key, and no additional surrogate column such as a sequence-generated ID is documented for this object.

Common Use Cases and Queries

Translation tables are normally joined to their base table on the shared identifier and filtered by the session or reporting language. A typical query retrieves the base relation together with its translated description for the user's language, falling back to the base row when no translation exists:

• Bilingual reporting: join OKR_IP_RELATIONS to OKR_IP_RELATIONS_TL on IPR_ID and select the translated name or description for a specific LANGUAGE value.
• Translation completeness audits: count base rows in OKR_IP_RELATIONS that have no matching row in OKR_IP_RELATIONS_TL for a given LANGUAGE — a common data-quality check after a language patch or upgrade.
• Language-coverage analysis: group by LANGUAGE over OKR_IP_RELATIONS_TL to determine which installed languages are populated.
• Upgrade and migration validation: because OKR is obsolete, these queries are frequently used to confirm whether legacy translation data still exists before archiving.

A representative pattern is: SELECT r.ipr_id, t.description FROM okr_ip_relations r, okr_ip_relations_tl t WHERE r.ipr_id = t.ipr_id AND t.language = USERENV('LANG'). Note that the table is reported as not implemented in the sampled database, so queries should be preceded by an existence check.

Related Objects

The following objects are the most significant in relation to OKR_IP_RELATIONS_TL:

• OKR_IP_RELATIONS — The base table. Joined on IPR_ID; it holds the language-independent data for each intellectual property relation.
• OKR_IP_RELATIONS_TL_PK — The primary key constraint/index enforcing uniqueness on (IPR_ID, LANGUAGE).
• Other OKR module tables — Because OKR is classified as a standalone entity, no foreign keys are documented to parent tables; related OKR Contracts for Rights objects (rights, agreements, and IP records) are reached through the base table rather than directly from the translation table.

Given the obsolete status of OKR — Contracts for Rights, integration points with current releases are limited, and this object should be treated as legacy metadata effective for EBS 12.1.1 and 12.2.2 environments where the module was previously implemented.