iReport is a graphical tool you can use to create/edit templates (jrxml files) that will be later processed by JasperReports engine.

You must use iReport 4.0.1

Fonts

JasperReports introduced a change in version 3.6.1 that it should fail (throw an exception) when you're trying to use a font that is not available.

JasperReports 3.6.1 (2009-10-26, SVN 3170) --------------------------------------------- - net.sf.jasperreports.awt.ignore.missing.font configuration property added to control font availability verifications during report filling and report AWT rendering; 

If you open a JasperReports template and is using a font not available in your system, you won't see the text of label. To avoid this problem you need to configure your iReport to skip this check.

• Go to Tools > Options > JasperReports Properties
• Set to true the property net.sf.jasperreports.awt.ignore.missing.font

Scriplet Class

Openbravo 3 doesn't support out of the box any Scriplet class. Make sure your template doesn't contain any class in the template properties.

• Window > Report Inspector
• Scroll down in the More section
• Make sure the Scriptlet class property is empty

Language

The default language for expressions in Openbravo 3 is Java. Make sure that your template uses Java as language expression.

• Window > Report Inspector
• Scroll down to the More section
• Pick Java in the Language property

How to add a Constraint

In the Application Dictionary || Message window create a new record using the following details:

• Module Openbravo Howtos 2 as this is the module containing the constraint also.
• Search key: The search key must be exactly the same as the constraint's one, in this case em_ht2_ht_salary_dates_chk as this is the link between the constraint and the message.

• Message type: Depending on the type the UI for the message box will be different (green for success, yellow for warning...), in our case we want a red error message box, so we select Error.
• Message text: It is the user friendly message that will be displayed inside the message box. So let's enter: The Valid To date may not be before the Valid From date. 

   // create the object through the factory   final Category bpg = OBProvider.getInstance().get(Category.class);

Configuring export parameters in your Openbravo environment

You can change the decimal separator, the field separator, and the encoding of the file you get when you use the Export to Spreadsheet functionality in Openbravo if you need them to be different from the default values.

This is done via preferences. After logging in to Openbravo, go to the Preference window and do the following:

• If you want to change the decimal separator: create a new record. Select the "CSV Decimal Separator" in the "Property" field. In the "value" field, type your selected decimal separator (for example, the comma character (,), or the decimal point (.)). Save the record.

• If you want to change the field separator: create a new record. Select the "CSV Field Separator" in the "Property" field. In the "value" field, type your selected field separator. Save the record.

• If you want to change the file encoding: create a new record. Select the "CSV Text Encoding" field in the "Property" field. In the "value" field, type the selected file encoding (for example, UTF-8 should work in most non-Windows non-Excel environments). Save the record.

After creating the preference (or preferences), log out of the application. Log in again, and try the Export to Spreadsheet functionality, to see the results.

（3） Create Shipment from orders 提示库存不足

检查Order所在的Org，其Warehouse Tab没有配置相应的Warehouse。

（4）Quotation无法转换成Sale Order

Document Type中的Quotation项目必须指定Document Type For Order

the "Quotation" document type requires a sales order document type (i.e. Standard Order) to be defined as "Document Type for Order" to allow the conversion of a sales quotation into a sales order.

(5)There are three ways of accounting in Openbravo:

• To manually post each document by using the process button "Post".
  The process button "Post" can be found in the window used to create a given document. For instance a purchase invoice is created and therefore could be posted in the Purchase Invoice window.
  • This button is shown for accounting users if the Attribute "ShowAcct" is visible for them. This configuration is enabled through a Preference.
• To manually post all the documents/transactions related to a given database table for instance the table "Invoices", by using the process GL posting by DB Tables
• or to automatically post accounting transactions of any type by scheduling the "Accounting Server Process" in the Process Request window. 

 (6) Payment Status

To better understand the configuration of the payment method, it is also necessary to understand the payment status related to the process steps.

During the whole Payment Cycle, the payment is defined by one status so the user knows the last step of the process that took place and the following step that should take place.

In the following explanation and diagram below, the different Payment Statuses are explained.

• Awaiting Payment: This status appears when a Receipt/Payment has been created in either the Payment In window or in the Payment Out window, but it has no details of what it is going to be received or paid.
• Awaiting Execution: This status appears when the Receipt/Payment has been created and processed and there is an automated execution process to be executed.
  This is an optional status which will be skipped if:
  • the Payment Method is Manual
  • or if the Payment Method is Automatic and it is not set as "Deferred".
• Payment Received/Made: This status appears when the Receipt/Payment has been completed and processed.
• Deposited/Withdrawn not Cleared: This status appears when the Receipt/Payment has been added to the Financial Account screen, therefore the corresponding Deposit/Withdrawal transaction has been created in the Financial Account.
• Payment Cleared: This status appears when the Deposit/Witdrawal reconciliation has been executed. 

注册翻译模块

When you register the module, fill in the fields as follows:

• 从Module Type列表，选Module.
• 在Name字段，输入Java package name of the translation, using the correct naming convention.
• Complete the Description and Help fields, using the language that you are translating into.
• Select the Is translation module option.
• Clear the Has reference data, Translation required and Has chart of accounts options.
• Select the In development option. Remember that you cannot work on a module unless the In development option is selected.
• From the Module language menu, select the translation language. For example if you are translating into Czech, select Czech from the list.
• On the Dependencies tab, specify the module you are translating as the dependent module. For example if you are translating the Core module, select Core as the dependent module.

When you click Register Module you will be asked to supply your username and password for the Openbravo Forge

导出数据库

When you have registered the module, the next stage is to export the database to create the necessary module folders.

1. 执行下列命令：

   ant export.database

   Exporting the database creates a new subfolder within the Modules folder. The new folder has the same name as the java package of the translation module, for example modules/org.openbravo.translation.es_ES.

2. Within the Modules folder, manually create a subfolder called referencedata. You must use this exact name, note that it is all lower case and has no spaces.
3. Within the referencedata folder, create another subfolder called translation.
4. Within the 'translation folder create another folder for the translation, using the xx_YY language / country code naming convention. For example en_US for US English.
5. Place the translated .xml files within the folder for its respective language.

翻译.xml文件

You can now translate the .xml files using your preferred editor. When you have finished translating, copy them into the translation subfolder you have already created.

把模块打包成.obx文件

To package the module, 执行下列命令 ant package.module -Dmodule=modulename, where modulename is the Java package name of the module.

It is a known issue that the tree icon in the teams window does not work. If it is clicked it throws an error. Openbravo ERP does not support trees on modules yet. Still, the module has been designed to provide a mean to workaround this issue. As for that, some java files needs to be modified and the application recompiled to make the changes visible. Take into account that this is a core modification (and core modifications should not be done). If a core modification is done, whenever the system is updated with the next maintenaince pack, the changes will be lost (you will have to remember to do them again after updating the system).

Making this changes will make the tree icon work and so, the drag and drop functionality will be usable. The changes consist on adding the following lines in the following files:

• src/org/openbravo/erpCommon/utility/WindowTreeChecks.java - Line 132

   } else if (TreeType.equals("HCMC_TE")) {



result = "";

• src/org/openbravo/erpCommon/utility/WindowTreeUtility.java - Line 73

   else if (keyColumnName.equals("Hcmc_Team_ID"))



TreeType = "HCMC_TE";

• src/org/openbravo/erpCommon/utility/WindowTreeUtility.java - Line 155

   else if (TreeType.equals("HCMC_TE"))



data = WindowTreeData.selectTeam(conn, vars.getUser(), strEditable, strParentID, strNodeId,



TreeID);

• src/org/openbravo/erpCommon/utility/WindowTree_data.xsql - Line 290

  <SqlMethod name="selectTeam" type="preparedStatement" return="multiple">



<SqlMethodComment></SqlMethodComment>



<Sql>



SELECT tn.Node_ID,tn.Parent_ID,tn.SeqNo,tb.IsActive, te.HCMC_TEAM_ID AS ID, te.NAME, ' ' AS Description,te.IsSummary 



FROM AD_TREENODE tn LEFT JOIN AD_TREEBAR tb ON  tn.AD_Tree_ID=tb.AD_Tree_ID



AND tn.Node_ID=tb.Node_ID 



AND tb.AD_User_ID = ?  , 



HCMC_TEAM te



WHERE tn.Node_ID = te.HCMC_TEAM_ID



AND tn.AD_Tree_ID = ? 



ORDER BY COALESCE(tn.Parent_ID, '-1'), tn.SeqNo



</Sql>



<Parameter name="adUserId"/>



<Parameter name="editable" optional="true" type="none" after="WHERE " text="tn.IsActive='Y' AND te.isActive='Y' AND "/>



<Parameter name="parentId" optional="true" after="WHERE " text="tn.Parent_ID = ? AND "/>



<Parameter name="nodeId" optional="true" after="WHERE " text="tn.Node_ID = ? AND "/>



<Parameter name="adTreeId"/>



</SqlMethod>

Notice that the line number above may change over time. Notice that this lines should be eliminated manually if the module is unistalled.

Add Team Manager 

org.openbravo.hcm.common.ad_process.HCMC_addmanager_process.java

      final Calendar today = Calendar.getInstance();
      final SimpleDateFormat sdf = new SimpleDateFormat();
      sdf.applyPattern(bundle.getContext().getJavaDateFormat());

      final Date effectiveFrom = sdf.parse(strEffectiveFrom);
      final Date effectiveTo = ((strEffectiveTo != null && strEffectiveTo != "") ? sdf
          .parse(strEffectiveTo) : null);

Assign roles to users

Logged in as client admin, users can be created navigating to General Setup || Security || User . In the user roles tab, roles can be assigned to this users. Later on, once the employees are inserted in the system, each employee can be associated to a user. This way, the employee can access the system with his/her own user and see their personal information.

Example: Creation of a user for an employee called Peter:

• Go to General Setup > Security > User
• Fill mandatory fields and set a password.
• Select Peter as business partner. Notice that this step can only be done after the employees are inserted in the system (explained below)
• Go to User Roles and enter a new record for Employee role.
• Now Peter can log in in the application with the username and password provided. He will only have access to his own information in the employee self service tab.

Example: Creation of a user for a manager called Mary:

• Go to General Setup > Security > User
• Fill mandatory fields and set a password.
• Select Mary as business partner. Notice that this step can only be done after the employees are inserted in the system (explained below)
• Go to User Roles and enter a new record for Manager role.
• Now Mary can log in in the application with the username and password provided. She will have access to her own information in the employee self service tab. She will also have access to the window employee (manager view) where the information of the employees reporting to her can be seen. Notice that Mary has to be the current manager of at least one team. she will see the information of the employees associated to those teams.

Summary

This article explains in detail how to install and configure the whole stack required for a Openbravo ERP development environment, including:

• PostgreSQL.
• Oracle.
• Sun JDK.
• Apache Ant.
• Apache Tomcat.

The whole guide is valid for all the hardware architectures the stack supports, such as x86 or x86_64. A minimum of 2GB or RAM is recommended for x86 and 3GB for x86_64.

Motivation

A development setup has different needs than a production environment. The main goal is to make the developer's life as easy as possible, while increasing the productivity.

Some of the components are configured in the same way as in a production system. In those cases a link to the production environment setup is provided.

Operating System

We recommend using Linux or another UNIX-alike flavor (*BSD, OS-X, OpenSolaris). The amount of useful development tools provided by these operating systems are vastly superior to the rest, at least regarding Openbravo ERP. Do not use Windows.

Create an unprivileged user for you in this operating system. And once the environment is configured, avoid using the root user for anything related to Openbravo ERP development. Specially, do not compile as root.

PostgreSQL

Follow the installation steps to install PostgreSQL, configure an admin (postgres) password, and setup the MD5 password authentication. 8.3.5 or higher is the recommended version. Additionally, make sure the postgresql-contrib modules is installed (UUID requires it). Once it is installed, and to make the database accessible from anywhere, so that external developers or yourself can access it easily with PgAdmin3, psql or any other development tool. Locate and edit the postgresql.conf file, and uncomment the following line, assigning this new value:

listen_addresses='*'

This makes the database be listening in all the interfaces available in your system and not only in localhost (default).

Locate and edit the pg_hba.conf file, and add this line at the end:

host    all         all         0.0.0.0/0          md5

Or if you want more security you can change the 0.0.0.0/0 with the concrete IP that you want to give access for example 1.2.3.4/32.

Just for safety purposes, this assumes you have a firewall in your local LAN preventing outsiders to access the database.

As an example, in Ubuntu 10.04, these file are located in /etc/postgresql/8.4/main, assuming that you have installed PostgreSQL 8.4.x

Oracle

Do not use Oracle XE 10g. It's 4GB storage limitation makes it useless for heavy development in a few days, and it has a bug that happens usually when using Openbravo ERP. Therefore, the recommended version is Standard Edition 11g (>=11.1.0.6.0).

The number of open cursors should be 3000 at least. To verify this:

SELECT value FROM v$parameter WHERE name = 'open_cursors';

To increase it:

ALTER SYSTEM SET open_cursors = 3000 SCOPE=BOTH;

Make sure that the number of processes is 150 at least. To verify this:

SELECT value FROM v$parameter WHERE name = 'processes';

To increase it:

ALTER SYSTEM set processes=150 SCOPE=SPFILE;

And restart Oracle after doing this change.

Sun JDK

Follow the installation steps to set up the Sun JDK. Notice that version JDK 1.6 must be used for version >=2.50 developments.

The IBM JDK works well too, but almost all the developers use Sun's version. It is therefore the recommended one.

Apache Ant

Follow the installation steps to set up the Apache Ant. Since version 2.50 Ant needs its memory settings to be tweaked. Otherwise some basic tasks like a compilation are likely to fail. Assuming you are using Bash as your shell, append the following line to your ~/.bashrc file:

export ANT_OPTS="-Xmx1024M"

For 64bit machines:

export ANT_OPTS="-Xmx1024M -XX:MaxPermSize=128M"

See the Apache Tomcat section for an explanation of what these options mean.

Close your current shell session and open a new one to apply changes.

Apache Tomcat

Do not use the Tomcat version provided by your operating system's package manager. The packaged version of Tomcat is very unfriendly in terms of development due to web application deployment specifics. This especially applies to Linux distributions.

Instead, download the official distribution (version 6.0.x), and extract the files in your home directory. We recommend you to place it in ~/servers/tomcat.

Every Linux distribution and operating system packages Tomcat in a different way, with different security settings, permissions, memory setting and logging configuration. Some of these configurations are not development friendly. This is the reason of the recommendation to use the official distribution.

The default memory settings of Tomcat are not enough for a proper Openbravo ERP functioning. Thus append the following line to your ~/.bashrc

export CATALINA_OPTS="-Djava.awt.headless=true -Xms384M -Xmx512M -XX:MaxPermSize=256M"

• -Djava.awt.headless: this setting controls running the environment with a headless implementation. In Openbravo ERP the client is always a web browser, so the JVM does not need to run any graphical window at all.

• -Xms: this setting controls the initial size of the Java heap. Properly tuning this parameter reduces the overhead of garbage collection, improving server response time and throughput.

• -Xmx: this setting controls the maximum size of the Java heap. Properly tuning this parameter reduces the overhead of garbage collection, improving server response time and throughput.

• -XX:MaxPermSize: this setting controls the section of the heap reserved for the permanent generation, and holds all of the reflective data for the JVM.

These options are the same ones as for production environment, except for the -server option. This is useful only in production servers, because it makes the JVM to use the optimizing compiler instead of the standard one. And while this change increases significantly the performance of the server, it takes longer to warm up. And deployment speed is something that a developer appreciates.

In order to avoid the Unable to find a javac compiler; com.sun.tools.javac.Main is not on the classpath. Perhaps JAVA_HOME does not point to the JDK error when trying to compile the application from Tomcat using the Openbravo ERP web interface, add the tools.jar library to Tomcat's classpath:

cp $JAVA_HOME/lib/tools.jar ~/servers/tomcat/lib/

In order to avoid Tomcat from auto-reloading itself, comment the WatchedResource line in conf/context.xml:

<!-- <WatchedResource>WEB-INF/web.xml</WatchedResource> -->

Configure a username and password for the Tomcat Manager, by replacing the conf/tomcat-users.xml file with these contents:

<?xml version='1.0' encoding='utf-8'?>

<tomcat-users>

<role rolename="manager"/>

<role rolename="admin"/>

<user username="admin" password="admin" roles="admin,manager"/>

</tomcat-users>

Replace password="admin" with your own password.

Finally, to start and stop tomcat use the following commands:

cd ~/servers/tomcat/bin

./startup.sh

./shutdown.sh

Mercurial

Follow the Mercurial manual for Openbravo developers to install and configure it.

Error received in IO response:
liveGrid.getBackendPageSize is not a function



解決方法:

清除流覽器的Cookie后 OK

 postgresql-8.4

postgresql-contrib-8.4