Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0010609 | Openbravo ERP | 09. Financial management | public | 2009-09-15 12:00 | 2009-11-12 00:00 |
|
Reporter | networkb | |
Assigned To | vmromanos | |
Priority | high | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | | OS | 5 | OS Version | |
Product Version | 2.40MP8 | |
Target Version | 2.40MP11 | Fixed in Version | 2.50MP9 | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | OBPS |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0010609: The general ledger journal report cut the gl_entries |
Description | The general ledger journal report cut the gl_entries.
This reports cuts the gl_entries depending on the record range variable defined
in the session preferences window. By default this variable is set to 100
so the reports prints the gl_entries in other page when it has
printed 100 entries in the first page. Some times a gl_entry does not enter in the first page, but as there are 100 rows printed, the rest of the gl_entry
is printed on the next page, what is not a correct way to show the financial reports. |
Steps To Reproduce | In a application with several gl_entries, execute the report
general ledger journal report in order to show more than 100 rows.
See that in the first page, the last gl_entry showed, is probably cut
and continues in the next page. |
Proposed Solution | |
Additional Information | |
Tags | No tags attached. |
Relationships | depends on | backport | 0010621 | 2.40MP11 | closed | vmromanos | The general ledger journal report cut the gl_entries |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2009-09-15 12:00 | networkb | New Issue | |
2009-09-15 12:00 | networkb | Assigned To | => rafaroda |
2009-09-15 12:00 | networkb | OBNetwork customer | => Yes |
2009-09-15 15:12 | rafaroda | Note Added: 0020073 | |
2009-09-15 15:12 | rafaroda | Assigned To | rafaroda => dalsasua |
2009-09-16 11:04 | dalsasua | Status | new => scheduled |
2009-09-16 11:04 | dalsasua | Note Added: 0020104 | |
2009-09-16 11:04 | dalsasua | fix_in_branch | => pi |
2009-09-16 11:54 | rafaroda | Priority | immediate => high |
2009-09-16 11:54 | rafaroda | fix_in_branch | pi => |
2009-10-03 11:28 | psarobe | Note Added: 0020683 | |
2009-11-09 19:06 | vmromanos | Assigned To | dalsasua => vmromanos |
2009-11-09 21:14 | vmromanos | Note Added: 0021659 | |
2009-11-10 12:16 | hgbot | Checkin | |
2009-11-10 12:16 | hgbot | Note Added: 0021682 | |
2009-11-10 12:16 | hgbot | Status | scheduled => resolved |
2009-11-10 12:16 | hgbot | Resolution | open => fixed |
2009-11-10 12:16 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/80ef47d370f7f4a061f5d45dd30d004110e6daff [^] |
2009-11-11 08:49 | sureshbabu | Status | resolved => closed |
2009-11-11 08:49 | sureshbabu | Note Added: 0021708 | |
2009-11-11 08:49 | sureshbabu | Fixed in Version | => 2.50MP9 |
2009-11-12 00:00 | anonymous | sf_bug_id | 0 => 2896284 |
Notes |
|
|
David,
Can you please comment on this 2.40 issue with the General Ledger Journal report?
Thanks. |
|
|
|
Hi,
After discussing the proper solution, we decided that:
- html format: if the last entry of the page is not complete, a message will be displayed at the bottom to make the user know that the last entry continues in the next page.
- pdf format: each new page will start a new entry, to avoid splitting them between pages.
Regards,
David |
|
|
|
This is not an acceptable solution for html format and it's annoying and not usable for the end user. The end user needs to see the whole entry in one shot and not to remember what is in one page and in the other page
The solution for the html format must be the same than for the PDF format. So please take into account this note for the solution |
|
|
|
The PDF file is not going to be modified for two reasons:
1- The file is delivered as "one piece", being possible to read it in a continuous way; the user has always the complete accounting entry available in the file. However, the HTML format is totally different, since it can show partial accounting entries in an independent way, which can confuse the user due to the context's lack.
2- If we have a very long entry with a lot of lines, the entry will always be split between one or more pages, so it's impossible to avoid it in the PDF format. However, in HTML we have the chance to increase the length of the page as much as we want. |
|
|
(0021682)
|
hgbot
|
2009-11-10 12:16
|
|
Repository: erp/devel/pi
Changeset: 80ef47d370f7f4a061f5d45dd30d004110e6daff
Author: Víctor Martínez Romanos <victor.martinez <at> openbravo.com>
Date: Tue Nov 10 12:16:41 2009 +0100
URL: http://code.openbravo.com/erp/devel/pi/rev/80ef47d370f7f4a061f5d45dd30d004110e6daff [^]
Fixed bug 10609: The general ledger journal report cut the gl_entries
---
M src/org/openbravo/erpCommon/ad_reports/ReportGeneralLedgerJournal.java
M src/org/openbravo/erpCommon/ad_reports/ReportGeneralLedgerJournal_data.xsql
---
|
|
|
|
Tested working as per the proposed solution, Its working fine in HTML format but in PDF the GL entries are still displayed partially in two pages. |
|