Tryton - Issues

 

Issue3696

Title Add a report to allow printing of account moves
Priority wish Status in-progress
Superseder Nosy List ced, rhertzog, yangoon
Type feature request Components account
Assigned To rhertzog Keywords review
Reviews 4131002
View: 4131002

Created on 2014-02-20.11:13:12 by rhertzog, last changed by ced.

Files
File name Uploaded Type Edit Remove
move.odt rhertzog, 2014-03-08.22:53:56 application/vnd.oasis.opendocument.text
move.odt rhertzog, 2014-03-14.17:10:25 application/vnd.oasis.opendocument.text
move.odt yangoon, 2014-06-30.21:28:31 application/vnd.oasis.opendocument.text
piece_comptable.odt rhertzog, 2014-02-20.11:13:11 application/vnd.oasis.opendocument.text
Messages
msg18043 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2014-09-12.19:31:32
issue3679 is solved.
msg17496 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2014-07-10.00:38:55
Few comments on the last report:

- The first title doesn't have the style "Table Heading"
- I will put border on the table as it is done on every other standard report
- Other reports don't use a table for general information like date, journal etc.
- Why not putting each move on his own page?

About the print of state, I think we should wait issue3679
msg17378 (view) Author: [hidden] (yangoon) (Tryton translator) Date: 2014-07-01.10:08:31
amsg17374: Finally I would prefer to use 
IF TEST...
CHOOSE TEST...
WHEN TEST

like in account_invoiice/invoice.odt, rather duplicating strings, but only prviding one logic for the title.
msg17374 (view) Author: [hidden] (yangoon) (Tryton translator) Date: 2014-06-30.21:28:31
Hi Raphaël, 
I attached a quick version using a hack with tables, but at least it does, what seems to be intended.
msg17369 (view) Author: [hidden] (rhertzog) (Tryton committer) Date: 2014-06-30.16:23:56
Any chance you could give some guidance on how to go further with this ticket? I have answered your questions and provided an updated file.
msg16159 (view) Author: [hidden] (rhertzog) (Tryton committer) Date: 2014-03-14.17:10:25
Attaching a new version of move.odt that includes your suggestions. The only
detail that I don't know how to fix is how to include the "Draft" string on the
same title line so that a draft move shows "Draft Account Move (#123)" as title.
I could include the logic in a field but then the "Draft" string would no longer
be translatable...
msg16158 (view) Author: [hidden] (rhertzog) (Tryton committer) Date: 2014-03-14.16:31:48
About your comments, please note that I started from general_journal.odt so most
of your comments actually apply to general_journal.odt too...

> why not put both the move number and post_number like that no need to have two
cases

general_journal has two cases to showing "Posted <post_number>" or "Draft" so I
build on this to show the state of the account move as part of the table title...

> why not put date, journal post date and origin on the same line

Because journal name and origin are often long strings  (the latter in
particular) and we waste less space by giving them more width by default.

> I think it is better to always show description even if empty

OK.

> For the account use rec_name and not a custom format

OK, but this is a left-over from general_journal.odt.

> I think you use a stronger lines for the table as other reports

Actually I use two line width. The same as other formats for interior lines and
a larger one to split the multiple parts (header part, lines part).

> Generally we don't put so much spacing between tables or it should be a page
break.

As I explained, my goal is to print the report and cut the individual account
move. The additional space makes it easier to cut the paper and later attach it
to the corresponding supporting statement. So this is a feature.

> For post date, you should test only if the date is filled

OK.

> Use ternary operator instead of and/or
> Use rec_name for journal

OK.
msg16053 (view) Author: [hidden] (ced) (Tryton committer) (Tryton translator) Date: 2014-03-08.23:21:53
About the layout:

- why not put both the move number and post_number like that no need to have two
cases
- why not put date, journal post date and origin on the same line
- I think it is better to always show description even if empty
- For the account use rec_name and not a custom format
- I think you use a stronger lines for the table as other reports
- Generally we don't put so much spacing between tables or it should be a page
break.
- For post date, you should test only if the date is filled
- Use ternary operator instead of and/or
- Use rec_name for journal

PS: be sure to follow: https://code.google.com/p/tryton/wiki/ODTGuideLines
msg16052 (view) Author: [hidden] (rhertzog) (Tryton committer) Date: 2014-03-08.22:53:56
Attaching move.odt that is part of review4131002 on request of ced.
msg15875 (view) Author: [hidden] (rhertzog) (Tryton committer) Date: 2014-03-07.00:15:54
I submitted a proposed fix for this in review4131002
msg15689 (view) Author: [hidden] (rhertzog) (Tryton committer) Date: 2014-02-20.11:13:11
While I do all my accounting with Tryton, all my supporting statements are still
on paper and I attach a copy of the corresponding account move to each
supporting statement. Everything is archived in multiple folders (expenses,
revenues, bank, taxes, misc).

Up to now I copied the account move manually in pre-printed forms for generic
account moves (see attachment piece_comptable.odt) and the reference number I
used in my ledger was the same than the unique number printed on those forms.

With the switch to tryton, I have many more account moves because I'm no longer
using some of the not-so-clean shortcuts I was used to use (like recording
expenses directly as credit of the bank account instead of going through a
proper invoice recorded in a supplier account) and it would be really useful if
I could print all those account moves instead of copying them manually.

I believe that this should be a relatively easy enhancement to implement.

The only possibly tricky part is how to put two account moves per A4 page if we
want to keep the same layout than I used to use (with an A5 paper in landscape
mode for each account move). That said this is not a requirement and any
solution that doesn't waste a full page per account move while still ensuring
that account moves can't be split over multiple pages is OK (except for account
moves that have an unreasonable number of moves of course). Note that we can
defer this to the user side by using a full landscape A4 and letting the user
print in 2 pages per sheet mode.
History
Date User Action Args
2014-09-12 19:31:32cedsetmessages: + msg18043
2014-07-10 00:38:56cedsetmessages: + msg17496
2014-07-01 10:08:32yangoonsetmessages: + msg17378
2014-06-30 21:28:33yangoonsetfiles: + move.odt
nosy: + yangoon
messages: + msg17374
2014-06-30 16:23:57rhertzogsetmessages: + msg17369
2014-03-14 17:10:26rhertzogsetfiles: + move.odt
messages: + msg16159
2014-03-14 16:31:49rhertzogsetmessages: + msg16158
2014-03-08 23:21:54cedsetstatus: chatting -> in-progress
keyword: + review
nosy: + ced
messages: + msg16053
reviews: 4131002
assignedto: rhertzog
2014-03-08 22:53:57rhertzogsetfiles: + move.odt
messages: + msg16052
2014-03-07 00:15:55rhertzogsetstatus: unread -> chatting
messages: + msg15875

Showing 10 items. Show all history (warning: this could be VERY long)