Results for “ps_plng_cls_vw”

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

Overview

PS_PLNG_CLS_VW is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMP (Process Manufacturing Process Planning) product family. The view exposes a consolidated, presentation-ready list of planning classes — the OPM category-set classifications used to group items and resources for process planning, forecasting, and capacity purposes. Because the view's name centers on planning class, it is the object most frequently referenced when a user or developer searches for "planning_class" in the ETRM data dictionary.

Rather than storing data itself, PS_PLNG_CLS_VW projects and reformats columns from the underlying category model, trimming concatenated segment strings and descriptions to fixed widths and supplying a stable, denormalized column layout. This makes it suitable for Oracle Reports, OAF/Forms LOVs, concurrent-program extracts, and inbound/outbound interface programs that need a planning-class lookup without navigating the multi-table category-set structure directly. The view is documented with status VALID in both 12.1.1 and 12.2.2 ETRM registries and carries the standard Oracle Proprietary, Confidential Information designation.

Underlying Base Objects

The view is defined over four documented base objects. MTL_CATEGORY_SETS and GMI_CATEGORY_SETS are accessed through synonyms, while MTL_CATEGORIES_V is a view and MTL_CATEGORY_SET_VALID_CATS is a synonym used in the validation sub-query.

• GMI_CATEGORY_SETS (OCS) — the OPM category-set definition table. Its OPM_CLASS column is restricted to 'PLANNING_CLASS', which is the key filter that distinguishes this view from other category-set views.
• MTL_CATEGORY_SETS (CS) — joined on CATEGORY_SET_ID and used to obtain STRUCTURE_ID and VALIDATE_FLAG.
• MTL_CATEGORIES_V (C) — joins on STRUCTURE_ID and supplies concatenated segments, description, disable date, and the DFF attribute columns.
• MTL_CATEGORY_SET_VALID_CATS — used in the EXISTS clause to restrict results to valid categories when the category set is validated.

Key Columns

The view's column names inherit ETRM naming conventions. The most significant are:

• PLANNING_CLASS — the first eight characters of CATEGORY_CONCAT_SEGS, upper-cased, acting as the short planning-class identifier.
• PLANNING_CATEGORY_ID — the numeric CATEGORY_ID from MTL_CATEGORIES_V; the join key to item/category assignments.
• PLANNING_CLASS_DESC — the category description truncated to 70 characters.
• DELETE_MARK, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO and soft-delete audit columns; DELETE_MARK is DECODE'd to 1 when DISABLE_DATE is set.
• ATTRIBUTE1 through ATTRIBUTE15, ATTRIBUTE_CATEGORY — the descriptive-flexfield attribute columns passed through from MTL_CATEGORIES_V, with ATTRIBUTE_CATEGORY placed last in the projection.
• TEXT_CODE, TRANS_CNT, REPORTING_UOM, ATTRIBUTE16 through ATTRIBUTE30 — placeholder columns assigned NULL so the view presents the full 30-attribute EBS signature expected by forms and reports.

Common Use Cases and Queries

The view is typically used for LOV population, validation of user-entered planning classes, and extraction of the planning hierarchy for planning engines. A representative query listing active planning classes follows:

• SELECT PLANNING_CLASS, PLANNING_CATEGORY_ID, PLANNING_CLASS_DESC FROM APPS.PS_PLNG_CLS_VW WHERE DELETE_MARK = 0 ORDER BY PLANNING_CLASS;
• Joining to item assignments to report which items belong to each planning class: SELECT i.SEGMENT1, v.PLANNING_CLASS FROM APPS.PS_PLNG_CLS_VW v, APPS.MTL_ITEM_CATEGORIES i WHERE v.PLANNING_CATEGORY_ID = i.CATEGORY_ID AND v.DELETE_MARK = 0;
• LOV definition in Forms/OAF — because the view already trims the class code to eight characters and the description to seventy, labels render cleanly without further SUBSTR processing.

Because the view hides the underlying category-set joins and the OPM_CLASS = 'PLANNING_CLASS' filter, it is the preferred access path for any 12.1.1 or 12.2.2 custom component that must resolve a planning class without duplicating the base-object logic.