Search Results gmd_val_rule_gtmp




Overview
Explore in AI Chat

Overview

GMD_VAL_RULE_GTMP is a Process Manufacturing Product Development table owned by the GMD schema. The name suffix _GTMP indicates that it is a Global Temporary Table used during recipe validity rule processing. In Oracle EBS 12.1.1 and 12.2.2, this object serves as an interim staging structure for evaluating and applying recipe validity rules, which determine which recipe version is selected for a given organization, item, and usage context during manufacturing execution, planning, and costing.

Based on the heuristic Data Vault classification derived from its foreign key structure, this table is modeled as a standalone satellite. It carries descriptive measures and status attributes tied to parent business entities but does not itself act as a hub or link. As a temporary staging table, its rows are typically session- or transaction-scoped and are purged or truncated after rule evaluation completes.

Key Information Stored

The table contains 61 documented columns. Its most significant attributes fall into three categories: rule linkage, quantity thresholds, and audit/attribute context.

The two surrogate-to-business linkage keys are RECIPE_VALIDITY_RULE_ID and RECIPE_ID, both documented as foreign keys. No additional unique index is described in the metadata, so business-key uniqueness is presumed to be enforced through the parent rule table.

Common Use Cases and Queries

Typical scenarios involve diagnosing recipe selection behavior, validating rule coverage, and troubleshooting manufacturing transactions that resolve to an unexpected recipe revision. Because the table is temporary, queries are generally session-bound or executed during active rule-processing flows.

  • Identifying which recipe was selected for an item/organization combination: join on RECIPE_ID, ITEM_ID, and ORGANIZATION_ID.
  • Auditing quantity threshold overlaps: SELECT RECIPE_VALIDITY_RULE_ID, MIN_QTY, MAX_QTY, STD_QTY FROM GMD_VAL_RULE_GTMP WHERE ITEM_ID = :item AND ORGN_CODE = :org;
  • Checking status and preference ranking: filter on VALIDITY_RULE_STATUS and order by PREFERENCE to confirm deterministic rule resolution.
  • Reviewing effective dating: compare START_DATE/END_DATE against the transaction date to detect out-of-period rules.

Related Objects

Because the table is a temporary staging object, direct integration or extract reporting is discouraged; consumers should reference GMD_RECIPE_VALIDITY_RULES for stable rule data.