Search Results okx_orderline

Overview

The view APPS.OKC_REL_OBJ_ORDER_LINES_V is a reporting and integration construct within the Oracle E-Business Suite Order Capture and Contracts (ETRM) schema. It presents order line records that have been explicitly linked to contract relationships through the OKC relationship object framework. As implied by the search term "okx_orderline," the view surfaces Order Capture order lines identified by the relationship code OKX_ORDERLINE, joining them to their associated contract relationship objects and item definitions. It is not a base transactional entity but a denormalized projection intended to simplify the retrieval of contract-to-order-line associations for both reporting and programmatic integration.

Underlying Base Objects

The ETRM metadata documents that this view is defined over three referenced objects, all of which are themselves views or packages. The FROM clause references OKX_ORDER_LINES_V (aliased OL), OKC_K_REL_OBJS_V (aliased REL), and OKX_SYSTEM_ITEMS_V (aliased SI). The ASO_ORDER_INT package is also documented as a referenced base object, reflecting the Order Capture integration layer that underpins order line data. The central join is OL.ID1 = REL.OBJECT1_ID1, meaning an order line's identifier is matched to relationship object 1's primary identifier. A second join, OL.INVENTORY_ITEM_ID = SI.ID1 AND OL.ORG_ID = SI.ID2, resolves the inventory item and organization to a system item record. The filter REL.JTOT_OBJECT1_CODE = 'OKX_ORDERLINE' restricts results to relations that specifically bind contract objects to Order Capture order lines.

Key Columns

• LINE_NUMBER — A composed identifier concatenating the line number with optional shipment number and option number, delimited by periods. This yields the canonical human-readable order line reference.
• ORDER_HEADER_ID — The header identifier of the parent order, derived from OL.HEADER_ID.
• DESCRIPTION — The item description obtained from the system items view.
• QUANTITY — The ordered quantity (OL.ORDERED_QUANTITY).
• AMOUNT — The total amount (OL.TOTAL_AMOUNT) for the line.
• OBJECT1_ID1 — The relationship object identifier from the contract relations view, correlating with the order line identifier.
• CHR_ID — The contract header or contract relationship identifier anchoring the association.
• ITEM_NAME — The system item name (SI.NAME).

Together these columns enable a contract-aware view of order line content without requiring the caller to reconstruct the multi-way join.

Common Use Cases and Queries

This view is typically queried to reconcile contract relationships against Order Capture lines, for example to list all order lines financially or legally tied to a specific contract. A representative query filters by contract identifier:

SELECT line_number, order_header_id, item_name, quantity, amount
FROM apps.okc_rel_obj_order_lines_v
WHERE chr_id = :contract_id;

Alternatively, reporting against a specific order header uses ORDER_HEADER_ID. Because the view is read-only and built entirely on other views, it is suited to operational reporting and integration extracts rather than direct DML. Developers should be aware that OKX_ORDER_LINES_V and OKC_K_REL_OBJS_V carry their own security and performance characteristics, so query cost depends on the volume of relationship objects filtered by the OKX_ORDERLINE code. Use of indexed predicates on CHR_ID or ORDER_HEADER_ID is recommended for performance.