Results for “shippable_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The JAI_OM_WSH_DELIVERIES_V view is an Oracle E-Business Suite dictionary object owned by the APPS schema and classified under the JA – Asia/Pacific Localizations product family. It presents a consolidated, delivery-detail level projection of shipping and order-management data, combining outbound delivery information with localized line attributes maintained by the Asia/Pacific localization layer. The view is defined as a simple (non-joining, column-projection) view over existing base objects, exposing a stable set of delivery, item, quantity, address, and descriptive-flexfield columns suitable for reporting, extract programs, and interface processing.

Because the object is a view rather than a table, it holds no data of its own and inherits the transaction-time semantics of its underlying delivery and localization tables. It is typically consumed by localization reports, tax and statutory extracts, and custom integration programs that require delivery-level detail without querying the base WSH delivery tables directly.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view references two base objects:

• JAI_OM_WSH_LINES_ALL (referenced via a synonym) — the Asia/Pacific localization table that stores line-level shipping attributes and descriptive-flexfield values.
• WSH_DELIVERY_DETAILS (referenced via a synonym) — the standard Oracle Shipping execution table holding delivery detail records for outbound shipments.

The view text selects all of its columns from a single alias A, indicating that the view joins or unifies these sources upstream and then projects the resulting row set. Columns such as TP_ATTRIBUTE_CATEGORY and TP_ATTRIBUTE1 through TP_ATTRIBUTE15 reflect the localization table’s descriptive-flexfield structure, while columns such as DELIVERY_DETAIL_ID, SHIPPED_QUANTITY, and RELEASED_STATUS derive from the standard shipping detail model.

Key Columns

• ROW_ID — the ROWID of the source row, exposed as a unique row identifier for the view.
• DELIVERY_DETAIL_ID — primary key linking to the underlying delivery detail record.
• SOURCE_HEADER_ID / SOURCE_LINE_ID / SOURCE_HEADER_NUMBER — originating order header and line references.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, SUBINVENTORY, REVISION, LOT_NUMBER, SERIAL_NUMBER, LOCATOR_ID — item and inventory-attribute context for the shipped goods.
• REQUESTED_QUANTITY, SHIPPED_QUANTITY, DELIVERED_QUANTITY, CANCELLED_QUANTITY, QUALITY_CONTROL_QUANTITY — quantity measures across the delivery lifecycle.
• OE_INTERFACED_FLAG — indicates whether the delivery detail has been interfaced to Order Management; this column is closely related to the INV_INTERFACED_FLAG concept users search for, and both flags govern downstream interface status.
• MVT_STAT_STATUS — movement statistics status used for localization/statutory reporting.
• CUSTOMER_ID, SHIP_TO_LOCATION_ID, SHIP_FROM_LOCATION_ID, DELIVER_TO_LOCATION_ID, INTMED_SHIP_TO_LOCATION_ID, ORG_ID — party and location context.
• TP_ATTRIBUTE1–15, TP_ATTRIBUTE_CATEGORY — Asia/Pacific descriptive flexfield attributes.

Common Use Cases and Queries

Typical usage covers delivery reporting, localization statutory extracts, and reconciliation of shipping detail against order management interfacing. A representative query filtering on interface status is shown below.

• List deliveries not yet interfaced to Order Management:
  SELECT delivery_detail_id, source_header_number, inventory_item_id, shipped_quantity, oe_interfaced_flag FROM apps.jai_om_wsh_deliveries_v WHERE oe_interfaced_flag = 'N';
• Report localized flexfield attributes per delivery detail:
  SELECT delivery_detail_id, tp_attribute_category, tp_attribute1, tp_attribute2 FROM apps.jai_om_wsh_deliveries_v WHERE org_id = :p_org_id;
• Aggregate shipped quantities by item for statutory movement statistics:
  SELECT inventory_item_id, SUM(shipped_quantity) qty FROM apps.jai_om_wsh_deliveries_v GROUP BY inventory_item_id;

Because the view is read-only and depends on localization tables, it should be queried within the correct operating unit (ORG_ID) and its results validated against the current state of WSH_DELIVERY_DETAILS and JAI_OM_WSH_LINES_ALL.