Results for “okc_chr_pvt”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKC_CHR_PVT is a private PL/SQL package in the Oracle E-Business Suite Contracts (OKC) module, owned by the APPS schema and classified as a PVT (private) API. Its purpose is to manage the persistence and versioning of contract header records (CHR) — the top-level contract entities stored in the OKC_K_HEADERS tables. The package encapsulates the low-level insert, update, delete, locking, validation, and version-control logic required to maintain contract headers, exposing this functionality only to other packages within the Contracts application rather than to external callers. Its $Header comment (OKCSCHRS.pls 120.5, dated 2007) confirms it forms part of the foundational Contracts schema infrastructure shipped across releases 12.1.1 and 12.2.2.

The package declares a global chr_rec_type record structure that mirrors the columns of the OKC_K_HEADERS_B table, including identifying attributes (id, contract_number, contract_number_modifier), classification fields (chr_type, qcl_id, sts_code, scs_code, trn_code), lifecycle flags (archived_yn, deleted_yn, template_yn), versioning references (chr_id_response, chr_id_award, chr_id_renewed), and standard WHO audit columns. Default values use OKC_API.G_MISS_* sentinels so callers can distinguish supplied from omitted attributes.

Key Procedures and Functions

  • INSERT_ROW — Creates a new contract header row in the base table.
  • UPDATE_ROW — Modifies attributes of an existing contract header.
  • DELETE_ROW — Removes or logically deletes a contract header record.
  • LOCK_ROW — Obtains a row-level lock to serialize concurrent modifications.
  • VALIDATE_ROW — Performs business-rule validation on header attributes before persistence.
  • IS_UNIQUE — Checks uniqueness constraints, such as contract number, prior to insertion.
  • CHANGE_VERSION and CREATE_VERSION — Manage contract versioning, creating new version records while preserving prior ones.
  • RESTORE_VERSION — Reverts a contract header to a previously stored version.
  • API_COPY — Copies contract header data, supporting cloning and template-based creation.
  • ADD_LANGUAGE — Inserts or maintains translated (TL) rows for multilingual deployments.
  • INSERT_ROW_UPG — Upgrade-specific insert routine used during patch or data-migration processing.
  • QC — Internal quality-control/consistency routine invoked as part of the package's processing.

Tables Accessed

The package reads and writes the core Contracts header tables: OKC_K_HEADERS_B, OKC_K_HEADERS_ALL_B, and their history/translation counterparts OKC_K_HEADERS_ALL_BH, OKC_K_HEADERS_TL, and OKC_K_HEADERS_TLH. It references the sequence OKC_K_HEADERS_B_S for key generation and FND_LANGUAGES for translation handling. Classification and status lookups draw on OKC_CLASSES_B, OKC_SUBCLASSES_B, OKC_STATUSES_B, and OKC_QA_CHECK_LISTS_B, while version control uses OKC_K_VERS_NUMBERS. Line-level data is referenced through OKC_K_LINES_B. DUAL and PLITBLM support internal PL/SQL constructs. All access occurs through APPS synonyms.

Usage Notes

As a private package, OKC_CHR_PVT is not intended for direct customer invocation. It is called by 52 other packages, including the public OKC_API and OKC_K_HEADERS APIs, which in turn are invoked by Contracts forms, concurrent programs, and versioning workflows. Customizations should call the supported public APIs rather than this package, because signatures are subject to change between patches and point releases.