Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0022839Openbravo ERP09. Financial managementpublic2013-01-18 11:152013-02-20 17:27
Reporterjonalegriaesarte 
Assigned ToioritzCia 
PriorityhighSeveritymajorReproducibilityhave not tried
StatusnewResolutionopen 
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
Summary0022839: GL posting by DB tables does not take into consideration the organization
DescriptionGL posting by DB tables does not take into consideration the organization. If the background process is running to one organization, but the user performs this process to other organization, the process fails
Steps To Reproduce- Unschedule accounting process defined in *
- Perform GL posting by DB, selecting one organization. Process works fine
- Schedule accounting process to organization F&B España - Región Norte
- Perform GL posting by DB, selecting other organization. Error appears: This task cannot be executed while background process is active
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2013-01-18 11:15jonalegriaesarteNew Issue
2013-01-18 11:15jonalegriaesarteAssigned To => jonalegriaesarte
2013-01-18 11:15jonalegriaesarteModules => Core
2013-01-18 11:15jonalegriaesarteTriggers an Emergency Pack => No
2013-02-14 11:09ioritzCiaNote Added: 0056434
2013-02-14 11:09ioritzCiaTypedefect => design defect
2013-02-20 17:27jonalegriaesarteAssigned Tojonalegriaesarte => ioritzCia
2013-02-20 17:27jonalegriaesarteTarget Version3.0MP21 =>

Notes
(0056434)
ioritzCia   
2013-02-14 11:09   
Changed to design defect.

Launching accounting twice could and eventually would involve into simultaneous transactions over the same table in database. This could cause table blocking. Due to this, the change would require a deep analysis of this problem. For this reason this issue is moved to design defect.