Search Results split_by

Overview

OKX_ORDER_LINES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKX – Contracts Integration product. Its documented purpose is to expose order line information in a flattened, denormalized form suitable for consumption by the Contracts Integration flows and by downstream reporting. The view carries a validity status of VALID and is present in both the 12.1.1 and 12.2.2 release lines, where the APPS-owned definition remains stable.

The view is characteristic of EBS "V" interface objects: it projects a large number of operational columns from the underlying order line entity while synthesizing placeholder values for descriptive flexfield-style attributes. Specifically, ID2 is hard-coded to '#', NAME and DESCRIPTION are set to NULL, END_DATE_ACTIVE is NULL, START_DATE_ACTIVE is populated with SYSDATE, and STATUS is fixed to 'A'. These conventions allow generic key-flexfield and value-set consumers to treat the view as a standard descriptive entity without requiring a physical table.

Underlying Base Objects

ETRM metadata for this view documents two referenced base objects: the package ASO_ORDER_INT and the synonym OE_ORDER_LINES_ALL. OE_ORDER_LINES_ALL is the core Order Management order lines entity; the view's column list mirrors that table almost one-for-one, selecting LINE_ID, HEADER_ID, ORG_ID, item, quantity, pricing, tax, and address/contact attributes directly from it. The alias OL in the view text confirms OE_ORDER_LINES_ALL as the primary driving source.

ASO_ORDER_INT is the Order Capture integration package used by Oracle Fusion/Order Capture style integrations. Its inclusion indicates that OKX_ORDER_LINES_V participates in the Contracts Integration pipeline, where order capture data is passed to contract generation and validation logic. Because the view is defined over the OE_ORDER_LINES_ALL synonym rather than a hard-coded schema-qualified table, it inherits the standard EBS synonym resolution and remains portable across the 12.1.1 and 12.2.2 table structures.

Key Columns

• ID1 / ID2 / NAME / DESCRIPTION / STATUS – Surrogate keys and descriptive placeholders. ID1 maps to LINE_ID; ID2 is the literal '#'.
• HEADER_ID, ORG_ID, LINE_NUMBER, LINE_TYPE_ID – Order header and operating unit context for each line.
• ORDERED_ITEM, INVENTORY_ITEM_ID – Item identifiers used for item validation and pricing.
• ORDERED_QUANTITY, SHIPPED_QUANTITY, FULFILLED_QUANTITY, CANCELLED_QUANTITY, SHIPPING_QUANTITY – Quantity lifecycle measures, each paired with its UOM column.
• PRICING_QUANTITY, PRICING_QUANTITY_UOM, PRICE_LIST_ID, PRICING_DATE – Pricing attributes for contract and invoice derivation.
• TAX_EXEMPT_FLAG, TAX_EXEMPT_NUMBER, TAX_EXEMPT_REASON_CODE, TAX_CODE, TAX_RATE, TAX_DATE – Tax determination inputs.
• SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, DELIVER_TO_ORG_ID, SOLD_TO_ORG_ID, SHIP_FROM_ORG_ID, SOLD_FROM_ORG_ID and their associated CONTACT_ID columns – Party and address routing.
• AGREEMENT_ID, SHIPMENT_NUMBER, SHIPPING_METHOD_CODE, FREIGHT_CARRIER_CODE, DEMAND_CLASS_CODE, SHIP_TOLERANCE_ABOVE/BELOW, CUST_PO_NUMBER – Fulfillment and agreement linkage.
• INVOICE_INTERFACE_STATUS_CODE – Indicates whether the line has been passed to the invoice interface, relevant to AutoInvoice and receipt accounting.

Common Use Cases and Queries

The view is typically queried when order line detail must be joined to contract or invoice processing logic. Although the search term "reference_customer_trx_line_id" does not appear in the documented column list, it is a common linkage column in adjacent OKX and OM interface views and is frequently sought when tracing a contract line back to a receivable transaction line.

A representative query retrieving line detail for a given order:

• SELECT header_id, line_id, line_number, ordered_item, ordered_quantity, shipped_quantity, pricing_quantity, tax_code FROM okx_order_lines_v WHERE header_id = :p_header_id ORDER BY line_number;

A reconciliation query identifying lines not yet invoiced:

• SELECT line_id, line_number, invoice_interface_status_code FROM okx_order_lines_v WHERE header_id = :p_header_id AND invoice_interface_status_code IS NULL;

Because NAME, DESCRIPTION, and ID2 are constants, the view should not be used for descriptive reporting; it is intended as a key-flexfield-compatible projection of OE_ORDER_LINES_ALL for Contracts Integration consumers.