Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
0009051Openbravo ERP09. Financial managementpublic2009-05-15 16:442009-07-21 00:00
mtaal 
rafaroda 
urgentminorhave not tried
closedduplicate 
5
pi 
pi 
Core
No
0009051: Finance: Default value in database and application dictionary differ, they need to be the same
See here for a complete listing of the different default values:

Column DocumentType.Sequenced Document: the Application Dictionary and the database have differing default values, AD: Y DB: N
Column FinancialMgmtGLJournal.Rate: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
Column FinancialMgmtGLJournal.Approved: the Application Dictionary and the database have differing default values, AD: Y DB: N
Column FinancialMgmtGLJournalLine.Rate: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
Column FinancialMgmtPaymentTermLine.Rest: the Application Dictionary and the database have differing default values, AD: Y DB: N
Column FinancialMgmtTaxZone.Creation Date: the Application Dictionary and the database have differing default values, AD: Sysdate DB: SYSDATE
Column FinancialMgmtTaxZone.Updated: the Application Dictionary and the database have differing default values, AD: SysDate DB: SYSDATE
Column FinancialMgmtPromissoryFormat.Line 1 Top: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
Column FinancialMgmtPromissoryFormat.Line 1 Left: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
Column FinancialMgmtPromissoryFormat.Line 2 Top: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
Column FinancialMgmtPromissoryFormat.Line 2 Left: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
Column FinancialMgmtPromissoryFormat.Line 3 Top: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
Column FinancialMgmtPromissoryFormat.Line 3 Left: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
Column FinancialMgmtPromissoryFormat.Line 4 Top: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
Column FinancialMgmtPromissoryFormat.Line 4 Left: the Application Dictionary and the database have differing default values, AD: 1 DB: 0
Column FinancialMgmtDPManagement.Updated: the Application Dictionary and the database have differing default values, AD: SysDate DB: SYSDATE
Column FinancialMgmtDPManagementLine.Creation Date: the Application Dictionary and the database have differing default values, AD: Sysdate DB: SYSDATE
Column FinancialMgmtDPManagementLine.Updated: the Application Dictionary and the database have differing default values, AD: SysDate DB: SYSDATE
250mp2
duplicate of feature request 0009968 new iciordia Support default values in AD fields 
blocks defect 0008900pi closed mtaal Inconsistencies between database default values and application dictionary default values 
Issue History
2009-05-15 16:44mtaalNew Issue
2009-05-15 16:44mtaalAssigned To => rafaroda
2009-05-15 16:44mtaalRegression testing => No
2009-05-15 16:52mtaalRelationship addedblocks 0008900
2009-05-15 16:57mtaalPrioritynormal => urgent
2009-05-15 16:57mtaalTag Attached: 250mp2
2009-05-15 18:05rafarodaStatusnew => scheduled
2009-05-15 18:06rafarodaAssigned Torafaroda => mtaal
2009-05-15 19:09mtaalNote Added: 0016397
2009-05-15 19:09mtaalAssigned Tomtaal => rafaroda
2009-07-20 16:11rafarodaRelationship addedduplicate of 0009968
2009-07-20 16:11rafarodaStatusscheduled => closed
2009-07-20 16:11rafarodaNote Added: 0018428
2009-07-20 16:11rafarodaDuplicate ID0 => 9968
2009-07-20 16:11rafarodaResolutionopen => duplicate
2009-07-21 00:00anonymoussf_bug_id0 => 2824521
2016-01-04 18:14shuehnerRelationship addedblocks 0031817

Notes
(0016397)
mtaal   
2009-05-15 19:09   
Hi Rafa,
I can't really say anything about the default values in finance tables. Someone knowledgeable in Finance should solve this one imo.

gr. Martin
(0018428)
rafaroda   
2009-07-20 16:11   
This issue will be addressed by feature request 0009968