Search Results chr_chr2_uk

Overview

The OKC_K_HEADERS_ALL_B table is the central repository for contract header information within the Oracle E-Business Suite Contracts Core (OKC) module. It serves as the primary entity that groups all associated lines, terms, and conditions for a single contract. This table is fundamental to the contract management lifecycle, storing the master attributes that define a contract's identity, classification, and status. Its design supports multi-organization access through the "_ALL" suffix, meaning it contains data for all operating units, with security typically enforced via views or application logic. The table's integrity and relationships are critical for maintaining accurate contract hierarchies and linkages, such as renewals and amendments.

Key Information Stored

The table stores a comprehensive set of header-level attributes. The primary identifier is the ID column, which is the system-generated primary key (OKC_K_HEADERS_ALL_B_PK). For business identification, the unique key CHR_CHR2_UK enforces uniqueness on the combination of CONTRACT_NUMBER and CONTRACT_NUMBER_MODIFIER, which together form the human-readable contract identifier. Other critical columns include status (STS_CODE), subclass (SCS_CODE), and quality assurance checklist ID (QCL_ID). The table also contains several self-referencing foreign key columns that establish relationships between contracts, such as CHR_ID_AWARD, CHR_ID_RENEWED, CHR_ID_RENEWED_TO, and CHR_ID_RESPONSE, which are essential for tracking contract versions, renewals, and linked documents.

Common Use Cases and Queries

This table is central to reporting on contract portfolios, tracking contract lifecycles, and integrating contract data with other EBS modules like Projects, Service, and Procurement. A common query involves retrieving a contract's basic header information using its business number. For instance, to find a contract's internal ID and status based on its number:

SELECT id, sts_code, scs_code FROM okc_k_headers_all_b WHERE contract_number = '<Number>' AND contract_number_modifier = '<Modifier>';

Another frequent use case is analyzing contract relationships, such as finding all contracts renewed from a specific parent contract:

SELECT child.id, child.contract_number FROM okc_k_headers_all_b parent, okc_k_headers_all_b child WHERE parent.id = child.chr_id_renewed AND parent.contract_number = '<Parent_Number>';

Data from this table is typically accessed via the Contracts Core public APIs or through dedicated views for reporting purposes.

Related Objects

The OKC_K_HEADERS_ALL_B table has extensive relationships within the Contracts Core schema, as documented in the provided metadata. Key dependencies include:

• Primary Keys: OKC_K_HEADERS_ALL_B_PK (ID), CHR_CHR2_UK (CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER).
• Foreign Keys (Referenced by this table):
  • OKC_K_HEADERS_ALL_B (self-reference via CHR_ID_AWARD, CHR_ID_RENEWED, CHR_ID_RENEWED_TO, CHR_ID_RESPONSE)
  • OKC_QA_CHECK_LISTS_B (via QCL_ID)
  • OKC_SUBCLASSES_B (via SCS_CODE)
  • OKC_STATUSES_B (via STS_CODE)
• Foreign Keys (Referencing this table):
  • OKC_K_GRPINGS (via INCLUDED_CHR_ID)
  • OKC_K_HEADERS_ALL_B (self-reference, as listed above)
  • OKC_OPERATION_LINES (via SUBJECT_CHR_ID and OBJECT_CHR_ID)

These relationships illustrate that the contract header is the anchor point for contract groupings, operational lines, and its own versioning hierarchy.