Search Results gmd_customer_spec_vrs_pk




Overview

GMD_CUSTOMER_SPEC_VRS is an Oracle Process Manufacturing (OPM) Product Development table that stores customer specification validity rules. It belongs to the GMD schema and is classified under the Process Manufacturing Product Development module. The table governs the conditions under which customer specifications apply to specific orders, order lines, ship-to sites, and organizations — defining the start and end dates of validity, the status of the validity rule, and associated quality assurance behaviors such as sampling plans and Certificates of Analysis (COA).

In Oracle EBS 12.1.1 and 12.2.2, this table functions as the validity-rule layer connecting customer-defined specifications to transactional and organizational contexts. Each row establishes an effective-dated, status-controlled rule that determines when a customer specification is enforceable. The metadata classifies this object heuristically as standalone within a Data Vault modeling context, suggesting it behaves as an independent satellite with no strong hub/link dependency in the mined foreign-key structure, though it does reference QA_SAMPLING_PLANS via SAMPLING_PLAN_ID.

Key Information Stored

The table contains 60 documented columns. The most operationally significant are summarized below.

The unique index GMD_CUSTOMER_SPEC_VRS_PK on SPEC_VR_ID is the business-key candidate. The remaining ATTRIBUTE1 through ATTRIBUTE30 columns provide extensibility via the descriptive flexfield mechanism (ATTRIBUTE_CATEGORY).

Common Use Cases and Queries

Typical reporting scenarios include identifying active specification validity rules by customer, order, or organization, and auditing COA requirements. A common query retrieves currently effective rules:

  • SELECT vr.SPEC_VR_ID, vr.SPEC_ID, vr.CUST_ID, vr.ORGN_CODE, vr.SPEC_VR_STATUS, vr.START_DATE, vr.END_DATE FROM GMD.GMD_CUSTOMER_SPEC_VRS vr WHERE vr.DELETE_MARK = 0 AND SYSDATE BETWEEN vr.START_DATE AND vr.END_DATE AND vr.SPEC_VR_STATUS = 'A';
  • Joining to QA_SAMPLING_PLANS on SAMPLING_PLAN_ID to report which validity rules carry sampling obligations.
  • Filtering by ORDER_ID and SHIP_TO_SITE_ID to determine which specification rule applies to a specific shipment.
  • Reporting on COA_AT_SHIP_IND or COA_AT_INVOICE_IND to support quality and billing compliance audits.

Related Objects

These relationships make GMD_CUSTOMER_SPEC_VRS a central control point for customer-specific quality and specification enforcement in OPM Product Development.