Results for “awn_id”

6 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKR_IP_AWDS_WON_V is a reporting and integration view within the Oracle E-Business Suite OKR (Contracts for Rights) module, which falls under the Oracle E-Records and intellectual property management family of applications. The view is documented as obsolete and, per the ETRM metadata, is not implemented in the reference database environment. It exposes the award records stored in the base table OKR_AWDS_WON_B, joined to its translation table OKR_AWDS_WON_TL, and presents a flattened, user-facing projection of awards won in the context of contracts for rights, typically related to intellectual property and royalty agreements.

Functionally, the view serves as a denormalized access layer: consumers query the view rather than the underlying base and translation tables directly, thereby benefiting from the built-in language filter and the consistent set of exposed columns. Because it is not implemented in the environment referenced by the metadata, any deployment or migration effort must verify the presence of the underlying tables before relying on the view.

Underlying Base Objects

The view is defined over two documented base objects:

  • OKR_AWDS_WON_B — the base table holding the awards-won records, aliased AWNBB in the view text. This table contributes the majority of the view's columns, including the primary key AWN_ID, descriptive attributes, and the standard Oracle EBS audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN).
  • OKR_AWDS_WON_TL — the translated table, aliased AWNBT, which supplies language-dependent content such as SFWT_FLAG and COMMENTS.

The two tables are joined on AWN_ID, with the translation restricted by the condition AWNBT.LANGUAGE = USERENV('LANG'). This ensures the view returns only the row matching the session's current language, one translation row per award identifier.

Key Columns

  • AWN_ID — primary identifier for the award record; the join key between base and translation tables.
  • PARTY_ID1 — identifier of the first party associated with the award, typically the awarding or owning organization.
  • PARTY_ID2 — identifier of the second party associated with the award, typically the counterparty, licensee, or recipient. This column is the direct source of the "party_id2" search term.
  • IP_ID — reference to the intellectual property record to which the award pertains.
  • AWARD_CODE — code identifying the award, used for lookup and display.
  • AWARD_DATE — date on which the award was granted or recorded.
  • OBJECT_VERSION_NUMBER — supports optimistic locking in the underlying entity.
  • SFWT_FLAG and COMMENTS — language-dependent columns sourced from the translation table.
  • ROW_ID — the ROWID of the base table row, useful for direct row addressing.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard DFF (Descriptive Flexfield) segment columns for extensible customer-defined data.

Common Use Cases and Queries

Typical usage centers on retrieving award data for a given party or intellectual property record, particularly when the second party in a rights agreement must be identified. A representative query filtering on the searched column is:

  • SELECT AWN_ID, AWARD_CODE, PARTY_ID1, PARTY_ID2, IP_ID, AWARD_DATE FROM OKR_IP_AWDS_WON_V WHERE PARTY_ID2 = :party_id;

Because PARTY_ID2 is exposed directly, integration routines and concurrent programs can resolve the counterparty without joining back to the base table. Additional scenarios include:

  • Listing all awards for a property: SELECT AWARD_CODE, PARTY_ID1, PARTY_ID2 FROM OKR_IP_AWDS_WON_V WHERE IP_ID = :ip_id;
  • Auditing changes within a period using the audit columns.
  • Extracting flexfield data via ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 for downstream reporting.

Given the view's obsolete status, any reliance on it should be accompanied by a validation that both OKR_AWDS_WON_B and OKR_AWDS_WON_TL exist in the target environment and that the DBA data confirms implementation.