Search Results okc_rep_wf_pvt




Overview
Explore in AI Chat

Overview

OKC_REP_WF_PVT is a private PL/SQL package body in the APPS schema that supports the Oracle E-Business Suite Contract Lifecycle Management workflow approval infrastructure. In EBS 12.1.1 and 12.2.2, the package belongs to the Oracle Contracts (OKC) module family, specifically the repository (OKC_REP) objects that manage contracts authored through Contract Terms and Oracle Approvals Management (AME). The package acts as the runtime bridge between the Contracts repository and the Oracle Workflow Engine, orchestrating approval and rejection processing, AME status synchronization, and workflow notification completion for contract approval hierarchies. Because it is classified as a PVT package, its entry points are not exposed as public APIs; they are invoked internally by workflow activity functions, the contract approval engine, and sibling package OKC_REP_UTIL_PVT.

Key Procedures and Functions

The documented interface exposes sixteen procedures and functions that fall into several functional groups:

Tables Accessed

The package reads and writes the following tables through APPS synonyms: OKC_REP_CONTRACTS_ALL and OKC_REP_CONTRACT_VERS store the contract repository rows and versions updated during approval; OKC_REP_CON_APPROVALS holds the approval history records; OKC_CONTRACT_DOCS and OKC_BUS_DOC_TYPES_B support the contract document and business document type logic used by CON_ATTACH_GENERATED_YN and CONTRACT_PREVIEW_YN; WF_ITEMS and WF_NOTIFICATIONS are used to read and update workflow item state and notification status; FND_USER is consulted to resolve the acting user; and the HR tables PER_ALL_PEOPLE_F, PER_ALL_ASSIGNMENTS_F, PER_ASSIGNMENT_STATUS_TYPES, together with JTF_RS_RESOURCE_EXTNS, are used to resolve approver identities and resource information for AME integration. PLITBLM is referenced for PL/SQL table operations.

Usage Notes

OKC_REP_WF_PVT is not a publicly callable API and is not referenced by any other database object. It is invoked indirectly when a contract is submitted into the AME approval workflow: the Workflow Engine calls the activity functions within this package through contract approval workflow definitions, and the package in turn calls AME_API2, AME_API6, AME_UTIL, AME_UTIL2, FND_API, FND_GLOBAL, FND_LOG, FND_NUMBER, OKC_API, OKC_REP_UTIL_PVT, OKC_TERMS_UTIL_GRP, WF_CORE, WF_DIRECTORY, WF_ENGINE, WF_NOTIFICATION, and WF_NOTIFICATIONS. Because these are internal entry points, customizations should not call the procedures directly; instead, integrators should extend behavior through supported OKC APIs and Workflow Builder configuration. Debugging typically involves examining FND_LOG output and WF_NOTIFICATIONS rows produced during approval processing.