| 18 | | === Documentation === |
| 19 | | * UserGuidelines/Logistics |
| 20 | | === Shipment === |
| 21 | | 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. |
| 22 | | * Send Items |
| 23 | | * Receive Items |
| 24 | | * Adjust Items |
| 25 | | * Cancel a shipment |
| 26 | | * Print Reports (Waybill, Goods Received, Donation Certificate) |
| 27 | | * Return goods - typically this is for when: |
| 28 | | * Goods are sent to a distribution point but |
| 29 | | * It was not possible to distributed all the goods and so |
| 30 | | * Some need to be returned to the warehouse |
| 31 | | |
| 32 | | 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. Whilst the place to where the items are being sent is referred to as the site. Both of these are references to org_site records. |
| 33 | | ==== Send & Receive ==== |
| 34 | | This involves a warehouse creating a send inventory record (inv_send) and populating it with stock item records (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 item records (inv_track_item). At this point their will be a send inventory and multiple track item records, physically the items will still be in the warehouse and all the records will have a status of "In Process". |
| 35 | | |
| 36 | | When each track item is created several actions are performed: |
| 37 | | * The tracking number is validated to be unique within the organisation that owns the warehouse |
| 38 | | * The organisation that is doing the shipment is added to the record |
| 39 | | * 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) |
| 40 | | |
| 41 | | 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 and a receive inventory record (inv_recv) is created. Each track item record is linked with this inventory receive record, the ownership of this record is set to being the site to where the goods are being sent. |
| 42 | | |
| 43 | | 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. |
| 44 | | |
| 45 | | 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. |
| 46 | | |
| 47 | | If a shipment is confirmed as having been received by the sending warehouse, then the status of the send inventory is changed to "Received" but within the system no site will actually receive the goods (although one hopes that reality is somewhat different). |
| 48 | | |
| 49 | | When the goods arrive at a site a person responsible for the stock can receive these goods. In this case they will select the sent record and then Receive the shipment. The person needs to view each individual item record and confirm the quantity receives and (optionally) provide details of the bin to where they will go to. Once this is done for every record then the goods in the track items can be received and they will then be moved into the warehouse stock. If their are matching inventory records (same item same bin) then the quantity in those records will be incremented, otherwise a new inventory item record will be created. |
| 50 | | |
| 51 | | Once stock has been received a Goods Received Notice and a Certificate can be printed off. |
| 52 | | |
| 53 | | It is also possible to cancel a received shipment, in this case the goods need to come out of the warehouse and effectively back into the track item records. The sent inventory record is then set to being in transit and the warehouse of origin will then need to cancel the goods for them to go back into the warehouse stock levels. |
| 54 | | |
| 55 | | * Inventory items can be set without being received by a different site. |
| 56 | | * Inventory items can be received without being sent. For example this can cover: |
| 57 | | * Inventory coming from a local supplier |
| 58 | | * Inventory coming from a donor |
| 59 | | ==== Adjusting a Received Shipment ==== |
| 60 | | During a shipment if the goods send and good received totals are different then an adjustment is made (all the original figures are retained for a proper audit trail) During a shipment the adjustment is generated automatically. |
| 61 | | |
| 62 | | The inventory totals in a warehouse are also fixed so once the goods arrive their is no way to adjust them except via a shipment process as described above. Obviously this is not sufficient since goods do get lost, damage or expire. To manage this a virtual stock-take can be done (potentially mirroring a real stock-take) which is essentially an adjustment. When an inventory adjustment is performed (as opposed to a shipment adjustment) all the items in the warehouse with non-zero quantities are automatically added to the adjustment record. It is possible to add new records to the adjustment but they can't be deleted. The user (warehouse manager) will then need to confirm the totals in each record. Once all the record quantities have been set the adjustment can be closes and then this record is locked and no further editing is possible. |
| 63 | | |
| 64 | | === Related === |
| 65 | | * [wiki:BluePrintFinance Finance] |
| 66 | | * BluePrint/Assets |
| 67 | | * BluePrint/Requests |
| 68 | | * BluePrint/Inventory |
| | 29 | ---- |
| | 30 | * [wiki:BluePrintFinance Finance] |
| | 31 | * BluePrint/Assets |
| | 32 | * BluePrint/Requests |
| | 33 | * BluePrint/Inventory |
| | 34 | * DeveloperGuidelines/Logistics |
| | 35 | * UserGuidelines/Logistics (Current Functionality) |
