tables · table
RMproduct1
The RMproduct1 table serves as a detailed production transaction log, specifically for raw material (RM) or component processing. It tracks the output of specific machine operations, including quantities produced (qtyinpic), quality metrics (acptqty, rejqty, scrapqty), and machine utilization/downtime. It is primarily used for secondary operation reporting and calculating work-in-progress (WIP) balances.
Row count
1
Last entry
2026-01-12
Source
tables
Columns
29| Column | Type | Nullable | Meaning |
|---|---|---|---|
index | integer | NO | Primary Key; Internal row identifier |
compcode | string | NO | Company Code identifier |
prodno | integer | NO | Production Record Number |
proddate | datetime | YES | Date the production occurred |
lotno | string | YES | Batch or Lot identification number |
shift | string | YES | Working shift code |
itemcode | string | YES | Part or material code produced/processed |
machine_cd | string | YES | Machine identifier |
qtyinpic | number | YES | Total quantity produced in pieces |
weight | number | YES | Physical weight of the produced items |
oprcode | string | YES | Operation Code (often the process being performed) |
downtime | string | YES | Duration of machine downtime |
dtreason | string | YES | Reason for machine downtime |
opername | string | YES | Name or ID of the operator |
issueno | integer | YES | Link to Material Issue document |
username | string | YES | User who recorded the entry |
acptqty | number | YES | Quantity accepted after inspection |
rejqty | number | YES | Quantity rejected due to defects |
scrapqty | number | YES | Quantity designated as scrap |
useradd | string | YES | User who created the record |
addtime | string | YES | Timestamp of record creation |
irno | integer | YES | Inspection Report Number |
shifthrs | number | YES | Actual hours worked during the shift |
heatno | string | YES | Material heat number for traceability |
cycle | number | YES | Machine cycle time |
variant | string | YES | Product variant/specification |
location | string | YES | Physical location or warehouse section |
HoldQty | number | YES | Quantity held for further inspection |
curoprcode | string | YES | Current/Active Operation Code |
Full documentation
### 1) Overview The `RMproduct1` table serves as a detailed production transaction log, specifically for raw material (RM) or component processing. It tracks the output of specific machine operations, including quantities produced (`qtyinpic`), quality metrics (`acptqty`, `rejqty`, `scrapqty`), and machine utilization/downtime. It is primarily used for secondary operation reporting and calculating work-in-progress (WIP) balances. ### 2) Column Dictionary | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage | | :--- | :--- | :--- | :--- | :--- | :--- | | **index** | integer | NO | Primary Key; Internal row identifier | | PK | | **compcode** | string | NO | Company Code identifier | e.g., "DAS" | Join key to `CompanyConfig` | | **prodno** | integer | NO | Production Record Number | e.g., 1000549 | Join key to `DownTime100DTL` | | **proddate** | datetime | YES | Date the production occurred | | Filtering/Reporting | | **lotno** | string | YES | Batch or Lot identification number | e.g., "29019P-6" | Join to `jobhdr`, `mrci_rep` | | **shift** | string | YES | Working shift code | A, B, C | Grouping | | **itemcode** | string | YES | Part or material code produced/processed | e.g., "OUTERRIN" | Join key to `itemmas`, `rmmas` | | **machine_cd** | string | YES | Machine identifier | e.g., "CNC230" | Join key to `machine` (mccode) | | **qtyinpic** | number | YES | Total quantity produced in pieces | | Aggregation | | **weight** | number | YES | Physical weight of the produced items | | | | **oprcode** | string | YES | Operation Code (often the process being performed) | e.g., "CLOSE", "CNC1" | Join key to `oprmas` | | **downtime** | string | YES | Duration of machine downtime | | | | **dtreason** | string | YES | Reason for machine downtime | | | | **opername** | string | YES | Name or ID of the operator | e.g., "1 MUKESH" | | | **issueno** | integer | YES | Link to Material Issue document | | Likely join to `rmpmchdr2` | | **username** | string | YES | User who recorded the entry | | | | **acptqty** | number | YES | Quantity accepted after inspection | | Quality Analysis | | **rejqty** | number | YES | Quantity rejected due to defects | | Quality Analysis | | **scrapqty** | number | YES | Quantity designated as scrap | | | | **useradd** | string | YES | User who created the record | | Audit | | **addtime** | string | YES | Timestamp of record creation | | Audit | | **irno** | integer | YES | Inspection Report Number | | Join to `iteminspectionhdr` | | **shifthrs** | number | YES | Actual hours worked during the shift | | Productivity metrics | | **heatno** | string | YES | Material heat number for traceability | | Traceability | | **cycle** | number | YES | Machine cycle time | | Efficiency metrics | | **variant** | string | YES | Product variant/specification | | | | **location** | string | YES | Physical location or warehouse section | | Join to `location` | | **HoldQty** | number | YES | Quantity held for further inspection | | | | **curoprcode** | string | YES | Current/Active Operation Code | | | ### 3) Relationships & Join Map #### Real Physical Joins (Grounded in SCHEMA_MAP) * **Production Context**: * `RMproduct1.prodno` → `dbo.DownTime100DTL.prodno` (Tracks specific downtime events for this production run) * `RMproduct1.prodno` → `dbo.DownTime100HDR.prodno` * **Master Data Joins**: * `RMproduct1.itemcode` → `dbo.itemmas.itemcode` (Retrieve part names, weights, and UOM) * `RMproduct1.itemcode` → `dbo.rmmas.rmcode` (Retrieve raw material specific details) * `RMproduct1.machine_cd` → `dbo.machine.mccode` (Retrieve machine names and specifications) * `RMproduct1.oprcode` → `dbo.oprmas.oprcode` (Retrieve full operation descriptions) * **Company/Location**: * `RMproduct1.compcode` → `dbo.CompanyConfig.compcode` * `RMproduct1.location` → `dbo.location.location` #### Logical/Likely Joins (Inferred from Logic) * **Lot Traceability**: `RMproduct1.lotno` likely joins with `dbo.jobhdr.lotno` or `dbo.mrci_rep.lotno` for end-to-end traceability. * **Operator Data**: `RMproduct1.opername` likely relates to `dbo.operatormas.oprname`. * **Issue Documents**: `RMproduct1.issueno` relates to material headers used in the production process (e.g., `rmpmchdr2`, though not explicitly in map).