Search Results rgts_txn_id

Overview

OKR_R_AVAIL_PREP_TEMP_V is a database view belonging to the Oracle E-Business Suite (EBS) module OKR — Contracts for Rights, which is flagged as obsolete in the ETRM (E-Business Suite Technical Reference Manual) metadata for releases 12.1.1 and 12.2.2. The view presents a denormalized, prepared availability data set drawn from a single underlying base table, OKR_R_AVAIL_PREP_TEMP. Its primary role is to expose rights availability preparation rows — including rights identifiers, transaction types, status codes, territory, language, media, and audit columns — through a stable interface used by OKR availability processing and reporting logic.

The object is documented as "Not implemented in this database," meaning it does not exist in every environment; its presence depends on whether the Contracts for Rights (OKR) product was installed and whether the relevant availability preparation functionality was enabled. Because OKR itself is obsolete, this view is effectively legacy and should be treated as read-only reference data.

Underlying Base Objects

The view is defined entirely over one base object: OKR_R_AVAIL_PREP_TEMP, aliased as RAPT in the view text. No other tables, joins, or documented base objects are referenced in the ETRM metadata, and no additional referenced base objects are documented for this view.

Each column in OKR_R_AVAIL_PREP_TEMP_V maps one-to-one with a column of the same name in OKR_R_AVAIL_PREP_TEMP. Because the view is a straight projection (SELECT RAPT. ... FROM OKR_R_AVAIL_PREP_TEMP RAPT), it introduces no filtering, aggregation, or transformation logic. Any row returned by the view corresponds directly to a row in the base table, and any DML against the view would depend on the base table's updateability constraints.

Key Columns

• USER_SESSION_ID, USER_NAME, SEARCH_ID: Identify the session, user, and search context under which the availability preparation row was generated.
• RGTS_TXN_ID, TXN_ID, TXN_TYPE_CODE: Core rights transaction identifiers. TXN_TYPE_CODE (the user's search term) is the transaction type code distinguishing the kind of rights transaction represented.
• OBJECT1_ID1, OBJECT1_ID2, JTOT_OBJECT1_CODE: Flexible key segments used to identify the primary object associated with the rights record.
• DNZ_RGTP_ID, IP_RIGHTS_ID: Internal identifiers for the rights template and intellectual property rights record.
• EXCLUSIVE_YN, RESTRICTED_YN, SELLABLE_YN: Yes/no flags describing whether the rights are exclusive, restricted, or sellable.
• CHR_ID, CLE_ID, NAME, DESCRIPTION: Contract rights identifiers together with descriptive text.
• RESTRICTION_TEXT, KEYWORD_TEXT: Free-text attributes capturing restrictions and searchable keywords.
• START_DATE_ACTIVE, END_DATE_ACTIVE, DURATION: Temporal attributes defining the active period and duration of the rights.
• SOURCE_CHR_ID, CONTRACT_NUMBER, VERSION_NUMBER, STS_CODE, STS_CODE_MEANING, BUY_OR_SELL: Contract-level context, status, and whether the rights are bought or sold.
• IP_NAME, IP_TYPE, IP_TYPE_MEANING: Intellectual property name and type classification.
• TERRITORY_ID, TERRITORY_NAME, LANGUAGE_CODE, LANGUAGE_MEANING, MEDIA_CODE, MEDIA_MEANING: Geography, language, and media scope of the rights.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN: Standard audit columns supporting concurrency control and traceability.

Common Use Cases and Queries

Typical use cases involve filtering availability preparation rows by transaction type, session, or contract to support rights availability reporting and troubleshooting. A sample query retrieving rights transaction rows for a specific transaction type is:

• SELECT TXN_TYPE_CODE, CONTRACT_NUMBER, IP_NAME, IP_TYPE, TERRITORY_NAME, LANGUAGE_CODE, MEDIA_CODE, STS_CODE_MEANING, START_DATE_ACTIVE, END_DATE_ACTIVE FROM OKR_R_AVAIL_PREP_TEMP_V WHERE TXN_TYPE_CODE = :txn_type_code;
• SELECT USER_SESSION_ID, USER_NAME, SEARCH_ID, RGTS_TXN_ID, TXN_ID, STATUS, CONTRACT_NUMBER FROM OKR_R_AVAIL_PREP_TEMP_V WHERE USER_SESSION_ID = :session_id ORDER BY LAST_UPDATE_DATE DESC;
• SELECT TXN_TYPE_CODE, BUY_OR_SELL, COUNT(*) FROM OKR_R_AVAIL_PREP_TEMP_V GROUP BY TXN_TYPE_CODE, BUY_OR_SELL;
• SELECT CONTRACT_NUMBER, VERSION_NUMBER, RESTRICTION_TEXT, KEYWORD_TEXT FROM OKR_R_AVAIL_PREP_TEMP_V WHERE RESTRICTED_YN = 'Y' AND SELLABLE_YN = 'N';

Because the view does not persist data and depends on OKR_R_AVAIL_PREP_TEMP, query results reflect the current contents of the base table. Given that OKR is obsolete and the view is documented as not implemented in all databases, developers should verify object existence (for example, via ALL_VIEWS and ALL_TAB_COLUMNS) before relying on it in production reporting or integrations.