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

View Issue Details[ Jump to Notes ] [ Issue History ] [ Print ]
ID
0028752
TypeCategorySeverityReproducibilityDate SubmittedLast Update
design defect[Localization Pack: Spain] AEAT 303majoralways2015-01-23 12:562015-02-26 11:20
ReporterpsanjuanView Statuspublic 
Assigned Toaferraz 
PriorityurgentResolutionfixedFixed in Version
StatusclosedFix in branchFixed in SCM revisionb95b5f2f6c06
ProjectionnoneETAnoneTarget Version
OSLinux 32 bitDatabaseOracleJava version1.6
OS VersionUbuntu 8.04.1Database version11.1.0.6.0Ant version1.7.0
Product VersionSCM revision 
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Regression introduced in release
Summary

0028752: 303 Year information should be considered from period's information instead of name set in Year window

Description303 Year information should be considered from period's information instead of name set in Year window
Steps To ReproduceDefine a calendar named 2014 for an Organization.

Manually create the periods of that year starting from July 2014 to December 2014 and then from January 2015 to June 2015

Navigate to Tax Report Launcher window and select Modelo 303 version 2015 mensual for the Organizacion.

Select Jan-15 as period.

Launch the report and realize that year 2014 is taken instead of year 2015
Proposed SolutionYear taken should be the one corresponding to the period selected.

* If period "Dec-14" 14 is selected by the end-user, 303 Tax form file should take 2014.

* If period "Jan-15" 14 is selected by the end-user, 303 Tax form file should take 2015.

TagsNo tags attached.
Attached Files

- Relationships [ Relation Graph ] [ Dependency Graph ]
related to defect 0028039 closedfsoto82 Modules Year information should be considered from period's information instead of name set in Year window 

-  Notes
(0074556)
hgbot (developer)
2015-02-17 14:00

 Repository: erp/pmods/org.openbravo.module.aeat303.es
Changeset: b95b5f2f6c06e5f46107a472805af1ff126a0c34
Author: Alvaro Ferraz <alvaro.ferraz <at> openbravo.com>
Date: Tue Feb 17 13:55:39 2015 +0100
URL: http://code.openbravo.com/erp/pmods/org.openbravo.module.aeat303.es/rev/b95b5f2f6c06e5f46107a472805af1ff126a0c34 [^]

Fixes issue 28752: Wrong year taken when launching Modelo 303 tax report

Instead of taking the year from the Tax Report Launcher window, it will be taken from the year of the period

---
M src-db/database/sourcedata/AD_MESSAGE.xml
M src/org/openbravo/module/aeat303/es/report/v2014/AEAT303Report2014.java
---
(0074557)
aferraz (developer)
2015-02-17 14:08

 Test plan:

- Define a calendar named 2014 for an Organization.
- Manually create the periods of that year starting from July 2014 to December 2014 and then from January 2015 to June 2015
- Add another period from December 2015 to January 2016 called Extra
- Navigate to Tax Report Launcher window and select Modelo 303 version 2015 mensual for the Organizacion. Select Jan-15 as period.
- Launch the report and realize that year 2015 is taken
- Navigate to Tax Report Launcher window and select Modelo 303 version 2015 mensual for the Organizacion. Select Extra as period.
- Launch the report and realize that "El periodo seleccionado debe comenzar y finalizar en el mismo año" error message is shown
(0074583)
hgbot (developer)
2015-02-18 10:52

 Repository: erp/pmods/org.openbravo.module.aeat303.es
Changeset: c4434f3b2724eddc31d9dbc683cadbff8af5a91d
Author: Alvaro Ferraz <alvaro.ferraz <at> openbravo.com>
Date: Wed Feb 18 10:52:20 2015 +0100
URL: http://code.openbravo.com/erp/pmods/org.openbravo.module.aeat303.es/rev/c4434f3b2724eddc31d9dbc683cadbff8af5a91d [^]

Related to issue 28752: Get correctly ending date

---
M src/org/openbravo/module/aeat303/es/report/v2014/AEAT303Report2014.java
---
(0074592)
psanjuan (manager)
2015-02-18 12:48

 Verified. Correct year selected once period is being selected.
An error is shown in case a period selected (nov-14 - Jan- 15) is selected, as there is no way to select the year.
(0074623)
Sandrahuguet (developer)
2015-02-18 18:28

 Code review done

- Issue History
Date Modified Username Field Change
2015-01-23 12:56 psanjuan New Issue
2015-01-23 12:56 psanjuan Assigned To => jonalegriaesarte
2015-01-23 12:56 psanjuan Relationship added caused by 0028040
2015-02-02 16:01 vmromanos Assigned To jonalegriaesarte => vmromanos
2015-02-02 16:01 vmromanos Status new => acknowledged
2015-02-13 11:08 psanjuan Relationship added related to 0028039
2015-02-13 12:17 psanjuan Steps to Reproduce Updated View Revisions
2015-02-13 12:17 psanjuan Proposed Solution updated
2015-02-17 10:20 aferraz Assigned To vmromanos => aferraz
2015-02-17 14:00 hgbot Checkin
2015-02-17 14:00 hgbot Note Added: 0074556
2015-02-17 14:00 hgbot Status acknowledged => resolved
2015-02-17 14:00 hgbot Resolution open => fixed
2015-02-17 14:00 hgbot Fixed in SCM revision => http://code.openbravo.com/erp/pmods/org.openbravo.module.aeat303.es/rev/b95b5f2f6c06e5f46107a472805af1ff126a0c34 [^]
2015-02-17 14:08 aferraz Note Added: 0074557
2015-02-18 10:52 hgbot Checkin
2015-02-18 10:52 hgbot Note Added: 0074583
2015-02-18 12:48 psanjuan Note Added: 0074592
2015-02-18 12:48 psanjuan Status resolved => closed
2015-02-18 18:28 Sandrahuguet Note Added: 0074623
2015-02-26 10:25 psanjuan Relationship deleted caused by 0028040
2015-02-26 11:20 psanjuan Summary It should be possible to launch 303 tax form for an Organization having a Fiscal Calendar defined from i.e. July to June => 303 Year information should be considered from period's information instead of name set in Year window
2015-02-26 11:20 psanjuan Description Updated View Revisions
2015-02-26 11:20 psanjuan Steps to Reproduce Updated View Revisions

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker