Search Results sts_id

Overview

OKR_K_STS_NOTIF_ROLES_V is a database view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 product family OKR – Contracts for Rights. The view is described authoritatively as a “View for OKR_KSTS_NOTIF_ROLES table,” meaning its sole function is to expose the columns of the underlying notification-roles table to reporting, integration, and dependent application logic layers. The view text shows a straightforward one-to-one projection from the base table (aliased KSTNR) with no joins, filters, aggregates, or computed expressions beyond the standard ROWID exposure.

In the EBS architecture, such views typically serve as a stable interface that shields consumers from direct table access and permits column renaming or derivation without breaking dependent code. This explains a subtle but important characteristic of the view: the selected column is KSTNR.ROWID, yet the catalogue lists the exposed column name as ROW_ID. Similarly, the STS_ID, CONTACT_ROLE, and other base columns are exposed unchanged. This naming convention signals that the view was designed as a formal published interface rather than an ad hoc query aid.

A critical documented fact is the status “Not implemented in this database.” In the ETRM documentation context, this indicates that OKR_K_STS_NOTIF_ROLES_V is referenced in the metadata repository of the obsolete OKR module but is not instantiated in the environment from which the documentation was generated, and the referenced base objects list is empty. Consequently, the view should be treated as a legacy or dormant object. Its practical significance in 12.1.1 and 12.2.2 is therefore mostly informational: it documents the historical structure of notification-role configuration within Contracts for Rights.

Underlying Base Objects

The single documented base object is the table OKR_K_STS_NOTIF_ROLES, referenced through the alias KSTNR. The view text is a pure SELECT … FROM OKR_K_STS_NOTIF_ROLES KSTNR with no additional joins, unions, or subqueries. No other tables are documented as referenced base objects, and the ETRM metadata explicitly states “Referenced base objects: none documented,” which is consistent with the view being non-instantiated. The relationship between the view and the table is strictly one-to-one: every row and every mapped column of the table appears in the view, preserving ROWID for row identification and including the complete set of fifteen descriptive flexfield columns (ATTRIBUTE_CATEGORY through ATTRIBUTE15).

Key Columns

• ROW_ID – The ROWID of the underlying OKR_K_STS_NOTIF_ROLES row, exposed from KSTNR.ROWID; used for direct row addressing in correction or purge scripts.
• ID – Primary key of the notification-role record.
• STS_ID – Foreign key to the status (STS) definition that the notification role applies to.
• CONTACT_ROLE and PARTY_ROLE – The role context for the notification. PARTY_ROLE is the column most relevant to the user search term “party_role” and identifies the trading-partner role (for example, buyer or seller) associated with the contact-role assignment.
• CONTACT_RESOURCE – The specific contact resource designated to receive or be associated with the notification.
• BUY_OR_SELL – Directional indicator distinguishing buy-side from sell-side notification roles.
• START_DATE_ACTIVE / END_DATE_ACTIVE – Effective dating that governs when the role assignment is valid, enabling date-effective reporting of historical and current assignments.
• OBJECT_VERSION_NUMBER – Optimistic locking control used by the underlying ADF/BC4J business components.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS who-column audit attributes.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – The full descriptive flexfield (DFF) context and segment columns.

Common Use Cases and Queries

The view supports reporting and integration patterns typical of EBS role and notification configurations: resolving which contact receives notifications for a given status, role, and buy/sell direction; auditing party-role assignments by effective dates; and extracting data for integration with trading-partner or contract-management systems. Because the object is documented as not implemented, the sample query below should be validated against the target environment before use.

SELECT row_id, id, sts_id, contact_role, party_role, contact_resource, buy_or_sell, start_date_active, end_date_active FROM okr_k_sts_notif_roles_v WHERE party_role = :p_party_role AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));

A second common pattern audits effective-dated role assignments for flexibility. Given that the object is obsolete and not instantiated, DBAs should confirm existence in ALL_VIEWS or DBA_VIEWS and prefer querying the base table OKR_K_STS_NOTIF_ROLES where the view is unavailable. Documentation-specific metadata confirms ROW_ID column exposure, confirming the view was formally catalogued rather than defined only in code.