-
Notifications
You must be signed in to change notification settings - Fork 105
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
9 changed files
with
120 additions
and
4 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,111 @@ | ||
» [Home](../index.md) / [Stock Management](./index.md) / [Stock Movements](./movement.md) / Shipments | ||
|
||
# Shipments | ||
|
||
When stock is transferred from one depot to another, it is called a "shipment". This could be involve collecting stock in one depot and shipping it via truck to another depot in an entirely different location. Or it could simply be taking some stock from one depot to another in the same building. For instance, purchasing and receiving stock from external suppliers is often done through a primary depot, while a pharmacy is also considered a "depot" in BHIMA. So once stock is received in the primary depot, transferring it to a pharmacy in the same building would still be considered a shipment. | ||
|
||
Shipments are restricted to transferring stock from one depot to another. These involve stock exits (from the sending depot) and stock entry (into the receiving depot). Technically, transferring stock from one depot to another could be done by directly using the Stock Exit and Stock Entry interfaces and not directly using the Shipping interface. However, users should be aware that even if the shipment interface is not directly used, a shipment is still created when stock is exited from one depot and sent to another. Other types of stock exits (such as exit to "Loss") or stock entries (such as entry by "Integration") do not involve BHIMA "Shipments". | ||
|
||
|
||
## The BHIMA Shipments interface | ||
|
||
In the BHIMA interface, there is "Shipments" menu entry in the top-level menu: | ||
<img src="./images/shipments-menu.png" alt="Main shipments menu" align="right" width="200"> | ||
|
||
There are two entries under the "Shipments" menu: | ||
1. New Shipment - Create a new shipment | ||
2. Shipment Registry - Display shipments with status and actions that can be performed on them. | ||
|
||
## The Lifecycle of a Shipment | ||
Shipments can be the following states: | ||
- **Empty** - the order has been created but contains no stock | ||
- **At depot** - the shipment has been created but not finalized | ||
- **Ready for shipment** - The shipment packing list is finalized | ||
- **In transit** - The shipment is in | ||
- **Partial** - Partially Received by the receiving depot | ||
- **Complete** - The order has been completed (sent and received) | ||
- **Delivered** - The order has been received but not unpacked or entered into stock | ||
- **Lost** - The order was lost (typically lost in transit) | ||
|
||
Shipments go through several phases during their lifetime (these phases are related to the states listed above): | ||
1. **Creation** - In this step, a shipment is created including information about | ||
- the sending and receiving depots | ||
- expected arrival date, and | ||
- a packing list of stock to be shipped. | ||
During creation, it is still possible to update the packing list of items in the shipment. Once the shipment container is completely packed, the warehouse proceeds to the next step. | ||
2. **Marked as "Ready to Ship"** - At some point, the user needs to declare that the shipment marked as complete and ready to ship. For instance, this could be when the container for the shipment is closed and ready to be shipped. Once a shipment is marked as ready to ship, the contents (packing list) of the shipment cannot be changed. | ||
3. **Stock Exit** - After a shipment is ready to ship, the stock involved needs to be "exited" from the sending depot. Up to this point, the packing list for a shipment is only tentative. It is still possible to delete the shipment at this point. When the stock exit for a shipment is performed, the stock is removed from the sending depot and is considered to be in transit. Once the stock exit for a shipment occurs, the shipment can no longer be deleted. Doing the "Stock Exit" for a shipment is easily accomplished using the action menu for the shipment in the Shipment Registry. | ||
4. **Departure from sending depot** - After the stock exit for a shipment is complete, it can depart from the sending depot. | ||
5. **Transit** - The physical movement of the stock could be as complicated as sending the shipment in a container and by truck or airplane to another location. Or it could be as simple as walking a few items to another room in the same building. While this occurs it is in transit. There are means in the Shipment Registry for updating the location and condition while it is in transit. | ||
6. **Arrival at the Receiving Depot** - Once the shipment arrives at the receiving depot, it is ready for stock entry. Until stock entry occurs, the stock is still not officially in any depot. | ||
7. **Stock Entry** - As the shipment is deposited in the receiving depot, the BHIMA software needs to be updated. This is accomplished by doing the "Stock Entry" for the receiving depot. Generally, once the stock entry occurs, the shipment is marked as complete. | ||
|
||
## Example Shipment Process | ||
The purpose of this example is to show the basic use of the BHIMA interface for shipments and how using the Shipments interface simplifies the process of sending stock from one depot to another. | ||
|
||
### Creating the shipment | ||
Suppose you want to ship several articles of stock from the "Primary Depot" to a "Secondary Depot". Start by going to the BHIMA `New Shipment` page. | ||
<div class="bs-callout bs-callout-success"> | ||
<p> | ||
<i>menu</i> > Shipments > <strong>New Shipment</strong> <br> | ||
⇒ Opens the form for creating a new shipment | ||
</p> | ||
</div> | ||
You will see a page like this partially completed form. | ||
<img src="./images/new-shipment.png" alt="New shipment form" align="right" width="700px"> | ||
The items in red indicate necessary inputs to complete the form: | ||
|
||
1. This item in blue shows the currently selected source depot. If no depot has been selected, you will be prompted to chose a source depot before the form will be shown. If the depot shown here is not the correct depot, use the "Change Depot" item in the [Menu] on the top right of the page to select the correct source depot. | ||
2. This area will shows the status of the shipment creation process and any alerts that need to be dealt with. | ||
3. Enter a label (or name) for the shipment. This is short identifier that the personnel both in the sending depot and receiving depot will recognize. | ||
4. Select the depot to receive the shipment | ||
5. Select the anticipated delivery date | ||
6. Add explanatory notes (optional). For instance if the shipment needs to be routed through some intermediate location, that could be shown here. This is also an appropriate place to add notes about the urgency or fragility of the shipment. | ||
7. When you are ready to add stock to the shipment, click on this [Add] button. This will add lines for each item as desired. | ||
8. Update and review articles of stock in the shipment. You can think of this as the packing list. Adding stock here works similarly to adding articles of stock in the Stock Exit form. Here we show an empty line immediately after clicking on the [Add] button. Select the article of stock to be added to the shipment by typing in an inventory code into the "Inventory Code" box and then selecting the desired lot and quantity. You can add additional items by clicking the [Add] button again. Note that the left end of each line in the packing list has a status indicator. When the line is correctly filled out, the status indicator will show a small green check. | ||
9. Once you have have added all the desired articles of stock to the shipment (and there are no warnings in the form), click on the [Submit] button to complete the shipment. | ||
|
||
### Mark the order as ready to go | ||
For this step, go to the `Shipment Registry` page. | ||
<div class="bs-callout bs-callout-success"> | ||
<p> | ||
<i>menu</i> > Shipment > <strong>Shipment Registry</strong> <br> | ||
⇒ Opens shipments registry | ||
</p> | ||
</div> | ||
The shipment registry will show all shipments along with their status. On the right end of each line is a link to open the action menu for that shipment. Here is what the registry and action menu look like at this point (in the example): | ||
<img src="./images/shipment-registry.png" alt="Shipment Registry" width="100%"> | ||
When you click on the **Actions** link it will bring up a menu like this: | ||
<img src="./images/shipment-actions1.png" alt="Shipment action menu - initial" align="right" width="300"> | ||
Here is a brief recap of the actions available at this point: | ||
|
||
a. These two commands show documentation for the shipment <br> | ||
b. The **Tracking Log** includes all events in the life of the shipment and allows the user to add additional comments as appropriate. For instance the user could add a comment indicating that the shipment has arrives at some intermediate location. <br> | ||
c. **Update Packing List** allows the user to edit or update the shipment including editing the packing list. <br> | ||
d. Mark the shipment **Ready to Ship** <br> | ||
e. Display the **Barcode** for this shipment <br> | ||
f. Delete the shipment. | ||
|
||
To complete this step in the example, select the "Ready to Ship" option and confirm the action in the modal dialog. | ||
|
||
<div class="bs-callout bs-callout-info"> | ||
**NOTE**: An important thing to note about the action menu for shipments is that it will only display actions that can be done based on the current status of the shipment. This makes it straightforward to process shipments since the action menu essentially guides the user through the normal process of dealing with shipments. | ||
</div> | ||
|
||
### Stock Exit at the Sending Depot | ||
At this point, the shipment is ready to to be shipped and a stock exit should be performed as soon as possible. Although this could be done by going to the Stock Exit page directly, it is easier to go back to the `Shipments > Shipments Registry` page again and bring up the action menu for the shipment. A new entry for the Stock Exit will appear: | ||
<img src="./images/shipment-actions2.png" alt="Shipment action menu - stock exit" align="right" width="300"> | ||
Notice the new entry on the menu: "Exit stock for this shipment". When you click on this action, it will take you directly to the Stock Exit page with the articles of stock in the shipment configured for quick approval. | ||
|
||
### Transit | ||
Once the stock exit for a shipment has been performed, the the shipment (and contained stock) is considered to be in transit. As far as BHIMA software is concerned this is a sort of "in limbo" state -- the items are tracked by the BHIMA software (via the shipment itself) but are no in any depot. It is possible that the shipment will sit on the loading dock of the origin depot until it is loaded on a vehicle and physically leaves the sending facility. Once the shipment leaves the sending depot, its transportation progress can be logged using the "Tracking Log" in the Shipments Registry action menu. | ||
|
||
### Arrival at the Receiving Depot | ||
Once a shipment arrives at the receiving depot, it will be unpacked and the items entered into the stock for the receiving depot. | ||
|
||
### Stock Entry at the Receiving Depot | ||
The Shipments interface makes this straightforward. Go back to the Shipments Registry and open the action menu for the desired shipment. A new entry for the Stock Exit will appear: | ||
<img src="./images/shipment-actions3.png" alt="Shipment action menu - stock entry" align="right" width="300"> | ||
When the user clicks on the "Enter stock for this shipment" item, the user will be taken to the Stock Entry page for the shipment with all the relevant information set up for easy approval. | ||
|
||
Note at this point, if the Stock Entry is approved with all items received, the shipment will automatically be closed (marked "Complete"). However, if any items are missing or lost due to damage, the shipment status will be marked as "Partial". It can remain in the "partial" state as appropriate, but it can be manually closed (via the action menu after the stock exit). |