Search Results opp_description




Overview
Explore in AI Chat

Overview

APPS.OKC_REL_OBJ_OPP_HEADERS_V is a reporting view in the Oracle E-Business Suite (EBS) Contracts and Oracle Trade Management (ETRM) schema. It is defined in the APPS schema and is documented in the ETRM 12.2.2 metadata set, with equivalent behavior in 12.1.1. The view joins opportunity header information to the relationship objects that link opportunities to contracts and other related entities, thereby presenting opportunity attributes alongside the relationship keys required for cross-object reporting.

The view's principal purpose is to expose a denormalized, read-only projection of opportunity data (number, description, amount, currency, win probability, status) together with the relationship object identifiers managed by the OKC (Contracts) relationship framework. Because the underlying opportunity object is itself exposed through a view, OKC_REL_OBJ_OPP_HEADERS_V serves primarily as a query and integration surface rather than a transactional entity. It is commonly consumed by reports, concurrent programs, and inbound/outbound interfaces that must reconcile opportunity records with their associated contract relationships.

Users searching on the term opp_description will find that this view is the documented location where the opportunity description is aliased. The column alias OPP_DESCRIPTION is explicitly defined in the view text, making this view the appropriate source when the business requirement is to retrieve descriptions of opportunities that participate in a relationship.

Underlying Base Objects

The documented base objects referenced by this view are:

The view is defined with an inner join between these two sources on the equality HDR.ID1 = REL.OBJECT1_ID1. Only opportunity headers that have at least one corresponding relationship object row are therefore returned; opportunities without a relationship are excluded. Both base objects are referenced through the APPS schema, and the view is created and owned by APPS.

Key Columns

  • OPP_NUMBER — sourced from HDR.NAME; the opportunity identifier or name.
  • OPP_DESCRIPTION — sourced from HDR.DESCRIPTION; this is the column users locate when searching for opp_description.
  • TOTAL_AMOUNT — the opportunity's total monetary value.
  • OBJECT1_ID1 — the relationship object identifier linking to the opportunity (ID1).
  • JTOT_OBJECT1_CODE — the object type code identifying the related object class.
  • CHR_ID — the contract header or relationship identifier from OKC_K_REL_OBJS.
  • CURRENCY — sourced from HDR.CURRENCY_CODE; the opportunity currency.
  • WIN_PROBABILITY — the opportunity's assessed probability of winning.
  • STATUS — the opportunity's current status.

Common Use Cases and Queries

Typical uses include reporting opportunities linked to contracts, extracting opportunity descriptions for interfacing systems, and reconciling relationship records with opportunity headers. A basic query to retrieve opportunity descriptions alongside relationship keys is:

  • SELECT OPP_NUMBER, OPP_DESCRIPTION, TOTAL_AMOUNT, CURRENCY, STATUS FROM APPS.OKC_REL_OBJ_OPP_HEADERS_V;
  • SELECT OPP_DESCRIPTION, WIN_PROBABILITY FROM APPS.OKC_REL_OBJ_OPP_HEADERS_V WHERE STATUS = 'OPEN';
  • SELECT OPP_NUMBER, OPP_DESCRIPTION, CHR_ID FROM APPS.OKC_REL_OBJ_OPP_HEADERS_V WHERE CURRENCY = 'USD';

Because the view performs an inner join, queries seeking opportunities irrespective of relationship existence should target OKX_OPP_HEADERS_V directly. When both opportunity and contract-side identifiers are required in a single result set, OKC_REL_OBJ_OPP_HEADERS_V is the documented, supported access path.