Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0011940
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] 02. Master data managementminoralways2010-01-12 16:102010-03-10 18:28
ReporternetworkbView Statuspublic 
Assigned Toadrianromero 
PriorityhighResolutionno change requiredFixed in Version
StatusclosedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version2.50MP14
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product Version2.50MP9SCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0011940: 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).
TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
related to defect 00118012.50MP11 closedharikrishnan Invoice date and Movement date are not correct when a POS order is imported 
related to defect 00119262.50MP11 closedharikrishnan Import Order creates uncorrect documentno and Date invoice 

-  Notes
(0024813)
psarobe (manager)
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 (developer)
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 (manager)
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

- Issue History
Date Modified Username Field Change
2010-01-12 16:10 networkb New Issue
2010-01-12 16:10 networkb Assigned To => rafaroda
2010-01-12 16:34 rafaroda Relationship added related to 0011926
2010-01-12 16:35 rafaroda Relationship added related to 0011801
2010-01-13 11:07 rafaroda Priority immediate => high
2010-01-13 11:07 rafaroda Status new => scheduled
2010-01-13 11:07 rafaroda version 2.50MP13 => 2.50MP9
2010-01-13 11:07 rafaroda Target Version 2.50MP9 => 2.50MP13
2010-02-11 11:07 rafaroda Assigned To rafaroda => adrianromero
2010-02-25 12:05 psarobe Note Added: 0024813
2010-02-25 12:05 psarobe Status scheduled => closed
2010-02-25 12:05 psarobe Resolution open => no change required
2010-02-25 13:04 networkb Note Added: 0024816
2010-02-25 13:17 psarobe Note Added: 0024817
2010-02-26 00:00 anonymous sf_bug_id 0 =>
2010-03-08 16:05 jpabloae Target Version 2.50MP13 => 2.50MP14
2010-03-10 18:28 anonymous sf_bug_id => 2967974

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker