Search Results okc_wf




Overview
Explore in AI Chat

Overview

OKC_WF is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that provides the workflow integration layer for the Oracle Contracts (OKC) module. Its business purpose is to translate contract lifecycle events and transaction data into Oracle Workflow constructs, generating and executing the PL/SQL and attribute strings that drive contract-related workflow processes. The package abstracts the mechanics of workflow message construction — building headers, assembling attribute strings, and value-formatting — so that contract APIs can raise workflow events consistently. In EBS 12.1.1 and 12.2.2 the package is documented as VALID in the ETRM repository with an API classification of OTHER, indicating it is an internal utility supporting the Contracts family of modules rather than a public, customer-facing API.

Key Procedures and Functions

The documented program units fall into three functional groups. The workflow string lifecycle is handled by INIT_WF_STRING, which initializes a workflow attribute string; APPEND_WF_STRING, which adds further content to an existing string; BUILD_WF_STRING and PREBUILD_WF_PLSQL, which assemble the workflow string or the PL/SQL block that will later be executed; GET_WF_STRING, which retrieves the assembled string for downstream use; and INIT_WF_HEADER, which establishes the workflow header metadata. Execution is handled by BUILD_WF_PLSQL and EXEC_WF_PLSQL, which construct and then dynamically execute workflow-related PL/SQL.

Attribute value formatting is provided by three helper functions: NVALUE for numeric values, DVALUE for date values, and CVALUE for character values. These normalize Oracle datatypes into the string representationsthat workflow attributes require, applying appropriate conversions and quoting.

Tables Accessed

The only documented table reference is PLITBLM, an APPS synonym for a PUBLIC table (PLITBLM, in the SYS/PUBLIC namespace). PLITBLM is the standard Oracle Tools table for storing PL/SQL source text lines, and OKC_WF uses it in connection with its dynamic PL/SQL build and execute logic. No Contracts transactional tables are documented as directly referenced by this package; contract data reaches the package through calls to OKC_API and OKC_OUTCOME_INIT_PVT rather than through direct DML.

Usage Notes

OKC_WF depends on FND_API, FND_PROFILE, OKC_API, OKC_OUTCOME_INIT_PVT, and itself, and the ETRM metadata records that it is referenced by two other packages. It is not referenced by any database object such as a view or trigger, confirming its role as a callable internal service. Typical invocation occurs from Contracts forms and from contract workflow-enabled business flows (for example, contract approval, outcome, and notification processes) that must generate a workflow message or execute a workflow PL/SQL block. Customizations should treat OKC_WF as an internal, non-public interface: calling code should prefer supported contract APIs, and any direct use of the string-building and execute routines (particularly EXEC_WF_PLSQL, which performs dynamic execution) should be undertaken only with careful attention to inputs, since the package does not document a supported signature contract in the ETRM metadata.