Search Results oke_k_headers

Overview

The OKE_K_HEADERS table is a core data object within the Oracle E-Business Suite Project Contracts (OKE) module. It stores extended header information specific to project contracts, functioning as a critical extension to the base contract header table (OKC_K_HEADERS_B) provided by the Oracle Contracts Core. This table is central to the management of project-centric contractual agreements, enabling the association of contracts with projects, programs, and specialized OKE attributes. Its role is to support the full lifecycle of project contracts, from creation and approval to billing and amendments, within both Oracle EBS 12.1.1 and 12.2.2 environments.

Key Information Stored

The table's primary key is K_HEADER_ID, which is a foreign key to OKC_K_HEADERS_B, establishing a one-to-one relationship with the foundational contract record. This design ensures integration with the shared contracts infrastructure. Other significant foreign key columns define the contract's operational context and classification. The PROJECT_ID links the contract to a specific project in the Project Accounting (PA) module, while PROGRAM_ID associates it with an OKE program. The K_TYPE_CODE classifies the contract type via a reference to OKE_K_TYPES_B. Additional key columns include PRIORITY_CODE (referencing OKE_PRIORITY_CODES_B) for workflow management and BOA_ID, which is a self-referencing foreign key used to establish hierarchical relationships between contract records, such as between an original contract and its amendments.

Common Use Cases and Queries

This table is essential for reporting and data extraction related to project contracts. Common use cases include generating a list of all contracts for a specific project, analyzing contracts by type or priority, and tracing amendment histories. A typical query would join OKE_K_HEADERS with OKC_K_HEADERS_B to retrieve both extended and base contract details, and with PA_PROJECTS_ALL for project information.

• Contract Listing by Project: SELECT okh.k_header_id, okh.project_id, pa.segment1 project_number, okc.contract_number FROM oke_k_headers okh JOIN okc_k_headers_b okc ON okh.k_header_id = okc.id JOIN pa_projects_all pa ON okh.project_id = pa.project_id WHERE okh.project_id = :p_project_id;
• Amendment Chain Analysis: Queries utilizing the self-referencing BOA_ID column can trace the lineage of contract versions and amendments.
• Integration Points: Data from this table is frequently accessed by OKE APIs, workflows, and the user interface forms to validate and process contract transactions.

Related Objects

As indicated by its extensive foreign key relationships, OKE_K_HEADERS is a central hub within the Project Contracts schema. It has a mandatory parent relationship with OKC_K_HEADERS_B. It is referenced as a foreign key by numerous transactional and supporting tables, including OKE_K_DELIVERABLES_B, OKE_K_TERMS, OKE_K_BILLING_METHODS, OKE_CHG_REQUESTS, and OKE_K_USER_ATTRIBUTES. This demonstrates its integral role in structuring deliverables, terms, billing plans, change management, and flexible field data for a contract. The relationships with OKE_APPROVAL_HISTORY and OKE_K_HOLDS underscore its importance in the contract approval and hold processes. The table OKE_K_HEADERS_H appears to be a history or audit table tracking changes to records in OKE_K_HEADERS.