Compiere 3.2 Release Notes

November 28, 2008

Copyright2008Compiere,inc.Allrightsreserved www.compiere.com

Table of Contents

Compiere 3.2 Release Summary _________________________________________________________________________________3
Audience ____________________________________________________________________________________________________________ 3 Prerequisites _________________________________________________________________________________________________________ 3
Software Management _________________________________________________________________________________________3
Previous Installations ___________________________________________________________________________________________________ 3 Recommended Infrastructure_____________________________________________________________________________________________ 3 Process to Log Support Requests for Compiere 3.2 ___________________________________________________________________________ 3 Update/Migration Procedure _____________________________________________________________________________________________ 3 Install Procedure ______________________________________________________________________________________________________ 3 Application Extensions __________________________________________________________________________________________________ 3 Delete Client and Delete Client Transactions_________________________________________________________________________________ 3 Compiere 3.2.1 Service Pack Information ___________________________________________________________________________________ 3
New In Compiere 3.2 ________________________________________________________________________________________________4
Warehouse Management _______________________________________________ Compiere Warehouse Management 4 Business View Layer ____________________________________________________ Compiere Professional Edition 4 New Data Dictionary Feature: Value Assignment _____________________________________________________________________________ 4 Account Balance Summary ______________________________________________________________________________________________ 4 Reports Enhancements _________________________________________________________________________________________________ 4 Provision New Tenants Enhancements _____________________________________________________________________________________ 4 Login Message Broadcast system Enhancement _____________________________________________________________________________ 5 Request Enhancements _________________________________________________________________________________________________ 5 Translation Enhancements_______________________________________________________________________________________________ 5 Additional Enhancements _________________________________________________ Compiere Professional Edition 5 Web User Interface Compiere 3.2
The Web User Interface in Compiere 3.2 ________________________________________________________________________________5
____________________________________________
Compiere Professional Edition 5
Fixed Issues for Compiere 3.2 ________________________________________________________________________________________6 Product Enhancements for Compiere 3.2 _______________________________________________________________________________6 Known Issues in the Migration Process ________________________________________________________________________________7 Known Issues in the Install Process ___________________________________________________________________________________7 Known Issues in Compiere 3.2 ________________________________________________________________________________________9
Appendix A _________________________________________________________________________________________________10
Compiere 3.2 Migration Instructions __________________________________________________________________________________11
Prerequisites ________________________________________________________________________________________________________ 11 Migration____________________________________________________________________________________________________________ 11 Preserving Customizations______________________________________________________________________________________________ 11 Migration Steps ______________________________________________________________________________________________________ 11 Preparation __________________________________________________________________________________________________________ 12 Migrate to a New Release ______________________________________________________________________________________________ 12 Post Migration Steps for RMA/RTV _______________________________________________________________________________________ 22

Compiere 3.2 is a major release that adds more than 30 new, functional, technical, and business analysis enhancements. This new release continues Compieres commitment to building open source applications that drive down costs and complexities of ERP. Visit http://www.compiere.com/products/new-compiere-erp-3-2.php to learn more about the Compiere 3.2 benefits. Certain features in Compiere 3.2 require a Compiere Professional Edition subscription. Contact a Compiere Authorized Partner or Compiere Sales (http://www.compiere.com/company/contact-us.php) to acquire Compiere Professional Edition. Compiere 3.2 may include certain prototype features and beta functionality as indicated in their respective user interfaces with a beta checkbox. These are not recommended for production. They are intended for only for evaluation as beta functionality.

Audience

This guide is designed for Compiere Business Partners and Customers. It provides essential information for current Compiere administrators planning to install or migrate (upgrade) to Compiere 3.2.

Prerequisites

Working knowledge of Compiere ERP and CRM Compiere Web Store Access
Sun Java 1.6.0 Update 5 or Later Database Oracle XE, Oracle 10gR2, Oracle 11g, or EnterpriseDB Postgres Plus Advanced Server 8.3

Software Management

Previous Installations
You can download the Compiere 3.2 from http://www.compiere.com/wstore. The migration tool will bring you up directly to Compiere 3.2 plus all the cumulative fixes included in the service packs without having to migrate to an intermediate release.
Recommended Infrastructure
Sun Java JDK 6 Update 5 or Later (not just JRE)
- also known as Sun Java SDK.
TCP/IP connection and Internet access Disk Space: > 5 GB (includes database) Swap Space: > 1GB Memory: > 512 MB - Recommended: > 1 GB Firefox Browser 3.0 is recommended for Web User

Interface.

Database Oracle XE, Oracle 10gR2, Oracle 11g, or
EnterpriseDB Postgres Plus Advanced Server 8.3.
Tip: It is Mandatory to use a Unicode character set.
Database approved Linux Operating System, Windows

2003 or Windows XP

Process to Log Support Requests for Compiere 3.2
To ensure timely service for any issues, we require that all new cases into Compiere's Case Management system. Start logging support requests by following the steps described in Support Requests on our web page.

Update/Migration Procedure

See Appendix A

Install Procedure

See Appendix B

Application Extensions

See Appendix C

Delete Client and Delete Client Transactions

See Appendix D

Compiere 3.2.1 Service Pack Information

See Appendix E

Copyright 2008 Compiere Inc. All rights reserved

New In Compiere 3.2

The following is a detailed description of the enhancements made available in Compiere 3.2.

Warehouse Management

Compiere Warehouse Management
Compiere introduces Warehouse Management in 3.2. A warehouse management system, or (WMS), is a key part of the supply chain, and is used to control the movement and storage of material within a warehouse, and process the associated transactions, including shipping, receiving, putaway, and picking. The following lists the main features added to the Warehouse Management Functionality: Zones and Zone Relationships Warehouse Management Rules Engine Wave Planning Warehouse Replenishment Warehouse Task Management Streamlined Receiving Directed Picking and Putaway Reports Compiere Professional Edition

Business View Layer

In 3.2 the Business View Layer enables report designers and users to access business data from an optimized reporting schema that incorporates user-friendly field names, Compieres role-based security, and database security. Compiere 3.2 includes pre-defined business views spanning customer, vendor, product, invoice, shipment, and material receipt objects. Customers can create additional Business Views in a single step from within the Compiere system. In 3.2, we have added a default BVL database user called CompiereBVL with the same password as the Compiere user, which will contain all the business views published by the user. Important: In the 3.1 release, this step was done as a setup using Initial BVL Setup window. The Initial BVL setup is no longer included in 3.2. For 3.1 users who have already setup their BVL using Initial BVL setup, this will not be overwritten. Compiere will not create the CompiereBVL user in 3.2 and the initial set up will be maintained. In 3.2, we have also added 2 sample Jasper reports called Customer Contact and Customers and Partners that can be used as an example to integrate Jasper reports with BVL. These reports are based on business views under the CompiereBVL user mentioned earlier. For users who have already setup BVL in 3.1 release, the query within the sample reports should be modified to refer to the BVL user created in Initial BVL Setup. This can be done using a tool of your choice to create Jasper reports (like iReport, JasperAssistant, etc)

New Data Dictionary Feature: Value Assignment
Compiere 3.2 provides the ability to dynamically create default field values when a new record is created (SQL, constant, preferences). In addition to this, Value Assignments allow the ability to set values after the user presses save, just before a record is saved. This could be used to create a default value without user intervention or if the user fails to define a value. Another use is to assign a certain value based on other fields. Value Assignments are basically a declarative way to define before-insert/update/delete trigger.

Account Balance Summary

Compiere 3.2 provides the ability to store and manage account balances by user-specified granularity of summarization. By default, the Update Accounting Balances process accumulates the accounting transactions of each day for each combination of the accounting schema elements. These values are stored in the Accounting Fact Balances table, which is the source of data for all Financial reports. Compiere provides a new screen called Balance Aggregation, which allows users to summarize accounting data by Calendar Week, Month, and Day. Choosing the option of Calendar Month will reduce the number of records in the Accounting Fact Balances table and should improve the performance of Financial reports. This summarization option can be specified up to a specific date, after which the accounting balances are accumulated daily. Note that the Balance Accumulation option of Period of a Compiere Calendar is not yet operational.

Reports Enhancements

Compiere 3.2 provides the ability to zoom to a record from web generated pdf reports.
Provision New Tenants Enhancements
Compiere 3.2 provides a consistent way of creating new tenants from self service web store, swing or professional edition User Interfaces.
Copyright 2008 Compiere Inc. All rights reserved 4
Login Message Broadcast system Enhancement
Display Messages to user(s) after Login Display custom license information to all or selective users Configurable rules based, targeted message and information broadcast system

Request Enhancements

Compiere 3.2 provides the ability to create and inquire requests from the toolbar of any document in the Web UI.

Translation Enhancements

Compiere 3.2 provides the ability to selectively translate portions of the product.

Additional Enhancements

Compiere supports the use of the Google Chrome Browser for web user interface.
Compiere Professional Edition
The Web User Interface in Compiere 3.2
The following is a detailed description of what the Web user interface has to offer in Compiere 3.2.
Web User Interface Compiere 3.2
In order to get properly acquainted with the Web User Interface, please read the section on Using the Web Application in the user documentation. At present, there are still some known features available in the Java Swing User Interface that are not yet available in Web User Interface of Compiere 3.2. Most of these features are scheduled for a future release. The following features are currently Not Available in the Web User Interface. However, they are fully functional in the Java Swing User Interface: The known features in the Java Swing User Interface that are not yet available in the Web User Interface include: Accounting Dimensions Windows used to set up Account structure. Work Flow Editor A form available from the Main Menu used to create or modify a Workflow. Resource & Schedule Info Windows Info Window available from the View menu to view Scheduled Resources. Resource Assignment A Form used to schedule a resource accessed from the Assigned Resource field in a Sales Order, Project, or Expense Report. Personal lock A security feature accessible from the toolbar used to lock a specific record to keep the record private. It is also used as a method to set security access rules for specific records. Archive Viewer A window used to view the Archived Records. Records or Documents can be archived via the toolbar from the document viewer or automatically via a setting available in the tenant window. Ability to print mass shipments A process available from the Main Menu used to print multiple shipments. Print from info windows A button accessible from any Info window used to print a screen shot of the information. Drill down on reports Interactivity on Reports which enables you to view a different report from a drill menu where a selected record is used. Ability to email documents/reports as attachment A button available from the toolbar of any report or document that opens an e-mail dialog box with the report attached as a.pdf file allowing users to send the report via e-mail. Sizing / Moving of columns in grid view / Info windows A mouse function that allows users to expand and contract columns as well as modify the column positions in the Grid view of a window or any Info Window. Product attribute grid A form available from the Main Menu which allows users to select an Attribute and view a grid of which products are available with the selected attributes.

Important: The Firefox Browser 3.0 is recommended when using Compiere Release 3.2 with the web user interface.
When using Internet Explorer 7.0, verify the options: Always switch to new tabs when they are created and A new tab in the current window are enabled: Under Tools> Internet Options> General Tab, open the Tab settings.
Fixed Issues for Compiere 3.2
The following is a list of the issues that have been fixed in Compiere 3.2.

Compiere Case Number

10018217 10018220

Description

The Last PO and last Invoice Price on the product Window. Swing UI - Menu Workflow Activity Tab. In the Replenishment Report, the process isn't including the Order Pack Qty correctly. It is ordering 1 pack too many. Replenishment report includes: a) Products that are discontinued b) Product > Purchasing records that are discontinued The replenishment report should ignore these. The Scheduler runs at unexpected times and slows down DB dramatically. On a "Bank Statement", when you "Create lines from" payments, the accounting date is not retrieved from the payment. RV_Payment UnAllocated The "UnAllocated Payments" reports displays all payments for which no allocation lines exists. The Invoiced Quantity is incorrect when creating an Invoice from a Material Receipt of a closed Purchase Order. Transaction support fails to work at all with EDB 8.2 on 3.0.2. When a rollback is issued the db retains the saved record. Please see the attached java class. When creating a location for a business partner; the default country is china, which displays without the "State" field. If this is changed it to Australia, the "State" field still doesnt appear. This results in not being able to input the address. Scheduler doesn't consider skip days. In the BankAccount Tab of the Bank Windows, no organization is proposed on Web UI. Lookup.run: C_Location.C_Location_ID: Loader - Too many records [45] MAX_ROWS is set at 10000 in MLookup.java Our C_Location table has more tha 12000 records. Double allocation lines are created when the Payment and Invoice ID are set to null. The double allocation lines have also caused the wrong Open balance of the Business Partner. Running the Validate Business Partners process didn't help. The allocation uses the transaction date of the payment for both its transaction and accounting date and so it is in the closed period and can not be completed. Sales Rep info window, Invoices for the given Sales rep are not displayed. Table and Column window Reference key needs to be mandatory when the reference type is Table.

10019141 10019216

10019280

10019460

10019593
Product Enhancements for Compiere 3.2
The following is a list of the enhancement Requests that have been completed in Compiere 3.2.

Product Enhancement

10016095
The product attribute pop-up window in the web UI is formatted in a not-so-ideal way. It starts with a checkbox called, "Edit Record" and a button called "Select Existing". Following are the user defined attributes. After which are a few more Compiere fields like "Guarantee Date", "Cancel", "OK". The problem is that these just wrap 3 to a row no matter what. So the first user-defined attribute is on the same line as the "Select Existing" button - They should start on a new line. Similarly an end line should follow the user-defined attributes, before the Compiere fields. Import Invoice and Import Order do not have the ability to import a line with a charge, only products. Would like this as an enhancement. Option to disallow negative Inventory at the warehouse level. If selected, the system will prevent the on-hand balances from being driven negative. In the web UI, the callouts do not cascade as it does in the swing UI. Credit Check code while preparing a shipment creates a heavy CPU load on the oracle server.

10019300 10019327

Known Issues in the Migration Process
Warnings and Error Messages you may see during the Migration steps.
Migration Issues Warning/Error Messages ORA-00001: unique constraint. violated ORA-01408: such column list already indexed ORA-01440: column to be modified must be empty to decrease precision or scale ORA-02296: cannot enable ORA-02275: such a referential constraint already exists ALTER TABLE S_ResourceType MODIFY ChargeableQty NUMBER(10) DEFAULT NULL Failed sql statements ERROR: cannot alter type of a column used by a view or rule Detail: rule _RETURN on view rv_asset_delivery depends on column "lot" - ALTER TABLE A_Asset_Delivery ALTER Lot TYPE VARCHAR(255) , ALTER Lot SET DEFAULT NULL Component migration not needed Unable to get migration steps WorkerData - java.lang.NullPointerException Unable to execute postgres/oracle function scripts Failded to run function scripts sql No component migration needed Unable to get target result set: SELECT.FROM AD_Role WHERE Name = 'GardenWorld Admin' - java.sql.SQLException: ORA-00904: "OVERRIDERETURNPOLICY": invalid identifier Unable to get target result set: SELECT.FROM AD_Column WHERE AD_Table_ID = 783 AND ColumnName = 'R_Request_ID' - java.sql.SQLException: ORA-00904: "ISRECURSIVEFK": invalid identifier No Key & No Parent - Table AD_RecentItem While executing RUN_Setup, refreshing an existing instance ===========> DB_PostgreSQL.getDataSource: DB_EnterpriseDB[null] [12] java.lang.IllegalArgumentException: DataSource with name 'CompiereDS' already exists! While executing RUN_Setup -----------> ModelValidationEngine.addClasses: GardenWorld: compiere.model.MyValidator - java.lang.ClassNotFoundException: compiere.model.MyValidator [12] -----------> ModelValidationEngine.addClasses: Extended Units of Measure: org.compiere.xuom.XUOMModelValidator - java.lang.ClassNo tFoundException: org.compiere.xuom.XUOMModelValidator [12] Error Dont have core when trying to install an application extension Database All All All All All EnterpriseDB Solution This is an acceptable warning message. This is an acceptable warning message. This is an acceptable warning message. This is an acceptable warning message. This is an acceptable warning message. This is an acceptable warning message.

No effect on the functionality. You may ignore this error.
No effect on the functionality. You may ignore this error
This is an acceptable warning message
Known Issues in Compiere 3.2
Issues you may encounter using Compiere 3.2
Issue Shortcuts: Firefox 3.0 on Windows, shortcut key 'Alt-Equals' does not expand in the Compiere Web UI. The Ctrl+M shortcut is not working in the Business Partner window and the Product window including all Product tabs except for BOM tab. Report Accounting Fact Details has been renamed to Accounting Fact Details Report. Keyboard Shortcut: F10 (Focus on the main auto completion menu) Issue: Mouse prompt is not visible in Main Menu field, so alternate key is suggested. Alternate Key: Ctrl+Alt+M. Keyboard Shortcut: F1 (Help) Issue: Brings up 2 help menus, Compieres help popup and IEs help popup Menu and close button is only half visible. Alternate Key: Ctrl+Alt+H. Keyboard Shortcut: Alt = (Expand) Issue: Not currently working. No Alternate Key Keyboard shortcut in Web UI Alt =, which is used to Expand All is not working in windows Firefox 3. When the workflow or workflow node responsible is set to Organization it does not get routed to the supervisor defined for that organization. The workflow stays in a suspended status but is not designated as a task for any user to complete. Views information gets over-written when saving more than 4 views. (Web) The footer of reports generated from the web UI shows some of the JDBC connection info. When items are removed (moved to the left pane) in Sort order of Business View they should not appear in Format Item tab. Currently you have to remove them two times (once in each tab.) In Work Order and Warehouse, Org * is not a valid value. Users must pick a specific org. However, if you login and select * as the org in the Role login window, you are able to save work orders and warehouse with org *. Log into an instance. Use Zoom to open another instance Go back to original (do not close second instance) Go back to second instance when the log in has time out. Log back in with the same user name, password and role. Go back to first browser and you get a message that you have logged in with a different role (this is not accurate) and to log off. When you log off you cannot log back in as you do not get a db connection (language field is blank.) You have to reload the browser The implementation of trees in the Web UI is not completed as of the 3.2 release. Chrome pop-ups: When you run a report using chrome, the report is opened in a new window and the new window is located at the bottom of the screen. Clear Browser cache before opening Compiere in the Web UI. All Web UI users need to clear their browser cache and reload the URL before re-starting Compiere 3.2 after migration. View customizations not migrated to Release 3.2. Added one user-maintained column as a view component and modified from clause of the view and marked as a customization, but these changes from 3.1 were not migrated to 3.2. They had been migrated to 3.1 from 3.0.3. Occurred in Production Compiere instance with view C_PaySelection_Check_v. In some instances when generating a Financial Report in the WebUI a print format called Create Report will be generated. Once generated it is then used in every Financial Report. If you delete the print format called Create Report for the tenant and then the correct print format will either be used for your Financial Reports. The Zone window: cannot add Locator (child tab) in grid view mode. BVL does not work on EnterpriseDB Database All All All All All All All All All All All Solution Open Open Open Open Open Open Open Open Open Open Open

All All All

Open Open Open

All All EDB

For a current list of open issues please query the list of public requests from our request system http://www.compiere.com/support/support-requests.php.

Appendix A

Compiere 3.2 Migration Instructions
- A valid Support contract - Sun Java JDK 6 (SDK) Update 5 or later (not just JRE) - Database Oracle XE, Oracle 10gR2, Oracle 11g or EnterpriseDB Postgres Plus Advanced Server 8.3.

Migration

The Compiere Migration Management solution allows the following:
Migrate from any release directly to Compiere 3.2.
Information: This is an optional convenience service. A skilled DBA monitoring SVN changes and/or with the help of a change management system can do this as all scripts used are available in SVN. Another alternative are EAI tools. The added service is the packaging and a database health check.
Preserving Customizations
Compiere will not modify any customizations - as long as the customizations are marked appropriately! By default, all added records in the dictionary will have the entity type "User Maintained":
- In the Change Audit window, mark the changes as Customizations before running the migration. Tip: Alternatively, changes may be applied manually. - Before performing the migration, run it in the test mode to ensure all customizations will be preserved.

Migration Steps

Migration Consists of the Following steps:
Preparation Test Mode Migrate to a New Release Post Migration Steps

Preparation

Use the following steps to prepare for the Migration:
Server needs to have access to the Internet. Stop the application server by executing utils/RUN_Server2Stop Backup the database If you are running EnterpriseDB 8.2 or older you must upgrade to EnterpriseDB Postgres Plus

Advanced Server 8.3

Rename COMPIERE_HOME/jboss directory Delete COMPIERE_HOME/data/compiere_'CPRO'.car file Delete COMPIERE_HOME/data/compiere_'XUOM'.car file

Test Mode (optional)

First, run the Migration Program in Test mode. This allows the ability to evaluate the actions taken when running it against the database. Please note that the first step (resolve ID conflicts) will not show the correct future IDs in test mode. If the program marks certain wanted tables for deletion, then create the table in the data dictionary (Window Table/Column) with the Entity Type User or Application. If the program marks certain wanted columns for deletion, make sure that the column has the Entity Type User or Application. If the wanted column has the Entity Type Data Dictionary or Compiere and it is marked for deletion, then copy it under another name and mark the new column as Custom or Application. The same applies to windows, tabs, fields, etc. Mandatory User or Application Columns must have a default value defined in the database, e.g. ALTER TABLE someTable MODIFY (myColumn DEFAULT 'myDefault'), otherwise adding new records will result in an error.

7) Next, read and accept the Compiere Public License agreement. Hint: You might get more than one license agreement, depending on the applications that you are installing. Notice that XUOM is a sample application extension
8) If you are installing Compiere Professional, you will receive a Commercial license agreement. Please read and accept the license agreement, in order to continue. Hint: You might get more than one license agreement, depending on the applications that you are installing.
9) If you are installing Compiere Professional, you will also receive a Commercial and Evaluation license agreement. Please read and accept the license agreement, in order to continue. Hint: You might get more than one license agreement, depending on the applications that you are installing.
10) Click on Start File Installation
11) When the File Installation has completed click on Start Migrate Database.
12) Provide the following information exactly as it was registered in the Compiere Web store and click Check License to validate your asset information (Note: This information may already be populated if it was entered in the system window) - System Name - Registered Email - Password
Tip: If you get the Core Invalid error after selecting the Check License button, that is an indication that you did not select the appropriate action for the Core component in step #5. In this case, Exit the setup and support windows and execute RUN_setup again selecting the Core plus any other components to install. 13) Click on Start Migration.
14) At the Compiere Version Migration Prompt, click Yes to proceed with the Migration.
15) Unselect the Test Only option, and click Start.
16) Confirm that you have a current back up of your database
17) Confirm that the Source and Target database versions from the Compiere Version Migration window are correct.
18) Verify that the migration finish with no errors and the message After Migration - DONE is displayed. In case you get any errors, please be sure to review the list of known issues listed in this document before logging a service request.
19) If you have a Compiere Professional Edition license, execute utils/RUN_Support and click Check License to activate your license. Tip: There is no need to click the start migration button.
20) After you have pressed the Check License button you should be able to see if your Professional License has been activated.
21) After Compiere Professional license has been updated you may click the X to close the window. Hint: It is NOT necessary to click the Start Migration at this point. 22) To start Compiere in the Web UI after migration, it is required that all Web UI users clear their browser cache first.

Note: After migration, (re-) apply the language packs when needed.
Post Migration Steps for RMA/RTV
This step is only relevant if you plan to use the new returns functionality and you are migrating from 2.6.3 or older.
Compiere now has explicit return transactions. We discontinued the previously seeded "Return Material" functionality. In the "Document Type" window you need to do the following for every Tenant/Client: 1) Delete or de-activate the document types Return Material MM Customer Return Hint: This is discontinued functionality
If you choose to deactivate the obsolete document types (as opposed to deleting them), please rename the document type 'MM Customer Return' to an alternate name (For eg., ' ** MM Customer Return ** Do Not Use **') so you can successfully create the new document types detailed below. 2) Create Return Document Types MM Vendor Return - Copy "MM Receipt" and set Name - Select Return Transaction - De-Select Counter Document flags - Optionally select Confirmations Vendor RMA - Copy "Purchase Order" and set Name - Select Return Transaction - De-Select Counter Document flags MM Customer Return - Copy "MM Shipment" and set Name - Select Return Transaction - De-Select Counter Document flags - Optionally create a special Document Sequence and or Confirmations Customer RMA (Copy Standard Order - Copy "Standard Order" and set Name - Select Return Transaction - De-Select Counter Document flags - Select AR Credit Memo for Invoice Document Type - Select the created MM Customer Return for Shipment Document Type - Optionally create a special Document Sequence Unfortunately, we cannot do the above steps automatically as this is configuration specific user data. Tip: For an example of a set-up, please check GardenWorld in a fresh install or in a newly created Tenant.

Appendix B

Compiere 3.2 Installation Instructions
This is for a new installation of Compiere. If you already have installed a previous version of Compiere, please refer to the Migration instructions.
- Swap Space: > 1GB - Database Oracle XE, Oracle 10gR2, Oracle 11g or - Memory: > 512 MB - Recommended: > 1 GB EnterpriseDB Postgres Plus Advanced Server 8.3. - TCP/IP connection Important: It is mandatory to use a Unicode character set - Network setup with DNS server and a domain. - Database approved Linux Operating System, Tip: Do not use IP addresses. Windows 2003 or Windows XP - Internet access - Disk Space: > 5 GB (includes database) Update: Compiere 3.2 now includes version 4.2.3 of JBoss Application Server. For more details please see the JBoss release notes. Hint: Notice that the screenshots in this document refer to the installation on Windows, but the process is the same for Linux, except for the paths (e.g. C:\Compiere2 vs. /Compiere2) and the extension of the scripts (.bat vs.sh)

Appendix E

Fixed Issues for Compiere 3.2.1
The following is a list of the issues that have been fixed in Compiere 3.2.1

10018401 10018527

Create Material Receipt from PO will not set Date Ordered SO line availibility not checked on new warehouse Able to Void Purchase Order After Matching Printing accounting tab of a tax declaration Migrate Copy Client errors GL Import Accounting currency rounding Specsavers issue Ctrl-Alt-Plus Expand Ctrl-Alt-Minus Collapse, these shortcuts don't work. Virtual Column Not Available on Report Order reference and description is being overwritten when a BP is selected. As these fields are sequentially before BP it is likely that a user will enter those before entered a BP, so it should only take the values from the BP default if the fields are blank. Regression Web UI - no place to change/ switch auto printing off. It seems to always print to the printer regardless. AD_Role.UserLevel: default not used - Has two spaces before the O (correct) The AD_Role.Userlevel column has a dictionary specified default of " O" (Organization). The default value is not being used for new records. (Maybe it has something to do with the fact that the field is 3 characters long, and the value in the list reference is " O" (2 leading spaces) as opposed to the AD_Column default "O".) Tax Correction: Error when the discount/write-off is applied on an invoice with prices including taxes. Tax Correction : Error when an invoice based on a different currency than default currency From Price List / PL version / Product Price, start the report. Then click the Filter button to clear all filter. You will get all prices. Customize the Print Format so that 3 columns are shown: PL Version, Product, and Price,. Group by on the 2 first columns Create a Sum on the third column. The result is a bug. We have an X / A Sub total but we do not have a X / B SubTotal and the Price 12 is totally affected to the Y / B Subtotal making it 26. But the Y total is 14 Limit some location fields, for example I want address4 field limited to 24 characters. I tried to modify the C_Location table address1 column to 24 length string without effect. After looking source code, I found that this window is hard-coded (VLocationDialog class). As a temporary solution, I changed the address4 declaration with a VString instead of CTextfield and was able to limit the size, but it's a dirty hack. When creating a business partner group, a Vendor Return Policy can be set. When creating a Business Partner of the type vendor, the default setting for Vendor Return Policy on the BP Group is not copied to the Business Partner. In the REQUEST screen, under the REFERENCE group, the field ORDER is wrong - it zooms and creates a Purchase Order when it should be a Sales Order. Re-Activated Sales Order does not print order but the reversed invoice. Print Format on Web UI are not sorted by "Default" field. Cannot set up a Default Print Format amongst different one so that COmpiere show me this one when I start the Report button When duplicating a bank A record to a new bank B, in Swing and Web UI, the location ID is also set to the same address. Afterwards, when changing the address of bank A, bank B address is also changed, and vice-versa. This issue is due to the common Location_ID, and we have no way to fork. (Other than resetting externaly in Oracle). Either, you also duplicate the address, or you set the duplicated address bank to null. We are rewriting all official documents with JasperReport. When an invoice is printed through a normal process, it works, but when printed through the print button of the invoice itself, it fails. (This on WebUI Only; on Swing, Jasper never works) Replicated: RV_OpenItem only exludes docstatus draft "DR" and doesn't take into account the workflow status "in progress" "IP".

10018793

10019058

10019309

10019339

10019452

10019512 10019554

10019569 10019571

10019581

10019614 10019627

10019638

10019721

10019745

10019877

In desktop version, we can print preview any document we want to print and then decide either to print it or not. While in browser version, when we want to print the document, Compiere will automatically do two things: 1. Create pdf for the document (which we can use it as preview printed document also) 2. Print to specified printer. The second one is cumbersome if we want to generate pdf only file (let say if we want to email it) because it also print the document. Is there anyway the web version let the user decide whether they want to print it or not? When using the Generate Invoices process, the system checks the field "Document Type for Invoice" on the Sales Order Document Type to know what Document Type to generate the invoices. However, there is a bug in that when 2 or more sales orders are being used in the Generate Invoice process, and each sales order is for a different document type, and the document type for invoicing is different, the system is consolidating the invoices into 1 instead of creating 1 per invoice document type. When clicking on the day, week, month or year button of the Sales Order lookup, it seems that Compiere wants to return all the records for the Sales Order. The same happens when you click on the week, year, etc buttons. See screenshot. I've defined different printing formats for "Standard order" for different customers. It's ok with the swing UI, because I can select the printing format before I print. But with the web ui, I have to go to the "Document type" window to change the print format which wastes a lot of time. Is it possible to select the printing format before printing in the web ui just to generate reports. Functions boomqtyonhand , boomqtyoredered y boomqtyreserved are using integer. The oracle equivalents uses NUMBER. That produces errors in edb. Process PricelistCreate uses currencyrate and it is reported as not found, but it is in the edb database. If you open a window that cannot be updated and then search and display a record that can be updated all fields are protected. If you refresh the window, the fields are updatable. If you open a window that has no current records (e.g. Document) and then search all, documents that are completed show as updateable. Logging in using the Finish language, the Web UI isn't displaying the currency and dates correctly where the Swing UI does. Seems to be an issue with all languages and currency and date displays Swing UI: Date dd.mm.yyyy, Currency 000,00 - Web UI: Date mm/dd/yyyy, Currency: 10,000,000.00. The same applies for English (UK) date formats. The Web UI seems to apply American formats for date and currency. Account info is available in web UI to users who do not have access to accounting info. More than one accounting schema. In financial reports (trial balance, statement of account, accounting fact,.) , in the dialog box just before execution, if you select a specific accounting schema, Account combo list is not filtered accordingly to selected accounting schema. It is therefore impossible to identify to which acocunting schema belongs a specific account in the list. (and we can had that combo doesn't display all accounts when combo capacity is over) Very expensive SQL in production, taking up to 38 minutes to execute, and with a ridiculous CBO cost of 1,622K GROUP BY in Exists Clase. UPDATE Fact_Acct_Balance ab - SET (AmtAcctDr, AmtAcctCr, Qty) = (SELECT COALESCE(SUM(AmtAcctDr),0), COALESCE(SUM(AmtAcctCr),0), COALESCE(SUM(Qty),0) FROM Fact_Acct a SQL seems to be from FinBalance.updateBalance line 162 After removing the GROUP BY in the WHERE clause the cost comes down to 551. Say a column had a value format of 00:00. This is useful for storing a time value in a string field. The value format would accept the input correctly, but when it was saved and the record requeried, the value was not displaying at all - it showed "00:00" even though in the db it was "01:00". EMail to support contains database password in Swing UI. It looks like the "EMail to support" message contains the password of the database schema owner. This message is also visible to the user. Processing a credit card payment from an SO. If you are using the payment function from the SO, the Online button will create a payment each time you click it and clicking the Ok button will also create a payment (does the same thing as the online). So while the payment is processed successfully or you receive a failure message, there are at least two payments created each time you try and use this payment function from the SO. I would think that after processing the payment (clicking the Online button) the button would disappear or be read only. And the Ok button would not create a payment but make the payment pop up disappear. Problems with some Keyboard Shortcuts. The new Key board shortcuts are as follows: Alt-Minus Collapse Alt-Equals or Alt-Plus Expand Alt-PageUp Previous Page/Record Alt-PageDown Next Page/Record For more information on Keyboard Shortcuts, please refer to the User documentation.

Compiere 3.2 Installation Instructions Windows System - EnterpriseDB
Compiere Learning Services Division
Copyright 2008 Compiere, inc. All rights reserved www.compiere.com

Table of Contents

Compiere 3.2 Installation Instructions EnterpriseDB Windows System
Compiere 3.2 - Installation Instructions EnterpriseDB Prerequisites Database Installation Compiere 3.2 New Installation Instructions Java Installation Edit the Path Download Compiere Complete Server Setup Start Compiere
Compiere Learning Services
Copyright 2008 Compiere Inc. All rights reserved
Compiere 3.2 - Installation Instructions EnterpriseDB

Prerequisites

- Database approved Windows Operating System: Windows 2003 or Windows XP - Disk Space: > 5 GB (includes database) - Recommended: Hardware RAID 10 - Memory: > 512 MB - Recommended: > 1 GB - TCP/IP connection to Clients Hint: It will ease the installation tremendously, if you have your network set up with DNS server and a domain (actually a must for non-Windows environments). Check with your system administrator - do NOT use IP addresses, use names.

Database Installation

1. Install Database this document will use Postgres Plus Advanced Server 8.3. 1) First, login as the Administrator or someone in the Administrator group. 2) Get the Postgres Plus Advanced Server 8.3 from the following website: http://www.enterprisedb.com/products/download.do Make sure download the Postgres Plus Advanced Server 8.3 for Windows 3) Download the executable file appropriate for your OS.
4) The welcome page displays. Hint: you may be using a later version. 5) Select the Next button to continue with the Installation.
6) Review and accept the License agreement. 7) Then select the Next button to continue.
8) Provide a Product key for either the Full or Evaluation License of EnterpriseDB or simply select the Express License Option. 9) Select the Next button to proceed.
10) Select the Oracle-Compatible defaults and samples option. 11) Select the Next button to continue.
12) Select the destination folder by selecting the Browse button. Hint: This document will assume C:\ is the selected directory. 13) Select the Next button to continue.
14) Under EnterpriseDB features, Accept the default selections. 15) Select the Next button to continue.
16) Take note of the following instructions provided by EnterpriseDB on Oracle Client connectivity. 17) Select the Next button to proceed.
18) Enter and confirm a User ID and Password for the System Administrator. Hint: The User ID and Password entered here will be used to run the Database Server. 19) Then select the Next button to continue.
20) Next, enter and confirm a User ID and Password for the Database Administrator. Hint: It is acceptable to use the System Administrator Password entered in Step 17. (This is optional) 21) Select the Next button to continue.
22) Select the appropriate option for Dynamic Tuning. 23) Select the Next button to continue.
24) Under Advanced Options, accept the default options. 25) Select the Next button to proceed.
26) Review the Installation Settings. Select the Back button to make changes if necessary. 27) If the Installation settings are correct, select the Install button to start the Installation.
28) When the Installation is complete, the following confirmation window will display: 29) Check the Launch Developer Studio Option and select Finish to complete the Installation.
30) Once the Developer Studio opens, enter the System Administrator User ID and Password entered in step 17. Note: This confirms the Database Installation.
Compiere 3.2 New Installation Instructions

Java Installation

1. Download and install Sun Java JDK 6 (SDK), Update 5 or a later version. Important: The Compiere Server requires the JDK (not just JRE).

Edit the Path

2. Add EnterpriseDB path into PATH 1) Go to Control Panel > System >Advanced > Environment Variables. 2) Add EnterpriseDB path to the end of the PATH environment variable (e.g. C:\EnterpriseDB\8.1\dbserver\bin)

Download Compiere

3. Install /Setup Compiere Server (this includes the Client as well) 1) Download the current version of Compiere: Download Compiere. (3.2 or higher) 2) Extract the.zip file. The steps shown assume that you extract to the root directory, resulting in a COMPIERE_HOME of C:\Compiere2 in Windows or \Compiere2 in Linux. 3) Verify that the bin directory for your database executables is included in the PATH. 4) Execute the script $COMPIERE_HOME/RUN_Setup. Note: if the following window does not display, please ensure that the following are updated. Add the folder where you have installed JDK 1.6 at the beginning of the PATH system environment variable. Set the JAVA_HOME system variable to the location of your java installation (e.g., C:\Program Files\Java\jdk1.6.0_5) Set the COMPIERE_HOME system variable to the path of your Compiere installation (e.g., C:\Compiere2)

5) Select Database Type of postgreSQL. 6) In System Password, use the Database Administrator User password. 7) For Database Password, use compiere (or any password.) 8) Enter or update the Parameters as necessary. 9) For Server Names, i.e., (Application, Database and Mail) use the DNS name of the server.
Hint: Do not use localhost (127.0.0.1) or IP address.
10) Select the Help button, for
information on any field.
11) Select the Test button to check the parameters. Note: Parameters must be
verified in order to save
12) If an entry is unverifiable, it will display with a red X. Correct the entry and reselect Test/Save. 13) Once all fields are verified, click the Save button to proceed.
14) At the prompt enter your company information as appropriate and verify that the common name is the address of your application server. Once all fields are complete, click ok to continue.
15) Next, read and accept the license agreement. Hint: You might get more than one license agreement, depending on the components that you are installing.
16) A default security key will be generated, click Ok to continue.
The Next step is to provide the Subscriber Information. Current customers should provide the subscriber information (System Name, Email and Password) exactly as it was registered in the Compiere Web Store to get a complete list of applications. Click Check Available Applications to get a list of applications that are available to be installed. Tip: Community Edition users may leave the fields blank and click Check available components to install the Community Edition.
Select the applications that you would like to install. You can include additional applications by using the button Add Application. By default all available applications will be installed. If you do not wish to install one of them you should change the action field from New Install to -None-. Notice that Compiere Core is a Mandatory Prerequisite and must be selected. Select the OK button to continue
Next, read and accept the Compiere Public License agreement. Hint: You might get more than one license agreement, depending on the applications that you are installing.
20) Then read and accept the Compiere Commercial License agreement. Hint: You might get more than one license agreement, depending on the applications that you are installing.
21) After accepting the license agreement the following window will display:
22) Select Start File Installation. Important: At this point, you must be connected to the internet to continue or the installation will not succeed. 23) Once the file installation is complete, select Start Create New Database.
Note: If you already have a Compiere database in your system, you will be presented with a split panel after Start Server Install. Click the left panel (Start DROP OLD and create NEW Database) if you want to replace the existing database with the new database.

24) At the prompt select Yes to Drop the existing Database and create a new database.
Warning: If you choose to replace the existing database, all data in the existing database will be removed. 25) Verify that you see a 10: ** Finished message at the end of this step. Then a new window should pop-up to do the license validation.
Hint: If you only intend to use the Community Edition of Compiere 3.2, you may skip the following steps and go to the Application Server section. Important: For customers with a valid support contract with Compiere, this is a required step to ensure that the features associated with the support level are enabled. If you are a customer and do not have a web store login, please contact your system administrator or Compiere Support first. If you are not a customer and would like to obtain a trial license for the Professional Edition, please Contact Us and request the files for the Professional Edition. 26) Provide the following information exactly as it was registered in the Compiere Web store and click Check License to validate your asset information. - System Name (name provided in the web store registration) - Registered Email (email address provided in the web store registration) - Password (web store password)
27) To verify your license, click the Check License button. Tip: Do not click Start Migration. Notice that internet access is required to validate the license information. 28) Review that your license information has been validated.
29) After Compiere Professional license has been verified, click the X to close the window.
Note: If the error You do not have an appropriate license to use this feature appears when starting the Web Application, execute utils/RUN_Support to validate your license and restart the application server.
30) Close the Support and the Setup windows.

Complete Server Setup

4. Start the Compiere Application Server 1) You can now start the JBoss based Compiere Application Server via RUN_Server2 in the $COMPIERE_HOME/utils directory. 2) There should be no errors. Check the logs in $COMPIERE_HOME/jboss/server/compiere/logs to verify this. 3) Common problems include ports already in use 17:41:09,085 ERROR [NamingService] Could not start on port 1099 java.net.BindException: Address already in use: JVM_Bind at java.net.PlainSocketImpl.socketBind(Native Method) There is another program using port 1099; Stop it and restart Run_Server2 or setup Compiere to use another port in RUN_setup. Likely port conflicts: 80 - You have some other web server running (or you need privileges under Linux/Unix) 8080 - The Oracle Database uses that 1099 - Often used by IDEs for debugging

Start Compiere

5. Start the Compiere Client 1) Start the Swing client by double clicking on the Compiere shortcut in your desktop or by executing RUN_Compiere2 from the $COMPIERE_HOME directory. Default users and passwords for the sample Garden World application. GardenUser/GardenUser GardenAdmin/GardenAdmin System/System SuperUser/System

2) Alternatively, if you have access to the Professional Edition, you can launch the application from the browser by
using the URL: http://server:port/apps (e.g. http://mycompany.com:80/apps)
Information: For additional information see the Compiere home page http://www.compiere.com.
Compiere Learning Services Copyright 2008 Compiere Inc. All rights reserved 17