Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0030277
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 04. Warehouse managementmajoralways2015-06-29 13:352015-07-16 11:51
ReporterpsanjuanView Statuspublic 
Assigned ToTriage Omni WMS 
PriorityurgentResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revisionno change
ProjectionnoneETAnoneTarget Version
OSLinux 32 bitDatabaseOracleJava version1.6
OS VersionUbuntu 8.04.1Database version11.1.0.6.0Ant version1.7.0
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0030277: Changing from an average costing rule to a standard costing rule is not working properly.

DescriptionChanging from an average costing rule to a standard costing rule is not working properly, because it does not take into account the standard cost defined but the price list defined for (*) organization.
Steps To ReproduceRun Initial organization setup to create a new organization named "AV to ST Org". Currency = EUR. Set is as Ready.

Go to Open/Close Period Control window and open all periods for the organization.

Go to Warehouse window and create a new one for the organization.
Assign this warehouse to the organization in "organization" window, warehouse tab.

Define a Purchase Price list at (*) level named "Purchase Price List"

Go to Costing rule window and create a new one for this organization by entering below setup:
Costing Algorithm= Average Algorithm
Starting Date = 01-01-2015
Backdated Transactions Fixed = Yes

Validate costing rule

Go to product window and create a new one named "Producto Asterisco" defined at * Org level.

Go to Price tab and select the price list (*) "Purchase Price List" and enter 125.00 as unit price/List price.

Go to Costing tab and manually enter a new record with below setup:
Organization = AV to ST Org
Cost Type = Average
Cost = 100
Starting date = 01-01-2015
Ending Date = 31-12-9999
Manual = Yes
Check that Warehouse field remains empty.

Navigate to purchase order and create an order for AV to ST Org dated on 29-06-2015, for any vendor, Product = Producto Asterisco, Ordered Qty = 1 unit
Complete the order

Go to Goods Receipt window and create a new one to receipt this 1 unit of the product, dated on 29-06-2015. Run Costing Background process and post the receipt.

Go back to Product window, Costing tab and realize that for this product, Average cost has changed to 125.00 €, starting from 29-06-2015 to 31-12-9999, which is correct.

Go to Costing Rule window and create a new one for ST to AV Org. This time with below setup:
Costing Algorithm = Standard Algorithm

Validate costing rule.

Go to product window, transaction tab and realize that for this product two new transactions have been created. One Inventory In transaction for the average closing valued at 125.00 which is correct, an another one Inventory In transaction for the Standard opening with no value as no standard cost has been entered for the product.

Run costing background process and run it for this organization. Realize that an error is shown because there is no standard cost defined for this product. This is correct.

Go to product window, costing tab and enter a new record there with below setup:
Organization = AV to ST org
Cost Type = Standard
Cost = 155
Starting Date = 29-06-2015
Ending Date = 31-12-9999
Manual = Yes
Check that warehouse field remains empty.

Run once again costing background process. Openbravo informs that the process completed successfully.

Go to Product window, Costing tab and realize that for this product a new record has been created there with below setup:
Cost Type = Standard
Cost = 125
Starting Date = 29-06-2015
Ending Date = 31-12-9999
Permanent = Yes
Currency = EUR

This is not correct.

Go to product window, transaction tab and realize that for this product Inventory In transaction created for the Standard costing opening is valued at 125.00.

This it is not correct.

The standard cost entered of 155.00 has not been taken into account but 125.00 defined for the price list.

See image attached.



Proposed SolutionThe standard cost entered must be taken into account.
TagsNo tags attached.
Attached Filespng file icon issue_30277.png [^] (91,950 bytes) 2015-06-29 14:01

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0030779 newTriage Omni WMS Costing Rule change from Average to Standard is not working. 

-  Notes
(0078560)
psanjuan (manager)
2015-06-29 14:15

Same behavior if the standard cost entered manually is defined as "Permanent" = Yes.
(0078856)
psanjuan (manager)
2015-07-16 11:50
edited on: 2015-07-16 11:54

Issue closed as no change is required because:

- Create a new Costing Rule with "Average Algorithm" and validate it
- Create a new product
- Set a Purchase and a Sales Price list with price = 5
- Set a new Average cost of 8 to new product
- Create a receipt to this product of 1 unit and complete
- Run Costing Background
- Average cost calculated is 8

- Create a new Costing Rule with "Standard Algorithm" and validate it
- Set a new Standard cost of 12 to new product
- Run Costing Background

Openbravo is not going to take 12 as standard cost but existing cost 8 as standard cost.

If that cost needs to be changed to 12, then it is necessary to run an inventory amount update at a given date, therefore product inventory closes at 8 and gets opened at 12.


- Issue History
Date Modified Username Field Change
2015-06-29 13:35 psanjuan New Issue
2015-06-29 13:35 psanjuan Assigned To => Triage Finance
2015-06-29 13:35 psanjuan Modules => Core
2015-06-29 13:35 psanjuan Triggers an Emergency Pack => No
2015-06-29 14:00 psanjuan Steps to Reproduce Updated View Revisions
2015-06-29 14:00 psanjuan Proposed Solution updated
2015-06-29 14:01 psanjuan File Added: issue_30277.png
2015-06-29 14:15 psanjuan Note Added: 0078560
2015-06-30 10:02 psanjuan Steps to Reproduce Updated View Revisions
2015-06-30 10:08 psanjuan Steps to Reproduce Updated View Revisions
2015-07-16 11:50 psanjuan Note Added: 0078856
2015-07-16 11:50 psanjuan Status new => scheduled
2015-07-16 11:50 psanjuan Resolution open => no change required
2015-07-16 11:50 psanjuan Fixed in SCM revision => no change
2015-07-16 11:51 psanjuan Status scheduled => resolved
2015-07-16 11:51 psanjuan Status resolved => closed
2015-07-16 11:54 aferraz Note Edited: 0078856 View Revisions
2015-09-07 12:59 psanjuan Relationship added related to 0030779


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker