Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014082Openbravo ERPB. User interfacepublic2010-07-28 20:582012-04-26 15:33
Reporterelopio 
Assigned Toalostale 
PriorityurgentSeveritymajorReproducibilityalways
StatusclosedResolutionout of date 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0014082: Number formats in goods shipment link to order are not the same in oracle and postgresql
DescriptionThe identifier that links a goods shipment with a sales order has different format in the amount numbers in oracle and in postgresql.

This applies to goods shipment lines too.

See the attached image.

The format.xml is the same on both installations. I'll attach it too.
Steps To ReproduceComplete a warehouse order.
Go to the linked goods shipment.

This can be done running the test:
http://code.openbravo.com/tools/automation/pi-dbunit/file/tip/src-test/com/openbravo/test/integration/erp/testsuites/guiunit/sales/transactions/salesorder/CompleteWarehouseSalesOrder.java [^]
Proposed SolutionOracle should have the same format shown in postgresql context.
Additional Information
TagsNo tags attached.
Relationships
related to defect 0010379 closed rafaroda Openbravo ERP Number formats in grid are not the same in oracle and postgresql 
blocks defect 0014112 closed elopio QA Do the goods shipment line verification on CompleteWarehouseOrder 
Attached Filesxml Format.xml (3,087) 2010-07-28 20:58
https://issues.openbravo.com/file_download.php?file_id=2807&type=bug
png oracle.png (4,293) 2010-07-28 20:58
https://issues.openbravo.com/file_download.php?file_id=2808&type=bug
png

png postgresql.png (4,693) 2010-07-28 20:58
https://issues.openbravo.com/file_download.php?file_id=2809&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2010-07-28 20:58elopioNew Issue
2010-07-28 20:58elopioAssigned To => dbaz
2010-07-28 20:58elopioFile Added: Format.xml
2010-07-28 20:58elopioFile Added: oracle.png
2010-07-28 20:58elopioFile Added: postgresql.png
2010-07-28 20:59elopioRelationship addedrelated to 0010389
2010-07-28 20:59elopioNote Added: 0029651
2010-07-28 21:03elopioRelationship deletedrelated to 0010389
2010-07-28 21:03elopioRelationship addedrelated to 0010379
2010-08-02 08:10alostaleAssigned Todbaz => alostale
2010-08-02 08:10alostaleStatusnew => scheduled
2010-08-02 08:10alostalefix_in_branch => pi
2010-08-02 18:13elopioRelationship addedblocks 0014112
2012-04-26 15:33alostaleStatusscheduled => closed
2012-04-26 15:33alostaleResolutionopen => out of date

Notes
(0029651)
elopio   
2010-07-28 20:59   
Priority set to high because having two different behaviors require to maintain two different versions of automated smoke test.