Search Results oke_version_pub

Overview

OKE_VERSION_PUB is the public application programming interface (API) package for version management within the Oracle E-Business Suite Oracle Contracts (OKE) module. Its central business function is to enable controlled, auditable manipulation of contract versions so that procurement and contract administrators can capture negotiated changes without destroying the prior state of an agreement. The package operates in the standard Oracle EBS layering model: OKE_VERSION_PUB exposes the public entry points, delegates processing to the private layer OKE_VERSION_PVT, and follows the Oracle Application Object Library conventions for API design by initializing the message list and handling savepoints through FND_MSG_PUB and FND_API. The package body is owned by the APPS schema and is documented as VALID, meaning it compiles and is available for use as delivered. It is classified as a PUB API, which signals that the interface is intended for external invocation rather than internal-only consumption, and it is a supported integration point for customizations, extensions, and programmatic contract processing.

Key Procedures and Functions

The package body documents two public procedures:

• VERSION_CONTRACT — Creates a new version of an existing contract. This is the procedure invoked when a contract that has already been approved and active must be revised. It establishes the new version record derived from the current contract data so that amendments, renewals, or renegotiations can be performed against a controlled copy rather than the live document.
• RESTORE_CONTRACT_VERSION — Restores a previously captured contract version, returning the contract to an earlier state. This supports rollback scenarios where a versioned change must be undone and the prior terms reinstated.

The parameter lists are not reproduced here. The procedures rely on OKE_VERSION_PVT for the substantive version-processing logic, with OKC and OKE standard utilities providing shared contract services.

Tables Accessed

The ETRM metadata does not enumerate the base tables referenced through APPS synonyms. Functionally, version management in Oracle Contracts operates against the OKE contract version entities — the contract header and version tables that hold version numbers, effective dates, status, and the versioned attribute values — together with the associated version history structures that preserve prior states for restoration. The package reads the current contract and version rows, writes new version rows during VERSION_CONTRACT, and updates or reinstates version records during RESTORE_CONTRACT_VERSION. Because access occurs through APPS synonyms and the private package layer, direct table references are encapsulated in OKE_VERSION_PVT rather than exposed at the public API surface.

Usage Notes

OKE_VERSION_PUB is typically invoked from the Oracle Contracts forms when a user initiates contract versioning or version restoration from the user interface, and from custom PL/SQL that requires programmatic version control over contracts. When called, the API follows the standard EBS API protocol: initialization of the FND message list, execution of the requested operation within a savepoint, and return of a success or error status with associated messages retrievable through FND_MSG_PUB. Callers in custom code should therefore initialize the message list, check the return status, and handle exceptions rather than relying on implicit commits. Utilization of the delivered public API is strongly preferred over direct DML against the contract version tables.