Search Results quote_description




Overview
Explore in AI Chat

Overview

OKC_REL_OBJ_QUOTE_HEADERS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKC – Contracts Core product. It is registered as a VALID object in both EBS 12.1.1 and 12.2.2. The view supplies a denormalized, relationship-aware projection of quote header information by joining quote header data to the contract relationship records that link a quote to a contract, and to the sales resource who owns the quote.

The view is primarily used in reporting, diagnostics, and integration scenarios where quote data must be examined from the perspective of a contract relationship rather than directly from the quote header. Because it exposes TOTAL_QUOTE_PRICE as a first-class column, it is a common target for queries that need to retrieve the monetary value of a quote without navigating the full OKX quote schema or the OKC relationship model manually. The view is not a base table and should not be used for DML.

Underlying Base Objects

The documented definition of the view references three underlying objects:

  • OKX_QUOTE_HEADERS_V (VIEW) — supplies the quote header attributes: name, description, total quote price, currency, and resource identifier. The join is driven from this view to the relationship object through HDR.ID1.
  • OKC_K_REL_OBJS (SYNONYM) — the Contracts Core relationship object that ties a contract or quote to a related object. It contributes OBJECT1_ID1, the JTOT object code, and CHR_ID.
  • JTF_RS_RESOURCE_EXTNS_VL (VIEW) — the resource extension view that resolves the sales resource identifier to a displayable resource name. The join is an outer join (HDR.RESOURCE_ID = JR.RESOURCE_ID(+)), so quotes without an assigned resource are still returned with a null sales person.

Because two of the three objects are themselves views, the view encapsulates joins across the OKX quotation schema, the OKC contracts schema, and the JTF resource schema. This makes it convenient but also means query performance is governed by the underlying view definitions, and access is effectively read-only.

Key Columns

  • QUOTE_NUMBER — the name of the quote header, serving as the business-facing identifier.
  • QUOTE_DESCRIPTION — descriptive text from the quote header.
  • SALES_PERSON — the resource name of the assigned sales person, resolved through the resource extension view; may be null for quotes with no resource.
  • TOTAL_QUOTE_PRICE — the aggregate value of the quote. This is the column most often targeted by searches such as "total_quote_price" and is the principal financial attribute of the view.
  • OBJECT1_ID1 — the identifier of the related object on side one of the relationship record, correlated to the quote header identifier.
  • JTOT_OBJECT_CODE — the JTOT object code associated with the relationship, indicating the related object type.
  • CHR_ID — the contract header relationship identifier used to associate the quote relationship to a contract.
  • CURRENCY — the currency code for the quote and its total price.

Common Use Cases and Queries

Typical uses include reconciling quote values against contract relationships, listing quotes with their owners and currencies for pipeline reporting, and locating the contract relationship record (CHR_ID) for a given quote. A representative query retrieving all quotes with their value and sales person is:

  • SELECT quote_number, quote_description, sales_person, total_quote_price, currency FROM apps.okc_rel_obj_quote_headers_v;
  • SELECT quote_number, total_quote_price FROM apps.okc_rel_obj_quote_headers_v WHERE total_quote_price > 10000;
  • SELECT chr_id, object1_id1, jtot_object_code, quote_number, total_quote_price FROM apps.okc_rel_obj_quote_headers_v WHERE object1_id1 = :quote_id;

Because the view performs outer and inner joins across multiple schema views, filters on TOTAL_QUOTE_PRICE or QUOTE_NUMBER should be applied where possible, and results compared against OKX_QUOTE_HEADERS_V directly when precise quote-only values are required.