tables · table
rmjobrec1stdtl
The rmjobrec1stdtl table stores the operational details and associated rates for the "1st Stage" Raw Material (RM) Job Receipts. It acts as a line-item detail table linking specific MRP (Material Requirement Planning) numbers to their required manufacturing operations (oprcode) and financial rates for a specific work order year.
Row count
6,997
Last entry
—
Source
tables
Columns
6| Column | Type | Nullable | Meaning |
|---|---|---|---|
compcode | string | No | Unique identifier for the company/plant location. |
mrpno | integer | No | Material Requirement Planning number; the document ID for the job receipt. |
itemcode | string | No | The unique identifier for the part or component. |
oprcode | string | No | Code representing the specific manufacturing operation. |
rate | number | Yes | The financial rate associated with performing this specific operation. |
woyear | integer | No | The fiscal or work order year associated with the document. |
Full documentation
### 1) Overview The `rmjobrec1stdtl` table stores the operational details and associated rates for the "1st Stage" Raw Material (RM) Job Receipts. It acts as a line-item detail table linking specific MRP (Material Requirement Planning) numbers to their required manufacturing operations (`oprcode`) and financial rates for a specific work order year. This table is primarily used in production tracking to determine which operations were performed on a received item and is referenced by reporting procedures like `JobIncRecd_Balance` to fetch operation names and calculate balances for incoming job work. ### 2) Column Dictionary | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage | | :--- | :--- | :--- | :--- | :--- | :--- | | **compcode** | string | No | Unique identifier for the company/plant location. | E.g., "DAS", "RF2" | Primary Join Key | | **mrpno** | integer | No | Material Requirement Planning number; the document ID for the job receipt. | | Primary Join Key | | **itemcode** | string | No | The unique identifier for the part or component. | E.g., "BWAUTO", "GC1" | Join Key to `itemmas` | | **oprcode** | string | No | Code representing the specific manufacturing operation. | E.g., "BC", "FINAL", "HOT" | Join Key to `oprmas` | | **rate** | number | Yes | The financial rate associated with performing this specific operation. | E.g., 0.0, 1.25 | Calculation | | **woyear** | integer | No | The fiscal or work order year associated with the document. | E.g., 2014, 2015 | Primary Join Key | --- ### 3) Relationships & Join Map #### Real Physical Joins (Confirmed via SCHEMA_MAP) * **dbo.rmjobrec1st**: Joined via `compcode`, `mrpno`, and `woyear`. This is the parent header table containing the receipt weights and dates. * **dbo.oprmas**: Joined via `compcode` and `oprcode`. Used to retrieve the descriptive name of the operation (`oprname`). * **dbo.itemmas**: Joined via `compcode` and `itemcode`. Used to fetch item descriptions and master rates. * **dbo.itemopr**: Joined via `compcode`, `itemcode`, and `oprcode`. Used to validate operation sequences or specific instruction numbers (`pisno`). * **dbo.desp1stjobdtl**: Joined via `compcode`, `itemcode`, and `oprcode`. Links operations to their respective dispatch records. #### Logical Joins (Likely) * **dbo.rmmrphdr**: Likely joins via `compcode` and `mrpno` to track quality inspection and acceptance status of the original material receipt. * **dbo.rmjobrec2nddtl**: Frequently used in `UNION ALL` views (like `view_JobworkINC_recd_Opr_sigle_record`) for full process visibility across 1st and 2nd stage receipts. ---