Search Results gmd_parsed_expression




Overview
Explore in AI Chat

Overview

GMD_PARSED_EXPRESSION is a table in the GMD schema, owned by the Process Manufacturing Product Development module of Oracle E-Business Suite. It stores the parsed expression for technical parameters, decomposing a formula or parameter definition into its constituent tokens so that downstream processing logic — typically Quality Management specification calculations and formula validation — can resolve parameter references without re-parsing the raw text on every access. The table is documented as VALID in both EBS 12.1.1 and 12.2.2, and the physical schema documented in ETRM 12.2.2 lists 11 columns.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone. This is a suggestion only: although GMD_PARSED_EXPRESSION carries a foreign key to GMD_TECH_PARAMETERS_B, it holds its own surrogate sequence identifier (TECH_EXP_SEQ_ID) and descriptive attributes, so it is best treated as an independent table rather than as a pure satellite hanging off a parent hub. Analysts modeling this data should retain the parent linkage while recognizing that the expression rows have their own identity lifecycle.

Key Information Stored

The documented column set is compact and centers on identifying which technical parameter an expression belongs to and how that expression is composed.

  • TECH_EXP_SEQ_ID — the surrogate primary key of the table; each parsed expression fragment receives a unique sequence value.
  • TECH_PARM_ID — foreign key to GMD_TECH_PARAMETERS_B; the technical parameter whose expression was parsed. This is the principal business-key candidate for joins.
  • EXPRESSION_KEY — the token or key identifying the expression element within the parsed structure.
  • EXPRESSION_TYPE — classifies the nature of the parsed element (for example, operand versus operator versus reference), allowing the application to reconstruct evaluation order.
  • EXPRESSION_PARM_ID — identifies a parameter referenced from within the expression, supporting nested or cross-parameter formulas.
  • DATA_TYPE — the datatype of the parsed value, used when coercing results during calculation.
  • CREATION_DATE, CREATED_BY — audit columns recording initial insertion.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS "Who" columns maintained by the audit trail, used for change tracking and concurrent-program diagnostics.

No unique index is documented beyond the surrogate key, so TECH_PARM_ID combined with EXPRESSION_KEY and EXPRESSION_TYPE is the practical composite identifier for business purposes.

Common Use Cases and Queries

The most frequent use is tracing how a technical parameter resolves during specification or formula evaluation. A typical query joins the parsed expression to its parent parameter:

  • Retrieve all parsed tokens for a parameter: SELECT p.tech_parm_id, p.expression_key, p.expression_type, p.data_type FROM gmd_parsed_expression p WHERE p.tech_parm_id = :tech_parm_id ORDER BY p.tech_exp_seq_id;
  • Find parameters that reference another parameter through a nested expression: SELECT tech_parm_id, expression_parm_id FROM gmd_parsed_expression WHERE expression_parm_id IS NOT NULL;
  • Audit recently modified expressions: SELECT * FROM gmd_parsed_expression WHERE last_update_date > SYSDATE - 7;
  • Reporting on datatype distribution to detect malformed parameter definitions.

These patterns support formula debugging, data-conversion validation in 12.1.1 to 12.2.2 upgrades, and reconciliation between the raw parameter text and the parsed representation.

Related Objects

  • GMD_TECH_PARAMETERS_B — the direct parent; joined on TECH_PARM_ID.
  • GMD_TECH_PARAMETERS_TL — translated parameter descriptions for reporting.
  • GMD_SPEC_TECH_PARAMETERS — links technical parameters to specifications.
  • GMD_SPECIFICATIONS_B — specification headers consuming evaluated parameters.
  • GMD_FORMULA_HEADERS / GMD_FORMULA_DETAILS — formula definitions that reference technical parameters.
  • GMD_QM_RESULTS and related Quality Management result tables — where evaluated expressions surface as measured values.
  • GMD_API / QM specification PL/SQL packages — programmatic consumers that read parsed expressions at runtime.

The ETRM documentation for this object is intentionally terse; column semantics beyond the documented list should be confirmed against the GMD schema DDL in each specific patch level.