Hi Daniel, thanks for the tips, What I was wondering in my previous mail is why has a supplier role be informed in a product requirement for it to be candidate for a purchase order. IMO a product requirement should always be subject to purchase. Anyway, I have yet to look closer on this.
Daniel Kunkel escribió: > Hi Daniel > > This subject has come up before, and there have been some interesting > ideas... > > One idea that intrigues me, as it is the way I think about making an > order, is if a business would setup a requirements/automatic purchasing > system that would run periodically on a supplier by supplier basis > instead of after every sale on an item by item basis. > >From my experience (small-medium sized production companies) companies purchase when ATP gets low (i.e. for products with regular demand) or by sales order (i.e. for products with peaks on demand). I haven't looked very close on ofbiz capabilities yet but I think it covers most needs. > For example, setup a purchasing scan that runs through all the > suppliers, and looks for items that need to be reordered. It might > eliminate the need for all of the requirements data tables in the > database, and instead could create orders automatically, or on-demand > for any particular supplier. > Well, I like a lot the requirement model of ofbiz because I think it is conceptually clear and very flexible. Also, IMO automatic creation of orders is not a good idea for most companies, I rather like automatic creation of requirements and then let the humans purchase ;). What I miss in ofbiz is to place an order from the requirement screen with the possibility select more than one but this shouldn't be difficult. Also, a planning report (one that shows links between sales/purchases orders and shipments) will be desirable ;). > Additionally, for those companies that like to operate this way, the > orders could easily be adjusted to meet minimum quantity or dollar > values for price breaks or reduce the number of orders you're likely to > need to place with a particular supplier by including items in the order > that you are running lowish on. Rather than just ordering items that > have a strict requirement, you would include items that are relatively > low on. This might save you from needing to place another order as soon, > and would probably cut down on shipping costs, but stocking would be a > little more complicated since the orders would have few numbers of a > larger variety of products. > In other words, if you're already placing an order, why not include some > of the other items that you're running low on. > If I understood well, grouping requirements in an order will cover this. > I believe a system like this might allow a business to reduce > backorders, since most items would usually be reordered before the > inventory actually reaches the minimum. > A previous discussion on the topic. > http://www.mail-archive.com/[email protected]/msg00675.html > > Another thread about combining Requirements, etc. > http://osdir.com/ml/java.ofbiz.user/2005-11/msg00020.html > > Thanks > Regards, -- Daniel Martínez
