Results for “opp_header_id”

16 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKC_REL_OBJ_OPP_LINES_V is an Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 reporting view owned by the APPS schema within the OKC – Contracts Core product. It exposes a denormalized, query-ready projection of opportunity line details combined with contract relationship metadata and inventory item descriptions. Its principal function is to bridge the Contracts (OKC) and Sales/Order Capture (OKX) functional domains so that opportunity lines associated with contract relationships can be reported through a single, joined result set without requiring the caller to reproduce the underlying multi-table join logic.

The view is classified as VALID and is intended for read-only consumption in reports, concurrent programs, form LOVs, and integration extracts. Because it depends on _V views in the OKX schema rather than on base tables directly, its output reflects the current business rules governing opportunity lines and system items.

Underlying Base Objects

The documented base objects referenced are all views rather than physical tables:

  • OKX_OPP_LINES_V — the primary source of opportunity line data, supplying the line identifier (ID1), the opportunity header identifier, quantity, total amount, inventory item identifier, and organization identifier.
  • OKC_K_REL_OBJS_V — supplies the contract relationship object mapping, contributing OBJECT1_ID1, CHR_ID, and JTOT_OBJECT1_CODE.
  • OKX_SYSTEM_ITEMS_V — supplies the item name and description, matched on inventory item and organization.

Joins are governed by two predicates: OL.ID1 = REL.OBJECT1_ID1 plus the static filter REL.JTOT_OBJECT1_CODE = 'OKX_OPPLINES', and (OL.INVENTORY_ITEM_ID = SI.ID1 AND OL.ORGANIZATION_ID = SI.ID2). The relationship join restricts the returned row set to contract relationships whose JTOT object code identifies them as opportunity lines, which is why the column OBJECT1_ID1 appears both as a filter key and as a projected output column.

Key Columns

  • LINE_NUMBER — aliased from OL.ID1; the opportunity line identifier.
  • OPP_HEADER_ID — the opportunity header to which the line belongs.
  • DESCRIPTION — item description sourced from OKX_SYSTEM_ITEMS_V.
  • QUANTITY and AMOUNT — line quantity and total amount (total_amount exposed as AMOUNT).
  • OBJECT1_ID1 — the contract relationship object identifier, correlated to the opportunity line. This is the column most frequently searched for, since it links contract relationships to their originating opportunity lines.
  • CHR_ID — the contract relationship identifier from OKC_K_REL_OBJS_V.
  • ITEM_NAME — the system item name (SI.NAME).

Common Use Cases and Queries

Typical scenarios include contract-to-opportunity reconciliation reports, identifying which opportunity lines underpin a given contract relationship, and validating item descriptive data for lines extracted into integration interfaces. A representative query retrieving all opportunity lines linked to a specific contract relationship identifier:

  • SELECT line_number, opp_header_id, object1_id1, chr_id, item_name, quantity, amount FROM apps.okc_rel_obj_opp_lines_v WHERE object1_id1 = :object1_id1;
  • SELECT object1_id1, chr_id, SUM(amount) FROM apps.okc_rel_obj_opp_lines_v GROUP BY object1_id1, chr_id ORDER BY object1_id1;

Because the view filters strictly on JTOT_OBJECT1_CODE = 'OKX_OPPLINES', queries cannot retrieve non-opportunity relationship objects. Additionally, rows are silently dropped when an inventory item or organization has no matching entry in OKX_SYSTEM_ITEMS_V; outer-join behavior must therefore be implemented in a custom view if orphan lines require reporting. Filtering on OBJECT1_ID1 and CHR_ID together is the most selective access path and is recommended for high-volume extracts.