Search Results oke_k_headers_full_hv




Overview
Explore in AI Chat

Overview

The APPS.OKE_K_HEADERS_FULL_HV view is a historical contract header extended information view within the Oracle E-Business Suite Project Contracts (OKE) module. Its naming convention, specifically the "_HV" suffix, indicates that it exposes historical or versioned contract header data rather than the current active record. In the OKE schema, contract headers are version-controlled, and the "_H" suffix denotes the history table that stores each prior version of a contract header. This view joins those historical version rows to the descriptive and lookup data required for full presentation of a contract header at any given major version.

The view serves reporting and integration purposes by flattening a broad set of header attributes—contract identifiers, organizational assignments, program and project linkage, classification flags, and various dates—into a single denormalized result set. Because contract versioning is central to Project Contracts, consumers of this view can reconstruct the state of a contract header as it existed at a specific major version, which is essential for audit reporting, change-history analysis, and downstream integrations that must reconcile historical contract states.

Underlying Base Objects

The view is defined over several documented base objects. Contract header history is sourced from OKE_K_HEADERS_H, which holds the versioned header extension rows. This is joined to OKC_K_HEADERS_ALL_B and its history counterpart OKC_K_HEADERS_ALL_BH, the core contract header base tables, and to OKC_K_HEADERS_TLH for translated descriptive columns such as cogomen and description. Contract type and status descriptions are resolved through OKE_K_TYPES_VL and OKC_STATUSES_TL respectively.

Organizational context is provided by HR_ALL_ORGANIZATION_UNITS_TL (authoring and owning organizations) and by joins to PA_PROJECTS_ALL and PA_TASKS for project linkage. Lookup values such as product line meaning are resolved via FND_LOOKUP_VALUES. Priority Code descriptions come from OKE_PRIORITY_CODES_TL, and program data from OKE_PROGRAMS. The OKE_UTILS package is invoked repeatedly to translate Y/N flags into display values through its YES_NO function.

Key Columns

The view exposes contract identity columns including K_HEADER_ID, MAJOR_VERSION, CONTRACT_NUMBER, and CONTRACT_NUMBER_MODIFIER. A derived version string concatenates the major version with a ".0" suffix to represent the full version label. Descriptive columns include COGNOMEN, SHORT_DESCRIPTION, and DESCRIPTION from the translated header table.

Organizational and classification columns include AUTHORING_ORG_ID and OWNING_ORGANIZATION_ID with their associated ORG.NAME values, plus SCS_CODE, BUY_OR_SELL, and the contract type codes (K_TYPE_CODE, K_TYPE_NAME, TYPE_CLASS_CODE). Financial and status columns include ESTIMATED_AMOUNT, PRIORITY_CODE, PROGRAM_ID, and STS_CODE with its meaning.

Multiple flags—CLASSIFIED_FLAG, DCAA_AUDIT_REQ_FLAG, BOOKED_FLAG, OPEN_FLAG, EXPORT_FLAG, HUMAN_SUBJECT_FLAG, PENALTY_CLAUSE_FLAG, SB_PLAN_REQ_FLAG, SB_REPORT_FLAG, CQA_FLAG, and REPORTING_FLAG—are each passed through OKE_UTILS.YES_NO with NVL defaulting to 'N', producing human-readable Yes/No values. Date columns include START_DATE, END_DATE, AWARD_DATE, AUTHORIZE_DATE, DATE_ISSUED, DATE_SIGN_BY_CUSTOMER, DATE_SIGN_BY_CONTRACTOR, DATE_RECEIVED, DATE_APPROVED, and the FAA approve/reject dates.

Common Use Cases and Queries

Typical usage involves historical audit and version-comparison reporting. A query to retrieve all versions of a given contract might select the version label and key attributes:

  • SELECT contract_number, major_version, contract_number_modifier, k_type_name, sts_code, start_date, end_date FROM oke_k_headers_full_hv WHERE contract_number = :p_contract_number ORDER BY major_version;
  • Reconciliation of estimated amounts across versions for financial review.
  • Reporting on classified or DCAA-flagged contracts by filtering the translated Yes/No columns.
  • Integration extracts that require project and program linkage for a historical header state.

Because the view relies on the OKE_UTILS package for flag translation and on translated (_TL) tables, filtering on those derived columns should account for the current language environment. Reports typically join this view back to OKC_K_HEADERS_ALL_B when current-state attributes are also required alongside the historical version data.