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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0002539
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] C. Securityminoralways2008-01-22 11:232008-06-19 09:50
ReporterpsarobeView Statuspublic 
Assigned Touser71 
PrioritynormalResolutionfixedFixed in Version2.40alpha-r2
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0002539: It can be changed the Organization in Processed Documents

DescriptionAlthough the documents are processed, it is possible to change the organization of these documents.

The organization can be changed in the header of the documents and in the lines as well.

The solution is to add this code:

OR(COALESCE(:old.AD_ORG_ID, '0') <> COALESCE(:new.AD_ORG_ID, '0'))

in the triggers

This happens in tables:

C_ORDER
C_ORDERLINE
M_INOUT
M_INOUTLINE
C_INVOICE
C_INVOICELINE
M_INVENTORY
M_MOVEMENT
GL_JOURNAL
GL_JOURNALLINE
A_AMORTIZATION
C_BANKSTATEMENT
C_BANKSTATEMENTLINE
C_CASH
C_CASHLINE
C_REMITTANCE
C_REMITTANCELINE
C_SETTLEMENT
C_DP_MANAGEMENT
C_DP_MANAGEMENTLINE
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
depends on backport 0003610 closeduser71 It can be changed the Organization in Processed  

-  Notes
(0003075)
user71
2008-01-24 19:12
edited on: 2008-06-12 09:24

 Logged In: YES
user_id=1964080
Originator: NO

The client as well, can not be changed
(the restriction is applied in application level, but not in database level)

The solution is to add this code in triggers:

OR(COALESCE(:old.AD_ORG_ID, '0') <> COALESCE(:new.AD_ORG_ID, '0'))
OR(COALESCE(:old.AD_CLIENT_ID, '0') <> COALESCE(:new.AD_CLIENT_ID, '0'))
(0003076)
user71
2008-01-25 11:59
edited on: 2008-06-12 09:24

 Logged In: YES
user_id=1964080
Originator: NO

To avoid an error, in coalesce function a numeric value must appear instead of a String

OR COALESCE(:old.AD_ORG_ID, 0) <> COALESCE(:new.AD_ORG_ID, 0)
OR COALESCE(:old.AD_CLIENT_ID, 0) <> COALESCE(:new.AD_CLIENT_ID, 0)
(0003077)
user71
2008-05-06 12:13
edited on: 2008-06-12 09:24

 Logged In: YES
user_id=1964080
Originator: NO

Resolved in revision 2272 in the trunk
(0006128)
user71
2005-06-01 00:00
edited on: 2008-06-12 09:43

 This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1877138 [^]

- Issue History
Date Modified Username Field Change
2008-06-19 09:50 psarobe Status resolved => closed

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker