Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0034847Openbravo ERP01. General setuppublic2017-01-03 18:522017-01-09 13:41
Reportermalsasua 
Assigned Tomalsasua 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformOS20OS VersionCommunity Appliance
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
Summary0034847: Unhomogeneous behavior when business partner is created: customer and employee accounting defaults
Descriptionwhen a business partner category has not got configured accounting configuration (configuration tab is empty), and a new BP is created using this business partner category, in tab "customer -> accounting" the accounting record are not created, but in tab "employee -> accounting" the accounting records are created
Steps To Reproducein F&B
. go to business partner category window:
 record: Employee
 . delete records in tab "accounting"

. go to business partner window:
 . new record: bp category: Employee
 . go to tab "customer -> accounting" -> it is empty
 . go to tab "employee -> accounting" -> there are two records

error: in the two accounting tabs, the result should be the same: no accounting record should be created
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 0033877 closed AtulOpenbravo Accounting default values not transferred from BP Category to Business Partner if the schema is assigned to a child organization 
related to defect 0032424 closed AtulOpenbravo New Account not created for Business Partner for organization F&B US, Inc. but works with F&B España, S.A 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2017-01-03 18:52malsasuaNew Issue
2017-01-03 18:52malsasuaAssigned To => Triage Finance
2017-01-03 18:52malsasuaModules => Core
2017-01-03 18:52malsasuaTriggers an Emergency Pack => No
2017-01-04 09:58aferrazRelationship addedrelated to 0033877
2017-01-04 10:04aferrazRelationship addedrelated to 0032424
2017-01-09 11:33psanjuanNote Added: 0093252
2017-01-09 11:34psanjuanNote Edited: 0093252bug_revision_view_page.php?bugnote_id=0093252#r14222
2017-01-09 11:37psanjuanNote Added: 0093253
2017-01-09 11:42psanjuanNote Added: 0093254
2017-01-09 11:42psanjuanAssigned ToTriage Finance => malsasua
2017-01-09 11:42psanjuanStatusnew => feedback
2017-01-09 13:41malsasuaStatusfeedback => new
2017-01-09 13:41malsasuaTypedefect => design defect

Notes
(0093252)
psanjuan   
2017-01-09 11:33   
(edited on: 2017-01-09 11:34)
If an Employee business partner is created, related to an Employee business partner category with no ledger accounts configured for it, there will be as many records in Employee-Accounting tab as general ledger configurations.

Therefore if that employee is later on also configured as Customer, for instance, customer - accounting tab will be empty because Employee business partner category did not have any ledger account, in our example.

Above is caused by the fact that employee accounting does not take ledger accounts configured in the business partner category which are related to "Customer" and "Supplier" business partner types.
(0093253)
psanjuan   
2017-01-09 11:37   
Current status of this issue is:
-Waiting for end-customer feedback. As it seems this customer has shown two fields in Employee Accounting tab that are "Employee Expense" and "Employee Prepayment".

- to research how those two fields work if shown normally and base on end-client customization.

Our first take is that this issue is not a bug because there are no Employee related ledger accounts which can be configured by default as part of a business partner category. Besides that we think there is no business logic behind those two fields showed by end-client, unless a customization is implemented.
(0093254)
psanjuan   
2017-01-09 11:42   
Issue status changed to Feedback.