Posted by
Si Chen-2 on
URL: http://ofbiz.116.s1.nabble.com/OFBiz-Users-Automatic-Purchasing-tp136301p136304.html
Chris,
Christopher Farley wrote:
>Si Chen (
[hidden email]) wrote:
>
>
>
>>It would be nice to have some automated purchase order creation.
>>
>>But, how is "Purchase orders will be automatically created, and the user
>>can approve them or cancel them" going to be really different than
>>"Requirements are automatically created, and the user can create
>>purchase orders from them or cancel them"? Might you be writing a lot of
>>code to support essentially the same business process.
>>
>>
>
>I could use requirements, but I would need to make the following
>enhancements to OFBiz:
>
> 1. Create a screen to automatically generate requirements from
> current inventory values: for each item with an ATP less than the
> minumumQuantity, create a new requirement. The quantity of this
> requirement is reorderQuantity - ATP. This screen should allow
> the user to limit automatic requirement generation by
> supplier, product SKU range, product category, etc.
>
>
>
This is already done automatically when you set the requirement enum for
your products, so you can re-use those services on your screen. This
shouldn't be too hard.
> 2. Improve the Approve Requirements process. A lot of businesses have
> thousands, or even tens of thousands of SKUs, and there needs to be
> a way to approve and reject requirements en masse. My idea would
> be to list all requirements on a single screen so they can be
> selected with a check box. Include buttons to Select All/Deselect
> All. Finally, you need a way to either approve or reject the selected
> requirements.
>
>
>
That is a good idea. Not too hard to implement either using
"service-multi" and multi forms.
> 3. For adding requirements to purchase orders: the Requirement List
> should only show requirements that contain products that are valid
> for the current Supplier. You would need to "SELECT * FROM requirement
> WHERE product_id IN (SELECT product_id FROM supplier_product WHERE
> party_id = ?)"
>
>
>
Good idea again. It would require adding some code to the screen for
purchase orders.
> 4. Currently, when you try and put a requirement on a purchase order,
> and the quantity is less than the supplier's minimum order qty, you
> get an error: "SupplierProduct not found". This needs to be fixed.
> Idea: Next to the "Submit Button" on the Requirement List, include
> a checkbox that says "Increase Quantities to Match Supplier's
> Minimum Order Quantities".
>
>
>
Maybe it's better to figure out what the minimum quantity is and put it
in there or at least show the user what that is?
>This would not necessarily require a "Primary Supplier" to be defined.
>
>
>
You're right.
>Maybe this would be easier than what I proposed earlier. My other
>solution could have been a stand-alone application, whereas enhancing the
>requirements involves mucking with existing OFBiz code/applications.
>I'm somewhat comfortable creating a stand-alone app, but moderately
>fearful of enhancing existing OFBiz code.
>
>
>
Yes, most people feel that way at first. But longer term it's better for
you to enhance the existing application because -
1. You can upgrade more easily over time. Having stranded orphan
features that are incompatible with new versions of OFBiz is no
fun--believe me, I know from first hand experience.
2. You'll get more familiar with OFBiz and be more able to customize it
in the future.
3. If you contribute stuff back, others can help you develop, debug, and
maintain your work.
Anyway, sounds like you have some great ideas. Let me know if you need
any help with them.
Si
_______________________________________________
Users mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/users