Search Results okc_chr_pvt




Overview

OKC_CHR_PVT is a private helper package body in the Oracle E-Business Suite Contracts (OKC) module, owned by the APPS schema. Its name reflects its role operating on contract header rows (CHR), and the PVT classification confirms that it is an internal implementation package rather than a public API. It provides the low-level, row-oriented infrastructure that underpins the contract versioning and multi-language model of the OKC schema: inserting, locking, updating, deleting, validating, and translating records in the contract header tables, as well as copying headers, creating new versions, and restoring prior versions. Because the package is documented with 18 procedures and functions and is referenced by 52 other packages, it functions as a shared service layer invoked by higher-level contract APIs such as OKC_API and OKC_CONTRACT_PVT rather than being called directly by end users. In EBS 12.1.1 and 12.2.2 the package is shipped as VALID, and its dependencies on FND_API, APP_EXCEPTIONS, OKC_DEBUG, and OKC_UTIL follow the standard EBS API design pattern of error stacking, message retrieval, and instrumentation.

Key Procedures and Functions

The documented entry points fall into distinct functional groups:

  • Row maintenance: INSERT_ROW, UPDATE_ROW, DELETE_ROW, LOCK_ROW, and VALIDATE_ROW perform the core DML and concurrency operations against a single contract header row, including validation of mandatory and derived values before persistence.
  • Version management: CREATE_VERSION, CHANGE_VERSION, RESTORE_VERSION, and API_COPY manage the contract versioning model, creating new header versions, switching an existing header between versions, restoring a prior version, and copying header content. These procedures interact with OKC_VERSION_PVT and OKC_K_VERS_NUMBERS.
  • Translation support: ADD_LANGUAGE inserts translated header rows, enabling the multi-language tables (OKC_K_HEADERS_TL and its history table) to hold locale-specific descriptions.
  • Utilities: QC (quality check) performs data-integrity validation, IS_UNIQUE enforces uniqueness of header identifiers, and INSERT_ROW_UPG provides the upgrade-path insert used when migrating contracts to a later release.

None of these procedures are intended as public API surface; they assume the calling package has already resolved contract context through OKC_CONTEXT and validated inputs via FND_API.

Tables Accessed

The package reads and writes the core contract header tables through APPS synonyms. OKC_K_HEADERS_ALL_B holds the base header rows, with OKC_K_HEADERS_B and the sequence OKC_K_HEADERS_B_S supplying identifiers and the history table OKC_K_HEADERS_ALL_BH recording prior versions. OKC_K_HEADERS_TL and OKC_K_HEADERS_TLH store translated and historical translated content, while OKC_K_HEADERS_V exposes a validation view. Supporting lookups include OKC_CLASSES_B, OKC_SUBCLASSES_B, OKC_STATUSES_B, OKC_QA_CHECK_LISTS_B, OKC_K_LINES_B (lines affected by copy operations), and OKC_K_VERS_NUMBERS (version numbering). FND_LANGUAGES and FND_CURRENCIES_VL provide language and currency validation, and DUAL and PLITBLM support PL/SQL-level constructs. OKX_LIST_HEADERS_V supplies list header information used for validation of contract types and groups.

Usage Notes

OKC_CHR_PVT is invoked indirectly through the OKC public APIs and is not exposed to Oracle Forms or concurrent programs as a callable unit. Typical invocation paths are OKC_API, OKC_CONTRACT_PVT, and OKC_VERSION_PVT during contract authoring, amendment, version creation, restoration, and mass copy operations executed from the Contracts workbench. Customizations that must respect versioning and translation semantics should call the public OKC APIs rather than OKC_CHR_PVT, since the private package assumes caller-supplied context, error handling through FND_API, and prior validation. Understanding OKC_CHR_PVT is primarily valuable for diagnosing versioning, locking, or translation failures and for tracing the 52 dependent packages that rely on its row-level services.