Search Results warehouse_name

Overview

OEFV_SHIPMENT_LINES is an Order Entry (OE) view in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes order line detail records enriched with shipping, warehouse, item, customer, and delivery attributes. It is a denormalized, reporting-oriented construct that joins the SO_LINE_DETAILS table to a set of master and reference tables spanning Order Entry, Inventory (INV), and organization definition schemas. The view is intended to present "shipment line" information — one row per order line detail record — with the descriptive values most commonly requested in operational reporting, rather than raw coded identifiers alone.

Each row corresponds to a single line detail record (DETAIL.LINE_DETAIL_ID), and carries both the foreign key identifiers and the resolved descriptive names for the associated item, warehouse, subinventory, customer item, ship-to site, contact, terms, and delivery/departure. Because the view resolves lookups into meanings and joins master item definitions, it is well suited for ad hoc queries, custom concurrent programs, and integration extracts where human-readable shipment information is required without re-implementing the join logic.

Underlying Base Objects

The documented view text defines OEFV_SHIPMENT_LINES over SO_LINE_DETAILS (aliased DETAIL) as the driving table and SO_LINES_ALL (aliased LINE). Additional referenced objects appearing in the FROM clause include MTL_SECONDARY_INVENTORIES (SUBINV), MTL_SYSTEM_ITEMS (INV_ITEM, MASTER_ITEM, DETAIL_ITEM), MTL_CUSTOMER_ITEMS (CUST_ITEM), ORG_ORGANIZATION_DEFINITIONS (ORG), along with commented references to MTL_ITEM_REVISIONS, MTL_LOT_NUMBERS, and destination/site/contact/terms tables. The ETRM metadata records no separately documented base object list and notes that the object is "Not implemented in this database" for the captured environment, meaning the view text reflects the shipped definition but the database instance under inspection did not instantiate the view. The resolution directives embedded in the SELECT (for example '_KF:INV:MSTK:INV_ITEM' and '_LA:...:SO_LOOKUPS:...:MEANING') indicate that item keys and lookup codes are resolved into descriptive values at query time.

Key Columns

• WAREHOUSE_ID / ORGANIZATION_NAME — the warehouse identifier and the resolved organization name from ORG_ORGANIZATION_DEFINITIONS. This is the column most relevant to searches for "warehouse_name."
• SECONDARY_INVENTORY_NAME — the subinventory associated with the line detail, drawn from MTL_SECONDARY_INVENTORIES.
• LINE_NUMBER, LINE_ID, LINE_DETAIL_ID — the order line and detail identifiers linking back to SO_LINES_ALL and SO_LINE_DETAILS.
• QUANTITY, UNIT_CODE — ordered/shipped quantity and unit of measure.
• INVENTORY_ITEM_ID — the inventory item key, with resolved item identifiers via MTL_SYSTEM_ITEMS.
• CUSTOMER_ITEM_NUMBER — customer-specific item number from MTL_CUSTOMER_ITEMS.
• SHIP_METHOD_CODE, SHIPMENT_PRIORITY_CODE, DEMAND_CLASS_CODE — coded attributes with lookup meanings resolved through SO_LOOKUPS and FND_COMMON_LOOKUPS.
• DELIVERY_ID / DELIVERY.NAME, DEPARTURE_ID / DEPARTURE.NAME — delivery and departure references.
• LOCATION, CONTACT name, TERM.NAME — ship-to site location, ship-to contact name, and payment terms.
• SCHEDULE_DATE, LATEST_ACCEPTABLE_DATE, LOAD_SEQ_NUMBER — scheduling and load sequencing attributes.
• Attribute flags — SHIPPABLE_FLAG, TRANSACTABLE_FLAG, RESERVABALE_FLAG, INCLUDED_ITEM_FLAG, REQUIRED_FOR_REVENUE_FLAG, resolved to Yes/No meanings.
• WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY.

Common Use Cases and Queries

The view is typically used to report shipment lines by warehouse, to reconcile order line details against inventory organization and subinventory, and to feed downstream extracts. A representative query retrieving shipment lines for a given warehouse follows:

SELECT line_number, warehouse_id, organization_name, secondary_inventory_name, inventory_item_id, quantity, unit_code, schedule_date FROM oefv_shipment_lines WHERE organization_name = :warehouse_name;

Because the underlying objects are inventory and order tables, queries should always be filtered by organization, date range, or line identifiers to avoid full scans. Join the view back to SO_LINES_ALL or OE_ORDER_HEADERS_ALL on LINE_ID to obtain order context, and to MTL_SYSTEM_ITEMS on INVENTORY_ITEM_ID for segment-level item attributes. Where the view is not implemented in a given database, equivalent results are obtained by joining SO_LINE_DETAILS to ORG_ORGANIZATION_DEFINITIONS and MTL_SECONDARY_INVENTORIES directly using WAREHOUSE_ID.