tables · table
prodfdowndtl
The prodfdowndtl table (Production Failure Downtime Detail) serves as a granular log for recording machine or production line downtime events. It captures the specific reason for a stoppage and the duration of the downtime associated with a specific production run (prodno).
Row count
28,799
Last entry
—
Source
tables
Columns
5| Column | Type | Nullable | Meaning |
|---|---|---|---|
index | integer | No | Internal primary key / record index. |
compcode | string | No | Company Identifier. |
prodno | integer | No | Production Header Reference Number. |
downtimereason | integer | Yes | Reference code for the cause of downtime. |
downtime | number | Yes | Duration of the downtime event. |
Full documentation
### 1) Overview The `prodfdowndtl` table (Production Failure Downtime Detail) serves as a granular log for recording machine or production line downtime events. It captures the specific reason for a stoppage and the duration of the downtime associated with a specific production run (`prodno`). This table is frequently used in OEE (Overall Equipment Effectiveness) calculations and production reporting views (e.g., `viewproductionDownTime`) to aggregate total minutes lost. The data indicates a format where the integer part of the `downtime` value typically represents a whole unit (e.g., hours or minutes) while the fractional part represents the remainder, often converted in SQL using logic such as `(floor(downtime)*60 + (downtime - floor(downtime))*100)`. ### 2) Column Dictionary | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage | | :--- | :--- | :--- | :--- | :--- | :--- | | **index** | integer | No | Internal primary key / record index. | Auto-incrementing | `PRIMARY KEY` | | **compcode** | string | No | Company Identifier. | e.g., "DAS" | `JOIN`, `WHERE` | | **prodno** | integer | No | Production Header Reference Number. | e.g., 61, 2, 5 | `JOIN`, `GROUP BY` | | **downtimereason** | integer | Yes | Reference code for the cause of downtime. | e.g., 1-8 | `JOIN` (to `downtimemas`) | | **downtime** | number | Yes | Duration of the downtime event. | e.g., 6.0, 0.45 | `SUM()`, Calculation | ### 3) Relationships & Join Map Based on the `SCHEMA_MAP` and `REFERENCE_JSON`, the following joins are authoritative: #### Direct Joins * **dbo.prodfhdr** (Production Failure Header): Joined via `compcode` and `prodno`. This relationship links downtime details to the specific machine, operator, and date of the production event. * **dbo.downtimemas** (Downtime Master): Joined via `compcode` and `downtimereason` (corresponds to `downcode` in the master table). Used to retrieve the descriptive reason for the stoppage (e.g., "Power Cut", "Tool Breakage"). * **dbo.product1** / **dbo.product2**: Joined via `compcode` and `prodno`. Used to correlate downtime against actual production output and shift durations. #### Related Tables (Inferred) * **dbo.DownTime100DTL**: Likely a similar detail table for distinct types of downtime reporting (e.g., 100% machine unavailability), sharing the same `prodno` and `compcode` keys.