Search Results gmd_qc_status_vl




Overview
Explore in AI Chat

Overview

GMD_QC_STATUS_VL is a seeded, VALID database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMD product family — Process Manufacturing Product Development (Oracle Process Manufacturing, OPM). The object is documented in ETRM as the "OPM Quality Status View." Its purpose is to expose the set of quality status codes used throughout Oracle Process Manufacturing quality workflows, resolving the underlying base record into the runtime session language.

As a "_VL" view, it follows the standard Oracle EBS multilingual (MLS) pattern: it joins the "_B" (base) table, which stores language-independent data and attributes, to the "_TL" (translation) table, which stores the language-dependent MEANING and DESCRIPTION. The translation join is filtered on T.LANGUAGE = USERENV('LANG'), so each query returns the quality status description in the current user's session language. The view is read-only in the reporting sense — it is a query surface over the two base objects — and is intended for lookups, reporting, and integration rather than direct DML. Because it is owned by APPS and referenced through synonyms in the GMD schema, it is available to application code, concurrent programs, and custom reports that need a consistent, localized list of quality statuses.

Underlying Base Objects

ETRM documents two referenced base objects, both accessed through synonyms:

The view is defined by joining these two tables on the composite key STATUS_CODE and ENTITY_TYPE, then restricting the translation rows to the current session language. The base table also supplies a ROW_ID (derived from B.ROWID) to give each row a unique identifier usable in tooling and integration frameworks. Because EBS is bilingual in some installations, only the row matching USERENV('LANG') is returned, which is the defining behavior of an MLS view.

Key Columns

  • ROW_ID — unique row identifier exposed from the base table's ROWID.
  • STATUS_CODE — the primary business key for the quality status; joins to the translation row.
  • MEANING — the localized display name of the quality status.
  • DESCRIPTION — the localized longer description.
  • ENTITY_TYPE — classifies the entity to which the status applies; part of the join key to the translation table.
  • STATUS_TYPE — categorizes the status (for example, its functional grouping within the quality workflow).
  • UPDATEABLE — flag indicating whether the status may be changed.
  • VERSION_ENABLED — flag indicating whether versioning applies to records using this status.
  • DELETE_MARK — soft-delete indicator; callers typically filter on this.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — descriptive flexfield segments for extensibility.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

Typical uses include populating quality-status lookup lists in forms and reports, validating a status code supplied by an interface, and driving conditional logic in quality data collection. A basic query retrieves the localized statuses:

  • SELECT status_code, meaning, description, status_type FROM apps.gmd_qc_status_vl ORDER BY meaning;
  • SELECT status_code, meaning FROM apps.gmd_qc_status_vl WHERE delete_mark = 0 AND updateable = 1;
  • SELECT status_code, meaning FROM apps.gmd_qc_status_vl WHERE entity_type = :entity_type;

Because the view already filters to the session language, callers should not add their own LANGUAGE predicate; instead they should control language via the EBS session setting. For integration, the ROW_ID may be used as a stable handle, while STATUS_CODE and ENTITY_TYPE form the business key. Reports should generally filter on DELETE_MARK to exclude logically deleted statuses.