Search Results qty_type




Overview
Explore in AI Chat

Overview

APPS.WMS_LOADED_QUANTITIES_V is a supplementary database view owned by the APPS schema within Oracle E-Business Suite, and it is registered under the FND Design Data identifier WMS.WMS_LOADED_QUANTITIES_V. Within the Warehouse Management System (WMS) module, this view is used to simplify the coding of Oracle Forms screens by consolidating quantity and load information from multiple temporary transaction tables into a single queryable structure. The view is classified as VALID in the documented ETRM metadata for EBS 12.1.1 and 12.2.2.

Oracle explicitly warns that this is a supplementary view intended for forms coding and does not recommend querying or altering data through it directly, since its definition may change dramatically in subsequent minor or major releases. Consequently, it should be treated as an internal, implementation-dependent object rather than a stable public interface. For the user search term "qty_type," the relevant column is QTY_TYPE, a CHAR column described as the "Status of Quantity" and present in the view's query text.

Underlying Base Objects

The view is defined over three documented base objects, all referenced as synonyms owned by APPS:

  • MTL_MATERIAL_TRANSACTIONS_TEMP — the temporary transaction staging table that holds unposted material transaction lines prior to validation and processing.
  • MTL_TRANSACTION_LOTS_TEMP — the temporary lot-level table associated with material transactions, supplying lot and revision detail.
  • WMS_DISPATCHED_TASKS — the warehouse task table that stores dispatched warehouse execution tasks and their load/LPN context.

The view consolidates transaction-line attributes, lot attributes, and WMS task attributes into one row per load quantity record. Its dependency footprint confirms that it participates in transaction staging and warehouse task flows rather than in finalized inventory balances, and it is referenced by other APPS objects including INV_CYC_LOVS, INV_MINMAX_PVT, and MTL_INV_UTIL_GRP.

Key Columns

  • ORGANIZATION_ID (NUMBER) — the inventory organization identifier.
  • INVENTORY_ITEM_ID (NUMBER) — the inventory item identifier.
  • REVISION (VARCHAR2) — the item revision code.
  • LOT_NUMBER (VARCHAR2, 80) — the lot number for lot-controlled items.
  • COST_GROUP_ID (NUMBER) — the cost group identifier used in costing contexts.
  • CONTAINERIZED_FLAG (NUMBER) — indicates whether the quantity is referenced in containerized (LPN-based) terms.
  • SUBINVENTORY_CODE (VARCHAR2, 10) — the subinventory code.
  • LOCATOR_ID (NUMBER) — the stock locator (bin) identifier.
  • QUANTITY (NUMBER) — the loaded quantity value.
  • QTY_TYPE (CHAR) — the status indicator for the quantity, distinguishing the role or state of the corresponding quantity record.
  • TRANSACTION_TEMP_ID (NUMBER) — the transaction line identifier linking back to the temporary transaction.
  • CONTENT_LPN_ID, LPN_ID, TRANSFER_LPN_ID (NUMBER) — license plate numbers for the content, the parent LPN, and the transfer LPN.
  • SERIAL_TRANSACTION_TEMP_ID (NUMBER) — the transaction line identifier used to join the serial number table for serial-controlled items.
  • SECONDARY_QUANTITY (NUMBER) — the transaction quantity expressed in the secondary (dual) unit of measure.

Common Use Cases and Queries

The primary practical application is inspecting the quantity and status recorded during warehouse loading or dispatch, especially where QTY_TYPE distinguishes between quantity roles. A typical query filters by organization and item:

  • SELECT organization_id, inventory_item_id, lot_number, lpn_id, quantity, qty_type FROM apps.wms_loaded_quantities_v WHERE organization_id = :org_id;
  • SELECT transaction_temp_id, content_lpn_id, lpn_id, transfer_lpn_id, qty_type, quantity, secondary_quantity FROM apps.wms_loaded_quantities_v;
  • SELECT qty_type, SUM(quantity) FROM apps.wms_loaded_quantities_v GROUP BY qty_type;

These queries are useful for diagnostics and for understanding how Oracle Forms retrieves staged load data. Because Oracle discourages direct querying of this view, production reporting should rely on supported interfaces or the underlying base tables wherever possible.