Results for “planning_class_desc”

24 results




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

Overview

PMI_PLNG_CLS_LOV_V is a list-of-values (LOV) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Process Manufacturing Intelligence (PMI) product family, a component of Oracle's Process Manufacturing suite that is documented as obsolete in ETRM metadata. Its stated purpose is to supply the set of valid planning class values and their descriptions for use in LOV-enabled fields, typically on concurrent program parameters, Oracle Forms fields, OAF pages, and BI Publisher or Oracle Reports parameter prompts.

The view behaves as a presentation-layer abstraction rather than a transactional or analytical object. It does not perform computation, aggregation, or joining beyond the projection defined in its view text, and it carries no filter predicates. Consequently, every row present in its driving base object is surfaced directly to any consumer of the view, making it a straightforward reference source for planning class-driven selection.

Underlying Base Objects

The documented view text is:

According to the documented ETRM metadata for release 12.2.2, the referenced base object is PS_PLNG_CLS, resolved through a synonym. PS_PLNG_CLS is the Process Manufacturing planning class definition table, which holds the valid planning class codes used to categorize process manufacturing items, formulas, and associated planning attributes. The view does not alter, restrict, or transform the source data; it projects exactly two columns from PS_PLNG_CLS, so row cardinality and ordering behavior in practice mirror those of the base table (no ORDER BY is imposed by the view itself).

Because PMI is flagged as obsolete in the ETRM documentation, the object may be absent, deprecated, or retained only for backward compatibility in later releases. In environments where the PMI product is not licensed or installed, the underlying synonym or table may not exist, and references to the view would fail at parse time.

Key Columns

  • PLANNING_CLASS — The planning class code. This is the value returned to the calling field or report parameter when a user makes an LOV selection. It is the functional key used throughout process manufacturing planning logic to group items with similar planning behavior.
  • PLANNING_CLASS_DESC — The descriptive text associated with the planning class. This is the value typically displayed to the end user in the LOV window, while PLANNING_CLASS is stored or passed downstream.

The absence of additional columns such as effective dates, organization identifiers, or enabled flags indicates that the view exposes the complete, unfiltered planning class domain as maintained in PS_PLNG_CLS.

Common Use Cases and Queries

The most frequent use of this view is as the validation and presentation source behind a planning class LOV. Typical consumers include process manufacturing concurrent program parameters, custom Forms or OAF personalizations, and ad hoc reporting where a user-readable planning class description is required alongside the code.

A basic lookup that emulates the LOV behavior:

  • SELECT PLANNING_CLASS, PLANNING_CLASS_DESC FROM APPS.PMI_PLNG_CLS_LOV_V ORDER BY 1;

Joining the view to planning data to enrich a report with descriptions:

  • SELECT p.PLANNING_CLASS, l.PLANNING_CLASS_DESC FROM some_planning_table p, APPS.PMI_PLNG_CLS_LOV_V l WHERE p.PLANNING_CLASS = l.PLANNING_CLASS;

Filtering a specific planning class for validation or a single-value prompt:

  • SELECT PLANNING_CLASS, PLANNING_CLASS_DESC FROM APPS.PMI_PLNG_CLS_LOV_V WHERE PLANNING_CLASS = :p_class;

Because the view is a thin projection, query performance is governed almost entirely by access to PS_PLNG_CLS. For reporting and integration, it should be treated as reference data: read-only, low-volume, and safe to query frequently, subject to confirming that the obsolete PMI components remain present in the target instance.