0019000: Balance sheet and P&L report does not work when system configured with MM-DD-YYYY date format

Notes
(0045696) vmromanos (manager) 2012-03-02 11:26	Closed as unable to reproduce. See attached files: - vma_filters.png shows the filters used for launching the report. See the US format dates - vma_report.pdf is the report. Dates are OK

(0046016) pjuvara (reporter) 2012-03-02 16:27	Victor, the video that I had prepared to illustrates this problem has been lost (apparently there is a silent failure in Mantis when you attach files above a certain size). Before you close this issue, can you please do the following test: 1) The data in the demo environment is in Aug - Sep 2010 2) If you run the P&L for the period 01-JAN-2010 (01-01-2010) to 31-AUG-2010 (08-31-2010) you should be getting a different result than if you run it for 01-JAN-2010 to 31-DEC-2010. 3) My video demonstrated that you are getting the same result. The reason for that is that 08-31-2010 is a valid date in MM-DD-YYYY format but it is invalid in DD-MM-YYYY and the report interprets it as null, behaving therefore as from 01-JAN-2010 till the end of 2010.

(0047469) vmromanos (manager) 2012-04-11 11:56	Paolo, thanks for the clarification. We will take a look to the issue again trying to follow these steps.

(0047771) vmromanos (manager) 2012-04-20 09:41	Closing the issue as unable to reproduce. This was my testing plan: 1. Create two different environments with exactly the same accounting data. (Two versions of PI in the same revision) 2. Environment "en" has "MM-DD-YYYY" as format date 3. Environment "es" has "DD-MM-YYYY" as format date 4. Run the P&L with the same filters in both environment. Important: select 31-AUG in "to date" filters. According to the issue, this date should be consider as null by the system, getting wrong data in the "en" environment. 5. Compare both reports and check amounts are equals. The result of my test is available in the attached 31AUG.zip file. The reports have exactly the same data, so the report works fine with the "MM-DD-YYYY" format. @Paolo, it looks like there is something wrong configured in your environment. It this issue is still present, please send us an email with more details (Openbravo.properties, DB you're using, etc.) and we will try to help you.

Issue History
Date Modified	Username	Field	Change
2011-11-07 01:11	pjuvara	New Issue
2011-11-07 01:11	pjuvara	Assigned To	=> jonalegriaesarte
2011-11-07 01:11	pjuvara	Modules	=> Core
2011-11-07 01:20	pjuvara	Relationship added	blocks 0019002
2011-11-07 01:43	pjuvara	Tag Attached: AccountingDemo
2011-12-19 19:12	marvintm	Assigned To	jonalegriaesarte => dalsasua
2012-02-29 12:43	iciordia	Assigned To	dalsasua => vmromanos
2012-03-02 10:47	vmromanos	Tag Attached: VMA-Reviewed
2012-03-02 10:47	vmromanos	Status	new => scheduled
2012-03-02 10:47	vmromanos	fix_in_branch	=> pi
2012-03-02 11:19	vmromanos	File Added: vma_filters.png
2012-03-02 11:20	vmromanos	File Added: vma_report.pdf
2012-03-02 11:26	vmromanos	Note Added: 0045696
2012-03-02 11:26	vmromanos	Status	scheduled => closed
2012-03-02 11:26	vmromanos	Resolution	open => unable to reproduce
2012-03-02 16:27	pjuvara	Note Added: 0046016
2012-03-02 16:27	pjuvara	Status	closed => new
2012-03-02 16:27	pjuvara	Resolution	unable to reproduce => open
2012-04-11 11:56	vmromanos	Status	new => scheduled
2012-04-11 11:56	vmromanos	Note Added: 0047469
2012-04-20 09:27	vmromanos	File Added: 31AUG.zip
2012-04-20 09:41	vmromanos	Note Added: 0047771
2012-04-20 09:41	vmromanos	Status	scheduled => closed
2012-04-20 09:41	vmromanos	Resolution	open => unable to reproduce