Cargo Type Details

1. Overview

Cargo Type Details is a child table Doctype in the VSD Fleet MS module. It defines the permit requirements for different types of cargo based on the type of movement (import, export, transit, etc.). This structure supports better compliance tracking and helps standardize cargo permit specifications.

2. Key Features

• Captures cargo permit names and their mandatory status.
• Classifies permits based on movement type (e.g., Local Import, Transit Export).
• Structured as a child table, ensuring contextual use inside parent documents.
• Supports listing and quick visibility in table views through in_list_view fields.

3. Pre-Requisites

• Ensure that the VSD Fleet MS module is installed and configured.
• Used as part of a parent document (e.g., Cargo Registration or Cargo Master).
• Proper user permissions are set for reading and editing this child table.

4. Step-by-Step Usage

1. Open the parent document where Cargo Type Details is embedded.
2. In the Cargo Type Details table, click Add Row.
3. Enter the Permit Name (e.g., Road Worthiness Certificate).
4. Check Mandatory if the permit is required for the cargo type.
5. Select the Permit Type from:
   • Local Import
   • Transit Import
   • Local Export
   • Transit Export
   • Border Exit
   • Border Entry
6. Save the parent document to preserve the permit configuration.

5. Script Customizations

The backend Python class is a minimal implementation that extends the base Document class:

from frappe.model.document import Document

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

| Issue                        | Possible Cause                          | Resolution                                                        |
|------------------------------|------------------------------------------|-------------------------------------------------------------------|
| Permit not saving            | Parent document not saved                | Save the parent document after adding permit details.             |
| Permit Type options missing  | Corrupted or modified JSON               | Verify the `permit_type` field includes select options.           |
| Mandatory flag not applying  | Field misconfigured                      | Ensure the field is of type "Check" and used correctly in logic.  |

---

## 7. User Roles and Permissions

- Users with permission to the parent document (e.g., **Cargo Registration**) can manage permit details.
- Only users with **write access** to the parent Doctype can add or modify permit configurations.

---

## 8. Key Notes

- This is a **child table**, so it cannot be created or used independently.
- Useful for tracking **regulatory requirements** per cargo type and route.
- Ensures consistency across cargo documents via **standardized permit categories**.

---

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

- Eliminates **manual tracking** of cargo permit requirements.
- Ensures **compliance** with customs and transport regulations based on cargo movement type.
- Reduces **documentation errors** by flagging mandatory permits clearly.
- Supports **faster processing** and verification of shipment readiness.