Search Results transactable_flag




Overview
Explore in AI Chat

Overview

The view WSH_DELIVERY_LINES_SC_V is a shipping execution schema object associated with the Oracle Order Entry (OE) module. It exposes picking line detail records from the Warehouse Management (WSH) subsystem in a denormalized form, joining picking line detail rows to inventory organization and container information so that consumers can report on delivery line contents without navigating the full normalized shipping data model. The "SC" suffix in Oracle EBS naming convention generally denotes a "Shipping/Container" or supply-chain-oriented variant, and the view is intended primarily for read-only reporting and integration rather than transactional processing.

The ETRM metadata for 12.2.2 records this object as "Not implemented in this database" in the source system from which the metadata was harvested. This is a significant caveat: the view text exists in the ETRM catalog, but the object was not deployed in the reference environment. The presence of the definition nonetheless confirms the object's intended structure and is useful for understanding how delivery line reporting is modeled across Oracle EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view text is dominated by references to PLD, which is the alias for WSH_PICKING_LINE_DETAILS, the primary transactional table storing individual picking line detail rows, including requested and shipped quantities, lot and serial attributes, subinventory and locator references, and scheduling information. Nearly every column in the view maps directly to a column on this table.

Two additional joins are visible in the excerpt. ORG resolves to ORG_ORGANIZATION_DEFINITIONS, supplying ORGANIZATION_CODE from the inventory organization. H_ORG provides the descriptive ORGANIZATION name. A further join to MSI2 on MTL_SYSTEM_ITEMS_B supplies CONTAINER_DESCRIPTION by CONTAINER_INVENTORY_ITEM_ID. The ETRM metadata lists no documented referenced base objects for this view, so the join relationships above are inferred from the SQL text. Note that PC, aliasing the container table that supplies CONTAINER_INVENTORY_ITEM_ID, is referenced in the select list but its underlying table is not named in the excerpt.

Key Columns

Common Use Cases and Queries

Typical use is delivery-line-level reporting: reconciling requested versus shipped quantities, identifying unscheduled or unautoscheduled lines, and auditing container assignments. A representative query follows.

  • Pending shipment by schedule date: SELECT ORGANIZATION_CODE, DELIVERY_ID, PICKING_LINE_DETAIL_ID, REQUESTED_QUANTITY, SHIPPED_QUANTITY, SCHEDULE_DATE FROM WSH_DELIVERY_LINES_SC_V WHERE SHIPPED_QUANTITY < REQUESTED_QUANTITY ORDER BY SCHEDULE_DATE;
  • Scheduling control audit: SELECT ORGANIZATION_CODE, DELIVERY_ID, SCHEDULE_DATE, AUTOSCHEDULED_FLAG FROM WSH_DELIVERY_LINES_SC_V WHERE AUTOSCHEDULED_FLAG = 'N';
  • Container consumption: SELECT DELIVERY_ID, CONTAINER_DESCRIPTION, SUM(SHIPPED_QUANTITY) FROM WSH_DELIVERY_LINES_SC_V GROUP BY DELIVERY_ID, CONTAINER_DESCRIPTION;

Consumers should confirm object existence and privileges in the target instance, since the ETRM metadata records the view as not implemented in the reference database, implying environment-dependent deployment.