Results for “okc_k_headers_all_b”

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

Overview

OKC.K_HEADERS_ALL_B is the base table that stores header-level attributes of a contract within the Oracle E-Business Suite Contracts Core (OKC) module. Each row represents a single contract, and the table serves as the anchor that groups all related lines, terms, and conditions belonging to that contract. The _ALL suffix indicates the table participates in multi-organization (Operating Unit) security via ORG_ID, while the _B suffix denotes the base table of a translated entity, with the corresponding _TL table supplying language-specific descriptive columns. In a Data Vault modeling context, the table’s FK and PK structure heuristically classifies it as a hub: it carries a stable business key (CONTRACT_NUMBER with modifier) and a surrogate primary key, with dependent descriptive attributes and many self-referencing and foreign-key links radiating outward.

Key Information Stored

The surrogate primary key documented in ETRM is ID (unique index OKC_K_HEADERS_ALL_B_U1), which is the internal CHR identifier referenced throughout the schema as CHR_ID. Business-key candidates are captured by OKC_K_HEADERS_ALL_B_U2 on the combination of CONTRACT_NUMBER and CONTRACT_NUMBER_MODIFIER, uniquely identifying a contract as users see it.

• ID — surrogate primary key; the contract header identifier.
• CONTRACT_NUMBER / CONTRACT_NUMBER_MODIFIER — user-facing contract number and its version/variation modifier.
• STS_CODE — current contract status, referencing OKC_STATUSES_B.
• SCS_CODE — subclass or contract type, referencing OKC_SUBCLASSES_B.
• CHR_TYPE — indicates the header type (e.g., contract versus template or grouping).
• START_DATE / END_DATE — effective period of the contract.
• ESTIMATED_AMOUNT / CURRENCY_CODE — monetary value and currency.
• CUST_ACCT_ID, BILL_TO_SITE_USE_ID, SHIP_TO_SITE_USE_ID — customer and site references.
• PAYMENT_TERM_ID — payment terms, referencing PN_PAYMENT_TERMS_ALL.
• TEMPLATE_YN, ARCHIVED_YN, DELETED_YN — classification flags.
• CHR_ID_AWARD, CHR_ID_RENEWED, CHR_ID_RENEWED_TO, CHR_ID_RESPONSE — self-referencing links to related contracts.
• ORG_ID, SECURITY_GROUP_ID — multi-org and data-security controls.
• OBJECT_VERSION_NUMBER — optimistic locking column.
• WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE) and ATTRIBUTE1–15 — audit trail and DFF storage.

Common Use Cases and Queries

Contract reporting typically starts from this header table. To list active contracts for an operating unit:

• SELECT ID, CONTRACT_NUMBER, STS_CODE, START_DATE, END_DATE FROM OKC_K_HEADERS_ALL_B WHERE ORG_ID = :p_org AND STS_CODE = 'ACTIVE';
• Joining to status and subclass lookups: ... JOIN OKC_STATUSES_B S ON S.CODE = H.STS_CODE JOIN OKC_SUBCLASSES_B SC ON SC.CODE = H.SCS_CODE.
• Resolving renewals via the self-referencing link: SELECT h1.CONTRACT_NUMBER, h2.CONTRACT_NUMBER renewed_to FROM OKC_K_HEADERS_ALL_B h1 JOIN OKC_K_HEADERS_ALL_B h2 ON h2.ID = h1.CHR_ID_RENEWED_TO.
• Template identification: WHERE TEMPLATE_YN = 'Y' to drive contract authoring.

Typical reports include contract repository extracts, expiration/renewal calendars, and integration feeds keyed on CONTRACT_NUMBER. Because it is the hub, ad-hoc queries should always link child lines and terms through ID.

Related Objects

• OKC_STATUSES_B — status lookup joined on STS_CODE.
• OKC_SUBCLASSES_B — subclass/type lookup joined on SCS_CODE.
• OKC_QA_CHECK_LISTS_B — quality check lists joined on QCL_ID.
• OKC_K_GRPINGS — contract groupings referencing INCLUDED_CHR_ID = ID.
• OKC_OPERATION_LINES — operations referencing SUBJECT_CHR_ID and OBJECT_CHR_ID.
• PN_PAYMENT_TERMS_ALL — payment terms joined on PAYMENT_TERM_ID.
• MTL_INV_PICKING_RULES — inventory rule joined on INV_RULE_ID.
• FND_SECURITY_GROUPS — security grouping joined on SECURITY_GROUP_ID.