Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013021Openbravo ERP09. Financial managementpublic2010-04-16 12:312010-04-21 10:32
Reporternetworkb 
Assigned Toadrianromero 
PriorityimmediateSeveritymajorReproducibilityalways
StatusclosedResolutionduplicate 
PlatformOS5OS Version
Product Version2.40MP12 
Target Version2.40MP13Fixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customerOBPS
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0013021: When you process a cash journal the database is not updated properly
Description-As Openbravo Admin go to General Setup || Security || User
-Create a new record:
    -name: User
    -username: User
    -password: user
-Save, go to User Roles and create a new record:
    -Role: Openbravo Admin.
-Save

-Go to Financial Management || Receivables & Payables || Transactions || Cash Journal
-Create a new cash journal with a line.
-Save

-Logout and login with the new user.
-Go to the cash journal created and process it.

-On DB:

select updatedby, updated, createdby, created from c_invoice order by updated desc

-Realize that '100' (Openbravo user) appears on UpdatedBy
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
duplicate of defect 00130232.40MP13 closed harikrishnan When completing or processing documents the updatedby column is not updated properly 
related to defect 00125202.40MP13 closed harikrishnan When you complete a sales invoice the database is not updated properly 
depends on backport 00130222.40MP13 closed dalsasua When you process a cash journal the database is not updated properly 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-04-16 12:31networkbNew Issue
2010-04-16 12:31networkbAssigned To => dalsasua
2010-04-16 12:31networkbOBNetwork customer => Yes
2010-04-16 12:31networkbRelationship addedrelated to 0012520
2010-04-16 12:42adrianromeroStatusnew => scheduled
2010-04-16 12:42adrianromerofix_in_branch => pi
2010-04-16 12:43adrianromeroIssue cloned0013022
2010-04-16 12:43adrianromeroRelationship addeddepends on 0013022
2010-04-16 15:34adrianromeroRelationship addedduplicate of 0013023
2010-04-16 15:34adrianromeroNote Added: 0026316
2010-04-16 15:34adrianromeroStatusscheduled => closed
2010-04-16 15:34adrianromeroResolutionopen => duplicate
2010-04-17 00:00anonymoussf_bug_id0 => 2988607
2010-04-20 18:23networkbAssigned Todalsasua => adrianromero
2010-04-20 18:23networkbStatusclosed => new
2010-04-20 18:23networkbResolutionduplicate => open
2010-04-20 18:24networkbPriorityurgent => immediate
2010-04-20 18:24networkbfix_in_branchpi =>
2010-04-21 10:32networkbStatusnew => closed
2010-04-21 10:32networkbResolutionopen => duplicate

Notes
(0026316)
adrianromero   
2010-04-16 15:34   
This issue is included in 13023