Results for “oks_cont_headers_v”

20 results




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

Overview

OKS_CONT_HEADERS_V is a lightweight reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Service Contracts (OKS) module. Its documented purpose is to expose contract header records for the object type OKS_K_HEADER, which is referenced by the update level attribute used during Mass Change processing. In this role the view acts as a narrow projection of contract header data, presenting only the fields that the Mass Change framework requires when evaluating or applying updates at the header level.

Because the view is filtered to a single application context, it returns only those contract headers belonging to Service Contracts. This makes it a convenient, low-overhead access point for reporting and integration scenarios in which the caller needs contract identity and validity dates without the wide column set of the full contract header entity. The view is marked VALID, and the same definition is documented across ETRM 12.1.1 and 12.2.2, indicating stable behavior between those releases.

Underlying Base Objects

The view is defined over a single documented base object, OKC_K_HEADERS_V, which is itself a view in the Contracts (OKC) core schema. OKC_K_HEADERS_V supplies the contract header rows, and OKS_CONT_HEADERS_V narrows them with the predicate APPLICATION_ID = 515, the application identifier for Service Contracts. The documented metadata also references the OKC_UTIL package, which supplies the utility logic used by the OKC contract header view family for derived values such as the contract number modifier and formatted identifiers.

The relationship is therefore one of progressive restriction: OKC_K_HEADERS_V provides the enterprise-wide contract header projection, OKC_UTIL contributes formatting and derivation behavior, and OKS_CONT_HEADERS_V exposes only the Service Contracts subset. No base tables are accessed directly by OKS_CONT_HEADERS_V; it depends entirely on the OKC layer beneath it.

Key Columns

  • ID1 — Maps to the contract header identifier (ID). The literal alias ID1 distinguishes it from ID2.
  • ID2 — A constant literal '#' returned for framework compatibility; it carries no contract data.
  • NAME — The contract number, aliased from CONTRACT_NUMBER. This is the value most commonly searched for as "contract_number".
  • CONTRACT_NUMBER — The contract number itself, exposed under its native name for direct filtering and joining.
  • CONTRACT_NUMBER_MODIFIER — The modifier segment appended to the contract number, used to distinguish contract versions or revisions.
  • DESCRIPTION — The short description of the contract header, aliased from SHORT_DESCRIPTION.
  • START_DATE — The contract start date.
  • END_DATE — The contract end date.

Common Use Cases and Queries

The most frequent use is locating a Service Contracts header by its number, either in full or by pattern. The following query retrieves header details for a specific contract number:

  • SELECT id1, contract_number, contract_number_modifier, description, start_date, end_date FROM oks_cont_headers_v WHERE contract_number = :contract_number;

For wildcard searches against the contract number, a LIKE predicate on CONTRACT_NUMBER is typical:

  • SELECT contract_number, contract_number_modifier, description FROM oks_cont_headers_v WHERE contract_number LIKE :prefix || '%';

Because the view exposes both START_DATE and END_DATE, it also supports validity and expiry reporting, such as identifying contracts active on a given date or contracts nearing expiration. In Mass Change contexts, the view supplies the header-level rows that the OKS_K_HEADER object type consumes when the update level is set to header. Integration consumers use it as a stable, Service Contracts-scoped interface when the full OKC contract header view is broader than required.