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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0023684
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 02. Master data managementminorhave not tried2013-04-30 10:532013-05-08 09:06
ReporterucayquoteView Statuspublic 
Assigned Todmiguelez 
PrioritynormalResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSWindowsDatabasePostgreSQLJava version1.6.0_35
OS VersionSeven 64bitDatabase version8.4.13Ant version1.8.4
Product Version3.0MP19.3SCM revision 
Review Assigned To
Web browserGoogle Chrome
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0023684: Cannot use the UOM Conversion in sales order

DescriptionAlready followed the instruction to use UOM Conversion, but it still didn't work.
http://wiki.openbravo.com/wiki/ERP_2.50:Configure_Products#Conversions [^]
http://www.wirabumisoftware.com/en/configopenbravoerp/15-productmultyuom- [^]


First, UOM in Sales Order Lines always disabled.
So I can't use for uom conversion
(I don't know what is to be configured first, because there're no more detail instruction for OB3, so i used the 2.50 configuration)

After enable the UOM in the Sales Order Lines, then change the UOM in the SO, i got an error

Error
Saving failed. Unit of Measure mismatch (product/transaction)
Steps To Reproduce- Add the UOM >> Pieces(12) and TEST
- Add the conversion in TEST, converted to Pieces(12) with multipy=12
- Add the product with the name TEST, and set the UOM to Pieces(12)
- Make the Sales Order, create lines.
- Choose the TEST product (default UOM is Pieces(12)).
- Change the UOM to TEST
- got an error >> Saving failed. Unit of Measure mismatch (product/transaction)
Proposed SolutionMake the detailed instructions for UOM Conversion in OB3 if there're additional configuration beside of the 2.50 config.
TagsNo tags attached.
Attached Filesjpg file icon ob-issue-uom conversion.jpg [^] (324,079 bytes) 2013-04-30 10:53

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0058473)
dmiguelez (developer)
2013-05-06 18:23

Hi,

This is not an Issue, but a problem while configuring the UOM's.
First, in the Product Window, in the UOM Tab, only the secondary UOM is needed, it does not make sense to include the same UOM that is also defined in the header, in your case Pieces(12)

Second, in the Sales Order, there are two fields that are hidden by default, 'Order UOM' and 'Order Quantity', it is needed to show them.

Lastly, when creating the Sales Order, in the More Information section those fields will be shown. UOM field is read only, so you should select the secondary UOM and set a quantity, afterwards the Order amount for the principal UOM will be updated according to the conversion rate.

More information can be found in our forums:
http://forums.openbravo.com/ [^]

Regards.
(0058496)
ucayquote (reporter)
2013-05-08 09:06

thanks for the explanation dmiguelez

- Issue History
Date Modified Username Field Change
2013-04-30 10:53 ucayquote New Issue
2013-04-30 10:53 ucayquote Assigned To => dmiguelez
2013-04-30 10:53 ucayquote File Added: ob-issue-uom conversion.jpg
2013-04-30 10:53 ucayquote Web browser => Google Chrome
2013-04-30 10:53 ucayquote Modules => Core
2013-04-30 10:53 ucayquote Triggers an Emergency Pack => No
2013-05-01 07:48 ucayquote Issue Monitored: ucayquote
2013-05-06 18:23 dmiguelez Note Added: 0058473
2013-05-06 18:23 dmiguelez Status new => closed
2013-05-06 18:23 dmiguelez Resolution open => no change required
2013-05-08 09:06 ucayquote Note Added: 0058496


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker