Search Results grade_pk_key

Overview

The view EDW_PMI_PGRD_PGRD_LTC_IV belongs to the PMI — Process Manufacturing Intelligence product family within Oracle E-Business Suite. PMI is Oracle's operational and analytical layer for process manufacturing, providing pre-built dimensional and fact objects that support the Process Manufacturing Intelligence dashboards, Oracle Business Intelligence (OBIEE) repositories, and downstream data warehouse extracts. The _IV suffix identifies this object as an "interface view" — a purpose-built projection over a base extract table that presents a curated, consistent column set to consuming ETL processes and reporting tools.

This view surfaces grade (quality specification) data for process manufacturing items. In process industries, a "grade" defines the quality or specification band that a produced batch or lot must meet, and is central to quality control, potency management, and inventory valuation. The view is therefore a reference and dimension-style source: it is not a transactional posting object and carries no business logic beyond column projection and renaming. It is intended for read-only consumption by the PMI extraction and reporting layers rather than by online transaction forms.

The ETRM metadata records that the view is "not implemented in this database" — a standard indication that the object is shipped as part of the PMI data model schema definition but is only physically deployed where the Process Manufacturing Intelligence components have been installed and configured. In 12.1.1 and 12.2.2, this view would typically reside in the PMI/EDW reporting schema rather than in the transactional APPS schema.

Underlying Base Objects

The view is defined over a single base object: EDW_PMI_PGRD_PGRD_LTC. No other base tables, joins, synonyms, or materialized objects are documented in the ETRM metadata; the definition is a straight SELECT ALL_FK, ... FROM EDW_PMI_PGRD_PGRD_LTC with one aliasing operation, mapping the source column GRADE_PK_ROWID to the exposed name ROW_ID and mapping a second reference to USER_ATTRIBUTE5 under the alias OPERATION_CODE.

The naming pattern reveals the lineage convention: PGRD denotes the Process Grade entity, and the repeated token PGRD_PGRD reflects the conformed dimension pattern used throughout PMI, where a grade dimension is joined to itself or to a grade-related fact grain during extraction. The base object name is inherited from the Enterprise Data Warehouse (EDW) staging convention, meaning the view is a thin presentation layer over a pre-extracted staging table rather than over live GMD_* or QM_* production tables. Consequently, data currency depends on the schedule of the PMI extraction concurrent program that populates EDW_PMI_PGRD_PGRD_LTC.

Key Columns

• ALL_FK and ALL_FK_KEY — foreign-key surrogate and key value used to resolve the grade record into the PMI conformed dimension model.
• GRADE_PK, GRADE_PK_KEY, and ROW_ID (sourced from GRADE_PK_ROWID) — the primary key of the grade record, with ROW_ID provided for row-level identification and change detection during incremental ETL.
• GRADE and GRADE_DP — the grade code and its descriptive/display value, used as the human-readable quality specification identifier.
• DESCRIPTION and NAME — descriptive attributes supporting dimension labelling in reports and dashboards.
• INSTANCE_CODE — identifies the source instance or operating unit context, enabling multi-org and multi-instance consolidation.
• USER_ATTRIBUTE1 through USER_ATTRIBUTE5 — the standard Oracle descriptive flexfield (DFF) segment columns, carrying customer-configured grade attributes.
• OPERATION_CODE — an alias of USER_ATTRIBUTE5, re-exposed under a semantically meaningful name for the consuming extract or interface process.

The duplication of USER_ATTRIBUTE5 under two names is significant: the base table stores the value once, but the interface view presents it both as a generic DFF segment and as a specifically named operational attribute, allowing downstream mappings to bind to either without altering the source.

Common Use Cases and Queries

Typical uses include populating grade dimensions in the PMI warehouse, validating grade-to-item assignments, and joining grade data to batch, lot, or quality results for specification compliance reporting. A simple listing query follows:

SELECT GRADE, DESCRIPTION, NAME, INSTANCE_CODE FROM EDW_PMI_PGRD_PGRD_LTC_IV ORDER BY GRADE;

To extract flexfield-driven attributes alongside the operational code:

SELECT GRADE_PK, GRADE, USER_ATTRIBUTE1, USER_ATTRIBUTE2, OPERATION_CODE FROM EDW_PMI_PGRD_PGRD_LTC_IV WHERE INSTANCE_CODE = :p_instance;

For incremental extraction keyed on the surrogate identifiers:

SELECT ALL_FK, ALL_FK_KEY, GRADE_PK_KEY, ROW_ID FROM EDW_PMI_PGRD_PGRD_LTC_IV WHERE ALL_FK_KEY > :last_high_water_mark;

Because the view resolves to a staging table, queries should not be treated as real-time; scheduling against the PMI extraction cycle is required for accurate results.