Results for “vendor_lot_no”

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

Overview

PMIBV_LOT_LOV_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the PMI (Process Manufacturing Intelligence) product family, which Oracle has since classified as obsolete. The view functions as a List of Values (LOV) source for lot selection, exposing a minimal projection of lot master data that front-end forms and concurrent programs can query when a user or process needs to pick a lot number.

Because the view is defined with a WITH READ ONLY clause, it is intended strictly for query and display purposes. It cannot be used as the target of DML statements, and any application logic requiring lot maintenance must operate against the underlying master table instead. This read-only constraint reinforces its role as a presentation and lookup layer rather than a transactional interface.

Underlying Base Objects

The view is defined over a single base object: IC_LOTS_MST, which is referenced through a synonym in the APPS schema. IC_LOTS_MST is the Process Manufacturing lot master table that stores the canonical definition of lots across inventory organizations.

The definition is deliberately thin. The full view text is:

• SELECT LOT_NO, SUBLOT_NO, LOT_DESC, VENDOR_LOT_NO FROM IC_LOTS_MST WITH READ ONLY

No joins, filters, or aggregations are applied. Consequently, the view inherits the full row population of IC_LOTS_MST, subject only to whatever organization-level security or synonyms are already enforced on the base table. There is no multi-organization filtering built into the view itself, so consumers must apply their own organization context where required.

Key Columns

The view exposes exactly four columns, each passed through directly from the base table:

• LOT_NO — The primary lot number identifier. This is the principal selection value presented in an LOV and the column most commonly used in join predicates.
• SUBLOT_NO — The sublot identifier, used where a lot is subdivided into subordinate units. It qualifies LOT_NO to form the complete lot key.
• LOT_DESC — The descriptive text associated with the lot. This is typically the display column shown alongside LOT_NO in a user-facing LOV so operators can identify lots by description rather than number alone.
• VENDOR_LOT_NO — The supplier's own lot reference. This column is directly relevant to the search term "vendor_lot_no," as it carries the externally assigned lot number received from the vendor, enabling traceability between supplier documentation and internal lot records.

Common Use Cases and Queries

The view is most often employed to populate lot LOVs in custom forms, OAF pages, and reports, and to resolve a vendor lot number back to the internal lot it corresponds to. A typical lookup by vendor reference is:

• SELECT lot_no, sublot_no, lot_desc FROM apps.pmibv_lot_lov_v WHERE vendor_lot_no = :p_vendor_lot_no;

A broader keyword search for LOV population may use a pattern match against either the internal or vendor reference:

• SELECT lot_no, sublot_no, lot_desc, vendor_lot_no FROM apps.pmibv_lot_lov_v WHERE lot_no LIKE :p_pattern OR vendor_lot_no LIKE :p_pattern;

Because the view is obsolete and unfiltered, integration developers should treat it as a convenience lookup rather than an authoritative reporting source, and should confirm that organization-level restrictions are applied by the calling application.