Search Results oke_k_lines_secure_hv




Overview
Explore in AI Chat

Overview

The view APPS.OKE_K_LINES_SECURE_HV is a secured, version-aware reporting object within the Oracle E-Business Suite (EBS) Project Contracts (OKE) module. Its name encodes its behavior: the _HV suffix denotes a "history view" that exposes both current and historical (versioned) contract line records, while the SECURE component indicates that row visibility is filtered through Oracle's Contracts security framework. The view is documented as a "Secured contract historical line extended information view," meaning it joins contract line history to a wide set of descriptive and financial attributes and then applies row-level access restrictions before returning data to the caller.

In EBS 12.1.1 and 12.2.2, this view is registered in the APPS schema and holds a VALID status. It is not a base table but a query layer intended for reporting, inquiry, and integration. Because it is secured, it should be preferred over direct queries against the underlying OKE_K_LINES structures whenever a report must respect the security profile of the requesting user. This makes it suitable for concurrent programs, Oracle Reports, OA Framework pages, and BI Publisher data templates where contractual data must be filtered by responsibility.

Underlying Base Objects

The ETRM metadata for 12.2.2 records the following referenced base objects:

  • OKC_K_HEADERS_B (SYNONYM) — the contract header base table, providing header-level context such as the owning contract and its identifiers.
  • OKE_K_LINES_FULL_HV (VIEW) — the full historical line view from which the secured, extended columns are derived. OKE_K_LINES_SECURE_HV effectively wraps this full view and adds the security predicate.
  • OKE_K_SECURITY_PKG (PACKAGE) — the security package that supplies the access-control logic restricting which contract lines a given user may see.
  • OKE_UTILS (PACKAGE) — a utility package used for common helper functions and value resolution within the OKE module.

Structurally, the view selects aliased columns (prefixed K.) from the historical line source, meaning the projection is largely a passthrough of OKE_K_LINES_FULL_HV with additional security filtering. The contract header is reached through OKC_K_HEADERS_B to associate each line with its parent contract, while OKE_K_SECURITY_PKG and OKE_UTILS supply the functions and predicates that enforce visibility.

Key Columns

The view exposes an extensive column list organized around versioning, line identity, and extended commercial attributes:

Common Use Cases and Queries

Typical uses include historical contract line extracts, billing reconciliation, and secured reporting where row-level access must be enforced. Because it is a secured view, callers inherit the OKE security model automatically.

  • Retrieve all historical versions of a contract's lines for audit:
SELECT K_LINE_ID, MAJOR_VERSION, MINOR_VERSION, VERSION_DISP,
       LINE_NUMBER, LINE_DESCRIPTION, LINE_VALUE, STATUS
FROM   APPS.OKE_K_LINES_SECURE_HV
WHERE  HEADER_ID = :p_header_id
ORDER  BY K_LINE_ID, MAJOR_VERSION, MINOR_VERSION;
  • List billable lines with their project and task context for a billing report:
SELECT LINE_NUMBER, PROJECT_NUMBER, TASK_NUMBER,
       LINE_QUANTITY, UNIT_PRICE, LINE_VALUE
FROM   APPS.OKE_K_LINES_SECURE_HV
WHERE  BILLABLE_YN = 'Y'
AND    TRUNC(START_DATE) BETWEEN :p_from AND :p_to;

Notes for developers: always qualify with the APPS schema, rely on the security predicate rather than adding manual access checks, and avoid treating _HV rows as current-only — filter on version columns when a single latest version is required.