Search Results intmed_ship_to




Overview
Explore in AI Chat

Overview

OE_ORDER_LINES_V is an APPS-owned view in the Oracle E-Business Suite Order Management (ONT) module, documented as VALID and present in both release 12.1.1 and 12.2.2. Its stated purpose in the ETRM reference is to present order line information for consumption by the Sales Order form. Functionally it acts as a reporting-oriented projection of the order line entity: it exposes the identifier and descriptive columns needed to render, validate, and query sales order lines without requiring the caller to join the surrounding Order Management and Trading Community tables directly.

Because the view is defined in the APPS schema and is a view rather than a table, it is read-mostly in nature. It is typically used by forms, concurrent programs, extensions, and custom reports that need a stable, denormalized read interface over order line data. The view does not itself hold data; all content is resolved at runtime from the underlying base objects listed below.

Underlying Base Objects

The documented view metadata lists the following referenced base objects: AR_LOOKUPS (VIEW), HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_LOCATIONS, HZ_PARTIES, HZ_PARTY_SITES, HZ_RELATIONSHIPS, MTL_PARAMETERS, OE_ORDER_HEADERS, OE_ORDER_LINES_ALL, OE_TRANSACTION_TYPES_TL, QP_LIST_HEADERS_B, QP_LIST_HEADERS_TL, RA_RULES, and RA_TERMS_TL. All entries other than AR_LOOKUPS are recorded as synonyms in the APPS schema.

The principal driving object is OE_ORDER_LINES_ALL, which supplies the line-level attributes. OE_ORDER_HEADERS provides header context such as order-level identifiers and transaction type. OE_TRANSACTION_TYPES_TL supplies translated transaction type descriptions. The HZ_ family resolves party, account, site, location, role, and relationship details, and MTL_PARAMETERS supplies inventory organization context. Pricing and terms-related lookups are drawn from QP_LIST_HEADERS_B, QP_LIST_HEADERS_TL, RA_RULES, and RA_TERMS_TL, while AR_LOOKUPS supplies code-to-meaning translations for various lookup columns.

Key Columns

The view exposes a broad set of line attributes. Identity and organization columns include ROW_ID, LINE_ID, ORG_ID, HEADER_ID, LINE_TYPE_ID, and LINE_NUMBER. Item and scheduling columns include ORDERED_ITEM, INVENTORY_ITEM_ID, ITEM_REVISION, REQUEST_DATE, PROMISE_DATE, SCHEDULE_ARRIVAL_DATE, and SCHEDULE_SHIP_DATE.

Quantities and units are represented by ORDER_QUANTITY_UOM, PRICING_QUANTITY, PRICING_QUANTITY_UOM, CANCELLED_QUANTITY, SHIPPED_QUANTITY, ORDERED_QUANTITY, FULFILLED_QUANTITY, SHIPPING_QUANTITY, and SHIPPING_QUANTITY_UOM. Financial and tax attributes include TAX_EXEMPT_FLAG, TAX_EXEMPT_NUMBER, TAX_CODE, TAX_RATE, TAX_DATE, PRICE_LIST_ID, and PRICING_DATE.

Party and site references include SOLD_TO_ORG_ID, SHIP_FROM_ORG_ID, SHIP_TO_ORG_ID, DELIVER_TO_ORG_ID, INTMED_SHIP_TO_ORG_ID, INVOICE_TO_ORG_ID, and the corresponding contact identifiers. Project and referencing columns include PROJECT_ID, TASK_ID, SOURCE_DOCUMENT_ID, SOURCE_DOCUMENT_LINE_ID, ORIG_SYS_DOCUMENT_REF, and ORIG_SYS_LINE_REF, which support source-document traceability and order import reconciliation.

Common Use Cases and Queries

Typical uses include order line extraction for reporting, validation of line quantities against shipped and fulfilled quantities, and source-document reconciliation for imported or externally originated orders.

  • Order line detail for a specific header: 
    SELECT LINE_ID, LINE_NUMBER, ORDERED_ITEM, ORDERED_QUANTITY, ORDER_QUANTITY_UOM
FROM   APPS.OE_ORDER_LINES_V
WHERE  HEADER_ID = :p_header_id
ORDER  BY LINE_NUMBER;
  • Open quantity analysis by item: 
    SELECT ORDERED_ITEM, SUM(ORDERED_QUANTITY) ORDERED, SUM(SHIPPED_QUANTITY) SHIPPED
FROM   APPS.OE_ORDER_LINES_V
WHERE  ORG_ID = :p_org_id
GROUP  BY ORDERED_ITEM;
  • Source traceability lookup: 
    SELECT LINE_ID, SOURCE_DOCUMENT_ID, SOURCE_DOCUMENT_LINE_ID, ORIG_SYS_DOCUMENT_REF
FROM   APPS.OE_ORDER_LINES_V
WHERE  ORIG_SYS_LINE_REF = :p_ref;

Queries should always be qualified by ORG_ID or HEADER_ID where possible, since the view resolves over a substantial set of joined lookups and master data tables.