Search Results oke_k_headers_secure_hv




Overview
Explore in AI Chat

Overview

OKE_K_HEADERS_SECURE_HV is a secured historical contract header extended information view owned by the APPS schema in Oracle E-Business Suite, within the OKE – Project Contracts product family. The name decomposes into three functional signals: "K_HEADERS" identifies the contract header entity, "SECURE" indicates that row-level security predicates are applied, and "HV" denotes a historical version view that exposes multiple major/minor versions of a contract rather than only the current revision. The view therefore delivers a version-aware, security-filtered projection of contract header data for reporting, integration, and inquiry purposes.

Its principal role is to present contract header attributes in a form suitable for external consumption without requiring the caller to replicate OKE's internal security logic. Because the underlying secured package supplies the authorization predicate, downstream reports, extracts, and interfaces automatically inherit the same access restrictions that apply inside the Project Contracts application forms.

Underlying Base Objects

The documented base objects are OKC_K_HEADERS_B (synonym), OKE_K_HEADERS_FULL_HV (view), OKC_K_SECURITY_PKG (package), and OKE_UTILS (package). OKC_K_HEADERS_B is the core contract headers table in the OKC (Contracts Core) schema, holding the primary header records. OKE_K_HEADERS_FULL_HV is the unsecured historical version view that assembles header columns, including the descriptive columns populated only on the current version, into a single wide row. OKE_K_HEADERS_SECURE_HV wraps that view and applies the security predicate obtained from OKC_K_SECURITY_PKG, with supporting logic drawn from OKE_UTILS.

The layering is significant. OKC_K_HEADERS_B stores the transactional data; OKE_K_HEADERS_FULL_HV performs the version join and column expansion; the security package evaluates the caller's access rights against authoring organization, contract ownership, and related security assignments; and OKE_UTILS supplies shared helper functions. The result is a view that is both denormalized for reporting convenience and filtered for authorization compliance.

Key Columns

The view exposes the full column list of OKE_K_HEADERS_FULL_HV. The following groups are most significant:

Notably, columns ending in _YN carry the user-facing Yes/No display values, while the corresponding _FLAG columns carry the internal flag. Reporting queries generally use the _YN columns.

Common Use Cases and Queries

The view is typically used for contract register reporting, version history analysis, security-respecting data extracts, and integration feeds. Because it is secured, it is the preferred source when querying on behalf of a specific user rather than a batch integration user.

Listing all versions of a contract:

SELECT k_number, major_version, minor_version, version_disp, status, start_date, end_date
FROM apps.oke_k_headers_secure_hv
WHERE k_number = :contract_number
ORDER BY major_version, minor_version;

Extracting active contract headers with project linkage:

SELECT k_number, k_alias, authoring_org, project_number, project_name,
       currency_code, status, booked_yn, start_date, end_date
FROM apps.oke_k_headers_secure_hv
WHERE open_yn = 'Y'
  AND end_date >= TRUNC(SYSDATE)
ORDER BY authoring_org, k_number;

Reviewing compliance attributes for audit purposes:

SELECT k_number, dcAA_audit_req_yn, cas_yn, cqa_yn,
       human_subject_yn, sb_plan_req_yn
FROM apps.oke_k_headers_secure_hv
WHERE classified_yn = 'Y';

Because security is enforced at runtime, result sets differ by the connecting user's authoring organization access. Integration processes that must see all rows should be executed under a user or responsibility granted unrestricted OKE contract access; otherwise rows are silently suppressed rather than raising an error, which is a common source of variance between report totals and base-table counts.