mrcirdtl

### 1) Overview
 The `mrcirdtl` table serves as the granular detail level for **Material Receipt Circulars (MRC)** or **Job Work Receipts**. It records the specific outcomes of manufacturing operations performed by external vendors. Each row represents a specific operation (`oprcode`) performed on an item (`itemcode`) under a specific receipt batch (`mrpno`). It tracks accepted versus rejected quantities, associated weights, and links the transaction back to the original Job Card (`jobcardno`) and Purchase Order (`pono`).
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Primary Key | | Internal reference |
 | **compcode** | string | No | Company Code | e.g., "DAS" | Join & Filter |
 | **mrpno** | integer | No | Material Receipt Process Number | | **Primary Join Key** to Header |
 | **itemcode** | string | No | Unique identifier for the item | e.g., "SE", "TOP5" | Join to `itemmas` |
 | **oprcode** | string | No | Operation Code performed | e.g., "BC" (Broaching), "MS" | Join to `oprmas` |
 | **qtyacpt** | integer | Yes | Quantity accepted after inspection | | Aggregation |
 | **qtyrej** | integer | Yes | Quantity rejected after inspection | | Aggregation |
 | **acptwt** | integer | Yes | Weight of accepted items (usually in grams/kg) | | Weight tracking |
 | **wtrej** | number | Yes | Weight of rejected items | | Weight tracking |
 | **oprrate** | number | Yes | Unit rate for the specific operation | | Cost Calculation |
 | **jobcardno** | integer | Yes | Link to the manufacturing Job Card | | Join to `jobhdr` |
 | **mrpdate** | datetime | Yes | Date of material receipt | | Date Filtering |
 | **lotno** | string | Yes | Internal batch or lot number | | Traceability |
 | **wooprqty** | number | Yes | Work Order Operation Quantity | | Balancing/Validation |
 | **rej_flag** | string | Yes | Rejection status indicator | "N", "Y" | Filtering |
 | **pono** | string | Yes | Purchase Order Number | | Join to `podtl` |
 | **podate** | string | Yes | Purchase Order Date | | Information |
 | **amendno** | string | Yes | PO Amendment Number | | Versioning |
 | **amenddate** | string | Yes | PO Amendment Date | | Information |
 | **vendcode** | string | Yes | Vendor/Supplier identifier | e.g., "BP", "MSOI" | Join to `vendmas` |
 
 ### 3) Relationships & Join Map
 
 #### Real Physical Joins (Authoritative)
 Based on `SCHEMA_MAP` and `REFERENCE_JSON`, the following joins are established:
 
 * **mrcirhdr (Header)**
  * `mrcirdtl.mrpno = mrcirhdr.mrpno`
  * `mrcirdtl.compcode = mrcirhdr.compcode`
  * *Context:* Master-detail relationship for material receipts.
 * **itemmas (Items)**
  * `mrcirdtl.itemcode = itemmas.itemcode`
  * `mrcirdtl.compcode = itemmas.compcode`
 * **jobhdr (Job Work Header)**
  * `mrcirdtl.jobcardno = jobhdr.jobcardno`
  * `mrcirdtl.compcode = jobhdr.compcode`
  * *Context:* Linking received material back to the issued production order.
 * **vendmas (Vendors)**
  * `mrcirdtl.vendcode = vendmas.vendcode`
  * `mrcirdtl.compcode = vendmas.compcode`
 * **oprmas (Operations)**
  * `mrcirdtl.oprcode = oprmas.oprcode`
  * `mrcirdtl.compcode = oprmas.compcode`
 * **itemvendopr (Vendor Operation Rates)**
  * `mrcirdtl.itemcode = itemvendopr.itemcode`
  * `mrcirdtl.oprcode = itemvendopr.oprcode`
  * `mrcirdtl.vendcode = itemvendopr.vendcode`
  * *Context:* Validating vendor-specific rates for the work performed.
 
 #### Likely Joins (Inferred)
 * **podtl:** Join on `pono`, `itemcode`, and `compcode` (Used for verifying billing rates against Purchase Orders).