Search Results okc_rel_obj_order_lines_v




Overview
Explore in AI Chat

Overview

The APPS.OKC_REL_OBJ_ORDER_LINES_V view is a Contracts Core (OKC) reporting and integration object in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents order line information in the context of contracts relationships, joining contract relationship records to order lines and item master data. The view is designed to answer the question of which order lines are associated with which contract relationships, and to present that association in a form suitable for reporting, for contract-to-order reconciliation, and for downstream integration logic that needs to retrieve ordered quantities, amounts, and item details for the lines tied to a contract relationship object.

Its name reflects its purpose: OKC (Contracts Core) + REL (relationship) + OBJ (object) + ORDER_LINES. The view resolves the relationship between a contract relationship object of code OKX_ORDERLINE and the corresponding order line record, enriching the line with description, quantity, amount, and item name attributes.

Underlying Base Objects

The view is defined over three base objects documented in the ETRM metadata:

  • OKX_ORDER_LINES_V — the order lines view (aliased OL), supplying line number, shipment number, option number, header ID, ordered quantity, total amount, inventory item ID, and org ID.
  • OKC_K_REL_OBJS_V — the contract relationship objects view (aliased REL), supplying OBJECT1_ID1, CHR_ID, and JTOT_OBJECT1_CODE.
  • OKX_SYSTEM_ITEMS_V — the system items view (aliased SI), supplying item description and item name (NAME), keyed by inventory item ID and org ID.

The join predicates are: OL.ID1 = REL.OBJECT1_ID1, OL.INVENTORY_ITEM_ID = SI.ID1, OL.ORG_ID = SI.ID2, and REL.JTOT_OBJECT1_CODE = 'OKX_ORDERLINE'. The metadata also lists ASO_ORDER_INT (PACKAGE) as a referenced base object, indicating the order line view derives from the order integration staging structure. This means the view is effectively a contract-to-order-line relationship view, filtered to order line relationship objects only.

Key Columns

  • LINE_NUMBER — a concatenated display string built from LINE_NUMBER, SHIPMENT_NUMBER, and OPTION_NUMBER using dot separators (for example 1.1.0). This is a formatted identifier, not the raw numeric line number.
  • ORDER_HEADER_ID — the order header identifier from OKX_ORDER_LINES_V (OL.HEADER_ID). This is the column matched by the user's search term "order_header_id" and is the primary key for grouping order lines.
  • DESCRIPTION — the item description from OKX_SYSTEM_ITEMS_V.
  • QUANTITY — the ordered quantity (OL.ORDERED_QUANTITY).
  • AMOUNT — the total amount for the line (OL.TOTAL_AMOUNT).
  • OBJECT1_ID1 — the contract relationship object identifier from OKC_K_REL_OBJS_V.
  • CHR_ID — the contract relationship identifier, linking the line to its contract header relationship.
  • ITEM_NAME — the item name from OKX_SYSTEM_ITEMS_V.

Common Use Cases and Queries

Typical use cases include reconciling contract relationships to ordered lines, retrieving all order lines for a given sales order header alongside their contract relationship identifiers, and building contract-versus-actual quantity or amount reports.

Example query to retrieve all lines for a specific order header:

  • SELECT ORDER_HEADER_ID, LINE_NUMBER, ITEM_NAME, QUANTITY, AMOUNT, CHR_ID FROM OKC_REL_OBJ_ORDER_LINES_V WHERE ORDER_HEADER_ID = :p_order_header_id;

Example query to list ordering data for a specific contract relationship:

  • SELECT CHR_ID, LINE_NUMBER, ITEM_NAME, QUANTITY, AMOUNT FROM OKC_REL_OBJ_ORDER_LINES_V WHERE CHR_ID = :p_chr_id ORDER BY LINE_NUMBER;

Because the view exposes CHR_ID and ORDER_HEADER_ID, it is commonly joined back to OKC_K_HEADERS_V or to order management tables for cross-functional reporting. Note that the view returns one row per matched order line, and only for relationships where JTOT_OBJECT1_CODE equals 'OKX_ORDERLINE'.