Search Results okr_ip_rgts_txn_dv

Overview

OKR_IP_RGTS_TXN_DV is a database view belonging to the OKR – Contracts for Rights module, a component of Oracle E-Business Suite historically used to manage intellectual property rights, licensing transactions, and contract templates. The OKR module is documented as obsolete in Oracle EBS 12.1.1 and 12.2.2, meaning it is no longer actively supported or delivered in current implementations. The suffix "DV" suggests "Denormalized View," reflecting its purpose of consolidating transaction-level rights data with descriptive and derived attributes into a single queryable structure. The ETRM metadata explicitly notes that this view is "Not implemented in this database," indicating it is unlikely to exist in a standard 12.1.1 or 12.2.2 instance unless the obsolete OKR schema was retained from an earlier upgrade. The view's role was to support reporting and integration by exposing rights transaction records alongside contract and IP metadata, sparing developers from writing complex joins across the underlying base tables.

Underlying Base Objects

The documented metadata lists no referenced base objects, which is a common limitation for obsolete or non-implemented views. However, the view text reveals its principal source: a table aliased as RTXB, which supplies most of the core columns including ID, OBJECT1_ID1, OBJECT1_ID2, JTOT_OBJECT1_CODE, IP_RIGHTS_ID, TXN_TYPE_CODE, and the various Y/N flags. A secondary table aliased RTXT provides descriptive columns such as NAME, DESCRIPTION, RESTRICTION_TEXT, KEYWORD_TEXT, and SFWT_FLAG, joined to RTXB on a common key. A third source, aliased IPRB, contributes VAL_PTRT_ID. These objects belong to the OKR rights transaction schema. Because the OKR module is obsolete and the view is not implemented, these base tables are typically absent from current 12.1.1 and 12.2.2 databases, and the view cannot be compiled or queried in a standard installation.

Key Columns

The view exposes a broad set of identifiers and derived attributes:

• OBJECT1_ID1 / OBJECT1_ID2 – Generic object reference keys; the first is directly referenced in the user search and is resolved against JTOT_OBJECT1_CODE to determine the owning entity. When the code is OKR_TEMPLATE_CONTRACT, OBJECT1_ID1 holds the contract identifier.
• JTOT_OBJECT1_CODE – Object type discriminator controlling the DECODE logic that populates contract number, version, status, and intent columns.
• CHR_ID – Contract header identifier, used when the object type is OKR_IP.
• IP_RIGHTS_ID, TXN_ID, TXN_TYPE_CODE – Core rights transaction identifiers and classification.
• EXCLUSIVE_YN, RESTRICTED_YN, SELLABLE_YN – Rights flags describing the transaction's commercial terms.
• START_DATE_ACTIVE / END_DATE_ACTIVE, DURATION – Effective period, with duration derived via OKR_UTIL_PUB.GET_PERIOD_DURATION.
• CONTRACT_NUMBER, VERSION_NUMBER, STS_CODE, STS_CODE_MEADNING, BUY_OR_SELL, IP_NAME – Derived values computed through OKR_UTIL_PUB functions.

Common Use Cases and Queries

In legacy OKR environments, this view supported rights-transaction reporting, integration extracts, and contract-to-IP reconciliation. A representative query follows:

SELECT OBJECT1_ID1, CHR_ID, TXN_TYPE_CODE, CONTRACT_NUMBER, VERSION_NUMBER, STS_CODE, DURATION
FROM OKR_IP_RGTS_TXN_DV
WHERE JTOT_OBJECT1_CODE = 'OKR_IP';

Analysts searching on object1_id1 would typically filter or join on that column to trace a rights transaction back to its originating contract or template. Because the view is obsolete and undocumented as implemented, any query should first verify existence via ALL_VIEWS before relying on it in 12.1.1 or 12.2.2.