Search Results line_currency_code

Overview

IBE_OE_ORDER_LINES_V is an iStore (IBE) reporting view that exposes order line detail for orders captured through Oracle iStore and the Oracle Order Management capture flow. Its stated purpose, per the ETRM metadata, is simply to "get the Order Line Details." It is a presentation-layer construct rather than a transactional entity: it joins header, line, and item information so that a single query returns everything required to display or export a line-level view of a sales order.

The view is one of a family of "ASO"_derived objects used by iStore and by external integrations that must read order capture data without navigating the full Order Management schema. Because it is built on top of the ASO views (not directly on OE_ORDER_LINES_ALL), it inherits the filtering, security, and profile-driven behavior defined in the ASO layer. It is therefore best understood as a convenience join, not as an authoritative base table. Note that in the documented 12.2.2 environment the object is marked "Not implemented in this database," meaning the view definition is registered in ETRM for reference but is not created in every instance; availability must be confirmed in the target environment before it is referenced by custom code.

Underlying Base Objects

The ETRM metadata documents the view as based on aso_i_oe_order_headers_v and aso_i_oe_order_lines_v. The view text confirms this and adds a third source, MTL_SYSTEM_ITEMS_VL, for item attributes. Specifically, the FROM clause joins ASO_I_OE_ORDER_LINES_V (aliased OL) to ASO_I_OE_ORDER_HEADERS_V (OH) on HEADER_ID, and to MTL_SYSTEM_ITEMS_VL (MSI) on INVENTORY_ITEM_ID, with the additional restriction that MSI.ORGANIZATION_ID equals OE_PROFILE.VALUE('OE_ORGANIZATION_ID', OL.ORG_ID). The item join is therefore organization-scoped through the OE_ORGANIZATION_ID profile option, which ties the item master lookup to the operating unit's default inventory organization. Header-level columns are pulled from the header view (notably TRANSACTIONAL_CURR_CODE), while line-level columns come from the line view. No base tables are documented directly against OE_ORDER_LINES_ALL or OE_ORDER_HEADERS_ALL; their contribution is indirect, inherited through the ASO layer.

Key Columns

• LINE_ID, HEADER_ID — primary and foreign keys linking the line to its order; HEADER_ID is the join key to the header view.
• LINE_NUMBER, SHIPMENT_NUMBER, OPTION_NUMBER — line and shipment sequencing, plus the option number for configured (ATO) items.
• LINE_CATEGORY_CODE, LINE_TYPE_ID, ORDER_SOURCE_ID — classification of the line and the order source.
• ITEM_NUMBER, ITEM_DESCRIPTION — sourced from MTL_SYSTEM_ITEMS_VL (SEGMENT1 and DESCRIPTION).
• ORDERED_QUANTITY, ORDER_QUANTITY_UOM, PRICING_QUANTITY, SHIPPING_QUANTITY, SHIPPED_QUANTITY, FULFILLED_QUANTITY, CANCELLED_QUANTITY — quantity metrics across the order-to-ship lifecycle.
• UNIT_SELLING_PRICE, UNIT_LIST_PRICE, EXTENDED_PRICE — pricing columns, each formatted through FND_CURRENCY.SAFE_GET_FORMAT_MASK using the transactional currency. EXTENDED_PRICE is computed as NVL(UNIT_SELLING_PRICE,0) * (NVL(ORDERED_QUANTITY,0) - NVL(CANCELLED_QUANTITY,0)). Because these are TO_CHAR outputs, they are strings, not numeric values suitable for arithmetic.
• SCHEDULE_SHIP_DATE, SCHEDULE_ARRIVAL_DATE, ACTUAL_SHIPMENT_DATE, ACTUAL_ARRIVAL_DATE, PROMISE_DATE, REQUEST_DATE — scheduling and fulfillment dates.
• SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, SHIP_TO_CONTACT_ID — party/site references.
• ATO_LINE_ID, TOP_MODEL_LINE_ID, LINK_TO_LINE_ID, MODEL_GROUP_NUMBER, CUST_MODEL_SERIAL_NUMBER — configuration and model relationships.
• CANCELLED_FLAG, OPEN_FLAG, BOOKED_FLAG — line status indicators.
• CREATION_DATE, LAST_UPDATE_DATE — audit columns for incremental extraction.

Common Use Cases and Queries

Typical uses include iStore order-status screens, customer-facing order history extracts, and integration feeds that push line detail to fulfillment or analytics. Because EXTENDED_PRICE and the price columns are pre-formatted character strings, they are suited to display and reporting rather than to aggregation.

A basic line listing for a single order:

• SELECT line_number, item_number, item_description, ordered_quantity, extended_price, open_flag FROM ibe_oe_order_lines_v WHERE header_id = :p_header_id ORDER BY line_number;

An open-line query for a date-bounded extract:

• SELECT header_id, line_id, item_number, ordered_quantity, schedule_ship_date FROM ibe_oe_order_lines_v WHERE open_flag = 'Y' AND creation_date >= :p_from_date AND creation_date < :p_to_date;

Before relying on the view, confirm it exists in the target instance, since the documentation records it as not implemented in every database, and verify that the OE_ORGANIZATION_ID profile is set so the MTL_SYSTEM_ITEMS_VL join resolves item data correctly.