tables · table
operatormas
The operatormas table is a master entity within the SQL Server database that stores information regarding machine and floor operators. It maps unique operator codes to their human-readable names and associates them with specific company codes and system users. This table is primarily used in production tracking and OEE (Overall Equipment Effectiveness) reporting to attribute output and downtime to specific personnel.
Row count
426
Last entry
—
Source
tables
Columns
5| Column | Type | Nullable | Meaning |
|---|---|---|---|
index | integer | NO | Primary key/Internal row identifier. |
compcode | string | NO | Unique identifier for the company or business unit. |
oprcode | integer | NO | Unique numeric identifier for the operator. |
oprname | string | NO | The full name or description of the operator/machine hand. |
username | string | YES | The system login/user ID who created or is responsible for this entry. |
Full documentation
### 1) Overview The `operatormas` table is a master entity within the SQL Server database that stores information regarding machine and floor operators. It maps unique operator codes to their human-readable names and associates them with specific company codes and system users. This table is primarily used in production tracking and OEE (Overall Equipment Effectiveness) reporting to attribute output and downtime to specific personnel. ### 2) Column Dictionary | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage | | :--- | :--- | :--- | :--- | :--- | :--- | | **index** | integer | NO | Primary key/Internal row identifier. | | `PRIMARY KEY` | | **compcode** | string | NO | Unique identifier for the company or business unit. | e.g., "DAS", "RFL" | `JOIN`, `WHERE` | | **oprcode** | integer | NO | Unique numeric identifier for the operator. | e.g., 1, 2, 3... | `JOIN`, `GROUP BY` | | **oprname** | string | NO | The full name or description of the operator/machine hand. | e.g., "CNC AKSHAY" | `SELECT` (Display) | | **username** | string | YES | The system login/user ID who created or is responsible for this entry. | e.g., "system", "dharamveer" | `WHERE` (Filtering) | --- ### 3) Relationships & Join Map The `operatormas` table serves as a reference for production logs and operational settings. Joins are typically performed using the composite key of `compcode` and `oprcode`. #### Physical Joins (via SCHEMA_MAP) * **Production Tracking (`dbo.product2`)**: Joined on `oprcode` and `compcode` to identify which operator produced specific parts in the first stage of production. * **Secondary Production (`dbo.RMproduct1`)**: Joined on `oprcode` and `compcode` to track personnel involved in subsequent production stages. * **Job Processing (`dbo.job`)**: Joined on `oprcode` and `compcode` to link operators to specific job work or subcontractor operations. * **Operational Definitions (`dbo.itemopr`)**: Joined on `oprcode` and `compcode` to define which operator types are authorized for specific item-process sequences. * **Machine Assignments (`dbo.MachineOperation`)**: Joined on `oprcode` and `compcode` to map operators to specific machines they are qualified to run. * **Invoice/Despatch Details (`dbo.invdespdtl`)**: Joined on `oprcode` and `compcode` to link labor charges or rework operations to a specific operator on the invoice level. #### Logical Joins (Inferred from Reference/Schema) * **Production Headers (`dbo.prodfhdr`)**: Likely joined on `oprcode` to attribute machine logs and shift summaries to a specific operator. * **Raw Material Operations (`dbo.RMOpr`)**: Likely joined on `oprcode` to specify which operator handles specific raw material preparations.