Search Results mth_plants_d_u1

Overview

MTH_PLANTS_D is a table owned by the MTH schema, which supports the Oracle Manufacturing Operations Center (MOC) product within Oracle E-Business Suite 12.1.1 and 12.2.2. The table stores plant-level master and descriptive data used by MOC to contextualize manufacturing operations analytics, dashboards, and shop-floor reporting. Each row represents a discrete manufacturing plant or production site, identified by the surrogate primary key PLANT_PK, which is enforced through the unique index MTH_PLANTS_D_U1.

From a Data Vault modeling perspective, the metadata classifies MTH_PLANTS_D as standalone, with no mined foreign-key dependencies to other tables. This suggests it functions as a reference or dimension-style entity rather than a transactional hub or link. In practice, it is best understood as a plant-level satellite/reference table supplying descriptive attributes (geography, ownership, business function, and operational parameters) that other MOC fact and staging objects consume via the plant identifier.

Key Information Stored

The table contains 37 documented columns. The most significant include:

• PLANT_PK — the surrogate primary key and unique business-key candidate (index MTH_PLANTS_D_U1). This is the value joined against by dependent MOC objects.
• PLANT_PK_KEY — an alternate or legacy key column frequently used during integration and load processes.
• PLANT_NAME — the human-readable plant or site name.
• PRODUCTION_SITE — the identifier linking the record to the corresponding EBS inventory organization or production site.
• ADDRESS, CITY, STATE, PROVINCE, ZIP_CODE, COUNTRY — geographic attributes for the plant location.
• CURRENCY_CODE — the currency associated with plant-level financial reporting.
• BUSINESS_FUNCTION_CODE, OWNERSHIP_CODE — classification codes describing the plant's operational role and ownership model.
• IDEAL_TEMPERATURE, E_GRID_ZONE, POWER_RATING_UOM — operational and environmental attributes relevant to energy or utility-oriented manufacturing analytics.
• USER_ATTR1–USER_ATTR5, USER_MEASURE1–USER_MEASURE5 — extensibility columns enabling customer-specific descriptive and numeric attributes without schema changes.
• FROM_DATE, TO_DATE, GRAVEYARD_SHIFT_FLAG — effective-dating and shift-related control columns supporting point-in-time reporting.
• CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_SYSTEM_ID, LAST_UPDATE_SYSTEM_ID — audit and multi-system integration columns.

The surrogate key PLANT_PK is distinct from the descriptive business attributes; no alternate unique business key beyond PLANT_PK is documented.

Common Use Cases and Queries

Typical usage includes plant master reporting, dashboard filters, and joining MOC operational metrics to plant context. A representative pattern retrieves active plants:

• SELECT PLANT_PK, PLANT_NAME, CITY, COUNTRY FROM MTH.MTH_PLANTS_D WHERE TO_DATE IS NULL OR TO_DATE > SYSDATE;
• Filtering by BUSINESS_FUNCTION_CODE or OWNERSHIP_CODE to segment plants by role or ownership.
• Extracting the USER_ATTR and USER_MEASURE columns for customer-specific KPI reporting.
• Resolving PRODUCTION_SITE against inventory organization data to reconcile MOC plants with EBS manufacturing sites.
• Auditing incremental loads using LAST_UPDATE_DATE and LAST_UPDATE_SYSTEM_ID.

Related Objects

Although MTH_PLANTS_D is documented as standalone (no mined FK relationships), it is referenced logically by other MOC objects through PLANT_PK:

• MTH_PLANTS (or the MOC plant/site staging or fact tables) — join on PLANT_PK.
• MOC operational fact and dashboard tables — consume PLANT_PK for plant-level aggregation.
• EBS inventory organization views (e.g., ORG_ORGANIZATION_DEFINITIONS) — associated via PRODUCTION_SITE for reconciliation.
• MTH data-load / interface tables — populate MTH_PLANTS_D from upstream sources.
• Customer-defined MOC reporting views that resolve plant descriptors from this table.