tables · table
Vehiclemas
The Vehiclemas table acts as a master registry for logistics and transport entities. It stores data for both specific physical vehicles (identified by license plates) and general transit methods (e.g., "BY - AIR", "BY - RAIL"). The table is primarily used as a lookup for dispatch documents, invoices, and job challans to ensure standardized transport tracking.
Row count
30
Last entry
—
Source
tables
Columns
5| Column | Type | Nullable | Meaning |
|---|---|---|---|
compcode | string | No | Unique identifier for the company/branch. |
Vehnumber | string | No | The primary identifier for the vehicle or transit method. |
Vehtype | string | Yes | Descriptive classification of the vehicle. |
username | string | Yes | The system user who created or last updated the entry. |
TransType | string | Yes | Categorization code for the type of transit. |
Full documentation
### 1) Overview
The `Vehiclemas` table acts as a master registry for logistics and transport entities. It stores data for both specific physical vehicles (identified by license plates) and general transit methods (e.g., "BY - AIR", "BY - RAIL"). The table is primarily used as a lookup for dispatch documents, invoices, and job challans to ensure standardized transport tracking.
### 2) Column Dictionary
| Column | Type | Nullable | Meaning | Allowed Values | SQL Usage |
| :--- | :--- | :--- | :--- | :--- | :--- |
| **compcode** | string | No | Unique identifier for the company/branch. | e.g., "DAS" | Primary join key for multi-tenant isolation. |
| **Vehnumber** | string | No | The primary identifier for the vehicle or transit method. | License plates (e.g., "HR47G7624") or Methods ("BY - AIR") | Join key for dispatch and invoice headers. |
| **Vehtype** | string | Yes | Descriptive classification of the vehicle. | "REG", "REGULAR", "THROUGH", "MOTOR VEHICLE" | Used for filtering or reporting vehicle classes. |
| **username** | string | Yes | The system user who created or last updated the entry. | e.g., "jitender", "system" | Audit tracking. |
| **TransType** | string | Yes | Categorization code for the type of transit. | "T" (Likely Transport Mode), "V" (Likely Vehicle) | Used to distinguish between methods and assets. |
### 3) Relationships & Join Map
The `Vehiclemas` table is a foundational master table used to validate transportation details across procurement, sales, and production modules.
#### Authoritative Joins (via SCHEMA_MAP):
* **dbo.invhdr**: Join via `compcode` and `Vehnumber`. (Used for sales invoice transport details).
* **dbo.Performainvhdr**: Join via `compcode` and `Vehnumber`. (Used for proforma invoice documentation).
* **dbo.Debithdr**: Join via `compcode` and `Vehnumber`. (Used for return/debit note logistics).
* **dbo.invdesphdr**: Join via `compcode` and `Vehnumber`. (Used for tracking dispatched goods).
* **dbo.bcdataHH**: Join via `compcode` and `vehnumber`. (Handheld device data integration).
* **dbo.despadvicehdr**: Join via `compcode` and `Vehnumber`. (Dispatch planning).
#### Likely Joins (Inferred via Column Naming):
* **dbo.jobhdr / dbo.job / dbo.rmjobhdr**: Join via `compcode` and `Vehicle` (Likely matches `Vehnumber`).
* **dbo.rgphdr**: Join via `compcode` and `vehicle` (Likely matches `Vehnumber` for Returnable Gate Pass).
* **dbo.ScrapChallan**: Join via `compcode` and `vehicle` (Likely matches `Vehnumber`).