Search Results gmd_stability_studies




Overview
Explore in AI Chat

Overview

APPS.GMD_QM_E_STABILITY_STUDIES_V is a reporting view in the Oracle E-Business Suite Process Manufacturing (OPM) Quality Management module. It consolidates stability study header information from the GMD_STABILITY_STUDIES base table and denormalizes critical descriptive attributes from related quality, inventory, and specification entities. The view presents each stability study as a single row, enriched with the human-readable status meaning, the inventory item's concatenated key flexfield segments, and the base specification name and version.

Its principal role is to support reporting, inquiry, and integration requirements where consumers need stability study details without performing multi-table joins themselves. Because it resolves the numeric STATUS code into a meaningful label through GMD_QC_STATUS, it is frequently used in dashboards, concurrent program extracts, and interfaces that must display quality status text. Users searching for "gmd_qc_status" typically arrive here because this view is one of the primary consumers of that status lookup table within the stability study domain.

Underlying Base Objects

The view is defined over four documented synonym-referenced objects:

  • GMD_STABILITY_STUDIES (alias A) — the driving table supplying the study header, scheduling dates, shelf-life recommendations, counters, and status code.
  • GMD_QC_STATUS (alias B) — the quality status lookup, joined on ENTITY_TYPE = 'STABILITY' and STATUS_CODE = A.STATUS, providing the MEANING column.
  • MTL_SYSTEM_ITEMS_KFV (alias C) — the key flexfield view of inventory items, joined on ORGANIZATION_ID and INVENTORY_ITEM_ID, supplying concatenated segments and item description.
  • GMD_SPECIFICATIONS (alias D) — joined on A.BASE_SPEC_ID = D.SPEC_ID, supplying the base specification name and version.

All joins are equi-joins on the natural keys, producing one row per stability study for which a matching status, item, and specification exist.

Key Columns

Common Use Cases and Queries

Typical uses include stability study status reporting, listing active studies per item, and extracting shelf-life data for specification management. Because DELETE_MARK is exposed but not filtered, consumers should explicitly exclude deleted rows.

List active studies with decoded status and item for an organization:

  • SELECT ss_no, meaning, concatenated_segments, base_spec_name, base_spec_vers, recommended_shelf_life, recommended_shelf_life_unit FROM apps.gmd_qm_e_stability_studies_v WHERE organization_id = :org_id AND delete_mark = 0 ORDER BY ss_no;

Find studies by quality status meaning:

  • SELECT ss_no, meaning, actual_start_date, actual_end_date FROM apps.gmd_qm_e_stability_studies_v WHERE meaning = 'Active' AND delete_mark = 0;

Report upcoming testing grace periods per item and base specification:

  • SELECT concatenated_segments, base_spec_name, testing_grace_period, testing_grace_period_unit, scheduled_end_date FROM apps.gmd_qm_e_stability_studies_v WHERE delete_mark = 0 AND scheduled_end_date >= TRUNC(SYSDATE);

These queries illustrate the view's value as a single-source, status-decoded foundation for stability study reporting and downstream integration.