Search Results gmd_actions_b




Overview
Explore in AI Chat

Overview

GMD_ACTIONS_B is a base table in the GMD schema (Process Manufacturing Product Development) that stores OPM Quality Actions. Within Oracle E-Business Suite 12.1.1 and 12.2.2, this table functions as the master repository for quality action definitions used by the Oracle Process Manufacturing (OPM) quality module, including Quality Control and Quality Assurance workflows. Each row represents a distinct action that can be invoked during quality data collection, specification evaluation, or disposition processing.

The ETRM metadata records this object as VALID with 41 documented columns. A heuristic Data Vault classification mined from the foreign-key structure identifies this object as standalone, meaning it exhibits no inbound or outbound foreign-key dependencies in the mined model. From a dimensional or Data Vault modeling perspective, this suggests GMD_ACTIONS_B is best treated as a reference or hub-style entity rather than a link or satellite: it holds descriptive attribute data keyed by a single business identifier and does not participate in relational joins at the database-constraint level.

Key Information Stored

The primary key is GMD_ACTIONS_B_PK, defined on the ACTION_CODE column. This is the single unique index documented in the metadata and therefore also serves as the business-key candidate — the natural identifier by which quality actions are created, referenced, and retrieved.

  • ACTION_CODE — surrogate and business key; the unique identifier for each quality action record.
  • ACTION_INTERVAL — the interval associated with the action, typically used to schedule or trigger re-evaluation or follow-up.
  • TEXT_CODE — reference to an associated text or message definition used to describe the action to end users.
  • DELETE_MARK — soft-delete/active indicator; rows are logical rather than physically removed.
  • MIGRATED_IND — flag indicating whether the row was introduced through a data migration versus native entry.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the standard Oracle EBS descriptive flexfield (DFF) container, providing 30 extensible attribute columns plus a context column for customer-specific or localization-driven data.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns that record insert and update provenance for every row.

The presence of the full 30-column attribute set and the WHO audit block confirms this is a standard Oracle Application Object Library (AOL)-enabled table using the conventional multi-org-compatible design pattern, though no ORG_ID column is documented here.

Common Use Cases and Queries

Typical usage centers on quality action maintenance and reporting. Administrators and developers query the table to validate action codes before assigning them to quality specifications or results. A representative lookup excluding logically deleted rows:

  • SELECT ACTION_CODE, ACTION_INTERVAL, TEXT_CODE, MIGRATED_IND FROM GMD.GMD_ACTIONS_B WHERE DELETE_MARK = 0 ORDER BY ACTION_CODE;
  • Audit and stewardship reporting using the WHO columns, for example retrieving records updated within a date window: SELECT ACTION_CODE, LAST_UPDATED_BY, LAST_UPDATE_DATE FROM GMD.GMD_ACTIONS_B WHERE LAST_UPDATE_DATE >= :p_from_date;
  • Flexfield extraction for integration or data-warehouse loads: SELECT ACTION_CODE, ATTRIBUTE_CATEGORY, ATTRIBUTE1, ATTRIBUTE2 FROM GMD.GMD_ACTIONS_B;
  • Migration reconciliation: SELECT MIGRATED_IND, COUNT(*) FROM GMD.GMD_ACTIONS_B GROUP BY MIGRATED_IND;

Because the table is classified as standalone, reports generally treat it as a lookup rather than joining it into transactional fact queries, although functional relationships to quality specifications and results exist through application logic rather than enforced constraints.

Related Objects

The documented metadata identifies no enforced foreign keys, consistent with its standalone classification. The following objects are the most significant functionally related tables and views in the OPM/quality domain, joined through ACTION_CODE or through specification/result linkage:

  • GMD_ACTIONS_TL — the translation table for action descriptions, joined on ACTION_CODE.
  • GMD_SPEC_ACTIONS — associates quality actions with specification headers, referenced via ACTION_CODE.
  • GMD_QUALITY_SPECS_B — specification definitions whose steps invoke quality actions.
  • GMD_RESULTS — quality results records that may trigger actions.
  • GMD_SAMPLES — sample records processed under quality action rules.
  • GMD_ACTIONS_VL / GMD_ACTIONS_V — the view layer exposing translated action data to forms and reports.
  • QC_ACTIONS API — the PL/SQL interface typically used for programmatic create/update of action definitions.