Search Results rgtp_id




Overview
Explore in AI Chat

Overview

The view OKR_VALID_PROP_RGTS_V belongs to the Oracle E-Business Suite product OKR — Contracts for Rights, a module that has since been classified as obsolete in the Oracle product taxonomy. In both Oracle EBS 12.1.1 and 12.2.2, OKR provided functionality for managing intellectual property rights contracts, royalties, and the associated rights allocations. This view is a straightforward projection over the single base table OKR_VALID_PROP_RGTS, exposing every column of that table alongside the ROWID pseudo-column as ROW_ID.

The view's purpose is to present rows of valid property rights associations. The columns IP_TYPE, RGTP_ID, LANGUAGE_YN, MEDIA_YN, START_DATE, and END_DATE indicate that each record defines a right granted against an intellectual property type for a specific rights group or template (RGTP_ID), optionally restricted to language or media rights, and bounded by effective dates. As an obsolete component, the view is not installed in current database instances and should not be relied upon for new development. Its value today is primarily historical and diagnostic — it appears in legacy code, reports, and upgrade analysis for organizations that ran OKR.

Underlying Base Objects

The documented base object is the table OKR_VALID_PROP_RGTS. The view text selects exclusively from this table, aliased as VPR, with a simple SELECT … FROM OKR_VALID_PROP_RGTS VPR clause and no joins, unions, or WHERE filters. There is therefore an exact one-to-one correspondence between rows in the table and rows in the view. Because the view adds no joins, all predicates, sorting, and business logic must be applied by the calling query. The metadata lists no other referenced base objects, which is consistent with the view text. The ROW_ID column is derived from VPR.ROWID, allowing consumers to address individual rows directly, a pattern commonly used for forms-based or programmatic update logic in EBS.

Key Columns

  • ROW_ID — the physical row identifier of the underlying table row, exposed for direct row addressing.
  • ID — the primary identifier of the valid property rights record.
  • IP_TYPE — the intellectual property type to which the rights definition applies.
  • RGTP_ID — the rights group/template identifier, the column referenced by the user search term "rgtp_id".
  • LANGUAGE_YN, MEDIA_YN — flags indicating whether language rights and media rights are included in the definition.
  • START_DATE, END_DATE — the effective window during which the rights definition is considered valid.
  • OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework for concurrent update control.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns maintained by the applications framework.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (descriptive flexfield) columns, available for customer-defined context and attributes.

Notably, the view does not expose ORG_ID, and multiple-organization filtering must therefore be handled by the consumer if the base table is partitioned by operating unit through another mechanism.

Common Use Cases and Queries

The primary historical use case was locating valid property rights definitions by rights group or template. A typical query joins the view to rights group data and restricts by effective dates:

SELECT v.id, v.ip_type, v.rgtp_id, v.start_date, v.end_date
FROM   okr_valid_prop_rgts_v v
WHERE  v.rgtp_id = :rgtp_id
AND    TRUNC(SYSDATE) BETWEEN v.start_date AND NVL(v.end_date, TRUNC(SYSDATE));

Another frequent pattern was auditing who created or maintained rights definitions using the standard audit columns:

SELECT v.id, v.rgtp_id, v.created_by, v.creation_date,
       v.last_updated_by, v.last_update_date
FROM   okr_valid_prop_rgts_v v
WHERE  v.last_update_date >= TRUNC(SYSDATE) - 30;

Because the view performs no filtering, queries must always qualify the effective dates and other business conditions explicitly. In upgrade or diagnostic work, DBAs can compare OKR_VALID_PROP_RGTS_V against the base table to confirm row alignment, since the two should be identical. Given the obsolete status of the OKR module in 12.2.2, any remaining usage should be treated as legacy and slated for replacement.