Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0011940Openbravo ERP02. Master data managementpublic2010-01-12 16:102010-03-10 18:28
Reporternetworkb 
Assigned Toadrianromero 
PriorityhighSeverityminorReproducibilityalways
StatusclosedResolutionno change required 
PlatformOS5OS Version
Product Version2.50MP9 
Target Version2.50MP14Fixed 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
Summary0011940: Import order creates uncorrect dates
DescriptionWhen a POS order is imported an order, good shipment/receipt and invoice is created. In all of them, same dates contains 00:00:00 hour. Date is correct but not the hour.

Here you are the list of uncorrect fields:

C_Order: DateOrdered, DatePromised, DateAcct
C_Invoice: DateInvoiced, DateAcct, DateOrdered
M_InOut: DateOrdered, MovementDate
C_Debt_Payment: DatePlanned
Steps To ReproduceNote: to be able to reproduce this bug, this bug 0011926 must be applied first.

Same steps as 0011926.

See C_Order, C_Invoice, M_InOut and C_Debt_Payment tables (ORDER BY CREATED DESC).
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to defect 00118012.50MP11 closed harikrishnan Invoice date and Movement date are not correct when a POS order is imported 
related to defect 00119262.50MP11 closed harikrishnan Import Order creates uncorrect documentno and Date invoice 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-01-12 16:10networkbNew Issue
2010-01-12 16:10networkbAssigned To => rafaroda
2010-01-12 16:34rafarodaRelationship addedrelated to 0011926
2010-01-12 16:35rafarodaRelationship addedrelated to 0011801
2010-01-13 11:07rafarodaPriorityimmediate => high
2010-01-13 11:07rafarodaStatusnew => scheduled
2010-01-13 11:07rafarodaversion2.50MP13 => 2.50MP9
2010-01-13 11:07rafarodaTarget Version2.50MP9 => 2.50MP13
2010-02-11 11:07rafarodaAssigned Torafaroda => adrianromero
2010-02-25 12:05psarobeNote Added: 0024813
2010-02-25 12:05psarobeStatusscheduled => closed
2010-02-25 12:05psarobeResolutionopen => no change required
2010-02-25 13:04networkbNote Added: 0024816
2010-02-25 13:17psarobeNote Added: 0024817
2010-02-26 00:00anonymoussf_bug_id0 =>
2010-03-08 16:05jpabloaeTarget Version2.50MP13 => 2.50MP14
2010-03-10 18:28anonymoussf_bug_id => 2967974

Notes
(0024813)
psarobe   
2010-02-25 12:05   
This is not a bug. The ERP is working fine.

1. The dates are defined in the AP with the reference DATE for I_ORDER table and for the other ones
2. With that reference the time is not calculated
3. There two difference in Oracle and postgres:
  3.1 In postgres date columns are defined as timestamp without time zone, meaning that the dates are always as for example 24/02/2010 0:00:00. If you create a sales order through the UI you can double check
  3.2 In Oracle date columns are defined as date so no time is recording

But if for example in the AP you define those columns as DATE/TIME you will record the time
(0024816)
networkb   
2010-02-25 13:04   
Pablo,

This is not true. In postre, if you create an invoice manually, hour is set.

I have created an invoice manually, and this are dates:

'2010-02-25 13:04:25.791967'

Please reopen the bug
(0024817)
psarobe   
2010-02-25 13:17   
Natalia,

But not if you create manually the sales order. Since the goods shipment, and sales invoice is created automatically based on that sales order (POS) the dates for those documents are with 0:00:00.

And this is correct. Remember that the flow is:

I_ORDER (0:00:00) --> C_ORDER (0:00:00).....


Finished