Search Results h_org




Overview

WSHFV_PICK_LINE_DETAIL is a Shipping Execution (WSH) view that consolidates picking line detail records with associated header, item, container, and organization context. In Oracle EBS 12.1.1 and 12.2.2, the object is registered under the OE - Order Entry product family and is documented in ETRM as "Retrofitted," with the implementation note "Not implemented in this database." This indicates the view is shipped as part of the standard schema definition but may not be created or populated in every environment, and its presence should be verified before being relied upon in custom reports or interfaces.

Functionally, the view serves as a denormalized read layer over the picking line detail and picking line structures used during wave planning, pick release, and ship confirmation. By joining organization, item, container, and ship-set information into a single row-per-detail shape, it allows reporting and integration logic to retrieve picking progress and attribute data without reconstructing the joins manually.

Underlying Base Objects

ETRM does not document explicit referenced base objects for this view. The view text, however, clearly references the WSH picking line and picking line detail tables (aliased PL and PLD), with additional joins to organization and item master data. Notable aliases include ORG for the warehouse organization, H_ORG for the organization name (the "h_org" term in the user search corresponds to this alias producing ORG_NAME), MSI1 and MSI2 for item description lookups, PC for container information, SH for the order category used in serial number logic, and SL for ship-set number derivation.

The join between the picking line detail and its parent picking line is driven by PICKING_LINE_ID, and the ROWID of the picking line is exposed as PL_ROW_ID. Because the view is documented as not implemented, DBAs should confirm existence through the data dictionary before referencing it in concurrent programs or SQL-based integrations.

Key Columns

Common Use Cases and Queries

Typical uses include pick-release monitoring, wave progress reporting, and integration extracts for warehouse management systems. A basic query returns picked versus requested quantities by warehouse:

  • SELECT ORG_NAME, WAREHOUSE_CODE, PICKING_LINE_ID, REQUESTED_QUANTITY, SHIPPED_QUANTITY FROM WSHFV_PICK_LINE_DETAIL;
  • SELECT PICKING_LINE_ID, SUM(SHIPPED_QUANTITY) FROM WSHFV_PICK_LINE_DETAIL GROUP BY PICKING_LINE_ID;
  • SELECT DETAIL_TYPE_CODE, SCHEDULE_STATUS_CODE, COUNT(*) FROM WSHFV_PICK_LINE_DETAIL GROUP BY DETAIL_TYPE_CODE, SCHEDULE_STATUS_CODE;

Because the view is documented as not implemented, queries should be preceded by a check of ALL_VIEWS to confirm its availability in the target environment.