Main Route Steps

1. Overview

The Main Route Steps is a child table within the Fleet Management system that outlines each stop or step along the main transport route of a trip. It is typically embedded in the Trips Doctype to detail all important logistics checkpoints such as loading/unloading points, borders, and document handling.

2. Key Features

• Links each route step to a specific Trip Location
• Tracks logistics timestamps: arrival, departure, loading, offloading
• Captures customs border crossing events
• Tracks document submission and receipt for compliance and audit
• Simple and structured layout using section breaks for clarity
• Integrated into Trips to provide a full journey overview

3. Pre-Requisites

Before using Main Route Steps, ensure the following are set up:

• The Trip Locations Doctype has defined entries.
• A Trip record exists to which this child table will attach.
• Users have access rights to view and update Trips.

4. Step-by-Step Usage

1. Navigate to the relevant Trip record.
2. In the Main Route Steps section (child table), click "Add Row".
3. Fill in the following details for each route step:
   • Location: Select from the Trip Locations list.
   • Location Type: Manually specify (e.g., Border, Loading Point, Offloading Point).
4. Under Dates section:
   • Provide Arrival Date and Departure Date.
   • Input Loading Date and Offloading Date as required.
5. Under Border Details:
   • Specify Documents received from driver (datetime).
   • Indicate Documents submitted to agent (date).
   • Enter Documents received by and Crossing date and time.
6. Under Extra Information:
   • Add any Additional Comment relevant to the step.
7. Save the Trip record to store the route steps.

5. Script Customizations

The main_route_steps.py Python file contains a basic class:

from frappe.model.document import Document

class MainRouteSteps(Document):
    pass
## 6. Troubleshooting (Common Errors and Resolutions)

| Issue                   | Cause                      | Resolution                                           |
|-------------------------|----------------------------|------------------------------------------------------|
| Cannot select Location  | Trip Locations are missing | Add entries in **Trip Locations** Doctype            |
| Invalid Date Range      | Arrival is after Departure | Ensure **Arrival Date** ≤ **Departure Date**         |
| Missing data in steps   | Incomplete entries         | Make sure all mandatory fields are filled before saving the Trip |

---

## 7. User Roles and Permissions

| Role          | Permission                          |
|---------------|--------------------------------------|
| Fleet Manager | Full access (Read, Write, Create)    |
| Trip Officer  | Can add and update route steps       |
| Driver        | Typically no access unless customized|

> Permissions are inherited from the parent **Trip** Doctype.

---

## 8. Key Notes

- Each row represents a single checkpoint or location event on the trip.
- Use consistent naming conventions for **Location Type** to support reporting (e.g., always use `"Border"`, not `"border"`).
- Ensure date fields are recorded promptly to support real-time tracking.

---

## 9. What Business Process Pain Point Does It Help Remove

The **Main Route Steps** table helps eliminate the lack of visibility and tracking in logistics operations.  
It ensures all movement events and checkpoints are documented with timestamps and document handling records.  
This reduces miscommunication, delays, and compliance issues during inland transport across borders and terminals.