Search Results okc_sav_pvt




Overview
Explore in AI Chat

Overview

The APPS.OKC_SAV_PVT package body is the private implementation layer of the Standard Articles Versioning subsystem within Oracle E-Business Suite's Enterprise Contracts (OKC) module. Standard Articles are reusable clause and boilerplate text libraries that contract authors attach to contract templates and contract documents. The _PVT suffix indicates the package is classified as a private API, meaning it is not intended for direct invocation by external integrations or customer extensions; instead it is consumed internally by the public OKC_API and related interfaces. The package body materializes the business logic that governs lifecycle management of standard article versions — creation, copying, language installation, validation, locking, update, and deletion — against the base and translated tables that store article definitions.

The package is status VALID and resides in the APPS schema. It is documented as not being referenced by any other database object, yet it in turn depends on a broad set of Oracle EBS foundation packages, including FND_API, FND_GLOBAL, FND_LANGUAGES, FND_PROFILE, APP_EXCEPTIONS, OKC_API, OKC_P_UTIL, OKC_UTIL, and the PL/SQL table type package PLITBLM.

Key Procedures and Functions

The ETRM metadata documents nineteen procedures and functions, of which the most significant are summarized below. Parameter lists are deliberately omitted because they are not part of the documented metadata.

  • CHANGE_VERSION — Advances or re-creates the version identifier for a standard article, driving the versioning lifecycle central to this package.
  • API_COPY — Copies a standard article version, enabling duplication of article content for new versions or new articles.
  • ADD_LANGUAGE — Installs an additional language translation row for an existing standard article version.
  • INSERT_ROW — Performs the physical insert of a standard article version record.
  • UPDATE_ROW — Applies changes to an existing standard article version record.
  • DELETE_ROW — Removes a standard article version record.
  • LOCK_ROW — Obtains a row-level lock to serialize concurrent modifications.
  • VALIDATE_ROW — Performs the master validation routine used across the transactional operations.
  • VALIDATE_SAV_RELEASE — Validates the release state of a standard article version.
  • VALIDATE_DATE_ACTIVE — Checks the active date range of the version.
  • VALIDATE_NO_K_ATTACHED — Confirms no contract (K) records are attached, guarding deletion or version changes.
  • VALIDATE_LATEST — Verifies whether the version is the latest.
  • VALIDATE_UPDATABLE — Determines whether the version may be modified.
  • QC — A quality-control / consistency check helper invoked during processing.

Collectively these routines implement a standard who-column, validation, locking, and DML pattern characteristic of Oracle EBS private APIs.

Tables Accessed

The package reads and writes the following documented tables through APPS synonyms:

  • OKC_STD_ARTICLES_B — Base table holding standard article definitions (language-independent attributes).
  • OKC_STD_ART_VERSIONS_B — Base table storing standard article version records, the primary target of INSERT_ROW, UPDATE_ROW, DELETE_ROW, and CHANGE_VERSION.
  • OKC_STD_ART_VERSIONS_TL — Translation table holding language-specific version text; populated by ADD_LANGUAGE.
  • OKC_STD_ART_VERSIONS_V — A view joining base and translation data, used for validation and QC reads.
  • OKC_K_ARTICLES_V — A view exposing contract-to-article associations, queried by VALIDATE_NO_K_ATTACHED.
  • FND_LANGUAGES — The installed-language reference table, consulted by ADD_LANGUAGE.
  • PLITBLM — The standard PL/SQL table / index-by table type package used for internal collection handling.

Usage Notes

Because OKC_SAV_PVT is a private (PVT) API, it is not designed as a public integration point. It is typically invoked indirectly through the Contracts authoring forms and the public OKC_API layer when a user creates, changes, or deletes a standard article version; the form triggers call the private routines to perform validation, locking, and DML. Concurrent programs that seed or migrate standard article libraries, and Oracle's own upgrade or patching scripts, may also invoke these routines during data conversion.

Custom code should avoid calling OKC_SAV_PVT directly, since signatures and behavior are subject to change across EBS point releases (12.1.1 and 12.2.2) without notice. When extension is required, the recommended approach is to wrap logic through the public OKC_API procedures or use supported personalization and extension hooks. The package depends on FND_GLOBAL for session context (user, responsibility, login), so it must be called from within a properly initialized EBS application session; otherwise validation and who-column population will fail.