Results for “pmibv_resource_lov_v”

14 results




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

Overview

PMIBV_RESOURCE_LOV_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite. It resides within the PMI (Process Manufacturing Intelligence) product family, which Oracle has classified as obsolete in release 12.1.1 and 12.2.2. Consistent with the "LOV" naming convention, the view was designed to supply a list-of-values (LOV) record set — a compact, query-friendly projection of resource data intended to populate selection lists, flexfields, and lookup windows within Process Manufacturing Intelligence and adjacent process manufacturing modules.

The view exposes only three columns: a resource identifier, a resource description, and a resource class. This narrow shape reflects its reporting and integration role: rather than presenting the full attribute set of a resource master record, it delivers the minimum fields required for value selection and lightweight analytic joins. Because PMI is obsolete, the view is retained primarily for backward compatibility. It remains VALID in the data dictionary, but new development should treat it as legacy and prefer current Process Manufacturing resource objects.

Underlying Base Objects

The documented view text is:

The view is therefore defined over a single base object, CR_RSRC_MST, which is referenced in the ETRM metadata as a synonym resolved within the APPS schema. CR_RSRC_MST is the Process Manufacturing resource master table, storing the definition of resources used in process execution, costing, and capacity planning. The view inherits the read-only characteristic directly from the base synonym and adds no filtering, aggregation, or join logic — it is a straight column projection. This design means query performance is governed almost entirely by the indexing and volume of CR_RSRC_MST; no compensating view-level predicates exist.

Key Columns

  • RESOURCES — The resource identifier. This is the primary value returned to LOV consumers and the column used to join the view to other resource-referencing tables.
  • RESOURCE_DESC — The descriptive name of the resource. In an LOV context this is typically the displayed value, offering a human-readable label alongside the coded identifier.
  • RESOURCE_CLASS — The classification assigned to the resource in the resource master. Resource class drives grouping, eligibility, and behavior for resources in process manufacturing; it is frequently used as a filter criterion when restricting an LOV to a specific category of resource.

Common Use Cases and Queries

The principal use case is populating resource selection lists and validating resource input in PMI-era forms and reports. Typical implementations include constraining the LOV by resource class, retrieving the description for display purposes, and joining resource identifiers to transaction or plan data for reporting.

Simple retrieval of all resource LOV entries:

  • SELECT resources, resource_desc, resource_class FROM apps.pmibv_resource_lov_v ORDER BY resources;

Filtering by classification, the most common pattern when the user searches for "resource_class":

  • SELECT resources, resource_desc FROM apps.pmibv_resource_lov_v WHERE resource_class = :p_class ORDER BY resource_desc;

Joining to transactional or plan data to resolve descriptions:

  • SELECT t.resource_id, v.resource_desc, v.resource_class FROM app_resource_table t, apps.pmibv_resource_lov_v v WHERE t.resource_id = v.resources;

Because the view is read-only and obsolete, queries should be limited to legacy reporting and compatibility scenarios. Where equivalent current Process Manufacturing Intelligence or Discrete/Process Manufacturing resource views exist, those should be adopted for new integrations, and any dependency on PMIBV_RESOURCE_LOV_V should be documented as a migration risk.