Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0042875Openbravo ERP09. Financial managementpublic2020-01-14 18:412020-01-20 10:49
Reporterdmiguelez 
Assigned ToTriage Omni OMS 
PrioritylowSeveritytrivialReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
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
Summary0042875: Accounting process in Sample Data should not be scheduled at system level
DescriptionAccounting process in Sample Data should be scheduled at Client level.
If a client installs Sample Data, but they are not going to use accounting, the background process should not be automatically scheduled.
Steps To ReproduceLog in as F&B Admin
Go to process request window
Check that there is a record for Accounting Process Background scheduled at System level.
Proposed SolutionLog in as F&B Admin
Go to process request window
Check that there is a record for Accounting Process Background scheduled at client level.
Additional Information
TagsNo tags attached.
Relationships
Attached Filesdiff 42875.diff (11,245) 2020-01-20 10:49
https://issues.openbravo.com/file_download.php?file_id=13870&type=bug
Issue History
Date ModifiedUsernameFieldChange
2020-01-14 18:41dmiguelezNew Issue
2020-01-14 18:41dmiguelezAssigned To => Triage Finance
2020-01-14 18:41dmiguelezModules => Core
2020-01-14 18:41dmiguelezTriggers an Emergency Pack => No
2020-01-20 10:49dmiguelezNote Added: 0117055
2020-01-20 10:49dmiguelezFile Added: 42875.diff

Notes
(0117055)
dmiguelez   
2020-01-20 10:49   
The proposed solution (attached) is to remove this process request at System level and create it at client level.

However, this will result in an API change, because there can be objects related to this process request already.

Also, from a functional point of view, if there is any client that relies on this process to calculate accounting, is a functional API change too.

That is the reason why this issue is not going to be solved right now.