Results for “gmd_parameters_hdr”

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

Overview

GMD_PARAMETERS_HDR is a table owned by the GMD schema within the Oracle EBS Process Manufacturing Product Development module. Its documented purpose is to store parameter definitions that are used instead of Oracle profile options for certain Process Manufacturing functionality. In practice, this means the table provides an application-level configuration mechanism where behavior is controlled per organization rather than through the standard FND profile hierarchy.

The table is documented in ETRM 12.2.2 as a standalone object with 9 physical columns. The heuristic Data Vault classification mined from the foreign-key structure is standalone, which suggests it can be modeled as an independent hub-like entity without inherited link relationships; because no FK dependencies were mined, it should not be treated as a satellite of another hub unless additional application metadata confirms otherwise. The primary key is GMD_PARAMETERS_HDR_PK on PARAMETER_ID.

Key Information Stored

The table holds 9 documented columns. The most significant are:

• PARAMETER_ID — Surrogate primary key, enforced by GMD_PARAMETERS_HDR_PK. Uniquely identifies each parameter header record.
• ORGANIZATION_ID — Business-key candidate. A unique index, GMD_PARAMETERS_HDR_U2, exists on this column, indicating that parameter settings are scoped to a single inventory organization and that only one parameter header is permitted per organization.
• LAB_IND — Indicator controlling laboratory-related parameter behavior.
• PLANT_IND — Indicator controlling plant or production-related parameter behavior.
• CREATION_DATE, CREATED_BY — Standard audit columns recording when and by whom the record was inserted.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns capturing the most recent modification and the login session responsible for it.

The distinction between the surrogate key and the business key is important: PARAMETER_ID is a system-generated identifier, whereas ORGANIZATION_ID acts as the natural or business key because of the unique index placed on it. Reporting logic should generally join and filter on ORGANIZATION_ID, while referential integrity is maintained through PARAMETER_ID.

Common Use Cases and Queries

The principal use case is retrieving the active parameter configuration for a given organization when Process Manufacturing behavior must be determined at runtime or during reporting.

• Determining lab and plant indicators for a specific organization.
• Auditing when a parameter record was created or last changed and by which user.
• Validating that exactly one parameter header exists per organization before data migration or setup completion.

A typical query retrieves the parameter header for an organization:

SELECT parameter_id, organization_id, lab_ind, plant_ind, last_update_date, last_updated_by FROM gmd.gmd_parameters_hdr WHERE organization_id = :p_org_id;

An audit query returns recent changes:

SELECT organization_id, lab_ind, plant_ind, last_update_date, last_updated_by FROM gmd.gmd_parameters_hdr WHERE last_update_date >= :p_from_date ORDER BY last_update_date DESC;

A completeness check confirms each organization has exactly one row, leveraging the GMD_PARAMETERS_HDR_U2 uniqueness:

SELECT organization_id, COUNT(*) FROM gmd.gmd_parameters_hdr GROUP BY organization_id HAVING COUNT(*) > 1;

Related Objects

The documented metadata classifies GMD_PARAMETERS_HDR as standalone, and no foreign-key relationships were mined. Consequently, the significant related objects are those that consume the parameter values by organization context rather than those joined through a formal FK. Given the limited documented relationship data, the most relevant associations are:

• GMD_PARAMETERS_HDR_PK — The primary-key constraint/index on PARAMETER_ID, used for unique row access.
• GMD_PARAMETERS_HDR_U2 — The unique business-key index on ORGANIZATION_ID, used to enforce one parameter header per organization.
• Process Manufacturing Product Development setup and configuration screens that read LAB_IND and PLANT_IND using ORGANIZATION_ID as the driving context.
• MTL_PARAMETERS and organization-definition tables, which share ORGANIZATION_ID as a common organization-scoping column for cross-reference reporting.
• Standard audit views and concurrent programs that reference the audit columns (CREATION_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY) for change tracking.

Because the mined relationship data is limited, joins beyond ORGANIZATION_ID should be verified against the application's actual foreign-key definitions before being relied upon in production reporting.