Results for “alloc_class”

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

Overview

PMI_ALOC_CLS_V is an Oracle E-Business Suite database view owned by the APPS schema and registered against the PMI (Process Manufacturing Intelligence) product family. It is documented in ETRM as an "Allocation Class List Of Values View," indicating that its primary architectural purpose is to support list-of-values (LOV) selection within Oracle Forms-based and OAF-based process manufacturing screens. Rather than storing data, the view projects a minimal two-column projection of allocation class information, making it suitable for lookup fields where users select an allocation class by its short code while viewing an accompanying descriptive name.

Within the Oracle EBS 12.1.1 and 12.2.2 releases, PMI is flagged as obsolete. This status reflects the strategic migration of process manufacturing analytics and reporting functionality into Oracle Fusion and later OBIEE-based reporting layers. Nevertheless, the view remains VALID in the data dictionary, meaning it continues to resolve at runtime and is still referenced by any customizations, reports, or legacy forms that depend on it. Because of its obsolete classification, it is not recommended as a foundation for new development; existing references should be inventoried during upgrade assessments.

Underlying Base Objects

The view is defined over a single base object: IC_ALLC_CLS. In the APPS schema this base table is exposed through a synonym, and the view's defining query simply selects two columns from it:

• ALLOC_CLASS — the allocation class code carried from IC_ALLC_CLS.
• ALLOC_DESC — the corresponding descriptive text for the allocation class.

No joins, filters, or aggregations are applied. The view is therefore a thin pass-through layer whose value lies in its naming convention and its designation as an LOV source rather than in any transformation logic. Because it depends entirely on IC_ALLC_CLS, any change to allocation class definition data is reflected immediately without refresh or materialization. There is no separate security predicate embedded in the view text, so row-level visibility is governed by whatever grants and responsibility-level access are configured on the underlying tables.

Key Columns

The view exposes exactly two columns, both derived directly from the base table:

• ALLOC_CLASS — The allocation class identifier. This is the primary selection value used in LOV windows and the value typically stored in foreign key columns on dependent process manufacturing transactions.
• ALLOC_DESC — The descriptive name associated with the allocation class, presented alongside the code to aid user recognition during selection.

Because the view provides no additional attributes such as effective dates, enabled flags, or organization identifiers, consumers requiring those fields must query the base table directly. Developers should treat the two columns as a stable, read-only interface for lookup purposes only.

Common Use Cases and Queries

The most common use of PMI_ALOC_CLS_V is populating an LOV or parameter list where an allocation class must be selected. A typical query returns the code and description for display:

• SELECT ALLOC_CLASS, ALLOC_DESC FROM APPS.PMI_ALOC_CLS_V ORDER BY ALLOC_CLASS;
• SELECT ALLOC_CLASS, ALLOC_DESC FROM APPS.PMI_ALOC_CLS_V WHERE UPPER(ALLOC_DESC) LIKE UPPER(:p_search || '%');

A frequent secondary scenario is validating that a user-entered or imported allocation class exists before inserting it into a downstream interface table. In that case the view functions as a lightweight reference check:

• SELECT COUNT(*) FROM APPS.PMI_ALOC_CLS_V WHERE ALLOC_CLASS = :p_alloc_class;

For integration or conversion scripts, the view can be joined to staging tables to translate codes into descriptions during load reporting. Given the obsolete status of PMI, any new integration should ideally reference IC_ALLC_CLS directly, while the view remains appropriate for maintaining compatibility with existing reports and forms that were built against the documented LOV interface.