Search Results insert_exhibits

Overview

PO_CLM_OKC_INTEG_PKG is a PL/SQL integration package in the APPS schema that bridges Oracle Purchasing (PO) with Oracle Contracts (OKC). Its name reflects its role: the CLM segment denotes Contracts Lifecycle Management functionality within Purchasing, while OKC_INTEG denotes integration with the Oracle Contracts Core schema. The package is classified as an OTHER API, meaning it is an internal integration utility rather than a public or user-facing API. It is a VALID object in the APPS schema across both Oracle EBS 12.1.1 and 12.2.2.

In practical terms, the package manages the lifecycle of contract-related purchasing documents by propagating exhibit information between Purchasing and Contracts, and by initiating workflow for the closeout of sourcing or contract documents. This integration is essential in procurement flows where contracts defined in OKC must be reflected as purchasing document exhibits, and where closeout of those documents must trigger a structured workflow process.

Key Procedures and Functions

Three documented procedures constitute the package interface:

• INSERT_EXHIBITS — Inserts exhibit records that link Purchasing documents with the associated Contracts data. This procedure ensures that exhibit details captured in the Contracts module are available as attachments or reference records on the corresponding purchasing document.
• DELETE_EXHIBITS — Removes previously inserted exhibit associations when the contract-to-purchasing linkage is dissolved or the exhibit is no longer applicable, maintaining data integrity between the two schemas.
• START_CLOSEOUT_WF_PROCESS — Initiates the Oracle Workflow closeout process for contract-related purchasing documents, driving the document through its closeout lifecycle and notifying participants as required.

Parameter lists are not documented in the ETRM metadata and must be validated against the deployed package source before use.

Tables Accessed

No database tables are directly documented as referenced by this package through APPS synonyms. However, dependency metadata shows it relies on the following PL/SQL collection types defined in the Purchasing schema: PO_TBL_NUMBER, PO_TBL_VARCHAR1, PO_TBL_VARCHAR30, and PO_TBL_VARCHAR240. These are standard PO table-with-collection types, typically used to pass bulk arrays of values into and out of APIs. Their presence confirms the package processes sets of records — most likely exhibit identifiers and descriptive attributes — in bulk rather than one row at a time.

Usage Notes

PO_CLM_OKC_INTEG_PKG is not intended to be called directly by end users. It is invoked indirectly by higher-level Contracts packages. The metadata identifies two dependent packages: OKC_CDRL_PVT (contract deliverables integration) and OKC_REP_CLOSEOUT_PVT (contract repository closeout). These are the primary drivers — when a contract deliverable or closeout action occurs in OKC, it calls into PO_CLM_OKC_INTEG_PKG to synchronize exhibits and/or launch the closeout workflow.

Because the package is classified as OTHER, customizations should treat it as an internal dependency rather than a supported extension point. Any direct invocation from custom code should be avoided in favour of using the documented OKC contract APIs, which manage the sequencing and error handling around these calls. When troubleshooting contract-to-purchasing integration issues, validate the package status in the APPS schema and inspect the dependent OKC packages for the calling context.