Search Results authorize_date




Overview
Explore in AI Chat

Overview

OKE_K_HEADERS is the extended header table for project contracts in the Oracle E-Business Suite (EBS) Project Contracts module (OKE). It exists within the OKE schema and stores project contract header information that extends beyond the base contract header record maintained in OKC_K_HEADERS_B from the Oracle Contracts Core (OKC) schema. While OKC_K_HEADERS_B holds the core contract definition shared across all contract categories, OKE_K_HEADERS captures the project-specific and government-contracting attributes — negotiation dates, definitization data, Federal Acquisition Regulation (FAR) related flags, and reporting indicators — that are unique to project contracts.

The table is documented as VALID in Oracle EBS 12.1.1 and 12.2.2, containing 69 documented columns in the 12.2.2 physical schema. Its primary key is OKE_K_HEADERS_PK, defined on K_HEADER_ID.

From a Data Vault modeling perspective, the metadata's heuristic classification suggests a hub-leaning structure. OKE_K_HEADERS functions as a candidate hub keyed by K_HEADER_ID, holding a distinct business concept (the project contract header) with descriptive attributes that in a strict Data Vault design would more naturally reside in an adjacent satellite. The presence of both a unique identifier and numerous descriptive, non-key columns reinforces this hybrid hub/satellite character.

Key Information Stored

The most significant columns in OKE_K_HEADERS include:

The unique index OKE_K_HEADERS_U1 on K_HEADER_ID confirms it as the business-key candidate, while the surrounding descriptive columns carry the contract header attributes.

Common Use Cases and Queries

OKE_K_HEADERS is central to reporting on project contract administration, particularly for government-facing organizations that must track definitization, funding limits, and compliance status.

A typical query joins OKE_K_HEADERS to the base OKC contract header and the associated project:

  • Contract administration reporting — Selecting contract number, project, award date, and definitization status for a portfolio view.
  • Not-to-exceed monitoring — Filtering records where NTE_AMOUNT exceeds a threshold or where NTE_WARNING_FLAG is set.
  • Compliance tracking — Querying government contracting flags (CAS_FLAG, CLASSIFIED_FLAG, DCAA_AUDIT_REQ_FLAG) for audit and reporting workflows.
  • Milestone dashboards — Reporting on DATE_NEGOTIATED, DATE_SIGN_BY_CUSTOMER, and DATE_SIGN_BY_CONTRACTOR slippage.

Because K_HEADER_ID is widely referenced, most queries start from the header and join outward to child tables such as OKE_K_TERMS or OKE_K_HOLDS to obtain terms and holds for a contract.

Related Objects

The following tables depend on or relate to OKE_K_HEADERS through documented foreign keys:

  • OKC_K_HEADERS_B — Base contract header; OKE_K_HEADERS.K_HEADER_ID references it, establishing the extension relationship.
  • PA_PROJECTS_ALL — The Oracle Projects master project, referenced via PROJECT_ID.
  • OKE_PROGRAMS — Program definition, referenced via PROGRAM_ID.
  • OKE_K_TYPES_B and OKE_PRIORITY_CODES_B — Lookup tables for contract type and priority.
  • OKE_K_TERMS and OKE_K_HOLDS — Contract terms and holds keyed by K_HEADER_ID.
  • OKE_CHG_REQUESTS — Change requests referencing the contract header.
  • OKE_K_BILLING_METHODS — Billing method configuration for the contract.
  • OKE_APPROVAL_HISTORY — Approval audit trail for the header.
  • OKE_K_RELATED_ENTITIES — Related entity associations, referencing K_HEADER_ID and RELATED_ENTITY_ID.
  • OKE_K_VERS_NUMBERS_H — Version history for the contract header.

These relationships make OKE_K_HEADERS a focal hub within the Project Contracts data model, anchoring terms, holds, billing, deliverables, and approval data.