View source | View content page | Page history | Printable version   
Main Page
Upload file
What links here
Recent changes

PDF Books
Show collection (0 pages)
Collections help


Projects:Average Cost Per Invoice Price/User Documentation

Warning.png   This document is still a work in progress. It may contain inaccuracies or errors.


Average Cost Per Invoice Price - User documentation



This module provides the user with an algorithm for the new Costing Engine that calculates the cost of the Products based on the Average Invoice price.


The Openbravo instance must be in a MP that supports the new Costing Engine.

Note. This manual assumes that the Openbravo instance has been migrated to the new Costing Engine. If it is not the case, please migrate the instance first, before continue any further.


As System Administrator the user can access to the window General Setup || Application || Module Management. There is possible to install new modules by clicking on Add Modules.

Search for this module, named Average Cost Per Invoice Price and install it. The system must be rebuilt after.


Once the module has been installed, the new Costing Algorithm has been created, but it has not been assigned yet to the Costing Process. To do so, the Client Administrator should go to the window Master Data Management || Product Setup || Costing Rules and create a new Costing Rule.

Click on Validate the Costing Rule to finish the setup. Now the next time that the Costing Process is run, this Costing Rule will be used, and therefore, the new costing Algorithm.



On Voiding and Reactivating Invoices

Once an Invoice is completed, the Costing Engine will calculate the cost of the Product using the Average Cost per Invoice Price. Since the cost calculated per each transaction can not be deleted once it has been processed, any changes in that Invoice will not be reflected in the cost of the Product.

This means that reactivating an Invoice, or voiding it and creating a new one, will not trigger a recalculation of the cost of the Product.

For example. An Invoice is created and completed. Therefore the cost of the Product will be recalculated based on this transaction. Then the Invoice is reactivated and the price of the Product is changed. This change will not affect the calculated cost of the Product, because this transaction was already processed by the Costing Algorithm.

On Goods Receipt not totally invoiced

This algorithm calculates the cost of a Product based on the Invoice price. Therefore is needed that each Goods Receipt of a Product has an Invoice associated.

If that is not the case, the Costing Engine will stop calculating the cost of that Product when it finds a transaction without an Invoice associated. And it will not continue until then.

For example. The user has five transactions, for one to five, order chronologically. But the third one does not have an Invoice yet. The Costing Engine will start calculating the cost of the Product using transactions one and two. But it will stop on the third one, and it will not calculate four and five either, until an Invoice is created for the third transaction.

Retrieved from ""

This page has been accessed 2,374 times. This page was last modified on 14 June 2012, at 10:15. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.