Results for “gmd_status_next”

4 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

GMD_STATUS_NEXT is a configuration table in the Oracle EBS Process Manufacturing Product Development (GMD) module. It stores the permissible status transitions for objects governed by the Process Manufacturing status framework — most notably formulas, recipes, and quality specifications. Each row defines a directed edge between a current status and a target status, effectively encoding the status workflow as a finite state machine. The table also identifies the intermediate pending status, an optional rework status, and a workflow indicator that signals whether the transition is driven by Oracle Workflow.

Under a heuristic Data Vault classification mined from its foreign-key structure, this object behaves as a link. It does not carry descriptive attributes about a single business entity; instead, it resolves a many-to-many relationship between status definitions, with the TARGET_STATUS and CURRENT_STATUS columns acting as the two connecting hubs. Modelers treating the GMD status framework as a vault would position GMD_STATUS_NEXT as the link between status hub records, while the audit columns remain as link-level metadata.

In Oracle EBS 12.1.1 and 12.2.2, the table resides in the GMD schema and is referenced at runtime whenever a user attempts to advance, promote, or rework a controlled object. The application validates the requested transition against the rows in this table before permitting the update, so the table is a functional prerequisite for status-driven approvals and change control.

Key Information Stored

The table contains ten documented columns. The most significant are:

  • CURRENT_STATUS — the status an object must be in for the transition to be available. Foreign key to GMD_STATUS_B.
  • TARGET_STATUS — the destination status an object may reach from the current status. Foreign key to GMD_STATUS_B.
  • PENDING_STATUS — the intermediate status applied while the transition is awaiting completion, typically during workflow-driven approval. Foreign key to GMD_STATUS_B.
  • REWORK_STATUS — the status to which a rejected or failed transition returns the object. Foreign key to GMD_STATUS_B.
  • WORKFLOW_INDICATOR — flag denoting whether the transition is executed through Oracle Workflow rather than a direct update.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — record who defined or amended the transition rule and when.

The compound unique index GMD_STATUS_NEXT_PK (TARGET_STATUS, CURRENT_STATUS) is the documented business-key candidate and serves as the primary key. Because all four status columns reference GMD_STATUS_B, GMD_STATUS_B functions as the effective domain of values for this table's semantics. There is no independent surrogate sequence key documented; identification is entirely by the pair of status codes.

Common Use Cases and Queries

The primary use case is enumerating the valid next actions for an object in a given state, which supports UI rendering of permissible status buttons and server-side validation. A representative query retrieves the available transitions for a specific current status and joins back to the status master for descriptive labels:

  • SELECT sn.current_status, cs.status_description, sn.target_status, ts.status_description, sn.pending_status, sn.rework_status, sn.workflow_indicator FROM gmd_status_next sn, gmd_status_b cs, gmd_status_b ts WHERE sn.current_status = cs.status_code AND sn.target_status = ts.status_code AND sn.current_status = :p_status;
  • Reporting on the complete state machine by listing every transition ordered by current status and target status to document approval paths for audit or training material.
  • Identifying workflow-governed transitions with WHERE workflow_indicator = 'Y' to reconcile workflow definitions against configured transitions.
  • Detecting rework paths via rows where REWORK_STATUS IS NOT NULL, useful when diagnosing why a rejected object returned to an unexpected state.
  • Troubleshooting a "transition not allowed" error by confirming the (CURRENT_STATUS, TARGET_STATUS) pair exists in the table.

Related Objects

All four foreign keys converge on a single parent, making GMD_STATUS_B the dominant dependent relationship:

  • GMD_STATUS_B — the status master, joined on CURRENT_STATUS, TARGET_STATUS, PENDING_STATUS, and REWORK_STATUS.
  • GMD_STATUS_TL — provides translated status descriptions for multilingual reporting.
  • GMD_FORMULAS_B / GMD_RECIPES_B — controlled objects whose status values are governed by transitions configured here.
  • GMD_SPECS_B — specification records subject to the same status framework.
  • Process Manufacturing status and workflow APIs — the PL/SQL packages that read GMD_STATUS_NEXT to validate transitions before updating object status.