Search Results oke_contract_pvt




Overview
Explore in AI Chat

Overview

OKE_CLE_PVT is a private PL/SQL package in the APPS schema that forms part of the Oracle E-Business Suite Contract Lifecycle Management / Enterprise Trading and Risk Management (ETRM) foundation. Its naming convention — the _PVT suffix — identifies it as an internal, non-public API layer that underpins the externally callable public APIs of the Contracts module. The package is classified as a Private (PVT) API within the ETRM 12.2.2 documentation set.

The business function of OKE_CLE_PVT centers on the creation and maintenance of contract line entities — specifically the integration between Oracle Contracts (OKE/OKC) contract lines and their associated project and billing attributes. It acts as a low-level data manipulation layer, providing atomic row-level operations (insert, update, delete, and validation) against the contract line and header base tables. By isolating these operations in a private package, Oracle preserves a stable public interface (for example, OKE_CONTRACT_PUB and OKE_CONTRACT_PVT) while allowing the private implementation to evolve. The package is recorded as VALID in the APPS schema and is a recognized dependency within the ETRM object hierarchy for both 12.1.1 and 12.2.2 releases.

Key Procedures and Functions

The documented package exposes eight procedures and functions. The principal documented entry points are the following four row-level operations:

  • INSERT_ROW — Inserts a new contract line record, populating the base table columns required to establish the line's identity and linkage to its parent header.
  • UPDATE_ROW — Modifies attributes of an existing contract line record, allowing changes to line-level details while preserving referential integrity with related entities.
  • DELETE_ROW — Removes a contract line record from the base table, typically invoked as part of a cascade or cleanup operation within a larger transaction.
  • VALIDATE_ROW — Performs business-rule validation on a prospective or existing line record, verifying that mandatory and cross-referenced fields are consistent before persistence proceeds.

The remaining exposed program units are not individually named in the documented metadata, but they follow the same private-API pattern of supporting row manipulation and validation for the contracts line model associated with the OKE_CLE family.

Tables Accessed

OKE_CLE_PVT references the following tables through APPS synonyms: OKE_K_LINES, MTL_CUSTOMER_ITEMS, OKC_ANCESTRYS, OKC_K_HEADERS_B, OKC_K_LINES_B, OKE_K_BILLING_METHODS, OKE_K_HEADERS, PA_PROJECTS_ALL, PA_TASKS, and PLITBLM.

The OKC_* and OKE_K_* tables represent the core Contracts repository — headers, lines, billing methods, and ancestry relationships that define the contract hierarchy. MTL_CUSTOMER_ITEMS links contract lines to inventory customer items, supporting service and trading line definitions. PA_PROJECTS_ALL and PA_TASKS connect contract lines to Oracle Projects, enabling project-associated contracting. PLITBLM is a standard Oracle identifier/PL-SQL helper structure used in row processing. Together these references confirm that the package bridges Contracts data with Projects and Inventory master data.

Usage Notes

Because OKE_CLE_PVT is a private package, it is not intended for direct invocation by customers or external integrations. The documented dependency list shows that it is referenced by OKE_CLE_PVT, OKE_CONTRACT_PUB (twice), OKE_CONTRACT_PVT (twice), OKE_IMPORT_CONTRACT_PUB, and OKE_KCOPY_PKG — four distinct calling packages. These callers invoke OKE_CLE_PVT during contract authoring flows (typically driven from the Contracts forms), bulk contract import (via OKE_IMPORT_CONTRACT_PUB), and contract copy operations (OKE_KCOPY_PKG). Custom code should always call the supported public API, OKE_CONTRACT_PUB, rather than OKE_CLE_PVT, and must be re-validated against both 12.1.1 and 12.2.2, since private signatures may change across patch levels.