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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0014082
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] B. User interfacemajoralways2010-07-28 20:582012-04-26 15:33
ReporterelopioView Statuspublic 
Assigned Toalostale 
PriorityurgentResolutionout of dateFixed in Version
StatusclosedFix in branchpiFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0014082: 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.
TagsNo tags attached.
Attached Filesxml file icon Format.xml [^] (3,087 bytes) 2010-07-28 20:58
png file icon oracle.png [^] (4,293 bytes) 2010-07-28 20:58


png file icon postgresql.png [^] (4,693 bytes) 2010-07-28 20:58

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0010379 closedrafaroda Openbravo ERP Number formats in grid are not the same in oracle and postgresql 
blocks defect 0014112 closedelopio QA Do the goods shipment line verification on CompleteWarehouseOrder 

-  Notes
(0029651)
elopio (reporter)
2010-07-28 20:59

Priority set to high because having two different behaviors require to maintain two different versions of automated smoke test.

- Issue History
Date Modified Username Field Change
2010-07-28 20:58 elopio New Issue
2010-07-28 20:58 elopio Assigned To => dbaz
2010-07-28 20:58 elopio File Added: Format.xml
2010-07-28 20:58 elopio File Added: oracle.png
2010-07-28 20:58 elopio File Added: postgresql.png
2010-07-28 20:59 elopio Relationship added related to 0010389
2010-07-28 20:59 elopio Note Added: 0029651
2010-07-28 21:03 elopio Relationship deleted related to 0010389
2010-07-28 21:03 elopio Relationship added related to 0010379
2010-08-02 08:10 alostale Assigned To dbaz => alostale
2010-08-02 08:10 alostale Status new => scheduled
2010-08-02 08:10 alostale fix_in_branch => pi
2010-08-02 18:13 elopio Relationship added blocks 0014112
2012-04-26 15:33 alostale Status scheduled => closed
2012-04-26 15:33 alostale Resolution open => out of date


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker