[
http://issues.apache.org/jira/browse/OFBIZ-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461699
]
David N. Welton commented on OFBIZ-584:
---------------------------------------
One algorithm for this might be:
Each supplier has a couple of thresholds:
* Minimum order - below this, simply do not order. Above this, go ahead and
order if you're going to be late with deliveries, but not otherwise.
* Order now - go ahead and just order.
Having this sort of automation could lead to automation of supplier orders -
manually sending hundreds of orders is simply not feasible for anyone doing a
decent volume of business.
Automation might also include an upper limit - block the order if it's above a
certain limit. If you wanted to be really clever, you could look at the
average amount for past orders and flag anything way above that...
> Consolidate orders
> ------------------
>
> Key: OFBIZ-584
> URL: http://issues.apache.org/jira/browse/OFBIZ-584
> Project: Apache OFBiz (The Open for Business Project)
> Issue Type: Improvement
> Reporter: Iain Fogg
>
> During the course of processing purchase orders (usual over several days),
> two or more orders for the same supplier might be created. It would be
> extremely useful to be able to consolidate these orders into a single order.
> The typical scenario here is that POs are generated from Requirements, which
> are often reviewed and approved on a daily basis. Sometimes the size of the
> generated order might be too small to send to the supplier, so you need to
> wait for a day or two to accumulate more items.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
