Search Results okr_template_rgts_v

Overview

OKR_TEMPLATE_RGTS_V is a reporting and integration view in the Oracle E-Business Suite OKR (Contracts for Rights) module. It exposes rights template assignment records — the association between a template and the rights held or granted under it — by joining the base assignment table OKR_TEMPLATE_RGTS_B to its translation table OKR_TEMPLATE_RGTS_TL. The view presents one row per template-right assignment per installed language, resolved at runtime through USERENV('LANG').

A key characteristic of this view is its obsolescence. OKR is documented as an obsolete product in the ETRM reference set, and the metadata explicitly states that OKR_TEMPLATE_RGTS_V is "Not implemented in this database." Practitioners should therefore treat this object as a legacy artifact: it exists in the effective database version (12.1.1 / 12.2.2) only where the OKR module was historically deployed. Any dependency on this view should be validated against the specific environment before reuse.

The view is primarily consumed for read-only purposes — report generation, data migration extraction, and integration extracts that require template-level rights detail rather than transaction-level rights activity.

Underlying Base Objects

The view is defined over two documented base tables:

• OKR_TEMPLATE_RGTS_B — the base (untranslated) table holding assignment rows, aliased TMRB in the view text. This table supplies the majority of columns, including the primary key ID and the foreign key VAL_PTRT_ID.
• OKR_TEMPLATE_RGTS_TL — the translation table, aliased TMRT, supplying the descriptive attributes NAME, DESCRIPTION, and KEYWORD_TEXT.

The join is an equijoin on TMRB.ID = TMRT.ID, filtered by TMRT.LANGUAGE = USERENV('LANG'), which restricts translated rows to the session's current language setting. The view also exposes TMRB.ROWID as ROW_ID, enabling row-level identification for tooling that operates on physical row identifiers rather than logical keys. No additional base objects are documented for this view.

Key Columns

• ID — primary identifier of the template-right assignment record.
• VAL_PTRT_ID — the value/party or party-role reference associated with the assignment, and the column most likely to be targeted in the search term val_ptrt_id. It functions as the linking foreign key into the rights template party/role structure.
• CHR_ID, IP_ID, RGTP_ID — contextual identifiers linking the assignment to characteristic, intellectual property, and rights template entities respectively.
• NAME, DESCRIPTION, KEYWORD_TEXT — translated descriptive attributes sourced from the TL table.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective-dating columns governing the active window of the assignment.
• SFWT_FLAG — a control flag inherited from the translation record.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit and optimistic-locking columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard DFF (descriptive flexfield) extension columns, surfaced for reporting completeness.

Common Use Cases and Queries

The most frequent scenario is retrieving assignment detail for a known party/role reference or template identifier. Because the view already resolves translations, reporting code can query it directly without re-implementing the language join:

• Extracting all active assignments for a given VAL_PTRT_ID in the current session language.
• Building a localized picklist or LOV of template rights for a downstream integration.
• Auditing effective-dating windows for assignments tied to a specific template.

A representative query targeting the searched column:

SELECT v.ID, v.VAL_PTRT_ID, v.NAME, v.START_DATE_ACTIVE, v.END_DATE_ACTIVE
FROM OKR_TEMPLATE_RGTS_V v
WHERE v.VAL_PTRT_ID = :p_ptrT_id
AND TRUNC(SYSDATE) BETWEEN NVL(v.START_DATE_ACTIVE, SYSDATE)
AND NVL(v.END_DATE_ACTIVE, SYSDATE);

Before deploying any such query, confirm the view is present in the target instance, since the ETRM metadata records it as not implemented. Where the view is absent, equivalent results must be assembled directly from OKR_TEMPLATE_RGTS_B and OKR_TEMPLATE_RGTS_TL.