Search Results launch_plsql

Overview

OKC_OUTCOME_INIT_PVT is a private (PVT-classified) PL/SQL package body in the Oracle E-Business Suite Contracts (OKC) module. Its central business function is to evaluate and execute the outcome associated with a contract or deliverable event. In the ETRM/Contracts architecture, an "outcome" defines what should happen when a business condition or lifecycle event is satisfied: either a PL/SQL program unit is executed directly, or a workflow process is launched to route the event for approval, notification, or downstream processing. This package provides the plumbing that dispatches those outcomes.

The primary entry point, Launch_outcome, accepts a correlation record and a message table, then resolves the configured outcome into its concrete action. Internally it branches into one of two execution paths — a PL/SQL procedure invocation or a workflow initiation — as reflected by the helper routines LAUNCH_PLSQL and LAUNCH_WORKFLOW. The package also reads profile options to determine recipients and context before performing the launch. The header comment (Version 1.0) and the launch_outcome API version constant (1.0) confirm this is the original, stable interface.

Key Procedures and Functions

• LAUNCH_OUTCOME — The main driver. It resolves the outcome definition, iterates over the outcome table, and delegates execution either to a PL/SQL call or a workflow launch. It returns standard API status, message count, and message data through its OUT parameters, and honors the FND_API initialization flag.
• LAUNCH_PLSQL — Executes the configured PL/SQL procedure associated with an outcome. It is the branch used when the outcome is defined as a stored program unit rather than a workflow, and it isolates the dynamic PL/SQL invocation logic from the dispatcher.
• LAUNCH_WORKFLOW — Initiates the workflow process tied to an outcome. This path is used when the outcome requires human routing, notifications, or multi-step business flow via Oracle Workflow.
• SUBMIT_DA_WF_MGR — Submits the Deliverables/DA workflow manager process, coordinating workflow execution with the Deliverables Application (OKS) interface records.

Tables Accessed

The package references the following objects through APPS synonyms:

• FND_PROFILE_OPTIONS and FND_PROFILE_OPTION_VALUES — read to resolve profile option settings such as the OKC_S_RECIPIENT recipient configuration used to determine notification targets.
• FND_USER — used to resolve user identity for recipients or workflow routing.
• JTF_RS_RESOURCE_EXTNS — provides resource/party details (resource extension data) for recipient resolution.
• OKC_WF_OUTCOME_S1 — the Contracts workflow outcome sequence/view supplying outcome definitions and identifiers.
• OKS_DA_INTERFACE_B and OKS_DA_INTERFACE_S — the Service/Deliverables interface base and staging tables used when submitting the DA workflow manager.
• DUAL — standard single-row utility select.
• PLITBLM — an internal helper table used for message/log handling (commonly associated with debug/trace utilities).

Usage Notes

OKC_OUTCOME_INIT_PVT is a private package and is not intended to be called directly by external integrations; it is invoked internally by public Contracts APIs and by the outcome-processing framework when a lifecycle event fires. Because the user search term was "launch_plsql," the most relevant reference is the LAUNCH_PLSQL routine, which is the internal dispatcher that executes the PL/SQL branch of an outcome. The package is referenced by three other packages and is typically triggered from contract lifecycle processing, concurrent outcome programs, or workflow-driven events rather than from Forms directly. When troubleshooting outcome behavior in 12.1.1 or 12.2.2, enable FND debug (AFLOG_ENABLED) since the source initializes l_debug from that profile, and inspect the message stack returned via x_msg_count and x_msg_data.