Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0034106Openbravo ERP09. Financial managementpublic2016-09-27 17:352016-09-30 19:07
Reporterplujan 
Assigned ToSanjota 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Versionpi 
Target VersionFixed in Version3.0PR16Q4 
Merge Request Status
Review Assigned Toaferraz
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0034106: Missing allowed value in Material Management DB table for Posted field
DescriptionWhen an accounting schema has material management table set as not active, posted shipments take this status with the value='T' in the m_inout table. However, the list of valid values for this list does not include 'T', generating an error in the consistency tests

Exception when parsing entity MaterialMgmtShipmentInOut (0D165FB59B1345EABDE76B76B93E9EE6):posted: Property MaterialMgmtShipmentInOut.posted, value (T) is not allowed, it should be one of the following values: [D, E, d, b, c, C, p, N, Y, NC, y, i] but it is value T
Steps To ReproduceSet MaterialMgmtShipmentInOut entity as not active in the General Ledger Configuration window and run the Accounting Server Process.
Proposed SolutionThere are actually two threads to fix. One, straightforward, is to add the value T to the list of allowed values for the reference list.
The other, more complex, is to identify why this checks job has started failing in recent days. It might be related with this changeset: https://code.openbravo.com/erp/devel/pi/rev/df9155c88ab2 [^]
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2016-09-27 17:35plujanNew Issue
2016-09-27 17:35plujanAssigned To => Triage Finance
2016-09-27 17:35plujanModules => Core
2016-09-27 17:35plujanRegression level => Pre packaging ( pi )
2016-09-27 17:35plujanTriggers an Emergency Pack => No
2016-09-27 17:37ngarciaIssue Monitored: ngarcia
2016-09-28 10:14aferrazRegression levelPre packaging ( pi ) =>
2016-09-29 19:04hgbotCheckin
2016-09-29 19:04hgbotNote Added: 0090390
2016-09-29 19:04hgbotStatusnew => resolved
2016-09-29 19:04hgbotResolutionopen => fixed
2016-09-29 19:04hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/42610ad2d4b903366ebf3752a65af7d8e2394443 [^]
2016-09-29 19:05aferrazAssigned ToTriage Finance => Sanjota
2016-09-29 19:05aferrazReview Assigned To => aferraz
2016-09-29 19:05aferrazNote Added: 0090391
2016-09-29 19:05aferrazStatusresolved => closed
2016-09-29 19:05aferrazFixed in Version => 3.0PR16Q4
2016-09-30 19:07hudsonbotCheckin
2016-09-30 19:07hudsonbotNote Added: 0090440

Notes
(0090390)
hgbot   
2016-09-29 19:04   
Repository: erp/devel/pi
Changeset: 42610ad2d4b903366ebf3752a65af7d8e2394443
Author: Sanjota <sanjota.nelagi <at> promantia.com>
Date: Wed Sep 28 14:25:07 2016 +0530
URL: http://code.openbravo.com/erp/devel/pi/rev/42610ad2d4b903366ebf3752a65af7d8e2394443 [^]

Fixes issue 34106: Created Missing references in m_inout table for Posted field

Added missing reference in posted reference list to avoid the exception while parsing m_inout record.

---
M src-db/database/sourcedata/AD_REF_LIST.xml
---
(0090391)
aferraz   
2016-09-29 19:05   
Code review + Testing OK
(0090440)
hudsonbot   
2016-09-30 19:07   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/538700cbd709 [^]
Maturity status: Test