itemstagewise

### 1) Overview
 The `itemstagewise` table serves as a granular tracking ledger for manufacturing throughput. It records the accepted quantity (`acptqty`) of specific items (`itemcode`) as they progress through various operational phases (`oprstage`) within a given production batch or lot (`lotno`). This table is essential for monitoring work-in-progress (WIP) status and identifying yield loss across different manufacturing stages.
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Primary Key. Unique internal identifier. | | `WHERE index = 0` |
 | **compcode** | string | No | Company Code. Physical identifier for the business entity. | e.g., "DAS" | `JOIN ... ON a.compcode = b.compcode` |
 | **lotno** | string | Yes | The production batch or lot number associated with the item. | e.g., "4643J-4", "5404P-1" | `GROUP BY lotno` |
 | **itemcode** | string | Yes | Unique identifier for the part or product. | e.g., "CP-044", "GPDN" | `JOIN itemmas ON itemcode` |
 | **oprstage** | string | Yes | The specific manufacturing operation or stage completed. | CLOSE, CF, CNC2, TRD, ODF, PIER, FINAL, ROLL, THREAD, PHOS, NORM, WELDING | `WHERE oprstage = 'FINAL'` |
 | **acptqty** | number | Yes | The quantity of items successfully passed/accepted at this specific stage. | 0.0 to N | `SUM(acptqty)` |
 
 ### 3) Relationships & Join Map
 
 The table is highly integrated with production tracking and master data tables via the triplet of `compcode`, `itemcode`, and `lotno`.
 
 #### Logical Joins:
 * **Item Master:** Join to `dbo.itemmas` (itemcode) to retrieve part names, drawings, or unit types.
 * **Production/Job Tracking:** Join to `dbo.jobhdr` (lotno, itemcode) or `dbo.product2` (lotno, itemcode) to compare stage-wise acceptance against original job card requirements.
 * **Operational Details:** The `oprstage` column logically relates to `oprcode` or `oprname` in `dbo.oprmas` or `dbo.itemopr`, though the values in this table appear to be descriptive aliases (Likely).
 * **Traceability:** Join to `dbo.ProductTag` (Lotno, Itemcode) to find the machine or date associated with specific batch movements.
 
 #### Join Constraints (SCHEMA_MAP):
 * **dbo.itemmas**: `compcode`, `itemcode`
 * **dbo.jobhdr**: `compcode`, `itemcode`, `lotno`
 * **dbo.ProductTag**: `compcode`, `Itemcode`, `Lotno`
 * **dbo.product2**: `compcode`, `itemcode`, `lotno`
 * **dbo.fghdr**: `compcode`, `itemcode`, `lotno`