OFBiz › OFBiz - Dev

[jira] Created: (OFBIZ-584) Consolidate orders

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

6 messages Options

Nicolas Malin (Jira)

[jira] Created: (OFBIZ-584) Consolidate orders

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

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-584) Consolidate orders

[ http://issues.apache.org/jira/browse/OFBIZ-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461674 ]

Iain Fogg commented on OFBIZ-584:
---------------------------------

Perhaps an extension to this idea is to extend the Quick PO generation tool in Requirements to allow the selection of an existing PO. If such a selection is made, the new Requirements are added to the existing PO, otherwise a new PO is created.

In this case, there would probably need to be a rule that says POs can only be extended if they are in the "Created" state (presumably, any other state means the PO is further advanced down its lifecycle, and changing the order in this way should be disallowed).

> 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

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-584) Consolidate orders

In reply to this post by Nicolas Malin (Jira)

[ http://issues.apache.org/jira/browse/OFBIZ-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461682 ]

Scott Gray commented on OFBIZ-584:
----------------------------------

Hi Iain

I can't find the Quick PO generation tool, what is the address of the page containing the link to this?

Thanks
Scott

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-584) Consolidate orders

In reply to this post by Nicolas Malin (Jira)

[ 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...

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-584) Consolidate orders

In reply to this post by Nicolas Malin (Jira)

[ http://issues.apache.org/jira/browse/OFBIZ-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461705 ]

Jacopo Cappellato commented on OFBIZ-584:
-----------------------------------------

Scott,

the screen is this:
https://demo.dejc.com:8443/ordermgr/control/ApprovedProductRequirements

(Order->Requirements->Approved Product Requirements)

When, in this screen, you filter the requirements by supplier AND you select the company for which you will perform the PO, using the "Bill To Customer Party Id" field, the list at the bottom will change into a multi-form list and a new link will appear to quickly create the po.

PS:
The "Approved Product Requirements" screen filters the requirements by:
- type = "Product Requirement" aka requirements for purchase orders
- status = approved

PPS: when a requirement is created the system will try to automatically assign it to a supplier (using the supplier preference order in SupplierProduct); however you can edit this information in Order->Requirements->Roles screen

Nicolas Malin (Jira)

[jira] Commented: (OFBIZ-584) Consolidate orders

In reply to this post by Nicolas Malin (Jira)

[ http://issues.apache.org/jira/browse/OFBIZ-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12461719 ]

Iain Fogg commented on OFBIZ-584:
---------------------------------

Jacopo,

Thanks for diving in a pointing Scott at the appropriate screens.

David,

I completely agree that providing more intelligence in the PO creation process would be very helpful, especially for larger businesses. I can just about cope with the amount of manual intervention required, but in the not too distant future I can see the need for some of the rules you suggest.

The idea of consolidating POs (or SOs, I guess) came mainly because I end up having multiple small POs for some of my suppliers. However, I also run into the opposite problem. For my larger suppliers, I will often have a 100 or more requirements built up. Since the "Approved Requirements" screen paginates the requirements, I'll end up generating multiple orders for the same (large) supplier, simply because the application operates a page at a time. This annoys my suppliers a bit.

I guess the obvious thing to do is to go in and reconfigure the pagination so it doesn't (paginate), but if we had the ability to add items to existing POs then you could still use the pagination mechanism and build up the PO page-by-page (quite handy if your working through your POs during less busy times of the day).