Search Results oprn_vers




Overview
Explore in AI Chat

Overview

FM_OPRN_MST_VW1 is a public view owned by the APPS schema in Oracle E-Business Suite, registered under the FND design data namespace GMD.FM_OPRN_MST_VW1. It is documented as a public view that may be useful for custom reporting or other data requirements, and its stated purpose is to present operation master information. In the Process Manufacturing (OPM) module, an "operation" represents a discrete unit of processing activity performed within a routing or recipe, such as mixing, heating, or packaging. This view consolidates the header-level attributes of those operations into a single, denormalized read interface.

The view is marked VALID in both the 12.1.1 and 12.2.2 releases and follows the standard EBS convention of exposing a business entity through a stable, query-only interface. Because it is a view rather than a base table, it abstracts the physical storage of operation data and shields custom reports and integrations from changes to the underlying table structure. It is not intended for direct DML; consumers should treat it strictly as a reporting and integration surface.

Underlying Base Objects

The documented metadata identifies a single referenced base object: the synonym GMD_OPERATIONS. At runtime this synonym resolves to the Process Manufacturing operations master table within the GMD (Process Manufacturing) product family. FM_OPRN_MST_VW1 is therefore a projection, or virtual copy, of that table, exposing its principal columns under the APPS schema for governed reporting access. Because the view depends on GMD_OPERATIONS, its returned data reflects the current state of the operation master records maintained by the OPM application, including their versioning, activation status, and descriptive flexfield content. The dependency is one-directional: changes committed to the base table are immediately visible through this view, and no materialization or refresh is involved.

Key Columns

  • OPRN_ID (NUMBER, 10) — Unique identifier of the operation; the primary key and join column to routings, recipes, and operation dependencies.
  • OPRN_NO (VARCHAR2, 57) — Operation number or code used by planners and production staff.
  • OPRN_DESC (VARCHAR2, 240) — Descriptive text explaining what the operation does.
  • OPRN_VERS (NUMBER) — Version of the operation, supporting revision-aware reporting.
  • PROCESS_QTY_UM (VARCHAR2) — Unit of measure for the quantity processed by the operation.
  • OPRN_CLASS (VARCHAR2) — Class of the operation, used for categorization and filtering.
  • INACTIVE_IND (NUMBER) — Indicator that the operation is inactive and should be excluded from active production reporting.
  • DELETE_MARK (NUMBER) — Marks records logically deleted; queries should normally filter this to zero.
  • TEXT_CODE (NUMBER, 10) — Code linking to the edit-text facility used for long descriptions.
  • LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns for change tracking and lineage.
  • ATTRIBUTE1 through ATTRIBUTE13 (VARCHAR2, 240) — Standard descriptive flexfield segments, allowing site-specific extensions to be surfaced in reports.
  • POC_CTL_CLASS and IN_USE — Documented as not used.

Common Use Cases and Queries

Typical usage includes operation master listings for production planning, validation extracts feeding manufacturing execution systems, and reconciliation of operation codes against routing steps. Because the view is denormalized at the operation-header level, it is frequently joined to routing and recipe views on OPRN_ID. A representative query is:

SELECT oprn_id,
       oprn_no,
       oprn_desc,
       oprn_vers,
       oprn_class,
       process_qty_um
FROM   apps.fm_oprn_mst_vw1
WHERE  inactive_ind = 0
AND    delete_mark  = 0
ORDER  BY oprn_no, oprn_vers;

Analysts requiring flexfield detail may add ATTRIBUTE columns to the projection. All access should be read-only and granted through the APPS schema, consistent with the view's documented role as a reporting interface.