Search Results gmd_monitoring_spec_vrs_pk

Overview

GMD_MONITORING_SPEC_VRS is the OPM Quality monitoring specification validity rule table in Oracle E-Business Suite, owned by the GMD schema and delivered with the Process Manufacturing Product Development module. The object stores the rules that determine when and where a quality monitoring specification is considered valid. Each row associates a monitoring specification with a validity rule that constrains applicability by organization, warehouse, location, or resource, and optionally attaches a sampling plan. In Oracle EBS 12.1.1 and 12.2.2 the table supports the Quality workbench, specification assignment, and results entry logic that governs which monitoring specification applies to a given manufacturing instance.

The metadata records the primary key as GMD_MONITORING_SPEC_VRS_PK on the column SPEC_VR_ID. A heuristic Data Vault classification mined from the foreign-key structure labels this table as standalone, meaning it is best modeled as an independent hub-style entity rather than as a satellite chained to a parent hub or a link resolving two business entities. Because the object carries a single-column surrogate primary key and no documented inbound dependent relationships in the supplied metadata, the standalone hub suggestion is reasonable; the surrounding specification, organization, and resource attributes behave as descriptive context on that hub.

Key Information Stored

Among the 57 documented columns, the following are the most consequential:

• SPEC_VR_ID — the surrogate primary key, unique via GMD_MONITORING_SPEC_VRS_PK. It is the identifier used by all downstream consumers of the validity rule.
• SPEC_ID — the monitoring specification to which the validity rule belongs. This is the principal business-key candidate alongside the scope attributes.
• RULE_TYPE — classifies the validity rule, driving how the remaining scope columns are interpreted.
• LOCT_ORGN_CODE, WHSE_CODE, LOCATION, SUBINVENTORY, LOCATOR_ID, LOCATOR_ORGANIZATION_ID — the organizational, warehouse, subinventory, and locator scope that bound where the rule applies.
• RESOURCES, RESOURCE_ORGN_CODE, RESOURCE_INSTANCE_ID, RESOURCE_ORGANIZATION_ID — resource-level scope for equipment or production resources.
• SAMPLING_PLAN_ID — the only documented foreign key, referencing QA_SAMPLING_PLANS; defines the sampling plan enforced under the rule.
• SPEC_VR_STATUS, START_DATE, END_DATE — rule state and effective dating; the primary filter for "currently valid" evaluations.
• DELETE_MARK — soft-delete flag, standard in OPM tables.
• TEXT_CODE — reference to a code/text lookup used for further classification.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the standard EBS descriptive flexfield columns.
• CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the mandatory audit columns.
• ERECORD_SPEC_VR_ID, MIGRATED_IND — migration and electronic-record linkage columns, relevant to regulated environments.

Only SPEC_VR_ID is documented as a unique index, so any alternate business key must be inferred from SPEC_ID combined with scope and status columns.

Common Use Cases and Queries

The dominant use case is resolving which monitoring specification applies to a combination of specification, organization, warehouse, and date. A representative query filters on status and effective dates:

• SELECT spec_vr_id, spec_id, rule_type, sampling_plan_id FROM gmd_monitoring_spec_vrs WHERE spec_id = :spec_id AND spec_vr_status = 1 AND delete_mark = 0 AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE + 1);
• Joining to the sampling plan to retrieve the enforced plan: SELECT v.spec_vr_id, s.sampling_plan_id FROM gmd_monitoring_spec_vrs v, qa_sampling_plans s WHERE v.sampling_plan_id = s.sampling_plan_id;
• Scope reporting by warehouse or locator for a given specification, grouping on WHSE_CODE, SUBINVENTORY, or LOCATOR_ID.
• Audit and migration reporting using ERECORD_SPEC_VR_ID and MIGRATED_IND to identify rules that were electronically recorded or carried forward during data migration.
• Flexfield-based reporting against ATTRIBUTE_CATEGORY and the ATTRIBUTE1–30 columns where customers have configured additional rule attributes.

Related Objects

The most significant related objects are:

• QA_SAMPLING_PLANS — referenced through SAMPLING_PLAN_ID, the single documented foreign key.
• GMD_MONITORING_SPECS — the specification master implied by SPEC_ID, the parent of each validity rule.
• GMD_SPEC_VRS and related specification validity objects — provide the quality specification framework this table specializes for monitoring.
• GMD_SPEC_VR_HEADERS / GMD_SPEC_VR_LINES pattern objects — analogous validity structures for other specification types.
• GMD_RECIPE_VALIDITY_RULES — a companion validity rule table for recipes, useful for comparison.
• HR_ORGANIZATION_UNITS and MTL_PARAMETERS — supply organizational context for LOCATOR_ORGANIZATION_ID, RESOURCE_ORGANIZATION_ID, and warehouse values.
• MTL_SYSTEM_ITEMS_B — where specifications are item-associated, provides the item context for SPEC_ID resolution.

Together these objects place GMD_MONITORING_SPEC_VRS at the center of OPM Quality specification resolution, linking monitoring specifications to sampling plans and scoped organizational applicability.