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

PDF Books
Show collection (0 pages)
Collections help




As shown in the image above a "Costing Rule" can be defined and assigned to an organization for which the cost of the transactions need to be calculated.

There can only be one rule valid at a time for an organization which besides needs to be a "Legal Entity" organization type. The valid time period of the costing rule is set by the Starting Date entered.

Once assigned the costing rule applies to every product transaction recorded on the Legal Entity and all its children.

The main property to set in a costing rule is the Costing Algorithm to used while calculating costs.
The Standard and the Average algorithms are available by default. Additional algorithms such as FIFO, LIFO can be implemented by extension modules.

Moreover, costs are calculated at organization level by default, however it is also possible to have the costs calculated for each Warehouse's organization.
This can be achieved by using the Warehouse Dimension flag of the costing rule.

Costing rules need to be validated to start using them. That is done by using the button "Validate Costing Rule".
Once a Costing Rule is validated it is not possible to modify or delete it.
If a costing rule needs to be change that is get by creating a new costing rule with the new setup required.

Let's imagine that an organization requires a new costing algorithm to be used for cost calculation. In that case a new costing rule needs to be created.
The new rule overwrites the existing one starting from a new and later "Starting Date".
In this case:

The closing and initialization inventory balances are managed as Physical Inventories in the new costing engine.
Two physical inventories are created for each organization and warehouse the costing rule applies to:

The costing rule validation process does several checks:

Fix Backdated Transactions

As already described a costing rule can also define whether backdated transactions booked for a product need to be fixed therefore the corresponding backdated transaction cost adjustment are created and booked for that product in order to get the correct cost of the product.

To make this work, one of the following two actions can be taken:

  1. use an existing and validated Costing Rule.
    This way fix backdated transactions feature gets activated by using the process button "Fix Backdated Transactions".
    This option allows entering a "Fix Backdated From" date as starting date, before running the process.
  2. create and validate a new Costing Rule.
    This way fix backdated transactions feature gets activated by checking Backdated Transactions Fixed check-box and filling in a Fix Backdated From date before validating the costing rule.

Both ways:

Retrieved from ""

This page has been accessed 418 times. This page was last modified on 28 October 2014, at 09:30. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.