Results for “conversion_rate_date”

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

Overview

OKC_K_HEADERS_HV is an APPS-owned database view in the Oracle E-Business Suite Contracts Core (OKC) module. It is defined as the history view for the OKC_K_HEADERS entity, presenting a full historical perspective of contract header records instead of only the current active rows. In Oracle EBS contracts architecture, current data resides in the _B (base) and _T (translation) tables, while historical and versioned rows are held in the _BH and _TLH tables. OKC_K_HEADERS_HV joins these history base objects along with the OKC_UTIL package to expose a single, query-friendly surface for reporting, reconciliation, and integration.

The view is registered as VALID in the ETRM metadata for both Oracle EBS 12.1.1 and 12.2.2, and its name carries the HV suffix that convention designates for this historical view family in the OKC schema. Because it flattens the history base objects and applies OKC_UTIL logic, it mitigates the need for downstream tools to reconstruct version history manually and supports point-in-time analysis of contract headers.

Underlying Base Objects

The documented referenced base objects are:

• OKC_K_HEADERS_BH (SYNONYM) — the history base table storing version-stamped contract header rows.
• OKC_K_HEADERS_TLH (SYNONYM) — the history translation table storing descriptive, translated text columns.
• OKC_UTIL (PACKAGE) — a Contracts utility package used to supply derived or decoded values in the view definition.

In the view text, the _BH source is aliased CHRB and the _TLH source is aliased CHRT. Most operational and status attributes are drawn from CHRB, while descriptive fields such as SHORT_DESCRIPTION, COMMENTS, DESCRIPTION, COGNOMEN, NON_RESPONSE_REASON, NON_RESPONSE_EXPLAIN, and SET_ASIDE_REASON are read from CHRT. This split follows the standard EBS multilingual table design in which translated text is separated from base attributes.

Key Columns

• ID, DOCUMENT_ID, MAJOR_VERSION, OBJECT_VERSION_NUMBER — contract identity and version control keys.
• CHR_ID_RESPONSE, CHR_ID_AWARD, CHR_ID_RENEWED — linkage to related response, award, and renewal contract headers.
• STS_CODE, SCS_CODE, QCL_ID — status, status class, and quality/status code identifiers.
• CONTRACT_NUMBER, CONTRACT_NUMBER_MODIFIER, CURRENCY_CODE — business identifiers for the contract header.
• NON_RESPONSE_REASON, NON_RESPONSE_EXPLAIN — the documented reason and explanation recorded when a response is not received, surfaced from the translation table.
• AUTO_RENEW_DAYS, DATE_APPROVED, DATE_ISSUED, DATE_SIGNED, DATE_TERMINATED, DATE_RENEWED, START_DATE, END_DATE — key lifecycle dates and renewal configuration.
• AUTHORING_ORG_ID, INV_ORGANIZATION_ID, BUY_OR_SELL, ISSUE_OR_RECEIVE, RFP_TYPE, CHR_TYPE — organizational and type classification attributes.
• ARCHIVED_YN, DELETED_YN, TEMPLATE_YN, GOVERNING_CONTRACT_YN, SFWT_FLAG — flags controlling inclusion, template behavior, and workflow status.

Common Use Cases and Queries

Typical uses include point-in-time contract reporting, audit of status transitions, tracking of renewal and award lineage, and extraction of non-response or set-aside reason codes for sourcing analysis. A representative query filtering on the searched term would be:

SELECT contract_number, NON_RESPONSE_REASON, NON_RESPONSE_EXPLAIN, STS_CODE, DATE_ISSUED, DATETIME_RESPONDED FROM APPS.OKC_K_HEADERS_HV WHERE NON_RESPONSE_REASON IS NOT NULL AND start_date >= :p_start_date;

Integrations commonly join OKC_K_HEADERS_HV to OKC_K_HEADERS_V (current), OKC_K_LINES_HV, and OKC_K_PARTY_ROLES_HV to assemble full historical contract documents for reconciliation, data migration, or reporting extracts consumed by BI Publisher and Oracle Data Integrator.