tables · table
prodfoprdtl
The prodfoprdtl table serves as a granular performance tracking entity within the manufacturing execution system (MES). It records the operational efficiency (eff) of specific items during a production run, categorized by operation code. This table is primarily used by production managers to analyze machine or process performance and to identify variances between standard and actual operational outputs.
Row count
568
Last entry
—
Source
tables
Columns
6| Column | Type | Nullable | Meaning |
|---|---|---|---|
index | integer | No | Synthetic primary key for row identification. |
compcode | string | No | The unique identifier for the company/organization. |
prodno | integer | No | The specific production order or batch number. |
oprcode | string | No | The functional operation code performed on the item. |
itemcode | string | No | The unique identifier for the raw material or finished part. |
eff | number | Yes | The calculated efficiency percentage for the specific operation. |
Full documentation
### 1) Overview The `prodfoprdtl` table serves as a granular performance tracking entity within the manufacturing execution system (MES). It records the operational efficiency (`eff`) of specific items during a production run, categorized by operation code. This table is primarily used by production managers to analyze machine or process performance and to identify variances between standard and actual operational outputs. ### 2) Column Dictionary | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage | | :--- | :--- | :--- | :--- | :--- | :--- | | **index** | integer | No | Synthetic primary key for row identification. | Auto-incrementing | `WHERE index = 0` | | **compcode** | string | No | The unique identifier for the company/organization. | e.g., "DAS" | `ON a.compcode = b.compcode` | | **prodno** | integer | No | The specific production order or batch number. | | `JOIN prodfhdr ON a.prodno = b.prodno` | | **oprcode** | string | No | The functional operation code performed on the item. | ODF, CNCT, CNC2, MILLING, THREAD | `JOIN oprmas ON a.oprcode = b.oprcode` | | **itemcode** | string | No | The unique identifier for the raw material or finished part. | e.g., "CP-091" | `JOIN itemmas ON a.itemcode = b.itemcode` | | **eff** | number | Yes | The calculated efficiency percentage for the specific operation. | 0.00 - 1000.00+ | `AVG(eff) AS AvgEfficiency` | ### 3) Relationships & Join Map The table serves as a detail-level child to production headers and a bridge between items and operations. #### Primary Joins * **dbo.prodfhdr** (Production Header): Linked via `(compcode, prodno)`. Used to associate efficiency metrics with a specific date, operator, or shift. * **dbo.itemmas** (Item Master): Linked via `(compcode, itemcode)`. Used to retrieve part names and categories for efficiency reporting. * **dbo.oprmas** (Operation Master): Linked via `(compcode, oprcode)`. Used to get descriptions for operation codes (e.g., ODF = Outer Diameter Finish). #### Secondary/Likely Joins * **dbo.product2**: Linked via `(compcode, prodno)`. Likely used to correlate efficiency with specific machine codes or rejection counts. * **dbo.DownTime100HDR**: Linked via `(compcode, prodno)`. Used to analyze if low efficiency correlates with high downtime on a specific production run. * **dbo.MachineOperation**: Linked via `(compcode, oprcode)`. Used to identify which machines are capable of performing the operations listed in this detail table.