Search Results ship_attribute1

Overview

IBE_ORDER_SHIPMENTS_V is a reporting view within the Oracle E-Business Suite iStore (IBE) module. It consolidates shipment-level scheduling and fulfillment data associated with iStore order capture lines, joining shipment records to ship-to party and location information. Its principal role is to expose a flattened, query-friendly projection of shipment attributes—promise dates, scheduling dates, shipping and freight instructions, reserved and requested quantities, and descriptive flexfield context—so that iStore order management, order tracking, and downstream integration components can retrieve delivery-related detail without navigating the normalized shipment schema directly.

For environments where a user or partner (for example, Ingram Micro Services Ltd.) is researching a specific delivery, quotation-driven shipment, or fulfillment obligation, this view provides the shipment identifier and the associated party and location context needed to trace the physical delivery against the originating order line.

Underlying Base Objects

The view is defined over the shipment entity (aliased S) in the iStore/I store order shipment model, joined to a party table (aliased P, supplying PARTY_NAME) and a location table (aliased L, supplying LOCATION_ID and the full set of location descriptive flexfield columns). The shipment source contributes the primary shipment identifiers, audit columns, quote and order line references, scheduling dates, ship-to identifiers, shipping and freight codes, quantity fields, reservation identifiers, and a set of descriptive flexfield attributes (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15) aliased with a SHIP_ prefix to avoid collision with the location flexfield columns.

The location source contributes the location identifier, its own update timestamp, and a parallel block of flexfield attributes (ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15) that are not prefixed, representing ship-to location context. The party source contributes the human-readable PARTY_NAME. In the specific environment from which this metadata was drawn, the view is recorded as not implemented in the database; therefore the referenced base objects are not enumerated in the ETRM documentation, and the precise table names must be confirmed against the deployment's data dictionary.

Key Columns

• SHIPMENT_ID — primary shipment identifier linking the view to the underlying shipment record.
• QUOTE_HEADER_ID / QUOTE_LINE_ID / ORDER_LINE_ID — quotation and order line references tying the shipment back to its commercial origin.
• PROMISE_DATE, REQUEST_DATE, SCHEDULE_SHIP_DATE — the delivery promise, request, and scheduled shipping dates central to delivery reporting.
• SHIP_TO_PARTY_ID / SHIP_TO_PARTY_SITE_ID / PARTY_NAME / LOCATION_ID — ship-to party and site identification, with the resolved party name and location key.
• SHIP_METHOD_CODE, FREIGHT_TERMS_CODE, FREIGHT_CARRIER_CODE, FOB_CODE — transportation and freight terms governing the delivery.
• SHIPPING_INSTRUCTIONS / PACKING_INSTRUCTIONS — free-text fulfillment directions.
• QUANTITY / RESERVED_QUANTITY / RESERVATION_ID — requested versus reserved quantities and the associated reservation.
• SHIP_ATTRIBUTE1–15 and location ATTRIBUTE1–15 — descriptive flexfield segments for shipment and location respectively.
• SHIP_CREATION_DATE, SHIP_CREATED_BY, SHIP_LAST_UPDATE_DATE — audit columns for traceability.

Common Use Cases and Queries

Typical uses include reviewing scheduled deliveries by promise date, reconciling reserved quantities against requested quantities, and reporting shipment freight terms alongside ship-to party and location. A representative query for delivery research is:

SELECT shipment_id, order_line_id, promise_date, schedule_ship_date, party_name, location_id, quantity, reserved_quantity FROM ibe_order_shipments_v WHERE party_name = 'Ingram Micro Services Ltd.' ORDER BY promise_date;

Additional filters on SHIP_METHOD_CODE, FREIGHT_CARRIER_CODE, or the location flexfield columns support carrier-level and site-specific delivery analysis. Because the view is documented as not implemented in the reference database, availability and column behavior should be validated against the target EBS 12.1.1 or 12.2.2 instance before relying on it in production reporting.