Results for “qa_eres_wsh_deliverables_v”

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

Overview

QA_ERES_WSH_DELIVERABLES_V is an APPS-owned reporting view in the Oracle E-Business Suite Quality (QA) module, validated for both 12.1.1 and 12.2.2. It exposes shipping electronic record (e-record) data derived from the Shipping Execution (WSH) deliverables layer, providing a flattened, denormalized row set suitable for e-records, compliance reporting, and integration with external shipping documentation systems. The view is built directly over the WSH_DLVY_DELIVERABLES_V view and layers in Quality-specific helper functions for status decoding, locator resolution, and container naming, so that shipping content, lot and serial details, weight/volume attributes, and source document references are available in a single query surface without requiring the caller to navigate the underlying WSH deliverable structure.

Underlying Base Objects

The view is defined over the WSH_DLVY_DELIVERABLES_V view, which supplies the delivery, delivery detail, delivery line, and container-level detail. Because ETRM documents indirect synonyms rather than physical tables for several dependencies, the referenced base objects are: HR_ALL_ORGANIZATION_UNITS_TL (organizations), MTL_CUSTOMER_ITEMS (customer item cross-references), MTL_PARAMETERS (inventory organization parameters), MTL_SYSTEM_ITEMS_KFV (concatenated item segments), PA_PROJECTS_ALL and PA_TASKS (project and task references), WSH_LOOKUPS (lookup meanings such as preferred grade), plus the QA_ERES_PKG, QA_FLEX_UTIL, and WSH_CONTAINER_UTILITIES packages used for decoding and formatting.

Key Columns

• DELIVERY_ID, DELIVERY_DETAIL_ID, DELIVERY_LINE_ID — core WSH identifiers; the third SELECT element substitutes container name for container-type rows via DECODE.
• Released status — computed by QA_ERES_PKG.DECODE_WSH_RELEASED_STATUS using SOURCE_CODE, RELEASED_STATUS, INV_INTERFACED_FLAG, and OE_INTERFACED_FLAG.
• Item and lot/serial detail — CONCATENATED_SEGMENTS, ITEM_DESCRIPTION, REVISION, TRACKING_NUMBER, LOT_NUMBER, SERIAL_NUMBER, TO_SERIAL_NUMBER, and CUSTOMER_REQUESTED_LOT_FLAG, the column of interest here, which indicates whether the customer stipulated a specific lot.
• Quantity and UOM columns — REQUESTED_QUANTITY, PICKED_QUANTITY, SHIPPED_QUANTITY with primary and secondary UOMs.
• Weight and volume — MAXIMUM_LOAD_WEIGHT, GROSS_WEIGHT, TARE_WEIGHT, NET_WEIGHT, WEIGHT_UOM_CODE, MAXIMUM_VOLUME, VOLUME, VOLUME_UOM_CODE.
• Container and location — parent and master container names via WSH_CONTAINER_UTILITIES, ORGANIZATION_CODE, HRORG.NAME, SUBINVENTORY, and locator via QA_FLEX_UTIL.LOCATOR.
• Source references — SOURCE_NAME, SOURCE_HEADER_NUMBER, SOURCE_HEADER_TYPE_NAME, SOURCE_LINE_NUMBER, and source quantities.
• Project, customer, and attribute columns — PPA.NAME, PT.TASK_NUMBER, CUSTOMER_ITEM_NUMBER, CUSTOMER_ITEM_DESC, CUSTOMER_PROD_SEQ, CUSTOMER_DOCK_CODE, and ATTRIBUTE1 through ATTRIBUTE7 (plus additional attributes) for extensibility.

Common Use Cases and Queries

The view supports e-record reporting that must document exactly what was shipped, including lot and serial traceability and whether lots were customer-mandated.

• Retrieve all deliverables where the customer dictated the lot, for compliance review:

SELECT delivery_id, delivery_detail_id, inventory_item_id, lot_number, serial_number FROM qa_eres_wsh_deliverables_v WHERE customer_requested_lot_flag = 'Y';

• List shipped quantities and weights per organization for a delivery:

SELECT organization_id, organization_code, item_description, shipped_quantity, net_weight, weight_uom_code FROM qa_eres_wsh_deliverables_v WHERE delivery_id = :p_delivery_id;

• Correlate deliverables to source documents and projects for traceability:

SELECT source_header_number, source_line_number, name, task_number, customer_item_number FROM qa_eres_wsh_deliverables_v WHERE source_name IS NOT NULL;

These patterns reflect the view's design as a read-only reporting and integration surface; it should not be used for transactional updates, and query performance benefits from filtering on DELIVERY_ID or ORGANIZATION_ID.