Search Results okx_launchpad_inbox_v




Overview
Explore in AI Chat

Overview

OKX_LAUNCHPAD_INBOX_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKX – Contracts Integration product family. Its documented purpose is the presentation of message notifications, and it functions as a filtered, presentation-ready projection over the Oracle Workflow notification tables rather than as a transactional object in its own right. The view is valid and available in both 12.1.1 and 12.2.2.

The view exists to support the Launchpad-style inbox experience for Oracle Contracts. It restricts Workflow notifications to those relevant to contract approval and contract change-request approval workflows, adds contract-specific metadata (contract number, modifier, and contract identifier), and translates internal status codes into user-facing meanings. Because the view derives its content from Workflow and Contracts tables, it is read-only by design; no DML is performed against it.

The column name recipient_role, which prompted the original search, is a direct pass-through of WF_NOTIFICATIONS.RECIPIENT_ROLE. In Workflow, this attribute normally carries a role name to which a notification is addressed. This view joins the notification's recipient to FND_USER on the user name, so notifications become attributable to a concrete application user record.

Underlying Base Objects

The documented base objects referenced by the view are:

  • WF_NOTIFICATIONS (synonym) — the primary notification store; supplies notification identifier, group, message type and name, recipient role, status, priority, dates, and user comment.
  • WF_LOOKUPS_TL (synonym) — the translated lookup values for lookup type WF_NOTIFICATION_STATUS, supplying the human-readable STATUS meaning.
  • FND_USER (synonym) — the application user directory, joined to the notification's recipient role to resolve USER_ID.
  • OKC_PROCESS_DEFS_B (synonym) — the Contracts process definitions, used as a subquery filter to limit notifications to Workflow processes whose PDF_TYPE is 'WPS' and whose usage is 'APPROVE' or 'CHG_REQ_APPROVE'.
  • OKC_QUERY (package) — invoked as OKC_QUERY.GETKNUMBER, GETKMODIFIER, and GETKID to resolve contract context for each notification.
  • WF_NOTIFICATION (package) — invoked as GETSUBJECT and GETSHORTBODY to render the notification subject and message body.

The join between WF_NOTIFICATIONS and WF_LOOKUPS_TL is constrained by LANGUAGE = USERENV('LANG'), ensuring status descriptions appear in the session language. The message-type filter is a UNION of qualifying contract process workflow names and the literal 'OKCALERT', so contract alerts flow into the same inbox as approval notifications.

Key Columns

  • NOTIFICATION_ID — unique identifier of the Workflow notification; the principal key for joining to other Workflow objects.
  • GROUP_ID — Workflow notification group, used to correlate related notifications.
  • USER_ID — application user resolved from FND_USER; identifies the actual recipient rather than the role string.
  • MESSAGE_TYPE / MESSAGE_NAME — the Workflow message type and message name that generated the notification.
  • RECIPIENT_ROLE — the Workflow role name to which the notification was addressed, joined to FND_USER.USER_NAME.
  • STATUS / STATUS_CODE — the translated lookup meaning and the raw Workflow status code respectively.
  • PRIORITY, BEGIN_DATE, END_DATE, DUE_DATE, USER_COMMENT — standard notification attributes for triage and aging.
  • SUBJECT and MESSAGE — rendered via the WF_NOTIFICATION package functions, giving displayable text.
  • CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER, CONTRACT_ID — contract context resolved by OKC_QUERY, allowing each notification to be tied back to a specific contract.
  • DUMMY_SORT — a constant value of 1, included to provide a stable sort key for the inbox presentation.

Common Use Cases and Queries

The view is typically used to build or troubleshoot contract approval inboxes, to audit which users hold outstanding approval notifications, and to correlate notifications with contracts.

  • Open notifications for a specific user by role name:

SELECT notification_id, subject, status, due_date FROM okx_launchpad_inbox_v WHERE recipient_role = :user_name AND status_code = 'OPEN';

  • Aging report of pending contract approvals by contract:

SELECT contract_number, contract_number_modifier, recipient_role, due_date FROM okx_launchpad_inbox_v WHERE status_code = 'OPEN' ORDER BY due_date;

  • Count of notifications per recipient to identify overloaded approvers:

SELECT recipient_role, COUNT(*) FROM okx_launchpad_inbox_v GROUP BY recipient_role ORDER BY 2 DESC;

Because the view calls packaged functions for subject and body, and executes a subquery against OKC_PROCESS_DEFS_B, queries should restrict on indexed and selective predicates such as recipient_role, status_code, or date range to avoid unnecessary function invocations. The view is appropriate for reporting and integration reads but must not be modified, since it is an APPS-owned, Oracle-delivered object.