Results for “shippable_flag”

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

Overview

The view APPS.JAI_OM_WSH_DELIVERY_NAME_V is a reporting and integration object belonging to the JA – Asia/Pacific Localizations product family in Oracle E-Business Suite. It is defined in the APPS schema and holds a documented status of VALID across the ETRM 12.2.2 metadata, which is consistent with its presence in 12.1.1 and 12.2.2 environments. Functionally, the view consolidates delivery-line localization attributes captured in the Oracle Order Management and Shipping execution flow, joining the Asia/Pacific localization extension table for order and shipping lines to the standard delivery detail table. It is intended to expose fiscal and statutory invoice references — VAT, excise, and GST invoice numbers — alongside core delivery identifiers and shipping attributes, so that downstream reports, interfaces, and localization compliance processes can resolve delivery-level tax documentation without directly querying the underlying base tables. As a view rather than a table, it carries no independent storage and inherits privileges, row-level access, and organization security from its base objects and the calling responsibility.

Underlying Base Objects

The documented definition of the view references two base objects, both exposed as synonyms in the APPS schema:

• JAI_OM_WSH_LINES_ALL (SYNONYM) — the Asia/Pacific localization extension for Order Management / shipping lines, supplying the order header, delivery, customer, invoice number, shippable flag, and operating unit context.
• WSH_DELIVERY_DETAILS (SYNONYM) — the standard Shipping execution delivery detail table, supplying the ship-to location and the delivery detail key used for the join.

The two objects are correlated on JOWLA.DELIVERY_DETAIL_ID = WDD.DELIVERY_DETAIL_ID, meaning each row of the view corresponds to a localization line record that has a matching delivery detail. Because it is a simple equi-join view with no aggregation, the grain of the result set is that of the localization line table, filtered to rows with a valid delivery detail. The view therefore serves as a thin localization facade over standard shipping data, which is why it remains directly accessible from the APPS schema in both 12.1.1 and 12.2.2.

Key Columns

The view projects nine columns, each drawn from one of the two base objects:

• ORDER_HEADER_ID — identifier of the sales order header associated with the delivery line.
• DELIVERY_ID — identifier of the delivery to which the line belongs.
• CUSTOMER_ID — the customer (ship-to party) for the order line.
• SHIP_TO_LOCATION_ID — the ship-to site, sourced from WSH_DELIVERY_DETAILS.
• VAT_INVOICE_NO — the VAT invoice reference recorded for the localization line.
• EXCISE_INVOICE_NO — the excise invoice reference, relevant for countries operating excise regimes.
• GST_INVOICE_NO — the GST invoice reference used in GST-applicable jurisdictions.
• SHIPPABLE_FLAG — indicates whether the localization line is eligible for shipping.
• ORG_ID — the operating unit identifier, enabling multi-org secured querying.

Common Use Cases and Queries

Typical uses include reconciling statutory invoice numbers against shipped deliveries, supplying localization invoice references to tax reporting extracts, and validating ship-to and shippable status during order-to-shipment audits. Because ORG_ID is exposed, queries should be run under a responsibility with the correct operating unit context.

SELECT ORDER_HEADER_ID, DELIVERY_ID, CUSTOMER_ID,
       SHIP_TO_LOCATION_ID, VAT_INVOICE_NO,
       EXCISE_INVOICE_NO, GST_INVOICE_NO, SHIPPABLE_FLAG
FROM   APPS.JAI_OM_WSH_DELIVERY_NAME_V
WHERE  ORG_ID = :p_org_id
AND    DELIVERY_ID = :p_delivery_id;

A second pattern retrieves all localization lines for a sales order, which is useful for invoice reconciliation:

SELECT ORDER_HEADER_ID, DELIVERY_ID, VAT_INVOICE_NO, GST_INVOICE_NO
FROM   APPS.JAI_OM_WSH_DELIVERY_NAME_V
WHERE  ORDER_HEADER_ID = :p_order_header_id
AND    SHIPPABLE_FLAG = 'Y';

Note that the view is documented with no aggregation and is read-only; it should be used for inquiry and extraction, not for DML. Performance depends on indexes on JAI_OM_WSH_LINES_ALL.DELIVERY_DETAIL_ID and WSH_DELIVERY_DETAILS.DELIVERY_DETAIL_ID, so selective predicates on ORG_ID, DELIVERY_ID, or ORDER_HEADER_ID are recommended.