Open mSupply represents our most recent advancement in the Logistics Management Information System (LMIS), expanding on more than two decades of development inherited from the well-established legacy of the original mSupply.
For a full description of this process refer to the mSupply Remote Authorisation documentation.
In Cloud Server,
A. The Master list that is used for authorisation
[x] Must be the part of the program
[x] The master list should be visible to both receiving and supplying stores
B. Store permissions
[x] In the requesting store, enable the store pref include requisitions from this store in supplier's remote authorisation process
[x] In the supplying store, enable the store preference Use remote authorisation for response requisitions
C. User permissions
[x] In the requesting store, to allow the respective user to change the status of an Internal order, they require permission Can confirm Internal Order as Sent to be enabled at their store.
[x] The authoriser user should have Use web authorisation system permission to authorise/deny the requisition
Creating Internal Order
Creating IO is the usual as Internal Orders; just a lil difference:
[x] When configured as above, the requesting store will see an additional column in the Internal Order list, showing the approval status.
[x] And when viewing a specific Internal Order, there are columns showing the approved quantity, approved number of packs and a comment entered by the approver, if there is one.
Approving Internal Order
After the normal IO is created from the requested store
You cannot send empty internal order and get alert like this
Supplier Requisition
Requisition is also pretty much the same as usual as Requisitions with some differences in authorisation status
[x] When configured as above, the supplying store will have an additional column in the requisition list view showing the approval status
[x] The status is Pending until the requisition is authorised
[x] Depending on the authorisation, the status will change to either of following
Authorised : The comments and quantity to supply can be edited and Outbound Shipments can be created from requisitions that are authorised.
Denied : a requisition with this status cannot be edited further and you cannot create Outbound Shipments from it
[x] And finally, a specific requisition will also have new columns, for the approved quantity and an approval comment, if one has been entered by the approverd
Remote Authorisation
Setup/Configuration
For a full description of this process refer to the mSupply Remote Authorisation documentation.
In Cloud Server,
A. The Master list that is used for authorisation
B. Store permissions
include requisitions from this store in supplier's remote authorisation process
Use remote authorisation for response requisitions
C. User permissions
Can confirm Internal Order as Sent
to be enabled at their store.Use web authorisation system
permission to authorise/deny the requisitionCreating Internal Order
Creating IO is the usual as Internal Orders; just a lil difference:
Approving Internal Order
After the normal IO is created from the requested store
server-URL/authorisation
(This could be sth like http://localhost:1024/authorisation)You cannot send empty internal order and get alert like this
Supplier Requisition
Requisition is also pretty much the same as usual as Requisitions with some differences in authorisation status
Pending
until the requisition is authorised