Search Results chg_req_approve

Overview

APPS.OKX_LAUNCHPAD_INBOX_V is a valid, internal Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as OKX.OKX_LAUNCHPAD_INBOX_V. It presents a consolidated, user-scoped inbox of workflow notifications relevant to the Oracle Contracts (OKX/OKC) Launchpad, exposing notification routing, status, priority, and contract context in a single relational structure. The view is classified as View Type "Internal," and Oracle explicitly warns that it is intended for internal use only and is not supported for direct data access outside standard Oracle Applications programs.

Its principal role is to drive the Contract Launchpad notification worklist, allowing the application to render each user's pending and processed notifications alongside the governing contract identifier and number. It supports reporting and integration scenarios where notification activity must be correlated with contracts without navigating the underlying Workflow notification tables directly.

Underlying Base Objects

The documented dependencies of OKX_LAUNCHPAD_INBOX_V are:

• FND_USER (synonym) — supplies application user identity and joins to USER_ID.
• WF_NOTIFICATIONS (synonym) — the core workflow notification store, supplying notification identifiers, status, dates, subject, and message.
• WF_NOTIFICATION (package) — provides notification attributes and derived values.
• WF_LOOKUPS_TL (synonym) — resolves QuickCode meanings such as STATUS.
• OKC_PROCESS_DEFS_B (synonym) — contract process definitions used to bind notifications to contracts.
• OKC_QUERY (package) — supplies contract query logic and contract lookups.

Because the view is defined over WF_NOTIFICATIONS, it inherits Workflow's notification lifecycle, including status transitions from OPEN through CLOSED or CANCELED. The contract-oriented columns are populated through the OKC objects, tying each notification to a contract number, modifier, and contract identifier.

Key Columns

• NOTIFICATION_ID — unique notification identifier; primary correlation key to WF_NOTIFICATIONS.
• GROUP_ID — groups related notifications.
• USER_ID — application user receiving the notification (joins to FND_USER).
• MESSAGE_TYPE / MESSAGE_NAME — item type and internal message name defining the notification's origin.
• RECIPIENT_ROLE — role of the recipient of the notification.
• STATUS / STATUS_CODE — QuickCode meaning and code representing the notification state.
• PRIORITY — numeric priority (1–100) used for ordering within the inbox.
• BEGIN_DATE / END_DATE / DUE_DATE — start, completion, and reply-by dates.
• USER_COMMENT, SUBJECT, MESSAGE — free-text notification content.
• CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER, CONTRACT_ID — contract context for the notification.
• DUMMY_SORT — internal sort helper column.

Common Use Cases and Queries

The view is used to list a user's contract-related notifications, to filter open items by priority or due date, and to correlate notification activity back to a specific contract. A representative query is:

• SELECT notification_id, user_id, status, priority, subject, contract_number FROM apps.okx_launchpad_inbox_v WHERE user_id = :p_user_id AND status_code = 'OPEN' ORDER BY priority, due_date;
• SELECT contract_id, contract_number, COUNT(*) FROM apps.okx_launchpad_inbox_v GROUP BY contract_id, contract_number;
• SELECT notification_id, subject, due_date FROM apps.okx_launchpad_inbox_v WHERE due_date < SYSDATE AND status_code = 'OPEN';

Because the object is marked Oracle Internal Use Only, any custom query should be restricted to read-only reporting and validated against standard Contracts functionality before operational reliance.