Search Results proc_stop

Overview

OKC_ASYNC_PUB is a public PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that provides asynchronous execution services for the Oracle Contracts (OKC) module. Its principal business purpose is to allow contract-related PL/SQL code to be invoked on a deferred, scheduled basis rather than synchronously within the calling session. This is accomplished by submitting arbitrary PL/SQL blocks as Workflow background items using the standard WF_ITEMS infrastructure, with scheduling controlled by period and stop-date parameters. The package also supports notification delivery through the Workflow notification tables, allowing contract events to generate messages to Workflow roles. In releases 12.1.1 and 12.2.2 the package is shipped under the APPS schema with a PUB API classification, indicating it is intended for external invocation by other EBS components and customer extensions. The package header carries the version identifier 120.1 and is marked "noship."

Key Procedures and Functions

• PROC_CALL — Submits a PL/SQL block for asynchronous execution. The caller supplies the code to be executed as a string, an optional execution period expressed in days, and an optional stop date that is truncated to the day. The procedure returns a key that identifies the scheduled job and can subsequently be used to stop or reschedule it.
• PROC_STOP — Stops or changes the stop date of a previously scheduled asynchronous execution. It accepts a new stop date, truncated to the day, and the key issued by PROC_CALL. A default stop date results in immediate termination of the scheduled execution.
• MSG_CALL — Sends a Workflow notification. The caller specifies a recipient expressed as a Workflow role, a message subject and body, an optional notification type used for Oracle Launchpad integration, and a contract identifier used to navigate from Launchpad to the relevant contract record. Remaining parameters are reserved for future use.
• PROC_MSG_CALL — A combined entry point that pairs asynchronous procedure execution with notification delivery.
• RESOLVER_CALL — Supports resolution processing driven by the asynchronous framework.
• SEND_DOC — Handles document delivery as part of the asynchronous processing set.
• LOOP_CALL — Manages iterative or looping asynchronous execution behavior.

All documented procedures follow the standard EBS public API convention, accepting p_api_version and p_init_msg_list inputs and returning x_return_status, x_msg_count, and x_msg_data outputs.

Tables Accessed

The package accesses OKC_WF_NOTIFY_S1, the Contracts Workflow notification sequence, to generate unique identifiers for notification records. WF_ITEMS is the core Workflow table in which deferred executions are queued; the package inserts and manages entries here to achieve scheduled execution via PROC_CALL and to update or remove them via PROC_STOP. DUAL is used for standard single-row queries and assignments. These three tables are referenced through APPS synonyms, consistent with the package's location in the APPS schema.

Usage Notes

OKC_ASYNC_PUB is typically invoked from Oracle Forms, concurrent programs, or custom PL/SQL code within the Contracts module when a task must not block the user session — for example, long-running contract validation, document generation, or notification dispatch. The documented package metadata lists seven packages that reference OKC_ASYNC_PUB, confirming its role as a shared utility within the OKC dependency chain. Because the package is classified PUB, it is supported for direct customer calls. Any invocation must observe the mandatory API parameters, and callers should retain the key returned by PROC_CALL so that PROC_STOP can later modify or cancel the scheduled execution.