Service Vehicle

1. Overview

The Service Vehicle DocType is designed to manage and track customer vehicles within the Service Management module. It acts as a digital profile for each vehicle, capturing important details like the registration number, owner, model, VIN, and engine details. This enables a centralized system for managing vehicle-related service operations, histories, and intervals.

2. Key Features

• Unique Registration Number: Ensures each vehicle is distinctly identified.
• Customer Linkage: Ties each vehicle to an existing customer record.
• Vehicle Model Integration: Auto-fetches the make and type from the selected vehicle model.
• Auto-fetch Customer Mobile No: For quick reference and communication.
• Engine, Chassis, and VIN fields: For complete identification and compliance tracking.
• Recommended Service Interval: Helps in proactive service planning.
• Sold By field: Allows tracking of the sales source or dealer.

3. Pre-Requisites

Before adding a Service Vehicle, ensure the following are in place:

• ✅ Customer records are available in the system.
• ✅ Vehicle Model records are configured with make and type fields.
• ✅ Optional: Sold By DocType and records are available (if used).
• ✅ Appropriate user role with access to this DocType is assigned.

4. Step-by-Step Usage

A. Creating a New Service Vehicle

1. Go to:
   Service Management > Service Vehicle
2. Click “New”.
3. Enter the following:
   • Registration Number (Required, must be unique)
   • Customer (Required; will auto-fetch mobile number)
   • Vehicle Model (Required; will auto-fill make and type)
   • Engine Number, Chassis Number, VIN (optional but recommended)
   • Recommended Service Interval (e.g., 10,000 KM or 6 months)
   • Sold By (optional, select from existing entries)
4. Click Save.

B. Viewing or Editing Service Vehicles

• Use filters on list view like Customer, Registration Number, or Vehicle Model to find specific records.
• Click on a record to edit or update details.

5. Script Customizations

You can enhance functionality with client-side scripting.

Example 1: Capitalize Registration Number

frappe.ui.form.on('Service Vehicle', {
  registration_number: function(frm) {
    frm.set_value('registration_number', frm.doc.registration_number.toUpperCase());
  }
});

Example 2: Prompt if Service Interval Not Set

frappe.ui.form.on('Service Vehicle', {
  validate: function(frm) {
    if (!frm.doc.recommended_service_interval) {
      frappe.msgprint("Please consider setting a recommended service interval.");
    }
  }
});

6. Troubleshooting (Common Errors and Resolutions)

7. User Roles and Permissions

By default, only users with the System Manager role have full access.

Suggested Role Permissions:

Use Role Permissions Manager to adjust as needed.

8. Key Notes

• The registration number is used as the document name; it must be unique.
• Fields like make, type, and mobile no are auto-fetched and read-only.
• The form layout uses section breaks and column breaks to improve readability.
• This DocType integrates with downstream service-related documents (e.g., Job Cards, Service Orders).

9. What Business Process Pain Point Does It Help Remove

This DocType addresses the pain of manual vehicle tracking and fragmented customer-vehicle-service mapping by:

• Digitizing all vehicle details in one place.
• Linking customers to their vehicles seamlessly.
• Enabling proactive service reminders through recommended intervals.
• Providing a base for accurate service history, parts forecasting, and customer engagement.

It ensures your service workflows are organized, scalable, and data-driven.