Search Results oke_k_headers_secure_v




Overview
Explore in AI Chat

Overview

OKE_K_HEADERS_SECURE_V is an APPS-owned database view in the Oracle E-Business Suite Project Contracts (OKE) module. It exposes the extended contract header information from the contract repository while applying the security model that governs who may see which contract records. In EBS 12.1.1 and 12.2.2, the view is delivered in VALID status and is used as a reporting and integration surface for contract header data.

Unlike the underlying full header view, OKE_K_HEADERS_SECURE_V is designed to return only those contract headers that the querying user is entitled to access. This makes it the appropriate source for custom reports, Discoverer workbooks, Oracle Business Intelligence extracts, and interface programs that must respect the same access rules enforced by the Project Contracts application. Because security is applied within the view, downstream code does not need to reproduce the contract access logic itself.

Underlying Base Objects

The view is constructed over contract header data together with the security decision logic. The documented base objects referenced by OKE_K_HEADERS_SECURE_V in release 12.2.2 are:

  • OKC_K_HEADERS_B (synonym) — the underlying Contracts Core base table that stores the primary contract header row, including identifiers, versioning, status, and flags.
  • OKE_K_HEADERS_FULL_V (view) — the extended, denormalized header view that joins the contract header to its descriptive, project, funding, and classification attributes.
  • OKE_K_SECURITY_PKG (package) — the security package that evaluates the current user's access to a given contract header.
  • OKE_UTILS (package) — utility package supplying supporting functions used in the view definition.

The SELECT list projects columns from the full header view (aliased K) such as K_HEADER_ID, MAJOR_VERSION, K_NUMBER, K_ALIAS, STATUS_CODE, and PROJECT_ID. The security package determines the predicate that filters rows, so the effective result set is the intersection of the full header data and the user's permitted contracts.

Key Columns

The view exposes an extensive set of header attributes. Principal columns include:

Common Use Cases and Queries

Typical uses include secured contract listings, project-to-contract reconciliation, and extract feeds for downstream systems. Because security is embedded, a simple query returns only authorized rows:

  • List active contracts for the current user: SELECT k_number, k_alias, status, start_date, end_date FROM oke_k_headers_secure_v WHERE status_code = 'ACTIVE';
  • Contracts tied to a project: SELECT k_number, project_number, project_name FROM oke_k_headers_secure_v WHERE project_id = :p_project_id;
  • Compliance review: SELECT k_number, dcaa_audit_req_yn, cas_yn, human_subject_yn FROM oke_k_headers_secure_v WHERE booked_yn = 'Y';
  • Integration extract: SELECT k_header_id, major_version, k_number, buy_or_sell, currency_code FROM oke_k_headers_secure_v;

Consult the ETRM repository for release-specific column availability, as the projected columns shown above reflect the 12.2.2 documented definition.