Search Results gmd_specifications_vl




Overview
Explore in AI Chat

Overview

GMD_SPECIFICATIONS_VL is a seeded, VALID database view owned by the APPS schema in Oracle E-Business Suite, registered under the Process Manufacturing Product Development (GMD) product family. It presents specification (quality and product specification) header data in a language-enabled form, exposing the specification identifier, name, version, description, item association, grade, revision, and status alongside the standard Oracle attribute columns and audit columns. As the "VL" (view, translated) layer, the view joins the base specification table to its translation table and filters the translated rows by the session language, so consumers receive exactly one description row per specification in the user's language.

Because the view already encapsulates this join and language filter, it is the preferred access point for reports, concurrent programs, Discoverer workbooks, and interface/API reads that need specification headers without re-implementing translation logic. The SPEC_STATUS column, which prompted the search on "spec_status", is the status flag of the specification and is central to any question about whether a given specification is active, obsolete, or otherwise unusable.

Underlying Base Objects

The ETRM metadata documents the view as defined over two referenced base objects, both exposed as synonyms at runtime:

The view definition performs an inner join on SPEC_ID between the translation and base tables. Consequently, a specification with no translation row in the session language will not appear, and writers must always route inserts and updates through the base and TL tables (or the supported product APIs) rather than through the view.

Key Columns

  • SPEC_ID — unique specification identifier and the primary join key.
  • SPEC_NAME / SPEC_VERS — specification name and version, forming the typical business key.
  • SPEC_DESC — language-specific description sourced from GMD_SPECIFICATIONS_TL.
  • SPEC_STATUS — the specification's status code; used to determine whether a specification is valid for use, pending, or obsolete.
  • INVENTORY_ITEM_ID / REVISION / GRADE_CODE — the item, revision, and grade the specification is tied to.
  • OWNER_ORGANIZATION_ID / OWNER_ID — organization and internal owner of the specification, supporting multi-org and security filtering.
  • SPEC_TYPE, OVERLAY_IND, BASE_SPEC_ID — specification type and overlay/base-spec relationships.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–30 — descriptive flexfield columns.
  • DELETE_MARK, SAMPLE_INV_TRANS_IND, TEXT_CODE — logical delete flag, sample inventory transaction indicator, and text code.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

Typical reporting joins this view to item, organization, and specification-detail objects. A query listing active specifications by status is the most common pattern:

SELECT spec_id, spec_name, spec_vers, spec_desc, spec_status FROM apps.gmd_specifications_vl WHERE spec_status = :p_status AND NVL(delete_mark,0) = 0 ORDER BY spec_name;

Filtering by specification status also supports the frequent question of which specifications are inactive or obsolete, which this view answers without needing to decode the base table. Restricting to a language other than the session language requires querying the translation table directly. Because the view is read-only and applies the language filter, it should not be used for DML; updates to SPEC_STATUS or other columns must target GMD_SPECIFICATIONS_B through the supported product APIs.