Search Results gmd_wip_spec_vrs




Overview
Explore in AI Chat

Overview

GMD_WIP_SPEC_VRS is a Process Manufacturing Product Development (GMD) table that stores Oracle Process Manufacturing (OPM) work-in-process specification validity rules. It defines the conditions under which quality specifications apply to in-process batches and operations, controlling attributes such as sampling behavior, lot status assignment, Certificates of Analysis (COA), and batch step completion. The table resides in the GMD schema and is part of the Oracle E-Business Suite 12.1.1 and 12.2.2 data model. It carries a status of VALID and comprises 83 documented physical columns. Since validity rules are typically effective-dated, each row governs a specification's applicability across a defined time window and organizational or recipe context.

From a Data Vault modeling perspective, the mined foreign key structure classifies this object heuristically as a standalone construct. This suggests it could be modeled as a satellite-like record capturing descriptive rule attributes, though the absence of a hub-style parent in the given FK inventory means the classification should be treated as a modeling suggestion rather than a definitive structural claim. The primary key GMD_WIP_SPEC_VRS_PK on SPEC_VR_ID provides the surrogate identifier for each rule instance.

Key Information Stored

The table centers on identifying and scoping WIP specification validity rules. The most significant columns include:

The unique index GMD_WIP_SPEC_VRS_PK on SPEC_VR_ID is the documented business-key candidate. The extensive ATTRIBUTE1 through ATTRIBUTE30 descriptive flexfield columns provide extensibility.

Common Use Cases and Queries

Typical use cases include reporting active specification rules for a given batch or recipe, validating sampling schemes prior to quality data collection, and auditing COA requirements at ship or invoice. A representative query retrieves active rules for an organization:

SELECT vr.spec_vr_id, vr.spec_id, vr.recipe_no, vr.start_date, vr.end_date
FROM gmd_wip_spec_vrs vr
WHERE vr.orgn_code = :orgn
AND vr.spec_vr_status = 'A'
AND SYSDATE BETWEEN vr.start_date AND NVL(vr.end_date, SYSDATE);

Joining to GMD_RECIPES_B on RECIPE_ID supports recipe-driven rule analysis, while joins to QA_SAMPLING_PLANS on SAMPLING_PLAN_ID enable sampling-plan reporting. The table also supports COA and lot-status analysis through its COA_TYPE and lot-status columns.

Related Objects

  • GMD_RECIPES_B — referenced via GMD_WIP_SPEC_VRS.RECIPE_ID, linking rules to recipe definitions.
  • QA_SAMPLING_PLANS — referenced via GMD_WIP_SPEC_VRS.SAMPLING_PLAN_ID, defining sampling behavior.
  • Specification tables (SPEC_ID domain) — supply the specification master referenced by SPEC_ID.
  • Organization and lot status reference tables — resolved through ORGN_CODE, ORGANIZATION_ID, and the lot-status _ID columns.
  • Routing- and formula-related tables — joined through ROUTING_ID, STEP_ID, and FORMULA_ID.