temprmreqgen

This documentation describes the `temprmreqgen` table, a temporary processing table used within the ERP's Material Requirements Planning (MRP) or Production module to calculate raw material (RM) requirements based on current schedules, sales, and Work-In-Progress (WIP).
 
 ### 1. Overview
 The `temprmreqgen` table serves as a staging area for calculating the "Raw Material Requirement Generation." It aggregates data points from sales schedules (`schqty`), current inventory (`opbal`), and WIP across various stages (in-house and vendor-side) to determine the net balance of material needed (`balwt`) to satisfy production demands.
 
 ### 2. Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Primary key for the temporary record. | | `PK` |
 | **compcode** | string | No | Company Code identifier. | e.g., "DAS" | `JOIN`, `WHERE` |
 | **rmcode** | string | Yes | Raw Material Code. | | `JOIN`, `GROUP BY` |
 | **itemcode** | string | Yes | Finished or semi-finished item code produced from the RM. | | `JOIN`, `WHERE` |
 | **chwt** | number | Yes | Charge Weight: The gross weight of RM required per unit. | | `CALC` |
 | **conversionwt** | number | Yes | The weight of the item after processing/conversion. | | `CALC` |
 | **opbal** | string | Yes | Opening Balance (Likely numeric stored as string). | | `WHERE` |
 | **clvendorist** | integer | Yes | Closing Stock at Vendor (Stage 1/I). | | `SUM` |
 | **clvendoriind** | integer | Yes | Closing Stock at Vendor (Stage 2/II). | | `SUM` |
 | **saleofthemonth** | integer | Yes | Total sales recorded/forecasted for the current month. | | `CALC` |
 | **onlinesc** | string | Yes | Online Scrap generated during production. | | `Likely Info` |
 | **itemreturn** | string | Yes | Quantity of items returned. | | `Likely Info` |
 | **semipurchase** | string | Yes | Semi-finished purchase quantities. | | `Likely Info` |
 | **productionist** | string | Yes | Production quantity from Stage 1/I. | | `Likely Info` |
 | **jobist** | string | Yes | Job work quantity from Stage 1/I. | | `Likely Info` |
 | **jobiind** | string | Yes | Job work quantity from Stage 2/II. | | `Likely Info` |
 | **rejaccept** | string | Yes | Rejections accepted back into stock. | | `Likely Info` |
 | **recofthemonth** | string | Yes | Recovered material for the month. | | `Likely Info` |
 | **fgtowip** | string | Yes | Finished Goods returned to WIP for rework. | | `Likely Info` |
 | **wip** | integer | Yes | Current Work-In-Progress quantity. | | `CALC` |
 | **wipwithvendors** | integer | Yes | WIP quantities currently held at external vendor locations. | | `CALC` |
 | **balwt** | number | Yes | Calculated balance weight required to meet schedule. | | `CALC` |
 | **origschqty** | integer | Yes | Original scheduled quantity before adjustments. | | `Inquiry` |
 | **schqty** | integer | Yes | Current adjusted production schedule quantity. | | `CALC` |
 | **extraschqty** | integer | Yes | Buffer or extra schedule quantity. | | `CALC` |
 | **inprocesswt** | number | Yes | Weight of material currently in process. | | `CALC` |
 
 ### 3. Relationships & Join Map
 
 The table links specific items and raw materials to their master definitions and current stock levels to facilitate requirement calculations.
 
 #### Primary Joins (SCHEMA_MAP Grounded):
 * **dbo.itemmas**: Join via `compcode`, `rmcode`, and `itemcode`. Used to fetch item names, conversion weights, and unit masters.
 * **dbo.rmmas**: Join via `compcode` and `rmcode`. Used to fetch raw material specifications (grade, size).
 * **dbo.itemrmchwt**: Join via `compcode`, `itemcode`, and `rmcode`. Used to validate the relationship between an item and its specific RM charge weight.
 * **dbo.wipstock / dbo.wipjobstock**: Join via `compcode` and `itemcode`. Used to compare calculated temporary WIP against persisted inventory snapshots.
 
 #### Likely Joins (Inferred):
 * **dbo.suppmas**: Join via `compcode` and `vendcode` (if derived from associated transaction tables) to identify specific vendors holding `clvendorist`.
 
 ---