Pentaho Report OpenERP 7.0 Module Installation and Configuration


This section explains how to install and configure Pentaho report module and report engine so it's possible to print and Forms, Report, Labels etc, that have been created with the Pentaho report designer,  directly from within OpenERP. This module integrates Pentaho's reporting engine with OpenERP 7.0.

The module will only work together with the pentaho print engine. You'll need first to:

 Installation and configuration of the pentaho_reports OpenERP Module

1. Download the pentaho_report module

  • Download and extract the .zip (ensure you download the version for OpenERP 7.0)

2. install on the OpenERP 7.0 server

  • Copy all the files in the extracted directory /addons/pentaho_reports to the location of your OpenERP server in the addons directory - keeping the same name pentaho_reports.
  • If your installation requires it; change the owner of the directory to openerp  sudo chown openerp: pentaho_reports
  • Restart the OpenERP 7.0 server
  • Load and install the "pentaho_reports" module in OpenERP and install (goto setting/modules/apps). To find the new module, I noticed in OpenERP 7.0 you won't find the new module under the menu "Apps". You'll need to go to the menu "/settings/modules/installed modules". then remove the filter "installed modules" then search "pentaho". 

3. Configure pentaho_reports module 

  • goto menu  /settings/parameter/system parameters
  • You'll see some parameters have already been pre-configured by the module. The default parameters will need to be changed according to your own installation. 
  • The address of the Pentaho server which is used to render the report is defined with the parameter:pentaho.server.url. Change the IP address of the server you installed the report engine on, as follows:

pentaho.server.urlhttp://<IP address of your server>:8090/pentaho-reports-for-openerp<IP address of your server>

  • For object based data sources, the Pentaho server will use XML-RPC to connect to the current database using the interface and port as defined in the OpenERP config file, and the reporting user's credentials.
  • I haven't tested this yet but, for SQL query based data sources, the Pentaho server will use the following parameters:
    • pentaho.postgres.port
    • pentaho.postgres.login
    • pentaho.postgres.password

4. Report Actions

  • Reports are defined to OpenERP under /Settings/Actions/Pentaho Reports.Reports can be handled by OpenERP in two ways. They can be linked to a menu, or they can be linked to a model.
  • Model linked reports will appear in the pull-down toolbar menu as per standard reports in OpenERP 7.0, or they can be specifically called with an action, such as a button. A record or number of records needs to be selected before the action will be invoked, and the ids of the selected records will be passed to the report as a list parameter called "ids". A report invoked this way will not prompt for any additional parameters. A front end custom wizard can be created if desired to invoke the action, but that wizard and the report would be very closely tied and needs to be developed in conjunction with one other.

5. Configure the reports and report menu location

  • After installation of the pentaho_reports module, a new menu appears under the /settings/Actions section called Pentaho Reports
pentaho report

  • Click on the menu to configure the report:
pentaho reports configuration form

  • Enter a name for the report. This will also be the name of the report menu item. 
  • Enter a service name. This can be any name you like and is used as reference if you need to trigger an action. The service name is only important if it is overriding an existing service, or if the report is to be invoked from coded actions like buttons or wizards.
  • Enter a prefix for the report (optional)
  • Associate the report to the correct model as defined when you created the report in Pentaho report designer
  • Output types specified here are defaults, and can be overridden by either a custom wizard or by menu linked reports. They will not be changeable for model linked reports which don't have specific coding.
  • Enter the location of the print menu by configuration of the Linked Menu Item. Ensure to put the menu in a logical place.
  • Upload the Pentaho report file .prpt that you created in the Pentaho report design in the previous section. The prpt (Pentaho report definition) file selected is stored in the database. Changing the report using the designer will require the report to be re-loaded.
  • A prpt file and action can easily be defined as part of a module and distributed this way. Be aware, though, if the module is upgraded from within OpenERP it could potentially reload the distributed report and may lose changes that were uploaded manually after module installation.
  • Object ids are not passed to these reports, so selections are probably required if not all data is to be included.
  • The actions can override existing OpenERP actions (such as invoice prints) or can be new actions.
  • Security groups entered against the action will be respected in regard to action visibility - they play no role in the report execution.
  • If a context value is required to set a default value, it needs to be set against the created action. It comes up under Settings/Actions/Window Actions. It will already have a Context Value with the service_name defined, which should be left intact.
6. Running the Report
  • Menu linked reports will appear in the menu where required. In this case I put the menu in the reporting/manufacturing section. It created automatically the menu Production Order in the correct location . 

pentaho report for openerp - report menu configuration

  • When the menu item is pressed a pop-up window appears, prompting for a report output type, and any additional (visible) parameters that are defined. 

pentaho reports for openerp

the default print type is to .pdf (this can be changed in the configuration step earlier). Different report formats can be selected too e.g. .xls, csv, rft, htlm, txt. 

pentaho reports for openerp - report types


Below are the instructions from the OpenERP 7.0 module

Pentaho - OpenERP Report Integration by Willow IT

This module integrates Pentaho's reporting engine with OpenERP.

This project was developed by Willow IT, using the libraries and extensions developed by De Bortoli Wines, Australia (Pieter van der Merwe in particular) for the Pentaho reporting system. The OpenERP addon also derives from and/or is inspired by the Jasper Reports addon developed by NaN-tic.

Willow IT contributions:
Deepak Seshadri - OpenERP-Pentaho server connector (Java) Richard deMeester - frontend and core functions, automated wizard and action implementation Douglas Parker - additional integration Jon Wilson - inspiration, testing, and whipping

Report Designer and Java Component

For notes on installing and running the report designer, refer to:

The README document contains instructions relevant to building and running the java component.

Report Types

Broadly speaking, two types of data sources can be used to produce the reports. OpenERP object data sources or SQL query data sources.

  • Object data sources have the advantage that they can use OpenERP model columns, even those that are not stored in the database. This includes functional fields, related fields, properties. They can iterate through one2many and many2many subfields. They also respect OpenERP record rules.
  • SQL data sources have the advantage that they allow greater flexibility in selections, and other SQL features like grouping and selective inclusion of sub-queries. It also allows selection where no OpenERP model relationship exists. It does not respect OpenERP record rules, which may be seen as an advantage for creating summary type reports which may be run by users who may not be able to view low-level data. Because of this, you need to be careful.

Report Parameters

Prompted and hidden parameters are supported, as are mandatory values.

Most Pentaho report parameter types and features have been mapped, where practicable, to something which makes sense to an OpenERP environment. This means that a number of Java data types don't necessarily differentiate. For example, (Integer / Long / Short / BigInteger / et al) will all be treated as integers.

Default values can be passed, but default value formulas are not implemented. The one special default value formula =NOW() is the only exception, which returns as the default.

Hidden parameters must obviously receive and work with a default value of some sort. This default can be the Pentaho default, or can be sent to the report in the context in the format:
{'pentaho_defaults' : { .... }}

where the passed dictionary contains the parameter names as keys. See below for guidance on where to set this up.

Pentaho Display Types have been consolidated. Drop Down, Single Value List, etc, all display as OpenERP selection pull downs. Pentaho multi value selection types, such as Multi Value List, Check Box, etc, are implemented as single value selection pull downs. Date Picker uses the standard OpenERP date/time widget.

Other Pentaho parameter features should be considered unsupported, such as Post-Processing Formula, Display Value Formula, Visible Items, Validate Values, et al.


This has been developed over time to meet specific requirements as we have needed to meet them. If something is wrong, or you think would make a great feature, please do let us know at:


We will be endeavouring to create a library of sample and useful reports. Check at:

where we will announce when and where this is available. In the meantime, if you develop any reports or templates that you would consider worth sharing, please email them through with some description or details.