Search Results source_chr_id




Overview
Explore in AI Chat

Overview

OKR_R_AVAIL_STS_TXN_DV is a database view within the Oracle E-Business Suite OKR (Contracts for Rights) module, a component historically associated with intellectual property and rights management. The view name carries the _DV suffix conventionally reserved for "detail value" or denormalized presentation views, and its column list indicates it is designed to expose rights availability status information alongside related transaction and contract attributes.

Critically, the ETRM documentation classifies OKR as obsolete and explicitly states that this view is "Not implemented in this database." This is a governance marker rather than a defect: the object definition exists in the data dictionary metadata, but the view is not created as a runtime database object within the referenced environment. As a result, the view has no functional reporting role in a live 12.1.1 or 12.2.2 instance. Its significance is therefore archaeological—it documents the intended shape of rights availability reporting in the legacy OKR data model and, where the view is present in older or customized environments, it can be queried for reconciliation and migration purposes.

Underlying Base Objects

The ETRM metadata does not document any referenced base objects under the standard "Referenced base objects" heading. However, the view text itself reveals the dependency graph. The SELECT joins two objects on a three-part composite key:

The join predicate matches on USER_SESSION_ID, SEARCH_ID, and RGTS_TXN_ID. This join structure is characteristic of Oracle Forms-based, session-scoped availability searches: the user initiates a rights availability query, a session identifier and search identifier are generated, and result rows are materialized into temporary staging objects before being presented. Because both underlying objects are temp objects or temp-backed views, the data is transient by design and is scoped to a single user session and search execution.

Key Columns

The view exposes a broad slice of rights and contract metadata. Column meanings follow from their names and the OKR domain model:

Common Use Cases and Queries

Because the view is documented as not implemented, standard query use is limited to environments where the object was manually created or retained. The most direct invocation filters on the search key of interest, and given the sensitive nature of SOURCE_CHR_ID, a tracing query would resemble:

  • SELECT CONTRACT_NUMBER, VERSION_NUMBER, SOURCE_CHR_ID, CHR_ID, STS_CODE_MEANING, START_DATE_ACTIVE, END_DATE_ACTIVE FROM OKR_R_AVAIL_STS_TXN_DV WHERE SOURCE_CHR_ID = :chr_id;
  • SELECT TERritory_NAME, LANGUAGE_MEANING, MEDIA_MEANING, SELLABLE_YN FROM OKR_R_AVAIL_STS_TXN_DV WHERE RGTS_TXN_ID = :txn_id;
  • SELECT * FROM OKR_R_AVAIL_STS_TXN_DV WHERE USER_SESSION_ID = :session AND SEARCH_ID = :search_id;

Typical scenarios include auditing which source contracts underlie derived rights availability rows, reconciling temporary availability search output against persisted contract records, and supporting data migration away from the obsolete OKR module. Any query should confirm view existence via ALL_VIEWS before execution, since the metadata confirms the object is absent from the standard 12.1.1 and 12.2.2 database.