Search Results okc_change_request_pub




Overview
Explore in AI Chat

Overview

OKC_COR_PVT is a private PL/SQL package in the APPS schema that supports Oracle Contract Terms and Conditions (OKC) change management. It belongs to the OKC application family and is classified as a PVT (private) API, meaning it is intended for internal use by other OKC packages rather than for direct invocation by external or customer code. The package implements the core row-level logic for creating, versioning, and maintaining records that describe changes (change requests) applied to contracts and their associated terms and conditions.

The central business function served by OKC_COR_PVT is change request administration. In Oracle Contracts, change requests allow authorized users to propose, validate, and commit modifications to contract content while preserving an audit trail of prior states. OKC_COR_PVT provides the procedural engine that records these changes in the OKC_CHANGES base and translation tables, manages version identifiers, and enforces the row-level validation and locking discipline required for consistent change records. Because the package references FND_API and OKC_API, it participates in the standard Oracle EBS API framework.

Key Procedures and Functions

The documented package exposes the following procedures and functions:

  • QC — A quality-control (quick check) routine used to confirm that the package session or environment is properly initialized before the main API logic executes.
  • CHANGE_VERSION — Generates or advances the version identifier associated with a change request, ensuring each change iteration is uniquely numbered.
  • API_COPY — Duplicates an existing change or contract-terms record into a new row, supporting copy and rework scenarios.
  • ADD_LANGUAGE — Inserts translation rows for the specified language, maintaining multilingual support for change descriptions in OKC_CHANGES_TL.
  • INSERT_ROW — Performs the actual insert into the change tables, including the base table and its translation counterpart.
  • LOCK_ROW — Obtains a row-level lock to serialize concurrent modifications and prevent lost updates.
  • UPDATE_ROW — Applies changes to an existing change request row, including corresponding translation updates.
  • DELETE_ROW — Removes a change record from the change tables, including its translation rows.
  • VALIDATE_ROW — Executes the business validation rules that govern whether a change record is internally consistent and permissible before it is committed.

Tables Accessed

OKC_COR_PVT reads and writes the following documented objects, accessed through APPS synonyms:

  • OKC_CHANGES_B — The base table storing change request records; primary target of INSERT_ROW, UPDATE_ROW, and DELETE_ROW.
  • OKC_CHANGES_TL — The translation table holding language-specific text for change records; maintained by ADD_LANGUAGE and the language-aware insert/update logic.
  • OKC_CHANGES_V — A view over change data used for read validation and access.
  • OKC_CHANGE_REQUESTS_B — Base table for change requests that this package validates against or references when building change records.
  • FND_LANGUAGES — The Oracle Applications installed-languages table, consulted to determine valid languages for translation inserts.
  • PLITBLM — A standard Oracle EBS PL/SQL table type used internally for bulk or in-memory data handling.

Usage Notes

Because OKC_COR_PVT is a PVT package, it is not designed for direct invocation by application forms, concurrent programs, or custom code. It is invoked indirectly by the public and private OKC change request APIs. The ETRM metadata shows that OKC_COR_PVT is referenced by OKC_CHANGE_REQUEST_PUB (the public wrapper) and OKC_CHANGE_REQUEST_PVT (the private implementation), as well as by itself for internal calls. Users searching for "okc_change_request_pub" will therefore typically reach OKC_COR_PVT through that public API rather than calling it directly. Custom developers should use OKC_CHANGE_REQUEST_PUB and avoid customizing OKC_COR_PVT, since Oracle may change private package signatures during upgrades.