oca / stock-logistics-transport

Transport management in Odoo

stock-logistics-transport

TODO: add repo description.

Available addons

addon	version	maintainers	summary
shipment_advice	16.0.1.4.1		Manage your (un)loading process through shipment advices.
shipment_advice_planner	16.0.1.1.0		This module is used to plan ready transfers in shipment advices.
shipment_advice_planner_toursolver	16.0.1.0.0		Shipment advices planning by geo-optimization (TourSolver)
shipment_advice_planner_toursolver_queue_job	16.0.1.0.0		Run TourSolver queries in queue jobs
stock_dock	16.0.1.0.1		Manage the loading docks of your warehouse.

Licenses

This repository is licensed under AGPL-3.0.

However, each module can have a totally different license, as long as they adhere to Odoo Community Association (OCA) policy. Consult each module's __manifest__.py file, which contains a license key that explains its license.

---

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

stock-logistics-transport's Issues

Migration to version 15.0

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-15.0

Modules to migrate

• shipment_advice
• stock_dock
• stock_location_address - By @JoanMForgeFlow - #74
• stock_location_address_purchase - By @JoanMForgeFlow - #75

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

How to choose the mean of transport in the shipment plan

Hi,

I'm testing the module and it's really great. Thanks a lot for that. The only point I found so far is that I do not know where I can define the means of transport for the shipment plan. I would like to add (air, truck, train, etc.)

Thanks for any answer.

Migration to version 13.0

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-13.0

Modules to migrate

• stock_location_address - By @JoanSForgeFlow - #52
• stock_location_address_purchase - By @JoanSForgeFlow - #53

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

[stock-shipment-management] Some entered fields are not passed around

The following fields are not passed around when entered in 'shipment.plan.creator':

1. carrier_tracking_ref: Fill 'carrier_tracking_ref' field in the wizard and click 'create'. A new 'shipment.plan' record is created with a 'carrier_tracking_ref' field filled with the value previously entered by the user. Open one of the picking from the shipment plan, and the user will be surprised that the 'carrier_tracking_ref' field is blank. Of course it does not get passed to the 'stock.picking' simply because all the related 'stock.picking' are already created before the 'shipment.plan' is created.
2. consignee_id: Same steps as the previous point. This time i think it does not get passed to the 'stock.picking' because there is no 'consignee_id' field in the _compute_shipment_data method.

Are there any reasons behind this decision? I think i can help with the PR if there are no reasons behind this decision. Thanks!

move_ids dummy field necessary on stock_shipment_management/wizard/create_shipment.py ?

This computed field needs some explanations.

#4 (comment)

Migration to version 17.0

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-17.0

Modules to migrate

• shipment_advice
• shipment_advice_planner
• stock_dock

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

Migration to version 12.0

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-12.0

Modules to migrate

• stock_location_address
• stock_location_address_purchase - By @Joansis - #51

RFC: Transportation Management System

Migration and refactoring of Jarsa TMS modules.
v15 sources: https://github.com/ursais/stock-logistics-transport/tree/15.0-jarsa
Credits: @alan196

TMS

• Menu items:

  • Dashboard: Teams (Kanban, Timeline, Activity)
  • Operations: All trips (List, Form), Odometers
  • Master Data: Vehicles, Drivers, Locations, Contracts, Services
  • Reporting: Trips (Graph, Pivot), Costs
  • Configuration: Settings, Teams, Stages (for Travel, Driver and Vehicle)

• Groups:

  • TMS / Administrator: Access to all menu items
  • TMS / User (dispatcher): Access to all menu items except Configuration
  • TMS / Driver: portal user?
  • Technical / Use TMS Teams

• Settings: Activation of advanced features via groups or modules

  • Fleet options
  • Activate Teams (a team shares the same process/stages)
  • Activate Crews (a crew shares the same vehicle)
  • Activate Driver License Expiration + Number of days
  • Activate Vehicle Insurance Expiration + Number of days
  • Integrations: GPS, Maps, Marketplaces, Telemetry

• Basic models:

  • Stages (tms.stage)
  • Teams (tms.team)
  • Vehicles (fleet.vehicle): cargo or passengers, type, capacity
  • Drivers (res.partner)
  • Locations (res.partner)
  • Routes (tms.route)
  • Travels (tms.order)

• Dependencies: fleet

TMS - Sale

To sell trips by quantity, volume, weight, quantity of a specific product, distance (miles, kilometers, nautic miles)

• Dependencies: tms, sale

TMS - Expenses

To manage expenses of a trip: hotel, tolls, fuel, etc.

• Dependencies: tms, hr_expense

TMS - Account

To invoice trips to the customer and create vendor bills to the drivers and other suppliers

• Dependencies: tms, account

TMS - Purchase

To create purchase requests to drivers and other suppliers

• Dependencies: tms, purchase

TMS - Account - Asset

To manage depreciation of vehicles

• Dependencies: tms, account_asset

TMS - Maintenance

To manage preventive maintenance

• Dependencies: tms, maintenance

TMS - Skills

To manage driver skills and licenses

• Dependencies: tms, hr_skills

TMS - Air

To manage transportation by air (airlines, air cargo):

• Vehicles: planes, helicopters, drones

• Locations: Airports

• Dependencies: tms

TMS - Water

To manage transportation by water:

• Vehicles: boats, tankers, barges, ferries, container ships

• Locations: Ports

• Dependencies: tms

TMS - Rail

To manage transportation by rails:

• Vehicles: Trains, Wagons

• Dependencies: tms

[stock-shipment-management] Partner address required?

In demo database, it is not possible to Add to shipment plan:
Traceback (most recent call last):
File "/home/eric/odoo/CVS/8.0/odoo_ocb/openerp/http.py", line 537, in _handle_exception
return super(JsonRequest, self)._handle_exception(exception)
File "/home/eric/odoo/CVS/8.0/odoo_ocb/openerp/http.py", line 588, in dispatch
return self._json_response(result)
File "/home/eric/odoo/CVS/8.0/odoo_ocb/openerp/http.py", line 526, in _json_response
body = simplejson.dumps(response)
File "/usr/lib/python2.7/dist-packages/simplejson/init.py", line 370, in dumps
return _default_encoder.encode(obj)
File "/usr/lib/python2.7/dist-packages/simplejson/encoder.py", line 269, in encode
chunks = self.iterencode(o, _one_shot=True)
File "/usr/lib/python2.7/dist-packages/simplejson/encoder.py", line 348, in iterencode
return _iterencode(o, 0)
File "/usr/lib/python2.7/dist-packages/simplejson/encoder.py", line 246, in default
raise TypeError(repr(o) + " is not JSON serializable")
TypeError: res.partner() is not JSON serializable

It is not possible to create a shipment plan either (probably for similar reasons)

Branches in OCA

This branch should not be here: https://github.com/OCA/stock-logistics-transport/tree/8.0-purchase_transport_multi_address-onchange_fix

I am not use if this was done on purpose or not but I don't think it is correct.

Regards.

Migration to version 9.0

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-9.0

Modules to migrate

• sale_transport_multi_address
• stock_shipment_management
• stock_route_transit
• stock_transport_multi_address - By @mikevhe18 - #42
• purchase_requisition_transport_multi_address
• transport_information - By @mikevhe18 - #43
• purchase_transport_multi_address

Migration to version 11.0

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-11.0

Modules to migrate

• purchase_requisition_transport_multi_address
• purchase_transport_multi_address
• sale_transport_multi_address
• stock_route_transit
• stock_shipment_management
• stock_transport_multi_address
• transport_information

[Road Map] module: stock_shipment_management doesn't support package info

Hi,

Currently for module: stock_shipment_management, there is no package information in the shipment plan, I think we should not only add the departure moves on shipment plan, but also the departure packages (stock.pack.operation) and should calculate the total gross/net weight and total volume depending on the packages.

I'll proceed to make a pull request.
Any feedback is welcomed.

thanks and best regards,
Alex

RFC for CMR Management and e-CMR Integration in Odoo ERP

RFC for CMR Management and e-CMR Integration in Odoo ERP

Introduction

eCMR, as a digital adaptation of the traditional CMR consignment note, has been legally validated and is an integral part of the international transport of goods. Endorsed by numerous countries and supported by the United Nations, its adoption signifies a pivotal move towards digitalization in the transportation sector. This transition is not only a technological advancement but also aligns with global efforts for sustainable and innovative logistics practices.

Objective

Develop and implement a functionality in Odoo ERP to manage transportation processes in compliance with the CMR Convention and to prepare for the mandatory use of e-CMR starting in September 2024.

General Description

• Sale as Route: Each sale represents a transport route.
• Purchases and Carriers: Each purchase linked to a route is a carrier.
• CMR Management: One CMR document is updated by each carrier.
• Final Signature and Invoicing: The completed CMR is attached to the invoice for client payment.

Technical Specifications

1. Sale Route Module: Links sales to transport routes and purchases.
2. CMR Management Module: Creates, updates, and tracks the CMR document.
3. Integration with Purchases: Links purchases to CMR updates.
4. Completion and Sending of CMR: Finalizes CMR for invoicing.
5. CMR Claims from Suppliers: Automated CMR request and collection.
6. Security and Compliance: Ensures legal compliance and data security.
7. User Interface and Experience: User-friendly design and accessibility.
8. Reporting and Analysis: Tools for tracking and improving logistics.

e-CMR Integration

• Compliance with 2024 Regulation: Adapts to mandatory e-CMR usage.
• Digital Transformation: Transitions from paper-based to digital CMR.
• Subsidy Utilization: Leverages financial programs like "Cheque Moderniza".
• Technical Adaptation: Prepares for technology changes required by e-CMR.
• Training and Support: Provides training for e-CMR system use.

Conclusion

Integrating CMR and e-CMR functionalities in Odoo aligns with regulatory changes and represents a commitment to digital transformation in logistics and transportation management.

Thank you in advance.

Best regards,

Rafael Blasco
@moduon MT-4057

Ref:

• https://www.iru.org/what-we-do/facilitating-trade-and-transit/e-cmr

Migration to version 16.0

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-16.0

Modules to migrate

• shipment_advice - By @lmignon - #87
• stock_dock - By @lmignon - #87
• stock_location_address - By @Mikheil-21 - #124
• stock_location_address_purchase

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

[Road Map] packing list printout of module stock_shipment_management

Hi,
Anyone has started the development on the packing list printout? If not yet, I'll start the development and make a pull request for it.

Thanks,

Alex

Migration to version 14.0

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0

Modules to migrate

• stock_dock - By @dzungtran89 - #63
• stock_location_address
• stock_location_address_purchase - By @JoanMForgeFlow - #73
• shipment_advice

Missing module? Check https://github.com/OCA/maintainer-tools/wiki/%5BFAQ%5D-Missing-modules-in-migration-issue-list

Migration to version 10.0

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-10.0

Modules to migrate

• purchase_requisition_transport_multi_address
• purchase_transport_multi_address
• sale_transport_multi_address
• stock_route_transit
• stock_shipment_management
• stock_transport_multi_address
• transport_information

[stock-shipment-management] Enhance the current module for sales shipments

Hi,
We have a customer who would use this module but it is currently missing some features we need:

• Current module is PO centered which is not ideal and not generic. Shipment should be either sales or purchases oriented.
• There is no Custom agent (it might be different from the carrier in our case)
• We should link the shipment with landing cost (extended), one for the carrier, one for the agent.
• all setup should be gathered in the warehouse menu (currently consignee is in sales, transport mode in purchase etc..)

I would rather modify this module for the sales part+setup and create a new one for the landed costs

Your thoughts

[13.0] [INFO] "stock_location_address" - Wrong github repository into manifest.py module

@etobella
It seems that information regarding "github module repository" in module manifest.py file, is wrong...
Should be : "website": "https://github.com/OCA/stock-logistics-transport",
Instead of : "website": "https://github.com/OCA/stock-logistics-warehouse",