| Version 24 (modified by , 13 years ago) ( diff ) |
|---|
Table of Contents
Blue Print - Logistics
To Do:
- Auto-detect alternative items (string compare?)
- Allow alternative items to represent a different quantity of the original item (fields in place, calculations may require some work)
- BluePrint/Inventories#ToDo
- BluePrint/Requests#ToDo
- Item Selector: Currently this just uses a dropdown which isn't scalable. Options:
- A simple Autocomplete
- A widget which allows you to browse via Category (e.g. Tree)
- We also want a 'Details' button to be able to see what a 'First Aid Kit' actually contains
Also See
References
- Requirements for the Logistics Application: http://wiki.sahanafoundation.org/doku.php?id=req:logistics_module
- Terminology used in this module is based on the following document: http://wiki.sahanafoundation.org/doku.php?id=req:logistics_module_definitions
Documentation
Shipment
Items can be moved from one site to another. This is managed by the shipment application. This application has a number of work-flows, which are briefly described here from a technical (developer rather than user) perspective. The shipment application manages the movement of stock items form one site to another. For clarity the word warehouse will be used for the site sending the goods although it would not necessarily be a warehouse.
Send & Receive
This involves a warehouse creating a send inventory (inv_send) and populating it with stock items (inv_inv_item) from the warehouse. The system will move these items from out of the warehouse totals, to avoid any potential problems with over-commitment, and into track items (inv_track_item). At this point their will be a send inventory and multiple track items, physically the items will still be in the warehouse and all the records will have a status of "In Process".
When each track item is created several actions are performed:
- The tracking number is validated to be unique within the organisation that owns the warehouse
- The organisation that is doing the shipment is added to the record
- Details from the inventory item are copied across so that they are preserved (for example if the price changes the price at time of shipping it retained)
When the items are ready to be sent (presumably they have been loaded onto some form of transport and are ready to leave the warehouse) they can then be sent (send shipment). At this point the status of the records are changed to "Sent". These records are now locked to prevent any change (except by someone with admin permissions) and a receive inventory record (inv_recv) is created. Each track item record is linked with this receive record, the ownership of this record is set to being the site to where the goods are being sent.
Once the goods have been send a "Waybill" can be printed off. The shipment can be cancelled (presumably the lorries have been called back) or it is possible to confirm that the shipment has been received, this is used if the items are being received by a site which is not using Sahana-Eden to track the goods. If a shipment is cancelled then the status is changed to "cancelled" (no surprises there) and the good are put back into the warehouse. The quantities in each track item are reduced to zero but the original values are added as a comment.
When the goods arrive
