Appendix B _________________________________________________________________________________________________23
Compiere 3.2 Installation Instructions _________________________________________________________________________________24
Prerequisites ________________________________________________________________________________________________________ 24 Database Installation __________________________________________________________________________________________________ 24 Java Installation ______________________________________________________________________________________________________ 24 Download Compiere___________________________________________________________________________________________________ 24 Run Application Server_________________________________________________________________________________________________ 31 Start Compiere _______________________________________________________________________________________________________ 32
Appendix C _________________________________________________________________________________________________33
Compiere 3.2 Application Extensions _________________________________________________________________________________34
Registration of Application Extensions Application Provider (Partner) ___________________________________________________________ 34 Creation of Application.car file Application Provider (Partner) _________________________________________________________________ 36 Installation Application Consumer (Customer) _____________________________________________________________________________ 38
Appendix D _________________________________________________________________________________________________39
Delete Client and Delete Client Transactions ___________________________________________________________________________40
Appendix E _________________________________________________________________________________________________42
Fixed Issues for Compiere 3.2.1 ______________________________________________________________________________________43 Product Enhancements for Compiere 3.2.1_____________________________________________________________________________45 Known Issues in the Install Process of Compiere 3.2.1 ___________________________________________________________________45 Known Issues in Compiere 3.2.1 _____________________________________________________________________________________45

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.

Always select Compiere Core when installing or migrating any additional applications.

All EnterpriseDB

This is an acceptable warning message This is an acceptable warning message This is an acceptable warning message
Select Reinstall/Migrate for the Core component when installing new application extensions
Known Issues in the Install Process
Warnings and Error Messages you may see during the Import steps.
Install Issues Warning/Error Messages -----------> g.a: DROP SEQUENCE T_Spool_Seq -----------> g.a: ORA-02289: sequence does not exist -----------> DB_PostgreSQL.convertStatement: Convert error! Converted statement Number=2 (CREATE OR REPLACE VIEW -----------> DB.saveError: DBExecuteError - ORA-00001: unique constraint (COMPIERE.C_REGION_NAME) violated [15] -----------> MRegion.saveNewInsertSQL: Not inserted - C_Region [15] -----------> ProgressPanel.publish: Unable to import Region, requires UNICODE database [15] ===========> DB.executeUpdate: INSERT INTO C_Region (AD_Client_ID,AD_Org_ID,C_Country_ID,C_Region_ID,Created,CreatedBy,Description,Is Active,IsDefault,Name,Updated,UpdatedBy) VALUES (0,0,216,438,TO_DATE('2006-02-23 15:43:34','YYYY-MM-DD HH24:MI:SS'),0,'???(Miyasaki)','Y','N','???',TO_DATE('2006-02Copyright 2008 Compiere Inc. All rights reserved

Database

Solution
This is an acceptable warning message. This is an acceptable warning message. These are acceptable if your database is not set for Unicode.
Install Issues Warning/Error Messages 23 15:43:34','YYYY-MM-DD HH24:MI:SS'),0) [null] [15] java.sql.SQLException: ORA-00001: unique constraint (COMPIERE263.C_REGION_NAME) violated; State=23000; ErrorCode=1 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:305) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:272) At the very end of the install process or when manually executing utils/RUN_Support 13:07:55.094 Compiere.startup: Client lap-fr/10.104.139.177: C:\Compiere2 - Java HotSpot(TM) Client VM 1.5.0_11-b03 - Windows XP 5.1 Service Pack 2 [15] Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at javax.swing.plaf.basic.BasicScrollBarUI.layoutHScrollbar(BasicScrollBarUI.java:676) at javax.swing.plaf.basic.BasicScrollBarUI.layoutContainer(BasicScrollBarUI.java:775) at java.awt.Container.layout(Container.java:1401) at java.awt.Container.doLayout(Container.java:1390) at java.awt.Container.validateTree(Container.java:1473) at java.awt.Container.validateTree(Container.java:1480) at java.awt.Container.validate(Container.java:1448) at javax.swing.RepaintManager.validateInvalidComponents(RepaintManager.java:379) at javax.swing.SystemEventQueueUtilities$ComponentWorkRequest.run(SystemEventQueue Utilities.java:113) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:209) at java.awt.EventQueue.dispatchEvent(EventQueue.java:461) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:24 2) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:163) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:157) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:149) at java.awt.EventDispatchThread.run(EventDispatchThread.java:110) Error after clicking Save on the RUN_Setup window ===========> CConnection.createConnection: jdbc:oracle:thin:@//lap-fr:1521/xe, (1) AutoCommit=true,TrxIso=READ_COMMITTED - ORA-010 17: invalid username/password; logon denied [12] -----------> CPreparedStatement.<init>: ALTER TABLE AD_System MODIFY Summary NVARCHAR2(2000) [12] java.lang.UnsupportedOperationException: No DBConnection at org.compiere.util.DB.getConnectionRW(DB.java:228) Error installing the sample application extension XUOM Failed sql statements: ORA-00955: name is already used by an existing object - CREATE INDEX M_Product_ProductCategory ON M_Product (M_Product_Category_ID) - java.sql.SQLException: ORA-00955: name is already used by an existing object Error installing the sample application extension XUOM Create Views ****************************************** Starting to create views for entity: XUOM Created view #1 for entity: XUOM Failed sql statements <<ERROR: ERROR: relation "m_product_expensetype" already exists - CREATE UNIQUE INDEX M_Product_ExpenseType ON M_Product (S_ExpenseType_ID) java.sql.SQLException: ERROR: relation "m_product_expensetype" already exists>> same error for other indexes <<ERROR: ERROR: constraint "fk208_10919" for relation "m_product" already exists - ALTER TABLE M_Product ADD CONSTRAINT FK208_10919 FOREIGN KEY (C_SubscriptionType_ID) REFERENCES C_SubscriptionType (C_SubscriptionType_ID) - java.sql.SQLException: ERROR: constraint "fk208_10919" for relation "m_product" already exists>> same error for other constraints

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.

Check List:

Server has HTTP (port 80) access to the Internet Compiere web store Asset - Support Contract

System Operation Steps:

Resolve ID Conflicts from Customizations/Extensions Synchronize Data Structure (Table/Column/Index/Constraints/.) Synchronize Data Content

Migrate to a New Release

Use the following steps on the Application Server box for migrating to the new release: 1) Be sure to delete or rename the existing jboss subdirectory (due to different JBoss version and configuration files.) Download and unzip/untar the distribution file, (e.g. Compiere_3XX.X.zip.) Tip: It is also possible to extract the distribution file into a new directory and copy your configuration files. Then change the COMPIERE_HOME environment variable to the new directory. 2) Execute RUN_setup. Verify all your environment settings and click Save to continue. If you get any errors in the parameters validation, youll see a red icon right next to the parameter with the problem; make the required changes, click Test to run the validation again and then click Save to continue.

3) The Compiere Public License Opens. Click Yes, I Understand and Accept to continue.
4) The following prompt will display describing your new Security Key. Click Ok to continue.
5) 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.
Note: To install additional applications once you have installed or migrated to the latest Compiere Core version, you must select Compiere Core plus any additional applications to install, and then run Migration.
6) Select the applications that you want to migrate and select the action Reinstall/Migrate. Compiere Core 3.0 is the main application that must always be installed or migrated to the latest release, but you also may choose additional applications provided by Compiere or any of our authorized partners. Tip: If you do not wish to install or migrate any of the applications listed, be sure to change the action to None- To install new applications change the action to New Install
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

login to the server and execute utils/RUN_Support to validate again your license and restart the application server.
31) Close any additional Setup and /or Support windows.

Run Application Server

3. Start the Compiere Application Server 1) Execute utils/RUN_Server2. 2) There should be no errors. Check the logs in $COMPIERE_HOME/jboss/server/compiere/log 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

4. 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.) Tip: For optimal performance, the Firefox browser is recommended for using the Compiere Web User Interface.
Information: For additional information see the Compiere home page http://www.compiere.com.
Copyright 2008 Compiere Inc. All rights reserved 32

Appendix C

Compiere 3.2 Application Extensions
This section is for Application Extensions in Compiere available as beta functionality in 3.2 for Partners. This framework will allow Partners to create application extensions that include both reference data and code, and can be distributed to their customers through Compiere. The rollout of the application marketplace is scheduled for the second half of 2008.
Registration of Application Extensions Application Provider (Partner)
Use the steps below to register for Application Extensions: 1) To register an Application Extension, log a Support Request with Compiere. 2) Login with the System Administrator role. 3) Open the Entity Type window (Application Dictionary => Entity Type) and create a new record.
Hint: Be careful not to modify the entities C, D, CPRO or XUOM. Important: Complete all the mandatory fields. For entity type, notice that names beginning with C and X are reserved for Compiere and you must use four characters.

Comments about optional fields: Version: The version of your extension. Usually 1.0 for the first version. Prerequisite version: The Compiere Core version that is required for this extension, e.g. 3.2. You need to use the exact text as defined for the entity type D. Prerequisite applications: The entity type of the applications that need to be installed in order to install this extension. For example, set it to CPRO if the extension must be applied on top of the professional edition. Classpath: List of additional jar files required for this extension. Model package: Specific model package from the jar files listed in the classpath field.
4) You do not need to enter any information on the Version, Modification, or Migration Step tabs. 5) Ensure that your System window contains your up to date information for your system and web store email/password information. 6) Click Register Application to send your request to Compiere. Tip: If an entity type with the same name has already been registered youll get an error Error: Already registered: XXXX. You will have to create a new record with the new entity type. Verify with Compiere that the new entity type that you plan to use is available. 7) Click Ok to start process.
8) Leave the defaults in place and click Ok to continue.
9) At this point the status will be pending approval from Compiere. A Compiere representative should contact you soon to confirm the registration or to ask any additional questions.
Copyright 2008 Compiere Inc. All rights reserved 35
Creation of Application.car file Application Provider (Partner)
Follow the steps below to create the Application.car file: 1) Make all the application dictionary changes using the entity type that you registered in the previous step. 2) Generate jar files for the custom code required by your extension. 3) After having your new Entity Type approved by Compiere; login to Compiere with the System Administrator role and query the entity type that you registered in the previous step and click Create Application File.

4) Click Ok to start process.
5) Provide the directory for the jar file directory.
6) The car file will be generated in the COMPIERE_HOME/data directory. The newly generated.car file will have a name of compiere_XXXX.car.
Important: The naming convention for.car files has changed, (e.g. compiere_CPRO.car prior to 3.2 is now compiere_CPRO.car in 3.2). If a customer unzipps the Compiere installation files into the same directory, it is possible to end up with both compiere_CPRO.car as well as compiere_CPRO.car. This in turn will cause Compiere Professional to show up twice in the installation window. To avoid this situation, customers will need to manually delete compiere_CPRO.car and compiere_XUOM.car from COMPIERE_HOME/data directory. These are the only two.car files that Compiere has distributed prior to 3.2. If a customer has created any additional.car files prior to 3.2, it is necessary to follow the same procedure for those.car files as well.
Installation Application Consumer (Customer)
Follow the steps below to install the Application: 1) After obtaining the car file for the application extension, copy it to the directory COMPIERE_HOME/data. 2) Execute RUN_Setup (see Appendix A for details on the setup information.) Important: Be sure to have internet connection available to be able to get the license terms for the application extensions that you plan to install. 3) When you get to the window to select the applications, besides the application extension that you need to install, also select the option Reinstall/Migrate for Compiere Core 3.2.
4) Then continue with the MIGRATION steps as usual. (See Appendix A for more details.)

Appendix D

Compiere 3.2 Delete Client and Delete Client Transactions
This allows you to remove unwanted tenants and transaction data that you might have added while testing the application. This is an existing functionality from previous releases, but the instructions are now different. To access this functionality you need follow the steps listed below. Complete the following steps to Delete a Client and Client Transactions: 1) Execute utils/RUN_Support. 2) Provide your system name, email address and password exactly as it was registered in the Compiere Web Store, and select Check License. 3) Update the source URL section. Then verify that the database is correct, and provide the Compiere user name and password. 4) Select Start Migration.
5) Click Yes to continue.
6) Select the operation Delete Client (all) or Delete Client Transactions. 7) Uncheck test only and select Start.
8) 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.

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.

Follow the instructions and then re-start the database. Oracle XE
Known Issues in Compiere 3.2.1
Issues you may encounter using Compiere 3.2.1
Issue Customers upgrading from 3.1 or older must delete or rename the COMPIERE_HOME/jboss folder before unzipping the binary distribution of Compiere to uptake version 4.2.3 of JBoss. For customers on 3.2.0 is is also recommended to do it because for Compiere 3.2.1 for performance reasons we have removed some JBoss services that are not used by Compiere. If you are having performance issues with the apps server when using the web UI, it is recommended that you tune your JVM parameters to the specific needs of your instance. As a starting point, you can set the following parameters: The best way is to add it to the CompiereEnv.properties file and execute RUN_Setup=>File Install COMPIERE_JAVA_OPTIONS=-Xms512M -Xmx1048M XX:MaxPermSize=128m -XX:NewRatio=3 -XX:NewSize=256m X:+HeapDumpOnOutOfMemoryError. If you don't want to execute RUN_Setup, change the appropriate line in myEnvironment.bat/sh and restart the apps server for immediate effect. Known issue for customers on 3.1 or 3.2 using BVL. If you have created BVL users with names that are not valid database users (i.e. names with spaces, special characters, etc.) and try to refresh your instance, the process will fail. As a workaround, update the the column Name in AD_EUL_Users to fix the names to comply with the restrictions on database user names. Database Solution

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