Search Results oks_auth_headers_v




Overview
Explore in AI Chat

Overview

OKS_AUTH_HEADERS_V is a view owned by the APPS schema in Oracle E-Business Suite, defined within the Service Contracts (OKS) product module. It consolidates header-level data for service contract authoring records — the umbrella records used by Oracle Service Contracts to manage contract capture, negotiation, approval, and lifecycle tracking. The view surfaces a broad set of descriptive, status, and administrative attributes drawn from the base contract header tables, together with translation-table content for textual fields.

The view is commonly accessed in reporting, integration, and personalization scenarios requiring a flattened, read-only window onto contract authorization headers. It exposes both operational columns (contract number, currency, dates, status codes) and informational columns (descriptions, comments, set-aside details). Because it is a view rather than a table, it presents no storage of its own and inherits the security and integrity characteristics of its underlying base objects.

Underlying Base Objects

The documented base objects underlying OKS_AUTH_HEADERS_V are:

  • OKC_K_HEADERS_B (SYNONYM) — the primary contract header base table.
  • OKC_K_HEADERS_TL (SYNONYM) — the translation table for header-level descriptive text.
  • OKC_STATUSES_V (VIEW) — statuses view referenced for status-related attributes.
  • OKC_SUBCLASSES_V (VIEW) — subclasses view referenced for classification data.
  • OKC_UTIL (PACKAGE) — utility package used by the view definition.
  • OKS_K_HEADERS_B (SYNONYM) — the Service Contracts header base synonym.

The view text joins the header base table (aliased CHRB) to the translation table (aliased CHRT), projecting header business keys and status fields from the base and descriptive fields from the translation. Textual columns such as SHORT_DESCRIPTION, COMMENTS, DESCRIPTION, COGNOMEN, NON_RESPONSE_REASON, and NON_RESPONSE_EXPLAIN originate from the translation table, while identifiers, dates, and codes originate from the base table.

Key Columns

The user search term non_response_explain maps directly to the NON_RESPONSE_EXPLAIN column, which stores the free-text explanation recorded when a non-response reason is captured.

Common Use Cases and Queries

Typical scenarios include reporting on contracts with outstanding non-response reasons, tracking approval and cancellation dates, and extracting header data for integrations.

  • Non-response analysis: 
    SELECT contract_number, non_response_reason, non_response_explain
FROM   apps.oks_auth_headers_v
WHERE  non_response_reason IS NOT NULL;
  • Active contract listing: 
    SELECT contract_number, sts_code, start_date, end_date
FROM   apps.oks_auth_headers_v
WHERE  deleted_yn = 'N' AND archived_yn = 'N';
  • Approval tracking: 
    SELECT contract_number, date_approved, date_issued
FROM   apps.oks_auth_headers_v
WHERE  date_approved IS NOT NULL;

Queries should account for translation-language joins and view-based access controls enforced by the APPS schema.