Search Results proc_msg_call
Overview
OKC_ASYNC_PUB is a public PL/SQL package owned by APPS in Oracle E-Business Suite, shipped as part of the Oracle Contracts (OKC) application module. The package provides a set of utility entry points for asynchronous and deferred execution of PL/SQL logic, for controlled termination of previously scheduled work, and for generating workflow-based notifications and document dispatches. Its source header (OKCPASNS.pls 120.1) indicates the package has been stable since release 12.0 and remains present in both 12.1.1 and 12.2.2.
The central design intent is to let contract-related business logic run outside the immediate transaction context. Instead of blocking a form or concurrent request while long-running or recurring work executes, the calling program hands the code, a period, and a stop date to OKC_ASYNC_PUB. The package registers the request and returns a key that the caller can use later to cancel or reschedule it. A second responsibility is notification: the package sends messages to workflow roles, typically in support of contract approvals, expiry alerts, and launchpad-driven navigation into a contract record.
Key Procedures and Functions
- PROC_CALL — Asynchronous execution of PL/SQL code. Accepts the code to execute, an optional execution period in days, and a stop date through which scheduled execution should continue; returns a key used later for cancellation.
- PROC_STOP — Stops, or changes the stop date of, a scheduled execution previously registered by PROC_CALL. The key issued by PROC_CALL identifies the target; when no new stop date is supplied, execution stops immediately.
- PROC_MSG_CALL — Convenience entry point combining the asynchronous scheduling path with message notification, allowing a notification to be raised as part of a scheduled call.
- MSG_CALL — Sends a notification to a recipient identified as a workflow role. Supports a message subject, a message body, an internal notification name (or launchpad notification type), and a contract identifier used to navigate from a launchpad to the contract.
- RESOLVER_CALL — Invokes the notification resolver logic, resolving the appropriate recipient or notification definition before delivery.
- SEND_DOC — Dispatches a document as part of the notification or delivery flow.
- LOOP_CALL — Drives repeated or looped invocation of a call, supporting recurring execution registered through PROC_CALL.
All procedures follow the standard Oracle API convention: p_api_version, p_init_msg_list, and the x_return_status, x_msg_count, x_msg_data output triplet, so callers can apply uniform error handling.
Tables Accessed
OKC_ASYNC_PUB accesses three objects through APPS synonyms: OKC_WF_NOTIFY_S1, WF_ITEMS, and DUAL. OKC_WF_NOTIFY_S1 is the Contracts workflow notification staging table, where notification rows generated by MSG_CALL and related procedures are held before/while the workflow notification framework picks them up. WF_ITEMS is the Oracle Workflow runtime table used to enqueue and track notification items and their delivery status. DUAL is used for simple expression evaluation as part of PL/SQL execution. No direct base-table DML beyond these objects is documented.
Usage Notes
The package is a public API (classification PUB), so it is intended to be called from custom code and from other Oracle Contracts packages; the ETRM metadata records seven packages referencing it. Typical callers are contract form handlers, contract-related concurrent programs, and launchpad notification logic. The proc_msg_call search term maps to the PROC_MSG_CALL procedure, which is the documented entry point for combining scheduled execution with notification delivery. Customizations should supply p_api_version, check x_return_status after each call, and retain the x_key_to_stop value returned by PROC_CALL so that scheduled work can be cancelled through PROC_STOP. Because recurring execution is driven by a period and a stop date, any cleanup logic should explicitly stop outstanding schedules to avoid orphaned executions after the source transaction changes.
-
PACKAGE: APPS.OKC_ASYNC_PUB
12.2.2
-
PACKAGE: APPS.OKC_ASYNC_PUB
12.1.1
-
PACKAGE BODY: APPS.OKC_ASYNC_PUB
12.2.2
-
PACKAGE BODY: APPS.OKC_ASYNC_PUB
12.1.1
-
APPS.OKC_RENEW_PVT dependencies on OKC_ASYNC_PUB
12.2.2
-
APPS.OKC_RENEW_PVT dependencies on OKC_ASYNC_PUB
12.1.1
-
APPS.OKC_ASYNC_PUB dependencies on OKC_ASYNC_PUB
12.2.2
-
APPS.OKC_ASYNC_PUB dependencies on OKC_ASYNC_PUB
12.1.1
-
APPS.OKC_ASYNC_PUB dependencies on OKC_ASYNC_PVT
12.1.1
-
APPS.OKC_ASYNC_PUB dependencies on OKC_ASYNC_PVT
12.2.2
-
PACKAGE BODY: APPS.OKC_RENEW_PVT
12.1.1
-
PACKAGE BODY: APPS.OKC_RENEW_PVT
12.2.2
-
APPS.OKC_RENEW_PVT dependencies on OKC_DEBUG
12.1.1
-
APPS.OKC_RENEW_PVT dependencies on OKC_DEBUG
12.2.2
-
APPS.OKC_RENEW_PVT dependencies on OKC_API
12.1.1
-
APPS.OKC_RENEW_PVT dependencies on OKC_API
12.2.2