Search Results contract_status_code




Overview
Explore in AI Chat

Overview

OKS_ENT_HDR_SUMMARY_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the OKS (Service Contracts) product family. As documented in ETRM for releases 12.1.1 and 12.2.2, the view "holds all the service contracts summary and party information," presenting a denormalized, flattened projection of service contract headers joined to their associated party roles. Its purpose is to simplify access to contract-level attributes — including the contract number, amount, currency, status, effective dates, and customer party identifier — without requiring report authors or integration developers to navigate the multi-table structure of the underlying OKC (Contracts Core) schema.

The view is particularly relevant to users searching on "contract_amount," because it exposes the estimated amount stored on the contract header under the alias CONTRACT_AMOUNT. It effectively serves as a lightweight, read-only interface for service contract summary reporting, dashboards, and external integrations that need contract header data combined with customer identification in a single query.

Underlying Base Objects

The view is defined over three documented base objects (referenced via APPS synonyms): OKC_K_HEADERS_ALL_B, OKC_K_PARTY_ROLES_B, and OKC_SUBCLASSES_B. The ETRM view text confirms the join structure using OKC_K_HEADERS_V (HDR), OKC_K_PARTY_ROLES_B (PTY), and OKC_SUBCLASSES_V (CLS). Header records are linked to party roles on HDR.ID = PTY.CHR_ID, and the subclass is matched on HDR.SCS_CODE = CLS.CODE. Two important filters restrict the result set: only non-template contracts are returned (HDR.TEMPLATE_YN = 'N'), and only rows belonging to the SERVICE subclass are included (CLS.CLS_CODE = 'SERVICE'). Additionally, only party roles of type CUSTOMER or SUBSCRIBER are considered, ensuring that each returned contract row carries the relevant external party. Because the view joins a header to party roles, a contract with multiple qualifying roles may appear more than once.

Key Columns

Common Use Cases and Queries

Typical use cases include contract value summaries, customer-to-contract listings, currency exposure analysis, and status/date-driven reporting on active service agreements. The view is well suited to concurrent programs, BIPublisher data models, and outbound interfaces.

The following query lists active service contracts with their amount and party:

  • SELECT contract_number, contract_amount, currency_code, start_date_active, end_date_active FROM oks_ent_hdr_summary_v WHERE contract_status_code = 'ACTIVE' ORDER BY contract_amount DESC;
  • SELECT party_id, SUM(contract_amount) total_value FROM oks_ent_hdr_summary_v GROUP BY party_id;
  • SELECT contract_number, contract_amount FROM oks_ent_hdr_summary_v WHERE currency_code = 'USD' AND start_date_active >= SYSDATE;

Because the view is read-only and filtered to non-template SERVICE contracts, it should not be used for data manipulation or for retrieving non-service agreements.