Search Results oks_header_details_v




Overview
Explore in AI Chat

Overview

The OKS_HEADER_DETAILS_V view is a denormalized reporting object in the Oracle EBS Service Contracts (OKS) module, owned by the APPS schema and shipped in a VALID state across release 12.1.1 and 12.2.2. It consolidates the descriptive and financial header information of a service or warranty contract together with customer party details, currency, operating unit, and bill-to address into a single, query-friendly structure. Its principal value is that it resolves the many-to-one joins that a technician or report developer would otherwise have to construct manually, and it translates the internally stored contract status code into a user-readable meaning through the OKC_STATUSES_V view. Because the view is restricted to contracts whose SCS_CODE is 'SERVICE' or 'WARRANTY', it functions as a purpose-built contract register rather than a general header dump. The ESTIMATED_AMOUNT column, which users frequently search for, is one of the earliest-selectable financial attributes exposed here and represents the contract's estimated monetary value as maintained on the underlying header.

Underlying Base Objects

The view is defined over four primary sources joined in its SELECT statement, backed by the additional package and view objects documented in the ETRM metadata. The driving object is OKC_K_HEADERS_V (aliased K), which supplies the contract identifiers, dates, status code, currency, organization identifiers, and the estimated amount. OKC_K_PARTY_ROLES_B (aliased PR) provides the party role rows, constrained so that the role code is 'CUSTOMER' and the relationship is the header-level role (CLE_ID IS NULL). HZ_PARTIES (aliased PX) resolves the party identifier into the party number and party name. OKX_CUST_SITE_USES_V (aliased BTO) supplies the bill-to site description via an outer join on BILL_TO_SITE_USE_ID, which permits contracts without a populated bill-to site to remain in the result set. OKC_STATUSES_V is used in a scalar subquery to convert the stored STS_CODE into its MEANING. The metadata further lists ARP_ADDR_LABEL_PKG and OKC_UTIL as referenced package objects, reflecting the utility logic embedded in the component views.

Key Columns

  • CONTRACT_ID — Surrogate primary key (K.ID) of the contract header; the join key to most other OKS tables.
  • CONTRACT_NUMBER / CONTRACT_NUMBER_MODIFIER — The user-visible contract number and its version modifier, forming the business identifier.
  • START_DATE / END_DATE — Effective service period of the contract, heavily used in coverage and expiry analysis.
  • STATUS — Decoded status meaning obtained from OKC_STATUSES_V rather than the raw code.
  • SHORT_DESCRIPTION — Free-text header description.
  • PARTY_ID / PARTY_NUMBER / PARTY_NAME — Customer identity and number derived from HZ_PARTIES.
  • HEADER_BTO_ADDRESS — Descriptive bill-to address label; nullable where no site use is linked.
  • CURRENCY — Currency code of the contract header.
  • ORG_ID / INV_ORG_ID — Authoring (operating unit) and inventory organization context; ORG_ID is the primary Multi-Org filter.
  • LAST_UPDATE_DATE — Audit column supporting incremental and changed-since extraction patterns.
  • ESTIMATED_AMOUNT — The estimated monetary value of the contract, sourced from K.ESTIMATED_AMOUNT.

Common Use Cases and Queries

Typical usage includes contract registers, customer-facing entitlement listings, estimated-value pipeline reporting, and integration extracts that feed downstream repositories or data warehouses. Because the view already filters to service and warranty contracts and decodes status, it is a convenient source for coverage and renewal analytics keyed on END_DATE.

The following query lists active customer contracts with their estimated value, restricted to the caller's operating unit:

SELECT contract_number,
       party_name,
       status,
       start_date,
       end_date,
       currency,
       estimated_amount
  FROM apps.oks_header_details_v
 WHERE org_id = :p_org_id
   AND status = 'Active'
   AND estimated_amount > 0
 ORDER BY estimated_amount DESC;

A second common pattern aggregates estimated value by customer for a date range, exploiting the pre-resolved PARTY_NAME and STATUS columns:

SELECT party_name,
       COUNT(*) AS contract_count,
       SUM(estimated_amount) AS total_estimated
  FROM apps.oks_header_details_v
 WHERE end_date >= :p_from_date
   AND start_date <= :p_to_date
 GROUP BY party_name
 ORDER BY total_estimated DESC;

When querying this view, always supply the ORG_ID predicate unless cross-operating-unit visibility is explicitly required, and treat HEADER_BTO_ADDRESS as optional because the bill-to join is outer.