Results for “default_task_id”

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

Overview

OKE_K_HEADERS_H is the project contract extended header historical table owned by the OKE schema within the Oracle E-Business Suite Project Contracts module. It stores versioned historical snapshots of contract header information, capturing the extended descriptive and administrative attributes that describe a project contract at each major version. In Oracle EBS 12.1.1 and 12.2.2, this table coexists with the operational header table OKE_K_HEADERS and the base contract header history table OKC_K_HEADERS_BH, forming part of the versioning architecture that preserves a complete audit trail of contract changes throughout the contract lifecycle.

The heuristic Data Vault classification for this object is satellite-leaning. This reflects the presence of a composite primary key combining a business entity identifier with a version attribute, together with extensive descriptive and flag columns that track the state of the contract at a point in time rather than representing an independent business entity. The object therefore behaves as a satellite historically attached to the underlying contract header hub.

Key Information Stored

The table contains 70 documented columns. The surrogate primary key is defined by OKE_K_HEADERS_H_PK on the composite of K_HEADER_ID and MAJOR_VERSION. A unique index, OKE_K_HEADERS_H_U1, is defined on the same combination, confirming it as the business-key candidate that uniquely identifies a version of a contract header.

• K_HEADER_ID — identifier linking the historical row to the parent contract header entity; also referenced by OKC_K_HEADERS_BH.
• MAJOR_VERSION — the version number that distinguishes successive snapshots of the same contract.
• K_NUMBER_DISP and PRIME_K_NUMBER — the displayed and primary contract numbers for reporting and lookup.
• K_TYPE_CODE — the contract type classification, validated against OKE_K_TYPES_B.
• PROJECT_ID — the associated project, referencing PA_PROJECTS_ALL; central to project contract reporting.
• BOA_ID — reference to the owning contract header record in OKE_K_HEADERS.
• PRIORITY_CODE — priority classification validated against OKE_PRIORITY_CODES_B.
• AWARD_DATE, DATE_DEFINITIZED, DATE_ISSUED, DATE_NEGOTIATED, DATE_RECEIVED — key lifecycle milestone dates.
• NTE_AMOUNT — not-to-exceed value governing contract spend ceilings.
• LINE_VALUE_TOTAL and UNDEF_LINE_VALUE_TOTAL — aggregated contract and undefined line values.
• OWNING_ORGANIZATION_ID and DEFAULT_TASK_ID — organizational ownership and default task references.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and PROGRAM_ID, providing audit and concurrency context.

Common Use Cases and Queries

Typical usage centers on historical contract reporting, version comparison, and audit reconciliation. A common pattern retrieves the latest historical version of a contract by filtering on the maximum MAJOR_VERSION for a given K_HEADER_ID:

• Version listing: SELECT k_header_id, major_version, k_number_disp, k_type_code, award_date FROM oke.oke_k_headers_h WHERE k_header_id = :p_id ORDER BY major_version DESC;
• Lifecycle milestone reporting: joining to PA_PROJECTS_ALL on PROJECT_ID to report contract award and definitization dates by project.
• Financial ceiling analysis: aggregating NTE_AMOUNT and LINE_VALUE_TOTAL across versions to reconcile contract value changes.
• Audit comparison: comparing successive MAJOR_VERSION rows for a single K_HEADER_ID to identify changes in priority, type, or milestone dates between contract revisions.
• Point-in-time reporting: selecting the version active as of a given date using the WHO date columns.

Related Objects

This table participates in a well-defined network of foreign key relationships. The parent reference is OKC_K_HEADERS_BH, which shares the K_HEADER_ID and MAJOR_VERSION key, making it the primary historical anchor. OKE_K_HEADERS provides the current operational header via BOA_ID. PA_PROJECTS_ALL supplies project context through PROJECT_ID, while OKE_PROGRAMS, OKE_K_TYPES_B, and OKE_PRIORITY_CODES_B provide program, type, and priority validation.

Several dependent historical tables reference OKE_K_HEADERS_H through the composite K_HEADER_ID and MAJOR_VERSION keys: OKE_K_BILLING_METHODS_H, OKE_K_STANDARD_NOTES_BH, OKE_K_TERMS_H, and OKE_K_USER_ATTRIBUTES_H. These child tables carry billing method, standard note, term, and user-attribute history that must remain synchronized with the header version, and together they support comprehensive historical contract reconstruction for reporting and audit purposes.