nonretitm

### 1. Overview
 The `nonretitm` table serves as the **Header** for **Non-Returnable Gate Passes (NRGP)**. It tracks the departure of items from the facility that are not expected to be returned, such as material rejected to vendors, scrap sales, or materials sent for one-way processing (e.g., washing, packing, or cold forging). 
 
 This table contains high-level transaction details including the vendor/recipient, total amount, transportation method, and document references. It is a critical component for inventory reconciliation, as it records a permanent reduction in stock levels for consumables and items.
 
 ### 2. Column Dictionary
 
 | Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
 | :--- | :--- | :--- | :--- | :--- | :--- |
 | **index** | integer | NO | Primary internal row identifier. | | `PRIMARY KEY` |
 | **compcode** | string | NO | Company code for multi-tenant/branch tracking. | e.g., "DAS", "BPH" | Join to `dbo.company` |
 | **nrgpno** | integer | NO | Unique Non-Returnable Gate Pass Number. | | Header Key for `nonretitmdtl` |
 | **nrgpdate** | datetime | NO | The date the gate pass was issued. | | Filtering by date range |
 | **slipno** | integer | YES | Reference number for an internal slip or manual record. | 0 if not used | Audit trail |
 | **vendcode** | string | YES | Unique identifier for the recipient/vendor. | e.g., "SGI", "BP" | Join to `dbo.vendmas` |
 | **through** | string | YES | The mode of transport or person responsible for transit. | e.g., "BY ROAD", "BY HAND" | Logistics tracking |
 | **amount** | number | YES | Total monetary value of the items issued. | | Financial reporting |
 | **remarks** | string | YES | Descriptive notes regarding the purpose of the exit. | | Qualitative analysis |
 | **mprint** | string | YES | Print status flag. | 'Y', Null | Control logic |
 | **mnrgpno** | integer | YES | Manual NRGP Number reference. | | Cross-referencing |
 | **nrgpdoc** | string | YES | Formatted document string for display/printing. | e.g., "1-2/NRGP/" | UI/Reporting |
 
 ### 3. Relationships & Join Map
 
 Based on the `SCHEMA_MAP` and usage in `REFERENCE_JSON`, the following joins are authoritative:
 
 #### Primary Joins (Confirmed via SCHEMA_MAP)
 * **dbo.nonretitmdtl** (Child Table):
  * `nonretitm.compcode = nonretitmdtl.compcode`
  * `nonretitm.nrgpno = nonretitmdtl.nrgpno`
  * *Note:* This join retrieves the specific items, quantities (`qtyissue`), and rates associated with the gate pass.
 * **dbo.vendmas** (Vendor Master):
  * `nonretitm.compcode = vendmas.compcode`
  * `nonretitm.vendcode = vendmas.vendcode`
  * *Note:* Used to retrieve `vendname` and address details.
 
 #### Likely Joins (Inferred from standard ERP logic)
 * **dbo.company**:
  * `nonretitm.compcode = company.compcode`
 * **dbo.citemmas** (Indirect via `nonretitmdtl`):
  * Joins via `nonretitmdtl.citmcode = citemmas.citmcode` to identify specific non-stock or consumable items.