Search Results mth_equipments_d




Overview
Explore in AI Chat

Overview

The MTH_EQUIPMENTS_D table is a core data object within the Oracle Manufacturing Operations Center (MTH) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the master definition, descriptive attributes, and manufacturing-relevant parameters for equipment assets tracked by the Operations Center. Each row represents a single equipment record spanning identity, physical characteristics, performance standards, and operational status, allowing plant and production personnel to model the machinery and work centers that drive shop-floor activity.

The table resides in the MTH schema and is documented as a VALID object with a physical structure of 41 columns. From a Data Vault modeling perspective, the mined relationship structure classifies MTH_EQUIPMENTS_D as a standalone object. This heuristic suggests it behaves primarily as a reference or dimension-style entity rather than a transactional link, meaning it can reasonably be modeled as a hub or satellite candidate when building downstream analytical or integration layers, without strong foreign-key dependencies to other MTH tables.

Key Information Stored

The table carries both surrogate and business identifiers alongside a rich set of descriptive and operational attributes. The most significant columns include:

Common Use Cases and Queries

Typical usage centers on equipment master reporting, capacity and utilization analysis, and asset valuation. A common query retrieves active production equipment for a given organization:

  • SELECT EQUIPMENT_NAME, EQUIPMENT_DESCRIPTION, STATUS, LOCATION FROM MTH.MTH_EQUIPMENTS_D WHERE EBS_ORGANIZATION_ID = :org_id AND PRODUCTION_EQUIPMENT = 'Y';
  • Reporting on asset value: aggregate FIXED_ASSET_VALUE grouped by plant or organization using PLANT_FK_KEY and EBS_ORGANIZATION_ID.
  • Calibration and maintenance audits: filter by LAST_CALIBRATED and INSTALLATION_DATE to identify overdue equipment.
  • Capacity planning: join STD_UTILIZATION, STD_EFFICIENCY, and STD_CYCLE_TIME into downstream OEE calculations.
  • Data integration: use EQUIPMENT_PK_KEY and EQUIPMENT_NAME for upsert logic when loading from external systems, leveraging the unique indexes U2 and U3.

Related Objects

The documented relationship data classifies this object as standalone, meaning no direct foreign-key constraints were mined from the schema. Nonetheless, operational linkage is implied through several columns that reference other MTH and EBS structures:

  • MTH_SYSTEMS_D — associated through SYSTEM_FK_KEY, defining the system hierarchy to which equipment belongs.
  • MTH_PLANTS_D — associated through PLANT_FK_KEY, providing plant-level context.
  • EBS organization/equipment tables — referenced via EBS_ORGANIZATION_ID and EBS_EQUIPMENT_ID for master alignment with EBS inventory and asset sources.
  • MTH work-order and production tables — consume EQUIPMENT_PK as the operational reference in shop-floor transactions and event collection.
  • MTH asset and maintenance tables — leverage SERIAL_NUMBER, MODEL_NUMBER, and FIXED_ASSET_VALUE for asset tracking.

Because no enforced foreign keys are documented, referential integrity toward these dependent objects is maintained at the application layer rather than by database constraints.