Results for “okc_k_headers_b”

50+ results




Overview
Explore in AI Chat

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

Overview

OKC_K_HEADERS_B is the master header table within the Oracle Contracts Core (OKC) module. It stores header-level attributes for a contract and serves as the primary grouping point for all lines, terms and conditions, party roles, and process definitions that make up a contract record. Every contract authored through Oracle Contracts, Oracle Service Contracts (OKS), or Oracle Enterprise Contracts resolves to a single row in this table, identified by the CHR_ID (ID) surrogate key. The table is a "_B" (base) table, meaning it holds the base-language columns for a multi-language entity translated by companion _TL tables.

From a Data Vault modeling perspective, the FK structure indicates hub-leaning behavior: the table is referenced by a very large number of child tables (lines, party roles, accesses, group ings, sections, sales credits, change requests, governance, and history), while its own outbound foreign keys are limited to a small set of lookup and self-referencing relationships. This makes OKC_K_HEADERS_B a natural business hub for the contract subject area, with dependent satellite and link structures radiating from the CHR_ID key.

Key Information Stored

The following columns are the most significant for identification, classification, and lifecycle management of a contract header:

  • ID — Surrogate primary key (OKC_K_HEADERS_B_PK). This is the CHR_ID referenced throughout the OKC schema and by external modules such as Service Contracts, Advanced Pricing, and Receivables.
  • CONTRACT_NUMBER / CONTRACT_NUMBER_MODIFIER — Composite unique business key (CHR_CHR2_UK) providing the user-visible contract identifier and its version or modifier suffix.
  • SCS_CODE — Foreign key to OKC_SUBCLASSES_B; defines the contract subclass (for example, service agreement, warranty, or lease).
  • STS_CODE — Foreign key to OKC_STATUSES_B; drives the contract lifecycle status (draft, active, terminated, expired).
  • QCL_ID — Foreign key to OKC_QA_CHECK_LISTS_B; links the header to its quality assurance checklist.
  • CHR_ID_RENEWED, CHR_ID_RENEWED_TO — Self-referencing keys that chain a contract to the prior contract it renewed and to the successor contract it was renewed into.
  • CHR_ID_AWARD — Self-referencing key linking a contract to the award contract that originated it.
  • CHR_ID_RESPONSE — Self-referencing key linking a contract to its associated response or quote document.

Common Use Cases and Queries

Typical reporting and integration scenarios retrieve contract headers by business number, subclass, or status, and then drill into lines and party roles. A representative query joins the header to its subclass and status lookups:

  • Contract status reporting: SELECT h.id, h.contract_number, s.meaning status, sc.meaning subclass FROM okc_k_headers_b h, okc_statuses_b s, okc_subclasses_b sc WHERE h.sts_code = s.code AND h.scs_code = sc.code AND h.sts_code = 'ACTIVE'.
  • Renewal chain analysis: self-joins on CHR_ID_RENEWED and CHR_ID_RENEWED_TO trace the lineage of a contract family over successive renewal cycles.
  • Service Contracts integration: OKS_K_ORDER_DETAILS.CHR_ID and LINK_CHR_ID join back to OKC_K_HEADERS_B to reconcile subscription order lines with their governing contract headers.
  • Receivables reconciliation: RA_CUSTOMER_TRX_ALL.CONTRACT_ID and RA_INTERFACE_LINES_ALL.CONTRACT_ID tie billing transactions to the originating contract header for revenue and invoice reporting.
  • Access control auditing: OKC_K_ACCESSES.CHR_ID joins to the header to report which users or organizations have visibility to each contract.

Related Objects

The principal dependent and referencing objects are:

  • OKC_K_LINES_B — Child lines belonging to the header, joined on CHR_ID.
  • OKC_K_PARTY_ROLES_B — Party roles (customer, supplier, contact) attached to the contract, joined on CHR_ID.
  • OKC_K_ACCESSES — Security and access records for the contract, joined on CHR_ID.
  • OKC_K_GRPINGS — Contract grouping membership, joined on INCLUDED_CHR_ID.
  • OKS_K_ORDER_DETAILS — Service Contracts order detail rows joined on CHR_ID and LINK_CHR_ID.
  • OKC_K_HISTORY_B — Historical snapshot records keyed by CHR_ID.
  • OKC_CHANGE_REQUESTS_B — Change request documents associated with the header, joined on CHR_ID.
  • OKC_SUBCLASSES_B and OKC_STATUSES_B — Lookup tables referenced via SCS_CODE and STS_CODE.

Because OKC_K_HEADERS_B is the structural hub of the contracts schema, any interface or report that extracts contract data should treat CHR_ID as the canonical join key and the CONTRACT_NUMBER / CONTRACT_NUMBER_MODIFIER pair as the business identifier for external reconciliation.