Results for “oks_k_headers_hv”

18 results




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

Overview

OKS_K_HEADERS_HV is a view owned by the APPS schema within the OKS (Service Contracts) product of Oracle E-Business Suite. Its documented purpose is to expose Service Contracts Header Attributes History. In practice the "_HV" suffix denotes a history view, meaning the object provides a versioned or historical perspective on contract header attribute records rather than a single current-state row. Each record corresponds to a major version of a service contract header, allowing consumers to trace how contractual terms such as payment instruments, tax parameters, renewal behavior, and revenue estimation changed across successive versions of a contract.

Because the view is registered in Oracle EBS as VALID and is queryable through the APPS schema, it can be used directly in custom reports, concurrent program SQL, Oracle BI Publisher data templates, and inbound or outbound integration extracts. It is not an interface or API object; it is a read-only reporting surface, and no DML should be attempted against it. The column named COMMITMENT_ID, which corresponds to the user's search term, is one of the attributes carried on the header history record.

Underlying Base Objects

Per the ETRM metadata for 12.2.2, OKS_K_HEADERS_HV is defined over a single referenced base object: the synonym OKS_K_HEADERS_BH. The "_BH" suffix conventionally identifies a base history table, i.e., the physical store of header attribute history rows that the view projects. The view text selects from this base table, aliased KHH, mapping columns one-for-one and appending the ROWID as ROW_ID for uniqueness and identification purposes.

Because the relationship is a straightforward projection, there is no join, aggregation, or filter evident in the documented view text. Any row-level filtering (for example by contract, version, or date) is expected to be applied by the calling query. The view therefore inherits the row population and retention characteristics of OKS_K_HEADERS_BH, and any change in the base table's data or definition flows directly into the view.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing how a contract's commitment reference changed over time, reconciling renewal terms that were proposed versus those actually used, and feeding historical contract attributes into data warehouse or compliance extracts.

To locate history rows for a specific commitment:

  • SELECT id, major_version, commitment_id, renewal_status FROM oks_k_headers_hv WHERE commitment_id = :p_commitment_id ORDER BY id, major_version;

To inspect the evolution of renewal and tax attributes for a contract:

  • SELECT id, major_version, tax_code, tax_amount, renewal_pricing_type, renewal_markup_percent, renewal_markup_percent_used FROM oks_k_headers_hv WHERE id = :p_contract_id ORDER BY major_version;

Joining back to OKS_K_HEADERS_BH using ROW_ID allows correlation to the physical base history row when additional base-table columns outside the view projection are required.