mcdtl

### 1) Overview
 The `mcdtl` (Machine Card Detail) table is a transaction-level table used to store granular data related to material issues and production operations, specifically for "Ist Operation" (First Operation) processes. It tracks quantities issued (in pieces and weight), the specific manufacturing operation performed (`oprcode`), and batch tracking via `lotno`. It functions as the detail component to the `mchdr` (Machine Card Header) table.
 
 ### 2) Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | No | Unique record identifier (Primary Key) | | PK |
 | **compcode** | string | No | Unique identifier for the company | | Join (Filter) |
 | **issueno** | integer | No | Machine Card issue number; links to header records | | Join (FK) |
 | **mrpno** | integer | Yes | Material Requirement Plan or Batch reference number | | Join/Filter |
 | **issuedate** | datetime | Yes | The date and time the material was issued for processing | | Filter |
 | **itemcode** | string | No | Unique code for the part or raw material | | Join (FK) |
 | **oprcode** | string | No | Operation code for the specific task (e.g., BC = Bar Cutting) | | Join (FK) |
 | **rate** | number | Yes | Unit cost or valuation rate of the item | | Calculation |
 | **pcs** | integer | Yes | Quantity issued in pieces | | Aggregate |
 | **weight** | number | Yes | Physical weight of the material (typically in KG) | | Aggregate |
 | **lotno** | string | Yes | Batch or heat number for material traceability | | Filter/Group |
 | **repeat** | string | Yes | Indicator for repeat operations or rework (Likely) | | Filter |
 
 ### 3) Relationships & Join Map
 
 #### Parent Tables
 * **mchdr**: Primary header for machine card issues. Joined on `compcode` and `issueno`.
 * **itemmas**: Master table for item descriptions and rates. Joined on `compcode` and `itemcode`.
 * **oprmas**: Master table for operation names and details. Joined on `compcode` and `oprcode`.
 
 #### Dependent Tables (Referenced in Logic)
 * **product2**: Production transaction table. While not a direct parent, production entries in `product2` are often validated against the issues recorded in `mcdtl`.
 * **viewproductionIst**: A standard view that aggregates `mcdtl`, `mchdr`, and `product2` to report on first-operation production.
 
 #### Join Examples
 * **To get operation names:** `mcdtl.oprcode = oprmas.oprcode`
 * **To get item names:** `mcdtl.itemcode = itemmas.itemcode`
 * **To link with production entries:** `mcdtl.issueno = product2.issueno` (via `mchdr` logic)