Openbravo Issue Tracking System - Openbravo ERP | ||||||||||||
View Issue Details | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
0031606 | Openbravo ERP | 09. Financial management | public | 2015-11-26 18:17 | 2015-11-26 18:17 | |||||||
Reporter | vmromanos | |||||||||||
Assigned To | Triage Omni OMS | |||||||||||
Priority | normal | Severity | major | Reproducibility | always | |||||||
Status | new | Resolution | open | |||||||||
Platform | OS | 5 | OS Version | |||||||||
Product Version | ||||||||||||
Target Version | Fixed in Version | |||||||||||
Merge Request Status | ||||||||||||
Review Assigned To | ||||||||||||
OBNetwork customer | ||||||||||||
Web browser | ||||||||||||
Modules | Core | |||||||||||
Support ticket | ||||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0031606: Acct Server Background process and context organization | |||||||||||
Description | Right 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 Reproduce | NA | |||||||||||
Proposed Solution | A 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. | |||||||||||
Additional Information | ||||||||||||
Tags | No tags attached. | |||||||||||
Relationships |
| |||||||||||
Attached Files | ||||||||||||
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 |
There are no notes attached to this issue. |