Reporting

From Wiki

Proposition

General Style

• use the Helvetica font everywhere
• margins (in millimeters):
  • top: 14
  • bottom: 16
  • left: between 12 and 13 to allow punching holes without punching in the text area
  • right: between 12 and 13

Note: the line separator between the header and the body can overlap slightly in the left and right margins: up to 9 millimeters on the left and up to 12 millimeters on the right

• for Titles use the font "Heveltica-Bold" with the size "14.5"

• put the context on each report: example, for the report account_balance: the context is the fiscal year and periods

• for the name of cells: use Capital Letter if the name contains more than one word (ex: Date Ordered)
• content and name of cells should have the same indentation

• for report, we can define two kinds of arrays:
  • array with general information, like reference, date..., use:
    • "Bold-Helvetica" and size=8 for cells name
    • and "Helvetica" for content
  • array with detailed information, use:
    • "Helvetica-Bold" size "9" for cells names
    • "Helvetica" size "8" for content

Headers and footers for internal reports

• Internal report = all accounting reports and other that have only internal use (not sent to customers)
• height of headers should be shorter
• take off corporate header and footer for internal report (Use a simplified header for internal reports: Company's name, report title, printing date and page number)

• header:
  • company's name: in the middle of each page
  • report's name: is printed centered after the header
• footer:
  • printing date: not in the middle of the report, but on the left in the header
  • page number: on each page, is printed on the right. This page number should contain the current page number and the total of pages. Ex: page 3/15

table line separator

• it's prettier if each line in the table have a light grey line as separator
• use a grey column separator only for array containing general information

table breaking

• a table header should at least have two data rows (no table header alone at the bottom of the page)
• if possible, when a big table is broken, the table header should be repeated on every page

how to differentiate parents and children ?

• When you have more than one level: use these styles:
  • level1 and 2:fontSize="8.0" fontName="Helvetica-Bold"
  • from the third level, use:fontName="Helvetica" fontSize="8.0" and increase the indentation with 13 (pixels) for each level
  • underline sums when the element is a parent

TO DO

• standard for separator of numbers (for decimals and for thousands) and for date format, belonging to the lang of user, the printing language can be changed by the user using the "Preference" menu of the OpenERP Client

• total page numbers (ex: 1/24) (NOTE: if we print invoices for many customers, it has to number correctly the pages corresponding to each customer. Ex: 1/2, 2/2 for customer A, then 1/3, 2/3, 3/3 for customer B, etc)

• lines too long should be truncated (word wrapped). don't truncate words, put the word in the next line, and if the word is too long, find a solution to wrap properly.

• printing speed: some reports takes too long to be printed. Some are never printed because the printing is aborted (too much time)

• the pdf file should have title. For the moment, the window title is 'untitled'

• recreate the 'packing list' and 'delivery order' report because it's too ugly

• if possible: bring forward the column amount in the following page when an invoice has to be printed on several page

• all dates should be formatted according to the user's language

• modify the 'account list' report (from the chart account) when CampToCamp will have modified it

• if we have only one line left at the bottom of a page, do not write just the firstline of a table, but start writing on the next page.
• When we arrived at the end of a page with a a table with a large number of lines. write a subtotal of each columns on the next page.

• in a table, be able to give a specific style (bold, italic, etc) for some lines. Ex: a style for the partner name, then another style for lines linked to the partner, then another style for this partner total.

• find a tip to be able to make a tabulated text without using the dash key '-' (not very clean in report)

• keep the print screen option but improve it (no overlaped columns, for ex.)