IBM Maximo Asset Management Release 5.

2 Patch 09

Release Notes

Note Before using this information and the product it supports, read the information in Notices on page 147.

This edition applies to version 5, release 2, modification 9 of Release Notes and to all subsequent releases and modifications until otherwise indicated in new editions. This edition replaces any previous edition of this document. Copyright International Business Machines Corporation 2007, 2009. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Contents

Chapter 1: Maximo 5.2 Patch 09 overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New supported components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Automated update process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Chapter 2: Installing the patch on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preparing to install the patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installing the patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Completing the patch installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1 1 1 1 1 2 3 3 4 5

Chapter 3: Installing the patch on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Preparing to install the patch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Installing the patch in X Window System mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Installing the patch in console mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Completing the patch installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Appendix A: Installing Maximo Enterprise Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 webMethods mxIntegration package updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Installing the webMethods package files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Appendix B: Building and deploying the EAR files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deleting the existing EAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . The EAR files to be rebuilt and deployed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building the Maximo EAR file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building the Maximo Help EAR files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building the Actuate EAR file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building the acadmin EAR file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Building the acweb EAR File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying the EAR files WebSphere Application Server 5.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Deploying EAR files WebLogic Server 8.1. SP6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Appendix C: Manually installing files of Maximo 5.2 Patch 09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Folder structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Manually updating the files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Lists of files to be manually updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 17 18 18 18 19 19 19 20 21 23 23 23 24

Appendix D: Updated .jsp files and scripts, and the autoupdate process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 The updated files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 The autoupdate process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Appendix E: Maximo 5.2 previous program patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updated .jsp files in Maximo 5.2 Patch 08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updated .jsp files in Maximo 5.2 Patch 07 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updated .jsp files in Maximo 5.2 Patch 06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updated .jsp files in Maximo 5.2 Patch 05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updated scripts in Maximo 5.2 Patch 05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updated .jsp files in Maximo 5.2 Patch 04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Copyright IBM Corp. 2007, 2009

29 29 29 30 31 31 32 iii

Updated scripts in Maximo 5.2 Patch 04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Updated .jsp files in Maximo 5.2 Patch 03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Updated scripts in Maximo 5.2 Patch 03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Appendix F: Fixed issues of Maximo 5.2 from patch 03 - 09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximo 5.2 Patch 09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximo 5.2 Patch 08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximo 5.2 Patch 07 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximo 5.2 Patch 06 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximo 5.2 Patch 05 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximo 5.2 Patch 04 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Maximo 5.2 Patch 03 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 35 41 52 62 67 71 83

Appendix G: Maximo 5.2 Patch 09 file manifest . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Appendix H: Notes on issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Issues noted for Patch 09 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 08-21903 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 09-13140 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 09-13237 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 09-14435 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Issues noted for Patch 08 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 07-24182 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 07-11133 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 07-15818 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 07-14303 and issue 07-15241 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 94470 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Issues noted for patches 04, 05, 06, and 07 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 06-17302 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 06-17561 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 06-11972 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 06-17315 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 83673 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 06-11520 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 94351 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 89388 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 86230 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 67853 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 93250 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 0610104 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 85429 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 64899 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 86226 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 90261 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 033265 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . About issue 77689 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 123 123 123 124 124 124 125 128 128 128 129 130 131 131 133 134 135 137 138 139 140 141 141 142 143 143 143 143 143 144

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

iv

Release Notes

Maximo 5.2 Patch 09 overview

These release notes provide an overview of IBM Maximo Asset Management 5.2 Patch 09 and the status of the product. The release notes cover the installation requirements and instructions, and all the known issues with the product.

Intended audience
To install Maximo 5.2 Patch 09, you must have administrator rights and privileges.

System requirements
If you want to install Maximo 5.2 Patch 09, the current Maximo Revision level must be at Patch 02 or 02A (revision level 5.2.150) or higher. If you have multiple Maximo folders or directories, run the patch utilities once for each Maximo folder or directory.

New supported components

Maximo 5.2 Patch 09 introduces the support for the following operating systems and application server: Microsoft Windows XP Service Pack 3 Client Java Runtime Environment (JRE) 1.6 Client Oracle WebLogic Server 8.1.6

Automated update process

The Maximo update utility establishes which versions of files are currently installed and makes the appropriate application file substitutions/additions. The update utility searches and replaces sections of Maximo .jsp files with updated information. The utility searches .jsp files line by line to check for changes. If the utility discovers changed JSP code to update, it skips that line and generates an entry in a log file. The entry explains what the update program attempted to do. The update utility also provides a code sample that illustrates the change. This action prevents the automatic update utility from overwriting customizations that you want to keep. When the update process is finished, the update utility displays a completion message and shows the name and location of the log file. The log file is named JspUpdate.log and it is located in the maximo_root directory.

Copyright IBM Corp. 2007, 2009

Installation checklist

If there is a section of code in the .jsp file that you changed before you apply the update, the patch might not automatically update the section of code. You must use the JspUpdate.log file and the JspUpdate.xml file to apply the changes that are not performed by the update utility. For detailed instructions about changing a .jsp file, see the Software Design Studio (SDS) Help.

Installation checklist
This checklist provides an overview of the installation process for users upgrading from Patch 02, 02A, 03, 04, 05, 06, 07, or Patch 08. For installation instructions, continue with the following actions: [ ] 1. Determine the current software version. [ ] 2. Process all transactions in queues (Maximo Enterprise Adapter users only) [ ] 3. Stop the Maximo application servers and services [ ] 4. Stop the MRO RMI Service (Windows users only) [ ] 5. Stop the Actuate servers and services [ ] 6. Stop the webMethods servers and services (Maximo Enterprise Adapter users only) [ ] 7. Back up the entire maximo folder [ ] 8. Back up entire webMethods B2B folder (Maximo Enterprise Adapter users only) [ ] 9. Back up your database [ ] 10. Install the Maximo 5.2 Patch 09 [ ] 11. Check JspUpdate.log [ ] 12. Delete Temporary folder/directories (WebSphere Application Server users only) [ ] 13. Perform manual updates of .jsp files.
Note:

[ ] 14. Also manually update any .jsp files for jsp fixes not installed by the jspupdate program. [ ] 15. Start the MRO RMI Service (Windows users only) [ ] 16. Rebuild and deploy the EAR files [ ] 17. Start the webMethods server [ ] 18. Install the Maximo Enterprise Adapter update (Maximo Enterprise Adapter users only) [ ] 19. Start the Actuate server [ ] 20. Start the Maximo application server [ ] 21. Check that the database upgrades successfully to the 5.2 Patch 09 level [ ] 22. Check that Maximo Enterprise Adapter is at the correct revision level (Maximo Enterprise Adapter users only) [ ] 23. Check that the Maximo application server starts successfully

Release Notes

Installing the patch on Windows

Before you install the patch in a production environment that runs the Windows operating system, you must complete the pre-installation procedure.

Preparing to install the patch

Before you install Maximo 5.2 Patch 09, complete the following steps:

1 Check that the current Maximo version is at patch level 02, 02A, 03, 04, 05, 06, 07
(revision levels 5.2.150, 5.2.254, 5.2.339, 5.2.409, 5.2.500, or 5.2.601), or Patch 08 (revision levels 5.2.633). From the command prompt in the maximo folder, type version.bat and press Enter. The Maximo (and optionally Maximo Enterprise Adapter) version is displayed as the final three digits of the build description. For example, nnn indicates the installed version and xx indicates the database version.
C:\Maximo>version Maximo Application Server 5.2.0 Build 061 nnn, DB Build V520-xx Maximo Enterprise Adapter (MEA) 5.2.0. Build MEA061 nnn, DB Build V520MEA-xx For Maximo 5.2 Patch 02 or 02A the build number is Build 061 150 DB Build V520-3 For Maximo 5.2 Patch 03 the build number is Build 061 254 DB Build V520-6 For Maximo 5.2 Patch 04, the build number is Build 061 339, DB Build V520-09 For Maximo 5.2 Patch 05, the build number is 5.2.05 Build 409, DB Build V520-14 For Maximo 5.2 Patch 06, the build number is 5.2.06 Build 500, DB Build V520-14 For Maximo 5.2 Patch 07, the build number is 5.2.07 Build 601, DB Build V520-14 For Maximo 5.2 Patch 08, the build number is 5.2.08 Build 633, DB Build V520-14 For Maximo 5.2 Patch 09, the build number is 5.2.09 Build 637, DB Build V520-14 For Maximo Enterprise Adapter (MEA) 5.2 Patch 02 or 02A the build number is Build 061 150, DB Build V520MEA-3 For Maximo Enterprise Adapter (MEA) 5.2 Patch 03 the build number is Build 061 254, DB Build V520MEA-6

Copyright IBM Corp. 2007, 2009

Installing the patch For Maximo Enterprise Adapter (MEA) 5.2 Patch 04, the build number is Build 061 339, DB Build V520MEA-6 For Maximo Enterprise Adapter (MEA) 5.2 Patch 05, the build number is 5.2.05 Build 409, DB Build V520MEA-6 For Maximo Enterprise Adapter (MEA) 5.2 Patch 06, the build number is 5.2.06 Build 500, DB Build V520MEA-6 For Maximo Enterprise Adapter (MEA) 5.2 Patch 07, the build number is 5.2.07 Build 601, For Maximo Enterprise Adapter (MEA) 5.2 Patch 08, the build number is 5.2.08 Build 633, DB Build V520MEA-6 For Maximo Enterprise Adapter (MEA) 5.2 Patch 09, the build number is 5.2.09 Build 637, DB Build V520MEA-6

2 If you use Maximo Enterprise Adapter, process all transactions in queues: a Process all transactions in the inbound and outbound queues. b Connect to the Maximo schema owner to determine whether there are any
outstanding transactions and run the following SQL statements:
select count(*) from mout_interdata; select count(*) from max_interdata; select count(*) from max_interdata_bat;

If any rows are returned in the tables, correct the error transactions and reprocess the transactions until no errors are returned.

3 Stop the Maximo application servers and services. 4 Stop the MRO RMI Service. 5 Stop the Actuate servers and services. 6 Stop the webMethods server. 7 Back up your entire maximo folder. 8 If you use Maximo Enterprise, back up the entire webMethods B2B folder. 9 To prevent data loss in the event of installation failure or corruption, back up all
databases and the entire maximo install directory.

10 Test this patch thoroughly in a test environment.

Installing the patch

To install Maximo 5.2 Patch 09, complete the following steps: 1 Download the Windows_MX52P09.zip patch file from the IBM Software Support Web site at http://www-01.ibm.com/support/docview.wss?uid=swg24023675 to your application server.

Release Notes

Completing the patch installation

2 Extract the MX52P09.exe file to a temporary folder. 3 Navigate to the temporary folder and double-click MX52P09.exe. 4 From the Introduction window, click Next. 5 Select the maximo_root folder. 6 From the Choose a Folder window, click Next. 7 Wait for the program to complete configuring your system and click Next. If you are at a level below Maximo 5.2 Patch 02 or 02A, a window indicating your software version opens.

Click OK to terminate the installation process and complete the required procedures to install Maximo 5.2 Patch 02A. You can obtain Maximo 5.2 02A Release Notes from the IBM Software Support Web site .

If you decide to continue with the installation program, click Continue Install. If you do not have a hotfix applied as listed previously, this window does not open.

8 Accept the default (C:\autoupdate) and click Next. 9 From the Pre-Installation window, click Next. When the installation is finished, the Build EAR Files window opens. The autoupdate installer rebuilds the maximo.ear file. The maximohelp.ear and the actuate.ear files are not rebuilt. If you changed any Actuate or Help files with this patch, you must manually rebuild and redeploy the associated EAR files. 10 . Indicate whether you want the EAR files to be built automatically. 11 Indicate whether you read the Release Notes and click Next. 12 Exit the installer.

Completing the patch installation

After you install the patch, you must complete the following steps:

1 If you use Maximo 5.2 in English, Dutch, French, German, Italian, Portuguese, and
Swedish and run the system on WebSphere Application Server 5.1 or WebSphere Application Server 5.1.1 versions with Actuate Server, install the Actuate fix for WebSphere Application Server 5.1 on the machine where you installed the Maximo application server. You obtain this update from the IBM Software Support Web site.

2 If you use WebSphere Application Server, delete all folders that are located in the
WebSphere\AppServer\temp folder.

3 Manually install .jsp, .js, and .txt files.

For a complete list of files and instructions about applying changes to the noted files, see Appendix C.

4 From the maximo_root folder, review the JspUpdate.log file to determine whether the
autoupdate did not completely update the .jsp files because of customizations. If the JspUpdate program did not implement the fix, a message that indicates "NO
Installing the patch on Windows

Completing the patch installation

MATCH FOUND" for that fix is included in the JspUpdate.log file. The .jsp file customizations were not updated and must be manually implemented again.

5 If there are updates that the jsp autoupdate program did not implement, use the
JspUpdate.xml file and the log files to update the .jsp files. If you use EAR files, rebuild and redeploy the EAR files as a result of this action. For more information about rebuilding and redeploying the EAR files, see Appendix B. For the list of .jsp file updates for this patch, see Appendix D.

6 Start the MRO RMI Service: a Select Control Panel > Administrative Tasks > Services. b From the services list, right-click MRO RMI Service. c From the drop-down list, click Start. 7 Build and deploy EAR files.
For instructions about using EAR files, see Appendix B.

8 Start the webMethods Server. 9 If you use Maximo Enterprise Adapter, update the adapter by installing the
maximo_root\wm\mxIntegration\mxIntegration-REV637.zip package. For the steps to update your Maximo Enterprise Adapter, see Appendix A.

10 Start the Actuate server. 11 Start the Maximo application server and update the database.
The MXServer name is obtained from the mxe.name entry in the mxserver.properties file in the maximo_root folder.

If you use WebLogic Server, complete the following steps:

a From a command prompt, change to: drive_letter\bea\user_projects\mydomain. b Run the startweblogic.cmd file. c After the MAXIMOSERVER is started and completes the database update (that
is, Running in Production Mode), review the database update log files to check that the updates ran successfully and that there were no error messages. If you are upgrading from Patches 02A, 03, 04, 05, 06, 07, and 08, the log file is titled MXServerName_UPGRADE_09.log. The log file is located in the \bea\user_projects\mydomain folder. If you use Maximo Enterprise Adapter, a log file for the adapter database changes is in the same folder. The log file name is MXServerName_MEAUPGRADE_09.log.

d Check that the database update utility ran the update correctly.

Release Notes

Completing the patch installation

After the start-up and database update, you can shut down Maximo to start it as a service if you want.

If you use WebSphere Application Server, complete the following steps:

a From a command prompt, change to websphere\appserver\bin. b Start the adminserver.bat and adminclient.bat processes and ensure that the
MAXIMOSERVER has started using the admin client.

c Review the database update log file to check that the update ran successfully and
that there were no error messages. The log file is titled MXServerName_UPGRADE_09.log. The log file is located in the drive_letter\Websphere\AppServer\bin folder. If you use Maximo Enterprise Adapter, a log file for the adapter database changes is in the same folder. The log file name is MXServerName_MEAUPGRADE_09.log.

d Check that the database update utility ran the update correctly.
After the start-up and database update, you can shut down Maximo to start it as a service if you want.

12 To check the Maximo Enterprise Adapter update, connect to the database as the
schema owner using an appropriate SQL utility and run the following statement: select * from maxvars where varname=MEAUPG The varvalue in the output = V520MEA-6 The default schema owner is Maximo.

13 Check that the Maximo application server starts correctly.

Installing the patch on Windows

Completing the patch installation

Release Notes

Installing the patch on UNIX

Before you install the patch in a production environment that runs UNIX and operating systems such as Solaris, HP-UX, and IBM AIX, you must complete the pre-installation procedure.

Preparing to install the patch

Before you install Maximo 5.2 Patch 09, you must complete the following steps:

1 Verify that the current Maximo version is at patch level 02, 02A, 03, 04, 05, 06, 07
(revision levels 5.2.150, 5.2.254, 5.2.339, 5.2.409, 5.2.500, or 5.2.601), or Patch 08 (revision levels 5.2.633). From a shell command in the maximo directory, type ./ version.sh and press Enter. The Maximo (and optionally Maximo Enterprise Adapter) version is displayed as the final three digits of the build description. For example, nnn indicates the installed version and xx indicates the database version.
$ ./version.sh Maximo Application Server 5.2.0 Build 061 nnn, DB Build V520-xx Maximo Enterprise Adapter (MEA) 5.2.0. Build MEA061, DB Build V520MEA-xx For Maximo 5.2 Patch 02 or 02A the build number is Build 061 150 DB Build V520-3 For Maximo 5.2 Patch 03 the build number is Build 061 254 DB Build V520-6 For Maximo 5.2 Patch 04, the build number is Build 061 339, DB Build V520-09 For Maximo 5.2 Patch 05, the build number is 5.2.05 Build 409, DB Build V520-14 For Maximo 5.2 Patch 06, the build number is 5.2.06 Build 500, DB Build V520-14 For Maximo 5.2 Patch 07, the build number is 5.2.07 Build 601, DB Build V520-14 For Maximo 5.2 Patch 08, the build number is 5.2.08 Build 633, DB Build V520-14 For Maximo 5.2 Patch 09, the build number is 5.2.09 Build 637, DB Build V520-14 For Maximo Enterprise Adapter (MEA) 5.2 Patch 02 or 02A the build number is Build 061 150, DB Build V520MEA-3 For Maximo Enterprise Adapter (MEA) 5.2 Patch 03 the build number is Build 061 254, DB Build V520MEA-6

Copyright IBM Corp. 2007, 2009

Installing the patch in X Window System mode For Maximo Enterprise Adapter (MEA) 5.2 Patch 04, the build number is Build 061 339, DB Build V520MEA-6 For Maximo Enterprise Adapter (MEA) 5.2 Patch 05, the build number is 5.2.05 Build 409, DB Build V520MEA-6 For Maximo Enterprise Adapter (MEA) 5.2 Patch 06, the build number is 5.2.06 Build 500, DB Build V520MEA-06 For Maximo Enterprise Adapter (MEA) 5.2 Patch 07, the build number is 5.2.07 Build 601, DB Build V520MEA-06 For Maximo Enterprise Adapter (MEA) 5.2 Patch 08, the build number is 5.2.08 Build 633, DB Build V520MEA-06 For Maximo Enterprise Adapter (MEA) 5.2 Patch 09, the build number is 5.2.09 Build 637, DB Build V520MEA-06

2 If you use Maximo Enterprise Adapter, process all transactions in queues: a Process all transactions in the inbound and outbound queues. b Connect to the Maximo schema owner to determine whether there are any
outstanding transactions and run the following SQL statements:
select count(*) from mout_interdata; select count(*) from max_interdata; select count(*) from max_interdata_bat;

If any rows are returned in the tables, correct the error transactions and reprocess the transactions until no errors are returned.

3 Stop the Maximo application servers and services. 4 Stop the Actuate servers and services. 5 Stop the webMethods server. 6 Back up your entire maximo folder. 7 If you use Maximo Enterprise, back up the entire webMethods B2B folder. 8 To prevent data loss in the event of installation failure or corruption, back up all
databases and the entire maximo install directory.

9 Test this patch thoroughly in a test environment.

Installing the patch in X Window System mode

You can install the patch in either X Window System mode and console mode. To install Maximo 5.2 Patch 09 in X Window System mode, complete the following steps:

10

Release Notes

Installing the patch in console mode

1 Download the appropriate patch file from the IBM Software Support Web site.

Table 1: Platform-specific Patch

Solaris HP-UX AIX Solaris_MX52P09.zip HP_MX52P09.zip AIX_MX52P09.zip

2 Extract the MX52P09.bin file to a temporary folder on the PC. 3 Use FTP to transfer the MX52P09.bin file in binary mode from the PC to the Solaris, HP-UX, or AIX application server. 4 Add execute permissions with the following command:
chmod +x MX52P09.bin

5 Run the ./MX52P09.bin update program. 6 Check that your Maximo product is in one of the following versions: Maximo application server Release 5.2 Build 061 150, DB Build V520-03 Maximo application server Release 5.2 Build 061 254, DB Build V520-06 Maximo application server Release 5.2 Build 061 339, DB Build V520-09 Maximo application server Release 5.2.05 Build 409, DB Build V520-14 Maximo application server Release 5.2.06 Build 500, DB Build V520-14 Maximo application server Release 5.2.07 Build 601, DB Build 520-14 Maximo application server Release 5.2.08 Build 633, DB Build 520-14 7 Follow the onscreen instructions. If you are not at Patch 02 or Patch 02A, a window indicating your software version opens. Click OK and complete the steps to install 5.2 Patch 02A before you install Patch 09. 8 In the Pre-Installation Summary window, review the summary. If you want, change the previous steps. 9 Install the update. 10 Indicate whether you want the EAR files to be built automatically. When the Release Notes screen opens, the installation process is complete. 11 Indicate whether you read the Release Notes and exit the installer.

Installing the patch in console mode

The console mode installer does not prevent you from installing the patch if you are at an incorrect version of 5.2. Check that you are at the 5.2 Patch 02, 02A, 03, 04, 05 06, 07, 08 levels before you install 5.2 Patch 09 in console mode. To install Maximo 5.2 Patch 09 in console mode, complete the following steps: 1 Download the appropriate patch file from the IBM Software Support Web site.

Table 2: Platform-specific Patch

Solaris HP-UX AIX Solaris_MX52P09.zip HP_MX52P09.zip AIX_MX52P09.zip

Installing the patch on UNIX

11

Completing the patch installation

2 Extract the MX52P09.bin file to a temporary folder on the PC. 3 Use FTP to transfer the MX52P09.bin file in binary mode from the PC to the application server. 4 Add execute permissions with the following command: chmod +x MX52P09.bin 5 Run the ./MX52P09.bin -i console update program, and then press Enter. 6 Review the warning message about your Maximo version, and then press Enter. 7 Enter the path of the directory to which the installation program installs the Maximo update. The log file that was created during the update process is placed in this directory. 8 Respond Y or N to the install folder prompt and press Enter. 9 Review the summary. If you want to change something on a previous step, type back. 10 To install the update, press Enter. The Installation Progress bar appears. When the installation process is complete, a configuration message appears, then the Release Notes message opens. 11 Enter the number for your choice: (2 is selected by default) (1) If you read the Release Notes. (2) If you did not read the Release Notes. If you selected option 1, a message notifies you that the autoupdate was installed. If you selected option 2, a message warns you to read the Release Notes before you run Maximo. 12 Exit the installer.

Completing the patch installation

After you install the patch, you must complete the following steps before you restart your Maximo application servers:

1 If you use Maximo 5.2 in English, Dutch, French, German, Italian, Portuguese, and
Swedish and run the system on WebSphere Application Server 5.1 or WebSphere Application Server 5.1.1 versions with Actuate Server, install the Actuate fix for WebSphere Application Server 5.1 on the machine where you installed the Maximo application server. You obtain this update from the IBM Software Support Web site.

2 If you use WebSphere Application Server, delete all directories that are located in the
WebSphere/AppServer/temp directory.

3 Manually install .jsp, .js, and .txt files.

For a complete list of files and instructions about applying changes to the noted files, see Appendix C.

4 From the maximo_root folder, review the JspUpdate.log file to determine whether the
autoupdate did not completely update the .jsp files because of customizations. If the JspUpdate program does not implement the fix, a message that indicates "NO

12

Release Notes

Completing the patch installation

MATCH FOUND" for that fix is included in the JspUpdate.log file. The .jsp file customizations were not updated and must be manually implemented again.

5 If there are updates that the jsp autoupdate program did not implement, use the
JspUpdate.xml file and the log files to update the .jsp files. If you use EAR files, rebuild and redeploy the EAR files as a result of this action. For more information about rebuilding and redeploying the EAR files, see Appendix B. For the list of .jsp file updates for this patch, see Appendix D.

6 Build and deploy EAR files.

For instructions about using EAR files, see Appendix B.

7 Start the webMethods Server. 8 If you use Maximo Enterprise Adapter, update the adapter by installing the
maximo_root\wm\mxIntegration\mxIntegration-REV637.zip package. For the steps to update your Maximo Enterprise Adapter, see Appendix A.

9 Start the Actuate server. 10 Start the Maximo application server and update the database.
Maximo 5.2 Patch 09 requires database changes only if you are updating from Patch 04 and lower patches. The first time you start MAXIMOSERVER after you run the update, the database update utility runs. For the list of updates that you must make to your database, see Appendix D. The MXServer name is obtained from the mxe.name entry in the mxserver.properties file in the maximo_root directory.

If you use Oracle WebLogic Server, complete the following steps:

a From a terminal window, change directory to: bea/user_projects/mydomain. b Run the startweblogic.sh file. c After the MAXIMOSERVER is started and completes the database update (that
is, running in production mode), review the database update log file to check that the updates ran successfully and that there were no error messages. If you are upgrading from patches 02A, 03, 04, 05, 06, 07, and 08, the log file is titled MXServerName_UPGRADE_09.log. The log file is located in the /bea/ user_projects/mydomain directory. If you use Maximo Enterprise Adapter, a log file for the adapter database changes is in the same directory. The log file name is MXServerName_MEAUPGRADE_09.log. After the start-up and database update, you can shut down Maximo to start it as a service if you want.

If you use WebSphere Application Server, complete the following steps:

Installing the patch on UNIX

13

Completing the patch installation

a From a terminal window, run /Websphere\AppServer\bin/adminserver.sh. b Start the adminserver.sh and adminclient.sh processes and ensure that the
MAXIMOSERVER has started using the admin client.

c Review the database update log file to check that the update ran successfully and
that there were no error messages. The log file is titled MXServerName_UPGRADE_09.log. The log file is located in the Websphere/AppServer/bin directory. If you use Maximo Enterprise Adapter, a log file for the adapter database changes is in the same directory. The log file name is MXServerName_MEAUPGRADE_09.log.

d Check that the database update utility ran the update correctly.
After the start-up and database update, you can shut down Maximo to start it as a service if you want.

11 To check the Maximo Enterprise Adapter update, connect to the database as the
schema owner using an appropriate SQL utility and run the following statement: select * from maxvars where varname=MEAUPG The varvalue in the output = V520MEA-6 The default schema owner is Maximo.

12 Check that the Maximo application server starts correctly.

See Step 10.

13 If you are an English or non-English Maximo Actuate user, manually install the files
that were not installed after you applied the patch. The actuate issue 83961 was fixed in 5.2 patch 06. The fix for this issue requires the manual installation of a few files in addition to changes to the build.xml and maximoui-web.xml files. For more details, see the Release Notes Patch 06. For a complete list of files and instructions on how to apply changes to the noted files, see Appendix C.

14

Release Notes

Installing Maximo Enterprise Adapter

You must determine your currently installed mxIntegration version by completing the following steps: 1 Open the webMethods B2B server. 2 From the Packages menu section, select Management. 3 To display package information and patch history for mxIntegration, click the mxIntegration package name in the Package List. 4 See the Patch History section. Entries in the Patch History section correspond to mxIntegration version file names.

webMethods mxIntegration package updates

The Maximo 5.2 Patch 09 installation distributes .zip files that pertain to the mxIntegration package. This package is included with Maximo Enterprise Adapter as part of the webMethods installation. The patch installation distributes the following .zip files: mxIntegration-REV254.zip (Revision 5.2.254) (Patch 03 or Patch 04) mxIntegration-REV409.zip (Revision 5.2.409) (Patch 05 or Patch 06) mxIntegration-REV601.zip (Revision 5.2.601) (Patch 07) mxIntegration-REV633.zip (Revision 5.2.633) (Patch 08) mxIntegration-REV637.zip (Revision 5.2.637) (Patch 09) These files are located in the maximo_root\wm\mxIntegration folder. If you applied any of these versions of the mxIntegration program fix during a previous update, you must only apply the later version(s). Otherwise, you must apply them in the order listed in the following example. Revision numbers are indicated at the end of each .zip file name. mxIntegration-REV254.zip mxIntegration-REV409.zip mxIntegration-REV601.zip mxIntegration-REV633.zip mxIntegration-REV637.zip If you made any customizations to your mxIntegration package, check the mxIntegrationREV254.zip, mxIntegration-REV409.zip, mxIntegration-REV601.zip, mxIntegrationREV633.zip, and mxIntegration-REV637.zip file to verify that any files contained in this package will overwrite your customizations.

Copyright IBM Corp. 2007, 2009

15

Installing the webMethods package files

Installing the webMethods package files

To apply the webMethods .zip files, you must complete the following steps: 1 Copy the mxIntegration-REV254.zip (if upgrading from patch level 02, 02A), mxIntegration-REV409.zip, mxIntegration-REV601.zip, mxIntegrationREV633.zip, and mxIntegration-REV637.zip files from the mxIntegration folder (default path maximo_root\wm\mxIntegration) to the \replicate\inbound folder of the Maximo B2B Server (default path\webMethods\IntegrationServer4\replicate\inbound). 2 Install the inbound mxIntegration-254 (if upgrading from patch level 02, 02A), the mxIntegration-409 package, the mxIntegration-REV601 package, mxIntegrationREV633 package, and the mxIntegration-REV637 package.
Note:

Ensure that the Activate upon installation box is checked. For more details, see the Maximo Enterprise Adapter Installation Guide. a From the Integration Server Packages > Management page, select Install Inbound Releases. b Select mxIntegration-REV254.zip (if you have not already installed this package from a prior patch) from the Inbound Release drop-down list. c Click Install Release. d Select mxIntegration-REV409.zip (if you have not already installed this package from a prior patch) from the Inbound Release drop-down list. e Click Install Release. f Select mxIntegration-REV601.zip from the Inbound Release drop-down list. g Click Install Release. h Select mxIntegration-REV633.zip from the Inbound Release drop-down list. i Click Install Release. j Select mxIntegration-REV637.zip from the Inbound Release drop-down list. k Click Install Release. 3 Once the package is successfully installed, reload the mxIntegration package. 4 Restart the WebMethods server. After restarting the WebMethods server, login and navigate to package management. Click the mxIntegration package name from the packages list to see a revision history describing the details of the program fix applied.

16

Release Notes

Building and deploying the EAR files

This appendix describes the steps that you follow to build Enterprise Application Archive files (EAR). In brief, you complete the following steps: Before you start building the EAR files, ensure that your browser can make an active connection to the Internet. Otherwise, see the Security Issues appendix in the Maximo Installation Guide. To validate the XML pages, the build process makes a clear (that is, no proxy) http connection to the following Sun Microsystems Web pages: http://java.sun.com/j2ee/dtds/application_1_2.dtd http://java.sun.com/j2ee/dtds/web-app_2_2.dtd Before running the batch files, the existing files that open in the build folder under your Maximo root installation folder must be deleted. The following table is a listing of all the files that reside in the build folder:

Table 1: Contents of the build folder

Application name Maximo Contents maximo.ear dynamic.jar inet.jar maximoui.war mbo.jar mbo.war maximohelp.ear maximohelp.war actuate.ear actuate.war acweb.ear acweb.war acadmin.ear acadmin.war

Maximo Help

Actuate

Acweb

Acadmin

Deleting the existing EAR files

Delete any existing EAR files before rebuilding them: 1 Using Windows Explorer, navigate to the \build folder under root Maximo installation directory. For example: C:\Maximo\build.

Copyright IBM Corp. 2007, 2009

17

The EAR files to be rebuilt and deployed

2 Select and delete the appropriate EAR file and its accompanying files. For example, to rebuild the Maximo application, delete the following files: maximo.ear, dynamic.jar, inet.jar, maximoui.war, mbo.jar, mbo.war.

The EAR files to be rebuilt and deployed

There are five EAR files that you might have to rebuild and deploy. These EAR files are listed in the following table:

Table 2: Listing of EAR files Windows

buildear.bat buildhelpear.bat buildactuateear.bat buildacadminear.bat buildacwebear.bat

UNIX
buildear.sh buildhelpear.sh buildactuateear.sh buildacadminear.sh buildacwebear.sh

The following sections describe how to build the EAR files and when you might need to build them.

Building the Maximo EAR file

To build the Maximo EAR file, perform the following steps: 1 Remove the maximo.ear, dynamic.jar, inet.jar, maximoui.war, mbo.jar, and mbo.war files from the build folder. 2 Open a command prompt (Windows) or terminal window (UNIX). 3 Change directory to your maximo_root directory, for example: C:\Maximo (Windows) or /mxadmin/Maximo (UNIX). (UNIX Users Only) All the shell files must have executable permissions, to ensure that all the files have executable permissions, run the chmod +x build*.sh command in the maximo_root folder. 4 Type buildear.bat (Windows) or ./buildear.sh (UNIX) and press Enter. The command prompt or terminal window then displays a BUILD SUCCESSFUL line. The script file creates a maximo.ear file (and associated WAR files) in the build subdirectory of the maximo_root directory. Rebuild and redeploy Maximo EAR files whenever you change any of the files located in the maximo_root directory, except Help files, for which there is a separate build file. For example, whenever you modify .jsp files in customizing your screens, rebuild the maximo.ear file.

Building the Maximo Help EAR files

To build the Maximo HELP EAR file, perform the following steps: 1 Remove the maximohelp.ear and maximohelp.war files from the build folder. 2 Open a command prompt in Windows or terminal window in UNIX. 3 Change directory to your maximo_root directory, for example: C:\Maximo (Windows) or /mxadmin/Maximo (UNIX) 4 Type buildhelpear.bat (Windows) or ./buildhelpear.sh (UNIX) and press Enter.

18

Release Notes

The EAR files to be rebuilt and deployed

The command prompt or terminal window then displays a BUILD SUCCESSFUL line. The script file creates a maximohelp.ear file (and associated WAR file) in the build subdirectory of the maximo_root directory. Rebuild and redeploy the maximohelp.ear file whenever you change any of the Maximo Help files in the jsp\help subdirectory of the maximo_root directory.

Building the Actuate EAR file

To build the Actuate EAR file, perform the following steps: 1 Remove the actuate.ear and actuate.war files from the build folder. 2 Open a command prompt in Windows or terminal window in UNIX. 3 Change directory to your maximo_root directory, for example: C:\Maximo (Windows) or /mxadmin/Maximo (UNIX) 4 Type buildactuateear.bat (Windows) or ./buildactuateear.sh (UNIX) and press Enter. The command prompt or terminal window then displays a BUILD SUCCESSFUL line. The script file creates an Actuate.ear file (and associated WAR file) in the build subdirectory of the maximo_root directory. Rebuild and redeploy the Actuate.ear file whenever you change the look-and-feel of the reporting screens in Maximo (for example, changes in .gif and html files).

Building the acadmin EAR file

To build the acadmin EAR file, perform the following steps: 1 Remove the acadmin.ear and acadmin.war files from the build folder. 2 Open a command prompt in Windows or terminal window in UNIX. 3 Change directory to your maximo_root directory, for example: C:\Maximo (Windows) or /mxadmin/Maximo (UNIX) 4 Type buildacadminear.bat (Windows) or ./buildacadminear.sh (UNIX) and press Enter. Running this file can take several minutes. The command prompt or terminal window then displays a BUILD SUCCESSFUL line. The script file creates an acadmin.ear file (and associated WAR files) in the build subdirectory of the maximo_root directory. Build and deploy a new acadmin.ear file whenever you change the address of the iServer /mgmtconsole server.

Building the acweb EAR File

To build the acweb EAR file, perform the following steps: 1 Remove the acweb.ear and acweb.war files from the build folder. 2 Open a command prompt (Windows) or terminal window (UNIX). 3 Change directory to your maximo_root directory, for example: C:\Maximo (Windows) or /mxadmin/Maximo (UNIX) 4 Type buildacwebear.bat (Windows) or ./buildacwebear.sh (UNIX) and press Enter. Running this file can take several minutes. The command prompt or terminal window then displays a BUILD SUCCESSFUL line. The script file creates an acweb.ear file (and associated WAR files) in the build subdirectory of the maximo_root directory. Build and deploy a new acweb.ear file whenever you change reports or change the web.xml that contains information about the report server.

Building and deploying the EAR files

19

Deploying the EAR files WebSphere Application Server 5.1.1

Deploying the EAR files WebSphere Application Server 5.1.1

If you stopped the IBM WebSphere Application Server V5 - dmgr process and closed the Administrative console, complete the following steps; otherwise, if the dmgr process is running and the Administrative console is open, continue with Step 2. 1 Ensure that the IBM WebSphere Application Server V5 - dmgr process is running:* a From a terminal prompt, go to the /bin directory where you installed the Network Deployment manager (dmgr). For example:
cd /usr/WebSphere/DeploymentManager/bin

b To start the Network Deployment manager, type the following command:

./startManager.sh

2 Start the NodeAgent by completing the following steps: a From a terminal window, change to the /AppServer/bin directory. For example:
cd /usr/WebSphere/AppServer/bin

b Type the following command:

./startNode.sh

3 Open the Administrative console by typing in your browser address bar: http://machine_name:9090/admin 4 Enter a user name to log in. You can use any name to log in. Security is not enabled. You can also set security levels for various user privileges. See the Maximo 5.2 System Administrators Guide for more details. 5 Click the Applications link in the left pane. 6 If you are accessing the Administrative console from the server where WebSphere 5.1.1 is installed, select Local Path. Otherwise, select Server Path and click Browse. 7 Navigate to your Maximo home directory and open the /build directory. 8 Select maximo.ear file and click Open in the window. 9 Accept the default settings and click Next. 10Click Continue in the Applications Security Warnings page. 11Step 1: Accept the defaults and type Maximo as your Application name and click Next. 12Step 2: Map virtual hosts for web modules by completing the following steps: a Check the Web Module box. b From the Virtual host drop-down list, select MAXIMOSERVER_host for the mbo.war and maximoui.war modules. c Click Next. 13Step 3: Map the modules to the MAXIMOSERVER application server: a Check the Module check box. b From the Clusters and Servers box, select MAXIMOSERVER.

20

Release Notes

Deploying EAR files WebLogic Server 8.1. SP6

c Click Apply. d Click Next. 14Step 4: In the Summary page, review your settings and click Finish. 15In the successfully installed confirmation page, click Save to Master Configuration. 16Click Save again if you changed anything. 17Repeat Steps 8 through 21 for the remaining four EAR files: As you complete Step 10 for each file, rename the applications as follows
EAR file maximohelp.ear actuate.ear acweb.ear acadmin.ear Application name MAXIMOHELP ACTUATE ACWEB ACADMIN

Deploying EAR files WebLogic Server 8.1. SP6

To deploy the EAR files, complete the following steps: 1 From the Start menu select: Programs > BEA WebLogic Platform 8.1 > WebLogic Server 8.1 > Server Tour and Examples > Start Admin Console. Alternatively, you can start the Admin Console by typing the following Web address in the address bar of your browser: http://host name:7001/console 2 Type in your user name and password. 3 Click Applications (under Deployments) and the mydomain>Applications page opens. 4 Click Configure a new Application from the main page and the Locate Application or Components to Configure page opens. 5 Click C:\ or your root Maximo installation directory. WebLogic Server displays folders on your root directory on the page. 6 Click your Maximo root installation folder (in this example: c:\Maximo). 7 Click and open the build folder. Note the EAR files that reside in the build folder: acadmin.ear Actuate.ear acweb.ear maximo.ear maximohelp.ear 8 Click [select] next to the maximohelp.ear file. The Configure Application or Component page opens. 9 Select MAXIMOSERVER from the Available Servers column. 10Using the arrow button, move it to the Target Server. 11Accept the default name maximohelp in the Step 4 text box inside the page or type another name for the maximohelp.ear application. 12Click Configure and Deploy. Wait for the deploy activity to complete. During this time after you click Configure and

Building and deploying the EAR files

21

Deploying EAR files WebLogic Server 8.1. SP6

Deploy, the page displaying in your browser refreshes every few seconds. Ensure that the Status of your Deployment Activity is Completed, before you continue. 13Repeat Steps 4 through 12 for the remaining four EAR files. Accept the default name for each application as it appears in the Step 4 of the Configure Component or Application page in your browser. Actuate.ear acweb.ear acadmin.ear maximo.ear

22

Release Notes

Manually installing files of Maximo 5.2 Patch 09

The Maximo Patch 09 installer does not automate installation of all .jsp, .js, and .txt files that are required for the patch to run correctly because many files were customized by clients or because of globalization reasons.

Folder structures
If you need to check, back up, or copy your Maximo customizations, you must open the maximo_root\user_files folder. This folder contains seven folder structures that range Maximo 5.2 from Patch 3 to Patch 09:

Folder structure MX52P03_files MX52P04_files MX52P05_files MX52P06_files MX52P07_files MX52P08_files MX52P09_files

Content Contains customizations up to and inclusive of Maximo 5.2 Patch 03 Contains customizations specific to Maximo 5.2 Patch 04 Contains customizations specific to Maximo 5.2 Patch 05 Contains customizations specific to Maximo 5.2 Patch 06 Contains customizations specific to Maximo 5.2 Patch 07 Contains customizations specific to Maximo 5.2 Patch 08 Contains customizations specific to Maximo 5.2 Patch 09

Manually updating the files

If you customized the .jsp, .js. and .txt files that are listed in Table 1: List of files to be manually updated, complete the following steps:

1 Before you start the manual installation, back up the current Maximo files, and then
copy the files based on the Maximo patch level.

2 Compare your customized files with the changes implemented in the fixed files.

Copyright IBM Corp. 2007, 2009

23

Lists of files to be manually updated

The fixed files are located in the maximo_root\user_files folder. If needed, manually apply the changes.

3 Rebuild and redeploy the Maximo EAR files.

If you did not customize any of the .jsp, .js, and .txt files that are listed in Table 1, back up the files and copy them from maximo_root\user_files\patch_number_files\subfolder\filename to the maximo_root\subfolder. Example: maximo_root\user_files\MX52P06_files\jsp\javascript\dynamic.js to the maximo_root\jsp\javascript folder.

Lists of files to be manually updated

Table 1: List of files to be manually updated
All the files listed in Table 1 must be manually installed. An X in the table denotes which changes are applicable based on the patch version from which you are upgrading. Compare the contents of these files, which are English, with the version currently on your system and implement the changes as needed.

Files to be manually installed:

If you are upgrading from 5.2 Patch: P02/ P03 P04 P05 P06 P07 P08 02A
X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X

The following files apply to all Maximo users MX52P08_files\build.xml MX52P08_files\WEB-INF\maximoui-web.xml MX52P08_files\jsp\javascript\dynamic.js MX52P08_files\jsp\app\receipts\qbe.jsp MX52P08_files\jsp\javascript\wait.js MX52P08_files\jsp\javascript\table.js MX52P07_files\jsp\common\reports\mroindex.jsp MX52P06_files\jsp\common\lookup\jobplan.jsp MX52P05_files\jsp\javascript\listboxcontrol.js MX52P05_files\jsp\common\assetcatalog\assetmain.jsp MX52P04_files\jsp\javascript\menus.js The following files apply to all Maximo Actuate users MX52P09_files\actfiles\activeportal\viewer\acrobatobj.js MX52P09_files\jsp\printing\browserobj.js MX52P08_files\actfiles\activeportal\viewer\directprint.jsp MX52P08_files\actfiles\activeportal\viewer\print.jsp MX52P08_files\jsp\common\system\printacrobast.jsp MX52P08_files\jsp\common\system\printdocs.jsp MX52P08_files\jsp\common\system\printofficecad.jsp MX52P08_files\jsp\common\system\printother.jsp
24

X X X X X X X X

X X X X X X X X

X X X X X X X X

X X X X X X X X

X X X X X X X X

X X X X X X X X

X X

Release Notes

Lists of files to be manually updated

X X X X X X MX52P08_files\jsp\common\system\printpdf.jsp X X X X X X MX52P08_files\jsp\common\system\printsettings.jsp X X X X X X MX52P08_files\jsp\common\reports\runreport.jsp X X X X MX52P06_files\actfiles\jarfiles\iServer.jar X X X MX52P06_files\actfiles\activeportal\WEB-INF\lib\iSer- X ver.jar X X X X MX52P06_files\actfiles\activeportal\private\filesfolders\filefolderlistcontent.jsp X X X X MX52P06_files\actfiles\activeportal\viewer\viewframeset.jsp X X X X MX52P06_files\jsp\common\reports\reorderreport.jsp X X MX52P04_files\actuate\MRO\functions.js X MX52P03_files\jsp\common\reports\reportsubmit.html Table 2: File to be manually installed only for non-English versions of Maximo
The file listed in Table 2 must be manually installed only for non-English versions of Maximo that are being upgraded from Patches 02, 02A, 03, or 04. Compare the contents of this file, which is in English, with the version currently on your system and implement the changes as needed. Files P02/02A If you are upgrading from: P03 P04 P05 P06 P07 P08

Non-English language Maximo users maximo_root\jsp\common\system\login.jsp

Manually installing files of Maximo 5.2 Patch 09

25

Lists of files to be manually updated

26

Release Notes

Updated .jsp files and scripts, and the autoupdate process

The updated files

If you are upgrading from Patch 08 to Patch 09, the following table lists the files that are updated in Maximo 5.2 Patch 09 by the jspupdate program. Issue Files

09-12676 09-11611

jsp\app\jobplan\main.jsp jsp\common\assetcatalog\assetmain.jsp

The autoupdate process

The following is an overview of the sequence of events that take place during the autoupdate process. The jspupdate.xml file checks the current revision number in the jsp.properties file. For example: the revision number in your jsp.properties file after installing Patch 03 is 245.0 the revision number in your jsp.properties file after installing Patch 04 is 306.0 the revision number in your jsp.properties file after installing Patch 05 is 364.0 the revision number in your jsp.properties file after installing Patch 06 is 482.0 the revision number in your jsp.properties file after installing Patch 07 is 584.0 the revision number in your jsp.properties file after installing Patch 08 is 628.0 the revision number in your jsp.properties file after installing Patch 09 is 637.0 If the current revision number in the jsp.properties is less than the revision number for the patch, the jspupdate program runs the jspupdate.xml file. For example: the current revision number can be 49.0, which is less than the revision number 64.0. The jspupdate program runs through each revision since the last revision number, and attempt to modify files with the changes. This update process uses a simple search and replace function in files to be modified to perform the changes. The jspupdate.xml succeeds only on exact matches within the file being modified. If the search function fails to find the segment to be modified, the update fails. All attempts by the jspupdate.xml file to modify a file are logged in the JspUpdate.log file. When a change is performed successfully, a note that says "MATCH FOUND", the file name, and a brief note on the change are written to the JspUpdate.log file. When the update fails, a note that says "NO MATCH FOUND", the file being modified, and brief details on the change that was attempted are written to the JspUpdate.log file.

Copyright IBM Corp. 2007, 2009

27

The autoupdate process

Once all revisions specified in the jspupdate.xml file have run, the update process stops. The jspupdate program updates the revision number in the jsp.properties file to the last revision number handled. Upon completion of the install, verify the JspUpdate.log file and identify all entries that have a NO MATCH FOUND message. A NO MATCH FOUND message indicates that the change failed, or that the change is already applied to the file being modified. The JspUpdate.log file specifies the file that the change was attempted for, and the change number (for example, change 3 of 7) where applicable. Investigate the reasons why the change failed. If the change failed because of customizations to the file being modified, manually implement the changes. To determine the change being performed: Look in the maximo_root\user_files\ for the appropriate backup version of the fixed file. For example, the backup version of the setcount.jsp file is available in: maximo_root\user_files\MX52P06_files\jsp\app\pm\setcount.jsp Examine the jspupdate.xml file for the changes being made. If you cannot determine the change performed by the jspupdate, or are unable to determine why the jspupdate failed, contact IBM Software Support.

28

Release Notes

Maximo 5.2 previous program patches

Updated .jsp files in Maximo 5.2 Patch 08

Table 1: List of the updated .jsp files in Maximo 5.2 Patch 08
Issue Files

07-13245 035463 07-22108

07-25303

jsp\app\wotrack\assignments.jsp jsp\app\wotrack\failrep.jsp jsp\app\jobplan\linkdocs.jsp jsp\app\jobplan\main.jsp jsp\app\jobplan\sparepart.jsp jsp\app\jobplan\viewtotals.jsp jsp\app\buyer\receipt.jsp

Updated .jsp files in Maximo 5.2 Patch 07

Table 2: List of the updated .jsp files in Maximo 5.2 Patch 07
Issue Files

06-10583 67682 041161 06-15656 06-17883 06-12870 06-17456

06-17162

jsp\app\location\qbe.jsp jsp\common\lookup\binnum.jsp jsp\common\lookup\invballot.jsp jsp\app\wotrack\main.jsp jsp\app\wotrack\main.jsp jsp\app\quickrep\main.jsp jsp\app\invoice\main.jsp jsp\app\buyer\details.jsp jsp\app\failure\copycodes.jsp jsp\app\invissue\selectitemsfortransferin.jsp jsp\app\invissue\selectitemsfortransferout.jsp jsp\app\invissue\selectpoitemsin.jsp jsp\app\invissue\selectpoitemsout.jsp jsp\app\invissue\selectreserveditems.jsp jsp\app\wotrack\pllabor.jsp jsp\app\invissue\selectreserveditems.jsp

Copyright IBM Corp. 2007, 2009

29

Updated .jsp files in Maximo 5.2 Patch 07

06-17270

resources\defaults\jspsettings.txt Note: The installation program updates the jspsettings.txt file. The jspupdate program does not implement this update, Therefore, there is no entry for this update in the jspupdate.log file.

Updated .jsp files in Maximo 5.2 Patch 06

Table 3: List of the updated .jsp files in Maximo 5.2 Patch 06
Issue Revision number Files

88937 86894 87515 87567 91072 0610104, 88783

426 438 444 456 468 482

jsp\common\lookup\problemcode.jsp jsp\app\receipts\qbe.jsp jsp\app\location\viewparents.jsp jsp\app\invissue\addmodifyreservepurch.jsp jsp\common\workflow\manualinput.jsp resources\defaults\main.jspsettings.txt

The Maximo 5.2 Patch 06 installation program installs three files in the maximo_root folder: jspupdate.xml, jsp.properties, and JspUpdate.log. These files play an important role in the autoupdate process. The jspupdate.xml file contains the updates listed in Table 1. The file also includes modifications from prior patches. You can view the changes that pertain to this update by searching for the tag: mxversion id=REVISION revision_number in the jspupdate.xml file. The revision_number is listed in the previous table. The jsp.properties file holds the revision number. This number is the last revision handled by the jspupdate program. This revision number is revised every time the jspupdate completes the update process. The JspUpdate.log file is a log file created by the jspupdate program. Each attempt by the jspupdate.xml file to modify a file is logged in this file. You inspect this file at the end of the install process to identify failures of the jspupdate program.
Note:

Starting with Maximo 5.2 Patch 05, the existing JspUpdate.log file is backed up by the installation program. For example, on installing Patch 05, the patch installer backs up the existing JspUpdate.log file to the JspUpdate_P05.log file.

30

Release Notes

Updated .jsp files in Maximo 5.2 Patch 05

Updated .jsp files in Maximo 5.2 Patch 05

If you are upgrading from Patch 04, the following table lists the files that are updated in Maximo 5.2 Patch 05 by the jspupdate program.

Table 4: List of the updated .jsp files in Maximo 5.2 Patch 05

Issue Revision number Files

90261

341

jsp\common\linkdocs\attachdoclinksfile.jsp jsp\commom\system\header.jsp jsp\common\linkdocs\docregistrationfile.jsp jsp\app\pm\setcount.jsp

84728

364

Updated scripts in Maximo 5.2 Patch 05

Table 5: List of the updated database scripts in Maximo 5.2 Patch 05
Issue Script Issue description

83484

script\V520_10.ora script\V520_10.sqs script\V520_11.ora script\V520_11.sqs script/V520_12.ora script/V520_12.sqs

script/V520_13.ora script/V520_13.sqs

MAXTABLES definition differs from MAXTABLESCFG for A_LONGDESCRIPTION Drilldown takes a long time to display Problems viewing drilldown. Set the default of the change child status check box on work orders through the maxsyscolumns2 table in the database. Cannot enter negative values for quantity, hours, rate, or line cost for tool transactions in a work order.

62265 85854 86226

84897

script/V520_14.ora script/V520_14.sqs

The Maximo 5.2 Patch 05 installation program installs three files in the maximo_root folder: jspupdate.xml, jsp.properties, and JspUpdate.log. These files play an important role in the autoupdate process. The jspupdate.xml file contains the updates listed in Table 1. The file also includes modifications from prior patches. You can view the changes that pertain to this update by searching for the tag: mxversion id=REVISION revision_number in the jspupdate.xml file. The revision_number is listed in the previous table. The jsp.properties file holds the revision number. This number is the last revision handled by the jspupdate program. This revision number is revised every time the jspupdate completes the update process.

Maximo 5.2 previous program patches

31

Updated .jsp files in Maximo 5.2 Patch 04

The JspUpdate.log file is a log file created by the jspupdate program. Each attempt by the jspupdate.xml file to modify a file is logged in this file. You inspect this file at the end of the install process to identify failures of the jspupdate program.
Note:

Starting with Maximo 5.2 Patch 05, the installation program backs up the existing JspUpdate.log file. For example, on installing Patch 05, the patch installer backs up the existing JspUpdate.log file to the JspUpdate_P05.log file.

Updated .jsp files in Maximo 5.2 Patch 04

If you are upgrading from Patch Level 03, the following table lists the files that are updated in Maximo 5.2 Patch 04 by the jspupdate program.

Table 6: List of the updated .jsp files in Maximo 5.2 Patch 04

Issue Revision File

69643 66179, 70989 66179, 70989 65829, 78856, 79117 65124 62519 13589 64699 Several issues

256 258 258 262 263 264 273 276 289 289

\jsp\app\item\main.jsp actuate/MRO/functions.js jsp/common/reports/mroindex.jsp jsp\app\invoice\invlines.jsp jsp\app\invissue\selectitemsforreturnissue.jsp jsp\app\location\resident.jsp jsp\common\linkdocs\attachdoclinksfile.jsp jsp/app/invissue/selectreserveditems.jsp jsp\app\invissue\selectpoitemsout.jsp jsp\app\invissue\selectpoitemsin.jsp jsp\common\system\login.jsp

74505

306

32

Release Notes

Updated scripts in Maximo 5.2 Patch 04

Updated scripts in Maximo 5.2 Patch 04

Table 7: List of the updated database scripts in Maximo 5.2 Patch 04
Issue Script Issue description

80790

script\V520_8.ora script\V520_8.sqs

The MATUSETRANS object needs to support negative line costs for returned transactions rather than flip-flopped accounts. Equipment records are missing specification attributes following upgrade from 4.1.1 to 5.2 The work priority calculations and response times are displayed correctly for the first site only. Work priority and response times are not displayed for any other site.

76464

script\V520_7.ora script\V520_7.sqs script/V520_9.ora script/V520_9.sqs

67636

Updated .jsp files in Maximo 5.2 Patch 03

If you are upgrading from Patch Level 02A or 02, the following table lists the files that are updated in Maximo 5.2 Patch 03 by the jspupdate program.

Table 8: List of the updated .jsp files in Maximo 5.2 Patch 03

Issue Revision number Files

041035, 62031, 66271, 66533 67722 12608 69727 62444, 67408, 73622

165 168 198 203 216

actuate/MRO/Functions.js jsp/common/reports/runreport.jsp jsp/common/lookup/datelookup.jsp jsp/common/workflow/multipleassignments.jsp actuate\MRO\Functions.js jsp\app\woreq\main.jsp jsp\app\woreq\reviewdetails.jsp jsp\common\lookup\longdesc.jsp jsp\common\lookup\problemcode.jsp resources\defaults\jspsettings.txt jsp/app/wotrack/actuals.jsp jsp/app/wotrack/plans.jsp jsp/app/quickrep/main.jsp

73981 72004, 62474, 65223

223 224

Maximo 5.2 previous program patches

33

Updated scripts in Maximo 5.2 Patch 03

Table 8: List of the updated .jsp files in Maximo 5.2 Patch 03

Issue Revision number Files

69721 034653 74961, 75514 71920 75238

225 236 239 242 243

jsp\app\location\resident.jsp jsp\app\wotrack\showlist.jsp jsp\app\buyer\podetails.jsp jsp\common\lookup\glnavigator.jsp jsp\app\wotrack\selectmaterialsonplans.jsp jsp\app\wotrack\selectmaterialsonactuals.jsp jsp\app\quickrep\selectmaterials.jsp jsp\common\assetcatalog\assetmain.jsp jsp\common\system\login.jsp jsp\common\system\footer.jsp

74058 68008

245 254

Updated scripts in Maximo 5.2 Patch 03

Table 9: List of the updated database scripts in Maximo 5.2 Patch 03
Issue Script Issue description

041041

script\V520_4.ora script\V520_4.sqs script\V520_5.ora script\V520_5.sqs

In Equipment Search tab, the select location hierarchy button does not function correctly. In Invoices, when the received quantity is in different units than the entered quantity, the invoice cannot be approved. In Purchase Requisitions, unique index PRCOST_NDX2 in the PRCOST table prevents more than one PRCOST record to be added for one PRLINE.

74198

67003

script\V520_6.ora script\V520_6.sqs

34

Release Notes

Fixed issues of Maximo 5.2 from patch 03 - 09

Maximo 5.2 Patch 09

The following table lists all fixed issues in Maximo 5.2 Patch 09. Application ACTIONS Issue 09-11313 APAR IZ44536 Description The Auto Accept cron task used within the workflow engine stops at irregular intervals. Work Sets take a long time to build when there are many records in the WORKORDER table. In the Purchase Orders application, creating a pricing agreement, and then clicking the Change Status icon, results in an error. A Maximo message tells the user that they have selected an Invalid GL account when they have not. Assignment Manager becomes unresponsive when the status of a work order is changed. If the number of entries in the value list reaches 300, users are unable to log in to Maximo. Project title is not populated in purchase requisitions created from desktop requisitions. In the Work Order Tracking application, attaching a file fails when the file name contains a '#'. The Work Order Tracking application becomes unresponsive when attaching documents to work orders. In Signature Security, enabling E-Sig on the Attach a New Document security option of any application results in an error when a URL is attached to a document. You cannot use special characters in attached document file names.

ALL

08-20780

IZ30749

ASSET CATALOG ASSET CATALOG ASSIGNMENT MANAGER CONFIGURATION CREATE REQUISITION DOCLINK BROWSER DOCLINK BROWSER DOCLINK BROWSER

08-21012

IZ31057

08-21705

IZ32481

07-27490

IZ07306

08-22858

IZ34532

09-11893

IZ45806

08-19371

IZ28617

08-20262

IZ29932

08-21704

IZ32426

DOCLINK BROWSER ELECTRONIC AUDIT

09-13237

IZ49772

07-24182

IZ04174

Maximo .jsp files are vulnerable to SQL injections.

Copyright IBM Corp. 2007, 2009

35

Application EQUIPMENT

Issue 08-22066

APAR IZ33253

Description On the result list page in the Inventory application, users can reconcile the balance of items in storerooms that they do not have access to. In the Work Order Tracking application, user added fields are checked automatically, when navigating past the description field using the tab key. In the Equipment application, when you search the Asset Catalog by the domain attribute of a sub class, no records are returned. In the Equipment application, the Asset Catalog Search fails. When a storeroom is reordered, and one item is not selected, the items that have different vendors are grouped under one vendor. When transferring an item from on storeroom to another, the bin is not created. In the Issues and Transfers application, transferring an item between storerooms results in an incorrect CURRENTLINECOST in the Matrectrans table. In the Issues and Transfers application, if you select a reserved item from a desktop requisition, the following error occurs: Field task is read-only. Inventory balance transactions that do not specify a bin, are not recorded as inventory transactions. In the Inventory application, the conversion rate on the Reorder Details tab can be set to zero. When you add a new item with a current balance of 0, you cannot adjust the current balance. In the Work Order Tracking application, when you search the asset catalog, only 20 items are displayed. In the Work Order Tracking application, when you issue materials to an approved work order, the current balance of the item is not updated in the Inventory application. Unit cost is rounded incorrectly causing the value in the invoice to be different from the value in the matching purchase order. The Invoice application does not process the conversion rate correctly. In the Desktop Requisitions application, the general ledger debit account number used in the Material requisition line does not match with the GL Debit account number in the MRCost table. In the Invoice application, you cannot invoice a purchase order for a vendor that has been disqualified after the purchase order was approved. In the Purchase Orders application, when you approve one of two invoices associated with a purchase order, the purchase order is closed. The Issues and Returns application allows a transfer to the Surplus storeroom from the Surplus storeroom, resulting in incorrect data.

EQUIPMENT

08-23360

IZ35516

EQUIPMENT

08-24041

IZ36589

EQUIPMENT INVENTORY

09-11611 08-17503

IZ45156 IZ24842

INVENTORY

08-17600

IZ25054

INVENTORY

08-20692

IZ30552

INVENTORY

08-20760

IZ30701

INVENTORY

08-20897

IZ31026

INVENTORY

08-21903

IZ32932

INVENTORY

09-10026

IZ40827

INVENTORY

09-12440

IZ47998

INVENTORY

08-12202

IZ15274

INVOICES

08-18221

IZ26329

INVOICES INVOICES

08-19666 08-20195

IZ29119 IZ29881

INVOICES

09-11219

IZ44238

INVOICES

09-11280

IZ44350

ISSUES AND TRANSFERS

07-24467

IZ04303

36

Release Notes

Application ISSUES AND TRANSFERS ISSUES AND TRANSFERS ISSUES AND TRANSFERS ISSUES AND TRANSFERS ISSUES AND TRANSFERS ISSUES AND TRANSFERS ITEM

Issue 08-16448

APAR IZ22248

Description The inventory balance of an item is incorrect after issuing the item to a work order. When reserved items are issued from a desktop requisition, the Matusetrans table is not updated . Issuing a reserved item to a work order does not reduce the quantity of the item reserved in inventory. If you click the undelete icon after you delete an item, the item is not undeleted. In the Issues and Transfers application, the Select Items for Return dialog box does not return issues made against general ledger debit accounts. While Maximo is running, you receive multiple "NoWhere" Java stack traces in the log file. Calculation used during the transfer of capitalized items causes their stock value to be incorrect. After applying patch 08, new items have a period separating the attributes in the description, instead of a comma. In the Item Master application, adding a new item to a storeroom causes poor performance. In the Job Plan application, when you select Go to Labor from the supervisor field, all records that have that supervisor are returned. Labor transactions use the date the transaction was issued, instead of the start date, to determine the financial period. Values containing double backslashes are saved properly, but later when the values are displayed, the double backslashes have been replaced with single backslashes. The Chinese Characters in an XML file error message do not display correctly.

08-19376

IZ28541

08-20266

IZ29921

08-21757

IZ32550

08-23361

IZ35496

08-21715

IZ32499

08-16805

IZ23285

ITEM

08-24422

IZ37203

ITEM

09-11451

IZ44760

JOB PLAN

09-12676

IZ48282

LABOR REPORTING MATERIAL REQUISITION

08-23471

IZ35626

08-17323

IZ24191

MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER

08-16565

IZ22451

08-24382

IZ37137

When you install Maximo 5.2 patch 08 for Maximo Enterprise Adapter, you receive the following error: Error occurred installing mxIntegrationREV633.zip package. When you pass an OTSCALE value with an ENDECIMAL set, and regional settings that are not US decimals, the MAX_LPY_INTERFACE transaction fails. Sending a work order into Maximo using Maximo Enterprise Adapter sends out a transaction.

08-24817

IZ38201

08-25697

IZ40703

08-20426

IZ30093

In Maximo Enterprise Adapter for Oracle 5.2 revision 21, an incorrect Cooperative Applications Initiative file causes PO Line details not to be sent to Oracle when the PO line is deleted.

Fixed issues of Maximo 5.2 from patch 03 - 09

37

Application MAXIMO LOGIN MULTISITE SETUP PREVENTIVE MAINTENANCE PREVENTIVE MAINTENANCE PURCHASE ORDERS PURCHASE ORDERS PURCHASE ORDERS PURCHASE ORDERS

Issue 08-16300

APAR IZ22088

Description Database sessions are not released until the server is restarted.

08-25669

IZ40613

In the Organizations application, when you display the security limits of an organization, the security limits of other organizations are also displayed. Measure points from job plans populate incorrectly in work orders that you created using preventive maintenance.

08-18072

IZ26013

09-11784

IZ45645

Parent work orders generated by the PMWogen cron task are approved, but child work orders are not.

08-19323

IZ28528

The reservation quantity of items in purchase orders is incorrect.

08-19382

IZ28613

Canceling a purchase order does not remove the items awarded from the request for quote, and they are not deleted from the purchase request. In the Receiving application, a negative number in the UNIT COST field of a purchase order results in an error. In the Purchase Orders application, when you add a line item that has the Issue on Receipt check box selected and save, the check box cannot be cleared even though the status of the purchase order is WAPPR. In the Purchase Requisition application, it takes a long time for search results to return. In the Receiving application, when you try and receive a record for a location that you do not have access to, the administrator permission error message is not displayed. When you receive a rotating item that has not been added to a storeroom, a primary vendor is added to the inventory record. In the Purchase Orders application, on the PO lines tab, the values in the Line Cost field are not rounded correctly. When you use Copy PR Line items to PO, the entered date field is populated by the entered date from the PR Line instead of the current date. In the Purchase Requisitions application, when adding a PR line, the Condition Code field is set to read-only until the record is saved.

08-20759

IZ30702

08-23908

IZ36276

PURCHASE ORDERS PURCHASE ORDERS

08-25018

IZ38776

09-11012

IZ43822

PURCHASE ORDERS PURCHASE ORDERS PURCHASE ORDERS PURCHASE REQUISITIONS PURCHASE REQUISITIONS PURCHASE REQUISITIONS RECEIPTS

09-11312

IZ44509

08-17115

IZ23892

09-12009

IZ46728

08-17414

IZ24530

08-25667

IZ40619

In the Approval Limits application, if you belong to one organization, you cannot approve a purchase requisition for other organizations.

09-12254

IZ47453

In the Purchase Requisitions application, users who do not have the Approve Purchase Requisitions right in the Signature Security application can approve purchase requisitions. Select statement returns an incorrect unit cost on a return issue type from the Matrectrans table when returning a purchase order line item.

08-11973

IZ14889

38

Release Notes

Application RECEIPTS

Issue 08-15885

APAR IZ21162

Description In the Receiving application, a negative quantity received value is updated to the associated purchase order. While receiving a purchase order, deleting an item causes the status of the purchase order to be changed to COMPLETE. In the Maximo Receiving application, the total quantity on the material receipt does not match the total quantity on the purchase order, after a rollback occurs during a transaction. In the Purchase Orders application, an extra record is added to the MATRECTRANS table when distributing costs to two general ledger accounts. In the Issue and Transfers application, when you change the location of an item to DHL, the received cost on the purchase order in the Receiving application doubles. In the Receiving application, performing the receipt of a rotating item that belongs to a disqualified vendor results in the following error message: "You must enter a valid company that is not disqualified." In the Receiving application, when you specify a percent that contains thousandths, the line cost is rounded to the hundredths. In the reorder preview pane, sorting items causes items to be no longer grouped by vendor on the PR when reorder is run. In the Receiving application, you cannot create an asset record, when you receive a rotating item that was not previously added to a storeroom. In the Inventory application, the reorder process selects the incorrect cost. The Maximo Chinese Work Order Tracking application returns a "404 not found" error when printing with attachments. In Item Master, the Run Item List Report does not return the correct results when a double-byte keyword is used. In a double-byte language version of Maximo, when the Direct Print icon is used to print the Work Order Details Report the following error is displayed: "Error: 12097 There are no pages to display." Internet Explorer 6 update KB912945 forces an applet or object to require you to click the applet to activate it and then click it again to initiate the action. In the Equipment application, scheduling a report results in an error.

RECEIPTS

08-20014

IZ29688

RECEIPTS

08-20595

IZ30481

RECEIPTS

08-21826

IZ32766

RECEIPTS

08-23795

IZ36027

RECEIPTS

08-25162

IZ38945

RECEIPTS

08-25526

IZ39643

REORDER

08-17793

IZ25535

REORDER

09-10614

IZ42838

REORDER REPORTING ACTUATE REPORTING ACTUATE REPORTING ACTUATE

08-13164 07-25932

IZ16612 IZ05784

07-28961

IZ09102

08-15456

IZ20197

REPORTING ACTUATE

08-24122

IZ36680

REPORTING ACTUATE REPORTING INTEGRATION - ACTUATE REPORTING INTEGRATION - ACTUATE

09-10271

IZ42136

07-28937

IZ09081

In Work Order Tracking, filtering all work orders with attachments and then clicking Print With Attachments, does not print all the work orders.

08-15669

IZ20559

An error occurs when accessing the Factory Service Tab from within the Original Management Console.

Fixed issues of Maximo 5.2 from patch 03 - 09

39

Application SECURITY GROUPS SYSTEM

Issue 08-15375

APAR IZ19918

Description In the Purchase Requisitions application, synonym statuses are available to users that do not have the security rights to approve purchase requisitions. Stopping a query by closing the internet browser, causes the default WHERE clause to run. You receive an error when sorting a table by clicking the column header. The mxserver log file has been modified to allow all SQL statements to be traced.

08-18787

IZ27569

SYSTEM SYSTEM OBJECT SYSTEM USER INTERFACE SYSTEM USER INTERFACE SYSTEM USER INTERFACE SYSTEM USER INTERFACE SYSTEM USER INTERFACE WORKFLOW

09-12783 07-11133

08-17723

IZ25285

Minutes used to report downtime are not properly rounded.

08-24419

IZ37190

The Maximo login page contains a cross-site scripting vulnerability.

08-24421

IZ37194

Malicious code can be stored in the Query Description field and executed when the data is retrieved by a user.

09-10615

IZ42837

In the Job Plans application, when you use quotation marks in a labor description, you receive a Java Script error.

08-25533

IZ39732

In the Locations application, when you associate more than six systems with a location, all associated systems are not displayed in the drilldown.

08-13852

IZ17641

Workflow cron tasks that do not run because the database is unavailable are not rescheduled. Workflow cron tasks that do not run because the database is unavailable are not rescheduled. Initialization time is recorded in the Login Tracking table every time the Auto Accept cron task runs, even when no records are processed by the cron task. Maximo cannot validate work flows that contain recursive processes.

WORKFLOW

08-25558

IZ39834

WORKFLOW

09-11056

IZ43919

WORKFLOW DESIGN WORK ORDER TRACKING WORK ORDER TRACKING WORK ORDER TRACKING WORK ORDER TRACKING

08-24962

IZ38664

08-16862

IZ23387

In the Work Order Tracking application, sorting by fields added by the user, results in an error when the added fields do not contain values. If you change the status of selected work orders to CLOSED, all work orders on the results page are closed. The user is unable to select synonym statuses for work orders.

08-18223

IZ26385

08-19380

IZ28638

08-22481

IZ33797

In the Work Order Tracking application, when you add a labor row on the Actuals tab, the modified date is not updated.

40

Release Notes

Maximo 5.2 Patch 08

Application WORK ORDER TRACKING WORK ORDER TRACKING WORK ORDER TRACKING WORK ORDER TRACKING

Issue 08-24526

APAR IZ37476

Description Work orders are automatically saved when you click the Failure Reporting tab. When you insert a new task on a task work order, the following error message is displayed: "Record has been updated by another user." Work orders contain precautions that are not part of their safety plan.

09-10073

IZ40962

09-10526

IZ42727

09-11607

IZ45191

In a Workflow process, when you approve a work order, the status of the parent work order changes to APPR, but the status of the child work orders do not change. In the Work Order Tracking application, when you create a follow-up work order from another work order, you receive the following error: Record has been updated by another user. Refetch and try again.

WORK ORDER TRACKING

07-26746

IZ06423

Maximo 5.2 Patch 08

The following table lists all fixed issues in Maximo 5.2 Patch 08. Application ASSETS ASSETS ATTACHED DOCS ATTACHED DOCS CHRTACCT Issue 07-25442 07-19388 08-10236 APAR IZ05329 IZ00732 IZ12289 Description Average cost of capitalized item is not zero. Unable to duplicate an asset when it has an associated classification. System cannot execute attached documents function after applying Patch 06.

08-13681

IZ17312

In patch 07, attached documents do not display when attached from their current location. The general ledger account navigator does not sort the account components when SQL Server databases are used.

07-10209

CHRTACCT COMPANY

07-27820 94470

IZ07639

GLCREDITACCT issuing items incorrectly. This status change is not allowed. An error message appears when setting a vendor status to disqualified.

CONFIGURE CUSTAPP

08-11915 06-19947

IZ14808

Crossover from parent WO to child WO does not work correctly. When you access a custom application from an applink, and then select saved queries, all queries are displayed. Purchase Requisitions and Purchase Orders are not generated after user applies a fix to allow negative quantity and line cost. The Receiving Tab does not display any PO Lines where the status is a synonym of APPR. GL Debit account resource code is overridden when a material receipt with 3 or more lines is submitted for direct issue.

DESKTOPREQ

95045

DESKTOPREQ

06-20678

DESKTOPREQ

07-12640

Fixed issues of Maximo 5.2 from patch 03 - 09

41

Maximo 5.2 Patch 08

Application DESKTOPREQ DESKTOPREQ DESKTOPREQ

Issue 07-21189 07-25303 07-29020

APAR IZ01905 IZ05114 IZ09141

Description Unable to add line from another requisition. Currency line cost calculated incorrectly. If you cancel a desktop requisition after the PR is created and approved, an error occurs in the Receiving application. Invalid storeroom message appears when attempting to add to requisition. Canceling the PR inadvertently changes the status of the desktop requisition. After clicking top-level drilldown, children below that level cannot be displayed.

DESKTOPREQ DESKTOPREQ DRILLDOWN

07-29742 08-13391 93768

IZ10251 IZ16970

DRILLDOWN

07-18067

IY99703

Equipment drilldown sorting is incorrect for many pieces of equipment at the same location. Drilldown working incorrectly. Drilldown for Locations application does not show directory structure. Issue related to security audit. Maximo inadvertently displays item availability for the previously selected spare part. The location on a child equipment record is not changed when the parent equipment record is moved to a new location. System writes decimal values to AXVARS as ALN values. This action causes inconsistencies when using multiple regional settings. The Equipment interface does not check for Site ID when deleting equipment. Issue related to duplication of equipment record. Inadvertent error message appears that an asset currently occupies that location. Unique constraint (maximo.eqspec_ndx1) violation when duplicating equipment with an attached specification.

DRILLDOWN DRILLDOWN EAUDIT EQUIPMENT

07-19047 08-11445 07-24182 06-15348

IZ00475 IZ14161 IZ04174

EQUIPMENT

07-12824

EQUIPMENT

07-14296

EQUIPMENT

06-18993

EQUIPMENT EQUIPMENT

07-19469 07-19847

EQUIPMENT

07-20270

EQUIPMENT

07-28964

IZ09107

Unique constraint (maximo.eqspec_ndx1) violation when duplicating equipment with eqnum autokeyed. When you duplicate an existing failure code with many failure code records, the application loops and the server runs out of memory. After you create multiple Field Security records for the same object, you must restart the MXServer after creating the first record. The Belongs to field does not display Parent Item detail.

FAILURE

07-14958

FIELD SECURITY IAS IAS INVENTORY

06-16039

07-13953 07-27138 76752 IZ09469

PM records to not appear to user. When setting up reorder details, the system allows a conversion factor of 0. This value must always be 1 or greater.

42

Release Notes

Maximo 5.2 Patch 08

Application INVENTORY

Issue 92618

APAR

Description Error message "Failure to perform reorder due to exclusive access by user" appears when you select the View Item Availability link in the Reorder Items Detail screen. The reorder process does not convert reorder demand from issue units to order units, resulting in over ordering or under ordering. Cannot move equipment between inventory type locations. When an item is transferred from one storeroom to another, the manufacturer and model data from the sending storeroom do not populate the destination storeroom. When rotating equipment is returned to the storeroom, the inventory cost remains zero. Users without access to a storeroom can perform balance, count, and reconciliation adjustments on the storeroom inventory. On a multiple item reorder, none of the items are reordered if any of the items are not available. Direct issue items are not being displayed for reorder. Memory leak results in server running out of memory.

INVENTORY

94702

INVENTORY INVENTORY

06-15928 06-17426

INVENTORY

06-19108

INVENTORY

07-11021

INVENTORY

07-13629

INVENTORY INVENTORY INVENTORY INVENTORY

07-14387 07-27810 07-30059 07-30421 IZ10897 IZ11659

Application cannot issue an item without a specified bin. Receive "Location is not valid error message when transferring current item. Invalid Location message appears when transferring an item with a NULL bin within the same storeroom. Cannot change default bin after applying patch 06. When issuing materials to an approved work order, the current balance does not get updated. Change to default value not accepted for MINLEVEL column of INVENTORY table. The Transfer In tab does not require entry of a From Location when the GL Debit Account field is populated. When transferring to a courier using internal POs, the GL account is incorrect and the vendor is credited twice. In the Select Reserved Items page, the filter by Work Order is case sensitive. Storeroom access verification take place when rotating items are transferred to courier locations. This action prevents users with limited storeroom access from transferring the items to couriers. INVRESERVE table not updating properly. No system message appears if two users are simultaneously updating the same item.

INVENTORY

08-11325

IZ13834

INVENTORY INVENTORY

08-11840 08-12202

IZ14766 IZ15274

INVENTORY

08-13940

IZ17710

INVISSUE

001842

INVISSUE

06-10909

INVISSUE INVISSUE

06-17197 06-20634

INVISSUE INVISSUE

06-20941 07-13672

Fixed issues of Maximo 5.2 from patch 03 - 09

43

Maximo 5.2 Patch 08

Application INVISSUE INVISSUE INVISSUE

Issue 07-23771 07-24467 07-28534

APAR IZ03846 IZ04303 IZ08505

Description Unable to issue an item to an approved task on an unapproved Work Order. Users can modify the Return from Location to match the To Location. Transferring rotating equipment results in an incorrect update to the storeroom balance. Return of issued materials results in returned amount added back onto reserved items. Long description data entered on a PO line does not carry over to the Invoice line when Copying PO Lines to the Invoice. Loaded cost excludes prorated costs when costs are recalculated. PO does not change to CLOSE status when a service invoice has been approved. When invoicing a line, the InvoiceCost.EnteredAsTask value does not remain the same as it was on the POLine. When distributing costs, all InvoiceMatch records have CostLineNum=1 in the INVOICEMATCH table. The INVOICEMATCH table does not contain a match for all receipts. Edits are not retained after filtering invoice lines. If the associated purchase order has a cost greater than zero, invoices with a zero cost cannot be approved. User change to line cost results in inadvertent change to unit cost. After deleting invoice lines and then adding them back, the system does not add the values of these lines. Invoice variance issue with negative current balance. An invoice price variance transaction is not generated for credit notes. Issue with incorrect invoice variance. User change to line cost results in inadvertent change to unit cost. Approval limits are based on Total Cost instead of Total Base Cost.

INVISSUE

07-28987

IZ09137

INVOICE

88819

INVOICE INVOICE

06-15524 06-16086

INVOICE

06-18587

INVOICE

06-19680

INVOICE INVOICE INVOICE

06-20711 06-20722 07-10901

INVOICE INVOICE

07-11208 07-11810

INVOICE INVOICE INVOICE INVOICE INVOICE INVOICE

07-12830 07-13285 07-14207 07-14470 07-16213 07-29625 IZ10069

Cannot approve invoice if the invoice was entered in a closed financial period. After copying an item assembly structure with a rotating item, message "A non-rotating item may not have a rotating child item" appears.

IAS

07-11058

ITEM MASTER ITEM MASTER

07-25048

IZ04988

When returning items to a new bin, errors occur in financial calculations.

07-26707

IZ06408

Error message appears when changing to a template that has no attributes in common with the existing template.

44

Release Notes

Maximo 5.2 Patch 08

Application ITEM MASTER IPC

Issue 07-27808

APAR IZ07596

Description Cannot add an item to a storeroom.

06-15203

After installing Internet Explorer security update, action is required on printer dialog box. Out of memory errors occur when a new work asset row is added to a job plan with many work assets. IZ01574 Generated task work orders incorrectly copy the measurement point from job plan tasks. Job plan can be saved with labor assigned to a non-existing task. Users can delete labor records even if the labor record is referenced on a work order. YTD Hours are calculated incorrectly when Labor actual records are added in the Quick Reporting application. Cost appears as zero when user attempts, but does not complete, delete action. IZ05698 When system prevents user from performing delete action, current estimate defaults to zero. No locations are displayed when using the location drilldown. When two sites have a location with an identical name and a labor references one of the locations, users cannot delete the other location. When modifying parents of a location in one system, other location rows are deleted. On an Oracle database, when transferring records from Maximo Enterprise Adapter to the interface tables, it fails if the long description is over 2000 characters. IZ09689 Multiple Maximo Enterprise Adapter transactions do not appear.

JOBPLAN

06-21044

JOBPLAN

07-20763

JOBPLAN LABOR

07-30406 07-13253

IZ11635

LABOR

07-15529

LABOR

07-25933

LABOR REPORTING LOCATION LOCATION

07-25933

06-18495 06-18704

LOCATION

07-10983

MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MULTI-SITE

90929

07-13339

07-14418

Using the Maximo Enterprise Adapter Receipt Inbound program, you can override Maximo Receipt Cost. This issue is related to 07-12558.

07-14619

Inventory average cost is updated incorrectly when purchase order lines are partially received through the Maximo Enterprise Adapter interface.

07-27172

IZ06868

Issues related to Maximo Enterprise Adapter incoming transactions after applying hotfix 5.2.601.

06-19929

If the user changes the value in the Site field before saving the record, the incorrect site value is written to the MAXVARS table.

Fixed issues of Maximo 5.2 from patch 03 - 09

45

Maximo 5.2 Patch 08

Application MULTI-SITE

Issue 07-29100

APAR IZ09312

Description Approval limits functionality changed inadvertently between patches 6 and 7. Cannot change child work order status to WSCH. Work orders are not generated when the Use Target Start is cleared and the Next Due Date is in the past. After creating a Job Plan and selecting Update Associated PMs, a database error appears.

PM PM

07-10788 07-12436

IZ09958

PM

07-15602

PM PO

07-29556 034773

IZ09958

Could not change child work order status to WSCH. When a PO is partially received and the non-received purchase order line is deleted, the Receipt Status is not updated when the PO is approved again. The Issue on Receipt field cannot be cleared when the work order field is cleared on the PO line. When a release PO has a vendor with a currency other than the organization base currency, the total base cost is not reflected in the base currency, until the purchase order is approved. Approving an invoice based on a PO, with partially received materials, does not close the PO. POs can be approved against canceled desktop requisitions. This History Flag is set to N on default queries the first time you access the application. "The quantity cannot be less than the quantity that has already been received" error messages appears when updating an unapproved PO line with a partial receipt. If a release PO has a vendor with a currency other than the organization base currency, the total base cost is changed to the total cost when you save the release PO.

PO

74694

PO

06-11196

PO

06-14449

PO PO

06-19765 06-19808

PO

06-20942

PO

06-21523

PO

07-11082

IZ12684

Purchase requisition lines are copied to the PO in reverse order from their listing on the purchase requisition. After filtering for a PO line which is not the last line number, you cannot create a row. Incorrect line cost when approving and disapproving a PO. After filtering for a PO line which is not the last line number, if the user creates a line and saves it, the POCOST table does not populate with new line cost data. After filtering and then adding a PO line, the total cost of the PO is set to the value from the line that was added. The cost of all other lines is ignored. User cannot approve a blanket PO when the error message "Total cost of line items is greater than total cost of purchase order" appears.

PO

07-11721

PO PO

07-12125 07-12317

PO

07-14432

PO

07-17078

PO
46

07-19846

IZ01039

RFQ does not remain closed when creating a change order.

Release Notes

Maximo 5.2 Patch 08

Application PO

Issue 07-20286

APAR

Description Total Cost calculates incorrectly when you use the filter function and then revise a PO line quantity.

PO PO PO PO

07-26934 07-30013 08-10574 08-13022

IZ06616 IZ10873 IZ12684 IZ16491

Distributed costs between GL accounts are incorrect. If user selects the Service check box, the loaded cost does not update. PR Lines copied to PO in reverse order to how they are listed on the PR. When using foreign currency for a blanket PO, the calculation for available balance when viewing the blanket PO is incorrect. RFQ does not remain closed when creating a change a change order. If you enter an item on a purchase requisition line where the RLIN1 and STORELOC values are populated from the APPFIELDDEFAULTS table, the defaults are cleared. The Service check box is not read-only after an item is entered on a PR line. The Create PO screen does not display the input fields for the PO number and the PO description. If filtering for a PR line and the line is edited and saved, the Total Cost is set to the cost value from the line that was edited. The system ignores all other lines. An error "Unable to save after changing status, Record has been updated by another user. Refetch and try again" appears when canceling a PR generated from a Desktop Requisition.

PO PR

08-14425 06-18872

IZ18483

PR PR

06-20747 07-10451

PR

07-14083

PR

07-17447

PR PR RECEIPTS

07-23126 07-23432 63714

IZ03344

PR status cannot be changed to cancel if the associated MR is not approved. After you apply a hotfix for issue 06-20098, deletion marks are not visible. When receiving a lotted item, the bin number does not default to the default bin specified in Inventory. The Lot number does not automatically populate.

RECEIPTS RECEIPTS

86894 94701

IZ12170

Incorrect MBOATTRIBUTES point to vendor.name and changedate. Java script error occurs when receiving a rotating item with quotation marks ( " ) in the description. Problem receiving partial items when ordered in one type of unit and received in a different type of unit. When receiving items after populating the binnum with default table data and adding an item, the binum populates incorrectly. An error message, "Attribute FROMSTORELOC does not exist" appears when returning a receipted service line. Receipts are not allowed when the PO line references a closed parent work order and task. When you receive a service cost that is distributed over two GL accounts, the system doubles the cost.

RECEIPTS

94706

RECEIPTS

06-17232

RECEIPTS

06-17377

RECEIPTS

07-10354

RECEIPTS

07-10866

Fixed issues of Maximo 5.2 from patch 03 - 09

47

Maximo 5.2 Patch 08

Application RECEIPTS RECEIPTS

Issue 07-11012 07-11502

APAR

Description System does not assign costs to the Equipment field. Receipts are not allowed when the PO line references a closed task work order. The unitcost and actualcost are not calculated correctly for return receipts after exchange rates updates. After applying a hotfix for issue 06-20678, the Servrectrans Unitcost field shows 0 after receiving a Service PO with a unit cost greater than 0. Invalid date/time format appears when searching for company name. When receiving material into a storeroom, the control account from the inventory record overrides the debit account on the PO Line.

RECEIPTS

07-13171

RECEIPTS

07-14681

RECEIPTS RECEIPTS

07-18766 07-21246

RECEIPTS RECEIPTS

07-21582 07-23431

IZ02332

After running a report, a runtime error appears when using the Search tab. After you apply a hotfix for issue 06-20098, saved rows can inadvertently be edited.

RECEIPTS

07-26112

IZ05914

When selecting ordered items, purchase order line numbers appear in reverse order. After approving service receipts, no message appears and the check box remains cleared. Unable to perform a material receipt on a PO. Received cost is duplicated when using distributed costs. Inspection status reads approved for a returned good with a receipt that has not been inspected. Error message that the date and time format is invalid when searching a company name. After installing patch 07, material receipts no longer works. When multiple sites have storerooms with identical names, the application uses the first site created rather than the current one.

RECEIPTS

07-26467

IZ06070

RECEIPTS RECEIPTS RECEIPTS

07-26812 07-26817 07-28008

IZ06532 IZ06556 IZ07792

RECEIPTS

08-10133

IZ12170

RECEIPTS REORDER

08-13694 06-19982

IZ17334

REORDER REORDER

07-22802 07-29802

IZ03081 IZ10674

System orders one item too many. When the current balance equals the reorder point, the reorder does not take place. Incorrect page is returned after performing reorder tasks. When users click the cancel button when printing a detail report, then click the navigation bar to go to the next page, another prompt to print the detail report appears. Due to a change in underlying Acutate software, inconsistencies occur when sending reports though e-mail. The Select Value window opens after a field value is cleared in Lookup.

REORDER REPORTS

08-12481 60628

IZ15587

REPORTS

88080

REPORTS

06-14519

48

Release Notes

Maximo 5.2 Patch 08

Application REPORTS

Issue 06-18380

APAR

Description Report PDF files are not removed from the webserver directory once the report has successfully printed. With the silent print fix, the input output stream does not close. Files are not deleted. Timezone functionality does not account for the new Energy Act requiring changes to daylight saving time. PDF file not found when printing a French-language report. Toolbar icon for e-mail attachment creates an incorrect file type (not a .PDF file). When using Direct Print functionality, the printed report does not use the regional locale settings from the user profile. Unable to filter storerooms when running the Inventory Transaction Report.

REPORTS

06-18413

REPORTS

06-19490

REPORTS REPORTS

06-20050 06-21148

REPORTS

07-12185

REPORTS REPORTS

07-18518 07-28748 IZ08788

Report prints with additional attached page when printing with image or text files. Report does not print with .PDF attachment. Report does not print with image or text files attachments. The PO value on the RFQ lines is blanked out if a change order is processed against the original purchase order. Signature security settings in equipment do not have the correct functionality when you change update to N. Users without access to KPI Manager application can select KPI applications from dashboard. Also, system hangs up when applications are selected this way.

REPORTS REPORTS RFQ

07-28749 07-28752 07-14643

IZ08786 IZ08775

SIG

07-11574

START CENTER

07-15241

SYSTEM

11899

IZ13195

Workflow cron tasks do not run when the application server loses its connection to the database and then reconnects. Delimiters are included in the GL account length verification even when writing delimiters to the database has been turned off, preventing entry of a full GL account number. Multiple issues occur with the silent print fix. When you use Advanced Search to enter search criteria and one of the results is bookmarked and selected, the system corrupts the search condition. The selected record does not appear. Oracle performance degradation because of action from SQL statement When you run reports after applying three group restrictions, the report windows displays an error message. Two tasks are inserted for each new row when a job plan has at least six tasks and your Java Runtime Environment is version 1.5.

SYSTEM

06-16049

SYSTEM SYSTEM

06-17625 06-19482

SYSTEM REPORTS

07-11956 07-12656

SYSTEM-OBJ

06-21513

Fixed issues of Maximo 5.2 from patch 03 - 09

49

Maximo 5.2 Patch 08

Application SYSTEM-OBJ

Issue 07-11133

APAR IZ09486

Description Customer requested that mxserver log file include information so that sql statements and blocks can be traced fully including INSERT and UPDATE statements. When you create custom applications at the 5.2 level from upgraded 5.1 custom tables, a blank screen appears when you select the Select Records check box. Review Requisition page displays a "-" in the item column for requisition lines with no item. If you select this item, an Item Details page appears with unrelated item information. The AUTOCOMPLETE attribute is not disabled on forms where sensitive information, such as passwords and user names, is entered. Select Value dialog box appears inadvertently. When users enter double slashes (\\) in a field and save the record, the display of the double slashes is converted to a single slash. Description becomes a required field for task work orders on the Plans tab. After applying patch 6, the job plan tasks tab focus reverts to first line. Cursor tabs to incorrect field in PR lines table row. When inserting more than six job plan tasks, two job plans are created for each new row. After applying a hotfix for issue 06-20321, the select value list does not display in every application. Screen hangs up after adding and deleting a new row.

SYSTEM-UI

06-13267

SYSTEM-UI

06-16019

SYSTEM-UI

06-18422

SYSTEM-UI SYSTEM-UI

06-18697 06-18918

SYSTEM-UI SYSTEM-UI SYSTEM-UI SYSTEM-UI

06-19494 06-20098 06-20321 06-21517

SYSTEM-UI

07-10450

TAG/LOCK OUTS TAG/LOCK OUTS TAG/LOCK OUTS WORKFLOW

06-20200

07-19714

IZ09117

Many records are generated in the SafetyLexicon table when duplicating tagout records in Maximo. When duplicating Tagouts with Tagout ID autokeyed, many records are erroneously generated. View Status/Workflow History does not display memos entered when the invoice status was changed. Task work order status not updated by workflow. Unable to change status when the user time zone is ahead of the database time zone and the actuals finish date and time are ahead of the database server time. When failure and problem codes are changed and you access the Failure Reporting tab, an error message displays, "Error building Table Body for the table: FAILURE_REPORT." System does not display message to user that a required field has been left blank.

07-28968

IZ09117

07-11318

WORKFLOW WOTRACK

07-14874 88850

WOTRACK

035463

WOTRACK

91741

50

Release Notes

Maximo 5.2 Patch 08

Application WOTRACK

Issue 06-11067

APAR IZ09456

Description Message displays "Attribute ACTUALDATE does not exist" when you attempt to add a tool on the Work Order Actuals page. Inefficient use of eventListener in the Asset, MatUseTrans, LabTrans, PM, and WO business objects. This item causes performance issues. When the Maximo Server and client are in different time zones, the Actual Finish time is ahead by a few hours. The Planned Materials field populates with the wrong item when Catalog Search is used to find and select an item.

WOTRACK

06-16290

WOTRACK

06-19141

WOTRACK

06-20814

WOTRACK

06-26746

IZ06423

When creating a follow-up work order from another work order, receive error message that the record has been updated by another user. Parent work order information displays in results tab. Report Downtime does not allow entry of negative numbers in the Hours field. When you select a subset of work orders on the search results page and perform the change status action, all work orders are changed rather than only the work order selected. You are able to delete failure codes from history. When selecting the 'Go To Crafts' link, the system does not return the correct values. System lets users delete Failure Reporting information about closed work orders. After applying a hotfix for issue 88850, Maximo uses the current date time rather than the date time you entered. Order units cannot be modified for direct issue planned materials. When entering Actual Labor transactions, the Actual Start date is set back to Labor Start date. The Actual Finish date is incorrectly set to the previous Actual Start date. Incorrect estimated cost appears when using exchange rates and adding or removing a work order to a blanket release.

WOTRACK WOTRACK

07-10266 07-11309

WOTRACK

07-12751

WOTRACK WOTRACK

07-13167 07-13245

WOTRACK

07-14609

WOTRACK

07-14615

WOTRACK WOTRACK

07-15818 07-17627

WOTRACK

07-17629

WOTRACK WOTRACK

07-22920 07-25358

IZ03184 IZ05169

Inability to enter a new field in GL MAXTYPE. Unit Cost and Line Cost are not read-only when recording material actuals on work order. When creating a follow-up work order, error message appears that record has been updated by another user. Unable to save record if you attempt to save without putting a value in the Labor Code field.

WOTRACK

07-26746

WOTRACK

07-27804

WOTRACK

07-28005

IZ07790

When changing the status of tasks, the Change Status dialog box appears with the incorrect task.

Fixed issues of Maximo 5.2 from patch 03 - 09

51

Maximo 5.2 Patch 08

Application WOTRACK

Issue 07-28352

APAR IZ08420

Description When user deletes a PO line with a foreign currency, the system incorrectly calculates the work order.

Maximo 5.2 Patch 07

The following table lists all fixed issues in Maximo 5.2 Patch 07. Application ALL ASSET ASSET CATALOG Issue 06-17390 06-12008 06-10690 Description Users can approve PRs, POs, and receipts against a disqualified vendor. Incorrect values are populated while performing an Asset Catalog Search. Clicking the Refine button and entering a filter sometimes produces results where no records are displayed and the table header shows information such as "Displaying 11-1 of 1". In Assignment Manager, the availability time continues to show a non-zero value after setting the hours of availability to zero. This is a follow-up to issue 93394. In Assignment Manager, when entering retrospective work assignments and then completing the assignment the actual finish date is displayed incorrectly. If the labor hours are 0:00, clicking the OK button in the Assign Labor screen of Assignment Manager only refreshes the screen. Error: "The Quantity Cannot Be Less Than Zero" When the User Attempts to Interrupt an Assignment With a Status of Started. Unable to attach a file that contains double -byte characters.

ASSGNMGR

06-15559

ASSGNMGR

06-16389

ASSIGNMENT

06-16194

ASSIGNMENT

06-18572

ATTACHED DOCS ATTACHED DOCS COMPANY

94351

06-17704

When attempting to attach a new document with E-sig option Attach a new document enabled, an error occurs; "Required field document folder is blank." When modifying the changes to the contact information in Companies using the filter, the changes are not saved. A status of CLOSED should be included in the value list of financial control. The cron task does not shut down when the Maximo application is undeployed in the WebLogic Server administrative console. When a WOGEN cron task is scheduled to run on a single time basis and more than one logical node is running on the application server, the cron task executes on each of the nodes. The GL account code on a requisition line is overwritten if the user clicks the Previous Step button and enters a GL account code on the Charge Info page, then clicks Next Step to return to the requisition line. Requisitions can be submitted without requisition lines.

82982

COSTMGT CRONTASK

84935 83321

CRONTASK

06-16516

DESKTOPREQ

06-11311

DESKTOPREQ

06-12113

52

Release Notes

Maximo 5.2 Patch 08

Application DESKTOPREQ

Issue 06-12523

Description When using the Price and Availability button the description and storeroom is cleared on the requisition line. Requisition line hyperlinks on the Open or Draft Requisition pages render empty pages if during the original requisition entry, any line higher than line 1 was deleted. When choosing an item from favorite items, the storeroom field is cleared and the vendor field is populated. When creating a requisition, the 'Inspection Required' flag can be turned off even though it was originally set to required in Inventory. Some charge data are populated on templates when the template is created from a draft requisition. MRs cannot be charged to completed work orders. GL account number and location from a work order are not populated on the Desktop Requisition line when the REFWO field is unhidden and work order data are entered. Performance problems occur with entry of requisition lines referencing a storeroom that has several hundred thousand MATUSETRANS records. The updated unit cost is not saved when submitted on a requisition. Once Patch 5 is applied attached documents can no longer be viewed.

DESKTOPREQ

06-12870

DESKTOPREQ

06-14925

DESKTOPREQ

06-16077

DESKTOPREQ

06-16960

DESKTOPREQ DESKTOPREQ

06-17136 06-17299

DESKTOPREQ

06-19634

DESKTOPREQ DOCLINKBROWSER EQUIPMENT EQUIPMENT

06-20779 06-17093

82272 95018

Equipment number is not reset if it is applied to a different IAS When an equipment record is duplicated, the EQUIPMENTSPEC tables CHANGEBY and CHANGEDATE columns are not populated. Users must select the TO SITE twice when Moving an equipment record from one site to another site. Slow performance in the Equipment application on inserting a new equipment record. The Equipment interface does not check for Site ID when deleting equipment. System writes decimal values to AXVARS as ALN values. This action causes inconsistencies when using multiple regional settings. In the Failure application, designating a Problem Code for deletion does not designate associated Remedies for deletion. After clearing a failure class and canceling out of the failure hierarchy screen, the problem code still carries over onto the failure code tab. In Inventory, an incorrect bin lotnum combination is displayed in the issue current item dialog box where the item has multiple bin lot combinations. In Inventory, the conversion factor does not work correctly when transferring items between internal storerooms. Maximo loses focus after the first few records when using the tab key in the Inventory Physical Count Adjustment page.

EQUIPMENT

06-19657

EQUIPMENT EQUIPMENT EQUIPMENT

06-16274 06-18993 07-14296

FAILURE

06-12417

FAILURE

06-16909

INVENTOR

67682

INVENTOR

06-10769

INVENTOR

06-14701

Fixed issues of Maximo 5.2 from patch 03 - 09

53

Maximo 5.2 Patch 08

Application INVENTOR

Issue 06-18330

Description In Inventory, message "Balance in the bin will become negative as a result of this transaction popup" displayed when attempting an item return on an internal PO. When action "View Item Availability" is performed and the purchasing tab is selected, it is possible to view private POs from other sites. No warning or error message is displayed when an expired lotted item is issued. Maximo is allowing the Economic Order Quantity to be set to zero. Item returns are producing RETURN and CURBALADJ transactions instead of just RETURN transactions. The JVM heap experiences spikes when action "Reconcile Balances" is performed against a storeroom with many inventory records. When the default bin has no balance a rotating item cannot be issued from Inventory. After creating a default value for the Category field in Inventory it is not defaulting to that value. When ordering from a cloned application of Inventory, the reorder results have null values in the fields. A database error 904 is received when sorting by description on the Issue tab. When clicking the Attached Document tab in Inventory the application stops responding. When backdating transactions such as an Issue or Labor Reporting, no choice is given as to whether the next or current financial period should be used. When an item previously issued to labor is returned, the Issue To field is cleared and set to read only, so the correct labor value cannot be re-entered. When transferring to a courier using internal POs, the GL Account is incorrect and the vendor is credited twice. Item reservations cannot be deleted when the reservation is for a work order at WMATL status. In Issues and Receipts, poor performance is observed when using the Select Items for Return function. In Issues and Transfers, error message "POLine 1 was not included because user does not have access to storeroom Central" is incorrectly displayed. The CURBAL field is not being updated on the "All Lots" page of View Item Availability In the Transfer out tab, the rotating equipment and asset are not being populated from the lookup. Users transferring items to courier or labor locations must have access to the receiving storeroom. Error: 904 occurs when doing an order by on the quantity transferred column on the PO items button of the transfer out tab

INVENTORY

68414

INVENTORY INVENTORY INVENTORY

87826 94098 95176

INVENTORY

06-13386

INVENTORY INVENTORY

06-15591 06-15725

INVENTORY

06-16874

INVENTORY INVENTORY INVISSUE

06-17162 06-17270 83673

INVISSUE

95207

INVISSUE

06-10909

INVISSUE

06-11688

INVISSUE

06-12439

INVISSUE

06-14226

INVISSUE INVISSUE

06-17076 06-17140

INVISSUE

06-17432

INVISSUE

06-17456

54

Release Notes

Maximo 5.2 Patch 08

Application INVISSUE

Issue 06-17561

Description In Issues and Transfers, when transferring an item using an internal PO, the unit cost is captured from the Purchase Order instead of being captured from the issue cost of the supplying storeroom. Exchange rate cannot be overridden on an invoice. In Invoices, duplicating an invoice where the invoice number is greater than eight characters fails. Message "Could not change Invoice xxxx to APPR". The sum of all invoice quantities for invoice xxxx for purchase order line exceeds the quantity that has been received." is displayed due to rounding errors that occur when copying PO Lines to the invoice. When using the action 'Copy PO Lines', the Total Cost and Line Cost do not get populated until the record is saved. Invoice lines can be approved for services having a line quantity equal zero. Invoice lines can be approved for services having a line quantity equal zero. InvoiceMatch records for the variance are not being created for Service Lines in the database. Performance problems are experienced after applying 5.2 Patch 05 on a SQL Server database. Performance in the Invoice application is slow on clicking the new invoice icon. Invoices with a WAPPR or ENTERED status cannot be deleted if the invoice had previously been in a workflow. Return transactions on credit invoices are not displayed in the Materials tab when no PO is entered on the invoice header and the user is copying PO lines to the invoice. In Maximo, rounding of unit cost values causes Receipts and Invoices to not match with the Purchase Order. In Invoice, a company long description does not populate on creating an invoice where the company is listed as vendor. Items with MATRECTRANS records can be deleted as long as the reconciled inventory balance is zero. An item that is on an open purchase order with a status of WAPPR can be deleted from Item Master In Maximo, the add item as spare part flag does function correctly when performing a Desktop Requisition to a work order with an associated equipment record. When deleting a job plan, the job tasks, labor, and material are still present in the database. In Labor Reporting, the Financial period field is not updated in the Labtrans table on entering labor transactions. Changing parent/child relationships in complex network systems can cause Maximo to loop.

INVOICE INVOICE

75821 85223

INVOICE

88751

INVOICE

0610015

INVOICE INVOICE INVOICE

06-10608 06-10609 06-11851

INVOICE

06-12204

INVOICE INVOICE

06-12550 06-15027

INVOICE

06-16044

INVOICE

06-17453

INVOICE

06-17883

ITEM

94389

ITEM

06-13443

ITEM

06-13729

JOBPLAN

06-14511

LABREP

06-10545

LOCATION

88992

Fixed issues of Maximo 5.2 from patch 03 - 09

55

Maximo 5.2 Patch 08

Application LOCATION

Issue 92806

Description In Locations, unable to search for locations whose name contain quotation mark characters. In Locations, a "Not a valid number" error popup is displayed when using the detail menu Goto Failure Codes link. The lochierarchy.children flag is incorrectly set to N when a location with a child record has its parent record changed. Adding a child to a parent on a network system can cause Maximo to loop. Material reservations are not sent out of Maximo unless the work order is also sent out.

LOCATION

06-10583

LOCATION

06-11675

LOCATION MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER PERFORMANCE PM

06-14510 041097

90929

On an Oracle database, when transferring records from Maximo Enterprise Adapter to the interface tables, it fails if the long description is over 2000 characters

06-10888

Although the INV switch in MXCOLLAB is set to not update inventory balances, the check for negative balances still takes place and incoming issue transactions fail if the issue amount exceeds the quantity available. Poor performance with Maximo Enterprise Adapter when the number of records in the queue grows when records are transferred from the mxin_inter_trans_queue.

06-19555

06-18443

Maximo Enterprise Adapter stops transactions when a long incoming transaction is getting processed.

06-17120

When using the currency or organization lookup in Invoice the performance is slow

06-14541

In Preventive Maintenance, on changing the parent in the 'Belongs To' field, error messages 'Ancestor #### Already Exists' and 'Required Field Ancestor is blank' are displayed. When a PM with Override Due Date Information is Duplicated, the duplicated PM's Extended Date field is blank and read-only. The Adjust Next Due Date check box is checked and read-only. Meter reading is not being updated when the option "Set Reading at Last WO" e-sig is enabled. In PMs, error "Could not change child work order status to WSCH only PM generated work orders may have the status WSCH" message displayed when generating work orders from PM containing a job plan with tasks. Error "Total cost of line items is greater than total cost of purchase order" is displayed when attempting to approve a Blanket PO having multiple lines with large line costs. Internal POs are charging the wrong GL Account. Error message "The quantity cannot be less than the quantity that has already been received" is displayed when users attempt to change a PO line quantity on a previously approved and partially received line.

PM

06-15129

PM

06-17862

PM

07-10788

PO

06-11132

PO PO

06-12056 06-12168

56

Release Notes

Maximo 5.2 Patch 08

Application PO

Issue 06-14774

Description The Pay on Receipt flag on POs created from RFQs is not populated with the vendor Pay on Receipt. Users with approval limits equal to 0 are able to approve POs. It is possible to create Release POs with total amounts in excess of the Blanket POs remaining amount. When there is a PR that has the same number and is in two different sites, the copy PRlines to po does not work correctly. Receiving a Rotating Item on an Internal PO, user can select Eqnum that is not associated to Itemnum. Inspection required is selected on PO lines with rotating equipment on internal POs. If a blanket PO has several thousand releases, performance problems are encountered when users change status on newly created releases for the blanket PO. Inventory reserves are only updated with the last item on an internal PO. Blanket POs cannot be approved when the release amount is exactly equal to the blanket amount remaining. If the scale is set to 2 but the user has it set to display more than 2 on the jsp page the poline cost gets miscalculated. When action "View Blanket PO" is performed repeatedly against the same PO, the display of uncommitted costs is incremented by the original uncommitted cost amount. When a status change is attempted on a price agreement PO, an exception is thrown with a message indicating a right parenthesis is missing. Maximo counts Service amounts reported on a Blanket purchase order, whereas only service amounts reported on a Released Purchase order should be counted. Leaving the service check box cleared on the PO Line results in incorrect display of estimated costs in the View Costs page of the Work order. In Purchase orders, the wrong exchange rate is displayed on a release po. In Purchase orders, on deleting PO Lines selected using the Filter function, the PO Total cost is incorrectly displayed as zero. In PO, taxes roll up to the committed cost even when inclusive fields are set to 'N' for the Company and PO tables. PRs without PR lines cannot be canceled. PRs in a canceled status cannot be routed in workflow. In PR when the INVVENDOR.conversion is null in the database an error, invalid number is received. PRs with lines referring to a closed work order can be duplicated. When creating a REL type PO from PR using the 'create PO' option, the po number is not populated on the PR line until the record is saved.

PO PO

06-15627 06-15982

PO

06-16149

PO

06-16734

PO PO

06-16739 06-17375

PO PO

06-18187 06-18505

PO

06-18694

PO

06-18778

PO

06-20208

PO

90515

PO

94678

PO PO

06-11196 06-12107

PO

06-17315

PR PR PR

61903 63114 87748

PR PR

87917 06-10816

Fixed issues of Maximo 5.2 from patch 03 - 09

57

Maximo 5.2 Patch 08

Application PR PR

Issue 06-13306 06-13370

Description Action "Create PO from PR" creates PO lines for PR lines associated with an RFQ. In Purchase Requisitions, an error message "The sum of all invoice quantities for invoice xxxx for purchase order line 1 exceeds the quantity that has been received" is displayed as the invoiceline does not take conversion factors into consideration. Item long description is not retained when an existing item number is changed and a new item long description is entered. Action "Create PO" does not populate a user custom crossover field with vendor delivery data.

PR

06-14838

PR

06-13371

QUICKREP

91000

In QUICKREP, After inserting the sixth task the status is set to WAPPR instead of INPRG. Database error occurs when receiving rotating items In Receipts, returning a lotted item on a PO results in a negative current balance in Inventory, even though negative transactions are not allowed. Warning is not raised when receiving a material again an unapproved work order where the PO was originally approved against the same approved work order. When selecting ordered items in Receiving the Received Date can be changed to a future date. The total received cost can be different from the total ordered cost when conversion factors and unit costs have multiple decimal digits. In Receipts, Maximo does not calculate the received cost when receiving internal purchase orders. In Receipts, the Actual date displays a date prior to the current date for the first receipt line but not for the associated cost distribution Return to storeroom transactions are not writing records to the MATUSETRANS table. In Receipts, an error message "Record has been updated by another user; refetch and try again" is displayed when attempting to approve a material receipt. An exception is thrown with message "Attribute FROMSTORELOC Does Not Exist" when users click the Select Ordered Services button more than once while receiving a PO. An exception is thrown when users attempt to select ordered items on the Select Ordered Items page, and they cannot return to the Receiving page. Error message "Receipt failed to be created for selected row 1.Attribute FROMSTORELOC does not exist" is generated when users attempt to select PO Service lines. System does not assign costs to the Equipment field. Error message "Delete is not allowed on REORDERPAD" is displayed when users attempt to delete a row from the preview reorder page for a reorder of direct issue items.

RECEIPTS RECEIPTS

82706 89975

RECEIPTS

93408

RECEIPTS

93843

RECEIPTS

94647

RECEIPTS

06-10451

RECEIPTS

06-11246

RECEIPTS RECEIPTS

06-12248 06-14780

RECEIPTS

06-15846

RECEIPTS

06-19518

RECEIPTS

06-20150

RECEIPTS REORDER

07-11012 65143

58

Release Notes

Maximo 5.2 Patch 08

Application REORDER

Issue 93490

Description Reorder is not reordering materials entered through Desktop Requisitions for a particular work order if those materials are also listed in the planned materials of the work order. Payment terms are not set on PRs or POs generated by reorder when the ordered items are under a price agreement. Reorder hangs with page and table locks on the reorder pad table when it is run for more than one location simultaneously The reorder process is not grouping PR lines by vendor, nor is it using the Multisite Inventory Option Reorder setting that specifies the maximum number of lines per PR/PO. Reorder is using INVVENDOR.LASTCOST rather than the supplying storeroom issue cost on internal PRs and POs. The inventory promised delivery time is not being used to calculate the required date of a PR line. Error message "Object REORDERPAD is read only" is generated when direct issue reorders take place. In Maximo, a class cast exception is thrown while attempting to reorder direct issue items. When PR lines are copied to an RFQ, the PR phone and fax are not populated on the RFQ. When adding a standard service on the RFQ lines tab an error is received, "TAX1CODE does not exist. Synonyms of SENT status are not viewed as valid status codes. Order Unit field does not auto-populate when entering a storeroom first then item number on an RFQ line In Request for Quotations, RFQ Lines display incorrect data when lines on a PO created from the RFQ are deleted. In the Copy PRlines screen, the user can see canceled PRs if the PR exists in two sites. When a PR is associated with an RFQ and a PO is generated from the RFQ, the PR is not automatically closed. When a route record is deleted it gets deleted from the routes table but not the route_stop table. It should be deleted from both. In the Scheduling Status tab, the Submission time and Next Start Time are displayed in English on the report instead of German. The Safety plan filter does not function correctly in the Work Order Tracking application. After creating a storeroom, clicking the Item tab produces a Null Pointer Exception error. In Maximo, a Java deadlock occurs when a single user tries to submit multiple requests without waiting for the initial requests to complete. In Maximo, when using the quick key search field and no records are returned, Maximo returns user to the Search tab, however, the IsTask and History fields display as null.

REORDER

06-11069

REORDER

06-11363

REORDER

06-17436

REORDER

06-17448

REORDER

06-17459

REORDER

06-18819

REORDER

06-20223

RFQ

90786

RFQ

93528

RFQ RFQ

95215 06-10857

RFQ

06-15658

RFQ RFQ

06-17189 06-17383

ROUTES

06-14787

RPT-ACT

06-13531

SAFETYPLAN STOREROOM SYSTEM

06-11630 06-14245 68002

SYSTEM

93538

Fixed issues of Maximo 5.2 from patch 03 - 09

59

Maximo 5.2 Patch 08

Application SYSTEM

Issue 94581

Description In Equipment, an "invalid GL account" message is displayed when the rotating suspense account is changed - SQL server only When users implement scenario 1 listed in KB document M04727, actual labor start time and hours are cleared after the user presses the tab key. In Maximo, selections made in the KPI Dashboard are lost when the records are sorted by KPIs. In Maximo, the Save, New, and other icons disappear on saving a record. In Maximo, using the quick search function when not on the main or search tabs returns results to the main tab. In Maximo, when advancing to the next record, default values are cleared. An error is received, "PMNUM is not a valid attribute when searching for work orders down the hierarchy based on the PM field In Maximo, slow performance is observed when attaching a job plan with 250 tasks to a Work order. When using a "&" as a value in the lookup, any value to the right is not displayed. QBE lookups cannot be used when restrictions have been placed on the lookups. After clicking the Cancel button on the Move Equipment screen the record disappears. In Maximo, a performance issue was observed when querying Work order records using the Quick Key search from the Work Order tab. Upon selecting a date from the calendar look up, then adding a description and tabbing out causes the calendar to pop open again. Clicking the View Details button on the POline does not result in the row being displayed. When thousands of GL records share the same first GL component, GL Navigator searches are inefficient and operate slowly. When updating from patch 4, the INHERITEDFROMITEM column needs to be set to 'Y' in the EQUIPMENTSPEC AND LOCATIONSPEC table or the update fails. In Preventive Maintenance, work orders are generated for disabled sites incorrectly. When labor is restricted from accessing other labor information, records cannot be routed in workflow if the assignment is to a labor group. When a routed assignment is in a workflow step where the workflow criteria specify "When all assignments are accepted", WFTRANSACTION.MEMO is not populated. The maximum assembled length for a notification message can be exceeded. Error message "The labor group <laborgroup> does not exist for this assignment at site <site>" needs WFID and RECORDID values to be added to assist in debugging the root cause of the error. In Work order Tracking, using the Supervisor 'Goto Labor' detail lookup leads to the incorrect labor record.

SYSTEM

06-10589

SYSTEM

06-13352

SYSTEM SYSTEM

06-18636 06-21140

SYSTEM-OBJ SYSTEM-OBJ

06-11972 06-17751

SYSTEM-OBJ

06-18234

SYSTEM-UI SYSTEM-UI SYSTEM-UI SYSTEM-UI

89721 06-11905 06-13854 06-14406

SYSTEM-UI

06-18016

SYSTEM-UI SYSTEN-UI

06-20372 74109

UPGRADE

06-17302

WOGEN WORKFLOW

94631 06-16209

WORKFLOW

06-17311

WORKFLOW WORKFLOW

06-17676 06-17677

WOTRACK

041161

60

Release Notes

Maximo 5.2 Patch 08

Application WOTRACK

Issue 87660

Description After clicking the Clear button on the Find tab, the History flag and Is task fields do not refresh back to 'Y' values. In Work order Tracking, the estimated labor cost is updated incorrectly when the pay rate of labor is changed. In Work order tracking, the APPR status is not available as a status change option when the work order is in the WSCH status. In Work order Tracking, the WoAncestor table is not updated correctly on duplicating a work order record. When using the reports icon in work order tracking, performance is slow When duplicating an approved work order with material reservations the REQUESTNUM is not set to null. In Work order tracking, a work order can be closed without a warning even when it is referenced to an unapproved purchase order. In Work order Tracking, when a work order is moved within a hierarchy, common ancestors are being incorrectly deleted. In Work order tracking, the Remove Work Plan action in Work Order Tracking does not remove the job plan if only a job plan number exists on the job plan record. In Work order Tracking, planned material reservations are not updated correctly when switching to a Direct Issue item on an approved work order. The work order lockout record is missing the eqnum. In Work order Tracking, on selecting work order having a parent/child relationship and switching between parent and child, the child work order is not displayed. The Target Finish field does not correctly calculate the duration into the timestamp for work orders generated from a PM containing Job Plans of specific duration. In Work order Tracking, when a work order with an associated fincntrl work order is deleted, the fincntrl record is also deleted from the fincntrl table. In Work order Tracking, the financial period is derived based on the Start date and not the Entered date for the Labor Transaction record. When changing the status of a record in work orders and then moving back to the results screen, the status does not get updated. In Work Order Tracking, user is unable to change work order status to APPR when work orders are part of a hierarchy which are processed using the workflow. In Work Order Tracking, poor performance is observed with Job Plan functions. In Work Order Tracking, poor performance is observed with Job Plan functions. In Work Order Tracking, when selecting Safety Plans using the Select Value lookup, the filter function does not work. In Work Order Tracking, user is allowed to delete a child work order even when Signature Security permissions are set to N for Delete Work Order.

WOTRACK

88695

WOTRACK

94204

WOTRACK

94906

WOTRACK WOTRACK

94993 06-10782

WOTRACK

06-11520

WOTRACK

06-11955

WOTRACK

06-13526

WOTRACK

06-15424

WOTRACK WOTRACK

06-15473 06-15656

WOTRACK

06-15689

WOTRACK

06-15875

WOTRACK

06-16537

WOTRACK

06-17075

WOTRACK

06-17200

WOTRACK WOTRACK WOTRACK

06-17403 06-17417 06-17917

WOTRACK

06-18425

Fixed issues of Maximo 5.2 from patch 03 - 09

61

Maximo 5.2 Patch 08

Application WOTRACK WOTRACK

Issue 06-18578 06-20396

Description Generating a work order fails if there is a reference to a deleted job plan task ID. In Work order Tracking, user is unable to delete a work order after a task has been added and then removed. In Work order tracking, adding planned material on an approved work order does not create an inventory reservation Changing the Work order status to Complete results in an incorrect display of the Actual start date and time. In Work order Tracking, user is able to change the status of task work orders despite not having access to change status. In Work order Tracking, error message "The quantity cannot be less than what has already been issued" when attempting to enter planned materials on an approved work order. Changing status for selected work orders to CLOSED on results screen causes ALL work orders to be closed.

WOTRACK

06-21194

WOTRACK

06-12298

WOTRACK

06-17955

WOTRACK

69375

WOTRACK

07-12751

Maximo 5.2 Patch 06

The following table lists all fixed issues in Maximo 5.2 Patch 06.
KPI DASHBOARD 85917 ASSETS 88089 ASSIGNMENT MGR 93394 EQUIPMENT 041153 CUSTAPP 87549 DESKTOPREQ 87908 88799 93250 93985 91072 91593 92351 94126 "Invalid date/time" error when changing status A user without access to the first GL component will work order error message upon submit when GL comes from Work Order or Storeroom automatically Cannot enter negative quantities on Material Requisition / Desktop Requisition lines The Work Order reference should be carried through to Purchase Requisitions and Purchase Orders Error: "Unexpected Exception" when routing Desktop Requisitions consecutively with manual input node in a Workflow process When adding the REFWO field to the Requisition Lines (reqlines.jsp) the REFWO field is read only Desktop Requisitions are stuck in Workflow if there is an error during the submit stage Desktop requisition lines for Desktop Requisitions in Workflow are deleted when submitting multiple desktop requisitions for the same item. The "Unselect All" button does not work Class Description not copying over to Equipment description when flag set to "Y" Availability time still shows in Assignment Manager/Labor List despite Total Hours=0 for current date Catalog search uses the Class/Subclass combination for the Return and does not filter out ORG or SITE Applying Dashboard causes system to hang when user tries to close the Help window

62

Release Notes

Maximo 5.2 Patch 08 88711 94126 DOCLINK BROWSER 86369 DRILLDOWN 88667 When you have an Equipment with the same name in more than one site that belongs to a Location that exists with the same name in other site Location hierarchy, the information displayed in Drilldown in the same for both sites Cannot move several spare parts of a parent Equipment towards another parent that has never had spare parts Error: "Record has been modified by another user refresh and try again" when adding more than five new rows to a Subassembly EQUIPMENT.CHILDREN flag not being updated to 'N' when Equipment has more than one child and all these children are being moved away from this parent The Purchase Order application does not give the right exchange rate when 'Buy Ahead' box is checked In the Request for Quotation (RFQ) application, Attached Documents only displays attached document folder for first vendor when there are multiple vendor lines Desktop Requisition / Material Requisition does not change status when Purchase Requisition gets canceled Material Requisition Lines Disappear from Desktop Requisitions when using workflow.

EQUIPMNT 88697 84001 93402 EXCHANGE 88235 IAS 89779 INVENTOR 90338 92948 87847 88795 85297 11997 87105 91184 94645 INVISSUE 86488 87567 88757 87868 88675 87767 94042 90225 90460 Incoherent quantity of Reserved Spare Parts in "Issues and Transfers" application The Add/Modify Reservations dialog does not allow the user to see and edit Reservations for Purchase Order items for Internal transfer requests Cannot perform 'Bin to Bin' transfer actions when the Item type is 'LOT' In Issues and Transfers, disabling GL Validation does not work. The GL account field continues to act as required field. When you do transactions in the Issues Application and enter more than 10 lines, you get wrong values in CURBAL column "java.lang.NullPointerException" error when selecting Reserved Items in Issues & Transfers "Unknown error; null" during Issue/Transfer of Items between Storerooms Bin is not available when Transferring in Items When trying to transfer an Item out of a Storeroom that exists in two bins, a default bin with zero balance and a second bin with a balance of 5, the user receives the message "No Balance exists for this Item/Storeroom/Bin combination" Average cost not correctly updated when returning an Item to a new binnum "Out of memory" error when doing a Physical Count Adjustment with many records Rotating Item movement causes incorrect update in Average Cost and Current Balance Maximo is hanging when trying to save any modification from any Attribute in the Rotating Item Specifications No Lot number assigned when you press the New Row button multiple times MAXDEMO Data for Lotted Item 11453 is displaying incorrect information Actions in Inventory causing MBO object to fill up the Memory Heap Items whose primary vendor is another storeroom (internal) should not consider agreements, unless they are with that vendor Poor performance when copying an Item Assembly Structure to a new Item if the IAS has hundreds of Items

Fixed issues of Maximo 5.2 from patch 03 - 09

63

Maximo 5.2 Patch 08 INVOICE 90606 "Unable to Save Record After Changing Status, Record has been updated by another user. Refetch and try again" after changing Unit Cost of line items on Invoice and trying to change status TAX5 on SERVRECTRANS is always being set to TAX4 value Invoice Match record is not being written for Invoices with no PO reference Changes to Unit Cost not being accounted for on Invoice Invoices - FinancialPeriod not being set based on Enter Date In Invoice, an error message "cannot approve invoice because of unexpected error" is displayed when attempting to approve an invoice where an existing invvendor record cannot be found. In Invoice, incorrect variances are generated on invoices for inventory purchases where the order units are a numeric value larger than the issue unit conversion. An error message "Cannot Approve Invoice, To Lot is required for lotted items" is displayed when attempting to approve an invoice with work order items which is in the Secondary Base Currency and the exchange rates (between primary and secondary base currency) at the moment of purchasing, receiving and invoice approval are differentwork order In Invoice, the PO Line costs are not copied over to the Invoice line for a Service PO line with null quantity & unit cost. Primary Work Location description is not picking up the Location that is associated to the correct site In Labor, deletion of a Labor record is not validated on all sites. Define Filter displays no records when the user is ahead of the database server. In table window filter, user must query by one day ahead of Start Date that is wanted Drilldown is not showing the correct hierarchy when Choose Path to Top is selected from the Move Equipment page Changing Parent of a Location causes incorrect updates to LOCANCESTOR table Message 'Required field Location is blank', when trying to duplicate a Location with specifications and AUTOKEY function turned on Cannot restrict the user view of the Location Drilldown When the user views/modifies Parents, Maximo takes the previous entry and uses it as the Parent system In Locations and Locations (Tr) applications, the Parent of Drilldown opens up with the toplevel Location. It should default to the Location whose detail button you are clicking

89522 87951 88785 83273 06-10730 92077 94859

002568 LABOR 88969 06-10791 LABREP 90427 LOCATION 92461 87878 87880 041334 87515 82781 MAXIMO ENTERPRISE ADAPTER 89136 86853 87281 87288 90169 MSPROJECT 86230 PM

Invoice importing creates a Company in the user default site even if Invoice is meant for different site Query is being executed non-stop against database: select emailsent from max_interdata_bat where emailsent = :1 When Maximo Enterprise Adapter is building the XML tags to send data to another system, it performs a SELECT instead of an ORDER BY clause Locking occurs on the Labor table when reporting labor in Labor Reporting and Maximo Enterprise Adapter is enabled on SQL Server The application in Portuguese uses a dot, that is, 5.000. The SAP integration interprets the dot as a comma and multiplies the value Queries for Maximo Project need to respect ISTASK = 'N'

64

Release Notes

Maximo 5.2 Patch 08 89203 88421 06-11343 92004 PO 93741 89405 90515 89226 89099 88058 64194 83535 94386 View Blanket PO does not consider Release POs with PO Type having a REL synonym Error "Choose a Blanket Purchase Order to view the Blanket Details" when trying to view blanket details from a synonym value of POTYPE 'BLANK' Service Blanket PO amount is being charged to the Work Order cost, when it should ONLY charge the Release PO amount Cannot create a Blanket Release with a synonym status of POTYPE blank Error: "Purchase Order Type is Not Valid" when selecting a synonym of POTYPE Using the Item Interface to update a Pricing Agreement Purchase Order fails when Direct Issue is set to 'N' and the Purchase Order is a PRICE agreement Rounding of the unit cost field when calculated from linecost/quantity causes receipts and invoicing not to match PO when linecost=qty*unitcost(rounded) The cost on Purchase Orders is not equally distributed In PO, the entered date field under PO Line items copies the date from the PR line item when performing the action "Copy PR Line items to PO". Instead the date should be the date that the copy action was performed. PR Vendor is being populated with the Vendor on the Agreement Cannot create PR for Location when there is only one Equipment attached to it Cannot have all the data in the table section of PRLINES align to the right A purchase requisition without a vendor referencing an agreement PO with a vendor throws an error message "A vendor is required for a purchase order. Please enter a vendor. Enter a vendor on the purchase order". Cannot insert work order in Quick Reporting after installing fix in KBDoc M04662 against Patch 04 if user restrictions have been implemented against a users ability to change status On Quick Reporting / Labor subtab, hours are not being updated after changing start time and finish time Wrong mboattributes point at vendor.name and changedate Cannot perform Receiving action when the ITEM Lot Type is "LOT" Error message "Record Has Been Updated by Another. Refetch and Try Again" is displayed when attempting to receive a PO with a lotted Item with an Inspect on Receipt and Expiration Date. Receive Error message "Invalid Material Usage Transaction. Either the required components are not filled or the component values are not valid." when receiving materials against a task Work Order Object default value in the PM.WORKTYPE field is not working Target Finish Date is blank on Work Order tasks generated from PMs In the PM application, the Master PM field is checked when tabbing out of the location field while inserting a new PM. PM generated WOs which contain a Route and include Equ1 & Equ2 cause the Equipment to change to a higher hierarchy

PR 85534 88712 90912 06-11946

QUICKREP 92285 69557 RECEIPTS 86894 87822 06-10605

88468

RPT-ACT 06-14342 90976 Unable to compile acweb after loading WebLogic Server 7, SP7. (Installs JRE of 1.4.2) An error message "Invalid column prefix ': No table name specified" is displayed on executing the Item List report from the Item Master module, when selecting items with a where clause "where (upper(description) like '%BLOCK%')". Unable to direct print reports with Adobe Acrobat Reader version 7.0.1 (see Tech Alert M04867).

83961

Fixed issues of Maximo 5.2 from patch 03 - 09

65

Maximo 5.2 Patch 08 86847 90050 SIG 033311 SYSTEM 67853 75105 87395 87669 87582 88783 88694 87877 The mxserver log file should include user name and spid so that sql statements and blocks can be traced to specific users Maximo leaves hundreds of open cursors in PM generation and Assignment Manager If you use CTRL - or CTRL + to change a date field, the value goes back to the original date when you click OK When adding long description to a POLine, data does not populate the POLINE or LONGDESC tables WebLogic Server starts and fails while trying to connect if database has not opened Work Order Tracking Change Status action changes hundreds to many thousands of other Work Order statuses Various hot key combinations are not working When you open the calendar in any application it first shows the correct month. If you close it and bring it up again, it then shows the next month. If you select another calendar on another field, it opens the wrong month again. When a value list is created and associated to the WOPRIORITY field in the Work Order Tracking application, no validation is occurring on manually entered values Complex queries on SQLServer hang. An error "Record has been updated by another user" when one user is editing and another user attempts to save the record. In Maximo, using tab key to navigate causes the prior command to be replicated. In Maximo, the filter closes when a user clicks the tab key to move to another field Improve Maximo to prevent multiple concurrent activities in the same user session from within the same browser. Maximo on SQL Server hangs when complex queries are executed Safety Plan tab - Lock Out /Tag Out tab - When there are three tables, the data in the third window does not keep it's data when moving to other records Maximo on Oracle with Maximo Enterprise Adapter receives error "Calling the class V510MEA_10.class Null" during database autoupdate on Oracle 9.2.0.5 or higher Maximo creates Long description object though there is no LDKEYS in the application MBO (PO Mbo) Actions in PMs causing MBO object to fill up the Memory Heap In Workflow, when labor is restricted from accessing other labor information, user cannot route record in workflow. WO Priority blanks out when Reset button is clicked in the Work Requests application A user in a group with no Update rights, cannot create, edit, or use a Saved Query Ambiguous column error when running Suggested Reorder Report with multiple tables in the main design In Actuate Reports, when attempting to e-mail a report on the request page, an incorrect e-mail address is selected from the labor table.

87965 94984 94750 06-11041 06-12152 0610104 87950 90968 89388 SYSTEM-OBJ 89253 87182 WORKFLOW 62023 WOREQ 90752 WOTRACK 90835 89948

Actual Cost is positive instead of negative if RETURN type is selected before item in Actuals After duplicating a Work Order, in the Work Order Tracking application, Plans tab, Materials subtab, the Required Date stays the same, even if the Required Date cannot be earlier than today's date in this field Adding PARENT field to Work Order Tracking qbe.jsp page, with lookup="workorderistask" as it is in main.jsp results in errors

90356

66

Release Notes

Maximo 5.2 Patch 08 92039 93411 87584 81045 85936 66446 10404 13101 89043 88850 Cannot edit and update a failure of a Work Order that is already closed (status=CLOSE, or any synonym of CLOSE) When deleting a Material Return before SAVE, Maximo still shows negative value Work Order Tracking/Plans tab/Item Reservation uses old Qty Reserved value rather than new one Inserting a default value in the OBJECT DEFAULT VALUE does not work properly for the field LABTRANS.LABORCODE After adding Tag Out Hazard and Tag Out Record, the corresponding Lock Out operations cannot be copied to Work Order without a Safety Plan Using Maximo in IE causes the IEXPLORE.EXE memory usage to continue to grow, causing low memory client workstations to slow or freeze during the session Safety Plan Hazards do not automatically populate Precautions. Similar problem with Lock Out/ Tag Out procedures. Cannot save after duplicating a Work Order that has data on the Tag Out tab. Receive error, "Required Field HAZARD ID is blank." MAXVARS flag called WOSTATUSCLEARRESV does not seem to work when Work Order status changes from INPRG to COMP "Unable to change status, actuals may not be in the future" error message when the user time zone is ahead of the database time zone and status change is attempted on a Work Order where the Actuals Finish Date and Time are ahead of the database server time The description does not populate on the selected Problem Code in the Work Order Tracking main screen LABTRANS.TRANSTYPE field not editable in the Work Order application In Work order Tracking, the Charge to Store flag is always checked when rotating equipment is used. In the Work Order Tracking application, the "Show only job plans associated with current Work Assets" check box does not use the location or equipment specified on the search page In Work order tracking, user is unable to save a work order on the plans tab. An error message, "unknown error has occurred" is displayed. User needs to click the toolbar and field buttons twice when using Java JRE 1.4.2 or JRE 1.5.

88937 88464 70235 06-11029 06-10845 70452

Maximo 5.2 Patch 05

The following table lists all fixed issues in Maximo 5.2 Patch 05. Issue
85630 86520 86485 84452 81045 83666 83681 83511 83835

Application
ASSIGNMENT MGR ASSIGNMENT MGR CRONTASK DASHBOARD DATABASE CONFIGURATION DATABASE CONFIGURATION DATABASE CONFIGURATION DESKTOPREQ DESKTOPREQ

Description
Go To Work order Tracking' icon does not display the Work order screen. Assignment Manager causes all the Open Cursors to be used that causes the application to hang. Excessive number of Commits to the database. Saved queries are not executing after selecting the dashboard results list. Setting a default value in the Object Default Value column does not default the value for labtrans.laborcode. E-Signature fails when a Job Plan is deleted in the PM Job Plan sequence. Control Center for SQL Server allows DESCRIPTION ALN field length to be set greater than 254. Draft Requisition Template sets the Requisition line currency code to base currency, without changing the cost Price shown in Desktop Requisition line is not taking into account the Purchase Contract.

Fixed issues of Maximo 5.2 from patch 03 - 09

67

Maximo 5.2 Patch 08

Issue
84116 84307 84706 81901 83792 90261 61899 62265 73777 85854 60692 76341 80314 85141 85352 111045 84278 83272

Application
DESKTOPREQ DESKTOPREQ DESKTOPREQ DOCLINK BROWSER DOCLINK BROWSER DOCLINK BROWSER DRILLDOWN DRILLDOWN DRILLDOWN DRILLDOWN EQUIPMENT EQUIPMENT EQUIPMENT EQUIPMENT EQUIPMENT EQUIPMENT ESIG IAS

Description
Desktop Requisitions / Requisition Lines tab when entering a stocked item then removing the storeroom not all the default vendor information is displayed. Unable to change status error when routing a Material Receipt from the WF inbox Required field is blank error when adding to favorites within Desktop Requisitions when a Field Security record is enabled. Documents print in random order when selecting print with attachments if documents are in multiple folders. DMSManager is not being passing over the doc version information. Attached documents are not displayed properly when spaces exist in the document folder or file name of an attached document. Drilldown screen can take a long time to load. Drilldown is taking a long time to display. Portion of the drilldown shows a blank line instead of the Children data using WebSphere Application Server on UNIX, AIX, and Windows. Locations are looping when viewing them in the drilldown. The E-Signature popup action on a duplicate equipment record does not prompt for E-Signature. Equipment application hangs after selecting go to Locations then returning to the Equipment application. Moving an Equipment from a Parent location that was at a non-storeroom location to a storeroom location does not null out the parent field. Error moving equipment when using a labor location. Children flag remains set to 'Y' on parent equipment when child equipment is deleted. Entered equipment that does not exist on the Spare Parts Tab, Subassemblies table gets added to database. Setting an E-signature on set PM counter prompt for E-Signature. When an Item Assembly Structure (IAS) is created and you list a rotating item as one of the children, if the qty is entered first and then the item - any qty can be entered. Intermittent error ORA-00001 when trying to build an Item Assembly Structure. Jsp update for patch installs are not updating .js files. Current Balance Adjustment transactions sent by an external financials system are not creating Invtrans records or not correctly entering the data. Issue Current Item does not update the EnteredAsTask Flag in the MatUseTrans table. Debits and Credits the incorrect account for Standard Receipt cost adjustment. Rotating Equipment is transferred even if the item code was modified. User can successfully return items issued to a closed Work order. Cannot edit the work order field on the distributed costs dialog. Service Receipts are not being created when the invoice is being approved if the IVMATCH is set to 'Y' in the MXCOLLAB table. Invoice cannot be approved when a PO line has multiple receipts. Invoice match records not being generated for variances. Error Message "Unable to Save Record After Changing Status, Record has been updated by another user. Refetch and try again" when approving invoice for service PO. Actual service cost is updated on the last work order only when a service invoice with multiple lines from different work orders is being approved. Invoicing is opening excessive objects causing the application to become unresponsive. User can delete a job plan while this job plan is linked to a route.

86416 78309 87149 83725 85578 82450 84784 81735 82666 83555 84442 84980

IAS INSTALL INVENTOR INVENTORY INVENTORY INVISSUE INVISSUE INVOICE INVOICE INVOICE INVOICE INVOICE

85151 85882 1249

INVOICE INVOICE JOBPLAN

68

Release Notes

Maximo 5.2 Patch 08

Issue
60742 82293 82375 82683 83498 84063

Application
LOCATION LOCATION LOCATION LOCATION LOCATION LOCATION

Description
Adding Needham to more than six systems causes a truncation to the Systems box next to the drilldown. Cannot select a location from the drilldown hierarchy if there is a \ (backslash) in the location name. Locations table changedate and changeby are not updated to show when & by whom a location is changed. The "Belongs To:" Select Value should only open Locations belonging to that System. Asset catalog search performance. When selecting View Work Orders and PMs from the select action menu it creates an unexpected exception when clicking the Long Description icon in the Location description field. Drilldown not searching properly on the Location search screen. Physical Count Adjustment and Balance Adjustment transactions do not update the INVTRANS table. Non English locale settings causes errors in Maximo Enterprise Adapter transactions. MAX_FC_INTERFACE table index is not created when CreateTable.bat is run. String.java.lang.String:iface#1,000 Error when receiving a PO that has more than 999 PRlines. Inventory Balance Inbound error: The new value for the current balance is equal to the old value. No changes were made. "java.sql.SQLException: ORA-01000: maximum open cursors exceeded" error when changing the PM Options in Multi-Site setup. Unable to see all sites unless the filter is used on the Sites Tab. Job Plan field is nulled out if existing value is deleted and replaced. Active season PMs generate work orders that are outside the active season. Error: "Not a valid number" when entering meter readings. GL account not defaulting correctly from PM. Cannot see agreements when there are no line items on the agreement. Should not be able to specify anything but a storeroom on an internal PO or PR. Internal check box stays checked after changing company to external vendor. PO blanket: Copy PR Lines to PO Error: "Total cost of line items is greater than total cost of purchase order". If a PO is unapproved, another item is added & the PO is reapproved, receipt status stays complete. When creating a PO, the exchange rate used is always the one for the current date, but it should be calculated based on the "ordered date" on the PO. The cost on Purchase Order is not equally distributed. Default table data values should blank when changing records. Item availability is not correct after status has been changed. Cannot add a reference to a contract that has lines specified on a PO line that is for a service or material. When creating a PR then selecting 'Create PO' from the 'PR', the field 'Quantity Received' on the generated PO is 0.00. When a PO line is deleted the Receipt status does not go to Complete. GLCREDITACCOUNT is blank when creating a direct issue PR without a vendor. When copying over 400 PR Lines from Price Agreements to a PO performance is slow. Duplicate CLOSE status in PR application from View Status / Workflow History. Modified by field does not update after modifying the equipment field on the PR Line. Null or zero quantity is allowed on PRLINE or POLINE.

85970 80565 83392 84344 84940 85372 81342 70421 35269 74377 82449 84399 67339 79333 82569 83367 83381 83505 83535 83929 84226 84533 84570 85199 82454 82574 83363 84392 86147

LOCATION MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MAXIMO ENTERPRISE ADAPTER MULTI-SITE SETUP ORGANIZATION PM PM PM PM PO PO PO PO PO PO PO PO PO PO PO PO PR PR PR PR PR

Fixed issues of Maximo 5.2 from patch 03 - 09

69

Maximo 5.2 Patch 08

Issue
82122 85895 82063 82260 84549 84680 85069

Application
QUICK REPORTING QUICKREP RECEIPTS RECEIPTS RECEIPTS RECEIPTS RECEIPTS

Description
Incorrect error message "Regular hours plus overtime duration exceeds duration between start and finish time". Not able to change the status of Work order in Quick Reporting when the status is WSCH. Highlighted equipment line becomes blank when navigating through tabs in the action menu, Receive Rotating Items. When distributing cost to two accounts on a POLine the accounts are swapped over in matrectrans on receipt. When receiving rotating items from of a PO, the user to assign equipment numbers to more pieces of equipment than were received. Unable to use a storeroom as an internal vendor for direct issue to a work order when receiving items in the work order. When receiving more than the amount ordered on a PO for a particular item in multiple shipments after saving the previous receipts, amounts are only allowed to be negative. In Maximo Enterprise Adapter, when issuing items, it is taking the cost from the external system. For returns, it is taking the cost from the item in Maximo. Cannot receive a PO line with a negative quantity on it. Error: Receipt failed to be created for selected row 1. Cannot return more than what has been received. PO Line 1 appears multiple times and overwrites other PO Lines when doing Receipts if same item is on multiple POLines that reference different work orders. The Received cost is not updated when receiving PO lines that contain only a description, cost, quantity, and GL Account when the Storeroom field is null. When deleting an item in RFQ one needs to delete the whole line to type in the RFQ line. Bill To address is not populated on PO created from RFQ. Printing with attachments might fail if multiple tables at the top level of the report contain the key column name. Application hangs when attempting to search for Safety Plan by clicking in result button. Application hangs when attempting to select a related equipment record on the Tag Out tab. When a default start date is populated, then selects the filter search for a particular start date and clicks new row for daily time, the start date uses the system date not the default date. MAXTABLES definition differs from MAXTABLESCFG for A_LONGDESCRIPTION table. Debug printout in std class FldExchangeRate is filling up log file. Debug print mboCount. Pressing the tab key results in duplication of prior action rather than advancing to the next field. Application hangs on some complex queries. (SQL Server) Actions in application are causing objects to fill up the Memory Heap. ITEMSTRUCT objects filling up the heap. Im Maximo 5.2, user browser sessions are periodically and unexpectedly dropped, resulting in a return to the main Maximo Login page. Maximo 5.2 users can be redirected to the login screen while they are working in Maximo even if a session timeout has not been configured in Maximo. Tag / Lock outs application is hanging when attempting to search for a record. The GL Account field becomes null when a valid GL is entered and then an equipment or location is selected that has no GL associated. When the process number reaches 1000 or higher, application inserts a string causing Workflow to fail.

85627 86064 86095

RECEIPTS RECEIPTS RECEIPTS

86543 82622 83497 74391 83830 84988 83119

RECEIPTS RFQ RFQ RPT-ACT SAFETY PLANS SAFETY PLANS SYSTEM

83484 83534 85429 85706 86579 85007 86217 90704

SYSTEM SYSTEM SYSTEM SYSTEM SYSTEM SYSTEM-OBJ SYSTEM-OBJ SYSTEM

85173 86332 64899

TAG/LOCK OUTS WOREQ WORKFLOW

70

Release Notes

Maximo 5.2 Patch 08

Issue
73204 83312 86407 86519 61655 81686 82164 82680 83163 83340 83565 84066

Application
WORKFLOW WORKFLOW WORKFLOW WORKFLOW WOTRACK WOTRACK WOTRACK WOTRACK WOTRACK WOTRACK WOTRACK WOTRACK

Description
Escalation, Notify, and Reassign actions produce errors when escalating to a Role. WFID SQL Error 2601: Attempt to Insert Duplicate Key in Object with Unique Index. Cannot change status within Workflow. The status change is under the control of workflow and cannot be changed by the applications logic. Cannot modify the unit cost on the Work order Actuals. PM Last Completion Date differs if a Work order is in Workflow and when a Work order is not in Workflow if the PM use target Start = 'N'. Time Zone Errors with start time value on the Work order Labor Reporting tab. When searching with wildcards 'underscore _' or 'question mark ?', the application adds a percent sign '%' before and after the search string. No focus on the Labor field when entering a new row for planned labor or actual labor when using JRE version 1.4.1_01. Double reservation line created in Inventory for a single WPMaterial reservation. Users are allowed to choose values from the LTTYPE value list when not all values are not allowed to choose from. The reserved items from an approved work order are not clearing when the work order is unapproved and the reserved items are modified, causing a negative quantity. Unable to offset Tool transactions on a Work order. Application hangs after inserting a Safety Plan, saving the record, then selecting the Safety Plan tab again. After applying patch 04 all the synonymous status disappear. When creating a follow-up work order from a work order task, the generated followup work order becomes a task work order without a parent. Cannot set the default of Change Child Status check box to not be checked for child work orders. Error: 'FauxMboSet method count not implemented' in the Work order Actuals tab when selecting planned labor.

84897 84954 85600 86151 86226 87732

WOTRACK WOTRACK WOTRACK WOTRACK WOTRACK WOTRACK

Maximo 5.2 Patch 04

The following table lists all fixed issues in Maximo 5.2 Patch 04. Actuate Reports

Issue 66179 70989 74814 82086 78545

Description In Actuate Reports, occasionally the user is displayed an error message Your session has timed out, the Actuate and Maximo sessions are lost. malformedcookiesheader exception when running reports. Print with Attachments option does not print details report when using Adobe version 6.01 Certain custom columns can cause invalid Where clauses to be passed to Actuate with languages other than English. When scheduling a report against Selected Records, where a query returns zero records the WHERE clause is not passed to the Actuate request page. Instead 1=1 is passed and the report gets scheduled.

Fixed issues of Maximo 5.2 from patch 03 - 09

71

Maximo 5.2 Patch 08

All Applications

Issue 82021

Description ToolTip for check box title attribute does not work for the psdi:check box tag.

Attached Documents

Issue 77645 13589 75443 80889 81332

Description In Attached documents, unable to attach a new document in a cloned work request application. Attached document not shown when the file name is in Japanese or French (in Work Request, Buyer and Manage Document Library) WebSphere Application Server only. When attaching a document if you use quotation marks in the document description field, the system hangs or clears out your entry. Cannot create DOCTYPE folders with spaces in the name. Folder does not function and you cannot delete it. The 'Print with Attachments' action menu item is not working with Maximo 5.2 P2a running WebSphere Application Server 5.1.1.

Assignment Manager

Issue 81608 78839 67636

Description If an Assignment has a StartDate on the same date as the WorkPeriod (or ModLabAvail) WorkDate but has a time earlier than the StartTime, it is being ignored by the Remaining Availability calculation. When application server is in different time zone than user, the available hours in the labor list are not adjusted for the user time zone. Priority calculation and Response Time options are only available to the first Site.

Auto Update

Issue 81964

Description ORA-01408: such column list already indexed - program passes storagepartition, not schema name, to util.nativeIndexExistsForColumns()

Chart of Accounts

Issue 82435
Company

Description Maximo checks for a valid Currency Code at a specific Date and Time combination which causes problems when the exchange rates are updated daily.

Issue 82429
Craft

Description You should get a warning when marking a company that is the primary vendor for an item to disqualified in the Companies application.

Issue 78701

Description In Crafts, a craft code might be deleted even when referenced by Labor code.

Desktop Requisitions

Issue

Description

72

Release Notes

Maximo 5.2 Patch 08

65799 69833 80169

81166

82047 61434
Drill Down

When completing Receipts on a Partial PO that was generated from an MR, the MR stays in an OPEN status and does not CLOSE. In Desktop Requisitions, the GL Debit account specified on a material requisition line is not copied to the Purchase Requisition Line. When a Desktop Requisition line having a description but no item number is added to Desktop Requisition Favorite Items the description is not populated. In Multi-site Inventory Options, check the Disallow Negative Balance, the Disallow Negative Available Balance, and check the Create Approved PO from Agreement PO on PR Approval" options. On submitting a material requisition, an error message "Record has been updated by another user" is displayed. When creating an MR from a template (recurring MR) that has an item related to a vendor agreement, the field agreementponum is not populated. Adding Requisition lines, using lookup values are returned with error on page and tablewindow row details closes.

Issue 64634 81208

E-Signature

Description When the drilldown is called from the results page in the Locations application, message "Must Select an Operating Type Location" is displayed when a labor location occurs alphabetically before any operating locations. Child locations do not display in the locations Drilldown, when the location is the top location (with children) in a system, and a grandchild in another system.

Issue 70257
Equipment

Description E-sig does not log properly when altering more than one record on the results page.

Issue 64758 65062 69720 70446 79208 81570 77025 63587

Description In Equipment, if the user does not tab out of the EQNUM field upon insert, the record does not get saved after pressing the save button on the first try. In Equipment, on moving an equipment record that has an attached specification template, only the equipment record is moved to the new site the attached specification template is lost. In Equipment, the CHANGEBY AND CHANGEDATE database values do not update when the Equipmentspec record is updated. In the Equipment application, template attributes are not displayed for equipment records on assigning a specification template to a rotating item in the Item Master. In the Equipment application, several user-defined fields associated with lookups have the fields set to readonly="true" allow data to be brought in using the lookup. For the first Meter Reading entry, the Average Units/Day becomes zero. Placing Field Security on the Equipment table and one or all the DESCRIPTION, CHANGEBY, and CHANGEDATE columns, causes Specifications, Numeric, or ALN Value to freeze Spare Parts are deleted from Equipment Record upon save even though user prompted that the Equipment cannot be deleted because it has children.

Fixed issues of Maximo 5.2 from patch 03 - 09

73

Maximo 5.2 Patch 08

82572

When moving a parent equipment with one child, from one location to a new location, user receives error message: Record has been updated by another user. Refetch and try again.

74

Release Notes

Maximo 5.2 Patch 08

Inventory

Issue 35536 63984 66000 66808 73215 79090 80654 80062 80407

Description In Inventory, the credit GL Account field in the Issue Current Item screen does not reflect updated information when the Inventory Control Account field is updated in the storeroom application. In Inventory, when the server and client have different regional settings, an error message "The date format is not valid" is displayed on trying to add a new lot for a new bin. In Inventory, the Used on Equipment section in the Where Used Tab does not display the quantity used. In Inventory, a default bin transaction to another bin with the same name but in different lowercase or uppercase letters causes an incorrect current balance to be displayed. An error message "The available balance will become negative as a result of this transaction" is displayed on recording actuals against an approved work order. In the Inventory application Issues & Transfers tab, an incorrect sql statement causes slow performance when the Select Reserved Items button is clicked and the results are filtered by work order number. In Inventory, several matusetrans methods have been made public. Inventory last receipt cost is not updated from the invoice. CURBAL field in MATRECTRANS has a value of 0 when it should have a different value in it.

Issues and Transfers

Issue 041047 62615

64699 65124 65910 65912 66068

77548

77689 80474

Description In Issues and Transfers, a MATRECTRANS record is erroneously generated when returning a rotating piece of equipment. In Issues and Transfers, problems with work order GL account validation results in error message "Invalid GL account. Either the components are not filled or the components values are not valid." When adding or modifying a reservation in the Issue and Transfer Application entering a remark in the memo field and then going to Reserved items, the entered remark is displayed in the item description field. In Issues and Transfers, in the Select Items for Transfers screen, the "Select All" check box that allows for selection of all items displayed is unavailable. In Issues and Transfers, the Transfer Out tab Select PO Items screen displays internal Purchase Orders that are in a Canceled, Closed, or Waiting Approval status. In Purchase Orders, once a PO is processed through the Transfer Out tab, the PO should not show up for processing in the Transfer In Select PO Items list. In Issues and Transfers, when multi-site Inventory Options specify that negative balances are disallowed, negative balances can still be created if multiple ISSUE lines for the same item are entered without a save action after each new row. In Issues and Transfers, When rotating equipment is issued against a work order and returned to a storeroom via the Issues and Transfers module using the Select Items for Return button, the ROLLUP flag on the MATUSETRANS table for the RETURN transaction is not being reset to "N". In Issues and Transfers, the Select Items for Transfer button lists items available at the storeroom rather than items available for transfer. In Issues and Transfers, an unexpected exception error is displayed on creating an issue of type RETURN and then clicking the Mark Row for Delete button.
75

Fixed issues of Maximo 5.2 from patch 03 - 09

Maximo 5.2 Patch 08

81092 80790 68820 77495 61634 82457

Invoice

In Issues and Transfers, the default table data window does not function correctly when added to the Transfer Out tab. The MATUSETRANS object functionality needs to be returned to supporting negative linecosts for reversed (return) transactions. The Issue Type is READ-ONLY after returning from the "Select Items for Return" screen. YTD is not adjusted when you do a return through the Maximo Enterprise Adapter. Using Maximo Enterprise Adapter- loading issues and validating on refwo - gets message The charge details for a material issue/return has not been specified. No MATUSETRANS.FINANCIALPERIOD is being recorded when issuing an item to a work order.

Issue 65829

66066

70659 76195 77424 78518

78856

80203 82389 62665 80473 81707 82073 81106 81100

Description In Invoices, an error message "Could not change invoice to APPR. There is a cost or tax amount difference between the header and the lines which needs to be manually allocated." is displayed on trying to approve a credit type invoice. When the currency on a purchase order is different from the organizations base currency and the quantity invoiced is less than the quantity received, the currency used for INVOICEMATCH.LINECOST is the purchase order currency rather than the base currency. In Invoices, invoices without PO numbers cannot be approved when using service percent tolerances. In Invoices, unable to change the currency code after the invoice has been saved. In Invoices, when there is an invoice variance for a direct issue transaction, invoice issue type transactions are generated in the MATUSETRANS table. The GLDEBITACCT and the GLCREDITACCT are swapped with respect to the Issue transaction. In Invoices, on changing the status of an invoice that references multiple POs to a synonym of Waiting Approval, if the Close PO check box is checked, the referenced POs are closed. On CREDIT type invoices, if the Pretax Total and Total Tax are entered on the header, the Invoice Total is calculated incorrectly. If the Invoice Total is then manually corrected and an invoice line is entered with Line Cost and Tax Amount matching the header amounts, an attempt to approve the invoice results in the display of an error message indicating a cost or tax discrepancy exists between the invoice header and its line. In Invoices, when a credit invoice is created using the pay on receipt option, the invoicecost.quantity is not updated. When creating an invoice, then leaving the application without saving, the invoice record is saved regardless. Invoice Tolerances with an Upper Limit and a NULL Lower Limit stops an Invoice both over and under that amount. Discrepancy between enterdate in invoiceline and servrectrans. Invoice tolerance not functioning due to rounding on the unit cost for the service line. The Total Base Cost is still populated after clearing out the Pretax Total, Total Tax, and Invoice Total fields. In Invoice, the pretax total and total tax fields are different from the Purchase order, when the purchase order is in a foreign currency and the pay on receipt flag is checked. In Invoice, on deleting an invoice record that is in workflow, the inbox of the user contains a record of the deleted invoice record.

76

Release Notes

Maximo 5.2 Patch 08

Item Master

Issue 66799 69643

Labor

Description In Items, a default value cannot be set even when the cycle count frequency field has been updated on the additem.jsp page with a default value. In Items, an error message "Field Item is read-only" is displayed on using Asset Catalog search.

Issue 78302

Description In the Labor application, any field in the labor\main.jsp page that is associated to a lookup, can return a value after the field is set to readonly = "true".

Labor Reporting

Issue 80617
Location

Description In the Labor Reporting application, labor reported with the "Entered On" date as the first day of a Financial Period as is stored with the previous financial period name in the LABTRANS table.

Issue 62519 62836 63638 64092 65199 68426 73486 76898 79812 04137 4

Description In the Locations application, Equipment Tab, the Equipment field Detail Look up menu should not display the "Move To" and "Select Value" options. In Locations, a user with read only rights to locations cannot view locations in the drilldown. In Locations, unable to change status of an operating location when the status is a synonym. In Locations, the drilldown does not show the correct System and 'PLUS' sign icon if the Location is a child in one System and a Top Level in another system. In Locations, the equipment or locations application loads slowly due to a performance issue. In Locations, cannot delete a location at one site when Maximo records a purchase Order at another site with the same location name. In Locations, when a multiple level item assembly structure is applied to a multiple level location hierarchy and the Open Drilldown action is selected, not all levels are displayed in the drilldown. In Locations, while attempting to select a location from the drilldown menu to a customized field in the Locations application an error message "Attribute does not exist" is displayed. In Locations, in the View/Modify Parent window, after you select a new parent, you are not returned to the Locations application. Drilldown does not sort properly when opening a sub location.

Maximo Enterprise Adapter

Issue 78731 79117

Description In Maximo Enterprise Adapter, when receiving materials for a Pay on Receipt PO a Null Pointer Exception error message is displayed. Invoice header pretax total and sum of line cost validation fails when an interface system sends a CREDIT type invoice to Maximo.
77

Fixed issues of Maximo 5.2 from patch 03 - 09

Maximo 5.2 Patch 08

81037 81610 79968 81269 82420 82217

In Maximo Enterprise Adapter, null pointer exception is displayed when sending a PO update. The table MATUSETRANS could not be set for Syclo Maximo Enterprise Adapter transaction. Work Order Actual Cost for PARTIAL SERVICES RECEIPT is not calculated correctly. MATUSETRANS RETURN record updated by MEASyclo, but record errors out with Null Pointer Exception. Do not throw exception again in case of an error in Continuous Queue. No record sent to mout_gl_interface when tax is added on invoice when matrectrans.linecost = 0, should check loadedcost instead.

Materials Requisition

Issue 03540 3

Description When a new desktop requisition line is created with Search Requisitions/Add to Requisition, and the original requisition line contains a description with no item number, the description from the original desktop requisition line is not carried over to the new requisition line.

Multi-Languages

Issue 71574

Description The Agreement number does not display when the Vendor Analysis is on an item in Swedish version.

Preventive Maintenance

Issue 68167 80646 80667 034377

Description In Preventive Maintenance, the Master PM is not carrying over the entire Job Plan Sequence to the associated PMs. Only one Job Plan is carried over. In Preventive Maintenance, PM to work order cross over fields do not cross over to the child task work orders. In Preventive Maintenance, when the client time zone is different than the server time zone the Next Due Date field displays an incorrect date. Last Completion Date field needs to always remain populated.

Purchase Orders

Issue 65301 71371 72918

73696 75451

Description The purchase order auto number jumps by one when creating Purchase orders using the RFQ, Vendors tab, Create PO button. In Purchase Orders, the total cost is displayed as zero when the pretax total field is hidden on the PO main.jsp page. In Purchase Orders, PO Lines tab, when selecting items using the VENDOR ITEM button on selection of an item, the MODEL, MANUFACTURER, and CATALOG # information is not displayed on the PO Line. In Purchase Orders, on approving an internal purchase order that is a Price Agreement or Blanket Purchase order, items on the PO are placed on reserve in the vendor storeroom when they should not. In Purchase orders, the committed cost on the Blanket Purchase Order is not updated on performing a return item action on a release PO.

78

Release Notes

Maximo 5.2 Patch 08

75916 76342 76450 76972 80296 81156 033265 035491 63761 66426 74541 81729 81730 80475 81206 81352 81420 81438 82383 82477 82557 82582

84808

In Purchase orders, on entering an approved PR with line items that have the cost distributed to multiple GL accounts then converting it to an RFQ and PO the distribution of cost does not follow that line item. In Purchase Orders, a manually chosen PO Line quantity reverts to the quantity on the Price Agreement PO when the record is saved. In Purchase orders, the PO line number can be changed after unapproving the PO even if there are existing receipts against that PO Line. In Purchase orders, the stock category field type is no longer displayed on save of receiving items. In Purchase orders, while creating a PO for an item for which multiple price agreements with multiple vendors exist; the entered quantity is changed from the entered amount to the amount on the price agreement. In Purchase Orders, the tax Amount for tax code 5, which is based on the tax codes 1 and 3 fields, is not being recalculated after the values are changed. Cannot enter negative quantities on PO lines. After receiving material lines the extra field IT1 is Read Only. Distributed cost is off by a penny when tax option 'For All Items' Loaded Cost is used. When creating a Change Order, Maximo allows the user to modify the PO number but the PR Lines still reflect the autogenerated Change Order #, not the number that the user has modified. Committed costs are not updated when processing a return on a release PO. POLine numbers are incorrectly maintained on a duplicated PO (as Lines 1,3) when the original PO had three lines and line 2 was deleted. Error "A Storeroom Location is required for #" when tabbing out of the Item Number field after entering an Item Number on a POLine. Inspection required items which are returned do not show a record in matusetrans Change order POs are not pulling across the MR/Requisition number and requested by from the original PO. PO is not closed after approving the invoice though when the "Close PO" flag is checked. Matrectrans.loadedcost is not updated correctly when a return is done after receiving prorated PO lines with Invoice Management turned off. Entered by field on POlines defaults to the PR entered by when copying PRlines to POlines as a user that is different from the PR requestor. Error: "Could not change PO 'xy' to status APPR, a distributed cost for line 1 has an empty GL Acct." when Database configuration option 'validate Component Combinations' is selected. Vendor date is not editable on POLINE after approval. Error message "The quantity cannot be less than the quantity that has already been received" when updating the quantity in a po line of an unapproved purchase order that already had a partial receipt against it. Default table data does not work when a GL account is defined at the Inventory level for the item and not the storeroom level. An error message "The cost on purchase order line #1 is not equally distributed" is displayed on creating a PO from an RFQ, when the RFQ is created from a PR with distributed costs and the unit cost on the RFQ Quotation Lines is different from the unit cost on the PR Lines.

Fixed issues of Maximo 5.2 from patch 03 - 09

79

Maximo 5.2 Patch 08

Purchase Requisitions

Issue 60573 64572 74197 74566 75494 77375 78170 81448

Receipts

Description In Purchase Requisitions, the prline.POLINENUM on the PR is referencing the wrong POLINENUM on a change PO. In Purchase Requisitions, the required date is not automatically populated in the PR Lines when the date is entered on the main PR tab. In Purchase Requisitions, an incorrect total cost is displayed on changing the quantity or unit cost on a PR Line and the row is deleted before saving the record. In Purchase Requisitions, when auto-numbering is disabled and a canceled PR is duplicated the PR Line is copied twice on the duplicated PR. In Purchase Requisitions, the catalog code is not displayed on the PR Lines tab. When creating a PR line item, a vendor item cost per unit is not carrying over when selected using the Vendor Items button. In Purchase Requisitions, on changing the status of a PR to a synonym status of WAPPR, the PR is closed. In Purchase Requisitions, the View Status/Workflow History screen shows the history of purchase requisitions in other organizations and sites when the pr number referenced is the same.

Issue 66067 72235

76556

79152 79706 80639 82813 82446 82228 67066 81994 73401 73694

Description Cost calculations on RETURN transactions in the Receiving application are based on the current exchange rate rather than the exchange rate in effect when the RECEIPT transaction took place. In Receipts, receipt of a direct issue lotted item does not populate matusetrans with the lot and bin number. In Maximo Enterprise Adapter, when an outside system sends a partial receipt of a purchase order service line that contains a work order reference, and automatic approval of receipts is set to Y, log file error messages display "Record has been updated by another user. Refetch and try again." The work order Actual Service Costs are updated incorrectly. In Receipts, on manually receipting an item and then changing the item entered, an error message "This item is not on this purchase order" is displayed. In Receipts, an error message "Record has been updated by another user, refetch" is displayed when two direct issue material items which belong to a parent work order and its child task are received In Receipts, the CURRENCYLINECOST is null on receiving a PO with Distributed Costs when Maximo Enterprise Adapter is installed. After receiving the quantity ordered, receipt status changes to partial. Line item is editable if you are in the receiving application. Cannot change GL account after returning one of several items on a po and unapproving PO. Should display Message: 'Please use the issues and transfers application to receipt rotating items on internal purchase orders' when selecting an internal PO. When the matrectransid reaches a certain number it becomes negative which causes an application error when matching ordered and receipt info in the Receiving application. Receipt status is incorrect after changing accepted quantity. The return receipt transaction does not increase the current balances of the vendor storeroom.
Release Notes

80

Maximo 5.2 Patch 08

62426

Material transfers on internal POs result in duplicate POLines in the receiving application.

Request for Quotation

Issue 64056

69138 75822 65574 82261 82965

Description An incorrect GL Debit account is displayed when a PR is created against a work order and the GL Debit account is changed on the PR and an RFQ and PO are created based on the PR. Purchase Order lines display the GL Debit Account from the work order instead of the Purchase Requisition. In RFQs, the Description, Priority, Required Date and Supervisor field details are not carried over from the PR to the RFQ. In RFQs, the catalog number field on the Quotation tab does not populate with the selected vendors catalog code. If you hide the ship to, bill to section in PR, RFQ, or PO then other read only fields become editable. The vendors are not listed on the Items subtab of the Quotations tab when the RFQ is for a service or material without an item number. When inserting a new RFQ with an autonumber in the RFQ app. Application stays on the search tab and the RFQNum field remains blank.

Signature Security

Issue 79118
System

Description When an e-Audit is set against long description field additional records are created in the A_LONGDESCRIPTION table on modification of the long description.

Issue 033018 74505 76464 76478 78828 79339 81262 81543 82061 78268 61316 031909

Description In Maximo, building the maximo.ear files might fail with a connection error if there is a firewall or proxy server. In Systems, when logging in to Maximo with a browser that does not contain a JVM an error message is received that points to a link that is no longer valid. On upgrading Maximo from version 4.1.1 to version 5.2, there are missing specification attributes in the database after the upgrade. In Maximo, slow performance is observed in multiple applications because the applications perform a select * statement from the main table. In Work Order Tracking, an error message is displayed on trying to add a value to a field in the customized Default Table Data section in the Planned Materials sub tab. In Systems, if a user selects a query from a long list of queries in the Current Query dropdown list, on returning to select the next query, the user is brought to the first query in the list. In Maximo, the Maxsequence table does not check for duplicate records. In Maximo, user-defined value lists do not conform to the specified data range. The standard search screen in Work Order tracking adds 01 day to REPORTDATE=TO_TIMESTAMP in the Advanced Query. Cannot use the Move To action from a field, if the record was retrieved using a saved query. Spell Checker in long description does not correct multiple misspelled words Attached Documents with file names that contain Swedish characters are not viewable.

Fixed issues of Maximo 5.2 from patch 03 - 09

81

Maximo 5.2 Patch 08

Workflow

Issue 82426

Description Null pointer exception when routing a workflow process where WF design contains a series of manual nodes

Work Request

Issue 79125

Description Error message: "Failure code is not valid" when creating a Work Request and returning with value from the failure code application with a newly created failure code.

Work Order Tracking

Issue 61889

66794 70452 73101 73161 74743 75669 76703 78048 78847 79203 80232 80471 80573 80552 80885

Description In Work Order Tracking, after performing spell check for the long description, user receives a java.lang.NullPointerException error on trying to change the status of the work order. In Work Orders, selecting multiple work orders with status of WAPPR and APPR and changing the status to APPR is allowed even though the group that the user belongs to has been restricted. In Work Order Tracking, the screen does not move upon clicking the Find button on the Search tab. In Work orders, the View Costs screen displays costs from canceled purchase orders. In Work Order Tracking, after performing spell check for the long description, user receives a java.lang.NullPointerException error on trying to change the status of the work order. In Work Order Tracking, on the Actuals tab, Labor subtab a user is unable to manually type a new Start and Finish date on the first new row. In Work orders, the view cost screen shows incorrect data on duplication of a work order that is associated to a purchase order. In Work orders, the view costs screen displays incorrect information if the PO that the work order refers to is changed. In Work orders, an error message "Record has been updated by another user. Refetch and try again" is displayed while saving actual labor transactions on multiple work orders. In Work Order Tracking, when a work order status is in the APPR status it is possible to delete reserved items. In Work orders, the Supervisor field does not populate on child 'task' work orders from the parent. In Work Order Tracking, all job plans are being displayed when only the job plans associated to the selected item should be displayed. In Work orders, when a work order is duplicated, the OUTLABCOST and ACTLABCOST do not balance the LABTRANS records. In Work Orders, the CREWID field is not copied to child tasks as well as when the work order is duplicated. When changing the status on a parent work order that has a direct material item on a child work order, the child work order changes to the same status as the parent even if it has an outstanding receipt. When E-SIG is enabled for the removal of a safety plan from the work order, user can select cancel and the safety plan is still removed.

82

Release Notes

Maximo 5.2 Patch 08

81706 81873 018007 66904 77221 76768 71520 71666 82374

If the actual finish date/time is entered manually and the status is changed to COMP before the entered actual finish date/time, Maximo overwrites this field with the current date/time. Integer field as a column in the wotrack moveeq.jsp page restricts data entry to four characters. Respond By field not updating when duplicating a record. Task ID is not carried over to actuals when selecting Reserved Items. Actuals are carried over when duplicating work orders. Problem Already Reported window does not open if Change Status is selected before Saving record. Removing Calendar Lookups from Wotrack qbe.jsp causes error message Attribute does not exist. Linked documents can be detached from a closed work order. Current Query drop-down is blank if saved query name contains a quotation mark (")

Maximo 5.2 Patch 03

The following table lists all fixed issues in Maximo 5.2 Patch 03. Asset Catalog

Issue 74058

Description In Locations, the SQL generated for an asset catalog search is incorrect when the search is performed using the parent location lookup.

Condition Monitoring

Issue 73494

Description In Condition Monitoring, creating two measurement points on different sites but with the same Point Name causes error while generating work orders.

Database Configuration

Issue 76553 67408

Drill Down

Description The checkmxserver.bat batch file fails with the -s parameter. In Database Configuration, setting the "Is Positive" field to 'Y' does not affect the "leadtime" field in Preventive Maintenance.

Issue 73777

Description A portion of the drilldown shows a blank line instead of the children data when using a WebSphere server.

Desktop Requisitions

Issue 11042 72335

Description In Material Requisitions, on sending an ASN transaction to Maximo, the user is displayed an error message "Attribute INTERNAL does not exist". In Desktop requisitions, errors with auto-population of quantity and amount fields on a requisition line.

Fixed issues of Maximo 5.2 from patch 03 - 09

83

Maximo 5.2 Patch 08

72831 74961 75186 75238 76403 75514 76080

In Desktop requisitions, on a service line, the inspection required field remains editable even if the service flag is checked. In Desktop requisitions, the purchase order lookup on the requisition line hyperlinks to an incorrect purchase order. Purchase Requisitions created from Desktop Requisitions have the Receipt required field set to "Y" for service type lines. In Desktop requisitions, performance of Maximo is very slow when selecting materials as planned materials. In DesktopRequisistions, error message Amount of Order Exceeds Purchasing Limits displayed on submitting MR in a foreign currency In Desktop requisitions, the requisition line displays incorrect vendor information. Material requisitions with the same MR Number in two different organizations and sites result in incorrect records being displayed when querying for the MR.

Attached Documents

Issue 12696 14346 64735

Equipment

Description In Linked documents, on adding new documents to the library the autokey is not used though the autokey has been defined in the control center. In Attached Documents, when the file name contains foreign language characters the attached document is not displayed. Users belonging to a group with restrictions on attaching a Linked document are able to attach linked documents.

Issue 041057 63747 67722 69348 041041 64274

Inventory

Description In Equipment, once a specification template has been assigned to an equipment record it cannot be removed. When a piece of equipment belongs to a parent and the child equipment is moved, the parent EQUIPMENT.CHILDREN field is not changed from 'Y' to 'N'. In Maximo, if a user types in a year on the date lookup and clicks the lookup button, the system hangs. In Equipment, on trying to add sub assemblies to an equipment record, an error message "Required field 'Date moved is blank'" is displayed. In Equipment - Search tab, the select location hierarchy button does not function correctly. In equipment, unable to move a rotating piece of equipment into storeroom location when the storeroom is receiving the equipment for the first time.

Issue 041324 041336 62756 63306

Description In Inventory, the preview reorder time is calculated incorrectly. In Inventory, the order unit field does not populate for direct issue items on reorder generated PR/PO. Inventory Action --> Reorder Items does not generate purchase requisitions when one of the vendors in the vendor list has been marked as disqualified in the Companies application. Inventory --> Reorder Items generates purchase requisition or purchase order lines in the organization base currency rather than the vendor currency.

84

Release Notes

Maximo 5.2 Patch 08

65287 70942 71481 75198 77575 77825

In Inventory, details entered in the Remarks field on the Where Used tab are changed to the equipment description on saving changes. In Inventory, the psdi/app/item/InvVendor.isUnique method is public. In Inventory, a current balance adjustment is created when an item receipt is performed against a bin that has a zero balance. Purchase requisitions created from the reorder process have an incorrect unit cost when using blanket purchase orders with foreign currencies. In Inventory upon selecting an agreement item and vendor into a Desktop Requisition (DR) line, Maximo populates the requisition line unit cost and currency code in USD and not the agreement currency and unit cost. In Inventory, error message "Sum of breakpoints must be 1" is displayed on assigning user-defined breakpoints.

Issues and Transfers

Issue 60676 67849 75293 72457

Invoice

Description In Issues and Transfers, if the first selection is not saved the same item can be selected twice for return. In Issues and Transfers, on issuing an item against an equipment record and entering a meter reading on it, the Last Reading Date displays the TRANSDATE instead of the ACTUALDATE. Maximo populates an incorrect bin number on selecting an item for transfer out using the Select Items for Transfer button. In the Issues and Transfers application, on selecting a synonym for Issue type, the GLDebit and GLCredit account are interchanged.

Issue 65279 66378 65957

75200 66386 66500 67000 71080 71105 74919 74518

Description In Invoices, the fields 'Check Number' and 'Check Code' are editable after changing the status of an Invoice to PAID. Invoices cannot be approved when there is a currency variance between the PO and the invoice, and the invoice line references a PO service line having a null quantity. A PO with a null quantity service line is receipted with a negative receipt and an invoice is raised on this PO. On approving the invoice, an error message the total invoice amount exceeds the total received amount for purchase order line is displayed. In Invoices, when the invoice is raised in a currency different from the purchase order, the un-invoiced total does not include the difference in currencies between the PO and the invoice. In Invoices, a wrong GL account is used for entering currency variance transactions. The invoicematch table does not update on approval of the invoice when the referenced POline or invoiceline is set to a null quantity. In invoices, the line cost is miscalculated when distributing costs on the invoice lines. When copying PO lines of multiple POs with the same vendor to an invoice, the page freezes with the message "loading". The pretax total field is editable for an invoice in the APPR status. The purchase order associated to an invoice in workflow is not closed when the invoice status is changed. The purchase order associated to an invoice containing a service line is not closed when the invoice status is changed to PAID.
85

Fixed issues of Maximo 5.2 from patch 03 - 09

Maximo 5.2 Patch 08

74198 71572
Job Plan

In Invoices, errors with the received quantity matching logic prevent the invoice from being approved. In Invoices, a negative amount is displayed on a credit invoice that is created by duplicating another invoice.

Issue 71936
Labor

Description In Job plans Materials tab, unhide the directreq field. If the item is checked as a direct request item, the item number field is no longer editable and the vendor field is read only.

Issue 74740
Location

Description Maximo does not validate invalid data in the pay rate field.

Issue 62459 68092 69721

System

Description After associating a user-defined value list with the priority field on the Location application, the error message "Location Priority 0 is not in the value list" is displayed on saving the location. When a child location is a member of two systems, wrong nodes are displayed in the Location drilldown. Users not authorized to delete equipment in the Equipment application are able to delete equipment from the Locations application.

Issue 026328 64938 64940 65862 67815 68727 68008 73380

Description On Oracle databases, the long description field in any application is limited to 4000 characters. Lookup pages in Maximo Korean, Japanese, Chinese, and other double byte character languages were not displayed correctly. Problem with display of lookups in Korean, and other double byte character languages. Maximo does not free some database connections leading to idle session buildups. On large SQLServer databases, locks occur with long running main selects, implicit transactions, and cursors not being closed. In Issues and transfers, the application link to work order tracking does not function correctly when the Return with value link is selected under specific conditions. Occurrence of deadlocks causes Maximo 5.2 performance to degrade until the application hangs or crashes. Maximo code trap for debugging added.

86

Release Notes

Maximo 5.2 Patch 08

MAXIMO ENTERPRISE ADAPTER/MAXIMO ENTERPRISE ADAPTERPS/MAXIMO ENTERPRISE ADAPTERSAP

Issue 63606 64389 64780 64790 65169 65278 65300 65416

66039 66537 67090 68122 69244 70466 71157

71448 68486 72214

Description In Maximo Enterprise Adapter, the mxtrans_process locks tables when a string index out of range error is encountered. In Maximo Enterprise Adapter, PO updates fail with a "This action is not allowed" error message when the PO has services or goods receipt. Incoming inventory transactions erroneously update ITEM.CAPITALIZED with "N" when the value should have remained as "Y". In Maximo Enterprise Adapter, when no UTRANSTYPE is provided on the transaction, the default bin information about the inventory table is incorrectly updated. In Maximo Enterprise Adapter, the total tax value for purchase order headers imported into Maximo is calculated incorrectly. In Maximo Enterprise Adapter, slow performance is experienced when Preventive Maintenance generates approved work orders and material reservations are created. The AMOUNT element in OAG XML is incorrectly setting large numbers to the power of 7. In Maximo Enterprise Adapter, invoices sent to Maximo from the PeopleSoft Integration include only the total line cost plus the total tax1 value even when more than one tax code was applied to the total cost for the Invoice. When a Purchase order is sent to Maximo from an external system through Maximo Enterprise Adapter, the Purchase Requisition status is not set to CLOSE even when all the lines on the PR have been copied to the PO. When an invalid method is referenced for inbound transactions and the error log displays "no such method" messages, no corresponding error XML file is produced. The interface table polling program does not handle the error condition where the delete of mxin_inter_trans returns "no rows deleted". In Maximo Enterprise Adapter, when an encoding attribute is included in xml transactions sent to Maximo, the transactions are not processed and a Null pointer exception is displayed. In Maximo Enterprise Adapter, the incoming Invoice transaction does not close the corresponding PO, even when the maxvar setting is to close the PO. Maximo Enterprise Adapter prints more lines than necessary to the console and log file. Also, the Cleanup Maximo Enterprise Adapter process resets the sync controls for the queues when they are stopped. Transactions are dropped when databases containing the interface tables are stopped and restarted without a commensurate termination and restart of webMethods. Problems with date ranges occur within Maximo Enterprise Adapter due to inconsistencies between an internal Maximo Enterprise Adapter function and the public class on which it is based; one function uses month values in the range of 1-12 while the other uses values in the range of 0-11. Korean double byte characters are corrupted when went from SAP to Maximo. In Maximo Enterprise Adapter, Maximo does not update the referred work order costs with the variance on sending in an Invoice with variance.
87

Fixed issues of Maximo 5.2 from patch 03 - 09

Maximo 5.2 Patch 08

73624

73866

74883 75290 75291 76211

In Maximo Enterprise Adapter, on sending a receipt for a PO with distributed costs, error message unique constraint violated is displayed. When a transaction cannot be saved to the MOUT_INTERDATA due to problems such as bad network connections, then all the transaction objects are not being rolled back. This results in duplication of these objects when a successful save to MOUT-INTERDATA takes place. Multiple general ledger journal transactions are being sent out by Maximo Enterprise Adapter rather than a single journal transaction as specified in the setup controls. Amount values in OAG outbound xml files are in the scientific notation when the values are not in the accepted range of values. The VALUE field in the Amount OAG xml file contains a value that includes a negative sign. In Maximo Enterprise Adapter, XML written to file or HTTP POST'ed does not contain the character set encoding in the XML header.

Preventive Maintenance

Issue 67443 68167 70447 77214

Description If a work order is closed and the Use Target Start Date is set to 'N", the Next Due Date does not get updated. TOn using a cloned PM application to generate work orders, the user is displayed a "No work order is generated" message In Preventive Maintenance, multiple work orders are generated from an overdue PM. In the Preventive Maintenance Job plan sequence tab, the checked field "show only job plans associated with current work assets" has not effect on the job plans displayed.

Purchase Orders

Issue 034807 64583

64846 66861 69834 73054 75185 75479

Description In Purchase Orders, user is unable to modify a Change Order number even if the change order is in the WAPPR status. In Purchase Orders, on changing status of a Blanket Release PO to a status that is a synonym of the APPR status, the Amount Remaining value on the Blanket PO is incorrectly set back to the original value. Purchase orders cannot be changed from WAPPR to APPR status when the purchase order was generated from a purchase requisition that was created by a desktop requisition and the desktop requisition has a status of CLOSE. In Purchase orders, unable to change the status of a PO with no PO lines from a WAPPR to an APPR status. When the currency on a material requisition is different from the currency on its associated purchase order, there is a mismatch of currencies between the PO header and PO lines. When a purchase order has a currency different from a purchase requisition and a PR line is copied to the PO, the loaded cost on the PO line is expressed in the PR currency. In Purchase orders, creating a blanket PO from a purchase order that has receipts against it does not clear the receipts from the blanket PO. Error message "Could not change PR XXXX status to CLOSE" message is displayed on creating a purchase order from a purchase requisition in workflow.

88

Release Notes

Maximo 5.2 Patch 08

Maximo Project

Issue 73981

Description After Maximo Project is installed on a Windows XP machine, Maximo does not function through the browser on the XP machine.

Purchase Requisitions

Issue 041233 61587

62050 64582 68802 69836 71199 67003 74511 66991

Description When desktop requisitions create an associated purchase requisition, the priority from the desktop requisition is not populated in the purchase requisition. If a Storeroom is populated on the Default Table Data section of purchase requisition line entry and an inventory item is purchased for the first time, the order unit and conversion fields are not populated on the purchase requisition line. In Purchase Requisitions, if the PR has information in the long description field, and the user changes the PR status from APRR to either WAPPR or CAN, the user is displayed an error message "Purchase Requisition is read-only". When a PR has a status that is a synonym of WAPPR and the Distribute Costs button is clicked its PR line, a message displays "Status must be at WAPPR to distribute costs. In Purchase Requisitions, the class ReOrderService addFromWPMaterial is made public. In Purchase Requisitions, if an item has two price agreements, Maximo selects the lowest price but selects the wrong vendor. In Purchase Requisitions, information entered in the long description field of freight terms in the Purchase requisition is not carried over on generation of the purchase order. In Purchase Requisitions, unique index PRCOST_NDX2 in the PRCOST table prevents more than one PRCOST record to be added for one PRLINE. Purchase requisitions in Workflow are left in an open status when "Could not change PR status to CLOSE" are ignored to create Purchase orders In Purchase requisitions, unable to close a PR after PR Lines not needed on the purchase order have been deleted.

Quick Reporting

Issue 69508 61730 65223 76120

Receipts

Description Maximo displays an error message "single-row subquery returns more than one row" on associating the failure list record with the work order, where two failure list records exist with the same failure list values but belonging to different sites. In Quick reporting, the time displayed on adding a row in the labor tab is not the local time but the time on the database. In Quick reporting, the status of a task on a new work order is WAPPR instead of INPRG. In Quick reporting, selecting items using the "Select Spare Parts" button returns incorrect selections.

Issue 76471

Description Remarks entered in the remarks field on a purchase requisition do not carry over to the Purchase Orders Receiving application.

Actuate Reports

Issue

Description

Fixed issues of Maximo 5.2 from patch 03 - 09

89

Maximo 5.2 Patch 08

041035

62031 69727 033044 66271 66533 73418

Safety Plan

If the select location hierarchy field is used for searching and the result set would be included in a report, an error is displayed when the Work order List Report is selected for generation. In Work orders - Work order list reports, scheduling reports by entering hours and minutes returns an error message "Invalid Schedule Date/Time' even when the values entered are valid. In Maximo actuate reports, on running reports against result sets that contain records with the + character, an error message is displayed. In Actuate Reports, an error message is displayed on running a report when a query containing a plus sign is passed to it. In Actuate reports, invalid where clauses can be passed to the report when the WHERE clause is based on a table column whose name contains the name of another column. In actuate reports, an sql error message is displayed on running the equipment list report after selecting records where the GL account is a particular value. Actuate reports fail when parameters passed to them contain double byte characters.

Issue 70321

Description In Safety Plans, error message " This hazard does not exist for the specified equipment or location" is displayed.

User Registration

Issue 60597
Workflow

Description In User Registration, on submitting an entered user registration form a "cannot delete labor because it is referenced by a job plan" error message is displayed for Maximo systems running on a SQL Server database.

Issue 12608 70882 74506

Description In a workflow where one person is assigned twice to the same task, on routing a record from the workflow inbox, a "404 Not Found" error is displayed. In Workflow, while routing a manual node if the user clicks the text data next to the radio button, the system freezes. In Workflow, the user requires requisition approval authority when routing a purchase requisition such that the workflow process approves it.

Work Requests

Issue 033534 63461 62444 64117

Description In the Work Requests application, setting a default for WORKTYPE field does not work unless the USERNAME and GRPNAME values are specified. On changing the status of a work request, the e-signature dialog box is displayed twice, the second e-signature does not accept valid user password authorizing the change. In Work Requests, on entering over 2000 characters in the long description field and saving the data an error message "The value specified." is displayed. Unexpected exception error message displayed on attaching a document in a cloned work request application.

90

Release Notes

Maximo 5.2 Patch 08

Work Orders

Issue 13114 035511 041152 65299 65868 66343 69375 69430 69627 72345 034653 62467 62474 70784 71920 72004 72138 72200 73622 73898 75472 76110 77007

Description In Maximo, "Issue to" a user is not carried over from Work Order Planned materials to Inventory Issues and Transfers. In Work order tracking, the Purchase order cost is not converted to base currency on Work order costs (Select Action - View Costs). In Work order tracking, saved queries created in other sites are listed in the Current Query: drop down list. In Work order tracking, Quick reporting, user is unable to change time in minutes when the view details button is collapsed. In Work order tracking, view costs screen displays the cost of a service PO attached to work order even though the PO is in status CAN. In Work order tracking, an incorrect estimated service cost value is displayed on the View Costs page. Error message "The quantity cannot be less than what has already been issued" is displayed on entering a new planned material line on an approved work order that has an Actuals line for the same item. In PM generated work orders having children, the priority of child work orders does not carry over from the PM, it is instead carried over from the job plan. In Work order tracking, the actual labor hours are not carrying over to the View Costs screen when the hours are entered before the labor code. In Work order tracking, on creation of a new work order with a location and a piece of equipment, a performance delay occurs on clicking the Job plan selection widget with the 'show only job plans associated with current Work Assets' box checked. In Work order tracking, the Goto Results option is returning to the wrong page of results. The "Filter" link on the Actuals tab in Work orders does not return results. In Work orders, a saved query does not return valid records due to an incorrect SQL statement. In Work orders, a default query created after removing the '=N' values from the History and Is task fields runs queries with the history and is task fields set to '=N'. In Work orders, the "Refresh GL Account" button does not work as designed. In Work orders, after performing an advanced search and then using the "Move To" lookup to move from a parent work order to a child work order a blank page is displayed. In Work order tracking, the Select Materials button on the Actuals tab does not work. In the Work Order Tracking - Actuals tab, the Labor Start and Finish time are not masked by the time zone settings on the client machine, the database time is displayed instead of the client time. The problem-code lookup functionality broken by domain ID for crossover add to the PROBLEMCODE field In Work order tracking, when a long description is placed on one field, all the fields on the user-defined table where the table name contains an underscore get the same long description associated to it. In Work orders, the start date is incorrect when the browser client used to enter a work order is in a different time zone. In Work orders, on selecting a job plan, the lead craft field is overwritten with a null value even if a value was previously entered. In work orders, there is no validation for invalid values entered in the time field
91

Fixed issues of Maximo 5.2 from patch 03 - 09

Maximo 5.2 Patch 08

034405 77526 77768

In Work orders, when using a crossover field from the EQ7 field in the Equipment application to the WOEQ7 field in work orders, the default value is wiped out on selecting a location from the drilldown. In Work orders, the estimated service cost is incorrect when multiple purchase orders are written against same work order. In work orders, a new work order can be created with the first character being an '=' sign.

92

Release Notes

Maximo 5.2 Patch 09 file manifest

G
Size 422 422 1,909 7,006 5,368 4,899 6,248 5,078 6,623 4,654 11,125 14,715 14,759 503 1,976 20,153 4,578 1,919 4,111 7,265 754 3,260 24,005 43,767 569 1,543 706 10,380 135 506 86 4,787 2,196 6,262 6/3/2008 6/12/2009 6/12/2009 6/12/2009 6/12/2009 2/17/2005 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 12/30/2003 12/2/2004 6/12/2009 6/12/2009 6/12/2009 1/5/2006 6/12/2009 10/20/2005 12/22/2005 10/31/2003 6/12/2009 6/12/2009 6/12/2009 7/23/2003 1/2/2007 1/2/2007 1/2/2007 1/2/2007 3/22/2005 10/24/2003 10/20/2005 6/12/2009 6/12/2009

Name acrobatobj.js acrobatobj.js ActionPageHandler.class Actions.class Actions.class Actions.class Actions.class Actions.class Actions.class Actions.class Actions.class actuals.jsp actuals.jsp ActuateAPIEx.class ActuateAPILocatorEx.class ActuateControl.class AddHandler.class AddItemsHandler.class AddModifyDocLinksHandler.class

Path Modified user_files\MX52P08_files\ac...\view er\ user_files\MX52P09_files\ac...\view er\ psdi\jsp\common\ psdi\jsp\app\inventor\ psdi\jsp\app\invoice\ psdi\jsp\app\location\ psdi\jsp\app\po\ psdi\jsp\app\pr\ psdi\jsp\app\quickrep\ psdi\jsp\app\rfq\ psdi\jsp\app\wotrack\ user_files\jsp\app\wotrack\ user_files\MX52P03_files\j...\wotra ck\ psdi\servlet\ psdi\servlet\ psdi\servlet\ psdi\jsp\app\woreq\ psdi\jsp\app\item\ psdi\jsp\common\linkdocs\ user_files\MX52P06_files\...\invissu

addmodifyreservepurch.jsp e\ advanced.jsp user_files\jsp\app\workman\ AgreementInput.class psdi\app\po\virtual\ AgreementInput_Skel.class psdi\app\po\virtual\ AgreementInput_Stub.class psdi\app\po\virtual\ ampower.css user_files\jsp\css\ AncestorManager$AncestorChangeRecord.class psdi\app\common\ AncestorManager$HierarchyLevel.class psdi\app\common\ AncestorManager.class psdi\app\common\ AncMbo.class psdi\app\common\ AntErrorHandler.class psdi\ant\ app.txt user_files\jsp\app\workman\ AppletSupport.sav jsp\applet\ AppLink$linkedApp.class psdi\jsp\common\ AppLink.class psdi\jsp\common\

Copyright IBM Corp. 2007, 2009

93

ApplyIASHandler.class ApplyIASHandler.class ApprServRcptsHandler.class AppService.class AppService_Skel.class AppService_Stub.class AssetCatalogService.class AssetCatalogService_Skel.class AssetCatalogService_Stub.class AssetCatalogServiceRemote.class assetmain.jsp assetmain.jsp assetmain.jsp assignlab.jsp Assignment.class Assignment_Skel.class Assignment_Stub.class assignments.jsp assignments.jsp AssignmentSet.class AssignmentSet_Skel.class AssignmentSet_Stub.class AssignmntParty.class AssignmntParty_Skel.class AssignmntParty_Stub.class assignqu.rod attachdoclinksfile.jsp attachdoclinksfile.jsp AttachDocLinksFileHandler.class AttachDocLinksURLHandler.class Attendance.class Attendance_Skel.class Attendance_Stub.class AttendanceSet.class AttendanceSet_Skel.class AttendanceSet_Stub.class AttributeSetBean.class AutoKey.class BinLotLookup.class binnum.jsp

psdi\jsp\app\equipmnt\ psdi\jsp\app\location\ psdi\jsp\app\receipts\ psdi\server\ psdi\server\ psdi\server\ psdi\app\assetcatalog\ psdi\app\assetcatalog\ psdi\app\assetcatalog\ psdi\app\assetcatalog\ user_files\MX52P03_fi...\assetcatalo g\ user_files\MX52P05_fi...\assetcatalo g\ user_files\MX52P09_fi...\assetcatalo g\ user_files\jsp\app\workman\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ user_files\MX52P08_files\j...\wotra ck\ user_files\MX52P09_files\j...\wotra ck\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\laborgroup\ psdi\app\laborgroup\ psdi\app\laborgroup\ user_files\Reports\reques...\ASSIG NQU\ user_files\MX52P04_files\...\linkdo cs\ user_files\MX52P05_files\...\linkdo cs\ psdi\jsp\common\linkdocs\ psdi\jsp\common\linkdocs\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\jsp\common\assetcatalog\ psdi\mbo\ psdi\jsp\common\ user_files\MX52P07_files\js...\looku p\

9/18/2006 9/18/2006 6/12/2009 8/4/2005 8/4/2005 8/4/2005 6/12/2009 6/12/2009 6/12/2009 8/23/2005 1/6/2005 6/30/2005 6/12/2009 11/13/2003 10/5/2006 10/5/2006 10/5/2006 6/3/2008 6/12/2009 10/5/2006 10/5/2006 10/5/2006 12/5/2006 12/5/2006 12/5/2006 10/9/2003 6/7/2005 8/12/2005 10/24/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009 8/11/2005 8/11/2005 8/11/2005 11/9/2006 6/12/2009 7/7/2006 7/7/2006

3,008 3,006 2,974 10,169 5,419 10,650 24,451 18,902 33,327 3,913 8,722 8,719 8,720 3,762 4,907 24,863 45,190 5,878 5,878 14,636 39,460 73,562 3,805 24,215 44,274 168,448 7,208 6,822 8,332 6,043 4,316 23,662 43,096 3,581 39,835 74,178 2,965 5,032 4,440 1,865

94

Release Notes

user_files\MX52P08_files\jsp\printi browserobj.js ng\ user_files\MX52P09_files\jsp\printi 6/3/2008 6/12/2009 7/10/2003 7/10/2003 8/22/2003 8/22/2003 3/14/2006 6/3/2008 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 5/6/2005 5/6/2005 5/6/2005 5/6/2005 5/6/2005 5/6/2005 5/6/2005 6/12/2009 3/16/2006 3/16/2006 3/9/2007 3/16/2006 7/13/2006 3/16/2006 3/16/2006 3/22/2005 3/22/2005 4/12/2005 12/21/2004 6/12/2009 6/12/2009 6/12/2009 9/23/2004 7/22/2005 6/12/2009 6/12/2009 6/12/2009 8/11/2006 10/9/2003 8/11/2006 8/11/2006 10/9/2003 263 263 127 229 159 159 17,189 17,378 17,378 2,555 3,968 7,579 3,310 1,706 23,690 43,110 2,078 40,195 74,816 484 13,792 3,698 2,962 5,829 5,477 6,014 39,190 72,866 972 3,974 5,380 6,909 3,931 23,674 43,108 5,334 406 16,933 4,316 23,014 9,942 171,008 24,014 43,957 153,600

browserobj.js ng\ btn_modifylaboravail.gif user_files\jsp\images\ btn_showassignments.gif user_files\jsp\images\ btnicon_matchlabortowork.gif user_files\jsp\images\ btnicon_matchworktolabor.gif user_files\jsp\images\ build.xml user_files\MX52P06_files\ build.xml user_files\MX52P08_files\ build.xml user_files\MX52P09_files\ BulletinBoardService.class psdi\server\ BulletinBoardService_Skel.class psdi\server\ BulletinBoardService_Stub.class psdi\server\ CalendarBean.class psdi\jsp\beans\ CalendarView.class psdi\app\workorder\virtual\ CalendarView_Skel.class psdi\app\workorder\virtual\ CalendarView_Stub.class psdi\app\workorder\virtual\ CalendarViewSet.class psdi\app\workorder\virtual\ CalendarViewSet_Skel.class psdi\app\workorder\virtual\ CalendarViewSet_Stub.class psdi\app\workorder\virtual\ CalendarViewSetRemote.class psdi\app\workorder\virtual\ CatalogSearchHandler.class psdi\jsp\common\assetcatalog\ ChangeStatusHandler.class psdi\jsp\app\buyer\ ChangeStatusHandler.class psdi\jsp\app\woreq\ ChangeStatusHandler.class psdi\jsp\app\wotrack\ ChangeStatusHandler.class psdi\jsp\common\purchasing\ ChangeStatusSet.class psdi\app\common\virtual\ ChangeStatusSet_Skel.class psdi\app\common\virtual\ ChangeStatusSet_Stub.class psdi\app\common\virtual\ ChangeWebModuleContextTask$XEntityResolver .class ChangeWebModuleContextTask.class CheckBoxTag.class CheckMXServer.class ClassSpec.class ClassSpec_Skel.class ClassSpec_Stub.class CleanupMIG.class ColInfo.class ColumnBean.class ColumnDefinitionTag.class CommonActions.class Company.class company.rod Company_Skel.class Company_Stub.class cond.rod psdi\ant\ psdi\ant\ psdi\jsptags\ psdi\server\ psdi\app\assetcatalog\ psdi\app\assetcatalog\ psdi\app\assetcatalog\ psdi\iface\install\ psdi\iface\install\ psdi\jsptags\ psdi\jsptags\ psdi\jsp\common\ psdi\app\company\ user_files\Reports\request...\COM PANY\ psdi\app\company\ psdi\app\company\ user_files\Reports\request pa...\COND\

Maximo 5.2 Patch 09 file manifest

95

ConnectionKey.class ConRef.class copycodes.jsp CopyCodesHandler.class Cost.class craft.rod CreateTable.class CronTaskManager$CronIncrementThread.class CronTaskManager$CronShutdownThread.class CronTaskManager$CronThread.class CronTaskManager.class crystal.jsp Currency.class Currency_Skel.class Currency_Stub.class CurrencyService.class CurrencyService_Skel.class CurrencyService_Stub.class datelookup.jsp datelookup.jsp DBManager$ConnectionPoolThread.class DBManager$DBRetryThread.class DBManager$Lock.class DBManager.class DBShortcut.class DefaultOrderPrice.class DefineDoctypesHandler.class detailequip_fail_tbl.rod details.jsp directprint.jsp directprint.jsp directprint.jsp directprint.jsp divider_tableheader.gif DMSFactory.class DMSManager.class Docinfo.class Docinfo_Skel.class Docinfo_Stub.class Doclinks.class Doclinks_Skel.class
96

psdi\security\ psdi\server\ user_files\MX52P07_files\j...\failure \ psdi\jsp\app\failure\ psdi\app\common\ user_files\Reports\request p...\CRAFT\ psdi\iface\install\ psdi\server\ psdi\server\ psdi\server\ psdi\server\ user_files\jsp\app\wotrack\ psdi\app\currency\ psdi\app\currency\ psdi\app\currency\ psdi\app\currency\ psdi\app\currency\ psdi\app\currency\ user_files\jsp\app\workman\ user_files\MX52P03_files\js...\looku p\ psdi\server\ psdi\server\ psdi\server\ psdi\server\ psdi\mbo\ psdi\app\common\ psdi\jsp\common\linkdocs\ user_files\Reports\reques...\EQUIP MNT\ user_files\MX52P07_files\jsp...\buy er\ user_files\MX52P04_files\ac...\view er\ user_files\MX52P06_files\ac...\view er\ user_files\MX52P08_files\ac...\view er\ user_files\MX52P09_files\ac...\view er\ user_files\jsp\images\ psdi\util\ psdi\util\ psdi\app\doclink\ psdi\app\doclink\ psdi\app\doclink\ psdi\app\doclink\ psdi\app\doclink\

6/12/2009 6/12/2009 9/15/2006 10/5/2006 4/8/2005 10/9/2003 7/22/2005 6/12/2009 6/12/2009 6/12/2009 6/12/2009 9/4/2003 7/13/2006 4/26/2005 4/26/2005 6/12/2009 6/12/2009 6/12/2009 10/31/2003 8/17/2004 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 2/9/2005 10/9/2003 5/10/2006 3/21/2005 11/2/2005 6/3/2008 6/12/2009 8/22/2003 8/16/2005 8/16/2005 8/16/2005 8/16/2005 8/16/2005 6/16/2005 6/16/2005

1,036 6,242 2,965 2,298 5,515 170,496 13,523 881 565 1,884 10,936 3,219 5,584 25,484 46,275 4,134 8,096 15,286 7,095 6,891 2,026 1,454 351 11,799 3,925 11,088 3,508 166,912 8,338 4,826 5,256 5,334 5,431 45 2,156 2,941 6,722 24,788 44,924 9,098 24,211
Release Notes

Doclinks_Stub.class DoclinkService$URLUTF8Encoder.class DoclinkService.class DoclinkService_Skel.class DoclinkService_Stub.class DoclinksRemote.class DocRegistrationDMSHandler.class docregistrationfile.jsp DocRegistrationFileHandler.class DocRegistrationURLHandler.class DocTypesBean.class DrillDown.class DrillDown_Skel.class DrillDown_Stub.class DrillDownLine.class DrillDownMboSetBean$treeColumn.class DrillDownMboSetBean.class DrilldownPageHandler.class DrilldownTag.class DrilldownTreeTag.class drillequip_fail_tbl.rod dynamic.jar dynamic.js dynamic.js dynamic.js dynamic.js dynamic.js DynamicDataServlet.class DynamicSetValueApplet.sav eaudit_tbl.rod emresponse_kpi_l1.rod emresponse_kpi_l1.rod equip_costrollup_tbl_act.rod equip_costrollup_update_act.rod Equipment.class equipment_cost_tbl.rod
Copyright IBM Corp. 2007, 2009

psdi\app\doclink\ psdi\app\doclink\ psdi\app\doclink\ psdi\app\doclink\ psdi\app\doclink\ psdi\app\doclink\ psdi\jsp\common\linkdocs\ user_files\MX52P05_files\...\linkdo cs\ psdi\jsp\common\linkdocs\ psdi\jsp\common\linkdocs\ psdi\jsp\common\linkdocs\ psdi\app\common\virtual\ psdi\app\common\virtual\ psdi\app\common\virtual\ psdi\jsp\common\drilldown\ psdi\jsp\beans\ psdi\jsp\beans\ psdi\jsp\common\drilldown\ psdi\jsptags\ psdi\jsptags\ user_files\Reports\reques...\EQUIP MNT\ user_files\MX52P04_file...\javascrip t\ user_files\MX52P05_file...\javascrip t\ user_files\MX52P06_file...\javascrip t\ user_files\MX52P08_file...\javascrip t\ user_files\MX52P09_file...\javascrip t\ psdi\servlet\ jsp\applet\ user_files\Reports\reques...\CONFI GUR\ user_files\Reports\request ...\oracle\ user_files\Reports\reque...\sqlserve r\ ActuateReports\Reports\EQUIPMN T\ ActuateReports\Reports\EQUIPMN T\ psdi\app\equipment\ user_files\Reports\reques...\EQUIP MNT\

6/16/2005 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/16/2005 9/7/2004 11/8/2005 11/10/2005 9/7/2004 11/10/2005 12/13/2005 12/13/2005 12/13/2005 10/5/2006 6/12/2009 6/12/2009 7/12/2005 7/12/2005 7/12/2005 10/9/2003 6/12/2009 5/31/2005 7/20/2005 3/22/2006 6/3/2008 6/12/2009 3/23/2006 10/20/2005 10/9/2003 10/9/2003 10/9/2003 6/12/2009 6/12/2009 6/12/2009 10/9/2003

44,227 5,063 11,319 9,186 16,979 362 4,599 6,449 5,872 3,902 2,081 14,589 23,678 43,151 2,191 1,043 13,655 10,395 6,184 7,965 96,768 22,764 24,660 24,636 25,242 25,886 25,886 16,859 11,975 125,440 153,088 117,248 315,392 200,192 41,285 144,896
97

Equipment_Skel.class Equipment_Stub.class EquipmentInputSet.class EquipmentInputSet_Skel.class EquipmentInputSet_Stub.class EquipmentRemote.class EquipmentService.class EquipmentService_Skel.class EquipmentService_Stub.class EquipmentSet.class EquipmentSet_Skel.class EquipmentSet_Stub.class EquipmentSpec.class EquipmentSpec_Skel.class EquipmentSpec_Stub.class equipmnt.rod equipmnt_costrollup.rod esig_tbl.rod EventTopic$1.class EventTopic$Subscription.class EventTopic.class failrep.jsp failrep.jsp FailrepHandler.class failure.rod FailureList.class FailureList_Skel.class FailureList_Stub.class FailureReport.class FailureReport_Skel.class FailureReport_Stub.class FailureReportSet.class FailureReportSet_Skel.class FailureReportSet_Stub.class FauxMboSet.class FauxMboSet_Skel.class FauxMboSet_Stub.class filefolderlistcontent.jsp FinancialService.class FinancialService_Skel.class FinancialService_Stub.class finishassign.jsp FldActualsTaskID.class
98

psdi\app\equipment\ psdi\app\equipment\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\equipment\ psdi\app\equipment\ psdi\app\equipment\ psdi\app\equipment\ psdi\app\equipment\ psdi\app\equipment\ psdi\app\equipment\ psdi\app\equipment\ psdi\app\equipment\ psdi\app\equipment\ user_files\Reports\reques...\EQUIP MNT\ user_files\Reports\reques...\EQUIP MNT\ user_files\Reports\reques...\CONFI GUR\ psdi\server\event\ psdi\server\event\ psdi\server\event\ user_files\MX52P08_files\j...\wotra ck\ user_files\MX52P09_files\j...\wotra ck\ psdi\jsp\app\wotrack\ user_files\Reports\request...\FAIL URE\ psdi\app\failure\ psdi\app\failure\ psdi\app\failure\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\mbo\ psdi\mbo\ psdi\mbo\ user_files\MX52P06_fi...\filesfolders \ psdi\app\financial\ psdi\app\financial\ psdi\app\financial\ user_files\jsp\app\workman\ psdi\app\workorder\

6/12/2009 6/12/2009 11/17/2006 11/17/2006 11/17/2006 8/23/2005 7/21/2005 7/21/2005 7/21/2005 10/4/2006 10/4/2006 10/4/2006 6/12/2009 6/12/2009 6/12/2009 10/9/2003 10/9/2003 10/9/2003 6/12/2009 6/12/2009 6/12/2009 6/3/2008 6/12/2009 6/12/2009 10/9/2003 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 11/14/2005 11/14/2005 11/14/2005 10/7/2004 10/26/2006 10/26/2006 10/26/2006 11/21/2003 1/3/2006

39,099 71,496 6,532 39,339 73,380 3,737 8,296 6,255 12,123 16,519 43,011 79,881 4,521 24,005 43,790 132,608 129,024 126,464 402 1,640 4,199 3,774 3,774 862 153,600 7,542 25,563 47,346 1,788 23,676 43,110 7,777 39,138 73,065 21,812 38,589 71,678 36,842 8,592 10,344 19,113 3,719 2,301
Release Notes

FldCommonActualDate.class FldCommonCurrencyCode.class FldCommonLocation.class FldCommonService.class FldCommonTax.class FldCommonTaxCode.class FldCommonWonum.class FldCompanyDisabled.class FldConversion.class FldEQChild.class FldEQMoveModifyNewLocation.class FldEQMoveModifyNewParent.class FldEQMoveModifyNewSite.class FldEQVendor.class FldExchangeRate.class FldExpireDate.class FldFailureListFailureClass.class FldFailureListFailureCode.class FldInvAdjustmentBinNum.class FldInvAdjustmentLotNum.class FldInvBalancesLotNum.class FldInventoryCurBalTotal.class FldInventoryOrderQty.class FldInventoryStdCost.class FldInvoiceCostUnitCost.class FldInvoiceCostWONum.class FldInvoiceCurrencyCode.class FldInvoiceDocType.class FldInvoiceExchangeRate.class FldInvoiceInclusive.class FldInvoiceLineConversion.class FldInvoiceLineLineCost.class FldInvoiceLineProrateCost.class FldInvoiceLineQty.class FldInvoiceLineTax.class FldInvoiceLineTotal.class FldInvoiceLineUnitCost.class FldInvoiceOrigInvoice.class FldInvoicePONum.class FldInvoicePreTaxTotal.class FldInvoicePreTaxTotalForUI.class FldInvoiceTotalCostForUI.class FldInvoiceTotalTax.class FldInvoiceTotalTaxForUI.class FldInvoiceTransInvoiceNum.class FldInvoiceTransTransDate.class FldInvoiceVariance.class FldInvoiceVendor.class FldInvReserveReservedQty.class FldInvVendorAgreementPONum.class FldIssueCurrentItemEQNum.class
Maximo 5.2 Patch 09 file manifest

psdi\app\common\ psdi\app\common\purchasing\ psdi\app\common\ psdi\app\common\purchasing\ psdi\app\common\ psdi\app\common\ psdi\app\common\ psdi\app\company\ psdi\app\inventory\ psdi\app\equipment\ psdi\app\equipment\ psdi\app\equipment\ psdi\app\equipment\ psdi\app\equipment\ psdi\app\currency\ psdi\app\currency\ psdi\app\failure\ psdi\app\failure\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\inventory\ psdi\app\item\ psdi\app\inventory\virtual\

6/12/2009 6/12/2009 10/5/2006 6/12/2009 6/12/2009 3/4/2005 6/16/2005 6/12/2009 11/17/2006 3/24/2006 3/24/2006 3/24/2006 11/17/2006 6/12/2009 7/5/2005 4/26/2005 9/20/2006 10/5/2006 2/16/2006 6/12/2009 2/28/2005 9/21/2006 9/21/2006 6/12/2009 6/12/2009 7/7/2005 7/13/2006 1/13/2005 12/7/2006 12/7/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009 8/25/2005 6/12/2009 6/12/2009 6/12/2009 7/13/2006 6/12/2009 4/7/2005 4/7/2005 12/7/2006 4/7/2005 12/7/2006 3/7/2006 2/16/2005 6/12/2009 6/16/2005 3/3/2005 6/16/2005

2,256 2,139 4,200 1,931 3,489 1,593 5,119 2,209 1,053 5,268 3,570 2,885 3,025 944 2,037 2,020 905 2,439 2,242 1,128 2,546 773 714 853 741 2,658 1,436 2,041 1,390 1,878 1,163 3,491 1,561 1,768 2,087 1,189 1,449 1,956 4,922 2,702 1,363 1,339 3,724 1,932 2,201 1,280 877 4,231 1,841 2,645 961
99

FldIssueCurrentItemIssueType.class FldIssueCurrentItemLocation.class FldIssueCurrentItemQuantity.class FldIssueCurrentItemRefWO.class FldIssueCurrentItemStoreloc.class FldItemStructEqNum.class FldItemStructItemNum.class FldItemStructLocation.class FldJobMaterialDirectReq.class FldLaborPercentAlloc.class FldLaborWorkDate.class FldLabTransEnterDate.class FldLabTransLaborcode.class FldLabTransPOLineNum.class FldLabTransStartDate.class FldLabTransType.class FldLocAncestorLocation.class FldLocationCalNum.class FldLocationChildren.class FldLocationFailureCode.class FldLocationItemNum.class FldLocationLocPriority.class FldLocationNewPercent.class FldLocationStatus.class FldLocationWarrantyExpDate.class FldLocHierarchyNewParent.class FldLocHierarchyParent.class FldLockOutDeviceDescription.class FldLocSystemId.class FldLocType.class FldMatRecTransCategory.class FldMatRecTransConversion.class FldMatRecTransEqnum.class FldMatRecTransFromBin.class FldMatRecTransFromStoreLoc.class FldMatRecTransInvoiceUnitCost.class FldMatRecTransItemNum.class FldMatRecTransPoLineNum.class FldMatRecTransPoNum.class FldMatRecTransReceiptQuantity.class FldMatRecTransTaskID.class FldMatRecTransToBin.class FldMatRecTransToStoreLoc.class FldMatRecTransWoNum.class FldMatServCurrencyUnitCost.class FldMatServLineCost.class FldMatServQuantity.class FldMatUseTransActualDate.class FldMatUseTransBinnum.class FldMatUseTransEqnum.class FldMatUseTransIssueType.class
100

psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\item\ psdi\app\item\ psdi\app\item\ psdi\app\jobplan\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\safety\ psdi\app\location\ psdi\app\location\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\common\receipt\ psdi\app\common\receipt\ psdi\app\common\receipt\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\

8/4/2005 6/16/2005 6/12/2009 6/16/2005 6/16/2005 9/18/2006 8/2/2005 9/18/2006 10/22/2004 5/6/2005 5/6/2005 6/12/2009 9/28/2004 6/12/2009 6/12/2009 7/25/2005 10/26/2004 7/28/2005 4/1/2005 7/28/2005 7/28/2005 7/28/2005 7/28/2005 7/28/2005 7/28/2005 3/10/2005 8/22/2005 9/20/2006 6/12/2009 2/17/2005 2/24/2005 6/12/2009 6/12/2009 7/7/2006 6/12/2009 6/12/2009 9/20/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009 7/7/2006 6/12/2009 9/20/2006 6/12/2009 6/12/2009 6/12/2009 4/22/2005 7/7/2006 6/16/2005 8/4/2005

2,102 980 1,032 1,229 2,445 5,184 2,795 4,122 1,640 3,830 1,303 1,626 4,443 1,601 1,713 2,821 481 1,366 1,768 1,383 2,645 1,565 1,662 1,536 1,403 3,495 3,023 984 2,635 2,935 996 807 3,550 1,614 3,859 755 5,183 6,065 2,855 4,100 852 1,232 4,924 1,412 1,460 3,515 1,089 1,165 1,473 2,019 3,030
Release Notes

FldMatUseTransItemNum.class FldMatUseTransLineCost.class FldMatUseTransLocation.class FldMatUseTransLotNum.class FldMatUseTransQuantity.class FldMatUseTransRefWO.class FldMatUseTransStoreloc.class FldMatUseTransUnitCost.class FldMatUseTransWoNum.class FldMboKey.class FldMRCurrencyCode.class FldMRLineItemnum.class FldMRLineLineCost.class FldMRLineQty.class FldMRLineService.class FldMRLineStoreloc.class FldMRLineUnitcost.class FldMRLineWonum.class FldMRWonum.class FldPartialGLAccount.class FldPMJpnum.class FldPMSeqJpnum.class FldPOLineUnInvoicedCost.class FldPOLineUnInvoicedQuantity.class FldPOPONum.class FldPOPOType.class FldPOReceivedTotalCost.class FldPurAgreementPonum.class FldPurEqnum.class FldPurGLDebitAcct.class FldPurIssue.class FldPurItemNum.class FldPurLineCost.class FldPurLocation.class FldPurOrderQty.class FldPurPreTaxTotal.class FldPurRefWO.class FldPurSChargeCode.class FldPurStoreloc.class FldPurUnitCost.class FldPurVendor.class FldRFQLineItemNum.class FldServRecTransQtyToReceive.class FldSPLexiconLinkNonPer.class FldStatusChangeDate.class FldTaskID.class FldTransferCurItemQuantity.class FldTransferCurItemToBin.class FldWOActualDate.class FldWOEqnum.class FldWOEstLabCost.class
Maximo 5.2 Patch 09 file manifest

psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\mbo\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\app\financial\ psdi\app\pm\ psdi\app\pm\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\rfq\ psdi\app\labor\ psdi\app\safety\ psdi\app\common\ psdi\app\workorder\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\

8/4/2005 1/24/2006 6/16/2005 6/16/2005 6/12/2009 6/16/2005 6/16/2005 6/12/2009 6/12/2009 1/13/2005 6/12/2009 9/15/2006 6/12/2009 6/12/2009 1/18/2005 8/23/2005 6/12/2009 9/18/2006 9/18/2006 6/12/2009 6/28/2005 6/12/2009 3/24/2006 8/25/2005 6/16/2005 10/6/2005 6/12/2009 4/7/2006 6/12/2009 6/12/2009 1/20/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 8/18/2006 6/12/2009 6/12/2009 9/15/2006 9/18/2006 6/12/2009 6/28/2005 6/12/2009 6/12/2009 6/12/2009 7/7/2006 6/12/2009 9/2/2005 1/2/2007

5,668 1,470 1,450 1,375 2,217 2,532 4,191 1,209 2,550 3,757 600 6,484 1,689 1,589 1,227 2,609 1,321 566 1,935 2,789 1,668 1,033 835 950 975 2,826 1,339 4,174 2,111 1,560 1,288 8,847 3,542 1,689 3,156 1,985 1,906 2,083 2,808 1,512 5,827 2,435 1,305 9,615 1,487 2,704 972 1,172 912 2,763 1,341
101

FldWOParent.class FldWoSLHazardId.class FldWoSLTagoutId.class FldWOTaskID.class FldWpMatDirectReq.class FldWpMatLineCost.class FldWpMatOrderUnit.class FldWpMatQty.class footer.jsp Functions.js Functions.js Functions.js Functions.js GenerateWOHandler$AsyncProcess.class GenerateWOHandler.class GLComponentsSet.class GLComponentsSet_Skel.class GLComponentsSet_Stub.class GLFormat.class glnavigator.jsp Hazard.class Hazard_Skel.class Hazard_Stub.class hazards.rod Header.class header.jsp HttpCrossSiteScriptingSecurity.class HttpRequestModifyWrapper.class icon_laborlisthdr.gif icon_worklisthdr.gif iconbtn_refresh.gif IfaceLog.class InputTagSupport.class IntegrationDD.class interruptassign.jsp InvBalances.class InvBalances_Skel.class InvBalances_Stub.class InvBalancesRemote.class InvBalancesSet.class InvBalancesSet_Skel.class InvBalancesSet_Stub.class
102

psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ user_files\MX52P03_files\js...\syste m\ user_files\MX52P03_files\actuate\ MRO\ user_files\MX52P04_files\actuate\ MRO\ user_files\MX52P08_files\actuate\ MRO\ user_files\MX52P09_files\actuate\ MRO\ psdi\jsp\app\pm\ psdi\jsp\app\pm\ psdi\app\financial\ psdi\app\financial\ psdi\app\financial\ psdi\mbo\ user_files\MX52P03_files\js...\looku p\ psdi\app\safety\ psdi\app\safety\ psdi\app\safety\ user_files\Reports\request...\HAZ ARDS\ psdi\jsp\common\ user_files\MX52P05_files\js...\syste m\ psdi\webclient\system\filter\ psdi\webclient\system\filter\ user_files\jsp\images\ user_files\jsp\images\ user_files\jsp\images\ psdi\iface\util\ psdi\jsptags\ psdi\iface\mic\ user_files\jsp\app\workman\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\

6/12/2009 4/25/2006 4/25/2006 1/2/2007 6/12/2009 6/12/2009 6/12/2009 12/8/2006 3/9/2005 10/14/2004 3/4/2005 6/3/2008 6/12/2009 8/19/2004 8/19/2004 6/12/2009 6/12/2009 6/12/2009 7/7/2006 1/5/2005 11/2/2004 11/2/2004 11/2/2004 10/9/2003 10/20/2005 5/27/2003 6/12/2009 6/12/2009 8/11/2003 8/22/2003 8/22/2003 7/1/2004 7/13/2006 10/6/2005 11/21/2003 6/12/2009 6/12/2009 6/12/2009 6/12/2009 3/24/2006 3/24/2006 3/24/2006

2,663 3,640 2,737 2,208 2,644 921 595 1,703 457 17,604 17,571 17,580 17,720 1,689 4,524 7,637 40,677 75,382 8,134 4,442 4,112 23,656 43,090 170,496 2,757 2,063 1,410 2,398 83 85 64 17,817 7,946 5,813 3,984 11,202 25,450 46,704 622 3,902 38,638 71,708
Release Notes

user_files\MX52P07_files\js...\looku invballot.jsp inventor.rod Inventory.class inventory_abc_tbl.rod inventory_balance_tbl.rod inventory_eoq_tbl.rod inventory_rop_tbl.rod inventory_rop_tbl_act.rol inventory_rop_tbl_act.rol inventory_rop_update.rol inventory_rop_update.rol Inventory_Skel.class inventory_storeroompic_tbl.rod Inventory_Stub.class inventory_transactions_tbl.rod InventoryService.class InventoryService_Skel.class InventoryService_Stub.class InventorySet.class InventorySet_Skel.class InventorySet_Stub.class invlines.jsp Invoice$MatchResult.class Invoice$UninvoicedReceiptsInfo.class Invoice.class invoice.rod Invoice_Skel.class Invoice_Stub.class InvoiceCost.class InvoiceCost_Skel.class InvoiceCost_Stub.class InvoiceLine.class InvoiceLine_Skel.class InvoiceLine_Stub.class InvoiceLineSet.class
Maximo 5.2 Patch 09 file manifest

p\ user_files\Reports\reques...\INVEN TOR\ psdi\app\inventory\ user_files\Reports\reques...\INVEN TOR\ user_files\Reports\reques...\INVEN TOR\ user_files\Reports\reques...\INVEN TOR\ user_files\Reports\reques...\INVEN TOR\ ActuateReports\Reports\config\ora cle\ ActuateReports\Reports\c...\sqlserv er\ ActuateReports\Reports\config\ora cle\ ActuateReports\Reports\c...\sqlserv er\ psdi\app\inventory\ user_files\Reports\reques...\INVEN TOR\ psdi\app\inventory\ user_files\Reports\reques...\INVEN TOR\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ user_files\MX52P04_files\j...\invoic e\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ user_files\Reports\request...\INVOI CE\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\

7/7/2006 10/9/2003 6/12/2009 10/9/2003 10/9/2003 10/9/2003 10/9/2003 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 10/9/2003 6/12/2009 10/9/2003 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 2/15/2005 6/12/2009 6/12/2009 6/12/2009 10/9/2003 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009

1,915 153,088 19,567 154,112 161,280 162,304 110,080 64,512 64,000 35,840 64,000 32,598 110,592 60,062 210,432 17,969 13,294 24,012 9,329 42,319 79,184 10,511 872 6,167 38,825 153,600 42,849 76,463 10,049 24,963 45,832 39,495 29,516 55,096 5,159
103

InvoiceLineSet_Skel.class InvoiceLineSet_Stub.class InvoiceRemote.class InvoiceStatusHandler.class InvoiceSysCode.class invprint.rod InvReserve.class InvReserve_Skel.class InvReserve_Stub.class InvReserveRemote.class InvReserveSet.class InvReserveSet_Skel.class InvReserveSet_Stub.class InvReserveSetRemote.class InvVendor.class InvVendor_Skel.class InvVendor_Stub.class InvVendorRemote.class iServer.jar iServer.jar iServer.jar iServer.jar IssueCurrentItem.class IssueCurrentItem_Skel.class IssueCurrentItem_Stub.class IssueCurrentItemSet.class IssueCurrentItemSet_Skel.class IssueCurrentItemSet_Stub.class issues.jsp Item.class item.rod item_availability_tbl.rod item_availability_tbl_act.rol Item_Skel.class Item_Stub.class ItemService.class ItemService_Skel.class ItemService_Stub.class ItemSpec.class ItemSpec_Skel.class ItemSpec_Stub.class ItemStructSet.class
104

psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ psdi\app\invoice\ user_files\Reports\request...\INVOI CE\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\item\ psdi\app\item\ psdi\app\item\ psdi\app\item\ user_files\MX52P06_files\actfi...\lib \ user_files\MX52P06_files\...\jarfiles \ user_files\MX52P08_files\...\jarfiles \ user_files\MX52P09_files\...\jarfiles \ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ user_files\jsp\app\inventor\ psdi\app\item\ user_files\Reports\request pa...\ITEM\ user_files\Reports\reques...\INVEN TOR\ user_files\Reports\config\sqlserver \ psdi\app\item\ psdi\app\item\ psdi\app\item\ psdi\app\item\ psdi\app\item\ psdi\app\item\ psdi\app\item\ psdi\app\item\ psdi\app\item\

6/12/2009 6/12/2009 1/14/2005 6/12/2009 11/17/2006 10/9/2003 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 7/13/2006 3/3/2005 3/3/2005 3/3/2005 10/21/2004 10/7/2004 4/19/2004 6/3/2008 6/12/2009 9/21/2006 9/21/2006 9/21/2006 8/3/2005 8/3/2005 8/3/2005 9/10/2003 10/3/2006 10/9/2003 10/9/2003 10/8/2003 10/3/2006 10/3/2006 10/3/2006 10/3/2006 10/3/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009

40,131 74,469 1,780 4,493 1,405 153,600 4,732 24,864 45,238 430 9,955 43,321 79,459 1,671 4,850 24,661 45,385 506 1,321 5,168,851 5,167,575 5,167,575 4,850 23,698 43,114 3,580 39,204 72,873 6,599 16,490 114,176 145,408 55,296 28,362 52,239 10,454 8,215 15,472 5,297 23,985 43,770 7,693
Release Notes

ItemStructSet_Skel.class ItemStructSet_Stub.class ItemStructSetRemote.class itextlogo.gif JavaScriptGenerator.class JobLabor.class JobLabor_Skel.class JobLabor_Stub.class JobLaborSet.class JobLaborSet_Skel.class JobLaborSet_Stub.class JobMaterial.class JobMaterial_Skel.class JobMaterial_Stub.class JobPlan.class jobplan.jsp jobplan.rod JobPlan_Skel.class JobPlan_Stub.class JobTask.class JobTask_Skel.class JobTask_Stub.class JobTaskSet.class JobTaskSet_Skel.class JobTaskSet_Stub.class JobTaskSetRemote.class JobTool.class JobTool_Skel.class JobTool_Stub.class JpAssetSpLink.class JpAssetSpLink_Skel.class JpAssetSpLink_Stub.class JpAssetSpLinkSet.class JpAssetSpLinkSet_Skel.class JpAssetSpLinkSet_Stub.class JpAssetSpLinkSetRemote.class JPFilterHandler.class jspmessages.txt jspsettings.txt jspsettings.txt jspsettings.txt LabAvailViewSet.class LabAvailViewSet_Skel.class LabAvailViewSet_Stub.class Labor.class

psdi\app\item\ psdi\app\item\ psdi\app\item\ jsp\images\ psdi\jsp\beans\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ user_files\MX52P06_files\js...\looku p\ user_files\Reports\request...\JOBPL AN\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\app\jobplan\ psdi\jsp\common\ user_files\resources\defaults\ user_files\MX52P03_files\...\default s\ user_files\MX52P06_files\...\default s\ user_files\MX52P07_files\...\default s\ psdi\app\labor\virtual\ psdi\app\labor\virtual\ psdi\app\labor\virtual\ psdi\app\labor\

6/12/2009 6/12/2009 9/18/2006 9/6/2005 6/12/2009 6/12/2009 6/12/2009 6/12/2009 8/11/2005 8/11/2005 8/11/2005 6/12/2009 6/12/2009 6/12/2009 9/26/2006 3/27/2006 10/9/2003 6/28/2005 6/28/2005 10/5/2006 10/5/2006 10/5/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 4/7/2006 8/22/2003 11/23/2004 2/21/2006 9/1/2006 5/6/2005 5/6/2005 5/6/2005 6/12/2009

39,057 72,756 872 1,668 26,606 2,817 23,662 43,096 2,798 38,842 72,180 3,700 23,668 43,102 4,138 2,330 153,088 24,138 44,091 2,799 23,660 43,094 1,433 38,939 72,328 256 2,782 23,660 43,094 5,121 23,672 43,106 1,682 38,802 72,212 366 3,897 10,692 5,430 5,622 5,614 4,087 39,329 73,359 14,283

Maximo 5.2 Patch 09 file manifest

105

user_files\Reports\request labor.rod labor.txt Labor_Skel.class Labor_Stub.class LaborGroup.class LaborGroup_Skel.class LaborGroup_Stub.class LaborRemote.class LaborService.class LaborService_Skel.class LaborService_Stub.class LaborSet.class LaborSet_Skel.class LaborSet_Stub.class LaborSetRemote.class LabTrans$PostCommitLabTrans.class LabTrans.class LabTrans_Skel.class LabTrans_Stub.class LabTransListener.class LabTransSet.class LabTransSet_Skel.class LabTransSet_Stub.class LinkClassSpecSet.class LinkClassSpecSet_Skel.class LinkClassSpecSet_Stub.class linkdocs.jsp linkdocs.jsp LinkDocsTreeHandler.class LinkPropertiesHandler.class listboxcontrol.js listtabl.rod LocaleApplet.sav Location.class location.rod Location_Skel.class Location_Stub.class LocationService.class LocationService_Skel.class LocationService_Stub.class LocationSetRemote.class LocationSpec.class LocationSpec_Skel.class LocationSpec_Stub.class
106

p...\LABOR\ user_files\resources\defaults\ psdi\app\labor\ psdi\app\labor\ psdi\app\laborgroup\ psdi\app\laborgroup\ psdi\app\laborgroup\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\assetcatalog\virtual\ psdi\app\assetcatalog\virtual\ psdi\app\assetcatalog\virtual\ user_files\MX52P08_files\j...\jobpla n\ user_files\MX52P09_files\j...\jobpla n\ psdi\jsp\common\linkdocs\ psdi\jsp\common\linkdocs\ user_files\MX52P05_file...\javascrip t\ user_files\Reports\reques...\CONFI GUR\ jsp\applet\ psdi\app\location\ user_files\Reports\reques...\LOCA TION\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\

10/9/2003 11/4/2003 6/12/2009 6/12/2009 12/5/2006 12/5/2006 12/5/2006 10/26/2006 6/12/2009 6/12/2009 6/12/2009 5/18/2006 5/18/2006 5/18/2006 5/18/2006 10/26/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 9/13/2004 9/13/2004 9/13/2004 6/3/2008 6/12/2009 10/20/2005 10/20/2005 9/29/2004 10/9/2003 1/11/2005 6/12/2009 10/9/2003 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 1/3/2006 6/12/2009 6/12/2009 6/12/2009

152,576 4,692 28,351 52,181 4,285 24,787 45,415 1,454 8,677 6,872 13,135 5,459 40,984 76,607 1,581 1,840 13,228 23,812 43,525 1,723 8,444 42,319 79,152 1,984 39,204 72,873 1,916 1,916 2,112 4,103 4,396 110,592 3,106 28,942 154,112 36,054 67,923 16,230 8,493 15,973 3,594 4,444 24,001 43,786

Release Notes

LocationSpecSet.class LocationSpecSet_Skel.class LocationSpecSet_Stub.class LocHierarchy.class LocHierarchy_Skel.class LocHierarchy_Stub.class login.jsp login.jsp longdesc.jsp Lookup.class LookupState.class lowagie.jar main.jsp main.jsp main.jsp main.jsp main.jsp main.jsp main.jsp main.jsp main.jsp main.jsp main.jsp main.jsp manualinput.jsp ManualInputWFMboSetBean.class MatRecTrans.class MatRecTrans_Skel.class MatRecTrans_Stub.class MatRecTransRemote.class MatRecTransSet.class MatRecTransSet_Skel.class MatRecTransSet_Stub.class MatUseTrans$PostCommitMatUseTrans.class MatUseTrans.class MatUseTrans_Skel.class MatUseTrans_Stub.class

psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ psdi\app\location\ user_files\MX52P03_files\js...\syste m\ user_files\MX52P04_files\js...\syste m\ user_files\MX52P03_files\js...\looku p\ psdi\jsp\common\ psdi\jsp\common\ lib\ user_files\jsp\app\invoice\ user_files\jsp\app\labor\ user_files\jsp\app\workman\ user_files\jsp\app\wotrack\ user_files\MX52P03_files\...\quickr ep\ user_files\MX52P03_files\jsp...\wor eq\ user_files\MX52P04_files\jsp\app\i tem\ user_files\MX52P07_files\j...\invoic e\ user_files\MX52P07_files\...\quickr ep\ user_files\MX52P07_files\j...\wotra ck\ user_files\MX52P08_files\j...\jobpla n\ user_files\MX52P09_files\j...\jobpla n\ user_files\MX52P06_files\...\workfl ow\ psdi\jsp\beans\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\

8/4/2005 8/4/2005 8/4/2005 6/12/2009 6/12/2009 6/12/2009 3/15/2005 3/15/2005 10/29/2004 9/26/2006 3/3/2005 9/22/2005 9/15/2003 10/31/2003 11/3/2003 11/5/2003 12/13/2004 11/4/2004 1/26/2005 9/13/2006 6/30/2006 6/30/2006 6/3/2008 6/12/2009 4/9/2005 10/21/2004 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 10/17/2006 6/12/2009 6/12/2009 6/12/2009

1,922 39,622 73,639 10,200 25,282 47,191 9,574 9,581 2,552 12,609 2,409 2,802,283 7,194 8,917 11,447 11,247 10,717 6,059 5,941 7,176 10,672 11,224 5,773 5,797 2,470 745 26,671 26,681 48,348 532 21,359 41,696 77,584 1,906 21,850 27,725 50,943

Maximo 5.2 Patch 09 file manifest

107

MatUseTransListener.class MatUseTransRemote.class MatUseTransSet.class MatUseTransSet_Skel.class MatUseTransSet_Stub.class MaxAPProcess.class MaxAPProcess_Skel.class MaxAPProcess_Stub.class MaximoDD.class maximoui-web.xml maximoui-web.xml maximoui-web.xml maximoui-web.xml MaxInterData.class MaxInterData_Skel.class MaxInterData_Stub.class MaxInterDataBatch.class MaxInterDataBatch_Skel.class MaxInterDataBatch_Stub.class MaxISUProcess.class MaxISUProcess_Skel.class MaxISUProcess_Stub.class MaxItmProcess.class MaxItmProcess_Skel.class MaxItmProcess_Stub.class MaxPOProcess.class MaxPOProcess_Skel.class MaxPOProcess_Stub.class MaxPRProcess.class MaxPRProcess_Skel.class MaxPRProcess_Stub.class MaxRCVProcess.class MaxRCVProcess_Skel.class MaxRCVProcess_Stub.class MaxSequenceProvider$MaxSeq.class MaxSequenceProvider.class MAXTableDomain.class MaxType.class MaxVarInput.class MaxVarInput_Skel.class MaxVarInput_Stub.class MaxVarInputForInvDefs.class MaxVarInputForInvDefs_Skel.class MaxVarInputForInvDefs_Stub.class Mbo$SubQueryFormatter.class Mbo.class Mbo_Skel.class
108

psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\iface\app\ap\ psdi\iface\app\ap\ psdi\iface\app\ap\ psdi\mbo\ user_files\MX52P03_files\WEBINF\ user_files\MX52P06_files\WEBINF\ user_files\MX52P08_files\WEBINF\ user_files\MX52P09_files\WEBINF\ psdi\iface\interdata\ psdi\iface\interdata\ psdi\iface\interdata\ psdi\iface\interdata\ psdi\iface\interdata\ psdi\iface\interdata\ psdi\iface\app\isu\ psdi\iface\app\isu\ psdi\iface\app\isu\ psdi\iface\app\item\ psdi\iface\app\item\ psdi\iface\app\item\ psdi\iface\app\po\ psdi\iface\app\po\ psdi\iface\app\po\ psdi\iface\app\pr\ psdi\iface\app\pr\ psdi\iface\app\pr\ psdi\iface\app\rcv\ psdi\iface\app\rcv\ psdi\iface\app\rcv\ psdi\util\ psdi\util\ psdi\mbo\ psdi\util\ psdi\app\system\virtual\ psdi\app\system\virtual\ psdi\app\system\virtual\ psdi\app\system\virtual\ psdi\app\system\virtual\ psdi\app\system\virtual\ psdi\mbo\ psdi\mbo\ psdi\mbo\

6/12/2009 6/16/2005 6/12/2009 6/12/2009 6/12/2009 12/22/2005 12/22/2005 12/22/2005 1/7/2005 12/17/2004 3/14/2006 6/3/2008 6/12/2009 12/7/2006 12/7/2006 12/7/2006 12/7/2006 12/7/2006 12/7/2006 1/5/2006 1/5/2006 1/5/2006 9/21/2005 9/21/2005 9/21/2005 12/22/2005 12/22/2005 12/22/2005 12/22/2005 12/22/2005 12/22/2005 6/12/2009 6/12/2009 6/12/2009 7/5/2005 7/5/2005 12/7/2004 6/12/2009 8/16/2005 8/16/2005 8/16/2005 3/15/2005 3/15/2005 3/15/2005 6/12/2009 6/12/2009 6/12/2009

1,904 1,192 13,443 41,331 76,753 9,707 7,559 14,464 21,665 4,030 4,494 6,713 6,914 9,213 7,536 14,467 12,454 7,546 14,472 6,633 7,563 14,466 22,660 7,565 14,467 16,018 7,559 14,464 13,126 7,559 14,464 8,674 7,563 14,466 629 8,406 2,689 7,658 3,299 23,682 43,106 941 23,743 43,116 2,415 30,789 23,618
Release Notes

Mbo_Stub.class MboConstants.class MboCountCronTask.class MboLONGALNValue.class MboQbe$AttributeExpressions.class MboQbe.class MboSet$MboSetIterator.class MboSet.class MboSet_Skel.class MboSet_Stub.class MboSetBean.class MboValue.class MeasurementService.class MeasurementService_Skel.class MeasurementService_Stub.class MeasurePoint.class MeasurePoint_Skel.class MeasurePoint_Stub.class MEAVersion.class menus.js Mic.class Mic_Skel.class Mic_Stub.class MicData.class MicData_Skel.class MicData_Stub.class MicService$PollMaxInterdata.class MicService$PollMaxInterdataBatch.class MicService$PollMoutInterdata.class MicService.class MicService_Skel.class MicService_Stub.class MicSet.class MicSet_Skel.class MicSet_Stub.class MicSetIn.class MicSetIn_Skel.class MicSetIn_Stub.class MicSetOut.class MicSetOut_Skel.class MicSetOut_Stub.class MicValuesClone.class modavail.jsp MoutGLProcess.class MoutGLProcess_Skel.class MoutGLProcess_Stub.class MoutISUProcess.class MoutISUProcess_Skel.class MoutISUProcess_Stub.class MoutItmProcess.class
Maximo 5.2 Patch 09 file manifest

psdi\mbo\ psdi\mbo\ psdi\server\ psdi\mbo\ psdi\mbo\ psdi\mbo\ psdi\mbo\ psdi\mbo\ psdi\mbo\ psdi\mbo\ psdi\jsp\beans\ psdi\mbo\ psdi\app\measurement\ psdi\app\measurement\ psdi\app\measurement\ psdi\app\measurement\ psdi\app\measurement\ psdi\app\measurement\ psdi\util\ user_files\MX52P04_file...\javascrip t\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ psdi\iface\mic\ user_files\jsp\app\workman\ psdi\iface\app\gl\ psdi\iface\app\gl\ psdi\iface\app\gl\ psdi\iface\app\isu\ psdi\iface\app\isu\ psdi\iface\app\isu\ psdi\iface\app\item\

6/12/2009 6/12/2009 8/4/2005 7/14/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 9/18/2006 12/16/2004 12/16/2004 12/16/2004 12/16/2004 12/16/2004 12/16/2004 12/8/2006 5/31/2005 1/5/2006 1/5/2006 1/5/2006 11/8/2004 11/8/2004 11/8/2004 12/7/2006 12/7/2006 12/7/2006 12/7/2006 12/7/2006 12/7/2006 6/12/2009 6/12/2009 6/12/2009 1/5/2006 1/5/2006 1/5/2006 1/5/2006 1/5/2006 1/5/2006 8/19/2004 11/3/2003 4/12/2005 4/12/2005 4/12/2005 6/28/2005 6/28/2005 6/28/2005 9/23/2004

43,044 1,068 2,234 6,322 9,589 3,561 1,384 56,576 38,581 71,643 24,975 20,731 1,615 5,481 10,667 4,115 24,022 43,774 1,268 58,029 5,305 6,121 11,148 7,367 2,473 4,279 4,592 4,658 3,918 39,843 10,996 21,749 14,085 7,485 14,455 21,836 7,516 14,457 15,733 7,518 14,458 2,746 3,845 18,870 7,562 14,465 3,209 7,566 14,467 7,931
109

MoutItmProcess_Skel.class MoutItmProcess_Stub.class MoutRSVProcess.class MoutRSVProcess_Skel.class MoutRSVProcess_Stub.class MoveDetails.class MoveEQHandler.class MoveEQHandler.class MoveEQHandler.class MoveEQHandler.class MPFormData.class MPInputStreamHandler.class MR.class MR_Skel.class MR_Stub.class MRLine.class MRLine_Skel.class MRLine_Stub.class MRLineBean.class MRLineRemote.class mroindex.jsp mroindex.jsp mroindex.jsp mroindex.jsp MRService.class MRService_Skel.class MRService_Stub.class MRStatusHandler.class MultiAssignWFMboSetBean.class multipleassignments.jsp MXFormat.class mxIntegration-REV150.zip mxIntegration-REV254.zip mxIntegration-REV409.zip mxIntegration-REV49.zip mxIntegration-REV601.zip mxIntegration-REV633.zip mxIntegration-REV637.zip MXServer$CronTasks.class MXServer$ErrLogStream.class MXServer.class MXServer.properties MXServer_Skel.class MXServer_Stub.class MXTransactionImpl$TransactableInfo.class

psdi\iface\app\item\ psdi\iface\app\item\ psdi\iface\app\inventory\ psdi\iface\app\inventory\ psdi\iface\app\inventory\ psdi\app\equipment\ psdi\jsp\app\equipmnt\ psdi\jsp\app\po\ psdi\jsp\app\quickrep\ psdi\jsp\app\wotrack\ psdi\jsp\util\ psdi\jsp\util\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\jsp\app\buyer\ psdi\app\mr\ user_files\MX52P04_files\j...\report s\ user_files\MX52P07_files\j...\report s\ user_files\MX52P08_files\j...\report s\ user_files\MX52P09_files\j...\report s\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\app\mr\ psdi\jsp\beans\ user_files\MX52P03_files\...\workfl ow\ psdi\util\ wm\mxIntegration\ wm\mxIntegration\ wm\mxIntegration\ wm\mxIntegration\ wm\mxIntegration\ wm\mxIntegration\ wm\mxIntegration\ psdi\server\ psdi\server\ psdi\server\ user_files\MX52P03_files\ psdi\server\ psdi\server\ psdi\txn\

9/23/2004 9/23/2004 12/7/2006 9/9/2004 9/9/2004 6/12/2009 8/11/2006 8/11/2006 8/11/2006 8/11/2006 10/5/2006 10/5/2006 12/7/2006 12/7/2006 12/7/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009 12/7/2006 3/4/2005 6/22/2006 6/3/2008 6/12/2009 6/30/2005 6/30/2005 6/30/2005 6/12/2009 10/21/2004

7,568 14,468 7,274 7,578 14,473 11,857 3,259 3,254 3,260 3,259 7,765 1,627 14,957 40,687 74,565 14,041 26,100 48,474 3,471 876 7,903 7,977 8,281 8,281 8,087 7,095 13,523 10,745 679

6/2/2004 2,704 3/2/2005 16,341 9/9/2004 12,940 3/15/2005 72,530 10/20/2005 13,762,795 1/16/2004 45,813 3/12/2007 38,315 6/3/2008 19,492,463 6/12/2009 19,500,697 2/2/2006 1,327 2/2/2006 3,487 2/2/2006 26,107 11/24/2004 12,866 2/2/2006 6,581 2/2/2006 12,825 6/12/2009 473

110

Release Notes

MXTransactionImpl.class MXTransactionImpl_Skel.class MXTransactionImpl_Stub.class nav_icon_assignlabor.gif nav_icon_finish.gif nav_icon_interrupt.gif nav_icon_selectworkdate.gif nav_icon_start.gif NavbarHandler.class Navigate.class OAGData.class oee_kpi_l1.rod oee_kpi_l1.rod oraclethin.zip OrderBy$OrderByDatum.class OrderBy.class Organization.class Organization_Skel.class Organization_Stub.class OrganizationSet.class OrganizationSet_Skel.class OrganizationSet_Stub.class PhysCntSelect.class plans.jsp plans.jsp pllabor.jsp PM$PostCommitParentChange.class PM.class pm.rod PM_Skel.class PM_Stub.class PMListener.class pmoverdue_kpi_l1.rod pmoverdue_kpi_l1.rod PMService.class PMService_Skel.class PMService_Stub.class PMWoGenCronTask.class PO.class po.rod PO_Skel.class

psdi\txn\ psdi\txn\ psdi\txn\ user_files\jsp\images\ user_files\jsp\images\ user_files\jsp\images\ user_files\jsp\images\ user_files\jsp\images\ psdi\jsp\common\ psdi\jsp\common\ psdi\iface\oag\ user_files\Reports\request ...\oracle\ user_files\Reports\reque...\sqlserve r\ lib\ psdi\app\workorder\virtual\ psdi\app\workorder\virtual\ psdi\app\site\ psdi\app\site\ psdi\app\site\ psdi\app\site\ psdi\app\site\ psdi\app\site\ psdi\jsp\app\inventor\ user_files\jsp\app\wotrack\ user_files\MX52P03_files\j...\wotra ck\ user_files\MX52P07_files\j...\wotra ck\ psdi\app\pm\ psdi\app\pm\ user_files\Reports\request page...\PM\ psdi\app\pm\ psdi\app\pm\ psdi\app\pm\ user_files\Reports\request ...\oracle\ user_files\Reports\reque...\sqlserve r\ psdi\app\pm\ psdi\app\pm\ psdi\app\pm\ psdi\app\pm\ psdi\app\po\ user_files\Reports\request page...\PO\ psdi\app\po\

6/12/2009 6/12/2009 6/12/2009 7/10/2003 11/6/2003 11/6/2003 7/10/2003 11/6/2003 12/15/2006 6/12/2009 12/7/2004 10/9/2003 10/9/2003 10/8/2004 6/12/2009 6/12/2009 11/20/2006 11/20/2006 11/20/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009 10/22/2003 12/2/2004 9/15/2006 1/2/2007 6/12/2009 10/9/2003 6/12/2009 6/12/2009 6/12/2009 10/9/2003 10/9/2003 6/12/2009 6/12/2009 6/12/2009 7/7/2006 6/12/2009 10/9/2003 6/12/2009

4,609 5,192 9,343 132 107 143 98 143 12,932 5,371 11,327 169,984 169,984 1,241,043 734 2,823 5,066 23,664 43,098 2,892 38,630 71,700 2,671 15,047 15,092 3,596 2,020 26,561 153,600 28,777 53,517 2,008 153,088 117,248 5,802 6,389 12,437 6,898 39,753 154,112 44,227

Maximo 5.2 Patch 09 file manifest

111

user_files\Reports\request po_status_tbl.rod PO_Stub.class POCost.class POCost_Skel.class POCost_Stub.class podetails.jsp POLine.class POLine_Skel.class POLine_Stub.class POLineSet.class POLineSet_Skel.class POLineSet_Stub.class POLineSetRemote.class poprint.rod POService.class POService_Skel.class POService_Stub.class POSet.class POSet_Skel.class POSet_Stub.class POSetRemote.class POStatusHandler.class PR.class pr.rod PR_Skel.class PR_Stub.class precautn.rod PriCalcSet.class PriCalcSet_Skel.class PriCalcSet_Stub.class PriCalcSetRemote.class print.jsp print.jsp print.jsp printacrobat.jsp printacrobat.jsp printacrobat.jsp printacrobat.jsp page...\PO\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\po\ user_files\MX52P03_files\jsp...\buy er\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\po\ user_files\Reports\request page...\PO\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\po\ psdi\app\pr\ user_files\Reports\request page...\PR\ psdi\app\pr\ psdi\app\pr\ user_files\Reports\reques...\PREC AUTN\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ user_files\MX52P06_files\ac...\view er\ user_files\MX52P08_files\ac...\view er\ user_files\MX52P09_files\ac...\view er\ user_files\jsp\common\system\ user_files\MX52P05_files\js...\syste m\ user_files\MX52P06_files\js...\syste m\ user_files\MX52P08_files\js...\syste m\ 10/9/2003 6/12/2009 6/12/2009 6/12/2009 6/12/2009 12/16/2004 6/12/2009 6/12/2009 6/12/2009 5/9/2005 5/9/2005 5/9/2005 6/16/2005 10/9/2003 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 11/17/2006 6/12/2009 6/12/2009 10/9/2003 6/12/2009 6/12/2009 10/9/2003 6/6/2005 6/6/2005 6/6/2005 6/6/2005 10/13/2005 6/3/2008 6/12/2009 7/14/2004 7/7/2005 3/14/2006 6/3/2008 160,768 81,312 2,280 23,648 43,082 10,611 19,856 26,149 48,431 12,874 40,802 76,049 1,468 153,088 22,073 13,878 24,977 4,448 39,572 73,538 1,957 18,871 17,324 154,112 40,189 72,508 153,600 2,137 38,920 72,275 313 4,924 5,043 5,181 10,544 13,085 13,109 12,108

112

Release Notes

user_files\MX52P09_files\js...\syste printacrobat.jsp printdocs.jsp printdocs.jsp printdocs.jsp printdocs.jsp printdocs.jsp printer.htc PrinterBvr.cab printofficecad.jsp printofficecad.jsp printofficecad.jsp printother.jsp printother.jsp printother.jsp printother.jsp printpdf.jsp printpdf.jsp printpdf.jsp printpdf.jsp printsettings.jsp printsettings.jsp PRLine.class PRLine_Skel.class PRLine_Stub.class PRLineBean.class PRLineBean.class problemcode.jsp problemcode.jsp
Maximo 5.2 Patch 09 file manifest

m\ user_files\jsp\common\system\ user_files\MX52P04_files\js...\syste m\ user_files\MX52P06_files\js...\syste m\ user_files\MX52P08_files\js...\syste m\ user_files\MX52P09_files\js...\syste m\ jsp\printing\ jsp\printing\ user_files\MX52P06_files\js...\syste m\ user_files\MX52P08_files\js...\syste m\ user_files\MX52P09_files\js...\syste m\ user_files\MX52P04_files\js...\syste m\ user_files\MX52P06_files\js...\syste m\ user_files\MX52P08_files\js...\syste m\ user_files\MX52P09_files\js...\syste m\ user_files\MX52P04_files\js...\syste m\ user_files\MX52P06_files\js...\syste m\ user_files\MX52P08_files\js...\syste m\ user_files\MX52P09_files\js...\syste m\ user_files\MX52P08_files\js...\syste m\ user_files\MX52P09_files\js...\syste m\ psdi\app\pr\ psdi\app\pr\ psdi\app\pr\ psdi\jsp\app\po\ psdi\jsp\app\rfq\ user_files\MX52P03_files\js...\looku p\ user_files\MX52P06_files\js...\looku p\

6/12/2009 5/27/2004 4/20/2005 3/14/2006 6/3/2008 6/12/2009 10/31/2005 10/31/2005 10/21/2005 6/3/2008 6/12/2009 5/25/2005 5/25/2005 6/3/2008 6/12/2009 3/21/2005 3/14/2006 6/3/2008 6/12/2009 6/3/2008 6/12/2009 6/12/2009 6/12/2009 6/12/2009 11/9/2006 11/9/2006 11/9/2004 10/7/2005

12,108 5,604 5,655 6,164 6,211 6,211 4,519 69,688 1,411 1,371 1,371 1,248 1,248 1,371 1,371 2,630 2,889 2,885 2,885 108 108 8,779 25,109 46,327 882 884 1,800 1,812
113

user_files\Reports\request prprint.rod PRService.class PRService_Skel.class PRService_Stub.class PRServiceRemote.class PRStatusHandler.class PurchasingLineMbo.class PurchasingLineMbo_Skel.class PurchasingLineMbo_Stub.class PurchasingMbo.class PurchasingMbo_Skel.class PurchasingMbo_Stub.class qbe.jsp qbe.jsp qbe.jsp qbe.jsp qbe.jsp QbeFilter$QbeExpression.class QbeFilter.class QueryOptionCombobox.class QuerySet.class QuerySet_Skel.class QuerySet_Stub.class quickrep.rod QuotationLine.class QuotationLine_Skel.class QuotationLine_Stub.class receipt.jsp receipt.jsp ReceiptInput.class ReceiptInput_Skel.class ReceiptInput_Stub.class ReceiptInputSet.class ReceiptInputSet_Skel.class ReceiptInputSet_Stub.class ReceiptMbo.class ReceiptMbo_Skel.class ReceiptMbo_Stub.class receipts.rod RecordMboSetBean.class Reorder$CostAndQty.class
114

page...\PR\ psdi\app\pr\ psdi\app\pr\ psdi\app\pr\ psdi\app\pr\ psdi\app\pr\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ psdi\app\common\purchasing\ user_files\jsp\app\workman\ user_files\MX52P06_files\...\receipt s\ user_files\MX52P07_files\...\locatio n\ user_files\MX52P08_files\...\receipt s\ user_files\MX52P09_files\...\receipt s\ psdi\app\workorder\virtual\ psdi\app\workorder\virtual\ psdi\jsptags\ psdi\app\signature\ psdi\app\signature\ psdi\app\signature\ user_files\Reports\reques...\QUICK REP\ psdi\app\rfq\ psdi\app\rfq\ psdi\app\rfq\ user_files\MX52P08_files\jsp...\buy er\ user_files\MX52P09_files\jsp...\buy er\ psdi\app\po\virtual\ psdi\app\po\virtual\ psdi\app\po\virtual\ psdi\app\po\virtual\ psdi\app\po\virtual\ psdi\app\po\virtual\ psdi\app\common\receipt\ psdi\app\common\receipt\ psdi\app\common\receipt\ user_files\Reports\reques...\RECEI PTS\ psdi\jsp\beans\ psdi\app\inventory\

10/9/2003 6/12/2009 6/12/2009 6/12/2009 11/9/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 10/20/2003 11/4/2005 6/19/2006 6/3/2008 6/12/2009 12/14/2004 12/14/2004 5/6/2005 1/5/2006 1/5/2006 1/5/2006 10/9/2003 6/12/2009 6/12/2009 6/12/2009 6/3/2008 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 10/9/2003 12/14/2006 6/12/2009

154,112 4,404 6,187 12,073 612 11,172 6,971 24,659 45,259 1,868 36,704 66,142 7,990 8,530 4,530 8,530 8,530 3,595 2,136 4,475 3,897 39,096 72,537 154,112 5,874 25,245 46,398 10,751 10,751 3,882 25,818 46,778 9,035 39,182 72,862 10,722 25,445 46,006 153,600 2,897 565
Release Notes

Reorder.class Reorder_Skel.class Reorder_Stub.class ReorderDialog$AsyncProcess.class ReorderDialog.class ReorderItems.class ReorderItems_Skel.class ReorderItems_Stub.class ReorderItemsSet.class ReorderItemsSet_Skel.class ReorderItemsSet_Stub.class reorderreport.jsp ReorderService$ReorderLockMonitor.class ReorderService.class ReorderService_Skel.class ReorderService_Stub.class ReorderServiceRemote.class ReorderSet$NextItemRetriever.class ReorderSet.class ReorderSet_Skel.class ReorderSet_Stub.class reportlaunch.jsp reportsubmit.html reportsubmit.html ReqLineDetailsHandler.class RequisitionHandler.class RequisitionLinesHandler.class resident.jsp resident.jsp ResultsBean.class ResultSetBean.class reviewdetails.jsp RFQ.class rfq.rod RFQ_Skel.class RFQ_Stub.class RFQLine.class RFQLine_Skel.class RFQLine_Stub.class rfqprint.rod RFQService.class RFQService_Skel.class RFQService_Stub.class
Maximo 5.2 Patch 09 file manifest

psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\jsp\app\inventor\ psdi\jsp\app\inventor\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ user_files\MX52P06_files\j...\report s\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ psdi\app\inventory\ user_files\jsp\common\reports\ user_files\MX52P03_files\j...\report s\ jsp\common\reports\ psdi\jsp\app\buyer\ psdi\jsp\app\buyer\ psdi\jsp\app\buyer\ user_files\MX52P03_files\...\locatio n\ user_files\MX52P04_files\...\locatio n\ psdi\jsp\common\assetcatalog\ psdi\jsp\common\ user_files\MX52P03_files\jsp...\wor eq\ psdi\app\rfq\ user_files\Reports\request pag...\RFQ\ psdi\app\rfq\ psdi\app\rfq\ psdi\app\rfq\ psdi\app\rfq\ psdi\app\rfq\ user_files\Reports\request pag...\RFQ\ psdi\app\rfq\ psdi\app\rfq\ psdi\app\rfq\

6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 1/20/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009 10/24/2006 6/12/2009 6/12/2009 6/12/2009 6/12/2009 10/8/2003 11/3/2004 6/12/2009 7/13/2006 6/12/2009 4/11/2005 1/4/2005 2/16/2005 8/23/2005 6/12/2009 11/5/2004 9/20/2006 10/9/2003 9/20/2006 9/20/2006 6/12/2009 6/12/2009 6/12/2009 10/9/2003 4/12/2005 4/12/2005 4/12/2005

20,124 25,922 47,314 1,025 4,307 1,870 23,690 43,110 7,559 39,428 73,575 11,200 2,490 31,910 12,780 22,952 2,487 2,565 18,334 40,769 75,944 1,473 4,146 4,237 2,731 8,839 1,034 3,868 3,861 4,449 4,701 8,567 13,104 132,608 37,961 67,977 7,024 24,091 43,957 154,112 2,815 5,449 10,688
115

RFQStatusHandler.class RFQVendor.class RFQVendor_Skel.class RFQVendor_Stub.class RoundToScale.class Route.class routes.rod runreport.jsp runreport.jsp runreport.jsp runreport.jsp runreport.jsp SAContext.class safeplan.rod SafetyLexicon.class SafetyLexicon_Skel.class SafetyLexicon_Stub.class SafetyService.class SafetyService_Skel.class SafetyService_Stub.class search.jsp SearchReplace$JSPFile.class SearchReplace.class SecurityService$GroupRestrictionInfo.class SecurityService$SecurityInfo.class SecurityService$SiteRestrictionInfo.class SecurityService$UserMonitor.class SecurityService.class SecurityService_Skel.class SecurityService_Stub.class SelectItemsForReturnIssue.class selectitemsforreturnissue.jsp selectitemsforreturnissue.jsp selectitemsfortransferin.jsp selectitemsfortransferout.jsp selectmaterials.jsp selectmaterialsonactuals.jsp

psdi\app\rfq\ psdi\app\rfq\ psdi\app\rfq\ psdi\app\rfq\ psdi\app\common\ psdi\app\route\ user_files\Reports\request ...\ROUTES\ user_files\MX52P03_files\j...\report s\ user_files\MX52P04_files\j...\report s\ user_files\MX52P06_files\j...\report s\ user_files\MX52P08_files\j...\report s\ user_files\MX52P09_files\j...\report s\ psdi\jsp\util\ user_files\Reports\reques...\SAFEP LAN\ psdi\app\safety\ psdi\app\safety\ psdi\app\safety\ psdi\app\safety\ psdi\app\safety\ psdi\app\safety\ user_files\jsp\app\workman\ psdi\tools\ psdi\tools\ psdi\security\ psdi\security\ psdi\security\ psdi\security\ psdi\security\ psdi\security\ psdi\security\ psdi\jsp\app\invissue\ user_files\jsp\app\invissue\ user_files\MX52P04_files\...\invissu e\ user_files\MX52P07_files\...\invissu e\ user_files\MX52P07_files\...\invissu e\ user_files\MX52P03_files\...\quickr ep\ user_files\MX52P03_files\j...\wotra ck\

6/12/2009 9/20/2006 9/20/2006 9/20/2006 12/7/2006 9/26/2006 10/9/2003 12/3/2004 4/25/2005 3/7/2006 6/3/2008 6/12/2009 10/15/2004 10/9/2003 6/12/2009 6/12/2009 6/12/2009 6/28/2005 6/28/2005 6/28/2005 10/31/2003 8/18/2005 8/18/2005 8/11/2005 8/11/2005 8/11/2005 8/11/2005 8/11/2005 8/11/2005 8/11/2005 7/7/2006 9/3/2003 2/16/2005 9/15/2006 9/15/2006 1/5/2005 1/4/2005

5,029 8,876 25,209 46,138 493 2,974 153,600 19,734 19,960 20,410 20,506 20,503 7,919 153,600 6,673 23,670 43,104 11,171 7,232 13,915 2,770 4,690 9,367 2,597 2,349 2,352 1,552 11,741 6,804 12,558 3,096 2,969 2,990 3,036 2,937 1,941 1,991

116

Release Notes

user_files\MX52P03_files\j...\wotra selectmaterialsonplans.jsp selectpoitemsin.jsp selectpoitemsin.jsp selectpoitemsout.jsp selectpoitemsout.jsp selectreserveditems.jsp selectreserveditems.jsp SelectStoreroomHandler.class SelSafetyHandler.class serv.rod ServRecTrans.class ServRecTrans_Skel.class ServRecTrans_Stub.class ServRecTransSet.class ServRecTransSet_Skel.class ServRecTransSet_Stub.class setcount.jsp SetCounterHandler.class SetLastMRHandler.class setpreferences.jsp setquery.jsp setup.cab showassigns.jsp ShowAssignsHandler.class showlist.jsp showlist.jsp ShowPlanMboSet.class ShowPlanMboSet_Skel.class ShowPlanMboSet_Stub.class ShowTasksSet.class ShowTasksSet_Skel.class ShowTasksSet_Stub.class SilentPrintServlet.class Site.class Site_Skel.class Site_Stub.class SiteService.class SiteService_Skel.class SiteService_Stub.class SiteServiceRemote.class
Maximo 5.2 Patch 09 file manifest

ck\ user_files\MX52P04_files\...\invissu e\ user_files\MX52P07_files\...\invissu e\ user_files\MX52P04_files\...\invissu e\ user_files\MX52P07_files\...\invissu e\ user_files\MX52P04_files\...\invissu e\ user_files\MX52P07_files\...\invissu e\ psdi\jsp\app\item\ psdi\jsp\app\wotrack\ user_files\Reports\request pa...\SERV\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ psdi\app\labor\ user_files\MX52P05_files\jsp\app\ pm\ psdi\jsp\app\pm\ psdi\jsp\app\pm\ user_files\jsp\app\workman\ user_files\jsp\app\workman\ jsp\printing\ user_files\jsp\app\workman\ psdi\jsp\app\workman\ user_files\jsp\app\workman\ user_files\MX52P03_files\j...\wotra ck\ psdi\app\workorder\virtual\ psdi\app\workorder\virtual\ psdi\app\workorder\virtual\ psdi\app\workorder\virtual\ psdi\app\workorder\virtual\ psdi\app\workorder\virtual\ psdi\servlet\ psdi\app\site\ psdi\app\site\ psdi\app\site\ psdi\app\site\ psdi\app\site\ psdi\app\site\ psdi\app\site\

1/4/2005 3/16/2005 9/15/2006 3/16/2005 9/15/2006 2/17/2005 9/15/2006 6/12/2009 1/24/2007 10/9/2003 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/22/2005 7/5/2005 9/18/2006 11/3/2003 10/31/2003 10/31/2005 11/13/2003 5/6/2005 10/31/2003 12/15/2004 2/4/2005 2/4/2005 2/4/2005 6/16/2005 6/16/2005 6/16/2005 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 11/20/2006

1,996 2,867 2,887 2,887 2,907 3,135 3,155 2,948 4,414 153,600 8,369 26,285 47,544 6,262 39,514 73,742 2,126 2,643 3,091 4,801 4,371 9,878 4,531 3,318 1,441 1,638 6,575 39,453 73,073 4,288 39,449 73,071 10,237 3,114 24,216 44,080 5,254 6,175 11,989 418
117

SiteSetRemote.class soap.jar soap.jar sparepart.jsp sparepart.jsp SparePartsHandlerWO.class SpecificationMbo.class SpecificationMbo_Skel.class SpecificationMbo_Stub.class SpecificationMboSet.class SpecificationMboSet_Skel.class SpecificationMboSet_Stub.class SpellingHandler.class SqlFormat.class sqr.jsp startassign.jsp StatefulMbo.class StatefulMbo_Skel.class StatefulMbo_Stub.class stored.jsp storeroom.rod StructureData.class sumequip_fail_tbl.rod SyncPropertiesTask$XEntityResolver.class SyncPropertiesTask.class tabbar.jsp table.js table.js table.js table.js table.js TableBean.class tablewindow.css taglib.tld taglocks.rod TextExport.class TextInputTag.class tool.rod TransactionGLMerger.class
118

psdi\app\site\ actfiles\jarfiles\ lib\ user_files\MX52P08_files\j...\jobpla n\ user_files\MX52P09_files\j...\jobpla n\ psdi\jsp\app\wotrack\ psdi\app\assetcatalog\ psdi\app\assetcatalog\ psdi\app\assetcatalog\ psdi\app\assetcatalog\ psdi\app\assetcatalog\ psdi\app\assetcatalog\ psdi\jsp\common\ psdi\mbo\ user_files\jsp\app\wotrack\ user_files\jsp\app\workman\ psdi\mbo\ psdi\mbo\ psdi\mbo\ user_files\jsp\app\workman\ user_files\Reports\reque...\STORE ROOM\ psdi\iface\mic\ user_files\Reports\reques...\EQUIP MNT\ psdi\ant\ psdi\ant\ user_files\jsp\app\workman\ user_files\MX52P05_file...\javascrip t\ user_files\MX52P06_file...\javascrip t\ user_files\MX52P07_file...\javascrip t\ user_files\MX52P08_file...\javascrip t\ user_files\MX52P09_file...\javascrip t\ psdi\jsp\beans\ jsp\css\ meta-inf\ user_files\Reports\reques...\TAGL OCKS\ psdi\tools\ psdi\jsptags\ user_files\Reports\request pa...\TOOL\ psdi\app\common\

6/6/2005 6/12/2009 9/13/2005 6/3/2008 6/12/2009 12/30/2004 4/15/2005 4/15/2005 4/15/2005 6/12/2009 6/12/2009 6/12/2009 4/14/2005 9/15/2006 9/4/2003 11/21/2003 6/12/2009 6/12/2009 6/12/2009 10/31/2003 10/9/2003 1/5/2006 10/9/2003 3/22/2005 3/22/2005 10/31/2003 8/8/2005 4/25/2006 12/1/2006 6/3/2008 6/12/2009 6/12/2009 1/11/2006 1/11/2006 10/9/2003 6/12/2009 4/12/2005 10/9/2003 12/7/2006

574 232,498 232,498 1,452 1,452 2,344 3,952 24,017 43,750 2,409 39,591 73,600 11,124 11,694 3,186 2,781 4,547 26,003 47,330 610 153,600 6,880 160,768 927 7,109 653 35,682 35,744 35,751 35,876 35,876 22,792 5,197 92,968 154,112 14,094 14,207 153,600 7,788
Release Notes

TransferCurItemSet.class TransferCurItemSet_Skel.class TransferCurItemSet_Stub.class TreeBuilder$LinkDocsTreeLine.class TreeBuilder$RecordInfo.class TreeBuilder.class UserInfo.class Util$URLUTF8Encoder.class Util.class Util.class V510MEA_20.class V510MEA_21.class V520_10.ora V520_10.sqs V520_11.class V520_11.ora V520_11.sqs V520_12.ora V520_12.sqs V520_13.ora V520_13.sqs V520_14.ora V520_14.sqs V520_4.ora V520_4.sqs V520_5.ora V520_5.sqs V520_6.ora V520_6.sqs V520_7.ora V520_7.sqs V520_8.ora V520_8.sqs V520_9.ora V520_9.sqs V520MEA_4.class V520MEA_5.class V520MEA_6.class ValidateNewRowHandler.class ValueListDomain.class VectorBean.class Version.class viewframeset.jsp ViewItemAvailabilityHandler.class viewparents.jsp viewtotals.jsp viewtotals.jsp
Maximo 5.2 Patch 09 file manifest

psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\jsp\common\linkdocs\ psdi\jsp\common\linkdocs\ psdi\jsp\common\linkdocs\ psdi\security\ psdi\jsp\util\ psdi\jsp\util\ psdi\util\configure\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ script\ psdi\jsp\app\buyer\ psdi\mbo\ psdi\jsp\beans\ psdi\util\ user_files\MX52P06_files\ac...\view er\ psdi\jsp\common\itemavail\ user_files\MX52P06_files\...\locatio n\ user_files\MX52P08_files\j...\jobpla n\ user_files\MX52P09_files\j...\jobpla n\

6/12/2009 6/12/2009 6/12/2009 12/22/2005 12/22/2005 12/22/2005 6/12/2009 10/20/2005 10/20/2005 3/24/2005 6/24/2004 10/28/2004 6/30/2005 6/30/2005 7/21/2005 7/14/2005 7/14/2005 8/16/2005 8/16/2005 9/2/2005 9/2/2005 8/29/2005 8/29/2005 10/26/2004 10/26/2004 12/15/2004 12/15/2004 12/16/2004 1/25/2005 12/4/2006 12/4/2006 4/1/2005 4/1/2005 5/11/2005 5/11/2005 6/24/2004 10/28/2004 11/18/2004 2/10/2006 9/29/2005 8/23/2005 6/12/2009 10/7/2004 9/20/2006 9/12/2005 6/3/2008 6/12/2009

2,969 39,202 72,872 2,351 836 14,574 3,860 5,748 27,590 98,206 1,026 960 625 626 2,458 98 105 1,241 1,860 693 699 776 779 1,142 1,144 751 751 157 164 5,182 5,199 126 126 2,356 2,359 1,024 957 1,135 2,082 5,124 4,089 1,161 17,713 3,225 3,261 3,259 3,259
119

viewWOandPMsHandler.class wait.js wait.js wait.js WaitForMaterial.class warnings.txt web.xml web.xml WFAssignment.class WFAssignment_Skel.class WFAssignment_Stub.class WFAssignmentRemote.class WFAssignmentSet.class WFAssignmentSet_Skel.class WFAssignmentSet_Stub.class WFAutoAssignment.class WFCallStackSet.class WFCallStackSet_Skel.class WFCallStackSet_Stub.class WFCronTaskAdapter.class WFMbo.class WFMbo_Skel.class WFMbo_Stub.class WFNode.class WFNode_Skel.class WFNode_Stub.class WFNodeRemote.class WFNotification.class WFNotification_Skel.class WFNotification_Stub.class WFRoleSet.class WFRoleSet_Skel.class WFRoleSet_Stub.class WFSubProcess.class WFSubProcess_Skel.class WFSubProcess_Stub.class WFTask.class WFTask_Skel.class WFTask_Stub.class WFTaskRemote.class WhereUsedSet.class WhereUsedSet_Skel.class WhereUsedSet_Stub.class WO$compareJPTask.class
120

psdi\jsp\common\wopms\ user_files\MX52P05_file...\javascrip t\ user_files\MX52P08_file...\javascrip t\ user_files\MX52P09_file...\javascrip t\ psdi\workflow\ user_files\MX52P06_files\...\default s\ user_files\MX52P03_files\WEBINF\ user_files\MX52P09_files\WEBINF\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\mbo\ psdi\mbo\ psdi\mbo\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\workflow\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\inventory\virtual\ psdi\app\workorder\

6/28/2005 11/8/2005 6/3/2008 6/12/2009 6/12/2009 3/3/2006 12/17/2004 6/12/2009 12/5/2006 12/5/2006 12/5/2006 12/5/2006 8/3/2005 8/3/2005 8/3/2005 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/12/2009 6/6/2005 6/6/2005 6/6/2005 12/5/2006 12/5/2006 12/5/2006 12/5/2006 6/12/2009 6/12/2009 6/12/2009 12/5/2006 12/5/2006 12/5/2006 6/12/2009 6/12/2009 6/12/2009 12/5/2006 12/5/2006 12/5/2006 12/5/2006 2/22/2005 2/22/2005 2/22/2005 6/12/2009

4,183 17,133 17,261 17,261 1,387 962 4,005 4,207 11,350 27,413 50,760 1,202 9,939 42,211 78,494 3,369 7,740 46,046 84,484 4,526 9,591 36,483 65,621 7,919 33,000 61,737 2,807 8,593 27,050 50,108 4,459 38,618 71,688 3,653 25,491 47,168 8,065 28,977 52,827 1,360 3,569 39,190 72,919 807

Release Notes

WO$PostCommitParentChange.class WO.class wo_matlbal_tbl.rod wo_picklist_tbl.rod WO_Skel.class WO_Stub.class WOActions.class wobacklog_kpi_l1.rod wobacklog_kpi_l1.rod WOChangeStatusSet.class WOChangeStatusSet_Skel.class WOChangeStatusSet_Stub.class WoHazard.class WoHazard_Skel.class WoHazard_Stub.class woprint.rod woprint_act.rol WORemote.class woreq.rod WoReqHandler.class work_assign_tbl.rod work_assign_tbl.rod work_assign_tbl_crft_act.rod work_assign_tbl_wo_act.rod WorkDateLookup.class Workflow.class workflow_tbl.rod workorder.txt WorkOrderBean.class WorkOrderListener.class WorkPrioritySet.class WorkPrioritySet_Skel.class WorkPrioritySet_Stub.class WorkPrioritySetRemote.class worktype_kpi_l1.rod worktype_kpi_l1.rod WoSafetyLink.class

psdi\app\workorder\ psdi\app\workorder\ user_files\Reports\request...\WOT RACK\ user_files\Reports\request...\WOT RACK\ psdi\app\workorder\ psdi\app\workorder\ psdi\jsp\common\ user_files\Reports\request ...\oracle\ user_files\Reports\reque...\sqlserve r\ psdi\app\workorder\virtual\ psdi\app\workorder\virtual\ psdi\app\workorder\virtual\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ user_files\Reports\request...\WOT RACK\ user_files\Reports\config\sqlserver \ psdi\app\workorder\ user_files\Reports\request p...\WOREQ\ psdi\jsp\app\woreq\ user_files\Reports\request...\WOR KMAN\ user_files\Reports\request...\WOT RACK\ user_files\Reports\WORKMAN\ user_files\Reports\WORKMAN\ psdi\jsp\app\workman\ psdi\jsp\common\workflow\ user_files\Reports\reques...\WFDE SIGN\ user_files\resources\defaults\ psdi\jsp\app\wotrack\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ user_files\Reports\request ...\oracle\ user_files\Reports\reque...\sqlserve r\ psdi\app\workorder\

1/2/2007 6/12/2009 10/9/2003 10/9/2003 6/12/2009 6/12/2009 11/9/2006 10/9/2003 10/9/2003 5/26/2005 5/26/2005 5/26/2005 6/12/2009 6/12/2009 6/12/2009 10/9/2003 10/8/2003 1/2/2007 10/9/2003 6/12/2009 11/18/2003 10/9/2003 11/18/2003 11/18/2003 6/12/2009 4/7/2005 10/9/2003 11/13/2003 6/12/2009 6/12/2009 6/6/2005 6/6/2005 6/6/2005 6/6/2005 10/9/2003 10/9/2003 4/25/2006

2,076 51,343 145,920 170,496 51,836 95,210 6,643 153,088 117,248 1,381 39,245 72,871 6,038 23,666 43,100 155,136 414,720 3,336 115,200 3,045 178,176 179,200 176,128 192,512 5,932 5,775 153,600 14,326 1,210 1,938 2,072 38,930 72,295 323 117,760 117,248 17,658

Maximo 5.2 Patch 09 file manifest

121

WoSafetyLink_Skel.class WoSafetyLink_Stub.class WoSafetyLinkSetRemote.class WOService.class WOService_Skel.class WOService_Stub.class WOSet.class WOSet_Skel.class WOSet_Stub.class WOSetRemote.class WOStatusHandler$MaterialUsage.class WOStatusHandler.class WoTagOut.class WOTaskBean.class wotrack.rod wotrack_costanalysis_tbl.rod wotrack_pmoverdue_priority_kpi.rod wotrack_pmoverdue_priority_kpi.rod wotrack_pmoverdue_supervisor_kpi.rod wotrack_pmoverdue_supervisor_kpi.rod WPLabor.class WPLabor_Skel.class WPLabor_Stub.class WPLaborSet.class WPLaborSet_Skel.class WPLaborSet_Stub.class WPMaterial.class WPMaterial_Skel.class WPMaterial_Stub.class WPMaterialSet.class WPMaterialSet_Skel.class WPMaterialSet_Stub.class WPTool.class WPTool_Skel.class WPTool_Stub.class WriteInterTables.class

psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\jsp\app\quickrep\ user_files\Reports\request...\WOT RACK\ user_files\Reports\request...\WOT RACK\ user_files\Reports\request ...\oracle\ user_files\Reports\reque...\sqlserve r\ user_files\Reports\request ...\oracle\ user_files\Reports\reque...\sqlserve r\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\app\workorder\ psdi\iface\intertables\

4/25/2006 4/25/2006 4/25/2006 6/12/2009 6/12/2009 6/12/2009 6/16/2005 6/16/2005 6/16/2005 1/24/2007 6/12/2009 6/12/2009 4/25/2006 11/9/2006 10/9/2003 10/9/2003 10/9/2003 10/9/2003 10/9/2003 10/9/2003 6/12/2009 6/12/2009 6/12/2009 8/11/2005 8/11/2005 8/11/2005 6/12/2009 6/12/2009 6/12/2009 12/26/2006 12/26/2006 12/26/2006 3/8/2005 3/8/2005 3/8/2005 12/7/2006

24,242 44,097 629 19,181 6,481 12,442 13,205 43,025 80,248 4,095 1,460 14,291 4,092 999 154,112 169,472 116,736 116,736 110,592 110,592 5,375 23,664 43,098 4,730 38,630 71,700 8,611 24,434 45,029 9,850 39,342 73,097 4,261 23,662 43,096 6,328

122

Release Notes

Notes on issues

Issues noted for Patch 09

This section provides additional information about the following issues in Maximo 5.2 Patch 09:

08-21903 09-13140 09-13237 09-14435

About issue 08-21903

This issue requires that you run the following four SQL statements on the target Maximo database:
update maxsyscolscfg set customclassname='psdi.app.inventory.FldConversion' tbname='ORDERUNIT' and name='CONVERSION' ; update maxsyscolumns2 set customclassname='psdi.app.inventory.FldConversion' tbname='ORDERUNIT' and name='CONVERSION' ; update maxsyscolscfg set customclassname='psdi.app.inventory.FldConversion' tbname='INVENTORY' and name='CONVERSION' ; update maxsyscolumns2 set customclassname='psdi.app.inventory.FldConversion' tbname='INVENTORY' and name='CONVERSION' ; commit ;

where

where

where

where

About issue 09-13140

The issue requires that you complete the following steps:

1 Add mbo.jar to the WebLogic Server classpath to run reports. 2 Add code to /META-INFtaglib.tld in the web.xml and maximoui-web.xml files. 3 Place the -Dbea.home variable in the WebLogic Server classpath.
Copyright IBM Corp. 2007, 2009

123

Issues noted for Patch 08

About issue 09-13237

The issue requires changes to the doclink.properties file to prevent attached documents for non-English language from failing. You must complete the following steps:

1 In the doclink.properties file, include and set one of the following properties
equal to true. Choose the one appropriate for your environment.

mxe.doclink.multilang.aix.websphere mxe.doclink.multilang.windows.websphere mxe.doclink.multilang.solaris.websphere mxe.doclink.multilang.linux.websphere mxe.doclink.multilang.hpux.websphere mxe.doclink.multilang.windows.weblogic

Example: mxe.doclink.multilang.windows.weblogic=true

2 Rebuild and redeploy the EAR files.

About issue 09-14435

To view attachments that refer to file names that contain special characters or attachments whose Maximo document name contains special characters, you must complete the following steps:

1 For each .jsp file that is in the maximo_root\jsp\common\linkdocs folder, search for a
line that is similar to <%@ page contentType="text/html;charset=ISO-8859-1" %>.

2 If you find a line like the one that step 1 describes, add a line under it indicating the
same charset attribute. Example: <%@ page contentType="text/html;charset=ISO-8859-1" %> <% request.getSession().setAttribute("CharSet","ISO-8859-1" ); %>

Issues noted for Patch 08

This section provides additional information about the following issues in Maximo 5.2 Patch 08:

07-24182 07-11133 07-15818 07-14303 and 07-15241 94470

124

Release Notes

Issues noted for Patch 08

About issue 07-24182

This issue fixed the following XML files:

build.xml maximoui-web.xml

When you install Patch 08, these files are placed in the user_files\MX52P08 folder. Create a backup of your existing files with this name, then copy build .xml to your Maximo root folder and maximoui-web.xml to the maximo_root\WEB-INF folder. NOTE If you are running WebSphere Application Server 4.0.4, you cannot deploy the maximo.ear file. You must either comment out the filter lines in the web.xml file or upgrade to WebSphere Application Server 5.1.

Editing the maximoui-web.xml file

In your maximoui-web.xml file, search for the following text:
<!-<context-param> <param-name>weblogic.httpd.inputCharset./*</paramname> <param-value>Shift_JIS</param-value> </context-param> -->

After the </context-param> --> entry, add the following code:

<!-- XSS

Issue # 07-24182 -->

<filter> <filter-name>HttpCrossSiteScriptingSecurity</filter-name> <filterclass>psdi.webclient.system.filter.HttpCrossSite Scripting Security</filter-class> <init-param> <param-name>script</param-name> <param-value>script</param-value> </init-param> <init-param> <param-name>object</param-name> <param-value>object</param-value> </init-param> <init-param> <param-name>applet</param-name> <param-value>applet</param-value> </init-param> <init-param> <param-name>embed</param-name> <param-value>embed</param-value> </init-param> <init-param> <param-name>style</param-name> <param-value>style</param-value> </init-param> <init-param> <param-name>img</param-name>
Notes on issues

125

Issues noted for Patch 08 <param-value>img</param-value> </init-param> <init-param> <param-name>div</param-name> <param-value>div</param-value> </init-param> <init-param> <param-name>iframe</param-name> <param-value>iframe</param-value> </init-param> <init-param> <param-name>input</param-name> <param-value>input</param-value> </init-param> <init-param> <param-name>body</param-name> <param-value>body</param-value> </init-param> <init-param> <param-name>link</param-name> <param-value>link</param-value> </init-param> <init-param> <param-name>meta</param-name> <param-value>meta</param-value> </init-param> <init-param> <param-name>table</param-name> <param-value>table</param-value> </init-param> <init-param> <param-name>xss</param-name> <param-value>xss</param-value> </init-param> <init-param> <param-name>exp</param-name> <param-value>exp</param-value> </init-param> <init-param> <param-name>a</param-name> <param-value>a</param-value> </init-param> </filter> <filter-mapping> <filter-name>HttpCrossSiteScriptingSecurity</filter-name> <url-pattern>/*</url-pattern> </filter-mapping> <!--XSS End Issue #07-24182-->

Editing the build.xml file

In your build-web.xml file, search for the following text:
<target name="maximoUIWarBuild" depends="init, dynamicJARBuild, mboJarBuild, buildipc" description="Builds the MAXIMO Web Application Archive File (maximoui.war) file">

Complete the following two steps:

126

Release Notes

Issues noted for Patch 08

1 Comment out the following text:

<xmlvalidate file="${maximo.maximouiwebxmlfile}" warn="false">

2 Add the following text:

<include name="psdi/webclient/**/*.class"/> --> <!-- Fix for 07-24182

Refer to the following text:

<!-- Fix for 07-24182 . web-app_2.2.dtd does not support filter. Commenting out the xmlvalidate --> <!-<xmlvalidate file="${maximo.maximouiwebxmlfile}" warn="false"> <dtd publicId="-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" location="${maximo.rootdir}/WEB-INF/web-app_2_2.dtd"/> </xmlvalidate> --> <war destfile="${maximo.maximouiwarfile}" webxml="${maximo.maximouiwebxmlfile}" index="true"> <fileset dir="${maximo.rootdir}"> <include name="index.html"/> <include name="jsp/**/*.*"/> <include name="META-INF/taglib.tld"/> <include name="WEB-INF/web-app_2_2.dtd"/> <include name="resources/images/maximoui16.gif"/> <include name="resources/images/maximoui32.gif"/> <exclude name="jsp/help/**/*.*"/> <exclude name="jsp/applet/**/*.*"/> </fileset> <fileset dir="${maximo.builddir}"> <include name="dynamic.jar"/> </fileset> <classes dir="${maximo.rootdir}" > <include name="psdi/jsp/**/*.class"/> <include name="psdi/ipc/**/*.class"/> <include name="psdi/jsptags/**/*.class"/> <include name="psdi/servlet/**/*.class"/> <include name="psdi/webclient/**/*.class"/> <!Fix for 07-24182 --> <include name="resources/**/*.*"/> <include name="jsp/**/*.txt"/> <include name="drivemap.*"/> <exclude name="psdi/ipc/*.class"/> <exclude name="psdi/servlet/MAXIMOStartupServlet.class"/> <exclude name="psdi/servlet/HttpProxyServlet.class"/> <exclude name="resources/images/**/*.*"/> <exclude name="resources/xml/**/*.*"/> </classes> <manifest> <attribute name="Class-Path"value="$ maximo.commonclasspath}"/> </manifest> </war> </target>

Notes on issues

127

Issues noted for Patch 08

About issue 07-11133

A new property, mxe.db.refcount, is now available in the MXServer.properties file. If the number of references for a connection is greater than the value specified in this property, a stack trace appears. The stack track lets you see the origin of the getconnection. The mxe.db.refcount has a default value of 100.

About issue 07-15818

A database script must be manually executed against Maximo.

Oracle database users

Run the following script against your Oracle database:
update maxsyscolumns2 set customclassname='psdi.app.workorder.FldWpMatOrderUnit' tbname='WPMATERIAL' and name='ORDERUNIT' ; update maxsyscolscfg set customclassname='psdi.app.workorder.FldWpMatOrderUnit' tbname='WPMATERIAL' and name='ORDERUNIT' ; commit ;

where

where

Microsoft SQL Server database users

Run the following script against your Microsoft SQL Server database:
update maxsyscolumns2 set customclassname='psdi.app.workorder.FldWpMatOrderUnit' tbname='WPMATERIAL' and name='ORDERUNIT' go update maxsyscolscfg set customclassname='psdi.app.workorder.FldWpMatOrderUnit' tbname='WPMATERIAL' and name='ORDERUNIT' go

where

where

About issue 07-14303 and issue 07-15241

If you are a Maximo KPI user, you must download and install these two fixes. Issue 07-14303 is an Internet Explorer version 7 issue that impacts Maximo KPI users. The fix for this issue is available at the following location: www.ibm.com/support/docview.wss?uid=swg21263435 Issue 07-15241 is a KPI fix not included in the patch. The fix for this issue is available at the following location: www.ibm.com/support/docview.wss?uid=swg21268732

128

Release Notes

Issues noted for Patch 08

About issue 94470

This feature was added for the benefit of Maximo Enterprise Adapter users. If this maxvar does not exist, or if it is set to Y, the system displays warning messages if a primary or secondary vendor is disabled. These are the same messages you received prior to adding the maxvar. When the maxvar is set to N, only Primary vendors appear in warning messages. The fix for this issue is a new maxvar 'WARNDISABLEVENDOR'. You must manually execute database scripts against the Maximo database as part of the fix.

Oracle database users

Run the following script against your Oracle database:
insert into maxvars (varname, varvalue, orgid, siteid) values ('WARNDISABLEVENDOR','X',null,null) ; update maxvars set varvalue=(select varvalue from maxvars where varname='STORENOAS') where varname='WARNDISABLEVENDOR' ; insert into maxvartype (varname, vartype, defaultvalue, description) values ('WARNDISABLEVENDOR','SYSTEM','X','Show error if Vendor is Primary vendor in Inventory') ; update maxvartype set defaultvalue=(select varvalue from maxvars where varname='STOREYESAS') where varname='WARNDISABLEVENDOR' ; commit ;

Microsoft SQL Server database users

Run the following script against your Microsoft SQL Server database:
insert into maxvars (varname, varvalue, orgid, siteid) values ('WARNDISABLEVENDOR','X',null,null) go update maxvars set varvalue=(select varvalue from maxvars where varname='STORENOAS') where varname='WARNDISABLEVENDOR' go insert into maxvartype (varname, vartype, defaultvalue, description) values ('WARNDISABLEVENDOR','SYSTEM','X','Show error if Vendor is Primary vendor in Inventory') go update maxvartype set defaultvalue=(select varvalue from maxvars where varname='STOREYESAS') where varname='WARNDISABLEVENDOR' go

Notes on issues

129

Issues noted for patches 04, 05, 06, and 07

Issues noted for patches 04, 05, 06, and 07

This section provides additional information about the following issues:

Issue 06-17302 06-17561 06-11972 06-17315 83673 06-11520 94351 89388

Patch fixed Patch 07 Patch 07 Patch 07 Patch 07 Patch 07 Patch 07 Patch 07 Patch 06

Issue description INHERITEDFROMITEM column must be set to 'Y' Unit cost issue when an item is transferred from one storeroom on an internal PO or upon receipt of internal PO. Inability to retain values when advancing to the next record. Taxes roll up to the committed cost when inclusive fields are set to N for the Company and PO tables. Inability to backdate storeroom issue transactions or labor reporting transactions. Workorder can be closed without warning, even when it references an unapproved purchase order. Unable to attach a file that contains double-byte characters. Maximo on Oracle with Maximo Enterprise Adapter receives error "Calling the class V510MEA_10.class Null" during database autoupdate on Oracle 9.2.0.5 or higher Queries for Maximo Project need to respect ISTASK = 'N The mxserver log file should include username and spid so that sql statements and blocks can be traced to specific users Cannot enter negative quantities on Material Requisition / Desktop Requisition lines In Maximo prevent multiple concurrent activities in the same user session from within the same browser. For debug purpose print mboCount to stdout. Workflow Processid is treated as a string when its value is greater than 999. Default Setting for Workorder Change Child Status Checkbox should be a database default. Attached documents are not displayed properly when spaces exist in the document folder and/or file name of an attached document. Cannot enter negative quantities on PO lines. The select items for transfer button lists items available at the storeroom rather than items available for transfer.

86230 67853 93250 0610104 85429 64899 86226 90261

Patch 06 Patch 06 Patch 06 Patch 06 Patch 05 Patch 05 Patch 05 Patch 05

033265 77689

Patch 04 Patch 04

130

Release Notes

Issues noted for patches 04, 05, 06, and 07

About issue 06-17302

When upgrading from Maximo 5.2 to Maximo 6, the INHERITEDFROMITEM column needs to be set to 'Y' (or corresponding value in the local language) in the EQUIPMENTSPEC AND LOCATIONSPEC table or the upgrade fails. Make the V520_07 database scripts language independent. If you are on Maximo 5.2 Patch 03 or lower versions, installing 5.2 patch 07 is sufficient. If you are on Maximo 5.2 Patch 04 or later versions, manually update your database with the following statements:

Oracle database users

update equipmentspec set inheritedfromitem =(select varvalue from maxvars where varname='STOREYESAS') where inheritedfromitem = 'Y'; update locationspec set inheritedfromitem = (select varvalue from maxvars where varname='STOREYESAS') where inheritedfromitem = 'Y'; update equipmentspec set inheritedfromitem =(select varvalue from maxvars where varname='STORENOAS') where inheritedfromitem = 'N'; update locationspec set inheritedfromitem = (select varvalue from maxvars where varname='STOREYESAS') where inheritedfromitem = 'N'; commit;

Microsoft SQLServer database users

update equipmentspec set inheritedfromitem =(select varvalue from maxvars where varname='STOREYESAS') where inheritedfromitem = 'Y' go update locationspec set inheritedfromitem = (select varvalue from maxvars where varname='STOREYESAS') where inheritedfromitem = 'Y' go update equipmentspec set inheritedfromitem =(select varvalue from maxvars where varname='STORENOAS') where inheritedfromitem = 'N' go update locationspec set inheritedfromitem = (select varvalue from maxvars where varname='STOREYESAS') where inheritedfromitem = 'N' go

About issue 06-17561

This issue concerns the unit cost when an item is transferred out of one storeroom on an internal PO or when the internal PO is received. The default behavior in Maximo is to use the unit cost from the PO. A new Maxvar has been created as part of the fix. Note that you must restart the Maximo application server after running this script for changes to take effect.

If the SQL with the new maxvar is not executed against the database, then the unit cost on the transfer out comes from the unit cost on the PO. The received cost also uses the unit cost from the PO. If the SQL with the new maxvar sets the varvalue to Y, then the unit cost on the transfer out comes from the unit cost on the PO. The received cost also uses the unit cost from the PO.
131

Notes on issues

Issues noted for patches 04, 05, 06, and 07

If the SQL on the new maxvar sets the varvalue to N, then the unit cost on the transfer out comes from the supplying storeroom. The received cost also uses the issue cost from the supplying storeroom.

Oracle database users

insert into maxvars (varname, varvalue) select 'TRANSFERPOCOST', (select varvalue from maxvars where varname='STORENOAS') from maxvars where not exists (select varname from maxvars where varname='TRANSFERPOCOST') and (varname=(select max(varname) from maxvars));

insert into maxvartype (varname,vartype, defaultvalue, description) select 'TRANSFERPOCOST', 'SYSTEM', (select varvalue from maxvars where varname='STORENOAS'), 'Copy poline unit cost to matrectrans(Y) or use current def. issue cost(N) for internal POs' from maxvartype where not exists (select varname from maxvartype where varname='TRANSFERPOCOST') and (varname=(select max(varname) from maxvartype));

commit;

Microsoft SQLServer database users

insert into maxvars (varname, varvalue) select 'TRANSFERPOCOST', (select varvalue from maxvars where varname='STORENOAS') from maxvars where not exists (select varname from maxvars where varname='TRANSFERPOCOST') and (varname=(select max(varname) from maxvars)) go

insert into maxvartype (varname,vartype, defaultvalue, description) select 'TRANSFERPOCOST', 'SYSTEM',

132

Release Notes

Issues noted for patches 04, 05, 06, and 07 (select varvalue from maxvars where varname='STORENOAS'), 'Copy poline unit cost to matrectrans(Y) or use current def. issue cost(N) for internal POs' from maxvartype where not exists (select varname from maxvartype where varname='TRANSFERPOCOST') and (varname=(select max(varname) from maxvartype)) go

About issue 06-11972

In Maximo, when advancing to the next record, default data values are cleared. This fix provides the flexibility to clients to decide if they would like default values to be cleared or the values retained. The fix requires a new maxvar called CLRDEFDATA. If set to Y, default data clears as users advance to subsequent records. If set to N, defaultvalues are retained. Besides installing 5.2 patch 07, clients must manually run the following database script as part of the fix. Note that you must restart the Maximo application server after running this script for changes to take effect.

Oracle database users

insert into maxvars (varname, varvalue) select 'CLRDEFDATA', (select varvalue from maxvars where varname='STOREYESAS') from maxvars where not exists (select varname from maxvars where varname='CLRDEFDATA') and (varname=(select max(varname) from maxvars));

insert into maxvartype (varname,vartype, defaultvalue, description) select 'CLRDEFDATA', 'SYSTEM', (select varvalue from maxvars where varname='STORENOAS'), 'Test issue 06-11972' from maxvartype where not exists (select varname from maxvartype where varname='CLRDEFDATA') and (varname=(select max(varname) from maxvartype));

commit;

Notes on issues

133

Issues noted for patches 04, 05, 06, and 07

Microsoft SQLServer database users

insert into maxvars (varname, varvalue) select 'CLRDEFDATA', (select varvalue from maxvars where varname='STOREYESAS') from maxvars where not exists (select varname from maxvars where varname='CLRDEFDATA') and (varname=(select max(varname) from maxvars)) go

insert into maxvartype (varname,vartype, defaultvalue, description) select 'CLRDEFDATA', 'SYSTEM', (select varvalue from maxvars where varname='STORENOAS'), 'Test issue 06-11972' from maxvartype where not exists (select varname from maxvartype where varname='CLRDEFDATA') and (varname=(select max(varname) from maxvartype)) go

About issue 06-17315

Taxes roll up to the committed cost when inclusive fields are set to 'N' for the Company and PO tables. A new Maxvar has been created as part of the fix. This maxvar provides the flexibility to clients to decided if they would like to Include or Exclude tax information in Releases against a Blanket purchase order. In addition to installing 5.2 patch 07, clients must manually run the following database script against their Maximo database. The Maximo application server must be restarted after running this script for changes to take effect.

Oracle database users

insert into maxvars ( varname, varvalue, orgid, siteid) select 'COMMITLOADED', (select varvalue from maxvars where varname='STORENOAS'), null, null from maxvars where not exists (select varname from maxvars where varname='COMMITLOADED') and

134

Release Notes

Issues noted for patches 04, 05, 06, and 07 (varname=(select max(varname) from maxvartype)); insert into maxvartype ( varname, vartype, defaultvalue, description) select 'COMMITLOADED', 'SYSTEM', (select varvalue from maxvars where varname='STOREYESAS'), 'Include (Y) or Exclude(N) Taxes in View Blanket PO' from maxvartype where not exists (select varname from maxvartype where varname='COMMITLOADED') and (varname=(select max(varname) from maxvartype)); commit;

Microsoft SQLServer database users

insert into maxvars ( varname, varvalue, orgid, siteid) select 'COMMITLOADED', (select varvalue from maxvars where varname='STORENOAS'), null, null from maxvars where not exists (select varname from maxvars where varname='COMMITLOADED') and (varname=(select max(varname) from maxvartype)) go insert into maxvartype ( varname, vartype, defaultvalue, description) select 'COMMITLOADED', 'SYSTEM', (select varvalue from maxvars where varname='STOREYESAS'), 'Include (Y) or Exclude(N) Taxes in View Blanket PO' from maxvartype where not exists (select varname from maxvartype where varname='COMMITLOADED') and (varname=(select max(varname) from maxvartype)) go

About issue 83673

This issue concerns the inability to backdate storeroom issue transactions or labor reporting transactions. The default behavior is to generate an error message when a you attempt to process a transaction against a closed financial period. In addition to installing 5.2 patch 07, clients must manually run the following database script that creates a Maxvar, against their Maximo database. The Maximo application server must be restarted after running this script for changes to take effect.
Notes on issues

135

Issues noted for patches 04, 05, 06, and 07

If the SQL with the new maxvar is not run or if the varvalue is set to N, then an error message is generated when you attempt to process a transaction against a closed financial period. If the varvalue is set to Y, when a you attempts to process a transaction against a closed financial period, Maximo applies the next open financial period.

Oracle database users

insert into maxvars ( varname, varvalue, orgid, siteid) select 'USENEXTFINPERIOD', (select varvalue from maxvars where varname='STORENOAS'), null, null from maxvars where not exists (select varname from maxvars where varname='USENEXTFINPERIOD') and (varname=(select max(varname) from maxvartype)); insert into maxvartype ( varname, vartype, defaultvalue, description) select 'USENEXTFINPERIOD', 'SYSTEM', (select varvalue from maxvars where varname='STORENOAS'), 'Use next open financial period' from maxvartype where not exists (select varname from maxvartype where varname='USENEXTFINPERIOD') and (varname=(select max(varname) from maxvartype));

commit;

Microsoft SQL Server database users

insert into maxvars ( varname, varvalue, orgid, siteid) select 'USENEXTFINPERIOD', (select varvalue from maxvars where varname='STORENOAS'), null, null from maxvars where not exists (select varname from maxvars where varname='USENEXTFINPERIOD') and (varname=(select max(varname) from maxvartype)) go insert into maxvartype ( varname, vartype, defaultvalue, description) select 'USENEXTFINPERIOD', 'SYSTEM', (select varvalue from maxvars where varname='STORENOAS'),

136

Release Notes

Issues noted for patches 04, 05, 06, and 07 'Use next open financial period' from maxvartype where not exists (select varname from maxvartype where varname='USENEXTFINPERIOD') and (varname=(select max(varname) from maxvartype)) go

About issue 06-11520

In Work Order Tracking, a workorder can be closed without a warning even when it references an unapproved purchase order. A new Maxvar has been created as part of the fix. When the Maxvar is set to Y, the closing of work orders, which reference unapproved purchase orders, are not allowed. Clients must manually execute this script against their Maximo database. The Maximo application server must be restarted after running this script for changes to take effect.

Oracle database users

insert into maxvars ( varname, varvalue, orgid, siteid) select 'CHECKOPENPOS', (select varvalue from maxvars where varname='STOREYESAS'), null, null from maxvars where not exists (select varname from maxvars where varname='CHECKOPENPOS') and (varname=(select max(varname) from maxvartype)); insert into maxvartype ( varname, vartype, defaultvalue, description) select 'CHECKOPENPOS', 'SYSTEM', (select varvalue from maxvars where varname='STOREYESAS'), 'Flag to check open purchase orders when close or cancel work order' from maxvartype where not exists (select varname from maxvartype where varname='CHECKOPENPOS') and (varname=(select max(varname) from maxvartype)); commit;

Microsoft SQLServer database users

insert into maxvars ( varname, varvalue, orgid, siteid) select 'CHECKOPENPOS',
Notes on issues

137

Issues noted for patches 04, 05, 06, and 07 (select varvalue from maxvars where varname='STOREYESAS'), null, null from maxvars where not exists (select varname from maxvars where varname='CHECKOPENPOS') and (varname=(select max(varname) from maxvartype)) go insert into maxvartype ( varname, vartype, defaultvalue, description) select 'CHECKOPENPOS', 'SYSTEM', (select varvalue from maxvars where varname='STOREYESAS'), 'Flag to check open purchase orders when close or cancel work order' from maxvartype where not exists (select varname from maxvartype where varname='CHECKOPENPOS') and (varname=(select max(varname) from maxvartype)) go commit;

About issue 94351

Unable to attach a file that contains double-byte characters. Problems were discovered with the IBM HTTP Server version 1.38 which is the default version for WebSphere WebSphere Application Server 5. URL's for some languages can still fail to open. You can check for this issue by seeing if the filename has been stored correctly in the database versus the filename on the hard-drive, however clients displayed a 404 Page cannot be found page in the browser when accessing the file link in Maximo. Upgrading the IBM HTTP Server to Version 2.x resolves this problem. An additional edit can be necessary for some languages. Examine the jsp/common/linkdocs/attachdoclinksfile.jsp file, to verify if an explicit page encoding is set on the page, such as: <%@ page contentType="text/html;charset=ISO8859-1" %>, if so, clients must perform the following edits: Add a line immediately under the page encoding line described previously to set the charset to be the same as what it set on the page. This statement is case-sensitive:
<% request.getSession().setAttribute("CharSet", "ISO-8859-1" ); %>

The second parameter of that line should be set to the same charset that the page directive is set to.

138

Release Notes

Issues noted for patches 04, 05, 06, and 07

About issue 89388

The Maximo Enterprise Adapter portion of the database autoupdate can fail due to the Oracle bug numbered 3371684. An error message Calling the class V510MEA_10.class Null, Missing IN or OUT parameter at index:: 1 is displayed during the database autoupdate on Oracle versions 9.2.0.5 or higher. See Knowledge Base Doc ID M04746 on IBM Software Online Support for downloading a new oraclethin.zip file provided by Oracle as a fix for this issue. Following is the content of the KB Doc ID M04676: When installing or upgrading Maximo Enterprise Adapter on Oracle (only), if you receive the following error in the upgrade log:
Calling the class : null And you also see the following error in the stderr log: Tue Oct 11 14:53:31 EDT 2005 java.sql.SQLException: Missing IN or OUT parameter at index:: 1 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:124) Tue Oct 11 14:53:31 EDT 2005 at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:161) Tue Oct 11 14:53:31 EDT 2005 at oracle.jdbc.driver.OraclePreparedStatement.processCompletedBindRow(OracleP reparedStatement.java:1538Tue Oct 11 14:53:31 EDT 2005 at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedS tatement.java:2882)Tue Oct 11 14:53:31 EDT 2005 at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedSta tement.java:2959)Tue Oct 11 14:53:31 EDT 2005 at psdi.iface.install.CreateTable.createTable(CreateTable.java:604)Tue Oct 11 14:53:31 EDT 2005 at script.V510MEA_10.registerFC(V510MEA_10.java:290)Tue Oct 11 14:53:31 EDT 2005 script.V510MEA_10 -------------------------------------------------------------------

You have encountered Oracle bug 3371684. Oracle has provided a fix for this in the 9.2.0.6 version of the JDBC thin driver. Complete the following application serverspecific steps to install this fix.
WebLogic Server

If your application server is WebLogic Server, complete the following steps: 1 Rename the existing oraclethin.zip file in the maximo_root\lib folder. 2 Detach the attached file and copy it into the maximo_root\lib folder. 3 For WebLogic Server, see the Maximo WebLogic Server for Windows Installation Guide where it details adding oraclethin.zip to the BEA Classpath if using Oracle 8.1.7. Theres one place on page 37 for the installsvc.cmd file, and another in Appendix A on page 117 for editing startWLS.cmd for console startup. The instructions both explain how to add the maximo_install_folder\LIB\ORACLETHIN.ZIP to the front of the CLASSPATH in the two cmd files. 4 Restore or recreate the database. 5 Rebuild and redeploy your EAR files.

WebSphere Application Server

If your application server is WebSphere Application Server, complete the following steps: You must download and install the Oracle 9.2.0.6 patch on your WebSphere Application Server machine. WebSphere Application Server uses a full installation of Oracle Client

Notes on issues

139

Issues noted for patches 04, 05, 06, and 07

Software on Windows, or an installation of the client portion of the Oracle Database Software on unix. You cannot just drop the oraclethin.zip into place for WebSphere Application Server, although you must still detach and put the attached oraclethin.zip file into the maximo_root\lib folder and rebuild your EAR files.

About issue 86230

This issue fixes Maximo Project for excluding task workorders from the data being brought into Maximo Project from Maximo. The fix for this issue consists of a new database MaxVar flag called ScheduleWOTasks that takes values of Y or N and some Maximo code changes. The following scripts have to be run manually on the Maximo database for the fix to work.
Oracle

Oracle database users run the following statements on your Maximo database:
/************** Freeform Txn -- Inserts ScheduleWOTasks into the MaxVars table. *********/ insert into maxvars (varname, varvalue) select SCHEDULEWOTASKS, (select varvalue from maxvars where varname = YES) from maxvars where not exists (select varname from maxvars where varname = SCHEDULEWOTASKS) and (varname = (select max(varname) from maxvars)); /************** Freeform Txn -- Inserts ScheduleWOTasks into the MaxVarType table. ******/ insert into maxvartype (varname, vartype, defaultvalue, description) select SCHEDULEWOTASKS, SYSTEM, (select varvalue from maxvars where varname = YES), Transfer WO Tasks to Maximo Project? from maxvartype where not exists (select varname from maxvartype where varname = SCHEDULEWOTASKS) and (varname = (select max(varname) from maxvartype)); Commit;

SQL Server

SQLServer Database Users execute the following statements on your Maximo database:
/************** Freeform Txn -- Inserts ScheduleWOTasks into the MaxVars table. *********/ insert into maxvars (varname, varvalue) select SCHEDULEWOTASKS, (select varvalue from maxvars where varname = YES) from maxvars

140

Release Notes

Issues noted for patches 04, 05, 06, and 07 where not exists (select varname from maxvars where varname = SCHEDULEWOTASKS) and (varname = (select max(varname) from maxvars)) go /************** Freeform Txn -- Inserts ScheduleWOTasks into the MaxVarType table. ******/ insert into maxvartype (varname, vartype, defaultvalue, description) select SCHEDULEWOTASKS, SYSTEM, (select varvalue from maxvars where varname = YES), Transfer WO Tasks to Maximo Project? from maxvartype where not exists (select varname from maxvartype where varname = SCHEDULEWOTASKS) and (varname = (select max(varname) from maxvartype)) go

With these database changes, Maximo will construct SQL statements that fetch data from Maximo into Maximo Project based on the setting of the Maxvar ScheduleWOTasks. If this flag is set to Y, Maximo will continue with the existing format of retrieving the specified work order and tasks. If the Maxvar is set to N, then all the tasks among these descendants will not be brought in.

About issue 67853

This fix allows the username and spid to be written to the stdout log file so that sql statements and blocks can be traced to specific users. The property mxe.debug.spid=yes should be added to the MXServer.properties file. SQLLogger information should be enabled on SQLServer databases. Oracle database users would need permission to access the v$session table for this fix to work. The mxe.verbosity property in MXServer.properties should be set to 8 or above for both the user name and spid to be written to the log file. If the mxe.verbosity property were set to 2 or above, the spid id would be written to the log for slow sql statements.

About issue 93250

This issue fixes the problem Cannot enter negative quantities on Desktop Requisition lines. However, the Desktop Requisitions app will not let the user create a line for an item to be requisitioned from a storeroom and set the quantity to a negative number. Please note that a database script must be run manually on the Maximo database for this fix to function correctly.
Oracle

Oracle Database Users, run the following statements on your Maximo database:
update maxsyscolumns set ispositive = (select varvalue from maxvars where varname=STORENOAS) where tbname = MRLINE and name = QTY; update maxsyscolscfg set ispositive = (select varvalue from maxvars where varname=STORENOAS) where tbname = MRLINE and name = QTY; update maxsyscolumns set ispositive = (select varvalue from maxvars where varname=STORENOAS) where tbname = MRLINE and name = UNITCOST;

Notes on issues

141

Issues noted for patches 04, 05, 06, and 07 update maxsyscolscfg set ispositive = (select varvalue from maxvars where varname=STORENOAS) where tbname = MRLINE and name = UNITCOST; update maxsyscolumns set ispositive = (select varvalue from maxvars where varname=STORENOAS) where tbname = MRLINE and name = LINECOST; update maxsyscolscfg set ispositive = (select varvalue from maxvars where varname=STORENOAS) where tbname = MRLINE and name = LINECOST; commit; SQL Server

SQL Server Database users run the following statements on your Maximo database:
update maxsyscolumns set ispositive = (select varvalue from maxvars where varname=STORENOAS) where tbname = MRLINE and name = QTY go update maxsyscolscfg set ispositive = (select varvalue from maxvars where varname=STORENOAS) where tbname = MRLINE and name = QTY go update maxsyscolumns set ispositive = (select varvalue from maxvars where varname=STORENOAS) where tbname = MRLINE and name = UNITCOST go update maxsyscolscfg set ispositive = (select varvalue from maxvars where varname=STORENOAS) where tbname = MRLINE and name = UNITCOST go update maxsyscolumns set ispositive = (select varvalue from maxvars where varname=STORENOAS) where tbname = MRLINE and name = LINECOST go update maxsyscolscfg set ispositive = (select varvalue from maxvars where varname=STORENOAS) where tbname = MRLINE and name = LINECOST go

Please note that Desktop Requisitions allow for entering a negative quantity only with a Vendor. It does not allow a negative quantity to be entered with a storeroom.

About issue 0610104

This fix to Maximo prevents multiple concurrent activities in the same user session from within the same browser. As part of the fix for this problem, a new exception / diagnostic message will be thrown when multiple concurrent activities are detected within the same user session. The new message is in English, however, non-English language users can translate this message to their Maximo supported language and it is handled just like any other translated message. The exception wording is in the maximo_root\resources\defaults\warnings.txt file, the following message appears: A fatal error has occurred in your Maximo session. The error has been logged. When you acknowledge this message you are logged out and must restart your browser. This error was caused by trying to interrupt a running operation using the browser stop, refresh or back controls. This error dialog box has only an OK button, which when pressed, proceeds to shutdown the users session and return the user to the Maximo Login screen. For example: Requesting a refresh operation from the browser during a running Maximo transaction is likely to cause this situation. Diagnostic /error information regarding this exception are written to the Maximo log files for the Maximo system administrator

142

Release Notes

Issues noted for patches 04, 05, 06, and 07

About issue 85429

Having information about the current mbo count can be useful in solving problems in certain situations. To display the mbo count in the stdout, add the following property to MXServer.properties and add a frequency period:
mxe.cron.Task.psdi.server.MboCountCronTask=1m

The effect of the preceding setting is that every minute a crontask fires and send a list of mbo counts to stdout using this format: "mbo count for WORKORDER: 10". Upon adding the property to the MXServer.properties file, the Maximo EAR files is rebuilt and redeployed.
Note:

This property is only be used while debugging problems, this property should be commented out during normal use. When implementing this property or commenting it out, remember to rebuild the maximo.ear file.

About issue 64899

Contact IBM Software Support to obtain the latest copy of WFDesign.exe.

About issue 86226

Before 5.2 Patch 05, the default setting for the Workorder Change Child Status checkbox was controlled via the java code. This has been changed to a database setting, to allow customers control of this checkbox. The fix has been implemented to be compatible with the behavior of the checkbox before the change. For customers wanting to default the Workorder, clear the Child Status checkbox and use a database tool such as SQL Plus or Query Analyzer to run the following command:
update maxsyscolumns2 set objectdefaultvalue=(select varvalue from maxvars where varname='STORENOAS') where tbname='WORKORDER' and name='CHANGECHILDSTATUS'

About issue 90261

Users of the Notification service solution must manually update the <Maximo Root>\jsp\commom\system\header.jsp file. After installing Maximo 5.2 Patch 05, users of the Notification application will notice a NO MATCH FOUND message listed in the JspUpdate.log file for the change relating to the jsp\common\system\header.jsp file. Use the maximo_root\JspUpdate.xml file and the fixed version of the header.jsp file that is in the maximo_root\user_files\MX52P05_files\jsp\common\system folder to manually make updates that were not performed.

About issue 033265

Users who encounter the error: "The Quantity cannot be less than zero" when performing a return in the receiving application or when copying POLines to the Invoice on a Credit type invoice, see Reference number 1263444 on the IBM Software Support Web site.

Notes on issues

143

Issues noted for patches 04, 05, 06, and 07

About issue 77689

This issue fixes the problem "The select items for transfer button lists items available at the storeroom rather than items available for transfer". Users would have to add the following statements (listed in bold letters) to the jsp/app/invissue/ selectitemsfortransferint.jsp and rebuild and redeploy ear files before they can view the 'Location' from where the item is being transferred.
<psdi:table id="invbalancesin_Table" mbosetid="invbalancesin" scope="sacontext" rowsperpage="20" tabletype="multiselect" form="mainForm" > <psdi:tablebody norowmsg="No items found."enablefilter="open"> <psdi:columndefinition description="Item" dataattribute="itemnum" sortable="true" /> <psdi:columndefinition description="Description" dataattribute="item.description" sortable="true"/> <psdi:columndefinition description="Bin" dataattribute="binnum" sortable="true" /> <psdi:columndefinition description="Lot" dataattribute="lotnum" sortable="true" /> <psdi:columndefinition description="Current Balance" dataattribute="curbal" sortable="true" /> <psdi:columndefinition description="Manufacturer Lot#" dataattribute="invlot.mfglotnum" sortable="false" /> <psdi:columndefinition description="Shelf Life" dataattribute="invlot.shelflife" sortable="false" /> <psdi:columndefinition description="Expiration Date" dataattribute="invlot.useby" sortable="false" /> <psdi:columndefinition description="Site" dataattribute="siteid" sortable="false" /> <psdi:columndefinition description="Location" dataattribute="location" sortable="false" /> </psdi:tablebody>

144

Release Notes

Issues noted for patches 04, 05, 06, and 07

Notes on issues

145

Issues noted for patches 04, 05, 06, and 07

146

Release Notes

Notices
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY 10504-1785 U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan, Ltd. 3-2-12, Roppongi, Minato-ku, Tokyo 106-8711 Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

Copyright IBM Corp. 2007, 2009

147

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation 2Z4A/101 11400 Burnet Road Austin, TX 78758 U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. If you are viewing this information softcopy, the photographs and color illustrations may not appear.

148

Release Notes

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at www.ibm.com/legal/copytrade.shtml. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Other company, product, or service names may be trademarks or service marks of others.

149

150

Release Notes