Round Trip Mapping
Introduction
The Round Trip Mapping module in ERPNext Vehicle Trip Tracking manages the linkage between onward and return trip schedules. It ensures that trips labeled as "Onward" are correctly matched with corresponding "Return" trips to form logical round trips.
Purpose
This module helps fleet managers maintain proper round trip relationships between schedules to streamline planning, reduce duplication, and improve operational clarity.
Key Features
- Link an onward trip schedule with a corresponding return trip schedule.
- Validation to ensure onward trip is marked as "Onward" and return trip as "Return" in their respective schedules.
- Prevents conflicting or duplicate round trip mappings with error messages.
- Ensures city and state details for onward and return trips logically match to enforce correct round trip formation.
- Ability to disable round trip mappings if needed.
How to Use Round Trip Mapping
1. Create a New Round Trip Mapping
Create a new Round Trip Mapping record. Select an onward trip schedule from the list of "Onward" trips and a return trip schedule from the list of "Return" trips.
2. Verify Auto-filled Fields
The corresponding routes, cities, and states for both onward and return trips will auto-fill and be read-only. Review these for accuracy.
3. Validation on Save
Saving the document will perform validations to:
- Check that the onward trip is indeed marked as "Onward" and the return trip as "Return" in their schedules.
- Ensure that neither trip is already linked in another round trip mapping.
- Verify that the from and to cities and states logically pair between onward and return trips (e.g., onward from city matches return to city).
4. Disable Mapping (Optional)
You can disable a round trip mapping using the "Disabled" checkbox if the linkage is no longer applicable.
Important Fields
| Field | Description | Required |
|---|---|---|
| Onward Trip Schedule | Select the trip schedule marked as "Onward". | Yes |
| Return Trip Schedule | Select the trip schedule marked as "Return". | Yes |
| Onward Trip Route | Auto-filled linked route for onward trip (read-only). | No |
| Return Trip Route | Auto-filled linked route for return trip (read-only). | No |
| Onward From City/State | Auto-filled from linked onward route (read-only). | No |
| Onward To City/State | Auto-filled from linked onward route (read-only). | No |
| Return From City/State | Auto-filled from linked return route (read-only). | No |
| Return To City/State | Auto-filled from linked return route (read-only). | No |
| Disabled | Check to disable this round trip mapping. | No |
Validation and Errors
The system prevents creating invalid mappings by:
- Throwing an error if the selected onward trip schedule is not marked "Onward".
- Throwing an error if the selected return trip schedule is not marked "Return".
- Checking and preventing duplicate or conflicting mappings involving the same trips.
- Ensuring city and state fields logically correspond between onward and return trips.
Best Practices
- Create round trip mappings only after verifying trip types in schedules.
- Regularly review mappings to disable those no longer in use.
- Use clear naming and documentation in trip schedules to simplify mapping.