1. Overview
The Vehicle Model DocType is part of the Service Management module in ERPNext. It serves as a master database of vehicle models offered or serviced by your business. Each entry includes the model name, associated vehicle make, type, and an optional route. This central reference improves consistency when creating or managing vehicle-related records such as Service Vehicles.
2. Key Features
- Unique Model Identification: Each vehicle model is uniquely named to prevent duplication.
- Link to Vehicle Make: Ensures traceability between model and manufacturer.
- Categorized by Vehicle Type: Classify models by type (e.g., Sedan, SUV, Truck).
- Optional Route Field: Associate a default route for models if applicable to logistics or servicing.
- Used in Downstream Documents: Auto-populates relevant data in Service Vehicle records.
3. Pre-Requisites
To effectively use the Vehicle Model DocType, ensure the following:
- ✅ Vehicle Make DocType and entries exist.
- ✅ Service Vehicle Type DocType and entries exist.
- ✅ User role has permission to create or update Vehicle Model.
- ✅ A naming convention or format (if applicable) is agreed upon for consistency.
4. Step-by-Step Usage
A. Creating a New Vehicle Model
- Navigate to:
Service Management > Vehicle Model - Click “New”.
- Fill in the fields:
- Model: Required, unique identifier for the vehicle model.
- Make: Link to an existing Vehicle Make.
- Type: Link to a Service Vehicle Type.
- Route: Optional field, useful for route-based planning or servicing.
- Click Save.
B. Using Vehicle Model in Other Documents
- When selected in Service Vehicle, the make and type are automatically fetched, ensuring consistency and reducing data entry time.
5. Script Customizations
You can apply client-side scripts to improve user interaction and data integrity.
Example 1: Auto-format model name in uppercase
frappe.ui.form.on('Vehicle Model', {
model_name: function(frm) {
frm.set_value('model_name', frm.doc.model_name.toUpperCase());
}
});
Example 2: Warn if a route is not provided for certain vehicle types
frappe.ui.form.on('Vehicle Model', {
validate: function(frm) {
if (frm.doc.type === "Commercial" && !frm.doc.route) {
frappe.msgprint("Please enter a route for Commercial vehicle types.");
}
}
});
6. Troubleshooting (Common Errors and Resolutions)
| Issue | Cause | Resolution |
|---|---|---|
| Duplicate model error | Same name used for another record | Ensure each model name is unique |
| Make/Type not available in dropdown | No records exist in linked DocTypes | Add entries to "Vehicle Make" or "Service Vehicle Type" |
| Route field unused | Field not populated | This is optional and can be ignored unless used for logistics/service routing |
7. User Roles and Permissions
Default access is granted to the System Manager. Other roles can be configured as needed.
| Role | Access Level |
|---|---|
| System Manager | Full access |
| Service Admin | Create, Read, Write |
| Sales Executive | Read only |
| Workshop Manager | Read only |
Customize these permissions via Role Permission Manager.
8. Key Notes
- The model name is used as the document name, so it must be unique and descriptive.
- Make and Type are important for downstream data fetching in Service Vehicle and reporting.
- The Route field is flexible and can be used as needed by your business context.
- This DocType plays a central role in maintaining clean master data across the system.
9. What Business Process Pain Point Does It Help Remove
The Vehicle Model DocType helps eliminate inconsistent data entry and duplication by:
- Providing a central repository of all models offered or serviced.
- Ensuring consistent linkage between model, make, and type in service records.
- Enabling standardization across departments (sales, service, logistics).
- Reducing manual errors and improving service planning, inventory control, and customer management.
It streamlines data management for vehicle-based operations and supports accurate reporting and decision-making.