You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Sumit Pandit (JIRA)" <ji...@apache.org> on 2009/08/06 09:06:15 UTC

[jira] Updated: (OFBIZ-1742) Implementation of a service to compute the product average cost

     [ https://issues.apache.org/jira/browse/OFBIZ-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sumit Pandit updated OFBIZ-1742:
--------------------------------

    Attachment: ProdAverageCost.patch

Here in attached patch(ProdAverageCost.patch), a service which is invoked on receive Inventory (receiveInventoryProduct) service, it expires existing ProductAverageCost value, recalculate the average cost and create a new one.

> Implementation of a service to compute the product average cost
> ---------------------------------------------------------------
>
>                 Key: OFBIZ-1742
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1742
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: accounting, product
>    Affects Versions: SVN trunk
>            Reporter: Rashko Rejmer
>            Assignee: Jacques Le Roux
>            Priority: Minor
>             Fix For: SVN trunk
>
>         Attachments: averageCostScreen.patch, ProdAverageCost.patch, ProductAverageCostEntity.patch
>
>
> Based on:
> http://markmail.org/message/shcyetdwusggu6eo
> Jacopo Cappelato says:
> "I have to implement a service that computes the inventory average cost of a product (based on current QOH and inventory items' unit costs) and stores it somewhere...
> Do you think that storing it in the ProductAverageCost entity is a good idea?
> However I think that it is important to give the ability to maintain a separate cost for each facility (for example the items in a facility in US and the ones in a facility in China could have very different inventory costs); the key of the ProductAverageCost is now composed by productId, organizationPartyId, fromDate so I think we should add to it also the facilityId and possibly a productAverageCostTypeId field (to maintain different types of averages)....
> ... and run the service (probably as a seca) every time a product is received/shipped/etc... (i.e. everytime the qoh of a product changes); the result of the service call could be stored in the ProductAverageCost entity."

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.