Search Results cc_auth_code




Overview
Explore in AI Chat

Overview

OKS_K_HEADERS_V is a public view owned by the APPS schema in Oracle E-Business Suite. It belongs to the OKS (Service Contracts) product family and exposes service contract header attributes that are required by the Oracle Service Contracts pricing, billing, and renewal engines. The view is flagged VALID in the documented 12.2.2 environment and is present in both 12.1.1 and 12.2.2 releases as part of the standard Service Contracts seed data and API support layer.

The view presents attributes held in the OKS_K_HEADERS_B table, which stores pricing and billing header information keyed to a service contract through the CHR_ID (contract header reference) column. The suffix convention (_V) indicates a view, and the naming pattern is consistent with other OKS pricing-related data objects.

Underlying Base Objects

The documented metadata for the ETRM 12.2.2 release lists a single referenced base object: the synonym OKS_K_HEADERS_B owned by APPS. In practice, that synonym points to the underlying OKS_OKS_K_HEADERS_B table, which is the entity that physically stores the service contract header pricing and billing records.

The view is a straight projection of columns from that base object, using KHR as the driving alias. It does not perform joins to other tables in the documented excerpt, which makes it a low-cost access path for retrieving pricing header attributes. The ROWID of the base row is exposed through the ROW_ID column, allowing applications that use the view for updateable operations to resolve the underlying row.

The primary keys exposed are ID (the K_HEADERS row identifier) and CHR_ID (the associated contract header reference). ACCT_RULE_ID links the pricing header to accounting rules, while COMMITMENT_ID and BILLING_PROFILE_ID link to procurement and billing profile configuration respectively.

Key Columns

Common Use Cases and Queries

The view is used primarily in Service Contracts reporting, renewals processing, and integration extracts. Because the user query referenced ar_interface_yn, note that this particular column is not present in the documented view text; that attribute belongs to other OKS contract header or interface views and is commonly joined through CHR_ID. The following patterns apply:

  • Retrieve pricing and billing header details for a specific contract: SELECT id, chr_id, payment_type, tax_status, billing_profile_id FROM oks_k_headers_v WHERE chr_id = :chr_id;
  • Renewal workbench and notification extracts: SELECT chr_id, renewal_status, electronic_renewal_flag, renewal_po_required, renewal_price_list FROM oks_k_headers_v WHERE renewal_status = 'PENDING';
  • Revenue recognition reconciliation: SELECT chr_id, est_rev_percent, est_rev_date, rev_est_percent_used FROM oks_k_headers_v;
  • Tax exception reporting, joining to contractual headers via CHR_ID to resolve contract numbers.

Updates should be performed through the supported Service Contracts APIs rather than directly against this view, although ROW_ID is exposed to support row-based updates when necessary.