Add support for multiple stock locations per location -----------------------------------------------------

Key: ARCH-39 URL: https://openvpms.atlassian.net/browse/ARCH-39 Project: Archetypes Issue Type: Improvement Reporter: Tim Anderson Assignee: Tony De Keizer Priority: Minor

As of 1.5, party.organisationLocation can only be associated with a single party.organisationStockLocation, due to limitations in the stock updater.

In order to support multiple stock locations, the stock updater should: * select the default stock location if no product relationship exists * consult each stock location if multiple product relationships exists. If stock is being: ** added, it should go to the default location if a relationship exists, or failing that, the location with the least stock ** removed, it should be removed from the default location if a relationship exists, or failing that, the location with the least stock. If there is not enough stock in the selected location, any remainder should be removed from other stock locations where a relationship exists, drawing down those locations with the least stock first.

Users can do stock transfers if the physical locations don't reflect the selected locations.

-- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://openvpms.atlassian.net/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

_______________________________________________ OpenVPMS Developers Mailing List developers@lists.openvpms.org To unsubscribe or change your subscription visit: http://lists.openvpms.org/listinfo/developers Posts from this mailing list can be viewed online and replied to in the OpenVPMS Developer's forum- http://tinyurl.com/openvdf