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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0031606
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Openbravo ERP] 09. Financial managementmajoralways2015-11-26 18:172015-11-26 18:17
ReportervmromanosView Statuspublic 
Assigned ToTriage Omni OMS 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0031606: Acct Server Background process and context organization

DescriptionRight now (after fixing 0031265), the behavior of the Acct server background process is the following:

1. If the process is scheduled from the System client, then any table which is enabled for background process in any of the acct. schemas for any of the clients in the instance is taken into account.

2. If the process is scheduled inside a concrete client (different from System) and for the * org, then any table which is enabled for background process in any of the acct. schemas for this client is taken into account.

3. If the process is scheduled inside a concrete client (different from System) and for an organization different from *, then the process takes into account the tables that are enabled for the background process in any of the acct. schemas in the natural tree of the organization (parents and children).



It's true that this behavior covers multiple scenarios, but it's not consistent, and can lead to unexpected results depending on the way you configure it.
Steps To ReproduceNA
Proposed SolutionA redesign of AcctServerProcess should be done.

The process should be launched in cascade for the selected organization and its children.

For each of the organizations (scenarios 2. and 3.), the process should take into account the accounting schemas that affect each organization (i.e. the acct schemas defined at its level or any upper level), and for each of them calculate the right tables according to the Disable for Background flag.

For scenario 1., the process should process in cascade all the organizations in each client available in the instance.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 00312653.0PR16Q1 closedaferraz Acct Server Background process should only consider check "Disable for background" option for valid General Ledgers 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2015-11-26 18:17 vmromanos New Issue
2015-11-26 18:17 vmromanos Assigned To => Triage Finance
2015-11-26 18:17 vmromanos Modules => Core
2015-11-26 18:17 vmromanos Triggers an Emergency Pack => No
2015-11-26 18:17 vmromanos Relationship added related to 0031265


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker