All tables
tables · table

RMOpr

The RMOpr table serves as the Raw Material Routing/Process Sheet definition within the SQL Server database. It specifies the sequence of industrial operations (e.g., Annealing, Straightening, Cutting) performed on specific raw materials. Each record represents a step in the material's processing lifecycle, identified by a sequence number (sno) and an operation code (oprcode). This table is critical for calculating balances during production and determining the "Next Operation" in the manufacturing workflow.

Row count
116
Last entry
Source
tables

Columns

5
ColumnTypeNullableMeaning
compcodestringNOUnique identifier for the company/legal entity.
rmcodestringNOThe unique identifier for the Raw Material.
snointegerNOSerial number representing the sequence of operations.
oprcodestringNOCode for the specific manufacturing operation.
uomstringYESUnit of Measure for the material during this operation.

Full documentation

### 1) Overview
 The `RMOpr` table serves as the **Raw Material Routing/Process Sheet** definition within the SQL Server database. It specifies the sequence of industrial operations (e.g., Annealing, Straightening, Cutting) performed on specific raw materials. Each record represents a step in the material's processing lifecycle, identified by a sequence number (`sno`) and an operation code (`oprcode`). This table is critical for calculating balances during production and determining the "Next Operation" in the manufacturing workflow.
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **compcode** | string | NO | Unique identifier for the company/legal entity. | "DAS" | Primary filter for multi-tenant data isolation. |
 | **rmcode** | string | NO | The unique identifier for the Raw Material. | "1018-45", "11SAE4140" | Join key to `rmmas` and `rmproduct1`. |
 | **sno** | integer | NO | Serial number representing the sequence of operations. | 1, 2, 3 | Used to determine process order and "Next Operation" logic. |
 | **oprcode** | string | NO | Code for the specific manufacturing operation. | "P" (Production), "ANE" (Annealing), "BC", "STRAIGHT" | Join key to `oprmas` or `MachineOperation`. |
 | **uom** | string | YES | Unit of Measure for the material during this operation. | "KGS" | Defines measurement context for quantity calculations. |
 
 ### 3) Relationships & Join Map
 
 #### Real Physical Joins (Authoritative)
 Based on `SCHEMA_MAP` and stored procedure logic in `REFERENCE_JSON`:
 
 * **Raw Material Master**: Join `RMOpr (rmcode)` to `rmmas (rmcode)` to retrieve material descriptions (`rmname`).
 * **Operation Master**: Join `RMOpr (oprcode)` to `oprmas (oprcode)` to get the full name of the operation (`oprname`).
 * **Production Tracking**: Join `RMOpr (rmcode, oprcode)` to `rmproduct1 (itemcode, oprcode)` to link defined process steps to actual production floor entries.
 * **Vendor Pricing**: Join `RMOpr (rmcode, oprcode)` to `rmvendopr (rmcode, oprcode)` to determine the `billrate` or `oprrate` for outsourced material processing.
 * **Production Requirement Generation**: Joined during logic in `temprmreqgen` to calculate in-process weights and balances.
 
 #### Likely Joins (Inferred)
 * **Machine Mapping**: Join `RMOpr (oprcode)` to `MachineOperation (oprcode)` to identify which machines are capable of performing the specific routing step.
 * **Company Context**: Join `RMOpr (compcode)` to `company (co)` or `CompanyConfig (compcode)`.