Search Results mute_signer

Overview

OKC_ASYNC_PVT is a private (PVT) PL/SQL package in the APPS schema that provides the asynchronous workflow infrastructure for Oracle Contracts (OKC) in Oracle E-Business Suite 12.1.1 and 12.2.2. Its central responsibility is launching, routing, and resolving Oracle Workflow (WF) processes on behalf of contract-related APIs. Rather than embedding workflow logic directly in each business API, the Contracts modules call OKC_ASYNC_PVT to start a workflow item, deliver notifications to performers, and process the performer's response (accept, reject, timeout, or informational acknowledgement) asynchronously. This decouples long-running or human-driven approval steps from the calling form or concurrent program, allowing the contract transaction to proceed while the workflow engine handles routing and notification. Because the package is classified PVT, it is not part of the supported public API surface; it is invoked internally by the OKC product family and by the small number of packages documented as referencing it.

Key Procedures and Functions

The package exposes twenty documented procedures and functions. The core entry points are WF_CALL and RESOLVER_CALL, both of which accept standard API parameters (p_api_version, p_init_msg_list, x_return_status, x_msg_count, x_msg_data). WF_CALL starts a workflow process dynamically, optionally executing a PL/SQL procedure during the call, and passes notification and workflow-attribute data needed to construct the item. RESOLVER_CALL starts a resolver-style workflow in which the recipient chooses among accept, reject, or timeout outcomes.

The remaining routines support the callback and control side of that flow:

• SELECTOR — determines which workflow process or branch applies.
• ACCEPT, REJECT, TIMEOUT, TIME_OVER, PERIODIC — callback handlers that drive the workflow to its next activity based on the performer's action or elapsed time.
• GET_VERSION, GET_DOC, FUN_GENERIC, LOOP_CALL — utility routines for version retrieval, document or attribute lookup, generic function dispatch, and repeated invocation.
• SUCCESS_MUTE, ERROR_MUTE, FYI_MUTE, NO_EMAIL, MUTE_NXT_PFMR, MUTE_K_ADMIN, MUTE_SIGNER, UNMUTE — notification suppression controls. These routines mute or unmute workflow notifications for specific recipient roles (next performer, contract administrator, signer) or suppress e-mail delivery and success/error/FYI notifications, which is the context in which the SUCCESS_MUTE routine in particular is referenced.

Tables Accessed

The package reads and writes several workflow and contracts tables through APPS synonyms. WF_NOTIFICATIONS and WF_ITEM_ATTRIBUTES are the primary workflow tables manipulated when notifications are created, muted, or updated with item attribute values. OKC_WF_NOTIFY_S1 is a Contracts-specific workflow notification staging table. Contract header data is read from OKC_K_HEADERS_B and OKC_K_HEADERS_ALL_B to derive notification content and routing. FND_USER resolves performer identity, while FND_CONCURRENT_PROGRAMS and FND_CONCURRENT_REQUESTS support any concurrent-processing context. FND_LANGUAGES and NLS_SESSION_PARAMETERS supply language and NLS settings for message rendering, DUAL supports trivial queries, and PLITBLM is used for PL/SQL index-by table handling.

Usage Notes

OKC_ASYNC_PVT is invoked internally by Contracts business APIs and by the three packages documented as referencing it. It is not called directly from Oracle Forms or concurrent programs by customers; instead, contract approval, signature, and notification scenarios trigger it indirectly. Customizations that need to alter workflow notification behavior — for example, to suppress e-mail for a particular performer or to mute success notifications — should be implemented through the supported notification configuration rather than by calling these private routines directly, since the PVT classification means the interface may change between releases.