Search Results launch_outcome

Overview

OKC_OUTCOME_INIT_PVT is a private PL/SQL package in the APPS schema that forms part of the Oracle Contracts (OKC) outcome-processing infrastructure. Its role is to initialize and launch the execution of contract outcomes — the tasks, deliverables, or workflow actions that result from evaluating contract terms and conditions. In Oracle EBS 12.1.1 and 12.2.2, outcome processing is a core component of the Contracts Core (formerly ETRM) module, allowing a contract's terms to drive downstream business activity such as approval routing, fulfillment tracking, and deliverable generation.

As an API classification "PVT" (private) package, OKC_OUTCOME_INIT_PVT is not intended for direct invocation by external callers. It exposes internal program units consumed primarily by OKC_AQ_PVT, which relies on it during outcome launching operations. The documented dependency list confirms that OKC_OUTCOME_INIT_PVT is referenced by OKC_AQ_PVT, OKC_CONDITION_EVAL_PVT, OKC_WF, and itself, placing it at the intersection of condition evaluation, workflow integration, and advanced queue processing within the OKC module.

Key Procedures and Functions

• LAUNCH_OUTCOME — Initiates processing for a contract outcome, coordinating the initialization logic required before the outcome is executed.
• LAUNCH_PLSQL — Handles the PL/SQL-based launch path for outcomes implemented as stored procedures or packaged APIs rather than workflow processes.
• LAUNCH_WORKFLOW — Handles the workflow-based launch path, submitting an outcome as an Oracle Workflow process when the outcome definition specifies workflow execution.
• SUBMIT_DA_WF_MGR — Submits the Deliverables and Approvals (DA) workflow manager processing, integrating outcome launch with the deliverables/approval workflow framework.

These four program units collectively provide the dispatching layer that determines how a given outcome should be materialized — as inline PL/SQL or as a submitted workflow process.

Tables Accessed

• FND_PROFILE_OPTIONS, FND_PROFILE_OPTION_VALUES — Read to resolve site, application, responsibility, or user profile option values that control outcome processing behavior.
• FND_USER — Consulted to identify the user context or workflow initiator associated with a launch action.
• JTF_RS_RESOURCE_EXTNS — Used to resolve resource records (for example, owner or assignee details) tied to outcome execution.
• OKC_WF_OUTCOME_S1 — Provides sequence generation for workflow outcome records.
• OKS_DA_INTERFACE_B and OKS_DA_INTERFACE_S — Base and secondary interface tables used to stage deliverable/approval data for submission to the DA workflow manager.
• DUAL — Standard single-row utility table used for lightweight queries.
• PLITBLM — The standard PL/SQL table/array maintenance package used for collection handling.

It also references OKC_PROCESS_DEF_PARAMETERS_V, OKC_API, OKC_AQ_PVT, and FND_API, reflecting its dependence on Contracts API utilities and application framework services.

Usage Notes

Because OKC_OUTCOME_INIT_PVT is a private package, standard practice is not to call it directly from custom code. It is invoked internally by OKC_AQ_PVT during advanced queue-driven outcome processing, by OKC_CONDITION_EVAL_PVT after a condition is satisfied, and by OKC_WF during workflow step execution. Customizations requiring outcome launch should use the public OKC APIs (for example OKC_API) instead. On both 12.1.1 and 12.2.2, modifications should be limited to extensions layered through supported APIs, since the package's internal signatures are subject to change without notice.