Search Results okc_k_article_pvt




Overview
Explore in AI Chat

Overview

OKC_K_ARTICLE_PVT is a private PL/SQL package in the APPS schema within Oracle E-Business Suite. It belongs to the Oracle Knowledge Center (OKC) module, which underpins the Contracts (formerly Service Contracts) and related contract-authoring functionality. The package implements the core business logic for managing contract articles — the reusable, ordered text clauses that make up the body of a contract document. Articles are associated with contract templates and contracts, are ordered within sections, and can be maintained in multiple languages. OKC_K_ARTICLE_PVT encapsulates the create, update, lock, delete, validate, and translation operations that act on the underlying OKC_K_ARTICLES_B base table and its associated section-contents structure.

The package is classified as a PVT (private) API, meaning it is intended for internal use by the OKC application layer rather than as a public integration interface. It is invoked by the corresponding public wrapper package OKC_K_ARTICLE_PUB, which provides the supported, externally callable entry points. The status of the package is VALID in the reported environment, confirming that it compiles cleanly and its dependencies resolve.

Key Procedures and Functions

The package exposes ten documented procedures and functions, organised around article maintenance and article translation maintenance.

  • CREATE_K_ARTICLE — Creates a new contract article record, establishing the article definition within the knowledge/contract model.
  • UPDATE_K_ARTICLE — Modifies the attributes of an existing article, such as its descriptive text or classification.
  • LOCK_K_ARTICLE — Locks an article record, likely for concurrency control, ensuring that no conflicting modification occurs while an update is in progress.
  • DELETE_K_ARTICLE — Removes an article record from the contract model.
  • VALIDATE_K_ARTICLE — Performs business-rule validation on article data before it is committed, enforcing data integrity constraints.
  • ADD_LANGUAGE_K_ARTICLE — Adds a language variant to an existing article, supporting multilingual contract content.
  • CREATE_ARTICLE_TRANSLATION — Creates a translated version of an article for a target language.
  • LOCK_ARTICLE_TRANSLATION — Locks a translation record for concurrency control during maintenance.
  • DELETE_ARTICLE_TRANSLATION — Removes a translation record.
  • VALIDATE_ARTICLE_TRANSLATION — Validates translation data against business rules prior to commit.

Tables Accessed

The package operates against two documented base tables, accessed through APPS synonyms:

  • OKC_K_ARTICLES_B — The principal base table storing article definitions. The create, update, lock, delete, validate, and translation procedures all read from and write to this table to persist article and translation data.
  • OKC_SECTION_CONTENTS — Stores the content and ordering of items within contract sections, linking articles to their placement in the contract structure.

These tables form the persistence layer that the package's procedural logic manipulates on behalf of the contract-authoring user interface.

Usage Notes

OKC_K_ARTICLE_PVT is not intended for direct invocation by external integrators. It is referenced by OKC_K_ARTICLE_PUB, which is the public API wrapper, and by OKS_CONTRACTS_PUB, the public contracts API package. Custom code should therefore call the corresponding routines in OKC_K_ARTICLE_PUB rather than this private package, in order to remain on a supported interface and insulate against internal signature changes. The package depends on OKC_API, OKC_ATN_PVT, and OKC_CAT_PVT, reflecting its reliance on shared OKC utility routines, attachment handling, and catalog/classification logic. Typical invocation paths are the Contract Authoring and Template Authoring forms, which drive article creation, maintenance, and translation through the public API. No concurrent program or standalone concurrent executable is documented as calling this package directly. As with all PVT packages, it should be treated as internal implementation detail and not relied upon for direct database-level integration.