Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 03. Procurement managementminoralways2010-03-06 08:322011-07-22 11:32
ReporterbalamuruganView Statuspublic 
Assigned Tobalamurugan 
PriorityhighResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSLinux 32 bitDatabasePostgreSQLJava version1.6.0_18
OS VersionProfessional ApplianceDatabase version8.3.9Ant version1.7.1
Product VersionSCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0012581: In Purchase/Sales Order Lines tab, while editing Line Net Amount, it is changed when we save.

DescriptionIn Purchase/Sales Order Lines tab, the user entered Line Net Amount value got changed when we save the order lines.
Steps To Reproduce1. Go to Sales Management || Transactions || Sales Order || Header >> Lines tab
2. Select any product, and enter the following values.
  - Ordered Quantity=7
  - Now, the remaining fields like Net Unit Price, Net Standard price. etc., are populated as per the setup.
  - check the Edit Line Net Amount field and change the value of Line Net Amount to 45.33
  - Please realize that the Net Unit Amount is changed based on the Line Net Amount entered.
  - click Save.
  - Now, realize that Line Net Amount is changed to 45.36
Proposed SolutionMerge all c_orderlineX_trgX triggers into one only trigger.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks defect 0012582 closedbalamurugan "Line Net Amount is not Correct" Error message is displayed when we try to save any Purchase/Sales Invoice Line 

-  Notes
dalsasua (reporter)
2010-03-08 08:47

This is what I reported in issue 12495: that trigger is not working, and value is changed...
After debuging, I see that the problem is that when trigger c_orderline_trg3 is executed, it is already provided the changed value. Another trigger is acting on the table before the c_orderline_trg3 acts... My assumption is that this line:
new.LineNetAmt := ROUND(new.QtyOrdered*new.PriceActual, v_Prec);-- Modified by I.Ciordia
in the c_orderline_trg trigger is the one failing.
I change the proposed solution to merge all c_orderline_trgX triggers into one only trigger, where order in which statements are executed are not random, as it happens with different triggers for the same table.
psarobe (manager)
2011-07-22 11:32

It is working fine

- Issue History
Date Modified Username Field Change
2010-03-06 08:32 balamurugan New Issue
2010-03-06 08:32 balamurugan Assigned To => adrianromero
2010-03-06 09:15 balamurugan Assigned To adrianromero => dalsasua
2010-03-06 09:16 balamurugan Relationship added blocks 0012582
2010-03-08 08:29 dalsasua Assigned To dalsasua => balamurugan
2010-03-08 08:47 dalsasua Note Added: 0025107
2010-03-08 08:50 dalsasua Proposed Solution updated
2011-07-22 11:32 psarobe Note Added: 0039328
2011-07-22 11:32 psarobe Status new => closed
2011-07-22 11:32 psarobe Resolution open => no change required

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker