Results for “wf_notification_status”

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

Overview

OKR_LAUNCHPAD_INBOX_V is a reporting view within the Oracle E-Business Suite Contracts for Rights (OKR) module, an obsolete product line historically associated with rights and royalty contract management. The view functions as a specialized worklist ("Launchpad Inbox") that consolidates Oracle Workflow notification data with contract header context. Rather than exposing raw workflow tables directly, it joins notification records to their associated contract identifiers so that users and administrators can query pending or historical notifications in a business-meaningful form.

In the Oracle EBS 12.1.1 and 12.2.2 environments, this view is documented in the ETRM metadata as not implemented in the current database, meaning it is a legacy or product-specific object that may not exist in every instance. Its role is primarily read-only reporting and diagnostic: it surfaces workflow-driven approval or notification activity tied to Contracts for Rights documents. Because workflow notification tables are dense and technical, this view is the natural access point for integration and reporting efforts seeking notification records scoped to a particular contract.

Underlying Base Objects

The view is defined over a join of six documented base objects:

• WF_NOTIFICATIONS — the core Oracle Workflow notification table, supplying notification identity, status, priority, dates, and the recipient role.
• WF_NOTIFICATION_ATTRIBUTES — provides notification-level attributes; here it is filtered on NAME = 'CONTRACT_ID' to extract the contract reference.
• WF_MESSAGES_VL — the message definition view, joined by MESSAGE_NAME and MESSAGE_TYPE to resolve the notification's message template.
• WF_LOOKUPS_TL — translated lookup values, restricted to LOOKUP_TYPE = 'WF_NOTIFICATION_STATUS', used to convert the raw status code into a user-facing meaning.
• FND_USER — the application user table, joined so that user identity is resolved from the recipient role value.
• OKC_K_HEADERS_B — the contract headers base table, supplying CONTRACT_NUMBER and the contract identifier.

The join path requires that each notification carry a CONTRACT_ID attribute; the view then links that attribute to OKC_K_HEADERS_B.ID and further restricts results to header records where SCS_CODE = 'TDE_RIGHT', scoping the inbox to the rights-specific contract classification.

Key Columns

• NOTIFICATION_ID / GROUP_ID — unique notification and grouping identifiers from WF_NOTIFICATIONS.
• USER_ID — resolved FND_USER identifier corresponding to the recipient.
• MESSAGE_TYPE / MESSAGE_NAME — identify the workflow message template.
• RECIPIENT_ROLE — the workflow recipient role; notably the view joins this to FND_USER.USER_NAME, which is the column most relevant to a "recipient_role" search.
• STATUS — the translated meaning of the notification status lookup (for example, Open, Closed).
• PRIORITY, BEGIN_DATE, END_DATE, DUE_DATE, USER_COMMENT — scheduling and response metadata.
• SUBJECT, MESSAGE — computed subject text and a constant literal 'MESSAGE'.
• CONTRACT_NUMBER / CONTRACT_ID — the associated rights contract.
• DUMMY_SORT — a constant value of 1, provided for ordering convenience.

Common Use Cases and Queries

Typical usage involves locating notifications by recipient or contract, and monitoring outstanding workflow items.

To list open notifications for a specific contract:

• SELECT notification_id, recipient_role, status, subject, contract_number FROM okr_launchpad_inbox_v WHERE contract_number = :contract_number AND status = 'Open';

To find notifications routed to a particular recipient role:

• SELECT notification_id, contract_number, begin_date, due_date FROM okr_launchpad_inbox_v WHERE recipient_role = :user_name ORDER BY due_date;

Because the view is flagged as not implemented in the documented database, confirm its existence with a data dictionary query before relying on it in either release.