All tables
tables · table

downtimedtl

The downtimedtl table is a transaction-level detail table used to record machine downtime events linked to specific production runs. Each record represents a specific downtime instance associated with a production number (prodno), categorized by a downtime reason code (downcode). It is a critical component for calculating OEE (Overall Equipment Effectiveness), utilization, and machine efficiency reports.

Row count
232,100
Last entry
Source
tables

Columns

5
ColumnTypeNullableMeaning
compcodestringNoUnique identifier for the company or business unit.
prodnointegerNoThe production slip or run number associated with the downtime.
downcodeintegerNoIdentifier for the specific reason for downtime (e.g., breakdown, tool change).
downtimenumberNoThe duration of the downtime.
indexintegerNoInternal row identifier (Primary Key).

Full documentation

### 1) Overview
 The `downtimedtl` table is a transaction-level detail table used to record machine downtime events linked to specific production runs. Each record represents a specific downtime instance associated with a production number (`prodno`), categorized by a downtime reason code (`downcode`). It is a critical component for calculating **OEE (Overall Equipment Effectiveness)**, utilization, and machine efficiency reports.
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **compcode** | string | No | Unique identifier for the company or business unit. | e.g., "DAS", "RFL" | Primary key component; used in almost all joins to ensure multi-tenancy isolation. |
 | **prodno** | integer | No | The production slip or run number associated with the downtime. | e.g., 20, 29, 1058 | Foreign key to `product2`, `RMproduct1`, or `DownTime100HDR`. |
 | **downcode** | integer | No | Identifier for the specific reason for downtime (e.g., breakdown, tool change). | e.g., 2, 3, 6, 10 | Foreign key to `downtimemas.downcode`. |
 | **downtime** | number | No | The duration of the downtime. | e.g., 1.0, 2.3, 0.2 | Represented as `HH.MM`. SQL logic often converts this via: `(FLOOR(downtime)*60 + (downtime-FLOOR(downtime))*100)` to get total minutes. |
 | **index** | integer | No | Internal row identifier (Primary Key). | 0, 1, 2... | Internal use only. |
 
 ### 3) Relationships & Join Map
 
 The `downtimedtl` table acts as a bridge between production activity and downtime categorization.
 
 #### Primary Joins (Authoritative via SCHEMA_MAP)
 * **downtimemas**: Joined on `compcode` and `downcode` to retrieve the human-readable `downreason` and `Short_Code`.
 * **product2**: Joined on `compcode` and `prodno` to associate downtime with specific dates (`proddate`), machines (`machine_cd`), and operators (`opername`).
 * **RMproduct1**: Joined on `compcode` and `prodno` for raw material production downtime tracking.
 * **DownTime100HDR**: Joined on `compcode` and `prodno` to link downtime to specific production slips.
 * **oprstationmas**: (Indirectly) Joined via `downtimemas.stationcode` to group downtime by functional station or machine area.
 
 #### Likely Joins (Inferred)
 * **machine**: Joinable via `product2.machine_cd` to `machine.mccode` to report downtime per specific equipment.
 * **prodfhdr**: Likely join on `prodno` for production header details (referenced in OEE stored procedures).