Results for “icinv_class”

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

Overview

PMI_INV_CLS_LOV_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It belongs to the Process Manufacturing Intelligence (PMI) product family, which supplies the analytical and reporting infrastructure used by Oracle Process Manufacturing (OPM) applications. As its ETRM description states, the view exposes an "Inventory Class List Of Values," meaning it is designed to feed Oracle Forms LOV (List of Values) components, concurrent program parameters, and any custom reporting layer that needs to present users with a validated pick list of inventory classes.

The view is documented as VALID under both EBS 12.1.1 and 12.2.2. Because it contains no procedural logic and performs no joins, aggregation, or filtering, it functions purely as a projection of the inventory class master data. This makes it a lightweight and reliable access point for reference data. Users who search on the identifier "ic_invn_cls" are typically looking for the underlying table from which this view is derived, since the view name itself is a naming convention artifact of the PMI LOV layer.

Underlying Base Objects

The view text documented in the ETRM metadata is minimal and precise:

• SELECT ICINV_CLASS, ICINV_CLASS_DESC FROM IC_INVN_CLS

The single referenced base object is IC_INVN_CLS, which the ETRM registry records as a SYNONYM. In a standard OPM installation this synonym resolves to the inventory class definition table maintained by the Process Manufacturing inventory module. The view therefore inherits the full population of that table without any restriction applied at the view level. Any row visible in IC_INVN_CLS for the current organization or installation is equally visible through PMI_INV_CLS_LOV_V.

Because the base object is a synonym rather than a physical table in the APPS schema, the actual storage resides in the OPM application schema. This layering is consistent with Oracle's practice of separating product-owned tables from the APPS code layer and exposing curated views for cross-module consumption.

Key Columns

The view projects exactly two columns, both derived from the base inventory class record:

• ICINV_CLASS — The inventory class identifier or code. This is the value that consuming forms and reports would store as the selected class.
• ICINV_CLASS_DESC — The descriptive text associated with the inventory class, used for display in LOV windows and report output.

The absence of additional columns — such as organization identifiers, enable flags, or audit columns — confirms the view's narrow purpose. It is intended only to populate a selection list, not to drive business logic or complex reporting.

Common Use Cases and Queries

The principal use cases are populating LOV windows in OPM inventory and process execution forms, supplying values for concurrent program parameters that accept an inventory class, and joining to transaction or material tables to resolve descriptive labels in custom reports.

Typical query patterns include:

• Retrieving all available inventory classes for an LOV:
  SELECT ICINV_CLASS, ICINV_CLASS_DESC FROM APPS.PMI_INV_CLS_LOV_V ORDER BY ICINV_CLASS;
• Resolving a description for a known class code:
  SELECT ICINV_CLASS_DESC FROM APPS.PMI_INV_CLS_LOV_V WHERE ICINV_CLASS = :p_class;
• Filtering a report dataset by an LOV-selected class:
  SELECT t.* FROM your_transaction_table t WHERE t.inventory_class IN (SELECT ICINV_CLASS FROM APPS.PMI_INV_CLS_LOV_V WHERE ICINV_CLASS_DESC LIKE :p_desc);

Because the view carries no organization-level or security predicates, implementers should apply any required operating unit or organization filtering in the calling query rather than relying on the view itself. When the view returns unexpected results, the diagnostic path is to query IC_INVN_CLS directly through its synonym and compare the row counts, since the view adds nothing that could independently alter the result set.