Search Results lot_desc




Overview
Explore in AI Chat

Overview

APPS.PMIBV_LOT_LOV_V is a read-only database view in Oracle E-Business Suite that exposes lot and sublot information from the inventory lot master. Its name designates it as a List of Values (LOV) view, indicating that it is intended primarily to populate selection lists and value pickers in Oracle Forms-based EBS applications and in custom concurrent or OAF components. The view presents four columns — LOT_NO, SUBLOT_NO, LOT_DESC, and VENDOR_LOT_NO — drawn directly from the IC_LOTS_MST table through a synonym of the same name. Because the view is defined with the WITH READ ONLY clause, no DML operations can be issued against it, reinforcing its role as a query-only presentation layer rather than a transactional interface.

The view is owned by the APPS schema, which is consistent with standard EBS deployment practice in which application views are created under APPS while the underlying base objects reside in the relevant product schema. In releases 12.1.1 and 12.2.2 the object remains structurally identical, so reports, forms personalizations, and custom integrations built against it remain portable across those versions. The user search term “lot_desc” corresponds directly to the LOT_DESC column exposed by this view, confirming that the view is the correct access path when a description of a lot must be retrieved alongside its number.

Underlying Base Objects

The view is defined over a single documented base object: IC_LOTS_MST, referenced through a synonym. IC_LOTS_MST is the inventory lot master table that stores lot and sublot definitions used by Oracle Inventory, Oracle Process Manufacturing, and related supply chain modules. Because the view performs no joins, unions, or aggregations, it is a simple projection of four columns from that master table. This simplicity has two practical consequences: query performance parallels that of a direct table access with a column list, and all filtering, security, and validation logic associated with lot records remains governed by the base table rather than by the view. The synonym reference means the view resolves IC_LOTS_MST through the standard EBS synonym layer, ensuring correct schema redirection in a multi-org or multi-language installation.

Key Columns

  • LOT_NO — The lot number, the primary business identifier for a lot record. Frequently used as the returned value in an LOV and as the join key to transaction and on-hand tables.
  • SUBLOT_NO — The sublot number, used where inventory is tracked at a finer granularity than the lot itself. Nullable for lot-controlled items that do not use sublots.
  • LOT_DESC — The descriptive text associated with the lot. This is the column matched by the search term “lot_desc” and is typically the display field in an LOV, since it carries human-readable context that the numeric or coded lot number may not convey.
  • VENDOR_LOT_NO — The supplier-assigned lot number. This column supports receiving, quality, and traceability processes by linking the internal lot identifier to the vendor’s own reference.

Common Use Cases and Queries

Typical usage includes populating lot selection lists in custom forms, driving lot description lookups in reports, and enriching queries that require a readable lot label. The following example retrieves all lots and their descriptions:

SELECT lot_no, sublot_no, lot_desc, vendor_lot_no
FROM   apps.pmibv_lot_lov_v;

To support a searchable LOV keyed on the description, a query such as the following is common:

SELECT lot_no, lot_desc
FROM   apps.pmibv_lot_lov_v
WHERE  UPPER(lot_desc) LIKE UPPER(:p_search || '%');

Where vendor traceability is required, filtering on VENDOR_LOT_NO provides a direct path from a supplier reference to the internal lot. Because the view is read-only, these queries are safe to embed in report definitions, BI Publisher data models, and read-only integration interfaces without risk of unintended data modification.