204
Version 7 Upgrade Guide IBM Maximo 6 to Version 7 Products IBM Maximo

New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

  • Upload
    others

  • View
    8

  • Download
    0

Embed Size (px)

Citation preview

Page 1: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Version 7

Upgrade GuideIBM Maximo 6 to Version 7 Products

IBM Maximo

Page 2: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Seventeenth edition, March 2013.

© Copyright International Business Machines Corporation 2007, 2013. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

NoteBefore using this information and the product it supports, read the information in “Notices” on page 197.

Page 3: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

© Copyright IBM Corp. 2007, 2013 iii

Chapter 1: Upgrade overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Standard approach to the upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Summary of upgrade tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Upgrade resources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5What the upgrade program supports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5What the upgrade program does not support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Chapter 2: Preparing to upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Installing version 7 products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Creating a test copy of your Maximo database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Updating Maximo 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Completing the Maximo 6 database information worksheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Preparing properties files for the upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Editing the maximo.properties file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Modifying the upgpoints.xml file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Evaluating version 7 reporting options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Disabling custom triggers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Preparing for new field control functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Selecting the correct regional and language option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Preparing to upgrade Maximo Enterprise Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Preparing to upgrade SAP ERP adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Preparing to upgrade to the Oracle ERP adapter 7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Preparing to upgrade Maximo for Oil and Gas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Preparing to upgrade Maximo for Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Preparing to upgrade Maximo Spatial Asset Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Preparing to upgrade Maximo for Nuclear Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Preparing to upgrade Maximo Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Preparing to upgrade Maximo Mobile Work Manager or Maximo Mobile Inventory Manager . . . . . . . . . . . 37Considerations for CCMDB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Backing up your database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Chapter 3: Upgrading the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Maximo Upgrade Utilities program process overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Verifying database integrity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Validating the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Upgrading the database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Interrupting the upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Chapter 4: Completing the upgrade process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Verifying the install.properties values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Updating the Maximo database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Reviewing your upgraded screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Performing database administration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Reviewing custom relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Reviewing table domains and crossover domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Validating upgraded restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Re-enabling audit functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Reviewing version 7 planned attribute changes in work-order-based applications . . . . . . . . . . . . . . . . . . . . . . 69

Contents

Page 4: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

iv IBM Maximo: Upgrade Guide

Reviewing IBM Global Services applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Updating statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Associating existing document types (folders) with new version 7 applications . . . . . . . . . . . . . . . . . . . . . . . . 70Adding new applications to security groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Completing the Maximo Enterprise Adapter upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Completing the SAP ERP adapter upgrade process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Completing the Oracle ERP adapter upgrade process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Upgrading Integration Composer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Completing the Maximo for Oil and Gas upgrade process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Completing the upgrade for Maximo Mobile Work Manager or Maximo Mobile Inventory Manager . . . . 148Completing the upgrade for CCMDB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Running the VarcharMultiplier utility for double-byte languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Completing the upgrade for globalized languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Appendix A: Maximo Enterprise Adapter updates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Maximo Enterprise Adapter for SAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Maximo Enterprise Adapter for Oracle Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Component name changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158External systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Queues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Endpoints and handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Integration controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Integration objects and integration points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Inbound and outbound interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163System properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166URLs for inbound HTTP and HTTPS transactions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166XML transformation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Deleted version 6 tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172New version 7 tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Appendix B: Troubleshooting the upgrade process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Bracketed terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Checking the Support Web site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Integrity checker error messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Integrity checker warning messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Upgrade validation utility error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Upgrade validation utility warning messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Upgrade utility error messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Fixing and debugging SQL errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Trademarks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198

Page 5: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

© Copyright IBM Corp. 2007, 2013 1

Upgrading from IBM Maximo 6 to version 7 products is a multistage process. You use an upgrade program to perform the central part of the upgrade process, but the full process includes tasks that you perform before and after running the upgrade program.

The upgrade program supports multiple product configurations, including Maximo Asset Management and related components and products. For information about which products and components are supported, see the Product Upgrade Availability section on the Maximo Upgrade Resources Web page.

Some sections of the Upgrade Guide apply only to specific products or configurations. If the specified product or configuration does not apply to your installation, skip that section and continue with the next one.

Standard approach to the upgrade process

The standard approach to the upgrade process is to stop the production system while the upgrade process is underway. You run several trial upgrade processes to determine the changes that are needed in your production database. The trial upgrades minimize downtime when you upgrade the production system.

To upgrade from Maximo 6 to your version 7 product or products, you perform the following standard steps:

1 Make a copy of the production database for testing the upgrade process.

2 Perform pre-upgrade tasks.

3 Run the upgrade product utilities on the copy of the database. Back up the database at each stage.

a Run the integrity checker utility. Correct any errors that are found.

b Run the validation utility. Correct any errors that are found.

c Run the upgrade utility.

4 Perform the post-upgrade tasks on the copy of the database.

5 Check the upgraded environment by testing your version 7 product that is running on the upgraded database.

Upgrade overview 1

Page 6: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Summary of upgrade tasks

2 IBM Maximo: Upgrade Guide

While you do the preceding steps, your production database is still active and accessible to end users. You have tested the upgrade process against your copy of the database.

To complete the process, perform the following steps:

1 Take the production database off line.

2 Within the production database, perform the pre-upgrade tasks.

3 Perform the changes that you made in response to errors and warnings that were generated in steps 3a and 3b of the upgrade process.

4 Run the three upgrade utilities.

5 Perform the necessary post-upgrade tasks.

Summary of upgrade tasks

The upgrade process includes the tasks listed in the following table.

Task Description

Preparing to upgrade

Installing version 7 products (page 7) You install version 7 products first because the upgrade program uses version 7 information and the upgrade utilities are included with the version 7 product.

Creating a test copy of your Maximo database (page 8)

You create a copy of the database to test the upgrade process. This test reveals the problems that you must address with the production database.

Updating Maximo 6 (page 13) You update the database to the latest fix pack that is supported by the upgrade process.

Completing the Maximo 6 database information worksheet (page 14)

You use this worksheet when you run the upgrade utilities and connect to the database.

Preparing properties files for the upgrade process (page 15)

Version 7 uses two new applications to maintain the information in the version 6 properties files. You must copy the files to upgrade the information into the new applications.

Editing the maximo.properties file (page 17) You edit the maximo.properties file to point to the version 6 database that you are upgrading.

Modifying the upgpoints.xml file (page 17) Depending on your product configuration, you edit this file.

Evaluating version 7 reporting options (page 18)

Version 7 has several reporting options.

Disabling custom triggers (page 18) If you created custom triggers, you disable them.

Preparing for new field control functionality (page 19)

If you used the version 6 Field Control add-on, you have additional steps.

Page 7: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Summary of upgrade tasks

Upgrade overview 3

Selecting the correct regional and language option (page 19)

Select the correct setting for your implementation.

Preparing to upgrade Maximo Enterprise Adapter (page 19)

If you used the Maximo Enterprise Adapter to integrate your version 6 product with other products, you have additional steps.

Preparing to upgrade SAP ERP adapter (page 23)

If you are upgrading to the SAP ERP adapter 7.1 you have additional steps.

Preparing to upgrade to the Oracle ERP adapter 7.1 (page 34)

If you are upgrading to the Oracle ERP adapter 7.1, you have additional steps.

Preparing to upgrade Maximo for Oil and Gas (page 36)

If you are upgrading Maximo for Oil and Gas, you have additional steps.

Preparing to upgrade Maximo for Utilities (page 36)

If you are upgrading Maximo for Utilities, you have additional steps.

Preparing to upgrade Maximo Spatial Asset Management (page 36)

If you are upgrading Maximo Spatial Asset Management, you have additional steps.

Preparing to upgrade Maximo for Nuclear Power (page 37)

If you are upgrading Maximo for Nuclear Power, you might have additional steps.

Preparing to upgrade Maximo Calibration (page 37)

If you are upgrading Maximo Calibration, you might have additional steps.

Preparing to upgrade Maximo Mobile Work Manager or Maximo Mobile Inventory Manager (page 37)

If you are upgrading Maximo Mobile Work Manager or Maximo Mobile Inventory Manager, you have additional steps.

Considerations for CCMDB (page 38) If you intend to use IBM Tivoli Change and Configuration Management Database (CCMDB), you have additional steps.

Backing up your database (page 44) Back up your database before running the upgrade utilities.

Upgrading the database

Verifying database integrity (page 47) You run the integrity checker utility to evaluate database properties and identify errors that prevent a database upgrade. You fix the errors in the database before proceeding.

Validating the database (page 52) You run the validation utility to check that the data is valid and can be upgraded. You correct errors before proceeding.

Upgrading the database (page 55) The upgrade utility upgrades the database.

Completing the upgrade process

Verifying the install.properties values (page 65) Check that the property values point to the correct database.

Updating the Maximo database (page 65) You run the updatedb.bat utility to ensure that the database is at the latest version.

Reviewing your upgraded screens (page 66) If you customized screens in version 6, you decide on the best path to upgrading them.

Performing database administration tasks (page 66)

Depending on which database manager you use, you might have additional steps.

Task Description

Page 8: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Summary of upgrade tasks

4 IBM Maximo: Upgrade Guide

Reviewing custom relationships (page 67) If you modified or added table relationships in version 6, you review the relationships to see if any of them use tables that do not exist in version 7. If they do, you can re-create the relationship with the Database Configuration application.

Reviewing table domains and crossover domains (page 68)

If you added table or crossover domains in version 6, you review them to see if any of the domains reference tables that do not exist in version 7. If they do, you can re-create the domains.

Validating upgraded restrictions (page 69) There are multiple types of data restrictions in version 7 and only one type in version 6. If you used data restrictions in version 6, you specify how you want them to work in version 7.

Reviewing version 7 planned attribute changes in work-order-based applications (page 69)

Version 7 has a new way of treating records in the AutoAttrUpdate table. No action is required but you should be aware of the change.

Reviewing IBM Global Services applications (page 70)

If you used field control, you have additional steps.

Updating statistics (page 70) If you use Oracle, you update statistics using the Database Configuration application.

Associating existing document types (folders) with new version 7 applications (page 70)

If you used Attached Documents in version 6, you might want to associate some of them with new applications in version 7.

Adding new applications to security groups (page 71)

Ensure that users can access new applications.

Completing the Maximo Enterprise Adapter upgrade process (page 71)

If you upgraded the Maximo Enterprise Adapter, you have additional steps.

Completing the SAP ERP adapter upgrade process (page 77)

If you are upgrading the SAP ERP adapter, you have additional steps.

Completing the Oracle ERP adapter upgrade process (page 80)

If you are upgrading the Oracle ERP adapter, you have additional steps.

Upgrading Integration Composer (page 133) Depending on the version 7 products you installed, you might have to upgrade to Integration Composer version 7.

Completing the Maximo for Oil and Gas upgrade process (page 133)

If you are upgrading Maximo for Oil and Gas, you have additional steps.

Completing the upgrade for Maximo Mobile Work Manager or Maximo Mobile Inventory Manager (page 148)

If you are upgrading Maximo Mobile Work Manager or Maximo Mobile Inventory Manager, you have additional steps.

Completing the upgrade for CCMDB (page 148)

If you use CCMDB, you have additional steps.

Running the VarcharMultiplier utility for double-byte languages (page 149)

If you use a translated double-byte language, you run this utility.

Completing the upgrade for globalized languages (page 149)

If you use a translated version of the product, you run several commands.

Task Description

Page 9: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade resources

Upgrade overview 5

Upgrade resources

Be sure that you have the latest version of the Upgrade Guide. You can find the latest version of the Upgrade Guide, as well as additional information about upgrading, at the Maximo Upgrade Resources Web page.

The IBM Maximo Support Web site provides an extensive, continually updated knowledge base on upgrade topics.

What the upgrade program supports

The version 7 upgrade program supports upgrading the following elements of your Maximo system:

All dataAny configurations that you performed with the Maximo configuration toolsData modelUser interface and presentation layerWorkflow processesData validations and defaultsIntegration definitionsEscalations

For Maximo Enterprise Adapter upgrade information for version 6 user-defined integration components, see the Maximo Enterprise Adapter – Version 6 to Version 7 Upgrade release notes at www.ibm.com/support/search.wss?q=mam71relnotes.

What the upgrade program does not support

The version 7 upgrade program does not support upgrading the following possible elements of your system:

Any changes to the Maximo database schema that were not made with the Maximo Database Configuration application.

Any changes that you made to Maximo database objects (tables, columns, indexes, and so on) that were not made with the Database Configuration application. Changes made outside of Database Configuration are not upgraded to the version 7 database.

Any database objects that you created (including stored procedures, triggers, views, and synonyms) that are dependent on Maximo database objects. The upgrade does not re-create such objects.

Customizations to Maximo code such as changes or additions to JavaTM code, Java applets, JavaScript, and HTML.

Upgrading from one database platform to another. For example you cannot upgrade from version 6 on Oracle to version 7 on DB2®.

Page 10: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

What the upgrade program does not support

6 IBM Maximo: Upgrade Guide

The installation of additional Maximo product offerings can affect the Maximo installation in several areas, including the installation source code, the database structure, database content, and license keys. For product offerings whose installation affects the database structure or content, see the Maximo Upgrade Resources Web page for information about which of those products are supported by the upgrade.

The Maximo 7 upgrade does not grant security authorizations to new applications or to new options within existing applications.

For some of the items that the upgrade program does not support, you need to complete a task before you run the upgrade program. For example, you must disable custom triggers.

Attention Changes to the database that are not made by a method that is supported by the upgrade process can produce errors during the upgrade. Failure to perform pre-upgrade tasks also can produce errors during the upgrade. Address errors that occur when you run the upgrade program so that you can complete the upgrade. Unsupported database changes or skipping pre-upgrade tasks also can result in incorrect behavior of your version 7 product after you complete the upgrade.

Page 11: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

© Copyright IBM Corp. 2007, 2013 7

Installing version 7 products

To install the latest release of Maximo Asset Management version 7 and related components and products, refer to the installation guides for the respective products. Ensure that your version 7 product has the required updates applied, but note the following items regarding updates, order of installation, and database name.

If you are upgrading a Maximo industry solution product, install the latest supported base services fix pack, install your industry solution product, and apply any Maximo hotfixes followed by any hotfixes for your industry solution.

If you are installing Maximo for Service Providers in addition to one or more industry solution products, you must install Maximo for Service Providers last.

If you are upgrading a version 6 database to run with CCMDB 7.2 or Tivoli Service Request Manager 7.2, you must install the 7.2 version of the product and then install the 7.2.0.1 fix pack.

Even if your version 7 product supports the use of a Linux or Unix administrative workstation, the upgrade tools do not. Therefore, you must install your version 7 product from a Windows administrative workstation.

If you are upgrading a Maximo Enterprise Adapter product (either for Oracle or SAP), install and update Maximo Asset Management to the latest fix pack release, apply any Maximo hotfixes, install your specific adapter, and install the latest fix packs to your adapter.

When you install the Maximo database for the version 7 product, do not name the database the same as your Maximo 6 database.

You install the version 7 files on a Microsoft Windows server. You install the application server (Oracle WebLogic Server or IBM WebSphere® Application Server) on a Microsoft Windows or UNIX server. You deploy the enterprise archive (EAR) files on the application server.

After you upgrade, the version 7 product files can be on any Windows administrative computer. The computer does not need to be a server.

As a general approach, you install the version 7 system on dedicated servers that are separate from the servers running Maximo 6. If you intend to use the same computer for your version 7 system components, see the following guidelines:

Preparing to upgrade 2

Page 12: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a test copy of your Maximo database

8 IBM Maximo: Upgrade Guide

Where to install version 7 product components

Creating a test copy of your Maximo database

You first perform the upgrade process on a test copy of your Maximo database. During the test upgrade, you make notes of any special steps or database modifications that you need to make. It is a good idea to perform a test upgrade more than once, each time using a copy of the most current production database. The upgrade process can take two days or more, depending on the size of your database.

After you have successfully upgraded one or more test copies, you repeat the process with a copy of your current production database. This upgraded database becomes your new production database.

To create a test copy of your Maximo 6 database, perform the tasks listed in the following table. Refer to the platform-specific instructions that follow the table for detailed steps.

Database-related tasks

*If you plan to implement DB2 9 for your version 7 product, upgrade your DB2 installation after you upgrade the Maximo database.

If you are connecting to an Oracle database, continue with “Creating a test copy of your Maximo database in Oracle‚" page 9. Check that your Oracle 9 version is exactly 9.2.0.8. Oracle release 9.2.0.8 corrects an issue that can cause the Maximo upgrade to fail.

ApplicationInstall on same server where Maximo 6 components reside? Comments

IBM Maximo Asset Management version 7 and its related products

No Install version 7 files on a Windows server.

WebLogic Server Yes Use a different installation folder and different port numbers.

WebSphere Application Server No Concurrent versions of WebSphere Application Server do not run on the same server.

Oracle 9.2.0.8, 10.2.0.3 Microsoft SQL Server 2005 SP3 DB2 8.2.7, 9.1.4*

Create a database instance. Create a new database. Create a database instance.

Import your Maximo 6 schema. Back up and restore the production database to the new database.

Back up and restore the production database to the new database.

Install Oracle Text and grant privileges to Maximo 6 schema owner.

Prepare the database for text indexes.

Prepare the database for text indexes.

Turn off redo log archiving. Turn on redo log archiving after you upgrade to version 7.

Change to simple recovery model. Change back to full recovery model after you upgrade.

Page 13: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a test copy of your Maximo database

Preparing to upgrade 9

If you are connecting to a Microsoft SQL Server database, go to “Creating a test copy of your Maximo database in Microsoft SQL Server‚" page 10.

If you are connecting to a DB2 database, go to “Creating a test copy of your Maximo database in DB2‚" page 11.

Creating a test copy of your Maximo database in Oracle

This section contains information about the following Oracle database-related pre-upgrade tasks:

Creating a database instance.Backing up and restoring the production database to the new database.Granting privileges to the Maximo schema owner.Turning off redo log archiving.

Creating a database Instance

Create an Oracle instance for your test database. Install Oracle Text in the new instance.

To use an existing instance, you must install Oracle Text. For more information about installing Oracle Text, see your Oracle documentation.

Use an undo tablespace rather than rollback segments.

Ensure that the database has enough temporary tablespace (for example, 3 GB with space to grow to 7 GB), and an adequate tablespace size, and that autoextend is on.

Backing up and restoring the production database to the new database

If possible, create your test database in its own Oracle instance so that you can start, stop, or shut down the database without interfering with other databases. For more information about how to create an Oracle instance and a test copy of your database, see your Oracle documentation.

For information about importing a Maximo 6 schema, go to www.ibm.com/support/docview.wss?rs=3214&uid=swg21264067.

Granting privileges to the Maximo schema owner

To grant privileges to your Maximo schema owner, complete the following steps:

1 Log in to the database as the database system user, SYSTEM.

2 Run the following command from an SQL prompt:

Grant Execute On ctxsys.ctx_ddl to maximo

Turning off the redo log archiving

Turn off redo log archiving before you upgrade. If the upgrade fails, recover from a full backup. You cannot use log recovery.

Page 14: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a test copy of your Maximo database

10 IBM Maximo: Upgrade Guide

Creating a test copy of your Maximo database in Microsoft SQL Server

This section contains information about the following Microsoft SQL Server database-related pre-upgrade tasks:

Preparing a Microsoft SQL Server instance.Changing to simple recovery model.Deleting statisticsReassociating user accounts.

Preparing a Microsoft SQL Server instance

Full-text search is an option that you must install when you install Microsoft SQL Server 2005 SP3. To determine if full-text search is on your existing Microsoft SQL Server database, complete the following steps:

1 Open SQL Query Analyzer from the Tools menu.

2 In the top query window, type the following command:

select FULLTEXTSERVICEPROPERTY ( 'IsFulltextInstalled' )

If you did not install full-text search (the resulting value is zero), install it now.

To install the full-text search option after you install SQL Server, see your SQL Server documentation.

Changing to simple recovery model

To change to simple recovery model, see the SQL Server Enterprise Manager documentation.

Deleting statistics

The upgrade process cannot update a record that has statistics associated with it. The upgrade process reads statistics as indexes.

To delete statistics, see the SQL Server Enterprise Manager documentation.

Reassociating user accounts

If you are moving the database to a different server, you also must reassociate user accounts.

For information about reassociating user accounts, go to www.ibm.com/support/docview.wss?rs=3214&uid=swg21262275.

Page 15: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a test copy of your Maximo database

Preparing to upgrade 11

Creating a test copy of your Maximo database in DB2

This section contains information about the following DB2 database-related pre-upgrade tasks:

Creating and configuring a test database. Binding the database schema on the test database.Backing up and restoring the production database to a new database.

Creating and configuring a test database

Create a new instance for your test database to keep your production database isolated.

Use the DB2 Control Center to generate a script of tablespaces, buffer pools, and authorizations of your source database. The script will be used as a reference when you create your target database.

To create the data definition language (DDL) and configurations script:

1 Navigate to your current production database. This is the “source” database.

2 Right-click and select Generate DDL.

3 On the Statement tab, clear the Database objects check box and select Gather configuration parameters.

4 On the Object tab, select All Users and All Schemas from the drop-down lists.

5 Select Generate, and save the resulting DDL and configurations script.

6 From your target system or database instance, use the CREATE DATABASE command to create the target database. You can also use the DB2 Control Center to create the new database in the target instance.

7 Create additional buffer pools and tablespaces so that all the tablespaces from the source database exist in the target database. There are two ways that you can do this:

Use the DB2 Control Center and reference the DDL and configurations script that you created.Edit the DDL and configurations script to reference the target instance and containers, then run the script.

You can change the storage options. You probably need to change the container names. But ensure that you create the tablespaces from the source database.

8 Apply the source database configurations that are included in the DDL and configurations script.

For the upgrade, use circular logging and create as many primary logs as possible. The log settings for the test database might differ from the source database log settings. See the DB2 information center for your version of DB2 for more information about setting up logging.

Page 16: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Creating a test copy of your Maximo database

12 IBM Maximo: Upgrade Guide

Binding the database schema on the test database

To bind the database schema on the new test database:

1 Display a command prompt.

2 At the command prompt, type the following lines. Verify that IBM\SQLLIB\bnd is the correct folder.

cd c:\IBM\SQLLIB\bnd <Enter>

set DB2DBDFT=name_of_database_that_you_created <Enter>

Db2cmd <Enter>

db2 connect to name_of_database_that_you_created <Enter>

db2 bind db2schema.bnd <Enter>

db2 bind @db2cli.lst clipkg 4 <Enter>

Backing up and restoring the production database to the new database

To back up and restore your production database to the new test database:

1 Use the DB2 Control Center or the BACKUP DATABASE command to back up your test database. Make the backup an off-line backup.

2 If necessary, copy the backup image to the target database system.

3 Perform a redirected restore into the target database.

See the DB2 Command Guide and the DB2 information center for more information about doing a redirected restore.

Performing a redirected restore

Performing a redirected restore is a three-step process:

Use the RESTORE DATABASE command.Assign target containers to tablespaces.Restore the data.

Using the RESTORE DATABASE command

Use the RESTORE DATABASE command with the REDIRECT option. This statement specifies the source database to restore and the target database.

Assigning target containers

Assign the target containers to the tablespaces that are being restored. Because the source database container definitions are likely different from the target database definitions, you use the SET TABLESPACE CONTAINERS command to assign target containers for each tablespace.

You must obtain the tablespace IDs from the source database and map them to the tablespaces of the target database.

For example, consider the following SET TABLESPACE CONTAINERS statement:

db2 set tablespace containers for 2 using (path 'userspace1.0', path 'userspace1.1')

Page 17: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Updating Maximo 6

Preparing to upgrade 13

The “2” in the statement is the tablespace ID for USERSPACE1 of the source database. To determine the tablespace ID, run the LIST TABLESPACES command while you are connected to the source database.

The containers that are referenced in the statement are the containers that are defined for the tablespace USERSPACE1 of the target database, or the tablespace that you want to redirect to.

Restoring the data To restore the data to the test database, use the RESTORE DATABASE command with the CONTINUE option.

Because DB2 stores its authorities and privileges within the database, you should not have to issue grants after you restore the data. However, if you are using SERVER authentication and the target server is different from your production server, the user profile that is referenced in the database security tables might need to be created on the target system.

Updating Maximo 6

You first must determine your current Maximo 6 version and release. To check your Maximo version and release, click Help > About.

The version 6 requirements change with each Maximo 7 release following a new version 6 release. For the time between the latest version 6 patch release and the subsequent Maximo 7 release, the latest version 6 patch is not supported by the Maximo 6 to 7 upgrade. During this time, PowerUpdate cannot be used.

Updating from versions 6.0 and 6.1

IMPORTANT: Before you update, review the other sections in this chapter for any restrictions or version requirements that might apply to specific products, and review the information on the Maximo Upgrade Resources web page for additional version and fix pack requirements.

If you are on any patch level of Maximo 6.0 or on Maximo 6.1, you must first order and install Maximo 6.2 media:

1 Go to the Maximo Upgrade Resources Web page at www.ibm.com/support/docview.wss?rs=3214&uid=swg21266217.

2 Open and complete the Maximo Upgrade Request Form.

In the For Replacements/Additional Media section, enter the following information:

Maximo version: Your current installed version and release of Maximo. Media Requested: Maximo 6.2.

3 Save and submit the request form by e-mail.

4 When you receive the media, install Maximo 6.2.

5 Download and install the latest upgrade utilties, as described on the Maximo Upgrade Resources web page.

Page 18: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo 6 database information worksheet

14 IBM Maximo: Upgrade Guide

Updating from version 6.2 or later

You must be on the latest fix pack of Maximo 6.2 that supports the upgrade process.

IMPORTANT: Before you update, review the other sections in this chapter for any restrictions or version requirements that might apply to specific products, and review the information on the Maximo Upgrade Resources web page for additional version and fix pack requirements.

Completing the Maximo 6 database information worksheet

Complete the following worksheet by recording names and values from the Maximo 6 test database that you created. Refer to this information when you use the Login tab of the Maximo Upgrade Utilities.

You might need to edit the maximo.properties file to specify the information that you record here so that the correct information about the database to upgrade appears on the Login tab. Use a text editor to edit the maximo.properties file.

Page 19: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing properties files for the upgrade process

Preparing to upgrade 15

Maximo 6 database information

Preparing properties files for the upgrade process

Maximo 6 is configured by using properties files:

maximo.propertiesdoclink.propertiessetting.propertieslogging.propertieswebclient.properties

The properties that were configured in version 6 by using the properties files are managed by two applications in version 7:

System PropertiesLogging

The System Properties application manages the properties that were in the version 6 maximo.properties, doclink.properties, setting.properties, and webclient.properties files. The Logging application manages the properties that were in the version 6 logging.properties file.

You can use the upgrade process to upgrade the contents of the Maximo 6 properties files into the version 7 database so that they can be managed by the System Properties and Logging applications.

Database information

Database server name

Database port number:

Oracle: 1521 (default)Microsoft SQL Server: 1433 (default)DB2: 50000 (default)

Database name

Tablespace name

Temp tablespace name

Database/schema owner

Database owner name and password

Maximo administration information

Maximo administrator For example, SYSADM or MAXADMIN.

User name to create new Maximo users

Default is DEFLTREG.

Password

Page 20: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing properties files for the upgrade process

16 IBM Maximo: Upgrade Guide

The Maximo 6 properties files are located in the following directory:

Maximo_root\applications\maximo\properties

If you want to upgrade the properties files, complete the following steps for each file that you want to upgrade:

1 Create a copy of the properties file. Name the copied file with the specific file name that is shown in the following Properties files table.

For the webclient.properties file, copy the contents of the file and paste them into upgmaximo.properties.

2 Place the copied file in the following folder:

Maximo_root\tools\maximo\classes\psdi\upgrade\V600

If you use a database manager other than Oracle, update the maximo.properties file to ensure that the mxe.db.systemdateformat and mxe.db.format.nullvalue properties are set properly for the target database. The installation process will fail if these properties are not updated.

Properties files

You can edit the upgname.properties files that you created for upgrading. For example, you might want to delete some properties that you do not want to be upgraded.

After you create and edit the upgname.properties files, place them in the following folder:

Maximo_root\tools\maximo\classes\psdi\upgrade\V600

Maximo 6 properties file Action to create file for upgrading

maximo.properties Copy maximo.properties and save as upgmaximo.properties

doclink.properties Copy doclink.properties and save as upgdoclink.properties

setting.properties Copy setting.properties and save as upgsetting.properties

webclient.properties Copy contents of webclient.properties and paste into upgmaximo.properties

logging.properties Copy and save as upglogging.properties

setting_two-letter_language_code.propertiesFor example, settingFR.properties

Copy and save as upgsetting_two-letter_language_code.properties For example, copy and save as upgsettingFR.properties

Page 21: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Editing the maximo.properties file

Preparing to upgrade 17

Choosing not to upgrade properties files

If you do not want the Maximo Upgrade Utilities to upgrade your properties files, do not create any upgname.properties files. When the upgrade process runs, you will receive warning messages that certain upgname.properties files were not found. You can ignore the messages if you do not want to upgrade properties.

If you choose not to upgrade the properties files, you need to use the System Properties application and the Logging application in your version 7 product. Use System Properties and Logging to create or modify the properties that you need to configure for your environment.

Editing the maximo.properties file

Edit the maximo.properties file on the version 7 administrative workstation to point to the database you are upgrading. For example, in the following line, edit mydomain and maximo to specify the computer and database of your version 6 instance:

mxe.db.url=jdbc:oracle:thin:@mymachine.mydomain.com:1521:maximo

If the database schema name has changed, the following properties should also be updated with the new schema name in maximo.properties:

mxe.db.schemaowner=[database schema name]

mxe.db.user=[database schema name]

mxe.db.password=[database schema password]

Modifying the upgpoints.xml file

The upgpoints.xml file contains information about which products the upgrade utility will attempt to upgrade. You might need to edit the upgpoints.xml file, depending on the add-on products that you have installed and whether the Maximo Upgrade Utilities currently support upgrading all of your installed products.

See the Maximo Upgrade Resources Web page for information about which add-on products are currently supported by the Maximo Upgrade Utilities.

Even if the upgrade process does not support all of your installed products, you might want to test the upgrade process and the Maximo Upgrade Utilities. You can modify the upgpoints.xml file to specify which add-on products the upgrade utility should not attempt to upgrade.

You modify the upgpoints.xml file by commenting out any line that references an installed add-on product that is not yet supported by the Maximo Upgrade Utilities. You comment out a UPGPOINT line so that the upgrade utility will not check the database for the presence of the product referenced in that line.

Page 22: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Evaluating version 7 reporting options

18 IBM Maximo: Upgrade Guide

Example

You have installed version 6 of IBM Maximo for Transportation. The upgrade process does not yet support upgrading Maximo for Transportation to version 7. But you want to test the Maximo Upgrade Utilities on core Maximo 6. You want the upgrade process to ignore Maximo for Transportation. In the upgpoints.xml file, you need to comment out the UPGPOINT line that references Maximo for Transportation.

The following segment from the upgpoints.xml file shows the UPGPOINT line for Maximo for Transportation in its default state, before it is edited:

<UPGPOINT maxvar="DBTRANSPORTATION" metaformat="DBTRANSPORTATION_MetaFormat.sql" metadoc="DBTRANSPORTATION_MetaDoc.xml" callouts="DBTRANSPORTATION_AppCallOutList.xml" upgmessages="" promptfilename="dbtransportation"></UPGPOINT>

The following segment shows the commented-out UPGPOINT line after you edit the file:

<!--<UPGPOINT maxvar="DBTRANSPORTATION" metaformat="DBTRANSPORTATION_MetaFormat.sql" metadoc="DBTRANSPORTATION_MetaDoc.xml" callouts="DBTRANSPORTATION_AppCallOutList.xml" upgmessages="" promptfilename="dbtransportation"></UPGPOINT>-->

Note the addition of “<!--” at the beginning of the UPGPOINT tag and the addition of “-->” at the end of the tag.

Evaluating version 7 reporting options

In version 7, the following reporting options are available:

Business Intelligence Reporting Tool (BIRT). BIRT is the embedded reporting tool for version 7 products.Cognos® Reporting, through integrationBusiness Objects Crystal Reports, through integration.External report integration (ERI), which enables integration from your version 7 product to the reporting tool of your choice.

Evaluate your business reporting needs and the skill sets that are available to you to determine the reporting option that is best for you.

Disabling custom triggers

Disable all custom triggers that exist on any table in your Maximo 6 database, including Syclo triggers.

Page 23: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing for new field control functionality

Preparing to upgrade 19

Preparing for new field control functionality

The features provided by the version 6 Field Control add-on are incorporated into the core features of version 7 products. If you used the version 6 Field Control add-on, you must make database modifications before running the upgrade utilities. See the following tech note for instructions: Field Control and Domains, Data Restrictions, Conditional UI, Conditional Application Options, and Conditional Domains.

Selecting the correct regional and language option

You specify the correct installation language in the operating system local settings.

1 From the Control Panel, select Regional and Language Options.

2 Ensure that the Regional and Languages Options tab and the Advanced tab both reflect the correct language.

Preparing to upgrade Maximo Enterprise Adapter

The following list provides an overview of the pre-upgrade tasks for Maximo Enterprise Adapter.

Identifying the alternate keys in the integration objects

Registering the Maximo business object attribute setting restrictions

Reconfiguring multiple integration points in the integration objects

Reconfiguring multiple outbound integration points in the interfaces

Processing integration transactions

Reconfiguring integration controls and interfaces

Reconfiguring interface processing rules in inbound integration points

Reconfiguring version 6 XML schemas

If you are upgrading the Maximo Enterprise SAP ERP adapter or the Maximo Oracle ERP adapter (sections that follow), you must still complete the Preparing to upgrade Maximo Enterprise Adapter section. Ensure that the configurations you specify in each section are compatible.

Identifying alternate keys in the integration objects

In version 6, several tables in Maximo Enterprise Adapter implemented and controlled the alternate key capabilities of Maximo business objects. Maximo 6 also supported the specification of alternate keys outside the business object

Page 24: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade Maximo Enterprise Adapter

20 IBM Maximo: Upgrade Guide

definition. It was possible to register different alternate keys to the same Maximo business object by using different integration objects.

In version 7, alternate key capabilities are only in the business-object definition. Each business object can have only one alternate key. You can define the alternate keys in the Database Configuration application.

To avoid upgrade processing errors that are caused by different alternate keys that are registered to the same Maximo business object:

1 Open the Maximo 6 Integration Objects application.

2 Select the integration objects that include the same Maximo business object.

3 Identify the alternate key that is used by the Maximo business object.

4 Register identical alternate keys to the Maximo business objects in all the identified integration objects.

Registering the Maximo business object attribute setting restrictions

In version 6, several tables in Maximo Enterprise Adapter implemented and controlled the attribute setting restrictions of Maximo business objects. Maximo 6 also supported the specification of setting restrictions outside the business-object definition. It was possible to register different alternate keys to the same Maximo business object by using different integration objects.

In version 7, setting restrictions are exclusive to the business-object definition. The setting restriction that is associated with each Maximo business-object attribute definition determines whether integration processing can update any data that is associated with the attribute. You can define the setting restrictions in the Database Configuration application.

To avoid upgrade processing errors that are caused by different setting restrictions that are registered to the same Maximo business object:

1 Open the Maximo 6 Integration Objects application.

2 Select the integration objects that include the same Maximo business object.

3 From the Select Action menu, select Inbound Setting Restrictions.

4 Identify the Maximo business-object setting restrictions.

5 Register identical setting-restriction parameters to the Maximo business objects in all the identified integration objects.

Reconfiguring multiple integration points in integration objects

In version 6, integration objects can have multiple inbound and outbound integration-point definitions. In version 7, object structures do not support the concept of inbound or outbound integration points. Object structures provide

Page 25: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade Maximo Enterprise Adapter

Preparing to upgrade 21

processing capabilities that are equivalent to one inbound and one outbound integration point.

To avoid upgrade processing errors that are associated with integration objects and multiple inbound and outbound integration points, you must delete the multiple integration points from your integration-object definitions. The integration object can have only one inbound integration point or one outbound integration point. You can view the existing integration points for an integration object in the Integration Objects application.

You have the option of reconfiguring the integration points that are marked for deletion. To reconfigure the integration points:

1 Create an integration object for each inbound and outbound integration point that is marked for deletion.

2 Create an interface for each new integration object.

3 If any processing rules are based on the original integration object and integration-point definition, you must re-create these rules and associate the rules with the integration object definitions.

4 Add the new interface to the appropriate external system.

Reconfiguring multiple outbound integration points in interfaces

In version 6, integration interfaces can have multiple outbound integration points. In version 7, publish channels do not support the concept of outbound integration points. Object structures provide processing capabilities that are equivalent to one outbound integration point.

To avoid upgrade processing errors that are associated with integration interfaces and multiple outbound integration points, you must delete the multiple outbound integration points from your integration-interface definitions. The interface definition can have only one outbound integration point.

You have the option of reconfiguring the integration points that are marked for deletion. To reconfigure the integration points:

1 Create an outbound interface for each outbound integration point that is marked for deletion.

2 Add the integration object that is associated with the outbound integration point as the primary integration object in the new outbound interface.

3 If any processing rules are based on the original integration object and outbound integration point definition, you must re-create these rules and associate the rules to the new integration-object definitions.

4 Add the new interface to the appropriate external system.

Processing integration transactions

Queues Before you perform the upgrade, you must ensure that all messages that are in the inbound and outbound queues are processed. All messages include messages that

Page 26: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade Maximo Enterprise Adapter

22 IBM Maximo: Upgrade Guide

encountered an error. Data in the Java Message Service (JMS) queues is not migrated from version 6 to version 7. You can check your error directory for messages that encountered an error.

Interface tables You can identify unprocessed inbound interface-table transactions by viewing the MXIN_INTER_TRANS table. Unprocessed interface-table transactions are present when records exist in the MXIN_INTER_TRANS table. Unprocessed transactions are not processed when you upgrade to version 7. You must complete the processing in version 6, or delete the rows from this table. You also must ensure that all outbound interface-table transactions have been processed by your external system.

Reconfiguring integration controls and interfaces

In version 6, interface controls are registered at the adapter level. Duplicate names and different control types or domain values are permitted when the names are unique within the adapter. In version 7, integration controls are registered at the system level.

The upgrade program cannot combine duplicate integration control values when the controls do not share the same type value or the domain value. In both situations, the upgrade program deletes one of the duplicate integration controls. You must then configure and associate the remaining integration control with either an enterprise service or a publish channel.

In version 6, interfaces are registered at the adapter level. Duplicate names are permitted when the names are unique within the adapter. In version 7, enterprise services and publish channels are registered at the system level.

All version 6 interface names must be unique across adapters so that the upgrade program can run successfully. To avoid upgrade processing errors, you must delete the duplicated interfaces.

Integration controls You have the option of reconfiguring the integration controls that are marked for deletion. To reconfigure the integration controls:

1 Create an integration control for each integration control with a duplicated name.

2 If any processing rules are based on the original integration control, you must re-create the rules and associate the rules with the integration control definitions.

Interfaces You have the option of reconfiguring the interfaces that are marked for deletion. To reconfigure the interfaces:

1 Create an interface and enter a new name.

2 Create any processing rules that apply to the interface.

3 Add the new interface to the appropriate external system.

Page 27: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade SAP ERP adapter

Preparing to upgrade 23

Reconfiguring interface processing rules in inbound integration points

In version 6, you can specify processing rules for any inbound integration point that is registered to an interface. In version 7, you can specify rules only for the primary object structure in an enterprise service. The upgrade utility deletes any interface processing rules that are registered to additional integration points.

If your integration scenarios require processing rules:

1 Identify the interfaces that have multiple inbound integration points and rules, other than the rules that are supported by the interface integration object.

2 Create an interface for each of the integration points that you want to maintain after the upgrade.

3 Associate one inbound integration point with the new interface.

4 Create the processing rules that are associated with that particular integration point.

Regenerating version 6 XML schemas

If your enterprise services or publish channels continue to use the version 6 XML files in an external schema definition, you must generate the XML schemas. Generate the XML schemas before you start the upgrade process. When the upgrade process is complete, you no longer can generate the version 6 XML schemas. In version 7, you can only generate the version 7 XML schemas.

Preparing to upgrade SAP ERP adapter

The following list provides an overview of the pre-upgrade tasks for the SAP ERP adapter:

Stopping transactions between SAP and Maximo

Updating the release 6.2 customizations

Configuring the SAP Process Integration System Landscape Directory

Importing integration objects

Configuring integration objects

Configuring integration scenarios

Adjusting interface determination objects manually

Processing SAP XML files in SAP Exchange Infrastructure to Maximo 6.2

Resolving SAP integration transactions in Maximo 6.2

Page 28: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade SAP ERP adapter

24 IBM Maximo: Upgrade Guide

Backing up Maximo 6.2 database

Applying the latest Maximo 6.2 patches

Applying the latest SAP ERP 6.2 adapter patches

Backing up the Maximo Database

Ensure that the configurations you specify in this section are compatible with those you specified in “Preparing to upgrade Maximo Enterprise Adapter‚" page 19.

Stopping transactions between SAP and Maximo

To prevent the SAP ERP adapter from sending transactions to Maximo while you upgrade, you must stop all transactions between SAP and Maximo before you begin to upgrade.

Updating the release 6.2 customizations

A major part of the upgrade process is planning and implementing the transfer of customizations from release 6.2 to release 7.1 of the SAP ERP adapter.

You must review your custom release 6.2 interfaces, processing classes, and mappings to determine whether the release 7.1 database columns, interfaces, enterprise services, publish channels, and integration controls affect them.

After you upgrade if you have any customizations in FI invoice or invoice variances you must move them to the MM invoice enterprise service.

For more information about the release 7.1 features, see the IBM Maximo Enterprise Adapter System Administrator Guide for SAP ERP 6.0 Adapter.

Configuring the SAP Process Integration System Landscape Directory

You must perform configuration tasks in the SAP Process Integration System Landscape Directory. The System Landscape Directory contains all the information about the information technology landscape of a system.

You must have system administrator rights and authorities to perform the SAP Process Integration configuration.

Configuring the System Landscape Directory

The SAP Process Integration is a set of applications that you use to configure the components of the integration in SAP. This configuration lets SAP and Maximo exchange information.

The first Process Integration tools application that you must configure is the System Landscape Directory. The system landscape is logically divided into the following parts:

Technical landscape: computers, hardware, systems, servers, and so on

Page 29: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade SAP ERP adapter

Preparing to upgrade 25

Business landscape: logical definitions and configurations

Logging on to the System Landscape Directory

Before you configure the System Landscape Directory, you must log on to the http://server_name:http_port/rep/start/index.jsp.

1 Select the System Landscape Directory link.

2 Type the System Landscape Directory user ID and password, and then click Log on.

Adding Maximo to the System Landscape Directory software catalog

The first task in the System Landscape Directory is to register your Maximo integration software with SAP. To do so, you add a new product to the software catalog.

The software catalog contains the information for software products installed on the SAP system. You must add the SAP ERP adapter to the catalog.

To add the SAP ERP adapter to the Process Integration software catalog:

1 In the System Landscape Directory home window, select the Products link.

2 In the Software Catalog window, click New Product Version.

3 In the Add Non-SAP Product to Software Catalog window, complete the Name, Vendor, and Version fields as shown in the following table:

4 Click Create.

5 In the Name field of the Add New Non-SAP Software Unit window, type IBM Maximo Enterprise Adapter.

6 Click Create.

7 In the Add Software Component to Non-SAP Product window, complete the fields as shown in the following table. Type the values exactly as shown in the table. When you import the Maximo software component version, it must match the values that you type here.

Field Value

Name IBM Maximo Enterprise Adapter for SAP

Vendor ibm.com

Version 7.1

Field Value

Name (must be in uppercase) IMEA-INTEGRATE

Version IMEA71-mySAPERP2005

Page 30: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade SAP ERP adapter

26 IBM Maximo: Upgrade Guide

8 Create the catalog entry by clicking Create.

9 Return to the System Landscape Directory home window by clicking the Home link.

Importing integration objects

You must copy a file of integration objects, and then import the integration objects in the Integration Repository.

Copying the integration objects file from the xi-repository folder

Before you complete the configuration tasks in the integration repository, you must copy a file from the SAP ERP adapter xi-repository folder to your SAP process integration system.

To copy the integration objects file:

Copy the following file from the \\MAXIMO\SAP-Side\xi-repository folder on the Maximo application server (n = a sequential number):

XI3_0_IMEA-INTEGRATE_IMEA71-mySAPERP2005_of_ibm.com_n.tpz

Copy the file to the following folder on the process integration server (SID = the SAP system number):

\\usr\SAP\SID\SYS\global\xi\repository_server\import

This file contains all the process integration objects that the SAP ERP adapter integration needs.

If you downloaded a fix pack when you installed the SAP ERP adapter, the fix pack might add one or more additional files to the \\MAXIMO\SAP-Side\xi-repository folder on the Maximo application server. A file in the fix pack has a name such as the following example:

XI3_0_IMEA-INTEGRATE_IMEA71-mySAPERP2005_of_ibm.com-objs_x.tpz

If the file is part of a fix pack, the file name contains the string objs. The file contains the objects that are fixed in the fix pack. Copy the files by using the same method and location described previously in step 1.

Importing objects into the integration repository

After you copy the integration objects file to the process integration server, you must import the integration objects into the process integration repository.

To import integration objects:

1 In the XIQ: Process integration Tools home window, click Integration Repository.

2 In the logon window, log on to the Integration Builder.

Page 31: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade SAP ERP adapter

Preparing to upgrade 27

3 In the Design: Integration Builder window, select Tools > Import Design objects.

4 In the Choose Import Source window, select the following install file from the list:

XI3_0_IMEA-INTEGRATE_IMEA71-mySAPERP2005_of_ibm.com_x.tpz

Click OK.

5 In the Import design objects window, click Import. The import process uploads the interface and message mapping, design objects, interfaces, structures, and so on, that you previously copied from the installation CD.

6 If you downloaded a fix pack during your installation of the SAP ERP adapter, repeat the import process (steps 4 - 6) for all fix pack files in the \\MAXIMO\SAP-Side\xi-repository folder on your Maximo application server. The fix pack files have names such as XI3_0_IMEA-INTEGRATE_IMEA71-mySAPERP2005_of_ibm.com-objs_n.tpz. The n immediately before the.tpz extension in the file name is replaced in the actual file name with a number. If you have multiple fix pack files, you must begin with the lowest sequential number.

This process can take several hours.

On the Objects tab of the repository, you can expand IMEA-INTEGRATE to view the imported objects.

Configuring integration objects

After you register the integration software in the System Landscape Directory and import the integration objects, you must configure the integration objects that you need for exchanging data between SAP and Maximo.

You configure integration objects in the process integration directory application.

To log on to the Integration Directory:

1 In the XIQ: Process integration Tools home window, select the Integration Directory link in the Configuration: Integration Builder module.

2 Log on as the Integration Builder user.

Configuring integration scenarios

Integration scenarios are templates that are included with the integration.

You select the integration scenarios that are specific to your integration requirements. You can use these scenarios as a basis for configuring the information and details of your integration between Maximo and SAP.

You complete the following tasks to configure each scenario:

1 In the component view of the integration repository, assign business system services to scenario template component actions.

Page 32: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade SAP ERP adapter

28 IBM Maximo: Upgrade Guide

2 Configure connections.

3 Generate the scenario.

You can create custom configurations by building transaction flows, using every object, message type, and so on. To save configuration time, you can review the scenario templates provided with the integration to decide if you can use them for your customization requirements.

Selecting integration scenarios

The first task when configuring integration scenarios is to transfer a scenario from the Integration Repository.

To select an integration scenario:

1 In the Configuration: Integration Builder window, from the Tools menu, select Transfer Integration Scenario from Integration Repository.

2 In the Transfer Integration Scenario from the Integration Repository window, open the selection list of the Name field. The Select Integration Scenario from Integration Repository Search Result window opens, showing the selection list for integration scenario names. The list shows all the integration scenarios in the Integration Repository.

Scenarios for the integration between Maximo and SAP begin with the MX71_ prefix.

3 Select a scenario to configure from the list. For example, select MX71_M2S_WorkOrder.

4 Return to the Transfer Integration Scenario from the Integration Repository window by clicking OK.

5 Open the Create Configuration Scenario section of the wizard by clicking Continue.

The default scenario name appears in the Configuration Scenario field. Use the default naming convention, which matches the scenario name in the repository.

6 Click Finish.

Configuring the scenario You must configure an integration scenario in the Integration Scenario Configurator.

Assigning services to templates in the scenario

After you assign services (that you defined in the System Landscape Directory) to each template that has one or more actions.

In the Component View section of the configurator, three templates are shown. Two of them contain process boxes. These boxes are called actions.

In the example of the MX71_M2S_WorkOrder scenario, you assign services to the actions in the SAP Enterprise and Maximo Enterprise Templates.

The SAP scenario templates are always assigned to the SAP business system or service.

Page 33: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade SAP ERP adapter

Preparing to upgrade 29

The Maximo scenario templates always are assigned to the Maximo business system or service.

To assign services to a scenario template:

1 In the Integration Scenario Configurator window, right-click the SAP Enterprise Template, and then click Assign Service.

2 In the Assign Services to Application Components window, click the Plus icon to add a service.

3 Open the Service value list. Select Service for Business Systems.

4 In the Select Services for Business Systems window, select a Service from the list.

5 Click OK.

6 To assign a service to the SAP template, click Assign. In the Component View, an icon appears in the template heading to show that a service has been assigned.

7 To assign services to the Maximo template, repeat steps 1 through 6 for the Maximo Enterprise template, assigning the Maximo service to the template.

Generating scenarios You must generate the integration scenario in the Generate step of the component view of the Integration Scenario Configurator.

To generate the integration scenario:

1 Click 4. Generate.

2 In the Create Configuration Objects window, change the following settings:

General: Select Generation

Scope of Generation: Clear the Sender/Receiver Agreement check box.

3 Click Start. The generation log file view shows your configuration entries. You can use this view to check for errors.

4 Expand the Notes for Using the Log section for help text.

5 Save or close the log file.

6 Close the Integration Scenario Configurator and confirm that you want to save your changes.

7 Click Apply. The Configuration Scenario Objects tab shows the objects that you just created.

So far, you have created the receiver determination and the interface determination.

To review configuration information for objects you created, select the tree view Objects tab, expand Receiver Determination and Interface Determination, and double-click the objects created to see configuration information in the right pane.

Page 34: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade SAP ERP adapter

30 IBM Maximo: Upgrade Guide

Continue selecting and configuring the scenarios that apply to your integration requirements. Do so for transactions that go from SAP to Maximo, and for transactions that go from Maximo to SAP.

Repeat this configuration process for each scenario you will use in your integration.

Adjusting interface determination objects manually

The next set of configuration tasks is to adjust the interface determination objects manually. You edit the expressions that define the conditions for how the interfaces handle transactions between SAP and Maximo.

You must configure the following interface determination objects (replace SAP system and Maximo with the values that you use for both systems):

SAP systemSAP_MATERIALS_TOMXMaximo

MaximoMXINVOICE_TOSAP05SAP system

MaximoMXWODETAIL_TOSAP05SAP system

SAP systemSAP_GM_TOMXMaximo

Distributing material master data from SAP to Maximo

The Maximo interface that SAP will send a Material Master transaction to is identified by conditions that you apply to the object.

Distributing material master data from SAP to Maximo uses the following interface determination object (SAP system and Maximo are the values that you use for both systems):

SAP systemSAP_MATERIALS_TOMXMaximo

The interface that is called depends on the data that is sent, based on conditions set in the interface determination object. For example, one condition for distributing data might be to call the reservation interface only if a work order reservation is attached.

The SAP ERP adapter uses three material master data transactions:

ItemInventoryInvBalances

To define the conditions for distribution of material master data from SAP to Maximo:

1 In the Configuration: Integration Builder window, click the Objects tab, and expand Interface Determination.

2 Double-click the SAP_MATERIALS_TOMX interface determination. For this sender interface, the possible Maximo receiver inbound interfaces appear on the right in the Configured Inbound Interfaces section of the window.

Page 35: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade SAP ERP adapter

Preparing to upgrade 31

3 Change to edit view by clicking the pencil icon.

4 Open the condition editor by clicking the Condition field. Use the condition editor to add the conditions. The following tables show the values that you must configure for each interface determination object. If the condition requires a namespace prefix (p1), add the prefix and namespace information to the list of namespaces at the bottom of the Condition Editor.

S2M_MaterialMaster, Material Master from SAP to Maximo

S2M_MaterialMovement, Material Movements from SAP to Maximo

M2S_Invoice, Invoice from Maximo to SAP

SENDER interface

SAP_MATERIALS_TOMX

RECEIVER interface Condition

MXITEM_FRSAP05 //IDENT=XII

MXINVENTORY_FRSAP05 //WERKS~+*

MXINVBAL_FRSAP05 //LGORT~+*

SENDER interface

SAP_GM_TOMX

RECEIVER interface Condition

MXINVISSUE_FRSAP05 //IDENT=XISU

MXRECEIPT_FRSAP05 //IDENT=XRCVI

SENDER interface

MXINVOICE_TOSAP05

RECEIVER interface Condition

SAP_INVOICEMM_TOSAP //p1:SAP_APTYPE=MM

SAP_INVOICEFI_TOSAP //p1:SAP_APTYPE=FI

Additional information

prefix = p1

namespace = http://www.ibm.com/maximo

Page 36: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade SAP ERP adapter

32 IBM Maximo: Upgrade Guide

M2S_Reservation, Reservation from Maximo to SAP

5 Click Save. The saved configured inbound interfaces now appear with conditions.

Deleting Maximo 6.2 related interface determinations

After configuring the Maximo 7.1 scenarios, some interface determinations will have the existing Maximo 6.2 interface and the installed Maximo 7 interfaces. The Maximo 6.2 receiver interfaces must be deleted.

The following interface determinations must be modified:

Sender-Service = SAP systemSender-Interface = starting with ‘SAP_’Receiver Service = Maximo system

Processing SAP XML files in SAP Exchange Infrastructure for Maximo 6.2

Interface messages that are queued in SAP Exchange Infrastructure for Maximo 6.2 must be processed before you upgrade.

Resolving SAP integration transactions in Maximo 6.2

To complete any SAP integration related transactions in Maximo, perform the following:

1 Resolve any errors on transactions that you want to send to Maximo.

2 Complete any open transactions in Maximo that you want to send to SAP.

Activating the change list

To switch the integration from Maximo 6.2 to Maximo 7.1 activate the change list.

You have completed the installation and basic configuration of the SAP ERP adapter.

For additional configuration and reference information, see the IBM Maximo Enterprise Adapter for SAP ERP 6.0 System Administrator Guide.

SENDER interface

MXWODETAIL_TOSAP05

RECEIVER interface Condition

SAP_WO_TOSAP

SAP_RESERVATION_TOSAP //p1:INVRESERVE/@action=Add

Additional information

prefix = p1

namespace = http://www.ibm.com/maximo

Page 37: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade SAP ERP adapter

Preparing to upgrade 33

Backing up the Maximo 6.2 database

To prevent accidental loss or corruption of data, back up the following data:

Maximo databaseMaximo directory and all subdirectoriesCustomized user exitsAdditional customizations that you want to use after you upgrade

Applying the latest Maximo patches and fix packs

You must determine your current Maximo 6.2 version and release. To check your Maximo version and release, click Help > About.

If necessary, update to the latest patch level of Maximo 6.2.

For information about importing the latest Maximo 6.2 patch, refer to “Updating Maximo 6‚" page 13.

Applying the latest SAP ERP adapter patches and fix packs

You must be on SAP ERP adapter 6.2.3 or later to upgrade to version 7. There are two ways to update to version 6.2.3 or later:

Run PowerUpdate.Install the latest patch.

Option 1: Run PowerUpdate

To update to SAP ERP adapter with PowerUpdate.

1 Run PowerUpdate.

2 Run updatedb.bat.

Option 2: Install the latest patch

To update to SAP ERP adapter with the latest patch:

1 Go to the following Web page:

www.ibm.com/software/sysmgmt/products/support/IBMMaximoAssetManagement.html

2 Download the latest patch.

3 Install the patch.

4 Run updatedb.bat.

Backing up the Maximo database

After you complete the SAP ERP adapter pre-upgrade tasks, back up your Maximo database.

Page 38: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade to the Oracle ERP adapter 7.1

34 IBM Maximo: Upgrade Guide

Preparing to upgrade to the Oracle ERP adapter 7.1

There are tasks that you complete to make Maximo, Oracle E-Business Suite, and Oracle ERP adapter meet the required conditions for upgrading the adapter 6.2 to release 7.1.

The following list provides an overview of the these tasks:

Updating the release 6.2 customizations

Completing transactions

Backing up data

Applying the latest patches

Ensure that the configurations you specify in this section are compatible with those you specified in “Preparing to upgrade Maximo Enterprise Adapter‚" page 19.

Updating the release 6.2 customizations

A major part of the upgrade process is planning and implementing the transfer of customizations from release 6.2 to release 7.1 of the Oracle ERP adapter.

You must review your custom release 6.2 interfaces, processing classes, and mappings to determine whether the release 7.1 database columns, interfaces, enterprise services, publish channels, and integration controls affect them.

For more information about the release 7.1 features and mappings of the Oracle ERP adapter, see the following guides:

IBM Maximo Enterprise Adapter Version 7.1 System Administrator Guide for Oracle Applications 12 Adapter

IBM Maximo Enterprise Adapter Version 7.1 Integration Mappings Guide for Oracle Applications 12 Adapter

Completing transactions

Before you upgrade the adapter, you must ensure that there are no unprocessed transactions in the Maximo queues and the Maximo and Oracle interface tables.

To complete the transactions:

1 Check for unprocessed transactions in the Maximo queues:

a Go to the directory that holds the profile with which you installed Maximo and open the error directory.

For example, if you use IBM WebSphere® Application Server, go to the following directory:

Page 39: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade to the Oracle ERP adapter 7.1

Preparing to upgrade 35

C:\IBM\WebSphere\AppServer\profiles\Custom01\error

b If subdirectories exist in the Oracle WebLogic Server or IBM WebSphere Application Server error directory, resolve the problems in the XML files that the subdirectories contain and move the subdirectories to the retry directory.

2 Check for unprocessed transactions in the Maximo interface tables:

a Connect to the Maximo schema owner and enter the following SQL statement:

SELECT ifacetbname FROM maxifaceWHERE ifacetype = 'OA11I' ORDER BY ifacetbname;

b Connect to the MAXORA schema in the Oracle E-Business Suite database and enter the following SQL statement:

SELECT* FROM <ifacetablename>WHERE oa_ifacestatus <> 'DONE';

c If any rows are returned, correct any errors and reprocess the transaction.

3 Check for unprocessed transactions in the Oracle open interface tables:

a Run the concurrent report in Oracle E-Business Suite for every integration point that you use.

b Check the exception report for errors.

c If errors appear after you check for unprocessed transactions, correct them and run the concurrent reports until no errors are returned.

Backing up data

When you are preparing to upgrade your adapter, you must back up some data to prevent accidental loss or corruption of data.

Back up the following data:

PL/SQL user exitsJava user exitsCustomizations that you want to use after the upgradeThe Maximo database and the Oracle E-Business Suite databaseThe oracleapis folder and every folder that it contains

Applying the latest patches

Maximo 6.2.6 and the Oracle ERP adapter release 6.2.3 must be installed in your environment before you upgrade. Otherwise, update them with their latest patches to enable the upgrade utilities program to upgrade Maximo and your adapter successfully.

To apply the latest patch to Maximo, see “Updating Maximo 6‚" page 13.

Page 40: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade Maximo for Oil and Gas

36 IBM Maximo: Upgrade Guide

To apply the latest patch to the Oracle ERP adapter:

1 From C:\<Maximo>\PowerUpdateClient\MEAOraAdapterPowerUpd, run the update.exe file.

2 Download and run the meaupd623.exe file to install the MEAforOraFixPack3 patch.

Preparing to upgrade Maximo for Oil and Gas

In version 6 of IBM® Maximo® for Oil and Gas, you can load ISO 14224 (1999) industry standard asset specifications, failure codes, or both. A newer version of the standard, ISO 14224 (2006), is available in version 7. If you want the 1999 data to be available to you after you upgrade, the 1999 data must be loaded on version 6 before you upgrade.

Preparing to upgrade Maximo for Utilities

You must install the Maximo for Utilities 6.3.3 fix pack before you can upgrade to Maximo for Utilities 7.1.1.

After you install the fix pack, run the checkgis.bat file, which is included with the 6.3.3 fix pack. The file location is <maximo_root>/tools/maximo/checkgis.bat.

To upgrade from Maximo for Utilities 6.3.3 to Maximo for Utilities 7.1.1, you must install both Maximo for Utilities 7.1.1.1 and Maximo Spatial Asset Management 7.1.1.1. Install Maximo Spatial Asset Management 7.1.1 even if you did not deploy Maximo Spatial Asset Management version 6, and even if you do not intend to deploy Maximo Spatial Asset Management 7.x. Version 6 included Maximo for Utilities and Maximo Spatial Asset Management in one common code base. To upgrade the version 6 tables and columns to Maximo for Utilities 7.1.1, both version 7.1.1 products must be installed.

Preparing to upgrade Maximo Spatial Asset Management

Fix pack You must install the Maximo Spatial Asset Management 6.3.3 fix pack before you can upgrade, and you must install the Maximo Spatial Asset Management 7.1.1.1 fix pack.

After you install the 6.3.3 fix pack, run the checkgis.bat file, which is included with the fix pack. The file location is <maximo_root>/tools/maximo/checkgis.bat.

GIS software To use Maximo Spatial Asset Management 7.1, you must install the following version of the GIS software:

ESRI ArcGIS Server 9.3 Enterprise AdvancedESRI ArcSDE 9.3

Page 41: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Preparing to upgrade Maximo for Nuclear Power

Preparing to upgrade 37

When you install version 9.3, the ArcGIS and ArcSDE configurations must not be changed.

Preparing to upgrade Maximo for Nuclear Power

To upgrade to Maximo for Nuclear Power 7.1.1, you must first install Maximo Calibration 7.1.1.1 or later.

Preparing to upgrade Maximo Calibration

To use Maximo Calibration 7.1.1.1 with Maximo Mobile Inventory Manager or Maximo Mobile Work Manager, you must install version 7.1.1 of those products.

Preparing to upgrade Maximo Mobile Work Manager or Maximo Mobile Inventory Manager

Before you upgrade Maximo Mobile Work Manager or Maximo Mobile Inventory Manager, your installed products must be the latest versions and you must process transactions and delete tables.

To prepare to upgrade:

1 Ensure that your products are at version 6.5 and that all available hotfixes have been installed.

2 Ensure that all transactions have been committed to the Maximo application server.

3 Ensure that all users select the Reset Application option on their mobile application.

4 Ensure that no transactions remain in the Mobile Error Management application. For example, delete or resubmit transactions with errors.

5 Using a SQL query tool, execute the following query:

select devicedatatable from mobiledevtrack order by devicedatatable

6 Drop each table that the above query lists.

7 Execute the following query:

delete from mobiledevtrack

Page 42: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Considerations for CCMDB

38 IBM Maximo: Upgrade Guide

Considerations for CCMDB

If you intend to use IBM Tivoli Change and Configuration Management Database (CCMDB) version 7, complete the following pre-upgrade tasks.

Prerequisites

Ensure the following prerequisites have been considered or completed prior to upgrade.

The CCMDB 7.2.0.1 deployment must use the same database type and level as the Maximo 6.2.5 deployment.

Verify that the Domain ID value and tablespace names are consistent for the Maximo database.

To verify that the database storage value and tablespace names are consistent, execute the following SQL statements against the database of your existing Maximo deployment:

select * from user_tablespaces;select domainid,value from alndomain where domainid='DBSTORAGEPARTITION';

The values returned for the database storage value and tablespace name should match. If they do not, refer to http://www-01.ibm.com/support/docview.wss?&uid=swg21262981 for corrective actions.

These procedures provide details for upgrading a Maximo 6.2.5 deployment. If you have an earlier version of Maximo deployed in your environment, you must upgrade it to 6.2.5 prior to using these instructions.

To determine the version level, execute the following SQL statement against the database of your existing Maximo deployment:

select * from maxvars where varname='MAXUPG';

This command should result in one of the following responses:

Result: V600-502 (at 6.2.0 level)Result V600-530 (at 6.2.1 level)Result V600-609 (at 6.2.2.level)Result V600-664 (at 6.2.3.level)Result V600-694 (at 6.2.4.level)Result V600-724 (at 6.2.5.level)

If the result is not V600-724, you must apply the necessary upgrades to get the deployment to the 6.2.5 level. Be advised that patches are not cumulative. Each patch must be applied in succession to get to the 6.2.5 level prior to proceeding with the CCMDB upgrade.

If the upgrade is being performed on a DB2 8 environment, complete the following steps prior to beginning the upgrade process:

1. Increase the log file size for the DB2 Instance. During the upgrade process, there are a large number of uncommitted changes that accumulate. If the log

Page 43: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Considerations for CCMDB

Preparing to upgrade 39

file size limit is too low, the upgrade could fail. Increase the log file size by completing the following steps:

a. Open DOS command prompt and run the following command:

C:\> db2cmd db2 connect to <db_name> user db2admin using db2admin

b. From the db2cmd prompt, run the following command to view database configuration information:

db2 get db cfg for <db_name>

Ensure the following parameter is set to a value of 10

Number of primary log files (LOGPRIMARY) = 10

c. Run the following command to set the log size:

db2 UPDATE DATABASE CONFIGURATION FOR <db_name> USING LOGPRIMARY 10db2 connect resetdb2 connect to <db_name>

2. Ensure the System Tools Schema is present:

a. Open the DB2 Command Center.

b. Using the Navigation Tree, locate the database used with Maximo.

c. Right-click on the database, and select Refresh.

d. In the Schemas folder nested underneath the database entry, verify the existence of a schema named SYSTOOLS.

This procedure can be environment-specific. If the System Tools Schema is not present, you will receive a systemtools error message when the Integrity Checker is first initiated.

Migrating users to a directory server

The latest release of CCMDB 7 can use a directory server for authentication of users. Refer to the CCMDB Planning and Installation Guide for information about supported products and versions.

Other version 7 products also support the use of a directory server for authentication.

You can use the Maximo to LDAP User Registry Utility to migrate your users and groups from the Maximo security registry to a supported directory server. The user and group information is exported from the Maximo registry into an LDIF file, which can be imported into your directory server.

The LDAP User Registry Utility is provided as part of the IBM Service Management Toolkit, available from the Tivoli Open Process Automation Library (OPAL) Web site. To learn about this utility and other tools, read the What's New section of the Toolbox Master Integration Guide. You can read or download the Toolbox Master Integration Guide at www.ibm.com/software/brandcatalog/portal/opal/details?NavCode=1TW10CC1P.

Page 44: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Considerations for CCMDB

40 IBM Maximo: Upgrade Guide

Checking for naming conflicts with previous versions

If the Maximo system whose database you are upgrading had the Maximo 6 Change Manager Extensions and Maximo 6 Release Manager Extensions installed, name conflicts might exist. New content being installed with the latest release of CCMDB 7 might produce name conflicts with objects such as job plans that you created while using the Extensions.

If you do not have the Extensions installed on the system from which you are upgrading, you do not need to check for naming conflicts.

If you have the Extensions installed, use the Change and Release Management Conflict Checking Utility. The utility checks for possible naming conflicts between the existing version 6 database and the content that is added with the latest release of CCMDB 7. If the utility finds conflicts, you must modify the existing database before you upgrade. The utility is installed with CCMDB 7.

Before you run the tool, you must obtain the change and release meta doc files from the installation media. It is a good idea to copy these files from the media to a subdirectory within the CCMDB installation.

Change extension If you have the change extension installed, then run the conflict tool to determine any conflicts for change. For example, in a command window, run the following:

cd <CCMDB_HOME>\maximo\tools\maximomkdir upgrade-pmpcopy <CCMDB_MediaPath>\UpdateTools\changeMetaDoc.xml

<CCMDB_HOME>\maximo\tools\maximo\upgrade-pmp.\conflictchecker -yupgrade-pmp -nchangeMetaDoc.xml

In this example, <CCMDB_HOME> is the directory where CCMDB 7.2 is installed and <CCMDB_MediaPath> is the drive or directory that contains the CCMDB installation media. The output from running the conflictchecker command will be contained in a log file named <CCMDB_HOME>\maximo\tools\maximo\log\ConflictCheckerTimeStamp.log where TimeStamp is a numeric time stamp value.

The following example represents sample data generated from running the conflictchecker command against the changeMetaDoc.xml file. The data shown in the sample log is generated when the change extension is installed, even if there are no user-created conflicts. You should not correct the data shown in the sample for the MAXPRESENTATION, MAXLABELS, MAXVARS, and KPIMAIN tables. That data is automatically changed and corrected during the normal upgrade installation process.

ConflictChecker started for schema MAXIMO Thu Jun 12 14:48:35 CDT 2008ConflictChecker connected to database jdbc:db2://myserver.mydomain.com:50000/maxdb62Thu Jun 12 14:48:35 CDT 2008Input file: C:\ibm\smp\maximo\tools\maximo\upgrade-pmp\changeMetaDoc.xml Thu Jun 1214:48:35 CDT 2008

*** CONFLICTS:A conflict is caused when a row in the target database has the same unique indexvalue as a row in the installable data. The colliding indexes are listed below foreach conflicting table.

TABLE MAXPRESENTATIONAPP : ACTIVITYAPP : CALENDRAPP : CHANGEAPP : JOBPLANAPP : LIBRARYAPP : LOOKUPSAPP : MENUS

Page 45: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Considerations for CCMDB

Preparing to upgrade 41

TABLE KPIMAINKPINAME : PMCHGALLACTIVE

TABLE MAXLABELSAPP : CHANGE, ID : actuals_children_table_1_children_details1_1, PROPERTY : labelAPP : CHANGE, ID : actuals_children_table_tablebody_3, PROPERTY : labelAPP : CHANGE, ID : costs_help, PROPERTY : innerhtmlAPP : CHANGE, ID : showplan_showplan_showallplanlabor_grid1_1_1_showallplanlabor_table_1_grid7_1, PROPERTY : labelAPP : CHANGE, ID : showplan_showplan_showallplanlabor_grid1_1_1_showallplanlabor_table_tablebody_2, PROPERTY : labelAPP : CHANGE, ID : showplan_showplan_showallplanmaterial_grid1_1_1_showallplanmaterial_table_1_grid7_1, PROPERTY : labelAPP : CHANGE, ID : showplan_showplan_showallplanmaterial_grid1_1_1_showallplanmaterial_table_tablebody_2, PROPERTY : labelAPP : CHANGE, ID : showplan_showplan_showallplanservice_grid1_1_1_showallplanservice_table_1_grid7_1, PROPERTY : labelAPP : CHANGE, ID : showplan_showplan_showallplanservice_grid1_1_1_showallplanservice_table_tablebody_2, PROPERTY : labelAPP : CHANGE, ID : showplan_showplan_showallplantool_grid1_1_1_showallplantool_table_1_grid7_1, PROPERTY : labelAPP : CHANGE, ID : showplan_showplan_showallplantool_grid1_1_1_showallplantool_table_tablebody_2, PROPERTY : labelAPP : CHANGE, ID : actuals_children_table_2_2, PROPERTY : labelAPP : CHANGE, ID : plans_children_table_2_2, PROPERTY : label

TABLE MAXVARSVARNAME : DBCHANGE_PMP, ORGID : NULL, SITEID : NULL

*** TABLES THAT DO NOT EXIST IN THE TARGET DATABASE:The following tables to be installed cannot be found in the target database.This likely means that they are new tables, and as such will have no conflicts.

SECURITYRESTRICTREPORTDESIGNMAXLOGGERREPORTPARAMREPORTAPPAUTHMAXROWSTAMPMAXWSREGISTRYMAXPROPVALUEMAXDOMAINLINKCONDITIONJOBPLANCLASSJPTASKRELATIONSIGOPTFLAGMAXPROPREPORTDEPENDDMDEPENDENCYCLASSUSEWITHDMCFGOBJECTSERVICEOBJECTCRONTASKHISTORY

*** COLUMNS THAT DO NOT EXIST IN THE TARGET DATABASE:The following columns cannot be found in the target database. However, they make up part of the unique index of some of the installable data. This means that you cannot check for conflicts in the tables that the columns belong to because there is no basis for comparison. This does not mean that there is a problem with these tables, but rather that the unique index for the table has been altered to include a new column, and therefore the old and new data cannot be compared.

KPITRENDCFG.CONTENTUIDREPORTLOOKUP.APPNAMESYNONYMDOMAIN.VALUEIDMAXINTOBJDETAIL.OBJECTIDSCTEMPLATE.CONTENTUIDESCNOTIFICATION.ESCALATIONDOCINFO.CONTENTUID

Conflict checking failed. Thu Jun 12 14:49:07 CDT 2008ConflictChecker completed Thu Jun 12 14:49:07 CDT 2008

The following example represents information shown in the conflictchecker log related to two name conflicts that might exist in the 6.2.5 database between the change extension and the 7.2 Change process manager function.

TABLE PERSONGROUP

Page 46: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Considerations for CCMDB

42 IBM Maximo: Upgrade Guide

PERSONGROUP : PMCHGMA

TABLE MAXGROUPGROUPNAME : PMCHANGEADMIN

If you find similar entries in your conflictchecker log file, it would mean the following:

You created a person group named PMCHGMA for Maximo 6.2, and this person group name conflicts with one that will be created for the 7.2 product.You created a security group named PMCHANGEADMIN for Maximo 6.2, and this security group name conflicts with one that will be created in the 7.2 product.

To resolve conflicts for the person group

1 Go to the person group application, and select the person group named PMCHGMA.

2 Duplicate the PMCHGMA person group.

3 Name the duplicated person group something other than PMCHGMA and save it.

4 Delete the person group named PMCHGMA.

To resolve conflicts for the security group

1 Go to the seurity group application, and select the security group named PMCHANGEADMIN.

2 Duplicate the PMCHANGEADMIN security group.

3 Name the duplicated security group something other than PMCHANGEADMIN and save it.

4 Delete the security group named PMCHANGEADMIN.

After you have resolved all conflicts, rerun the conflictchecker tool and verify that the only remaining conflicts are those documented in the sample log file above.

Release extension If you have the release extension installed, then run the conflict tool to determine if there are any conflicts for release. For example, in a command window, run the following:

cd <CCMDB_HOME>\maximo\tools\maximocopy <Release_MediaPath>\UpdateTools\releaseMetaDoc.xml

<CCMDB_HOME>\maximo\tools\maximo\upgrade-pmp.\conflictchecker -yupgrade-pmp -nreleaseMetaDoc.xml

<CCMDB_HOME> is the directory where CCMDB 7.2 is installed and <Release_MediaPath> is the drive or directory that contains the Release Process Manager installation media. The output from running the conflictchecker command shown above will be contained in a log file named <CCMDB_HOME>\maximo\tools\maximo\log\ConflictCheckerTimeStamp.log where TimeStamp is a numeric timestamp value.

The following example represents sample data generated from running the conflictchecker command against the releaseMetaDoc.xml file. The data shown in

Page 47: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Considerations for CCMDB

Preparing to upgrade 43

the sample log is generated when the release extension is installed even if there are no user created conflicts. You should not remediate the data shown in the sample for the MAXPRESENTATION, MAXLABELS, MAXVARS, and KPIMAIN tables. That data is automatically changed and remediated during the normal upgrade installation process.

ConflictChecker started for schema MAXIMO Thu Jun 12 14:49:52 CDT 2008ConflictChecker connected to database jdbc:db2://myserver.mydomain.com:50000/maxdb62Thu Jun 12 14:49:52 CDT 2008Input file: C:\ibm\smp\maximo\tools\maximo\upgrade-pmp\releaseMetaDoc.xml Thu Jun 1214:49:52 CDT 2008

*** CONFLICTS:A conflict is caused when a row in the target database has the same unique index valueas a row in the installable data. The colliding indexes are listed below for each conflicting table.

TABLE MAXPRESENTATIONAPP : LOOKUPSAPP : MENUSAPP : RELEASE

TABLE KPIMAINKPINAME : PMCHGALLACTIVEKPINAME : PMRELAVGTIMEKPINAME : PMRELCANCRELKPINAME : PMRELLATETSKKPINAME : PMRELOPENRELKPINAME : PMRELSUCCRELKPINAME : PMRELWAPPRREL

TABLE MAXLABELSAPP : RELEASE, ID : actuals_children_table_1_children_details1_1, PROPERTY : labelAPP : RELEASE, ID : actuals_children_table_tablebody_3, PROPERTY : labelAPP : RELEASE, ID : showplan_showplan_showallplanlabor_grid1_1_1_showallplanlabor_table_1_grid7_1, PROPERTY : labelAPP : RELEASE, ID : showplan_showplan_showallplanlabor_grid1_1_1_showallplanlabor_table_tablebody_2, PROPERTY : labelAPP : RELEASE, ID : showplan_showplan_showallplanmaterial_grid1_1_1_showallplanmaterial_table_1_grid7_1, PROPERTY : labelAPP : RELEASE, ID : showplan_showplan_showallplanmaterial_grid1_1_1_showallplanmaterial_table_tablebody_2, PROPERTY : labelAPP : RELEASE, ID : showplan_showplan_showallplanservice_grid1_1_1_showallplanservice_table_1_grid7_1, PROPERTY : labelAPP : RELEASE, ID : showplan_showplan_showallplanservice_grid1_1_1_showallplanservice_table_tablebody_2, PROPERTY : labelAPP : RELEASE, ID : showplan_showplan_showallplantool_grid1_1_1_showallplantool_table_1_grid7_1, PROPERTY : labelAPP : RELEASE, ID : showplan_showplan_showallplantool_grid1_1_1_showallplantool_table_tablebody_2, PROPERTY : labelAPP : RELEASE, ID : actuals_children_table_2_2, PROPERTY : labelAPP : RELEASE, ID : plans_children_table_2_2, PROPERTY : label

TABLE MAXVARSVARNAME : DBRELEASE_PMP, ORGID : NULL, SITEID : NULL

*** TABLES THAT DO NOT EXIST IN THE TARGET DATABASE:The following tables to be installed cannot be found in the target database.This likely means that they are new tables, and as such will have no conflicts.

REPORTDESIGNMAXLOGGERREPORTPARAMREPORTAPPAUTHMAXROWSTAMPJOBTASKSPECMAXWSREGISTRYMAXPROPVALUEMAXDOMAINLINKCONDITIONLNKCLAUSEATRNAMEJOBPLANCLASSJPTASKRELATIONMAXPROPREPORTDEPENDDMDEPENDENCYPMRELDEPACTNSCLASSUSEWITHMAXPROPINSTANCECLASSSPECUSEWITHDMCFGOBJECT

Page 48: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Backing up your database

44 IBM Maximo: Upgrade Guide

SERVICEOBJECTCRONTASKHISTORY

*** COLUMNS THAT DO NOT EXIST IN THE TARGET DATABASE:The following columns cannot be found in the target database. However, they make up part of the unique index of some of the installable data. This means that you cannot check for conflicts in the tables that the columns belong to because there is no basis for comparison. This does not mean that there is a problem with these tables, but rather that the unique index for the table has been altered to include a new column, and therefore the old and new data cannot be compared.

KPITRENDCFG.CONTENTUIDREPORTLOOKUP.APPNAMESYNONYMDOMAIN.VALUEIDMAXINTOBJDETAIL.OBJECTIDWFNOTIFICATION.UNIQUEIDSCTEMPLATE.CONTENTUIDESCNOTIFICATION.ESCALATIONDOCINFO.CONTENTUIDLONGDESCRIPTION.CONTENTUID

Conflict checking failed. Thu Jun 12 14:50:25 CDT 2008ConflictChecker completed Thu Jun 12 14:50:25 CDT 2008

After you resolve any conflicts other than those shown in the sample above, rerun the conflictchecker tool. Verify that the only remaining conflicts are those documented in the sample log.

Backing up your database

Regardless of your starting point, back up your newly prepared Maximo database.

Page 49: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

© Copyright IBM Corp. 2007, 2013 45

You upgrade the Maximo database using the Maximo Upgrade Utilities program, which is included with your version 7 product.

IMPORTANT Be sure that you are using the latest edition of the Upgrade Guide. You can find the edition number on the legal page (page ii) of the Upgrade Guide. The latest edition is available at the Maximo Upgrade Resources Web page.

Maximo Upgrade Utilities program process overview

The Maximo Upgrade Utilities program includes the following three utilities:

Integrity checker utility

Validation utility

Upgrade utility

The following sequence of tasks provides a high-level overview of running the utilities. Refer to the sections discussing each utility for detailed steps.

1 Start the Maximo Upgrade Utilities program and connect to the database that you are upgrading.

2 Run the integrity checker in report mode, review the error and warning messages (Appendix B), and correct reported errors as needed.

3 Run the integrity checker in repair mode.

4 Run the integrity checker again in repair mode until there are no errors.

5 Run the validation utility, fix reported errors, and run the utility again until there are no more errors.

6 Run the upgrade utility.

You back up your database after you run the integrity checker utility, after you run the validation utility, and after you run the upgrade utility.

Upgrading the database 3

Page 50: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Starting the Maximo Upgrade Utilities program

46 IBM Maximo: Upgrade Guide

Starting the Maximo Upgrade Utilities program

The Maximo Upgrade Utilities program (upgradeui.bat) is installed with your version 7 product in the Maximo_root\tools\maximo folder. Run the program from the server on which you installed it.

Prerequisites:

You installed your version 7 product or products.You applied the latest available updates for your version 7 product.You have ensured that database parameters in the Maximo. properties file specify the correct information for the database that you want to upgrade.

To start the Maximo Upgrade Utilities program:

1 From a command prompt, change directory to:

Maximo_root\tools\maximo\

For example: c:\Maximo\tools\maximo\

2 At the prompt, type upgradeui.bat and press Enter.

The Maximo Upgrade Utilities interface opens to the Login tab.

Verifying information on the Login tab

The Login tab specifies the database that you want to upgrade. The values are based on the values in the maximo.properties file.

To verify login information:

1 Ensure that the database values that are on the Login tab match the values that you recorded in the Maximo 6 Database Information worksheet on page 14. If necessary, edit the maximo.properties file of your version 7 product to specify the correct database information for the upgrade. Use a text editor to edit the maximo.properties file.

The program checks for a version number in the Current Maximo Version field.

2 Review the read-only information in the Database section, in the DB Alias, User Name, and Current Maximo Version fields. Check that the fields reflect the correct database information for your Maximo 6 product. The information that is in the Properties section pertains to your Maximo 6 system.

3 After you verify the information on the Login tab, click Check Integrity.

Actions that you initiate on the other tabs affect the database that is currently connected to on the Login tab. After you upgrade a database, you can return to the Login tab and enter a different path or properties file to connect to a different database.

Page 51: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verifying database integrity

Upgrading the database 47

You can view the output of the upgrade utilities in list files and log files, which the system generates in the Maximo_root\tools\maximo\log folder. If you run the utilities again, the system overwrites the log files unless you exit the Maximo Upgrade Utilities program and start it again. This action creates new files that have a different time stamp.

Back up your database after you run each utility.

Verifying database integrity

You use the integrity checker utility to identify data errors that can prevent a successful upgrade.

Integrity checker utility

The integrity checker utility checks the current database and reports on common errors. The integrity checker does not identify all of the data errors that might exist. However, you must correct all errors found by the integrity checker before you can run the validation utility.

The integrity checker utility performs the following tests as part of checking database integrity:

Checks “same-as” information. Certain columns in the Maximo database tables must be the same same type and size as another column, called a root column. The root column can be in the same table or in a different table.

Identifies indexes and related information, for example, a name length greater than 18 characters.

Identifies nonsequential primary-key sequences.

Identifies pending configuration changes.

Identifies inconsistencies between user and group accounts and security tables in Maximo.

Checks the existence of various Maximo tables and columns across metadata tables, and at the database (system) level.

Checks the definitions of tables and columns across metadata tables, and at the database (system) level.

The integrity checker utility updates the MAXVARS table to indicate whether the database integrity check completed successfully. You must run the integrity checker utility without errors before you can run the upgrade utility.

The integrity checker utility runs in two modes: report mode and repair mode.

Page 52: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verifying database integrity

48 IBM Maximo: Upgrade Guide

Report mode

Report mode creates a list of database errors and warnings. Fix all errors before you proceed with the validation utility.

Upon completion, the integrity checker utility produces two files:

List (LIS) file—basic information (for example, messages, warnings, errors).

Log (LOG) file—a detailed log that contains each transaction that the utility recorded. The log file includes a complete list of errors, warnings, and SQL statements that the integrity checker utility produced.

The list and log files are in the Maximo_root\tools\maximo\log folder. You can open and review the files with any text editor. Rename, save to another folder, or print a copy of each file, because the integrity checker utility overwrites the list and log files each time that it runs.

When you run the integrity checker utility in report mode, the database does not change. Review the list file and examine any errors and warnings. If you need more information, review the log file.

Responding to error messages and warning messages

You must fix many errors manually. Fix errors by using the Maximo 6 applications or an SQL editor. Other errors can be fixed by running the integrity checker utility in repair mode.

See Appendix B, “Troubleshooting the upgrade process‚" on page 173, to review the errors that would be fixed by running the integrity checker utility in repair mode. Check that the method that repair mode would use to fix an error is the method that you want to be used.

If a repair mode fix would yield results different from what you want, fix that error manually before you run the integrity checker utility in repair mode. For example, repair mode might remove a table that has no columns. If you want to keep the table, fix the error by adding a column to the table before you run the integrity checker utility in repair mode.

The list and log files provide some information about error and warning conditions that the integrity checker utility encountered. For more information about errors and warnings that are listed in the list and log files, see Appendix B.

Repair mode

Repair mode fixes errors that do not require manual intervention. Other errors are recorded in the list files and log files and you must fix them manually.

Correct all errors before you proceed with the validation utility. If the integrity checker utility runs and finds errors, investigate the cause of the errors and correct the problems. Also investigate warnings and correct the problems.

Page 53: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verifying database integrity

Upgrading the database 49

Running integrity checker in repair mode produces the following results:

If a Maximo user is not a database user, the user is dropped from Maximo and the security tables.

If a Maximo group is not a database user, the group is dropped from Maximo and the security tables.

If a Maximo group is not a Maximo user, the group is dropped from Maximo.

If a Maximo user is in a group that is not a Maximo group, the group is dropped from Maximo and security tables.

It refreshes MAXSYSINDEXS and MAXSYSKEYS from native indexes.

If a Maximo table owns no columns, the table is dropped from Maximo.

If a bad table alias exists, the alias is changed to V_ table_name.

If a rowstamp or a MaxTriggers trigger is missing, the trigger is created.

If a Maximo column does not exist, the column is dropped from Maximo.

If a Maximo column is defined differently on the database, the Maximo definition is changed to match the database.

If a rowstamp is null, the rowstamp is populated from the trigger.

If column A is the same as column B and the root column for column C, then column C is made the same as column B.

If a same-as column is defined differently than the root column, the same-as column definition is changed to match the root.

If an autokey is not referenced, it drops the autokey.

Data state checking The integrity checker utility also checks the following data states. These checks were not in some previous versions of the integrity checker:

Every Maximo table and view must have a valid primary key column sequence.

Every primary key column sequence must correspond to a unique index.

Every persistent Maximo table must have a column defined as its unique ID.

Every unique column ID must correspond to a unique index.

Nonpersistent tables cannot have persistent columns.

Same-as columns must have the same “must-be” setting.

A YORN column must be required (not null).

All autokeys that are referenced by columns must exist.

Columns that are mapped to domains cannot have values not in the domain.

Page 54: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verifying database integrity

50 IBM Maximo: Upgrade Guide

Columns that are mapped to domains must be the same datatype as the domain.

Domains must have valid domain types, maxtypes, and lengths.

All rows in configuration tables (MAXTABLECFG, MAXATTRIBUTECFG, and so on) must match the base table (MAXTABLE, MAXATTRIBUTE, and so on).

Orphaned LONGDESCRIPTION

An orphaned long description is a record in the LONGDESCRIPTION table that is not linked to a Maximo record, such as a work order record. The LDKEY column links the LONGDESCRIPTION record to the Maximo record. Orphaned long description records might be in the LONGDESCRIPTION table because of archiving or because the database was manually updated.

If any orphaned long descriptions exist, the upgrade fails.

The integrity checker utility issues a warning when it finds orphaned long descriptions. Run integrity checker in repair mode to remove orphaned long descriptions.

Use of the configdb.bat file

If repair mode changes the database, you are prompted to run the configdb.bat file. Run the configdb.bat file to complete configuration of the changes that repair mode makes.

Repeat use of report mode

After you run the integrity checker utility in repair mode and configure the database, run the integrity checker utility again in report mode. You repeat the use of report mode to determine if any errors remain. If errors still occur, fix them. Then run the integrity checker utility in report mode again.

Also investigate warnings. For more information, see Appendix B, “Troubleshooting the upgrade process‚" on page 173. Repeat the process until integrity checker runs without reporting errors.

After the integrity checker utility runs without error, it marks the database as having passed the verification of the integrity of the database. The Integrity Checker Successful dialog box is displayed. Click OK.

You cannot upgrade until the integrity checker reports no errors. Warnings do not prevent a database from passing the integrity checker utility verification. You can correct the situations that generate warnings before or after you upgrade.

Back up your database after you run each utility.

Integrity checker record count

The integrity checker counts the number of records in each of the applications.

The record count is in the Integritytime_stamp.lis file, which is in the following folder: Maximo_root\tools\maximo\log.

Page 55: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Verifying database integrity

Upgrading the database 51

You can use the record count to identify potential trouble spots (very large records, for example) and flag them with a pause callout. The pause creates an opportunity for you to take actions. For example, you can create temporary indexes to help improve performance, or back up the database. You resume the upgrade by pressing the Enter key. You then can create another backup when the next pause callout is reached. For more information about pause callouts, see “Interrupting the upgrade process‚" on page 61.

Running the integrity checker utility

You run the integrity checker utility to verify that your database is internally consistent and can be upgraded. You must run the integrity checker utility to completion without errors before you can upgrade your database.

To run the integrity checker utility:

1 Clear the Repair Mode check box to run integrity checker in report mode.

2 Click Run Integrity Checker.

3 Use Windows Explorer to navigate to the error messages list (LIS) and log (LOG) files located in the following folder (the Maximo 7 installation folder):

Maximo_root\tools\maximo\log

4 Use your text editor to open the list file (Integritytime_stamp.lis) to find the problem areas. Then open the log file (Integritytime_stamp.log) to see details about the error messages.

5 Review the errors that can be fixed by running the integrity checker utility in repair mode. Check that the errors would be fixed by the method that you want. If the repair mode fixes would yield results different from what you want, fix those errors manually before you run the integrity checker utility in repair mode.

6 Select the Repair Mode check box.

7 Click Run Integrity Checker.

8 If you are prompted to, run Database Configuration (the configdb.bat file) in Maximo 6 to fix reported errors. You might also need to use the Security applications to fix some errors.

For errors that are written to the metadata instead of to the configuration tables, you can use an SQL tool to access the records in the database. Correct the errors from the SQL prompt.

9 Run the integrity checker utility in report mode again.

10 Exit from the Maximo Upgrade Utilities, shut down the database, and create a full backup of the database.

11 Start the database, and then start the Maximo Upgrade Utilities (upgradeui.bat).

Page 56: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Validating the database

52 IBM Maximo: Upgrade Guide

You might need to run the integrity checker utility multiple times and search again for errors in the log and list files. Resolve all errors before you run the validation utility.

The integrity checker utility updates the MAXVARS table to indicate whether the integrity check completed successfully. You must run the integrity checker utility without errors before you can run the validation utility.

Validating the database

You use the validation utility to check additional database properties and files to ensure that the upgrade will proceed properly.

Validation utility

The validation utility checks that valid data in the source Maximo database that needs user intervention is transformed correctly before the upgrade can proceed. For example, you might need to provide a unique e-mail address for users whose e-mail address is not unique.

The validation utility also generates list files and log files. The files contain the same information, but the log file includes the SQL statements. The list file does not contain the SQL statements.

The validation utility performs the following tasks as part of validating your database for the upgrade:

Checks for the existence of tables, columns, or indexes to be added.

Checks that data will change successfully, for example, report registrations, addition of unique indexes, updating of data for bug fixes, and new features.

Checks that the database passed the integrity checker utility.

Checks that the database version matches MetaDoc.xml.

Checks that no backup or unrestored tables exist.

Checks that the database is not being configured.

Checks that a table, column, or index that is to be updated or deleted does exist.

Checks that two menu items do not have the same menu position.

Checks that no Workflow processes are active.

If duplicate records exist, the utility lists error messages and generates the corresponding XML files. Edit the files to correct the corresponding errors.

The validation utility updates the MAXVARS table to indicate whether validation completed successfully. You must run the validation utility without errors before you can run the upgrade utility.

Page 57: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Validating the database

Upgrading the database 53

XML files generated by the validation utility

The validation utility writes error data to XML files. Resolve the errors by editing each file and adding a new value to each error record. The XML files are in the Maximo_root\tools\maximo\classes\psdi\upgrade\V600 folder.

The validation utility might lock an XML files for editing. If the XML file is locked, close the Maximo Upgrade Utilities (upgradeui.bat). Edit the XML file, save it, and then restart the Maximo Upgrade Utilities.

UpgEmail.xml In version 7, all users must have a unique e-mail address. Every e-mail address in the Maximo 6 database that is associated with more than one user is written to the UpgEMail.xml file.

Duplicated entries will be listed in the file with newemailaddress=””. You can specify the existing e-mail address within the quotation marks in the newemailaddress parameter for one user. You must specify a different, unique e-mail address for the other user or users.

Example

An example of the UpgEmail.xml file before editing. The final pair of quotation marks in each record line does not contain a value.

<?xml version="1.0" encoding="UTF-8"?><document table="EMAIL" database="jdbc:oracle:thin:@172.22.40.18:1521:MAXIMO"> <RECORD emailaddress="[email protected]" emailid="146133" newemailaddress="" /> <RECORD emailaddress="[email protected]" emailid="145840" newemailaddress="" /> <RECORD emailaddress="[email protected]" emailid="145903" newemailaddress="" /> <RECORD emailaddress="[email protected]" emailid="146131" newemailaddress="" /></document>

You must specify a unique e-mail address inside the newemailaddress=””.

An example of the UpgEmail.xml file after editing. The final pair of quotation marks in the record lines now contains a value.

<?xml version="1.0" encoding="UTF-8"?><document table="EMAIL" database="jdbc:oracle:thin:@172.22.40.18:1521:MAXIMO"> <RECORD emailaddress="[email protected]" emailid="145840" newemailaddress="[email protected]" /> <RECORD emailaddress="[email protected]" emailid="145903" newemailaddress="[email protected]" /> <RECORD emailaddress="[email protected]" emailid="146131" newemailaddress="[email protected]" /> <RECORD emailaddress="[email protected]" emailid="146133" newemailaddress="[email protected]" /></document>

UpgCompTypeI.xml Version 7 introduces a new company type: I for internal. The other company types are M for manufacturer, V for vendor, and C for courier.

If, in version 6, you introduced your own value I as an additional company type, the validation utility generates the UpgCompTypeI.xml file. UpgCompTypeI.xml

Page 58: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Validating the database

54 IBM Maximo: Upgrade Guide

is produced so that you can specify a new value for I that does not conflict with the use of I by version 7. Insert the value between the empty pair of quotation marks (““) in the XML file.

Valid options for the new value for I are V, for vendor, M, for manufacturer, C, for courier, and I, for internal. You can also specify any other value that you added to the COMPTYPE ALN domain in version 6. For example, if you added a company type of X, X is a valid value. The value you specify will be used to update any existing company values that are currently, in version 6, type I. If you maintain the value of I, it will map to the new I, for internal, version 7 company type.

Example

An example of the UpgCompTypeI.xml file before editing. The final pair of quotation marks in the record line does not contain a value.

<?xml version="1.0" encoding="UTF-8"?><document table="COMPANIES" database="jdbc:inetdae7a:woody:1433?database=UPGGABI&amp;language=us_english&amp;nowarnings=true&amp;mars=false"> <RECORD value="I" description="Type of company for I" newcomptype="" /></document>

An example of the UpgCompTypeI.xml file after editing. The final pair of quotation marks in the record line now contains a value.

<?xml version="1.0" encoding="UTF-8"?><document table="COMPANIES" database="jdbc:inetdae7a:woody:1433?database=UPGGABI&amp;language=us_english&amp;nowarnings=true&amp;mars=false"> <RECORD value="I" description="Type of company for I" newcomptype="V" /></document>

Properties files checked by validation

The validation utility checks to see if the following properties files exist:

upgmaximo.propertiesupgdoclink.propertiesupgsetting.properties

The validation utility generates a warning if a properties file is not found.

For information about upgrading properties files, see “Preparing properties files for the upgrade process‚" on page 15.

Page 59: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrading the database

Upgrading the database 55

Running the validation utility

Ensure that you corrected all errors that the integrity checker utility reported before you continue with the validation tasks. To run the validation utility:

1 On the Validation tab, click Run Validation.

2 Navigate to the error message list and log files in the following folder (the version 7 installation folder):

Maximo_root\tools\maximo\log

3 Use a text editor to open the list file (Validationtime_stamp.lis) to find the problem areas. Then open the log file (Validationtime_stamp.log) to see details about the error messages.

Notable errors include a list of XML files that you must edit. These XML files are in Maximo_root\tools\maximo\classes\psdi\upgrade\V600\ (or the appropriate folder for the current Maximo version that you are upgrading to version 7).

4 Use a text editor to open each XML file and specify a unique value between the pairs of quotation marks.

5 Exit the upgrade utilities, shut down the database, and back up the database.

6 Start the database, and then start the Maximo Upgrade Utilities (upgradeui.bat).

The validation utility updates the MAXVARS table to indicate whether validation completed successfully. You must run the validation utility without errors before you can run the upgrade utility.

Upgrading the database

You use the upgrade utility to perform the actual database upgrade. Depending on the size of the database the upgrade can take hours. You can pause or stop the upgrade at preset points by editing specific files. See “Interrupting the upgrade process‚" on page 61 for more information.

Upgrade utility

The upgrade utility performs the actual database upgrade.

Ensure that the database values that are on the Login tab match the values that you recorded in the Maximo 6 database information worksheet, page 14. The values on the Login tab specify the version 6 database that the upgrade utility operates on.

Page 60: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrading the database

56 IBM Maximo: Upgrade Guide

Upgrading screens

Because screen presentation definitions are stored in the database, the upgrade utility upgrades your screen presentations as part of the database upgrade.

The upgrade utility upgrades any screen configurations that you made as part of the database upgrade.

Maximo_root\tools\maximo\ screen-upgrade folder

The upgrade uses and generates screen presentation XML files. The XML files are in the Maximo_root\tools\maximo\screen-upgrade folder. Some files do not exist until after the upgrade.

The upgrade utility provides or generates four XML files:

The base6.xml file provides a copy of the default version 6 screens.

The cust6.xml file lists your current version 6 presentations. The upgrade generates the cust6.xml file to record your version 6 screen presentations, including any configurations that you might have made.

The base7.xml file provides a copy of the default version 7 screens. This file is generated by the upgrade.

The upg7.xml file provides a copy of all the screen presentations after the upgrade process, including upgraded screen configurations, if there are any. The upg7.xml file is generated by the upgrade.

During the upgrade, any screen configurations that are recorded in the cust6.xml file are applied, as nearly as possible, to the default version 7 screen presentations that are recorded in the base7.xml file.

Screen upgrade options

You have three options for upgrading screens:

Do not upgrade any version 6 configurations. Start with the default version 7 screens for all applications.Upgrade your version 6 screen configurations, and keep all the upgraded configured presentations.Upgrade version 6 screen configurations, but keep upgraded configurations for selected applications only. Use the default version 7 screens for other applications.

Option 1: Do not upgrade version 6 configurations

You might have made configurations to your version 6 screens, but do not want to upgrade the configurations to version 7.

Before you run the upgrade, review your own configured version 6 screens. Compare them to the default version 7 screens in the version 7 product that you installed. You might decide that you do not want to upgrade your version 6 configurations.

To have the upgrade process ignore your version 6 screen configurations, rename or relocate the base6.xml file before you run the upgrade.

After you upgrade, use the Application Designer to configure the version 7 screens.

Page 61: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrading the database

Upgrading the database 57

Option 2: Keep all upgraded configurations

The default behavior of the upgrade process is to attempt to match all version 6 configurations in the upgraded version 7 screens.

After you upgrade, use the Application Designer to configure the version 7 screens.

Option 3: Keep some, but not all, upgraded configurations

After you upgrade, review the upgraded screens. You can keep the upgraded configured screens for some applications, and revert to the default version 7 screens for other applications.

Upgpoints.xml file

The upgpoints.xml file in the Maximo_root\tools\maximo\classes\psdi\upgrade\V600 folder contains several <UPGPOINT ...></UPGPOINT> tags. The upgpoints.xml file that is shipped with the Maximo Upgrade Utilities has each of the UPGPOINT tags uncommented. For each uncommented UPGPOINT maxvar in the file, the upgrade utility examines the database that is being upgraded to determine if the product associated with that maxvar is installed.

For example, the following segment from the upgpoints.xml file shows the UPGPOINT and related maxvar for the IBM Maximo for Transportation industry solution.

<UPGPOINT maxvar="DBTRANSPORTATION" metaformat="DBTRANSPORTATION_MetaFormat.sql" metadoc="DBTRANSPORTATION_MetaDoc.xml" callouts="DBTRANSPORTATION_AppCallOutList.xml" upgmessages="" promptfilename="dbtransportation"></UPGPOINT>

If the MAXVARS table in the database that is to be upgraded has a row for the maxvar DBTRANSPORTATION, then the upgrade utility determines that the database has that industry solution installed. The check for the presence of a maxvar DBTRANSPORTATION row is:

select * from maxvars where varname='DBTRANSPORTATION'

If the check returns a record, then the upgrade utility will behave as if the product is installed. In the folder hierarchy of the upgrade utility, the upgrade process searches for a metadoc.xml file that is specific to that product. The check for the metadoc.xml reference is done to attempt to upgrade that product as part of the database upgrade. If the metadoc.xml reference is not found, the upgrade utility generates an error.

For example, if your database has IBM Maximo for Transportation installed, but the upgrade utility does not support upgrading that product at the time you run the upgrade, you would see the following error:

Input file Maximo_root\tools\maximo\classes\psdi\upgrade\V600\EN\DBTRANSPORTATION_MetaDoc.xml was not found.

In the default upgpoints.xml file, the UPGPOINT tags are uncommented so that the upgrade will not proceed if the database has any add-on products installed that the upgrade process does not support. Check the Maximo Upgrade Resources Web page for information about which add-on products are supported by the Maximo Upgrade Utilities.

Page 62: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrading the database

58 IBM Maximo: Upgrade Guide

If your database has an add-on product installed, but the upgrade utility installation does not contain the necessary metadoc.xml file for that product, the upgrade utility does not support upgrading that product. You cannot upgrade your entire installed product set until all of your products are supported by the upgrade.

Doing a partial upgrade for testing

You still might want to run the upgrade process in a test environment to experiment with how the upgrade process operates on the products, such as core Maximo, that it currently supports. To run the upgrade process on the supported elements of your installation, comment out the lines in the upgpoints.xml file that list a UPGPOINT that has a maxvar for which a row does exist in the database that is to be upgraded.

A completed run of the upgrade utility for that database does not represent a complete, successful upgrade. The add-on products that are installed in the database, and which have had their corresponding UPGPOINT lines commented out in the upgpoints.xml file, have not been upgraded.

Exception: Maximo for Service Providers

If you have IBM Maximo for Service Providers installed, the core Maximo database was affected by its installation. Trying to upgrade only core Maximo will fail if Maximo for Service Providers is not yet supported by the upgrade process. To upgrade core Maximo and Maximo for Service Providers, wait until the Maximo Upgrade Utilities support upgrading Maximo for Service Providers to version 7.

Upgrade tab of the upgrade utility

The Upgrade tab of the upgrade utility interface has fields where you enter data. Use the descriptions of the fields to help you determine the values to enter when you run the upgrade utility.

Specifying the person ID for E-mail Listener staging

Use the Person ID for E-mail Listener Staging field to specify the e-mail address to send e-mail listener staging messages to.

Specifying a name for the EVERYONE security group

In version 7 products, there is a new security group with the default name of EVERYONE. By default, all users belong to the EVERYONE security group.

You can change the name for the EVERYONE security group by editing the default value of EVERYONE in the Name for the EVERYONE Security Group field.

Specifying a new internal value for version 6 company type values

In Maximo 6, there are three default company types in the COMPTYPE domain, which is an ALN domain:

V, for vendorM, for manufacturerC, for courier

Page 63: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrading the database

Upgrading the database 59

You might have created additional version 6 ALN company types, such as I, X, Y, and Z.

In version 7, the COMPTYPE domain is a SYNONYM domain type. There is also a new default company type, I, for internal. Any additional company types in version 7 must map to, be a synonym of, one of the four default company types:

V, for vendorM, for manufacturerC, for courierI, for internal

If, in version 6, you created one or more additional company types, those company types must be a synonym of V, M, C, or I in version 7.

Use the Default for All COMPTYPE Values That Are Not V, M, C, or I field to specify the internal version 7 company type that user-defined version 6 company types should be mapped to. The one possible exception is a version 6 user-defined company type of I, which will be mapped in version 7 to the value that is specified in the UpgCompTypeI.xml file.

The default internal type for version 6 company types that are not V, M, C, or I, is V, for vendor.

See the Mapping of version 6 Company Types table for an example. The value that you specify in the Default for All COMPTYPE Values That Are Not V, M, C, or I field would replace the question marks in the table after the upgrade process.

Mapping of version 6 company types to version 7 internal company types

Viewing or specifying the log file name

The default value of the Log File Name field is a system-generated name for the upgrade utility log file. You can edit the value in this field.

6 Company Type 7 Company Type, Display Value

7 Company Type, Internal Value

V (vendor) V (vendor) V (vendor)

M (manufacturer) M (manufacturer) M (manufacturer)

C (courier) C (courier) C (courier)

I (user-defined) I (internal) I (internal)

X (user-defined) X ?

Y (user-defined) Y ?

Z (user-defined) Z ?

Page 64: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrading the database

60 IBM Maximo: Upgrade Guide

Running the upgrade utility

The database must pass the validation check successfully with no errors. To help you decide what values to enter on the Upgrade tab, refer to the previous section describing the utility.

Prerequisite

Review the default version 7 screens that are in the installation of your version 7 product. If you do not want your version 6 screen configurations upgraded, rename the base6.xml file before you run the upgrade utility. The base6.xml file is in the Maximo_root\tools\maximo\screen-upgrade folder.

To run the upgrade utility:

1 Click the Upgrade tab.

2 In the Person ID for E-mail Listener Staging field, enter an e-mail address.

3 If you want to change the name of the default security group, in the Name for EVERYONE Security Group field, enter a new name for the EVERYONE security group.

4 In the Default for All COMPTYPE Values That Are Not C, M, V, or I field, specify the internal company type value that you want to be associated with any version 6 user-defined company types. The default is V, for vendor.

5 If you want to change the name of log file, in the Log File Name field, enter a new log file name.

6 Click Set.

7 Click Run Upgrade.

Depending on the size and complexity of your database, the upgrade process might take many hours.

8 Check for errors in the log files (Maximo_root\tools\maximo\log\).

9 Back up your database.

Page 65: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interrupting the upgrade process

Upgrading the database 61

The upgrade utility log files

Interrupting the upgrade process

You can interrupt the upgrade process in two ways: by pausing it or stopping it.

You pause the upgrade process to query the data or create indexes to improve the upgrade performance. You can also back up the database using the importing and exporting capabilities of your database software. However, importing and exporting take much longer to back up and restore than shutting down the database and backing up the files. Stopping the upgrade process is generally more time efficient than pausing it.

The upgrade program uses sets of files called callouts to manipulate the data within the Maximo database tables. To pause the upgrade program, you insert a special type of callout XML statement, the pause callout. If there are any problems with your upgrade process after a pause callout, you can restore the database, and fix the error. You can then resume the upgrade process from the pause that you inserted before the failure. If the upgrade program fails, it rolls back any changed data to the previous successful commit statement. When you resume the upgrade program, it continues processing from after the last successful callout.

To stop the upgrade process so that you can back up the database, insert a stop callout. Also create an SQL file that the stop callout will call and cause the database to stop running.

For example, you can review the integritytime_stamp.lis file that the integrity checker utility generates and identify large table sizes. You can then insert pause callouts to manually pause the upgrade process for those tables. When the upgrade pauses, you can create a snapshot or export of the database, run SQL queries, create indexes, modify data values, and so on.

You can view a list of the callouts in the AppCalloutList.xml file in the Maximo_root\tools\maximo\classes\psdi\upgrade\V600 folder.

Identifying where to interrupt the upgrade process

The pause and stop features apply to the upgrade utility. When you click Run Upgrade on the Upgrade tab, the upgrade process begins the first of three phases:

Phase 1: The upgrade process creates a new data structure. The upgrade process uses Metadoc files to create Maximo configuration tables. It adjusts values and performs database configuration to create new tables with no restrictions.

File name Description

Upgradetime_stamp.log Check the entire Upgrade file for any upgrade errors.

ConfigDBtime_stamp.log Check the ConfigDB file for any configuration errors.

RestoreFromBackuptime_stamp.log Check the RestoreFromBackup file for possible restore errors.

DropBackuptime_stamp.log Check the DropBackup file for any errors, although it is unlikely to contain errors.

Page 66: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interrupting the upgrade process

62 IBM Maximo: Upgrade Guide

Phase 2: The callouts are executed in the second phase. Data is moved to new tables. You insert the pause and stop callouts in this phase.Phase 3: The upgrade uses Database Configuration to place table and column restrictions, such as this column is not null.

Stop the upgrade once before phase 2 begins, once before phase 3 begins so that you back up each segment.

Where to insert the stop callouts depends upon the callouts that have more than one commit statement. If the upgrade fails at one of the commit statements in the middle of the callout, you cannot correct the problem and then resume the upgrade. You must restart the database from the most recent backup, then correct the problem and restart the upgrade.

When you run the integrity checker utility, it produces a set of log files in the Maximo_root\tools\maximo\log folder. The list and log files list the number of records for each Maximo table in the database. You use these log files to identify the tables that have a large number of records and would take a longer time to process. Consider pausing the upgrade before any callout that manipulates large database tables. You can insert as many pause callouts as you want.

Inserting a pause or stop callout

A good approach to using callouts is to insert four stop callouts in the AppCalloutList.xml file:

Before the first callout, UpgradeDefaults.Before the UpgradeItemOrgInfo callout.Before the UpgradeCOA callout.At the end of the last callout, UpgradeMaxLabelPropCase.

You can insert as many stop callouts as you want in the AppCalloutList.xml file. You are not limited to the four in the list.

To insert a pause or stop callout:

1 Open the AppCallOutList.xml file from the following location:Maximo_root\tools\maximo\classes\psdi\upgrade\V600

2 Search for the UpgradeDefaults callout. It is the first in the AppCallOutList.xml file.

3 Using a text editor, insert a line before the UpgradeDefaults callout.

Page 67: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interrupting the upgrade process

Upgrading the database 63

4 Type one of the following callouts, exactly as it appears::

5 Search for the UpgradeItemOrgInfo callout.

6 Include the pause or the stop callout before the UpgradeItemOrgInfo callout. Insert another callout before the UpgradeCOA callout.

7 Scroll down the AppCallOutList.xml file and find the last callout, UpgradeMaxLabelPropCase.

8 Insert a pause or stop callout after the UpgradeMaxLabelPropCase callout.

9 Save the AppCallOutList.xml file and close it.

Running the upgrade with the stop callouts

You can use stop callouts in the upgrade utility. To run the upgrade utility with the stop callouts:

1 After you modify the AppCallOutList.xml file, run the upgrade utility.

2 When the upgrade utility stops with a missing table error at the first stop, UpgradeDefaults, shut down the database and create a full backup of the database.

3 Remove the first pause (before UpgradeDefaults), save the AppCallOutList.xml file, and restart the database and the upgrade utility (upgradeui.bat) until it stops again.

4 Shut down the database and create another full backup of the database. Repeat steps 2 and 3 for the UpgradeItemOrgInfo, UpgradeCOA, and UpgradeMaxLabelPropCase callouts.

5 After the upgrade process stops when the upgrade utility completes, create another backup.

Callout Type Purpose

Stop: <APP filename=”Stop”></APP> Stops the upgrade. Use a stop callout for all four interruptions. Complete the following steps:

a Create a file named UpgradeStop.sql. The file name is case-sensitive.

b The file must contain the following lines, with the semicolon on a separate line:

select 1 from Stop_the_upgrade;

c Save the file in the following directory: \tools\maximo\classes\psdi\upgrade\V600

Pause: <APP filename=”Pause”></APP> Queries data or creates indexes. You do not need to create an SQL file. A pause file already exists.

Page 68: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Interrupting the upgrade process

64 IBM Maximo: Upgrade Guide

Using a pause callout

The pause callout gives you an opportunity to decide whether to stop the database. You can insert as many stop and pause callouts as you want. With pause callouts, you do not need to shut down the database. You can run queries or create indexes. You press Enter to resume the upgrade.

Resuming the upgrade

If the upgrade process fails, you can resume the upgrade process from the point of failure, rather than from the beginning of the process. Resuming from the point of failure can save you time and resources.

If the upgrade fails, the upgrade process undoes or rolls back data manipulation to the previous commit statement. The upgrade keeps track of the last successful callout. When you resume the upgrade, all processing is bypassed until it reaches the last successful callout and continues from there. Press Enter to resume the upgrade.

Page 69: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

© Copyright IBM Corp. 2007, 2013 65

Verifying the install.properties values

Check your install.properties file to ensure that the database property values are correct.

Ensure that the following properties point to the correct upgraded database:

Database.type.ServerHostName=valueDatabase.type.ServerPort= valueDatabase.type.DatabaseName= value (for DB2 and SQL)Database.Oracle.InstanceName= value (for Oracle)

Also check the properties in the database, by using the System Properties application, to ensure that the values match.

For example, if you upgraded to Maximo Asset Management 7.1 and use a DB2 database, ensure the property values point to the upgraded 7.1 database, similar to the following values:

Database.DB2.ServerHostName=9.6.127.235Database.DB2.ServerPort=50000Database.DB2.DatabaseName=MAXIMO

Updating the Maximo database

Ensure that the Maximo 7 database is at the latest version. To update the database to the latest version:

1 Back up your newly upgraded database.

2 From a command prompt, change directory to Maximo_root\tools\maximo.

3 Run updatedb.bat.

4 Back up the updated database.

Completing the upgrade process 4

Page 70: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reviewing your upgraded screens

66 IBM Maximo: Upgrade Guide

Reviewing your upgraded screens

If you customized any screens in version 6, review your upgraded screens after the upgrade. Use the Application Designer application in version 7 to make additions or adjustments to the upgraded screens.

You might decide to keep the upgraded screen configurations only for some applications and use the default version 7 screens for other applications.

Keeping upgraded screen configurations for selected applications

To keep upgraded screen configurations for some applications, and to use the default version 7 screens for other applications, you use the base7.xml file. This file contains the default version 7 screen definitions. It is located in the Maximo_root/tools/maximo/screen-upgrade folder. Upg7.xml is in the same folder and contains the upgraded screen definitions.

To keep screen configurations for selected applications:

1 Run the upgrade utility using the default behavior to upgrade all your screen configurations.

2 After the upgrade, make a copy of the base7.xml file, base7copy.xml, for example.

3 Open the base7copy.xml file in a text editor.

4 By application, delete the default version 7 screen presentation definitions that you do not want to use.

5 Save your changes and close the copied file.

6 Open the Application Designer application in version 7.

7 Import the edited, copied file (base7copy.xml, in the example).

The default version 7 screen definitions that remain in base7copy.xml are applied to the database. These default screen definitions overwrite the upgraded, customized screen presentation definitions.

Use the Application Designer to change the default screens and the upgraded customized screens.

Performing database administration tasks

Database administration consists of the following tasks:

Reorganizing and resizing the data filesTurning on transaction logging

Page 71: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reviewing custom relationships

Completing the upgrade process 67

After you upgrade Maximo, the tablespace can be up to five times its original size. Condense the Maximo tablespace and condense the data files after you upgrade Maximo.

Reorganizing and resizing data files

In Oracle, you use the Export/Import utility. Complete the following steps to reorganize and resize data files:

1 Export the Maximo schema.

2 Drop the Maximo schema.

3 Resize the data files of the tablespace. One option is to use the alter database datafile resize command.

4 Create the Maximo user.

5 Import the Maximo schema from the file that was created in step 1.

For more information, see the Oracle Utilities guide.

Turning on Redo Log Archiving (Oracle)

Create a full backup of your database and turn on redo log archiving before you go into production.

Changing to Full Recovery Model (Microsoft SQL Server)

Create a full backup of your database and change to full recovery model before you go into production.

Reviewing custom relationships

Review all custom relationships—table relationships that you modified or added—to ensure that they use version 7 table and column names.

The upgrade process updates core relationships and custom relationships. But the upgrade process does not change WHERE clauses in your custom relationships.

For information about Maximo 6 tables that are not present in the version 7 database, see the following table.

Maximo 6 tables that are not in version 7

Maximo 6 table Comment

ASSETCUST A table view. No data mapping by the upgrade utility is needed.

Page 72: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reviewing table domains and crossover domains

68 IBM Maximo: Upgrade Guide

You must edit any custom relationships that name any of the tables that were referenced in version 6, but that do not exist in version 7. Ensure that you examine all custom relationships.

Use the Database Configuration application to respecify the table and column information with the new version 7 table and column names.

Reviewing table domains and crossover domains

Review all custom crossover domains and table domains. If you added or modified any crossover domains or table domains, review their WHERE clauses. Ensure that the WHERE clauses use the version 7 table and column names.

If necessary, use the Database Configuration application to respecify the table and column information. You must edit any custom domains that name any of the tables that were referenced in version 6, but that do not exist in version 7. Ensure that you examine all custom crossover and table domains.

GROUPRESTRICTION Dropped by the upgrade utility. Data is mapped to the SECURITYRESTRICTIONS and CONDITION tables in version 7.

MAXADAPTERINST A nonpersistent table. No data mapping by the upgrade utility is needed.

MAXADPTINSTDET A nonpersistent table. No data mapping by the upgrade utility is needed.

MAXAVLINSADAPTER A nonpersistent table. No data mapping by the upgrade utility is needed.

MAXIFACE Dropped by the upgrade utility. Data is mapped to the MAXIFACEIN and MAXIFACEOUT tables in version 7.

MAXIFACETBPROPS A nonpersistent table. No data mapping by the upgrade utility is needed.

MAXIFACETYPE Dropped by the upgrade utility. Data is mapped to the MAXIFACEIN table in version 7.

MAXINTMSGTYPE Dropped by the upgrade utility. Functionality is reimplemented in the MESSAGETYPE domain in the ALNDOMAIN table in version 7.

MAXINTPOINT Dropped by the upgrade utility. Data is mapped to the MAXIFACEOUT and MAXINTOBJECT tables in version 7.

MAXINTWSPROPS Dropped by the upgrade utility. Data is mapped to the MAXPROP table in version 7.

TICKETASSET Dropped by the upgrade utility. Data is mapped to the MULTIASSETLOCCI table in version 7.

Maximo 6 table Comment

Page 73: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Validating upgraded restrictions

Completing the upgrade process 69

Validating upgraded restrictions

Group restrictions that existed in version 6 are replaced by data restrictions in version 7. In version 6, the group entity and condition were stored in a common table. In version 7, data restrictions split this information across multiple tables. There are multiple types of data restrictions in version 7, which provides more flexibility in the ways that data can be displayed.

Conditions that were used in version 6 data restrictions are migrated to the new CONDITION table by the upgrade process. The new Conditional Expression Manager application in version 7 provides you access to the conditions so that you can view and manage them. Group restrictions are also migrated by the upgrade to data restrictions. Data restrictions are stored in the SECURITYRESTRICT table, and are managed in the Security Groups application.

Because there are many types of data restrictions in version 7, and only a single type of group restriction in version 6, you must validate the syntax of the conditions and the types of the restrictions to ensure that they behave like you want them to.

See the version 7 System Administrator Guide for information about condition syntax and data restrictions.

Re-enabling audit functions

Because version 7 products configure the database based on objects and attributes instead of tables, you must re-enable each object for electronic audit.

The upgrade program maintains all of your audit tables and audit data, but because your audit tables no longer match the version 6 database, you cannot use the existing audit tables. You must use the Database Configuration application to create a new audit table for each object.

Reviewing version 7 planned attribute changes in work-order-based applications

In version 6, if you used the Move/Modify action in work-order-based applications to modify asset or location specification attributes, a permanent record of the changes was saved. A record was written to the AutoAttrUpdate table when the plan was saved. When the plan was executed, the record remained in the AutoAttrUpdate table. Those version 6 records remain in the AutoAttrUpdate table after the upgrade process.

In version 7, planned attribute change records are written to the AutoAttrUpdate table. However, in version 7, the records are deleted after the changes are executed. The records are not stored permanently.

Therefore, in version 7, the AutoAttrUpdate table can contain a mix of permanent records from version 6 and newer, temporary records from version 7.

Page 74: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Reviewing IBM Global Services applications

70 IBM Maximo: Upgrade Guide

There is no action for you to take. Simply be aware of the new way of treating new records in the AutoAttrUpdate table in version 7. The change might affect you only if you used the historical AutoAttrUpdate records for reporting or querying.

Reviewing IBM Global Services applications

The upgrade process does not support upgrading of IBM Global Services applications.

Field control

The features provided by the version 6 Field Control add-on are incorporated into the core features of version 7 products. For information about how and when you can move your Field Control configurations forward to version 7, see the following online tech note: Field Control and Domains, Data Restrictions, Conditional UI, Conditional Application Options, and Conditional Domains.

You can manually upgrade the Field Control add-on yourself, or you can use IBM Global Services to upgrade Field Control for you.

Updating statistics

In Oracle, system administration tasks include analyzing table commands. Analyze all tables to ensure that the Oracle Cost-Based Optimizer has up-to-date statistics.

1 Sign into the Maximo application.

2 Open the Database Configuration application.

3 From the Select Action menu, select Update Statistics, and then click OK to continue.

Associating existing document types (folders) with new version 7 applications

The Associate Folders action lets you select the folders of documents to be included in the document collection of an application. Associate document folders with an application so that you can attach documents in those folders from within that application. You can only modify folders in the document collection of the current application.

You must have appropriate security authority to access this feature. Typically, a system administrator adds document folders.

By default, the titled attachments, images, and diagrams of the folder are included with every application that has attached documents.

Page 75: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Adding new applications to security groups

Completing the upgrade process 71

When you create a folder, the folder is associated with the application where it was created.

To associate a folder with another application, associate the folder from the additional application.

To associate a document folder with an application:

1 Sign into the Maximo application.

2 Open any application that has Attached Documents actions.

3 From the Select Action menu, choose Attachments Library/Folders.

4 Click Associate Folders.

5 Click New Row.

6 In the Document Folder field, specify a value for a defined folder.

The Document Folder Description field displays a description of the selected folder. The name of the application that you are working in is displayed in the Application field.

7 Choose one of the following options:

To add another row, click New Row.To close the Row Details, click the down arrow.To mark the row for deletion, click the trash can icon.To cancel the changes and return to the application tab, click Cancel.Click OK to save changes and return to the application tab.

Adding new applications to security groups

To ensure that your users have access to new applications, add the applications that you intend to use to your security groups.

Completing the Maximo Enterprise Adapter upgrade process

The following list provides an overview of the post-upgrade tasks for the Maximo Enterprise Adapter:

Enabling the integration framework applications

Configuring the continuous queue

Configuring the sequential queue cron task

Selecting the Support Flat Structure check box in the object structure records

Page 76: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo Enterprise Adapter upgrade process

72 IBM Maximo: Upgrade Guide

Enabling the integration framework components

Creating the interface tables

Updating the external system endpoint

Configuring the system properties

Creating the nonpersistent business objects

Enabling the event listeners

Redeploying the Web services

Updating the XML format

Updating the HTTP entry point

Reviewing any customizations and external system processing

Reviewing any processing rules

Associating integration controls to enterprise services and publish channels

If you are upgrading the SAP ERP adapter or the Oracle ERP adapter (sections that follow), you must still complete this section. Ensure that the configurations you specify in each section are compatible.

Enabling the integration framework applications

You must define the appropriate security options to each integration framework application. You also can grant access privileges to the options in each application.

For more information about granting access privileges to applications, see the online help in the Security Groups application.

Configuring the continuous queue

The message beans that are used by the continuous queue definition are not enabled by default. You can enable the message beans by working with the message bean configuration in the application server deployment files.

For more information about enabling message beans, see the JMS queue configuration information in the Integration Guide.

Page 77: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo Enterprise Adapter upgrade process

Completing the upgrade process 73

Configuring the sequential queue cron task

The sequential queue is a Java Message Service (JMS) queue that has a system cron task as a consumer. You can configure two system sequential queues for inbound and outbound message processing. A predefined cron task, JMSQSEQCONSUMER, polls the queues. There are two instances of the task, one that polls the inbound queue and one that polls the outbound queue.

For more information about enabling the JMSQSEQCONSUMER cron task for sequential queue-based message processing, see the JMS queue configuration information in the Integration Guide.

Selecting the Support Flat Structure check box in the object structure

You must select the Support Flat Structure check box on the object structure record when your integration processing scenarios require flat file or interface table data.

For more information about selecting the Support Flat Structure check box, see the online help in the Object Structures application.

Enabling the integration framework components

When you enable integration components, all inbound and outbound messages can be processed to and from Maximo. The integration framework accepts inbound messages, sends outbound messages, and permits the use of the Data Export and Data Import features.

You must enable the following integration framework components: external systems, publish channels, and enterprise services.

For more information about enabling external systems, publish channels, and enterprise services, see the online help in the External Systems application.

Creating the interface tables

Interface tables are not created by default. To create interface tables, specify the endpoint that uses an interface table handler. The endpoint identifies where Maximo creates the interface tables. The predefined endpoint uses the Maximo database. You can set up new endpoints to create interface tables on a database that differs from the Maximo database.

For more information about creating interface tables, see the online help in the External Systems application.

Updating the external system endpoint

If your integration scenarios rely on interface table processing, you must update the endpoint that is associated with an external system.

Page 78: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo Enterprise Adapter upgrade process

74 IBM Maximo: Upgrade Guide

After the upgrade, the external systems that used interface table endpoints in version 6 are assigned endpoints that implement the XMLHANDLER handler. To enable external systems to work with interface tables, you must specify an endpoint that implements an interface table handler, for example IFACETABLE.

For more information about assigning endpoints to external systems, see the online help in the External Systems application.

Configuring the system properties

You must configure and update the following system properties when you complete the upgrade process. You can update these properties in the System Properties application.

mxe.int.webappurl - You must update the default value that is associated with the Web application URL. The updated value must include the port number that your application server is configured to use.

For example, the value http://localhost/meaweb must be changed to http://localhost:7001/meaweb.

mxe.int.<adaptername>.convert6to7ml - If you need the integration framework to support the processing of Maximo 6 XML files, you must set this property value to 1 (true). The true value instructs the integration framework to convert any inbound message from a version 6 to version 7 XML format, and any outbound message from a version 7 to a version 6 XML format. The default value of this property is 0 (false).

Creating the nonpersistent business objects

In version 6, a merged integration object provided a mechanism to support multiple primary-level Maximo business objects (matrectrans and servrectrans) within a single transaction (receipt). An example of a merged integration object is the MXRECEIPT, which contains the Maximo business objects matrectrans (material receipts) and servrectrans (service receipts).

In version 7, object structures that are based on nonpersistent business objects provide processing capabilities that are equivalent to the version 6 merged integration objects.

The upgrade utility changes the merged integration objects to nonpersistent object structures. However, the upgrade utility does not convert version 6 custom merged integration objects.

To convert your version 6 custom merged integration objects:

1 In version 7, create a nonpersistent business object that contains a list of unique attributes that is based on the original Maximo business objects, for example, matrectrans and servrectrans.

2 Create an object structure and add the new business object. Include the applicable nonpersistent columns on the object structure.

Page 79: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo Enterprise Adapter upgrade process

Completing the upgrade process 75

3 Create an enterprise service using the new object structure to process inbound messages, or a publish channel using the new object structure to process outbound messages.

4 Add the enterprise service and publish channel to the appropriate external system.

If you are using the object structure to bring data into Maximo, you must provide an object structure processing class that examines the inbound message and creates the appropriate Maximo business object, for example, matrectrans or servrectrans. The framework then maps the inbound message to the created Maximo business object.

If you are using the object structure to send data out of Maximo, you must provide a publish channel event filter class. This class identifies the Maximo business object that the listener monitors for events, for example, matrectrans or servrectrans. The framework then maps the outbound message from the Maximo business object that the event filter class identifies.

To create a nonpersistent business object:

1 Open the Database Configuration application.

2 In the Object tab, click New Object.

3 Enter a name in the Object field.

4 Clear the Persistent check box.

5 In the Attributes tab, create the attributes that are associated with the nonpersistent business object.

Each of the associated attributes must be linked to a persistent attribute and to its corresponding objects. To establish this correlation, you must enter a persistent business object value in the Same as Object field and its corresponding attribute value in the Same as Attribute field.

Enabling the event listeners

Publish channel event listeners are not enabled by default. You enable a publish channel listener to direct the integration framework to build and process the selected publish channel.

When the listener is enabled, it monitors the system for activities on the corresponding publish channel primary object. The publish channel processing is initiated when you or the Maximo system changes any instance of the associated object.

For more information about how to enable listeners, see the online help in the Publish Channels application.

Redeploying the Web services

Web services are not deployed by default. After the upgrade, you must deploy all Web services that you use as part of your integration. When you deploy a Web

Page 80: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo Enterprise Adapter upgrade process

76 IBM Maximo: Upgrade Guide

service, the schema and Web Service Description Language (WSDL) files for the Web service are deleted and regenerated.

For more information about deploying Web services, see the online help in the Web Services Library application.

Updating the XML format

After the upgrade, all transactions must comply with a version 7 XML format. When the XML format is not updated on the enterprise adapters and user-defined adapters, the integration framework can transform version 6 transactions into a version 7 XML format.

Updating the HTTP entry point

If your messages are processed using HTTP protocols, you must reconfigure your inbound transaction processes to point to a specific entry point that corresponds to the enterprise service.

In version 7, the concept of adapter has changed. You can use an adapter as a mechanism to group enterprise services. Adapters no longer require interpretation properties. You must specify the external system and enterprise service name as part of the URL.

You can use the following URL to post the messages to enterprise services that process messages:

http://hostname:port/meaweb/esqueue/extsysname/enterprise service name

extsysname is the name of the external system.

enterprise service name is the name of the enterprise service.

Support for a single global URL

In version 7, you can use the provided global URL when your inbound transaction processes require the use of a version 6 XML and a single URL for all messages. You can continue to use a single URL for Maximo services that you invoke from your external system.

The global URL maintains your version 6 integration processes in version 7. You must update your integration processes to support individual enterprise service URLs before you upgrade to the next release.

In version 7, the integration framework servlet is updated to provide single URL capabilities to support the use of the enterprise adapters, such as Oracle and SAP. The servlet also supports user-defined adapters that work with a global URL to exchange messages with the integration framework.

The changed servlet code identifies the SENDER and the INTERFACE information. The servlet code also identifies where the transaction is posted in the URL.

Page 81: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the SAP ERP adapter upgrade process

Completing the upgrade process 77

If the URL does not include an external system name and an enterprise service name, the servlet code checks the HTTP header for the SENDER and INTERFACE parameters. If the HTTP header parameters do not exist, the servlet code checks for a registered class file in the web.xml file. The registered class file determines the values of the SENDER and INTERFACE parameters in the received transaction payload. The inputs to this class are the HttpServletRequest object and the message payload.

Reviewing customizations and external system processing

After the upgrade, you must review and retest the XSL and Java class customizations to ensure that your customizations work as designed. Depending on the amount of changes, you may need to alter your customized code. You also must review and test external system data processing to ensure it works as designed.

Reviewing processing rules

After the upgrade, you must review any processing rules that you implemented in version 6. If the processing rules reference a control that the upgrade utility deleted, the processing rules may be deleted.

Associating integration controls with enterprise services and publish channels

After the upgrade, you must review the association of your integration controls with the enterprise services and publish channels. The upgrade utility does not update the associations for custom controls or custom interfaces. You must review all your control associations and corresponding default control and external system values.

Completing the SAP ERP adapter upgrade process

Completing the SAP ERP adapter upgrade process includes the following tasks:

Configuring the SAP ERP adapter in Maximo

Adding a service identifier class to the web.xml file in Maximo

Configuring the communication channel for the new service in SAP Process Integration

Ensure that the configurations you specify in this section are compatible with those you specified in “Completing the Maximo Enterprise Adapter upgrade process‚" page 71.

Adding a service identifier class to the web.xml file in Maximo

After you install the SAP ERP adapter, you must modify the web.xml file and add a service identifier class.

Page 82: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the SAP ERP adapter upgrade process

78 IBM Maximo: Upgrade Guide

1 Open the web.xml file, which is located at:

applications\maximo\meaweb\webmodule\WEB-INF\web.xml

2 Add the following entry to the content of <web-app>:

<!-- Service Identifier class for SAP Adapter -->

<env-entry>

<description>Service Identifier class for SAP Adapter</description>

<env-entry-name>SRVICEIDENTIFIERCLASS</env-entry-name>

<env-entry-type>java.lang.String</env-entry-type>

<env-entry-value>psdi.iface.servlet.SAPServiceIdentifier</env-entry-value>

</env-entry>

3 Save the web.xml file.

4 Rebuild and deploy the maximo.ear file.

5 Start the application server.

6 Sign in to Maximo to ensure that the Maximo application server started successfully.

For information about how to build and deploy EAR files, refer to IBM Maximo Asset Management System Administrator Guide.

Configuring the SAP ERP adapter in Maximo

As part of installing the SAP ERP adapter, you must complete configuration tasks in Maximo. To complete these tasks, you must log in to Maximo with system administrator rights and authorities.

Specifying the endpoint for the SAP ERP adapter

The end point defines where and how you send transactions to SAP.

Configure the SAP Exchange Infrastructure server as the endpoint for the SAP ERP adapter. The endpoint that you configure uses an HTTP Post handler. The handler that the endpoint uses describes how the SAP ERP adapter sends transactions to SAP.

To specify the endpoint for the SAP ERP adapter:

1 Open the End Points application:

Go To > Integration > End Points

2 On the List tab, select the SAPXI endpoint or the new SAP2005XI endpoint.

Page 83: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the SAP ERP adapter upgrade process

Completing the upgrade process 79

3 On the End Point tab, specify the following values for the properties of the endpoint:

4 Click Save.

Enabling the SAP2005 external system

After you install the SAP ERP adapter you will have the old SAP1 system name and the new SAP2005 system name. You have the option to enable the new SAP2005 external system. If you choose to use the new external system name your existing records in Maximo will not match the external system and you will need to set your integration control values for this new external system name.

To enable the SAP2005 external system:

1 Open the External Systems application:

Go To > Integration > External Systems

2 On the List tab, select the SAP2005 external system.

3 On the System tab, select the Enabled check box.

Configuring the communication channel for the new service in SAP Process Integration

You must modify the GeneratedReceiverChannel_HTTP communication channel for the Maximo service that you created.

To configure the communication channel for Maximo:

1 In the Objects tab of the Integration Builder window, expand the Maximo business system.

2 Double-click GeneratedReceiverChannel_HTTP.

3 Add the HTTP channel details for the connection to Maximo. HTTP is the default communication channel between SAP and other systems.

XI has four possible communication channels:

HTTPIDocRFCXI

Property Value

HTTPEXIT Use the default value.

PASSWORD The password of the SAP XI user (in the Encrypted Value field)

USERNAME The SAP Exchange Infrastructure user name

URL The SAP Exchange Infrastructure host and, if necessary, the port

Page 84: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

80 IBM Maximo: Upgrade Guide

The SAP ERP adapter uses only HTTP to communicate with Maximo.

The value in the Target Host field comes from the technical system that you defined in the System Landscape Directory.

4 Switch to edit mode by clicking the pencil icon.

5 In the Parameters tab of the Edit Communication Channel pane, specify the following connection parameters for the communication channel, GeneratedReceiverChannel_HTTP, and Maximo service:

6 Click Save and close the Edit Communication Channel pane.

For more information about SAP ERP adapter, see the IBM Maximo Enterprise Adapter System Administrator Guide for SAP ERP 6.0 Adapter.

Completing the Oracle ERP adapter upgrade process

After the upgrade utilities program runs, you perform the tasks that enable the Oracle ERP adapter to integrate Maximo Asset Management and Oracle E-Business Suite.

The following list provides an overview of the tasks that you perform to complete the adapter upgrade process:

Configuring the Oracle ERP adapter

Installing PL/SQL objects

Field Value

Service Number

(The SAP ERP adapter part of the installation uses this port number.)

Maximo port number

Path /meaweb/esqueue/externalsystemname

Authentication Data Authentication Type

Logon Data for Non-SAP System.

Authentication Data User Name

(The MAXVAR.MXINTDBUSER column stores this value. You can configure it.)

mxintadm

Authentication Data User Password

(In practice, this value is typically the same as the user name.)

Page 85: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 81

Synchronizing data between Oracle and Maximo

Creating and running concurrent requests

(Optional) Configuring the Projects integration

Ensure that the configurations you specify in this section are compatible with those you specified in “Completing the Maximo Enterprise Adapter upgrade process‚" page 71.

Configuring the Oracle ERP adapter

You must configure your adapter to transform data from the Maximo Asset Management format to a format that is compatible with the Oracle E-Business Suite format.

Adding support for flat structure

If you use the object structure in interface tables or flat files, you must enable the support for flat structure. After you enable this support, the objects are checked for duplicate column names in the object structure. Duplicate column names produce errors.

To enable the support for flat structure:

1 Select Go To > Integration > Object Structures.

2 Select the Support Flat Structure check box for the following object structures.

3 Click Save.

4 If duplicate column names exist, select Add/Modify Alias from the Select Action menu to change the alias name.

Verifying and associating the endpoint for the Oracle ERP adapter

The endpoint defines where and how you send outbound transactions to the Oracle E-Business Suite external system. After you run the upgrade utilities program, you must update the endpoint for the Oracle ERP adapter 7.1.

The following task uses OAExtSys as the external system name; however, you might continue using the name that you used in the previous release of the adapter.

MXCOA MXITEMMXCRAFT MXLABORMXGLCOMP MXPCMXGLTXN MXPOMXINVBAL MXPRMXINVENTORY MXPROJMXINVISSUE MXRCVROTITMMXINVOICE MXRECEIPTMXINVRES MXVENDOR

Page 86: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

82 IBM Maximo: Upgrade Guide

To verify and associate the endpoint:

1 Select Go To > Integration > End Points.

2 Select the endpoint that you used in the previous release of the Oracle ERP adapter.

3 Verify the following information:

4 Click Save End Point.

5 Select Go To > Integration > External Systems.

6 Associate the endpoint with OAExtSys.

7 Click Save External System.

Enabling publish channels

The integration framework uses the publish channel to transform data from the Maximo Asset Management format to an external format that is compatible with Oracle E-Business Suite.

The following task uses OAExtSys as the external system name; however, you might continue using the name that you used in the previous release of the adapter.

To enable publish channels:

1 Select Go To > Integration > External Systems.

2 Press Enter to display a list of external systems.

3 Click OAExtSys to display information about the Oracle E-Business Suite external system in the System tab.

4 Display all the publish channels by selecting the Publish Channels tab.

5 Clear the Enabled check box for any publish channels that you do not use for your integration.

6 Click Save External System.

Description Oracle Adapter 12 Upgrade EndpointISREMOTE 1URL jdbc:oracle:thin:[server-name]:[port-number]:[database-instance]

[server-name] is where Oracle E-Business Suite is hosted

[port-number] is the database port number

[database-instance] is the Oracle database instanceDriver oracle.jdbc.driver.OracleDriverUsername maxoraPassword maxora

Page 87: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 83

7 Enable the integration events for the publish channels that you want to use:

a Select Go To > Integration > Publish Channels.

b Filter the records by OA12 in the Adapter field.

c Select the Select Records check box and mark the publish channels that you want to use.

d From the Select Action menu, select Enable Event Listener.

Setting up the new integration controls

Integration controls give you the ability to override the behavior of certain predefined publish channel or enterprise service processing and to configure them according to the requirements of your organization and sites. You must set up the new integration controls of the Oracle ERP adapter.

The following task uses OAExtSys as the external system name; however, you might continue using the name that you used in the previous release of the adapter.

To set up your new integration controls:

1 Select Go To > Integration > External Systems.

2 Select the OAExtSys external system record.

3 From the Select Action menu, select Setup Integration Controls.

4 Click Save External System.

For a list of the new integration controls, see “Integration controls‚" page 158.

Setting active default item status

When you are sending item transactions to Maximo Asset Management, set the default item status to active.

To set the default item status to active:

1 Select Go To > Administration > Sets.

2 For each Item Set row, change the default item status to Active.

3 Click Save Set.

4 Select Go To > Administration > Organizations.

5 For each Organization row, change the default item status to Active.

6 Click Save Organization.

Page 88: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

84 IBM Maximo: Upgrade Guide

Enabling the blanket purchase order update

The Oracle Open interfaces use the PO_HEADER_ALL.VENDOR_ORDER_NUM column to identify and update the blanket purchase orders that Oracle E-Business Suite receives.

If you want to update open blanket purchase orders in version 7 of Maximo Asset Management, you must enter PO_HEADER_ALL.VENDOR_ORDER_NUM for the blanket purchase orders in Oracle E-Business Suite.

To enable the blanket purchase order update:

1 In Oracle E-Business Suite, identify the Maximo Asset Management blanket purchase orders that are in OPEN status.

2 Update the PO_HEADER_ALL.VENDOR_ORDER_NUM column with the value that is in PO_HEADERS_ALL.Segment1 for the blanket purchase order.

Installing PL/SQL objects

When you install and set up the adapter on the Oracle side of the integration, you must drop the previous integration schema and create another schema in the Oracle E-Business Suite database. You also must configure installation-dependent parameters, create interface tables, install packages, procedures, triggers, and objects in the database, update the external system value, and verify and fix installation errors.

Dropping the previous Oracle E-Business Suite integration schema

Before you create the Oracle E-Business Suite 12 integration schema, you must drop the previous integration schema.

To drop the previous schema, log on to the Oracle E-Business Suite database as a database administrator and run the following command:

drop user [previous maxora schema name] cascade;

The command must contain the schema that you used for the Oracle E-Business Suite 11i database integration.

Creating the Oracle E-Business Suite 12 integration schema

You must create a schema for managing the integration framework in the Oracle E-Business Suite database. You can create multiple integration schemas on the same database instance to support multiple Maximo Asset Management application servers.

The following task uses MAXORA as the Oracle E-Business Suite integration schema user name; however, you can choose any name for your schema owner.

To create the Oracle E-Business Suite integration schema:

1 In the Maximo_root\ORACLEAPIS\install directory, open the cremxora.sql file.

2 Replace all instances of MAXORA with your integration schema name.

Page 89: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 85

3 Replace all instances of USER_DATA with your tablespace name.

4 Save the cremxora.sql file.

5 Launch SQL * Plus and connect to the Oracle E-Business Suite database as a database administration user.

6 Create and grant privileges to the integration schema by entering the following command:

SQL > start Maximo_root\ORACLEAPIS\install\cremxora <Enter>

7 Review and correct any errors that you see on the screen.

For a list of the Maximo Asset Management objects in the MAXORA schema, see the following topic, “MAXORA schema objects".

MAXORA schema objects

There are a number of Maximo Asset Management objects that are created in the MAXORA schema by the Oracle ERP adapter.

You should not drop, modify, move, or have additional grants issued for objects listed below even though they are mentioned in this report.

The following table shows a list of the Maximo Asset Management objects in the MAXORA schema:

Object name Object typeAPILOG SEQUENCEAPI_APX_SP PROCEDUREAPI_BAL_SP PROCEDUREAPI_GLCC_PKG PACKAGE BODYAPI_GLCC_PKG PACKAGEAPI_GLCC_SP PROCEDUREAPI_GLCC_TRG TRIGGERAPI_GLCOMP_DESC_TRG TRIGGERAPI_GLCOMP_SP PROCEDUREAPI_GLCOMP_TRG TRIGGERAPI_INVCAPPR_SP PROCEDUREAPI_INVCAPPR_TRG TRIGGERAPI_INVC_TRG TRIGGERAPI_INV_SP PROCEDUREAPI_ITEM_PKG PACKAGE BODYAPI_ITEM_PKG PACKAGEAPI_ITEM_SP PROCEDUREAPI_LC_PA_SP PROCEDUREAPI_LC_SP PROCEDUREAPI_LOC_PKG PACKAGE BODYAPI_LOC_PKG PACKAGE

Page 90: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

86 IBM Maximo: Upgrade Guide

API_MTLBAL_TRG TRIGGERAPI_MTLISU_SP PROCEDUREAPI_MTLITMTL_TRG TRIGGERAPI_MTLITM_TRG TRIGGERAPI_PA_COMPENSATION_TRG TRIGGERAPI_PA_EMPLOYEE_TRG TRIGGERAPI_PCX_SP PROCEDUREAPI_PC_SP PROCEDUREAPI_POACTION_TRG TRIGGERAPI_POACT_PKG PACKAGEAPI_POACT_PKG PACKAGE BODYAPI_POAPPR_SP PROCEDUREAPI_POAPPR_TRG TRIGGERAPI_POIMP_TRG TRIGGERAPI_POLINE_SP PROCEDUREAPI_POLINE_TRG TRIGGERAPI_POLX_SP PROCEDUREAPI_POREL_TRG TRIGGERAPI_POX_SP PROCEDUREAPI_PRIMP_TRG TRIGGERAPI_PR_SP PROCEDUREAPI_PUT_ERROR_SP PROCEDUREAPI_RCVROT_SP PROCEDUREAPI_RCV_SERIAL_TRG TRIGGERAPI_RCV_SP PROCEDUREAPI_RECEIPT_TRG TRIGGERAPI_VNDCONTUPD_SP PROCEDUREAPI_VNDCONTUPD_TRG TRIGGERAPI_VNDCONT_SP PROCEDUREAPI_VNDCONT_TRG TRIGGERAPI_VNDHDR_TRG TRIGGERAPI_VNDSITE_TRG TRIGGERAPI_VND_SP PROCEDUREAP_INVOICES_ALL SYNONYMAP_INVOICES_INTERFACE SYNONYMAP_INVOICES_INTERFACE_S SYNONYMAP_INVOICE_DISTRIBUTIONS SYNONYMAP_INVOICE_DISTRIBUTIONS_ALL SYNONYMAP_INVOICE_LINES_INTERFACE SYNONYMAP_INVOICE_LINES_INTERFACE_S SYNONYMAP_SUPPLIERS SYNONYMAP_SUPPLIER_CONTACTS SYNONYM

Object name Object type

Page 91: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 87

AP_SUPPLIER_SITES_ALL SYNONYMAP_TAX_CODES SYNONYMAP_TERMS SYNONYMCREATE_DEBUG_SP PROCEDURECREATE_INSERT_SP PROCEDURECREATE_TRIGGER_SP PROCEDURECST_ITEM_COSTS SYNONYMCST_QUANTITY_LAYERS SYNONYM

CVROTITM_IFACE_NDX INDEX

ENTERPROC PROCEDURE

EXTRACT_FC_DATA PROCEDURE

FA_CATEGORIES SYNONYM

FINANCIALS_SYSTEM_PARAMETERS SYNONYM

FND_API SYNONYM

FND_APPLICATION_VL SYNONYM

FND_FILE SYNONYM

FND_FLEX_VALUES SYNONYM

FND_FLEX_VALUES_TL SYNONYM

FND_ID_FLEX_SEGMENTS SYNONYM

FND_ID_FLEX_STRUCTURES SYNONYM

FND_LANGUAGES SYNONYM

FND_MSG_PUB SYNONYM

FND_PRODUCT_GROUPS SYNONYM

FND_PROFILE_OPTIONS SYNONYM

FND_PROFILE_OPTION_VALUES SYNONYM

FND_USER SYNONYM

GET_OPERID_SP PROCEDURE

GET_PA_ORGID_SP FUNCTION

GL_CODE_COMBINATIONS SYNONYM

GL_INTERFACE SYNONYM

GL_LEDGERS SYNONYM

GL_SETS_OF_BOOKS SYNONYM

HR_ALL_ORGANIZATION_UNITS SYNONYM

HR_EMPLOYEES SYNONYM

HR_LOCATIONS SYNONYM

HR_LOCATIONS_ALL SYNONYM

HR_OPERATING_UNITS SYNONYM

HZ_CONTACT_POINTS SYNONYM

HZ_LOCATIONS SYNONYM

HZ_ORG_CONTACTS SYNONYM

HZ_PARTIES SYNONYM

HZ_PARTY_SITES SYNONYM

HZ_RELATIONSHIPS SYNONYM

INVISSUE_IFACE_NDX INDEX

Object name Object type

Page 92: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

88 IBM Maximo: Upgrade Guide

IN_INTER_TRANS_NDX INDEX

IS_PARENT_REJECTED FUNCTION

MAXAPIDEBUG PACKAGE BODY

MAXAPIDEBUG PACKAGE

MAXAPIERRORS PACKAGE

MAXAPIERRORS PACKAGE BODY

MAXAPIINSERT PACKAGE BODY

MAXAPIINSERT PACKAGE

MAXAPISET PACKAGE BODY

MAXAPISET PACKAGE

MAXAPITRIGGER PACKAGE BODY

MAXAPITRIGGER PACKAGE

MAXDEBUGAPI PACKAGE BODY

MAXDEBUGAPI PACKAGE

MAXIFACETRANSSEQ SEQUENCE

MAXORACTLS TABLE

MAXORACTLS_TRG TRIGGER

MAXORALOG TABLE

MAXPCPACK PACKAGE BODY

MAXPCPACK PACKAGE

MAXPOPACK PACKAGE BODY

MAXPOPACK PACKAGE

MAXSEQ SEQUENCE

MAXUTLPACK PACKAGE BODY

MAXUTLPACK PACKAGE

MOF_USR_APX_SP PROCEDURE

MOF_USR_AP_SP PROCEDURE

MOF_USR_BAL_SP PROCEDURE

MOF_USR_COA_SP PROCEDURE

MOF_USR_FC_SP PROCEDURE

MOF_USR_GLCOMP_SP PROCEDURE

MOF_USR_INV_SP PROCEDURE

MOF_USR_ISU_SP PROCEDURE

MOF_USR_ITM_SP PROCEDURE

MOF_USR_LC_PA_SP PROCEDURE

MOF_USR_LC_SP PROCEDURE

MOF_USR_PCX_SP PROCEDURE

MOF_USR_PC_SP PROCEDURE

MOF_USR_POLX_SP PROCEDURE

MOF_USR_POX_SP PROCEDURE

MOF_USR_PO_SP PROCEDURE

MOF_USR_PR_SP PROCEDURE

MOF_USR_RCVROT_SP PROCEDURE

MOF_USR_RCV_SP PROCEDURE

MOF_USR_VNDCONT_SP PROCEDURE

Object name Object type

Page 93: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 89

MOF_USR_VND_SP PROCEDURE

MO_GLOBAL SYNONYM

MTL_CATEGORY_SET_VALID_CATS SYNONYM

MTL_DEFAULT_CATEGORY_SETS SYNONYM

MTL_DEFAULT_SETS_VIEW SYNONYM

MTL_DEMAND SYNONYM

MTL_ITEM_CATEGORIES SYNONYM

MTL_ITEM_LOCATIONS SYNONYM

MTL_MATERIAL_TRANSACTIONS SYNONYM

MTL_MATERIAL_TRANSACTIONS_S SYNONYM

MTL_ONHAND_QUANTITIES SYNONYM

MTL_PARAMETERS SYNONYM

MTL_PHYSICAL_ADJUSTMENTS SYNONYM

MTL_RESERVATIONS_INTERFACE SYNONYM

MTL_RESERVATIONS_INTERFACE_S SYNONYM

MTL_SECONDARY_INVENTORIES SYNONYM

MTL_SERIAL_NUMBERS_INTERFACE SYNONYM

MTL_SYSTEM_ITEMS SYNONYM

MTL_SYSTEM_ITEMS_INTERFACE SYNONYM

MTL_SYSTEM_ITEMS_TL SYNONYM

MTL_TRANSACTION_ACCOUNTS SYNONYM

MTL_TRANSACTION_LOTS_INTERFACE SYNONYM

MTL_TRANSACTION_LOT_NUMBERS SYNONYM

MTL_TXN_SOURCE_TYPES SYNONYM

MTL_UNITS_OF_MEASURE SYNONYM

MTL_UNIT_TRANSACTIONS SYNONYM

MTL_UOM_CLASSES SYNONYM

MTL_UOM_CONVERSIONS SYNONYM

MXCOA_IFACE TABLE

MXCOA_IFACE_NDX INDEX

MXCRAFT_IFACE TABLE

MXCRAFT_IFACE_NDX INDEX

MXE_AP_SP PROCEDURE

MXE_GL_SP PROCEDURE

MXE_INVRESERVE_SP PROCEDURE

MXE_INV_SP PROCEDURE

MXE_ITM_SP PROCEDURE

MXE_PA_ACT_SP PROCEDURE

MXE_PR_SP PROCEDURE

MXE_RCV_LOT_SP PROCEDURE

MXE_RCV_SER_SP PROCEDURE

MXE_RCV_SP PROCEDURE

MXE_USR_AP_SP PROCEDURE

MXE_USR_GLOUTX_SP PROCEDURE

MXE_USR_GL_SP PROCEDURE

Object name Object type

Page 94: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

90 IBM Maximo: Upgrade Guide

MXE_USR_INVRESERVE_SP PROCEDURE

MXE_USR_INV_SP PROCEDURE

MXE_USR_ITM_SP PROCEDURE

MXE_USR_PA_ACT_SP PROCEDURE

MXE_USR_PC_SP PROCEDURE

MXE_USR_PO_SP PROCEDURE

MXE_USR_PRT_SP PROCEDURE

MXE_USR_PR_SP PROCEDURE

MXE_USR_RCV_LOT_SP PROCEDURE

MXE_USR_RCV_SER_SP PROCEDURE

MXE_USR_RCV_SP PROCEDURE

MXGLCOMP_IFACE TABLE

MXGLCOMP_IFACE_NDX INDEX

MXGLTXN_IFACE TABLE

MXGLTXN_IFACE_NDX INDEX

MXGLTXN_IFACE_TRG TRIGGER

MXINVBAL_IFACE TABLE

MXINVBAL_IFACE_NDX INDEX

MXINVENTORY_IFACE TABLE

MXINVENTORY_IFACE_TRG TRIGGER

MXINVISSUE_IFACE TABLE

MXINVOICE_IFACE TABLE

MXINVOICE_IFACE_TRG TRIGGER

MXINVRES_IFACE TABLE

MXINVRES_IFACE_NDX INDEX

MXINVRES_IFACE_TRG TRIGGER

MXIN_INTER_TRANS TABLE

MXITEM_IFACE TABLE

MXITEM_IFACE_NDX INDEX

MXITEM_IFACE_TRG TRIGGER

MXI_USR_GLINX_SP PROCEDURE

MXLABOR_IFACE TABLE

MXLABOR_IFACE_NDX INDEX

MXOUT_INTER_NDX2 INDEX

MXOUT_INTER_TRANS TABLE

MXPC_IFACE TABLE

MXPC_IFACE_NDX INDEX

MXPC_IFACE_TRG TRIGGER

MXPO_IFACE TABLE

MXPO_IFACE_NDX INDEX

MXPO_IFACE_TRG TRIGGER

MXPROJTXN_IFACE TABLE

MXPROJTXN_IFACE_TRG TRIGGER

MXPROJ_IFACE TABLE

MXPROJ_IFACE_NDX INDEX

Object name Object type

Page 95: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 91

MXPR_IFACE TABLE

MXPR_IFACE_NDX INDEX

MXPR_IFACE_TRG TRIGGER

MXRCVROTITM_IFACE TABLE

MXRECEIPT_IFACE TABLE

MXRECEIPT_IFACE_TRG TRIGGER

MXVENDOR_IFACE TABLE

MXVENDOR_IFACE_NDX INDEX

MX_SQL PROCEDURE

NVENTORY_IFACE_NDX INDEX

OF_ID_PKG PACKAGE BODY

OF_ID_PKG PACKAGE

ORG_ORGANIZATION_DEFINITIONS SYNONYM

PA_ALL_ORGANIZATIONS SYNONYM

PA_BILL_RATES_ALL SYNONYM

PA_BUDGET_TYPES SYNONYM

PA_BUDGET_VERSIONS SYNONYM

PA_COMPENSATION_DETAILS_ALL SYNONYM

PA_IMPLEMENTATIONS SYNONYM

PA_NON_LABOR_RESOURCES SYNONYM

PA_PROJECTS_ALL SYNONYM

PA_PROJECT_ACCUM_ACTUALS SYNONYM

PA_PROJECT_ACCUM_BUDGETS SYNONYM

PA_PROJECT_ACCUM_COMMITMENTS SYNONYM

PA_PROJECT_ACCUM_HEADERS SYNONYM

PA_STD_BILL_RATE_SCHEDULES_ALL SYNONYM

PA_TASKS SYNONYM

PA_TRANSACTION_INTERFACE SYNONYM

PA_TRANSACTION_SOURCES SYNONYM

PER_ADDRESSES SYNONYM

PER_ALL_ASSIGNMENTS_F SYNONYM

PER_ALL_PEOPLE_F SYNONYM

PER_ASSIGNMENT_STATUS_TYPES SYNONYM

PER_BUSINESS_GROUPS SYNONYM

PER_JOBS SYNONYM

PER_PAY_BASES SYNONYM

PER_PAY_PROPOSALS SYNONYM

PO_ACTION_HISTORY SYNONYM

PO_AGENTS SYNONYM

PO_API_ERRORS_REC_TYPE SYNONYM

PO_CANCEL_IFACE TABLE

PO_CHANGE_API1_S SYNONYM

PO_DISTRIBUTIONS SYNONYM

PO_DISTRIBUTIONS_INTERFACE SYNONYM

PO_DISTRIBUTIONS_INTERFACE_S SYNONYM

Object name Object type

Page 96: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

92 IBM Maximo: Upgrade Guide

PO_DISTRIBUTIONS_S SYNONYM

PO_DOCUMENT_CONTROL_PUB SYNONYM

PO_HAZARD_CLASSES SYNONYM

PO_HEADERS SYNONYM

PO_HEADERS_ALL SYNONYM

PO_HEADERS_INTERFACE SYNONYM

PO_HEADERS_INTERFACE_S SYNONYM

PO_HEADERS_S SYNONYM

PO_LINES SYNONYM

PO_LINES_ALL SYNONYM

PO_LINES_INTERFACE SYNONYM

PO_LINES_INTERFACE_S SYNONYM

PO_LINES_S SYNONYM

PO_LINE_LOCATIONS SYNONYM

PO_LINE_LOCATIONS_ALL SYNONYM

PO_LINE_LOCATIONS_S SYNONYM

PO_LINE_TYPES SYNONYM

PO_LOOKUP_CODES SYNONYM

PO_RELEASES SYNONYM

PO_RELEASES_ALL SYNONYM

PO_RELEASES_S SYNONYM

PO_REQUISITIONS_INTERFACE SYNONYM

PO_REQUISITIONS_INTERFACE_ALL SYNONYM

PO_REQUISITION_HEADERS SYNONYM

PO_REQUISITION_HEADERS_ALL SYNONYM

PO_REQUISITION_LINES SYNONYM

PO_REQ_DISTRIBUTIONS SYNONYM

PO_SYSTEM_PARAMETERS_ALL SYNONYM

PO_UNIQUE_IDENTIFIER_CONTROL SYNONYM

PO_UN_NUMBERS SYNONYM

PO_UPDATE_IFACE TABLE

PUT_IN_LOG PROCEDURE

RCV_HEADERS_INTERFACE SYNONYM

RCV_HEADERS_INTERFACE_S SYNONYM

RCV_INTERFACE_GROUPS_S SYNONYM

RCV_ROUTING_HEADERS SYNONYM

RCV_SERIAL_TRANSACTIONS SYNONYM

RCV_SHIPMENT_HEADERS SYNONYM

RCV_SHIPMENT_LINES SYNONYM

RCV_TRANSACTIONS SYNONYM

RCV_TRANSACTIONS_INTERFACE SYNONYM

RCV_TRANSACTIONS_INTERFACE_S SYNONYM

RESP_ID_PKG PACKAGE

RESP_ID_PKG PACKAGE BODY

RETPROC PROCEDURE

Object name Object type

Page 97: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 93

Checking Maximo Asset Management tables and columns for compatibility

After you install the Oracle ERP adapter, you might need to resize some of the tables and columns

The Maximo Asset Management table columns must be compatible with those in Oracle E-Business Suite. If the columns are not compatible, Maximo Asset Management cannot store the data it receives from Oracle E-Business Suite.

Table columns shared by the two systems must have the following properties in common:

Data typeMaximum column length (a length sufficient to contain the data)

To ensure that table columns are compatible:

1 Go to the Database Configuration application in Maximo Asset Management and check the size of the following tables:

RETPROCERROR FUNCTION

SET_OPERID_SP PROCEDURE

UT_INTER_TRANS_NDX INDEX

XINVOICE_IFACE_NDX INDEX

XPROJTXN_IFACE_NDX INDEX

XRECEIPT_IFACE_NDX INDEX

Object name Object type

Type Table Column Size

ALN ADDRESS ADDRESSCODE 60

ADDRESS ADDRESS1 240

CHARTOFACCOUNTS ACCOUNTNAME 240

COMPANIES ADDRESS1 240

COMPANIES ADDRESS3 150

COMPANIES BANKACCOUNT 55

COMPANIES COMPANY 57

COMPANIES CONTACT 52

COMPANIES CUSTOMERNUM 25

COMPANIES FAX 26

COMPANIES FOB 25

COMPANIES NAME 240

COMPANIES PAYMENTTERMS 50

COMPANIES PHONE 26

COMPANIES SHIPVIA 25

COMPANIES TYPE 30

Page 98: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

94 IBM Maximo: Upgrade Guide

2 Change any columns with incompatible properties.

3 Go to the Domains application in Maximo Asset Management and ensure that the COMPTYPE domain size is set to 30.

For information about the Domains application, see the IBM Maximo Asset Management System Administrator Guide or the online help for the Domains application.

Creating the Maximo interface tables in the Oracle E-Business Suite database

You must run the create procedure in Maximo Asset Management that creates the interface tables in the Oracle E-Business Suite database. Anticipate that it might take several minutes to build the interface tables.

The following task uses OAExtSys as the external system name; however, you might continue using the name that you used in the previous release of the adapter.

COMPCONTACT POSITION 30

ALN CONTRACT CONTRACTNUM 20

CRAFT CRAFT 240

CRAFT DESCRIPTION 240

CURRENCY CURRENCYCODE 15

GLCOMPONENTS COMPTEXT 240

GLCOMPONENTS COMPVALUE 150

GLCOMPONENTS EXTERNALREFID 15

INVENTORY BINNUM 49

INVENTORY MODELNUM 25

INVLOT LOTNUM 30

INVOICE DESCRIPTION 240

INVOICE DOCUMENTTYPE 25

INVOICE INVOICENUM 50

INVOICE VENDORINVOICENUM 50

ITEM DESCRIPTION 240

ALN ITEM ITEMNUM 40

ITEM MSDSNUM 40

MATRECTRANS PACKINGSLIPNUM 25

MATRECTRANS REJECTCODE 30

ALN MEASUREUNIT MEASUREUNITID 25

ALN PO PONUM 20

PO POTYPE 25

PRLINE REMARK 240

Type Table Column Size

Page 99: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 95

To create the interface tables in Maximo Asset Management:

1 Choose Go To > Integration > External Systems.

2 Select the System field and press Enter, then select the OAExtSys external system record.

3 Choose Select Action > Create Interface Tables.

4 Select all of the following interface tables.

5 Click Create.

Configuring installation-dependent parameters in the setofvar.sql script

The setofvar.sql script specifies the parameters for creating the PL/SQL objects and synchronizing Maximo Asset Management and Oracle E-Business Suite. You must configure the parameters that are in the setofvar.sql script to set the database service name, user name, owner, passwords, and directories for the Oracle E-Business Suite integration schema.

To configure the parameters:

1 In the Maximo_root\ORACLEAPIS\install directory, open the setofvar.sql script.

2 Configure the following parameters:

MXCOA_IFACE MXLABOR_IFACEMXCRAFT_IFACE MXPC_IFACEMXGLCOMP_IFACE MXPO_IFACEMXGLTXN_IFACE MXPR_IFACEMXINVBAL_IFACE MXPROJ_IFACEMXINVENTORY_IFACE MXPROJTXN_IFACEMXINVISSUE_IFACE MXRCVROTITM_IFACEMXINVOICE_IFACE MXRECEIPT_IFACEMXINVRES_IFACE MXVENDOR_IFACEMXITEM_IFACE

Parameter Description

hostStrOF = 'service name for Oracle database' Enter the Oracle database service name configured in tnsnames.ora.

MaximoUserName = 'MAXORA' User name created for the Oracle E-Business Suite integration schema.

MaximoPass = 'MAXORA user password' Password for MAXORA.

ORAAPPLSYSUSERNAME = 'APPS' Owner for the Oracle E-Business Suite database.

ORAAPPLSYSPASS = 'APPS' Password for the Oracle E-Business Suite owner.

Page 100: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

96 IBM Maximo: Upgrade Guide

Installing packages, procedures, triggers, and other objects to the Oracle E-Business Suite database

After you configure the parameters that are in the setofvar.sql script, you must install the packages, procedures, triggers, and objects in the Oracle E-Business Suite database.

To install packages, procedures, triggers, and objects:

1 In SQL * Plus, connect as the user MAXORA to the Oracle E-Business Suite database.

2 Run the following command:

SQL> start Maximo_root\ORACLEAPIS\install\setofvar

This command lists the install parameters that are defined in the setofvar.sql script.

3 Run the install.sql script by entering the following command:

SQL> start &InstallDir.install

4 In the Maximo_root\ORACLEAPIS\log\install.out directory, open the install.out file and check the file for any errors.

Verifying and fixing installation errors

After you install the packages, procedures, and triggers to the Oracle E-Business Suite database, you must check for installation errors and fix them.

To verify and fix installation errors:

1 Open the install.out spool file in the log directory and check for errors.

RootApis = 'Maximo_root\ORACLEAPIS' The install directory for the Oracle E-Business Suite adapter. It contains the following subdirectories:

apiuser

install

interfac

log

LogDir = 'Maximo_root\ORACLEAPIS\log' The location of output log files.

UserDir = 'Maximo_root\ORACLEAPIS\apiuser'

The location of user exit templates.

If you have customized versions of the user exits, be sure to add them to the templates.

Parameter Description

Page 101: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 97

The following table describes the types of errors that you might find:

2 Fix any problems that you find and rerun install.sql without errors.

Updating the external system value

The install.sql script sets the MAXORACTLS EXTSYS control to OA12. If you want to continue using the external system value of the Oracle ERP adapter 6.2 in release 7.1, you must update OA12 to the value that you used in the previous release of the adapter.

To update the external system value:

1 In SQL * Plus, connect to the Oracle E-Business Suite database as MAXORA.

2 Enter the following command:

UPDATE MAXORA.MAXORACTLS set CTLVALUE = '<external_system_name>' where CTLNAME = 'EXTSYS';

After you update the external system value, you enable inbound transactions.

Synchronizing data between Oracle and Maximo

Certain data that is shared by Maximo Asset Management and Oracle E-Business Suite must be consistent at the Maximo Asset Management organization-level and Oracle E-Business Suite ledger-level. To ensure consistency, you must configure and synchronize some Maximo Asset Management and Oracle fields by using the integration controls.

You must accurately synchronize information such as Oracle employees and Maximo Asset Management labor codes, and Oracle vendors and Maximo Asset Management companies before you can successfully exchange data between Maximo Asset Management and Oracle.

Error type Description

File not found Search for text similar to “unable to open file \Maximo_root\ORACLEAPIS\...”. Errors of this type indicate that the setofvar.sql file might not have correct directory settings. For example, the user directory Maximo_root\ORACLEAPIS\apiuser might be missing a \ after “apiuser.”

Statements not accepted by the system Search for “unknown command” text. If you find this error, check that your version of SQL * Plus for Windows is equal to or higher than 3.1.3.5.4.

Oracle Search for “ORA –” text. If you find any ORA-type errors, contact your Oracle Database Administrator.

Compile Search for “PLS –” text. If you find any lines that start with “PLS-”, then also search for “with compilation error” text. If you find any compile errors, contact IBM Support at www.ibm.com/software/sysmgmt/products/support/.

Page 102: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

98 IBM Maximo: Upgrade Guide

For example, if Oracle E-Business Suite uses the British pound as the base currency in a ledger, Maximo Asset Management must use the British pound as the base currency for the corresponding organization.

The following data must be consistent between Maximo Asset Management and Oracle E-Business Suite:

CurrenciesFinancial calendarsTax ratesUnits of measure and conversion factorsUser names (if you do not use the GENUSR integration control)

To maintain this data, update it manually in the applications.

Verifying the cron task for interface table polling

After you have completed configuring the Oracle ERP adapter on the Oracle side of the integration, you can send transactions between Maximo Asset Management and Oracle E-Business Suite. You must first verify that the cron task for interface table polling is set up and activated.

The following task uses OAPolling as the cron task name and OAExtSys as the external system value; however, you might continue using the cron task name and the external system value that you used in the previous release of the adapter.

To verify the cron task:

1 Select Go To > System Configuration > Platform Configuration > Cron Task Setup.

2 Press Enter to display a list of cron tasks.

3 Click IFACETABLECONSUMER and view OAPolling Cron Task Instance.

4 Click the Schedule icon to display the Select Schedule or Time Interval dialog box.

5 Verify that the schedule for the OAPolling cron task reflects how frequently you want to poll the interface table.

6 Click the Run as User icon to display a Select Value list where you can choose a User ID to associate with the cron task. The default value is MAXADMIN, which provides the highest level of user authorization.

7 On Parameters tab for OAPolling, select ENDPOINT and enter the name that you assigned to the endpoint for the Oracle ERP adapter.

8 Enter the OAExtSys value for the cron task parameter EXTSYSNAME.

9 Click Save Cron Task.

10 Click OAPolling to display record information.

11 Select the Active check box to enable the cron task.

12 Click Save Cron Task.

Page 103: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 99

13 Click Select Action > Reload Request.

14 Select OAPolling and click OK.

Enabling the external system

In addition to enabling the cron task for interface table polling, you also must enable the external system.

The following task uses OAExtSys as the external system name; however, you might continue using the name that you used in the previous release of the adapter.

To enable the external system:

1 Select Go To > Integration > External Systems.

2 Type OAExtSys in the System field, and press Enter.

3 Click OAExtSys to open the OAExtSys external systems window.

4 Select the Enabled check box.

5 Click Save External System.

Synchronizing Oracle and Maximo GL components

Oracle E-Business Suite and Maximo Asset Management must use the same chart of accounts structure before you can begin transferring GL data from Oracle to Maximo Asset Management. Oracle and Maximo Asset Management chart of accounts must share the same number of segments.

You can reconfigure Maximo Asset Management so that its account segments have the same structure as those in Oracle E-Business Suite.

Additionally, you can modify the Oracle and Maximo Asset Management GL structures with user exit procedures that transform accounts from one structure to the other. For example, Oracle allows null segments in any part of the account structure, while Maximo Asset Management does not allow a null segment to precede a populated segment. To reconcile these differences, you might need to create a user exit procedure that alters the number and position of the GL segments.

To transfer GL components from Oracle to Maximo Asset Management:

1 Navigate to the Install directory from Maximo_root and open the syncglcomp.sql file.

2 Edit the syncglcomp.sql file by using a WHERE clause to transfer all accounts or selected accounts to Maximo Asset Management.

3 Log on to SQL * Plus and connect to the Oracle E-Business Suite database.

Page 104: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

100 IBM Maximo: Upgrade Guide

4 Enter the following commands to set the Oracle ERP adapter environment and start the transfer of Oracle GL component data to Maximo Asset Management:

SQL> start <MAXIMO_root>\ORACLEAPIS\install\setofvar <Enter>

SQL> start &InstallDir.syncglcomp.sql <Enter>

5 When prompted, press Enter.

6 Enter a chart of accounts ID (COA_ID) from the list of IDs displayed on your screen, then press Enter.

The generated file is in the following location:

<MAXIMO_root>\ORACLEAPIS\log\syncglcomp.out

7 Review the syncglcomp.out file for errors.

The spool file might direct you to select from the MAXORALOG table to review error conditions. You can view this log in SQL * Plus after logging in as user MAXORA.

For example, you might see errors like the following error:

column application = ‘API_GLCC_SP’ ORA-06502: PL/SQL: numeric or value error

If you obtain the preceding error message, check the mapping for the MX_GLCOMP_IFACE table. This error indicates that the COMPTEXT field is not large enough to hold the GL component description from Oracle E-Business Suite. To resolve this type of error, reconfigure the Maximo Asset Management GLCOMPONENTS table and increase the length of the COMPTEXT field.

Synchronizing Oracle and Maximo chart of accounts

To transfer the chart of accounts from Oracle to Maximo Asset Management, complete the following steps:

1 Navigate to the ORACLEAPIS directory from Maximo_root and open the synccoa.sql file.

2 Edit the synccoa.sql file by using a WHERE clause to transfer all accounts or selected accounts to Maximo Asset Management.

3 Log on to SQL * Plus and connect to the Oracle E-Business Suite database.

4 Enter the following commands to set the Oracle ERP adapter environment and start the transfer of Oracle chart of accounts data to Maximo Asset Management:

SQL> start <MAXIMO_root>\ORACLEAPIS\install\setofvar <Enter>

SQL> start &InstallDir.synccoa.sql <Enter>

5 When prompted, press Enter.

Page 105: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 101

6 Enter a chart of accounts ID (COA_ID) from the list of IDs displayed on your screen, then press Enter.

The generated file is in the following location:

<MAXIMO_root>\ORACLEAPIS\log\synccoa.out

7 Review the synccoa.out file for errors.

8 Transfer additional chart of accounts IDs by selecting a different COA_ID from the list, rerunning the script, and reviewing the output file for errors.

Synchronizing Oracle employees and Maximo system labor codes

To transfer the Oracle employees to the Maximo Asset Management labor codes, complete the following steps:

1 Log on to SQL * Plus, then enter the following commands:

SQL> start <MAXIMO_root>\ORACLEAPIS\install\setofvar <Enter>

SQL> start &InstallDir.synclabor <Enter>

2 When prompted, press Enter.

3 Enter an Oracle business group ID from the list of IDs displayed on your screen, then press Enter.

Each time you want to transfer a different business group ID, select it from the screen and rerun the synclabor script.

The generated file is in the following location:

<MAXIMO_root>\ORACLEAPIS\log\synclabor.out

4 Review the synclabor.out file for errors.

Synchronizing Oracle organizations and locations and Maximo address codes

You must map the Oracle E-Business Suite organizations and locations to the Maximo Asset Management address codes. To synchronize the two systems, you must first obtain a listing of the organizations and locations in Oracle E-Business Suite. You also must define those codes in Maximo Asset Management.

Obtain a list of Oracle E-Business Suite organizations and location codes

To generate a list of Oracle organizations and locations:

1 Log on to SQL * Plus, then enter the following commands:

SQL> start <MAXIMO_root>\ORACLEAPIS\install\setofvar <Enter>

SQL> start &InstallDir.showaddr <Enter>

2 When prompted, press Enter.

Page 106: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

102 IBM Maximo: Upgrade Guide

You will see a list of Oracle organizations and locations that you must manually map to the Maximo Asset Management address codes. Map them as described in the procedure that follows.

The generated file is in the following location:

<MAXIMO_root>\ORACLEAPIS\log\showaddr.out

Map Oracle organizations and locations to Maximo address codes

The following procedure describes how to map the Maximo Asset Management address codes to the Oracle organizations and locations.

To map an address code in Maximo Asset Management to an Oracle organization or location:

1 In Maximo Asset Management, select Go To > Administration > Organizations.

2 Press Enter to display a list of organizations.

3 Click the name of the organization that you want to update.

4 Click the Address tab.

5 Click New Row.

6 Enter the Oracle location or organization in the Address Code field.

7 Enter the following address information:

Long descriptionAddressCityState/ProvinceZip/Postal CodeCountry

8 Click Save Organization.

Additionally, the following table shows how to map Maximo Asset Management Bill To Companies, Ship To Companies, and Bill To and Ship To contacts to Oracle E-Business Suite.

Synchronizing Oracle and Maximo currencies

Maximo Asset Management and Oracle E-Business Suite must use the same currency. To synchronize the two systems, you must first obtain a listing of the currency codes in Oracle E-Business Suite. You also must define those codes in Maximo Asset Management.

MaximoAsset Management

Oracle E-BusinessSuite

Asset Management System definition

Bill to company Organization Address codeShip to company Location Address codeBill to contact Employee Labor codeShip to contact Employee Labor code

Page 107: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 103

Obtain a list of Oracle E-Business Suite currency codes

To obtain a listing of the currency codes in Oracle E-Business Suite:

1 Log on to SQL * Plus and connect to the Oracle E-Business Suite database.

2 Enter the following commands:

SQL> start <MAXIMO_root>\ORACLEAPIS\install\setofvar <Enter>

SQL> start &InstallDir.showcurr <Enter>

The generated file is in the following location:

<MAXIMO_root>\ORACLEAPIS\log\showcurr.out

The showcurr.out file lists the currency codes defined in Oracle E-Business Suite.

Define Oracle currency codes in Maximo

To define the Oracle currency codes in Maximo Asset Management:

1 In Maximo Asset Management, select Go To > Financial > Currency Codes.

2 Click New Row.

3 Enter a currency code in the Currency field and a description in the adjacent text box.

4 Click Save Currency Code.

Synchronizing Oracle vendors and Maximo companies

To synchronize the Oracle vendors and the Maximo Asset Management companies, you must run a script that defines the Oracle E-Business Suite vendors as companies in Maximo Asset Management.

Before you run the synchronization script, you must set up the Oracle vendor type defaults in Maximo Asset Management by completing the following steps:

1 In Maximo Asset Management, select Go To > Financial > Chart of Accounts.

2 Choose Select Action > Company-Related Accounts to open the Company-Related Accounts screen.

3 Click New Row, then add the following information:

Company Type (Courier, Manufacturer, or Vendor)RBNI AccountAP Suspense AccountAP Control Account

4 Repeat Steps 1 – 3 for each Oracle vendor type you expect to transfer to Maximo Asset Management.

The newly defined company ID of Maximo Asset Management is a concatenation of the Oracle operating unit ID, vendor ID, and vendor site code. Hyphens separate the three segments.

Page 108: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

104 IBM Maximo: Upgrade Guide

The script adds the AP control account to each company ID of Maximo Asset Management. If you plan on using invoicing, update each company ID with an RBNI (received but not invoiced) and suspense account.

To synchronize the Oracle vendors and the Maximo Asset Management companies:

1 Navigate to the Install directory from Maximo_root and open the syncvnd.sql file.

2 Edit the syncvnd.sql file by using a WHERE clause to transfer all vendors or selected vendors to Maximo Asset Management.

3 Log on to SQL * Plus and connect to the Oracle E-Business Suite database.

4 Enter the following commands:

SQL> start <MAXIMO_root>\ORACLEAPIS\install\setofvar <Enter>

SQL> start &InstallDir.syncvnd <Enter>

5 When prompted, press Enter.

6 Enter an Oracle operating unit ID from the list of IDs displayed on your screen, then press Enter.

Each time you want to transfer a different operating unit ID, select it from the screen and rerun the syncvnd script.

The generated file is in the following location:

<MAXIMO_root>\ORACLEAPIS\log\syncvnd.out

7 Review the syncvnd.out file for errors.

Update the Maximo company ID with an RBNI and suspense account

To update the company ID with an RBNI and suspense account:

1 In Maximo Asset Management, select Go To > Purchasing > Companies.

2 Press Enter to display a list of company IDs.

3 Click the company you want to update to display the record in the Company tab.

4 Click the Select Icon for the RBNI Account to open the Select GL Account dialog box where you can build the RBNI account.

5 Repeat Step 4 for the Suspense Account.

6 Click Save Company.

Synchronizing Oracle inventory organizations and Maximo storeroom locations

To synchronize the Oracle inventory organizations and the Maximo Asset Management storeroom locations, you must first obtain a listing of the organizations in Oracle E-Business Suite. You also must define them as storerooms in Maximo Asset Management.

Page 109: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 105

Obtain a list of Oracle E-Business Suite organizations

To obtain a listing of the organizations and other control values from Oracle E-Business Suite:

1 Log on to SQL * Plus, then enter the following commands:

SQL> start <MAXIMO_root>\ORACLEAPIS\install\setofvar <Enter>

SQL> start &InstallDir.showids <Enter>

2 When prompted, press Enter to display a list of the Oracle E-Business Suite showids.out control values as shown in the following table.

The generated file is in the following location:

<MAXIMO_root>\ORACLEAPIS\log\showids.out

3 Review the showids.out file for any errors.

Define storerooms in Maximo

To define a storeroom in Maximo Asset Management:

1 In Maximo Asset Management, select Go To > Inventory > Storerooms.

2 Click New Storeroom.

3 Enter data about the storeroom, including:

Storeroom and site locationGL account informationShip to and Bill to information

4 Click Save Storeroom.

Synchronizing Oracle order units and Maximo units of measure

To synchronize the Oracle and the Maximo Asset Management order units, you must first obtain a listing of the order units in Oracle E-Business Suite. You also must define them in Maximo Asset Management.

Obtain a list of Oracle E-Business Suite order units

To obtain a listing of the order units in Oracle E-Business Suite:

1 Log on to SQL * Plus, then enter the following commands:

SQL> start <MAXIMO_root>\ORACLEAPIS\install\setofvar <Enter>

SQL> start &InstallDir.showuom <Enter>

Control Default valueAPLINETYPE ITEMGENSTORE Null or ORG_CODECOAXREF Chart_of_accounts_IDORGXREF Ledger_ID

Page 110: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

106 IBM Maximo: Upgrade Guide

2 When prompted, press Enter.

The generated file is in the following location:

<MAXIMO_root>\ORACLEAPIS\log\showuom.out

The showuom.out output file lists the units of measure defined in Oracle E-Business Suite.

3 Review the showuom.out file for any errors.

Define units of measure and conversion factors in Maximo

To define a unit of measure and a conversion factor in Maximo Asset Management:

1 In Maximo Asset Management, select Go To > Inventory > Item Master.

2 Choose Select Action > Unit of Measure and Conversion > Add/Modify Units of Measure.

3 Click New Row.

4 Enter the unit of measure, a long description, and an abbreviation for the unit of measure. For example, you might enter GBYTE, GIGABYTE, and GB.

5 Click OK.

6 Additionally, if you want to add a conversion factor for a unit of measure, choose Select Action > Unit of Measure and Conversion > Add/Modify Conversions.

For example, you might enter a conversion factor of 250 when converting a unit of measure value of BOX to a unit measure value of FEET.

7 Click OK.

8 Click Save Item.

Adding tax codes to Maximo

Before you can synchronize the Oracle and the Maximo Asset Management items, you must define the Oracle tax codes that you use in Maximo Asset Management.

Obtain a list of Oracle E-Business Suite tax codes

To obtain a listing of the tax codes in Oracle E-Business Suite:

1 Log on to SQL * Plus, then enter the following commands:

SQL> start <MAXIMO_root>\ORACLEAPIS\install\setofvar <Enter>

SQL> start &InstallDir.showtax <Enter>

2 When prompted if OK to continue, press Enter.

The generated file is in the following location:

<MAXIMO_root>\ORACLEAPIS\log\showtax.out

The showtax.out file lists the tax codes defined in the Oracle E-Business Suite.

Page 111: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 107

3 Review the showtax.out file for any errors.

Define Oracle tax codes in Maximo

To define tax codes:

1 In Maximo Asset Management, select Go To > Administration > Organizations.

2 Press Enter to display a list of organizations.

3 Click an organization to open the record.

4 Click Select Action > Purchasing Options > Tax Options.

5 Click New Row.

6 Enter values for the following fields:

Tax CodeTax Code DescriptionTax RateEffective DatePaid Tax GL AccountUnpaid Tax GL Account

7 Click OK.

8 Click Save Organization.

Synchronizing Oracle and Maximo items

To synchronize items between the two systems, you must complete the following tasks:

Check integration control settings and financial periodsRun an SQL script that transfers the Oracle items to Maximo Asset ManagementVerify that the Oracle items were added to the Item Master in Maximo Asset ManagementDefine the item as a direct delivery item in Oracle (optional)

You must define individual or all items in an Oracle organization as direct delivery so that you can receive an item in Oracle and then send the receipt to Maximo Asset Management.

Items that belonged to an organization in Oracle E-Business Suite belong to a storeroom in Maximo Asset Management after you run the syncitm.sql script.

To synchronize items between the two systems:

1 Verify that the item-related Maximo Asset Management integration controls for the Oracle ERP adapter have the default value set to 1.

Page 112: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

108 IBM Maximo: Upgrade Guide

2 In Maximo Asset Management, ensure that Default Item Status is set to Active at the Set and Organization levels. Items that come from Oracle system will take the default item status defined at the Organization level. Also, depending on the default item status, certain operations might not be allowed on the Item in Maximo Asset Management.

For more information about the Item Status function, see the IBM Maximo Asset Management 7.1 documentation.

3 Ensure that the financial periods during which you synchronize items are open in Maximo Asset Management.

For information about displaying the financial periods in Maximo Asset Management, see the IBM Maximo Asset Management Integration Guide.

4 Navigate to the Install directory from Maximo_root and open the syncitm.sql file.

5 Edit the syncitm.sql file by using a WHERE clause to transfer all items or selected items to Maximo Asset Management.

6 Log on to SQL * Plus and connect to the Oracle E-Business Suite database.

7 Enter the following commands:

SQL> start <MAXIMO_root>\ORACLEAPIS\install\setofvar <Enter>

SQL> start &InstallDir.syncitm <Enter>

The generated file is in the following location:

<MAXIMO_root>\ORACLEAPIS\log\syncitm.out

The syncitm.out file contains a list of all the inventory items that you can transfer to Maximo Asset Management.

8 Review the syncitm.out file for any errors.

9 Enter an Oracle item ID from the list of IDs displayed on your screen, then press Enter.

Each time you want to transfer a different item ID, select it from the screen and rerun the syncitm script.

10 Check that you successfully transferred an Oracle item to Maximo Asset Management:

a Select Go To > Inventory > Item Master.

b Enter the item number in the Item field, and press Enter.

If successfully transferred, the item search action displays a line item for the record.

Page 113: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 109

c Click the Item number to open the detail record.

For more information about integration controls and inventory management in Maximo Asset Management, see the IBM Maximo Asset Management Integration Guide.

Synchronizing Oracle and Maximo item balances

If you want to transfer item balances from Oracle to Maximo Asset Management, complete the following procedures. This synchronization transfers the current balance and the bin number where the balance is located. Transferring item balances is optional.

When testing reservations, receipts, and issues, you need a default bin. The script in the following procedure defines the default bin.

Transfer Oracle item balances to Maximo

To transfer item balances from Oracle to Maximo Asset Management:

1 Navigate to the Install directory from Maximo_root and open the syncbal.sql file.

2 Edit this file by entering an organization ID in a WHERE clause that represents the organization item balances that you want to transfer.

3 Log on to SQL * Plus, then enter the following commands:

SQL> start <MAXIMO_root>\ORACLEAPIS\install\setofvar <Enter>

SQL> start &InstallDir.syncbal <Enter>

4 When prompted, press Enter.

The generated file is in the following location:

<MAXIMO_root>\ORACLEAPIS\log\syncbal.out

The syncbal.out file lists the Oracle inventory organization IDs that can be transferred to Maximo Asset Management.

5 Review the syncbal.out file for any errors.

Each time you want to transfer a different inventory balance, select the inventory organization ID from the screen and rerun the syncbal script.

Check item balances in Maximo

To check that transferred items were updated with the correct balance and bin number in Maximo Asset Management:

1 In Maximo Asset Management, select Go To > Inventory > Inventory.

2 Type an item number in the Item field, and press Enter. Also, you can click the Select Icon > Select Value, and click an item number from the displayed list of items.

The summary line displays the current balance for the selected item.

3 Click the Inventory tab to view the item detail record, including bin and lot numbers.

Page 114: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

110 IBM Maximo: Upgrade Guide

Creating and running concurrent requests

You can create a POIMPORT concurrent request and use this request to send PO updates from Maximo Asset Management to Oracle E-Business Suite.

To create a POIMPORT concurrent request:

1 Register the POIMPORT procedure in Oracle E-Business Suite:

a Select Responsibility > System Administrator.

b Select Concurrent > Program > Executable.

c Enter the following values:

The schema name, MAXORA, should be replaced by the schema name used in your installation.

d Click Save.

e Close the form.

f Select Concurrent > Program > Define.

g Enter the following values on screen:

h Click Save.

i Click Incompatibilities.

j In the Name field, select MAXORA: Import Asset Management System PO Updates and Cancellations.

k Click Save.

Executable: POIMPORTShort Name: POIMPORTApplication: PurchasingDescription: Import Asset Management System PO Updates and

CancellationsExecution Method: PL/SQL Stored ProcedureExecution File Name: maxora.MaxPoPack.ImportPoData

Program: MAXORA: Import Asset Management System PO Updates and Cancellations

Enable Select this check boxShort Name: POIMPORTApplication: PurchasingDescription: Import Asset Management System PO Updates and

CancellationsExecutable Name: POIMPORTExecutable Method: PL/SQL Stored Procedure

Page 115: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 111

l Close the form.

2 Provide access to Purchase Responsibility:

a Select Security > Responsibility > Request.

b Press <F11> to enter the Query mode.

c In the Group field, enter All Reports.

d In the Application field, enter Purchasing.

e Press <CTRL+F11> to run the query.

f Place the cursor on one of the rows in the Requests table andselect File > New.

g Enter the following values on screen:

h Click Save.

Submitting the import process

After you create the concurrent request, you run the request and use it to send PO updates from Maximo Asset Management to Oracle E-Business Suite. To make the concurrent request run, you must submit the import process to the Oracle E-Business Suite task queue.

To submit the import process:

1 In Oracle E-Business Suite, select Responsibility > Purchasing.

2 Click OK.

3 Select Reports > Run.

4 Select the Single Request option and click OK.

5 Enter the name MAXORA: Import Asset Management System PO Updates and Cancellations.

If you want to start importing the report for the current data,click Submit.If you want the report to run on the background for a given time interval (for example, every five minutes), then continue with the following steps:

a Click Schedule.

b Select Periodically. Complete the Start and End date fields.

Type: ProgramName: MAXORA: Import Asset Management System PO Updates and

CancellationsApplication: Purchasing

Page 116: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

112 IBM Maximo: Upgrade Guide

c Select Run Every 5 Minute(s) from the drop-down list, or any other time interval you might need for the report to run.

d Select the Save this Schedule check box.

e Click OK.

The request now runs every five minutes for the period established between the Start and End dates. The request also imports all the purchase order updates from the interface tables.

Configuring the Projects integration

You must configure the Projects integration only if you have a new installation of Oracle Project Accounting and want to integrate it with Maximo Asset Management.

After you configure the Oracle ERP adapter, you can configure the integration between Maximo Asset Management and Oracle Project Accounting (the Projects integration). To configure the Projects integration, you must be familiar with the installation prerequisites and the configuration activities.

To complete these procedures, you need the following documentation:

IBM Maximo Enterprise Adapter System Administrator Guide for Oracle Applications 12 Adapter

The most recent Oracle ERP adapter patch release notes

Configuration prerequisites

Before you configure the Projects integration, you must define the following values. You might already have performed much of this configuration when you installed the Oracle ERP adapter.

Budget entry methodsBudget typesExpenditure categoriesExpenditure typesLabor and craft (as Oracle employees)Non-labor resourcesProject templatesProject typesResource listsTransaction sources

For information about these values, see your Oracle E-Business Suite documentation.

Page 117: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 113

Configuration activities

Depending on the combination of processes that you perform (installing the Oracle ERP adapter, installing the Projects integration, installing patches, and applying manual updates), there might be some overlap in the required activities. If you encounter the same activity a second time, perform it a second time. Skipping a duplicate procedure might cause errors.

Configuring the Projects integration involves the following activities. Some of the activities might not apply to you.

Updating database column lengthsEnabling new publish channels and the integration event listenerConfiguring the Projects-specific Maximo integration controlsAdding fields to user interfacesEnabling the financial control concurrent extract managerProviding access to the financial control concurrent extract managerSynchronizing the Oracle employees and the Maximo labor codes

Updating database column lengths

Use the Maximo Asset Management Database Configuration application to resize the following columns in the Maximo Asset Management database tables.

Enabling new publish channels and the integration event listener

The Projects integration adds the MXPROJTXN_TOOA12 publish channel and also uses the MXGLTXN_OA12 publish channel.

To enable the new publish channels, see “Enabling publish channels‚" page 82.

Configuring Projects-specific Maximo integration controls

The Projects integration uses the following Projects-specific Maximo Asset Management integration controls:

CHARGEORGEXPENDITEMEXPENDLABOREXPENDTOOLFCSTATUSXREFNLRORGPROJAPPROJPOPROJPRPROJSENDRESLEVELITEMRESLEVELLABORRESLEVELTOOLSRCTIMSRCUSE

Table Column Change type Size

CRAFT CRAFT ALN 240

CRAFT DESCRIPTION ALN 240

Page 118: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

114 IBM Maximo: Upgrade Guide

The Projects integration also uses the PROJPAY Oracle processing control to determine whether to extract cost rates from Oracle Human Resources (value 0) or Oracle Project Accounting (value 1). The default value of the control is 1 when the Projects integration is installed.

For information about these controls, see the Oracle Project Accounting information in the IBM Maximo Enterprise Adapter System Administrator Guide for Oracle Applications 12 Adapter.

For information about configuring the Maximo Asset Management integration controls, see the IBM Maximo Asset Management Integration Guide or the online help for the External Systems application.

Adding fields to user interfaces

The following table lists hidden fields that you might need to add to the user interfaces in the Maximo Asset Management work order, purchasing, inventory, and cost management applications. In some cases, adding the field is optional, depending on your business practices.

You add these fields through the Application Designer application in the Maximo Asset Management configuration module.

Application Page Field Required or optional

Work Order Tracking

Work Order tab Project IDTask ID

Required

Work Order Tracking

Labor subtab of Actuals tab Expenditure type See “Add expenditure type to the Labor [Actuals] subtab‚" page 117

Work Order Tracking

Materials subtab of Actuals tab

Expenditure type See “Add expenditure type to the Materials [Actuals] subtab‚" page 118

Work Order Tracking

Materials subtab of Actuals tab

Charge organization See “Add charge organization to the Materials [Actuals] subtab‚" page 118

Work Order Tracking

Materials subtab of Actuals tab

Non-labor resource organization

See “Add non-labor resource organization to the Materials [Actuals] subtab‚" page 119

Work Order Tracking

Services subtab of Actuals tab

Note: On the Services subtab, the fields are display only

Expenditure type See “Add expenditure type to the Services [Actuals] subtab‚" page 119

Work Order Tracking

Services subtab of Actuals tab

Note: On the Services subtab, the fields are display only

Charge organization See “Add charge organization to the services [Actuals] subtab‚" page 119

Page 119: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 115

Work Order Tracking

Services subtab of Actuals tab

Note: On the Services subtab, the fields are display only

Non-labor resource organization

See “Add non-labor resource organization to the Services [Actuals] subtab‚" page 120

Work Order Tracking

Tools subtab of Actuals tab Expenditure type See “Add expenditure type to the Tools [Actuals] subtab‚" page 120

Work Order Tracking

Tools subtab of Actuals tab Charge organization See “Add charge organization to the Tools [Actuals] subtab‚" page 121

Work Order Tracking

Tools subtab of Actuals tab Non-labor resource organization

See “Add non-labor resource organization to the Tools [Actuals] subtab‚" page 121

Purchase Requisition

PR Lines tab Expenditure type See “Add expenditure type to the PR Lines tab‚" page 122

Purchase Requisition

PR Lines tab Charge organization See “Add charge organization to the PR Lines tab‚" page 122

Purchase Orders PO Lines tab Expenditure type See “Add expenditure type to the PO Lines tab‚" page 122

Purchase Order PO Lines tab Charge organization See “Add charge organization to the PO Lines tab‚" page 123

Invoice Invoice Lines tab Expenditure type See “Add expenditure type to the Invoice Lines tab‚" page 123

Invoice Invoice Lines tab Charge organization See “Add charge organization to the Invoice Lines tab‚" page 124

Receipts Material Receipts tab Expenditure type See “Add expenditure type to the Material Receipts tab‚" page 124

Receipts Material Receipts tab Charge organization See “Add charge organization to the Material Receipts tab‚" page 125

Receipts Material Receipts tab Non-labor resource organization

See “Add non-labor resource organization to the Material Receipts tab‚" page 125

Application Page Field Required or optional

Page 120: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

116 IBM Maximo: Upgrade Guide

Expenditure type fields You do not have to add the expenditure type field if your business does one of the following:

Uses a single expenditure type for items, a single expenditure type for labor, and a single expenditure type for tools

Uses item number, labor code, and tool code as expenditure types

In these cases, transactions that require these values use the default values in the EXPENDITEM, EXPENDLABOR, and EXPENDTIOOL integration controls, respectively.

In all other cases, add the expenditure type field to the applicable user interfaces.

Charge organization and non-labor resource organization fields

If your business uses a single charge organization and a single non-labor resource organization for all transactions, you do not need to add the charge organization and non-labor resource organization fields. Transactions that require these values will use the default values in the CHARGEORG and NLRORG integration controls, respectively.

If your business uses multiple charge or non-labor resource organizations, add the two fields to the applicable user interfaces.

Receipts Service Receipts tab Expenditure type See “Add expenditure type to the Service Receipts tab‚" page 125

Receipts Service Receipts tab Charge organization See “Add charge organization to the Service Receipts tab‚" page 126

Receipts Service Receipts tab Non-labor resource organization

See “Add non-labor resource organization to the Service Receipts tab‚" page 126

Issues and Transfers

Issue Expenditure type See “Add expenditure type to the Issue subtab‚" page 127

Issues and Transfers

Issue Charge organization See “Add charge organization to the Issue subtab‚" page 127

Issues and Transfers

Issue Non-labor resource organization

See “Add non-labor resource organization to the Issue subtab‚" page 127

Cost Management Project tab Budget costBurdened costCommitted costRemaining cost

Optional

Application Page Field Required or optional

Page 121: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 117

Adding fields to the Work Order Tracking application

The following procedures add the required and optional Work Order Tracking fields. If you do not want to add an optional field, skip the corresponding procedure. You must add the project ID and task ID fields to the Work Order tab.

To add the project ID and task ID fields to the Work Order tab:

1 On the Applications tab in the Application Designer, select WOTRACK.

2 On the Workspace tab, click the Work Order subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

Add project ID to the Work Order tab

4 Drag the Textbox in the Controls dialog box below the Is Task field.

Do not close the Controls dialog box until you finish this procedure.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, enter FCPROJECTID.

7 In the Lookup field, enter PARENTPROJECT.

8 Move the cursor to the next field in the Textbox Properties dialog box. Do not close the Textbox Properties dialog box until you finish this procedure.

Add task ID to the Work Order tab

9 Drag the Textbox in the Controls dialog box to the space below the new Project ID field.

10 Ensure that the new textbox field is highlighted, then enter FCTASKID in the Attribute field of the Textbox Properties dialog box.

11 In the Lookup field, enter PARENTTASK.

12 Move the cursor to the next field in the Textbox Properties dialog box.

13 Close the Controls dialog box and the Textbox Properties dialog box.

14 Click the Save Application Definition.

Add expenditure type to the Labor [Actuals] subtab

To add the expenditure type field to the Labor [Actuals] subtab:

1 On the Applications tab in the Application Designer, select WOTRACK.

2 On the Workspace tab, click the Actuals subtab.

3 On the Actuals subtab, click the Labor subtab.

4 Click the Control Palette icon on the task bar. The Controls dialog box opens.

5 Drag the Textbox in the Controls dialog box to the location on the Labor subtab where you want the expenditure type field to appear.

Page 122: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

118 IBM Maximo: Upgrade Guide

6 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

7 In the Attribute field, select OA_EXPENDTYPE (object LABTRANS).

8 Move the cursor to the next field in the Textbox Properties dialog box, then close the dialog box.

9 Click the Save Application Definition.

Add expenditure type to the Materials [Actuals] subtab

To add the expenditure type field to the Materials [Actuals] subtab:

1 On the Applications tab in the Application Designer, select WOTRACK.

2 On the Workspace tab, click the Actuals subtab.

3 On the Actuals subtab, click the Materials subtab.

4 Click the Control Palette icon on the task bar. The Controls dialog box opens.

5 Drag the Textbox in the Controls dialog box to the location on the Materials subtab where you want the expenditure type field to appear.

6 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

7 In the Attribute field, select OA_EXPENDTYPE (object MATUSETRANS).

8 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

9 Click the Save Application Definition.

Add charge organization to the Materials [Actuals] subtab

To add the charge organization field to the Materials [Actuals] subtab:

1 On the Applications tab in the Application Designer, select WOTRACK.

2 On the Workspace tab, click the Actuals subtab.

3 On the Actuals subtab, click the Materials subtab.

4 Click the Control Palette icon on the task bar. The Controls dialog box opens.

5 Drag the Textbox in the Controls dialog box to the location on the Materials subtab where you want the charge organization field to appear.

6 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

7 In the Attribute field, select OA_CHARGE_ORG (object MATUSETRANS).

8 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

9 Click the Save Application Definition.

Page 123: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 119

Add non-labor resource organization to the Materials [Actuals] subtab

To add the non-labor resource organization field to the Materials [Actuals] subtab:

1 On the Applications tab in the Application Designer, select WOTRACK.

2 On the Workspace tab, click the Actuals subtab.

3 On the Actuals subtab, click the Materials subtab.

4 Click the Control Palette icon on the task bar. The Controls dialog box opens.

5 Drag the Textbox in the Controls dialog box to the location on the Materials subtab where you want the non-labor resource organization field to appear.

6 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

7 In the Attribute field, select OA_NLR_ORG (object MATUSETRANS).

8 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

9 Click the Save Application Definition.

Add expenditure type to the Services [Actuals] subtab

To add the expenditure type field to the Services [Actuals] subtab:

1 On the Applications tab in the Application Designer, select WOTRACK.

2 On the Workspace tab, click the Actuals subtab.

3 On the Actuals subtab, click the Services subtab.

4 Click the Control Palette icon on the task bar. The Controls dialog box opens.

5 Drag the Textbox in the Controls dialog box to the location on the Services subtab where you want the expenditure type field to appear.

6 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

7 In the Attribute field, select OA_EXPENDTYPE (object SERVRECTRANS).

8 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

9 Click the Save Application Definition.

Add charge organization to the services [Actuals] subtab

To add the charge organization field to the Services [Actuals] subtab:

1 On the Applications tab in the Application Designer, select WOTRACK.

2 On the Workspace tab, click the Actuals subtab.

3 On the Actuals subtab, click the Services subtab.

Page 124: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

120 IBM Maximo: Upgrade Guide

4 Click the Control Palette icon on the task bar. The Controls dialog box opens.

5 Drag the Textbox in the Controls dialog box to the location on the Services subtab where you want the charge organization field to appear.

6 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

7 In the Attribute field, select OA_CHARGE_ORG (object SERVRECTRANS).

8 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

9 Click the Save Application Definition.

Add non-labor resource organization to the Services [Actuals] subtab

To add the non-labor resource organization field to the Services [Actuals] subtab:

1 On the Applications tab in the Application Designer, select WOTRACK.

2 On the Workspace tab, click the Actuals subtab.

3 On the Actuals subtab, click the Services subtab.

4 Click the Control Palette icon on the task bar. The Controls dialog box opens.

5 Drag the Textbox in the Controls dialog box to the location on the Services subtab where you want the non-labor resource organization field to appear.

6 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

7 In the Attribute field, select OA_NLR_ORG (object SERVRECTRANS).

8 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

9 Click the Save Application Definition.

Add expenditure type to the Tools [Actuals] subtab

To add the expenditure type field to the Tools [Actuals] subtab:

1 On the Applications tab in the Application Designer, select WOTRACK.

2 On the Workspace tab, click the Actuals subtab.

3 On the Actuals subtab, click the Tools subtab.

4 Click the Control Palette icon on the task bar. The Controls dialog box opens.

5 Drag the Textbox in the Controls dialog box to the location on the Tools subtab where you want the expenditure type field to appear.

6 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

7 In the Attribute field, select OA_EXPENDTYPE (object TOOLTRANS).

Page 125: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 121

8 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

9 Click the Save Application Definition.

Add charge organization to the Tools [Actuals] subtab

To add the charge organization field to the Tools [Actuals] subtab:

1 On the Applications tab in the Application Designer, select WOTRACK.

2 On the Workspace tab, click the Actuals subtab.

3 On the Actuals subtab, click the Tools subtab.

4 Click the Control Palette icon on the task bar. The Controls dialog box opens.

5 Drag the Textbox in the Controls dialog box to the location on the Tools subtab where you want the charge organization field to appear.

6 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

7 In the Attribute field, select OA_CHARGE_ORG (object TOOLTRANS).

8 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

9 Click the Save Application Definition.

Add non-labor resource organization to the Tools [Actuals] subtab

To add the non-labor resource organization field to the Tools [Actuals] subtab:

1 On the Applications tab in the Application Designer, select WOTRACK.

2 On the Workspace tab, click the Actuals subtab.

3 On the Actuals subtab, click the Tools subtab.

4 Click the Control Palette icon on the task bar. The Controls dialog box opens.

5 Drag the Textbox in the Controls dialog box to the location on the Tools subtab where you want the non-labor resource organization field to appear.

6 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

7 In the Attribute field, select OA_NLR_ORG (object TOOLTRANS).

8 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

9 Click the Save Application Definition.

Page 126: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

122 IBM Maximo: Upgrade Guide

Adding fields to Purchase Requisition application

The following procedures add the optional purchase requisition fields. If you do not want to add a field, skip the corresponding procedure.

Add expenditure type to the PR Lines tab

To add the expenditure type field to the purchase requisition (PR) application:

1 On the Applications tab in the Application Designer, select PR.

2 On the Workspace tab, click the PR Lines subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the expenditure type field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_EXPENDTYPE (object PRLINE)

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Add charge organization to the PR Lines tab

To add the charge organization field to the purchase requisition (PR) application:

1 On the Applications tab in the Application Designer, select PR.

2 On the Workspace tab, click the PR Lines subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the charge organization field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_CHARGE_ORG (object PRLINE).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Adding fields to the Purchase Order application

The following procedures add the optional purchase order fields. If you do not want to add a field, skip the corresponding procedure.

Add expenditure type to the PO Lines tab

To add the expenditure type field to the purchase order (PO) application:

1 On the Applications tab in the Application Designer, select PO.

Page 127: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 123

2 On the Workspace tab, click the PO Lines subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the expenditure type field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_EXPENDTYPE (object POLINE).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Add charge organization to the PO Lines tab

To add the charge organization field to the purchase order (PO) application:

1 On the Applications tab in the Application Designer, select PO.

2 On the Workspace tab, click the PO Lines subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the charge organization field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_CHARGE_ORG (object POLINE).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Adding fields to the Invoice application

The following procedures add the optional invoice fields. If you do not want to add a field, skip the corresponding procedure.

Add expenditure type to the Invoice Lines tab

To add the expenditure type field to the Invoice application:

1 On the Applications tab in the Application Designer, select INVOICE.

2 On the Workspace tab, click the Invoice Lines subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the expenditure type field to appear.

Page 128: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

124 IBM Maximo: Upgrade Guide

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_EXPENDTYPE (object INVOICELINE)

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Add charge organization to the Invoice Lines tab

To add the charge organization field to the Invoice application:

1 On the Applications tab in the Application Designer, select INVOICE.

2 On the Workspace tab, click the Invoice Lines subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the charge organization field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_CHARGE_ORG (object INVOICELINE).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Adding fields to the Receipts application

The following procedures add the optional receipts fields. If you do not want to add a field, skip the corresponding procedure.

Add expenditure type to the Material Receipts tab

To add the expenditure type field to the Material Receipts tab:

1 On the Applications tab in the Application Designer, select RECEIPTS.

2 On the Workspace tab, click the Material Receipts subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the expenditure type field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_EXPENDTYPE (object MATRECTRANS).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

Page 129: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 125

8 Click the Save Application Definition.

Add charge organization to the Material Receipts tab

To add the charge organization field to the Material Receipts tab:

1 On the Applications tab in the Application Designer, select RECEIPTS.

2 On the Workspace tab, click the Material Receipts subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the charge organization field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_CHARGE_ORG (object MATRECTRANS).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Add non-labor resource organization to the Material Receipts tab

To add the non-labor resource organization field to the Material Receipts tab:

1 On the Applications tab in the Application Designer, select RECEIPTS.

2 On the Workspace tab, click the Material Receipts subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the non-labor resource organization field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_NLR_ORG (object MATRECTRANS).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Add expenditure type to the Service Receipts tab

To add the expenditure type field to the Service receipts tab:

1 On the Applications tab in the Application Designer, select RECEIPTS.

2 On the Workspace tab, click the Service receipts subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

Page 130: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

126 IBM Maximo: Upgrade Guide

4 Drag the Textbox in the Controls dialog box to the location on where you want the expenditure type field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_EXPENDTYPE (object SERVRECTRANS).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Add charge organization to the Service Receipts tab

To add the charge organization field to the Service Receipts tab:

1 On the Applications tab in the Application Designer, select RECEIPTS.

2 On the Workspace tab, click the Service Receipts subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the charge organization field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_CHARGE_ORG (object SERVRECTRANS).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Add non-labor resource organization to the Service Receipts tab

To add the non-labor resource organization field to the Service Receipts tab:

1 On the Applications tab in the Application Designer, select RECEIPTS.

2 On the Workspace tab, click the Service Receipts subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the non-labor resource organization field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_NLR_ORG (object SERVRECTRANS).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Page 131: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 127

Adding fields to the Issues and Transfers application

The following procedures add the optional issue fields. If you do not want to add a field, skip the corresponding procedure.

Add expenditure type to the Issue subtab

To add the expenditure type field to the Issue subtab:

1 On the Applications tab in the Application Designer, select INVISSUE.

2 On the Workspace tab, click the Issue subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location on the Issue subtab where you want the expenditure type field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_EXPENDTYPE (object MATUSETRANS).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Add charge organization to the Issue subtab

To add the charge organization field to the Issue subtab:

1 On the Applications tab in the Application Designer, select INVISSUE.

2 On the Workspace tab, click the Issue subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location on the Issue subtab where you want the charge organization field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_CHARGE_ORG (object MATUSETRANS).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Add non-labor resource organization to the Issue subtab

To add the non-labor resource organization field to the Issue subtab:

1 On the Applications tab in the Application Designer, select INVISSUE.

2 On the Workspace tab, click the Issue subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

Page 132: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

128 IBM Maximo: Upgrade Guide

4 Drag the Textbox in the Controls dialog box to the location on the Issue subtab where you want the non-labor resource organization field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select OA_NLR_ORG (object MATUSETRANS).

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Adding fields to the Cost Management application

You can add budget, burdened, committed, and remaining cost fields to the Cost Management application. These optional fields display the rolled-up project costs transferred from Oracle PA to Maximo Asset Management.

Add budget cost To add the budget cost field to the Cost Management (FINCNTRL) application:

1 On the Applications tab in the Application Designer, select FINCNTRL.

2 On the Workspace tab, click the Project subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the budget cost field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select BUDGETCOST (object FINCNTRL)

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Add burdened cost To add the burdened cost field to the Cost Management application:

1 On the Applications tab in the Application Designer, select FINCNTRL.

2 On the Workspace tab, click the Project subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the burdened cost field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select BURDENEDCOST (object FINCNTRL)

Page 133: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 129

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Add committed cost To add the committed cost field to the Cost Management application:

1 On the Applications tab in the Application Designer, select FINCNTRL.

2 On the Workspace tab, click the Project subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the committed cost field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select COMMITTEDCOST (object FINCNTRL)

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

Add remaining cost To add the remaining cost field to the Cost Management application:

1 On the Applications tab in the Application Designer, select FINCNTRL.

2 On the Workspace tab, click the Project subtab.

3 Click the Control Palette icon on the task bar. The Controls dialog box opens.

4 Drag the Textbox in the Controls dialog box to the location where you want the remaining cost field to appear.

5 Ensure that the new textbox field is highlighted, then click the Control Properties icon on the task bar. The Textbox Properties dialog box opens.

6 In the Attribute field, select REMAININGCOST (object FINCNTRL)

7 Move the cursor to the next field in Textbox Properties dialog box, then close the dialog box.

8 Click the Save Application Definition.

For more information about all listed fields, see the Oracle Project Accounting information in the IBM Maximo Enterprise Adapter System Administrator Guide for Oracle Applications 12 Adapter.

Page 134: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

130 IBM Maximo: Upgrade Guide

Enabling the financial control concurrent extract manager

The financial control concurrent extract manager (MAXFCEXP) initiates the transfer of project and task summary information from Oracle Project Accounting to the Maximo Asset Management Cost Management application.

To register procedure MAXFCEXP as a concurrent process:

1 In Oracle E-Business Suite, select Responsibility: System Administrator.

2 Select Concurrent | Program | Executable.

3 Enter the following values:

4 Save the data and close the form.

5 Select Concurrent | Program | Define.

6 Enter the following values:

Field Value

Executable MAXFCEXP [case-sensitive]

Short Name MAXFCEXP

Application Projects

You might want to set up a custom application and group outside of Oracle PA.

Description Financial Control Updates to the asset management system

Execution Method PL/SQL Stored procedure

Execution File Name maxora.extract_fc_data

Replace the schema name (in this case, maxora) with the schema name used in your installation.

Field Value

Program PRC: Asset Management System Financial Control Update from Oracle

Enable [Select this check box]

Short Name FCEXTRACT

Application Name Projects

Description Financial Control Updates to Asset Management System

Executable Name MAXFCEXP

Executable Method PL/SQL Stored Procedure

Page 135: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

Completing the upgrade process 131

7 Save the data.

8 Click INCOMPATIBILITIES.

9 In the Name field, select PRC: Asset Management System Financial Control Update from Oracle.

10 Save the data and close the form.

11 Click Parameters.

12 Enter the following values:

13 Move the cursor to the next Seq line and enter the following values:

14 Move the cursor to the next Seq line and enter the following values:

Field Value

Seq 10

Parameter Operating Unit ID

Description Operating Unit ID

Value Set 10/Number

Default Type Profile

Default Value ORG_ID

Display [Select this check box]

Field ValueSeq 20Parameter Project NumberDescription Project NumberValue Set PA_SRS_PROJECT_NUMBERDisplay [Select this check box]

Field Value

Seq 30

Parameter Budget Type

Description Budget Type

Value Set PA_SRS_BUDGET_TYPE_COST

Display [Select this check box]

Page 136: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Oracle ERP adapter upgrade process

132 IBM Maximo: Upgrade Guide

15 Move the cursor to the next Seq line and enter the following values:

* Replace the schema name (in this case, MAXORA) with the schema name used in your installation.

16 Save the data and close the form.

Providing access to the financial control concurrent extract manager

To provide access to this program to Projects Responsibility in Oracle E-Business Suite:

1 In Oracle, select Responsibility: System Administrator.

2 Select Security | Responsibility | Request.

3 Select View | Query by Example | Enter.

4 In the Group field, select All Project Programs.

5 Select View | Query by Example | Run.

6 Place the cursor on a row in the Requests table and Select File | New.

7 Enter the following values:

8 Save the data.

Field Value

Seq 40

Parameter Start Date

Description Retrieve all records modified on or after this date

Value Set FND_STANDARD_DATETIME

Default Type SQL Statement

Default Value* select maxora.MaxUtlPack.GetMaxOraCtl('FCEXTRACTDATE') from dual

Display [Select this check box]

Field Value

Type Program

Name PRC: Asset Management System Financial Control Update from Oracle

Application Projects

Page 137: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrading Integration Composer

Completing the upgrade process 133

Synchronizing Oracle employees and Maximo labor codes

To synchronize the labor and craft to update Maximo Asset Management with cost rates from Oracle Project Accounting, see the synchronizing Oracle employees and asset management system labor codes information.

Upgrading Integration Composer

If any of the following products are installed, you must also upgrade IBM Tivoli Integration Composer:

Change and Configuration Management Database (CCMDB)Tivoli Asset Management for ITService Request Manager

To upgrade to Integration Composer version 7, follow the instructions in the IBM Tivoli Integration Composer Installation Guide. Installing Integration Composer upgrades an existing version to a new version.

Completing the Maximo for Oil and Gas upgrade process

In version 6 of IBM® Maximo® for Oil and Gas, you can load ISO 14224 (1999) industry standard asset specifications, failure codes, or both. A newer version of the standard, ISO 14224 (2006), provides new and updated asset specifications and failure codes. You can load these values after you upgrade to version 7 of Maximo Oil and Gas.

Updates to asset specifications and failure codes

The upgrade process migrates 1999 and custom asset specifications and failure codes to version 7. If you take no further action, version 7 contains the same data as version 6.

You use two Maximo for Oil and Gas actions to load the 2006 data and additional custom asset specifications and failure codes. These actions are on the List tab in the Organizations (Oil) application.

If you select these actions multiple times, only records that were not previously loaded are selected.

The update procedures in version 7 reduce processing time from version 6. To further accelerate processing, update only one organization at a time.

Data to load Action

Asset specifications Oil and Gas > Update Asset Specifications

Failure codes Oil and Gas > Update Failure Codes

Page 138: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas upgrade process

134 IBM Maximo: Upgrade Guide

ISO 14224 (1999) data

Version 7 of Maximo for Oil and Gas does not provide 1999 ISO data. If you want to use 1999 data in version 7, that data must be loaded in version 6. The upgrade process migrates the 1999 data to version 7.

In most cases, the Maximo Oil and Gas actions update the 1999 data with 2006 values. When this is not possible, the 1999 record is retained and the 2006 record is added.

Custom data

The upgrade process migrates your custom asset specifications and failure codes to version 7. To insert additional custom data in version 7, you write and manually run statements to insert the custom data into auxiliary tables, and then you run one or both update actions.

Upgrade scenarios

The following table describes several scenarios that involve combinations of 1999 ISO data, 2006 ISO data, and custom data.

Scenario Processing

You use 1999 ISO data and custom data in version 6.

You want to load 2006 ISO data in version 7.

The upgrade process migrates the 1999 data and custom data to version 7. The custom data does not change.

You run one or both Oil and Gas update actions to update 1999 records with 2006 values and add any new 2006 records.

You do not use 1999 ISO data in version 6.

You use custom data in version 6.

You want to load 2006 ISO data in version 7.

The upgrade process migrates the custom data to version 7.

You run one or both Oil and Gas update actions to load the 2006 ISO records.

The custom data does not change, unless a 2006 record has the same unique index as a custom record. In that case, the update action updates the custom record with the 2006 data.

Page 139: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas upgrade process

Completing the upgrade process 135

You use 1999 ISO data and custom data in version 6.

You want to load 2006 ISO data in version 7.

You want to add additional custom data in version 7.

The upgrade process migrates the 1999 data and custom data to version 7.

You run one or both Oil and Gas update actions to update 1999 records with 2006 values and add any new 2006 records.

You write and manually run statements to insert the custom data into auxiliary tables. You then rerun one or both update actions to add the custom data to the database.

(Optional) You can insert the data into the auxiliary tables before you load the 2006 data. In this case, the update actions load the 2006 data and your custom records at the same time.

At any time after the upgrade, you want to add additional custom data.

You write and manually run statements to insert the custom data into auxiliary tables. You then run one or both update actions to add the custom data to the database.

Scenario Processing

Page 140: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas upgrade process

136 IBM Maximo: Upgrade Guide

Auxiliary tables

To insert custom data into the auxiliary tables, you can use any database client application. After you write and manually run statements to insert records, you run the Update Asset Specifications action, the Update Failure Codes action, or both.

You can insert custom records before or after you load the ISO tables. If you insert custom records first, the update action loads the custom records and the 2006 ISO records to the database. If you insert the custom records after you load the ISO records, run the applicable update action again to load the custom records to the database.

The following table lists the auxiliary tables that you can use to insert custom asset specifications and failure codes.

Type of data Auxiliary tables

Asset specifications PLUSG_AS_AUX1PLUSG_AS_AUX2PLUSG_AS_AUX3PLUSG_AS_AUX4PLUSG_AS_AUX5PLUSG_AS_AUX6

Failure codes PLUSG_FC_AUX1

Page 141: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas

Completing the upgrade process 137

PLUSG_AS_AUX1 table

You use the PLUSG_AS_AUX1 table to insert data in the MEASUREUNIT database table.

PLUSG_AS_AUX1 table

Examples insert into plusg_as_aux1 (measureunitid, abbreviation, description)values ('%', '%', 'Percent');

insert into plusg_as_aux1 (measureunitid, abbreviation, description)values ('A', 'A', 'Amperes');

Column Description Same As Type Length Nulls Allowed

Comments

MEASUREUNIT Unit of measure MEASUREUNIT.MEASUREUNITID UPPER 8 No The update process inserts new records and updates the abbreviation and description if the MEASUREUNIT record already exists.

ABBREVIATION Abbreviation MEASUREUNIT.ABBREVIATION ALN 8 Yes

DESCRIPTION Description M,EASUREUNIT.DESCRIPITION ALN 100 Yes

Page 142: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas upgrade process

138 IBM Maximo: Upgrade Guide

PLUSG_AS_AUX2 table

You use the PLUSG_AS_AUX2 table to insert data in the MAXDOMAIN database table.

PLUSG_AS_AUX2 table

Examples insert into plusg_as_aux2 (domainid, description, domaintype, maxtype, length)values ('ABATEMENT', 'Type of abatement control', 'ALN', 'ALN', 30);

insert into plusg_as_aux2 (domainid, description, domaintype, maxtype, length)values ('ACT_PRINCIPLE', 'Actuator Operating Principle', 'ALN', 'ALN', 40);

Column Description Same As Type Length Nulls Allowed

Comments

DOMAINID Domain MAXDOMAIN.DOMAINID UPPER 18 No The update process inserts new records. Existing records are not updated.

DESCRIPTION Description MAXDOMAIN.DESCRIPTION ALN 100 Yes

DOMAINTYPE Domain type MAXDOMAIN.DOMAINTYPE UPPER 20 No

MAXTYPE Data type MAXDOMAIN.MAXTYPE UPPER 8 Yes

LENGTH Length MAXDOMAIN.LENGTH INTEGER 12 Yes

Page 143: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas

Completing the upgrade process 139

PLUSG_AS_AUX3 table

You use the PLUSG_AS_AUX3 table to insert data in the ALNDOMAIN database table.

PLUSG_AS_AUX3 table

Examples insert into plusg_as_aux3 (domainid, value, description)values ('ABATEMENT', 'Steam', 'Steam');

insert into plusg_as_aux3 (domainid, value, description)values ('ABATEMENT', 'Water', 'Water');

insert into plusg_as_aux3 (domainid, value, description)values ('ACT_PRINCIPLE', 'Single-acting', 'Single-acting');

Column Description Same As Type Length Nulls Allowed

Comments

DOMAINID Domain MAXDOMAIN.DOMAINID UPPER 18 No

VALUE Value ALNDOMAIN.VALUE 100 No The update process inserts only values that are not related to the DOMAINID column in the ALNDOMAIN table.

DESCRIPTION Description ALNDOMAIN.DESCRIPTION ALN 100 Yes

Page 144: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas upgrade process

140 IBM Maximo: Upgrade Guide

PLUSG_AS_AUX4 table

You use the PLUSG_AS_AUX4 table to insert data in the ASSETATTRIBUTE, CLASSSPEC, and CLASSSPECUSEWITH tables.

The CLASSPECUSEWITH table shows the applications in which class specs can be used. Each new CLASSSPEC record generates three CLASSPECUSEWITH records, one for ASSET, one for ITEM, and one for LOCATION. You can add other values by using the Classifications application.

You cannot add asset attributes to existing classifications. You can add them only when you insert the classification at the same time.

PLUSG_AS_AUX4 table

Column Description Same As Type Length Nulls Allowed

Comments

ASSETATTRID Asset attribute identifier

ASSETATTRIBUTE.ASSETSTTRID UPPER 8 No The update process inserts new ASSETATTRIBUTE and CLASSSPEC records, and updates the description and unit of measure if the ASSETATTRIBUTE record already exists.

The ISO standard code consists of the first letter of the description, followed by four digits (for example, A0200).

Custom records can use any format in this field.

DESCRIPTION Description ASSETATTRIBUTE.DESCRIPTION ALN 100 Yes

Page 145: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas

Completing the upgrade process 141

DATATYPE Data type ASSETATTRIBUTE.DATATYPE UPPER 8 No Valid values:

NUMERIC - for attributes that are associated with a MEASUREUNITID value or are from a numeric type.

ALN - for attributes that are associated with a DOMAINID value or are from a free-text type.

MEASUREUNITID Unit of measure MEASUREUNIT.MEASUREUNITID UPPER 8 Yes Applies only if DATATYPE = NUMERIC. This value must exist in the MEASUEREUNIT table.

DOMAINID Domain MAXDOMAIN.DOMAINID UPPER 18 Yes Applies only if DATATYPE = ALN. The value must exist in the MAXDOMAIN table. If DATATYPE = ALN, this value can be null.

CLASSIFICATIONID Classification CLASSIFICATION.CLASSIFICATIONID UPPER 8 No This value is the identifier for the PLUSG_AS_AUX5 table.

If the length of this value is 2, the asset attribute applies to parent and child classifications of the same type. If the length of this value is 4, the asset attribute applies only to the child classification.

Column Description Same As Type Length Nulls Allowed

Comments

Page 146: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas upgrade process

142 IBM Maximo: Upgrade Guide

Examples insert into plusg_as_aux4 (assetattrid, description, datatype, measureunitid, domainid, classificationid)values ('A0100', 'A-frame height', 'NUMERIC', 'M', '', 'CR');

insert into plusg_as_aux4 (assetattrid, description, datatype, measureunitid, domainid, classificationid)values ('A0600', 'Actuation Principle', 'ALN', '', 'ACT_PRINCIPLE', 'VA');

insert into plusg_as_aux4 (assetattrid, description, datatype, measureunitid, domainid, classificationid)values ('N0700', 'Number of Battery Banks', 'NUMERIC', '', '', 'UP');

/* The same asset attribute can be inserted with different classifications (CE and GT) */

insert into plusg_as_aux4 (assetattrid, description, datatype, measureunitid, domainid, classificationid)values ('A0500', 'Air-inlet Filtration Type', 'ALN', '', '', 'CE');

insert into plusg_as_aux4 (assetattrid, description, datatype, measureunitid, domainid, classificationid)values ('A0500', 'Air-inlet Filtration Type', 'ALN', '', '', 'GT');

/* When the classificationid (in this table) length is 2, the asset attribute applies to all classifications of that type (parent and children). If the length is 4, the asset attribute applies only to that child.*/

insert into plusg_as_aux4 (assetattrid, description, datatype, measureunitid, domainid, classificationid)values ('A0900', 'Annular Preventers - Manufacturer (and Model)', 'ALN', '', '', 'DEBS');

insert into plusg_as_aux4 (assetattrid, description, datatype, measureunitid, domainid, classificationid)values ('A0900', 'Annular Preventers - Manufacturer (and Model)', 'ALN', '', '', 'DEBT');

Page 147: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas

Completing the upgrade process 143

PLUSG_AS_AUX5 table

You use the PLUSG_AS_AUX5 table to insert data in the CLASSIFICATION table.

You cannot add child classifications to existing classifications. You can add them only when you insert the parent classification at the same time.

PLUSG_AS_AUX5 table

Example insert into plusg_as_aux5 (classificationid, description)values ('CE', 'Combustion engines (piston)');

insert into plusg_as_aux5 (classificationid, description)values ('CEDE', 'Combustion engines (piston) - Diesel engine');

insert into plusg_as_aux5 (classificationid, description)values ('CEGE', 'Combustion engines (piston) - Otto (gas) engine');

insert into plusg_as_aux5 (classificationid, description)values ('CO', 'Compressors');

Column Description Same As Type Length Nulls Allowed

Comments

CLASSIFICATIONID Classification CLASSIFICATION.CLASSIFICATIONID UPPER 8 No The update process inserts new records and updates the description if the CLASSIFICATION record already exists.

DESCRIPTION Description CLASSIFICATION.DESCRIPTION ALN 100 Yes

Page 148: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas upgrade process

144 IBM Maximo: Upgrade Guide

PLUSG_AS_AUX6 table

You use the PLUSG_AS_AUX6 table to insert data in the CLASSSTRUCTURE, CLASSUSEWITH, and CLASSANCESTOR tables.

The CLASSUSEWITH table shows the applications in which class structures can be used. Each new CLASSSTRUCTURE record generates three CLASSUSEWITH records, one for ASSET, one for ITEM, and one for LOCATION. You can add other values by using the Classifications application.

You cannot add child classifications to existing classifications. You can add them only when you insert the parent classification at the same time.

PLUSG_AS_AUX6 table

Column Description Same As Type Length Nulls Allowed

Comments

CLASSIFICATIONID Classification CLASSIFICATION.CLASSIFICATIONID UPPER 8 No The update process inserts new records. Existing records are not updated.

Child classifications must start with the CLASSIFICATIONID value of their parent.

Example:

CE - Parent classification

CEDE - Child classification of CE

CDDE - Not a child classification of CE

DESCRIPTION Description CLASSSTRUCTURE.DESCRIPTION ALN 100 Yes

PARENT Parent class structure

YORN 1 No Specifies whether the CLASSIFICATIONID value is a parent classification.

Page 149: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas

Completing the upgrade process 145

Examples /* CE is the parent classification of CEDE and CEGE. */

insert into plusg_as_aux6 (classificationid, description, parent)values ('CE', 'CE - Template for Combustion engines', '1');

insert into plusg_as_aux6 (classificationid, description, parent)values ('CEDE', 'CEDE - Combustion (piston) - Diesel engine', '0');

insert into plusg_as_aux6 (classificationid, description, parent)values ('CEGE','CEGE - Combustion engines (piston) - Otto (gas) engine', '0');

/* CO is the parent classification of COAX, COBL and COCE. */

insert into plusg_as_aux6 (classificationid, description, parent)values ('CO', 'CO - Template for Compressors', '1');

insert into plusg_as_aux6 (classificationid, description, parent)values ('COAX', 'COAX - Compressors - Axial', '0');

insert into plusg_as_aux6 (classificationid, description, parent)values ('COBL', 'COBL - Compressors - Blowers/fans', '0');

insert into plusg_as_aux6 (classificationid, description, parent)values ('COCE', 'COCE - Compressors - Centrifugal', '0')

Page 150: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas upgrade process

146 IBM Maximo: Upgrade Guide

PLUSG_FC_AUX1 table

You use the PLUSG_FC_AUX1 table to insert data in the FAILURECODE and FAILURELIST database tables.

You cannot add failure codes of type PROBLEM, CAUSE, or REMEDY to existing failure classes. You can add them only when you insert the failure class at the same time.

PLUSG_FC_AUX1 table

Examples /* Failure Hierarchy Codes. */

insert into plusg_fc_aux1 (failurecode, description)values ('CEDE', 'Combustion engines (piston) - Diesel engine');

insert into plusg_fc_aux1 (failurecode, description)values ('CEGE', 'Combustion engines (piston) - Otto (gas) engine');

insert into plusg_fc_aux1 (failurecode, description)values ('COAX', 'Compressors - Axial');

Column Description Same As Type Length Nulls Allowed

Comments

FAILURECODE Failure code UPPER 8 No The update process inserts new records. Existing records are not updated.

DESCRIPTION Description ALN 100 Yes

TYPE Type of failure code

UPPER 12 Yes Valid values:

nullPROBLEMCAUSE REMEDY

ABBREVFAILCODE Failure code abbreviation

UPPER 8 Yes A 2-digit code that is needed only when TYPE = PROBLEM.

Page 151: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the Maximo for Oil and Gas

Completing the upgrade process 147

insert into plusg_fc_aux1 (failurecode, description)values ('FGBA', 'Fire and gas detectors - Others');

/* PROBLEM - If a problem is applicable to all failure codes being inserted that start with 'CE', user can insert only 'CE' in abbrevfailcode. */

insert into plusg_fc_aux1 (failurecode, description, type, abbrevfailcode)values ('AIR', 'Abnormal Instrument Reading', 'PROBLEM', 'CE');

/* PROBLEM - If a problem is applicable to a specific failure code being inserted, user can insert the 4-digit failure code ('FGBA') in abbrevfailcode. */

insert into plusg_fc_aux1 (failurecode, description, type, abbrevfailcode)values ('FTF', 'Failure to Function on Demand', 'PROBLEM', 'FGBA');

/* CAUSE - Applicable to all failure codes*/

insert into plusg_fc_aux1 (failurecode, description, type)values ('DESGEN', 'Design-related Causes - General', 'CAUSE');

insert into plusg_fc_aux1 (failurecode, description, type)values ('IMPCAP', 'Improper Capacity', 'CAUSE');

/* REMEDY - Applicable to all failure codes */

insert into plusg_fc_aux1 (failurecode, description, type)values ('RPL', 'Replace', 'REMEDY');

insert into plusg_fc_aux1 (failurecode, description, type)values ('REP', 'Repair', 'REMEDY');

Page 152: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the upgrade for Maximo Mobile Work Manager or Maximo Mobile Inventory Manager

148 IBM Maximo: Upgrade Guide

Completing the upgrade for Maximo Mobile Work Manager or Maximo Mobile Inventory Manager

On the application server, after you deploy the maximo.ear file that points to the upgraded database, complete the following steps:

1 Navigate to <maximo_root>\mobiletools\maximo\metadatafiles.

2 Rename mobileinv.xml to mobileinv.xml.ORIGINAL.

3 Rename mobilewo.xml to mobilewo.xml.ORIGINAL.

4 Open and modify the following file to specify your application server and port usage: <maximo_root>\mobiletools\maximo\mobiletools.properties.

5 Open a command prompt to <maximo_root>\mobiletools\maximo\

6 Execute the following command:

exportmetadata.cmd mobileinv metadatafiles\mobileinv.xml

7 Execute the following command:

exportmetadata.cmd mobilewo metadatafiles\mobilewo.xml

Completing the upgrade for CCMDB

There is a significant difference between the groups that were used to provide access to applications in Maximo 6.2.5 and the set of groups used in CCMDB 7.2. Listed below are the groups and roles used in CCMDB 7.2:

Group Roles

PMCIOWNER CI Owner

PMCFGADM Configuration Administrator

PMCFGAUD Configuration Auditor

PMCFGLIB Configuration Librarian

PMCFGMGR Configuration Manager

PMCHANGEADMIN Change Administrator

PMCHANGEANALYST Change Analyst

PMCHANGEAPPROVER Change Approver

PMCHANGEIMPL Change Implementer

PMCHANGEMGR Change Manager

PMCHANGEOWNER Change Owner

PMREQUESTER Process Management Requester

Page 153: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Running the VarcharMultiplier utility for double-byte languages

Completing the upgrade process 149

CCMDB 7.2 groups were designed to adhere to ITIL® specifications.

You will have to plan and execute the migration of users that were previously assigned to groups in Maximo 6.2.5 to groups provided in CCMDB 7.2 that are applicable to their role and their need to access particular applications within the Maximo console.

For more information, you can access ITIL best practice information from each application within the Maximo console made available though its integration with the IBM Tivoli Unified Process tool.

Running the VarcharMultiplier utility for double-byte languages

If your upgraded database is for a double-byte language, such as Japanese, Korean, or Simplified Chinese, run the VarcharMultiplier utility before you import translated data (xliff files). Run the VarcharMultiplier utility so that you can import xliff files without truncation errors.

The VarcharMultiplier utility is applicable only to MS SQL Server and DB2 databases. It is not needed for Oracle databases.

The VarcharMultiplier utility is a batch file, varcharmultiplier.bat. You can find the varcharmultiplier.bat file in the tools\maximo directory of your version 7 installation.

For more information about the VarcharMultiplier utility, see the following online tech note: Tdtoolkit data truncation error during import when using SQLServer or DB2 and double-byte languages.

Completing the upgrade for globalized languages

If you are using globalized languages, you must run commands to apply the translated application files.

To apply globalized languages:

1 Verify that after the upgrade the following file structures exist for the products or components that you are upgrading:

PMRELEASEADMIN Release Administrator

PMRELEASEMGR Release Manager

PMRELEASEOWNER Release Owner

PMRELEASESPECIALIST Release Specialist

Group Roles

Page 154: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the upgrade for globalized languages

150 IBM Maximo: Upgrade Guide

Maximo Asset Management

<Maximo_root>\tools\maximo\<lang code>\xliff<Maximo_root>\tools\maximo\<lang code>\xliff\common_pmp

The <lang code> is the code for the globalized language, for example, nl for Dutch.

SAP ERP adapter

<Maximo_root>\tools\maximo\<lang code>\xliff\sap2005

Oracle ERP adapter

<Maximo_root>\tools\maximo\<lang code>\xliff\oa12

Industry solutions or other product

<Maximo_root>\tools\maximo\<lang code>\xliff\<industry solution or product name>

For example, the globalized Dutch files for Maximo for Service Providers are in <Maximo_root>\tools\maximo\nl\xliff\serviceprovider

The xliff folder contains application folders that contain .xliff files, for example, ACTION.xliff.

2 From the <Maximo_root>\tools\maximo directory, run the following commands as needed to import the .xliff files. The command lines use Dutch (nl) as an example.

Maximo Asset Management, all versions

TDToolkit -pmpupdate"common_pmp" -version"V7100-000"

Maximo Asset Management 7.1.1

TDToolkit -import -tlnl -version”V7100-000”

The above command replaces the primary language with Dutch. To add a language instead of replacing the primary one, run the following command:

TDToolkit -addlangnl

SAP ERP adapter

TDToolkit -pmpupdate”DBSAP2005” -version”V7100-000”TDToolkit -pmpupdate”sap2005” -version”V7100-000”

Oracle ERP adapter

TDToolkit -pmpupdate”DBOA11I” -version”V7100-000”TDToolkit -pmpupdate”oa12” -version”V7100-000”

An industry solution (for example, Maximo for Service Providers)

TDToolkit -pmpupdate”serviceprovider” -version”V7100-000

Page 155: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the upgrade for globalized languages

Completing the upgrade process 151

The -pmpupdate tag applies translation for the primary language and for any additional language.

Page 156: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Completing the upgrade for globalized languages

152 IBM Maximo: Upgrade Guide

Page 157: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

© Copyright IBM Corp. 2007, 2013 153

If you use the Maximo Enterprise Adapter (MEA), the pre-upgrade and post-upgrade tasks that you must do depend on the data format that you use in the IBM Maximo Enterprise Adapter XML files or interface tables, and the extent of the customization. Not all update tasks apply to all situations.

Maximo Enterprise Adapter for SAP

The Maximo Asset Management upgrade program upgrades the Maximo® Enterprise Adapter for SAP ERP 6.0 (SAP ERP adapter) and your Maximo database at the same time. Run the upgrade program only once. After completing the upgrade, your SAP ERP adapter will be upgraded to release 7.1.

What is new

Before you upgrade the SAP ERP adapter, ensure that you are aware of the features in release 7.1 and how the features might affect your implementation and customizations.

Inbound invoices integration

In release 7.1 of the SAP ERP adapter, one invoice enterprise service manages the transfer of SAP MM invoices, FI invoices, and invoice variances to Maximo. If you have any customizations for FI invoices or invoice variances, you must plan to move them to the MM invoice enterprise service.

Purchase requisition integration

In release 7.1, you can now transfer purchase requisitions from the Maximo database into your SAP system using the new purchase requisition BAPI (Business Application Programming Interfaces). This new BAPI gives you the option to send purchase requisition header long description to SAP purchase requisition.

The purchase requisition data that is sent to SAP includes Maximo purchase requisition header information and long descriptions. After the purchase requisition data is sent to SAP, SAP can send purchase requisition status updates back to Maximo.

For more information, see the IBM Maximo Enterprise Adapter System Administrator Guide for SAP ERP 6.0 Adapter.

Maximo Enterprise Adapter updates A

Page 158: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Maximo Enterprise Adapter for Oracle Applications

154 IBM Maximo: Upgrade Guide

What is upgraded

The upgrade program adds columns, external system, enterprise services, and publish channels to the SAP ERP adapter. The upgrade program also marks all of the obsolete components as user-defined.

The upgrade program uses the DBSAP2005_MetaDoc.xml file to add, modify, or delete SAP ERP adapter integration components for the Maximo 7.1 release.

For more information about end points, external system, enterprise services, publish channels, columns, objects, and integration controls, see the IBM Maximo Enterprise Adapter System Administrator Guide for SAP ERP 6.0 Adapter.

What is not upgraded

The upgrade program deletes the following enterprise services from SAP ERP adapter:

MX6_INVOICEFI_TOMXMX6_INVOICEVAR_TOMX

Maximo Enterprise Adapter for Oracle Applications

The Maximo Asset Management upgrade program upgrades Maximo® Enterprise Adapter for Oracle Applications (Oracle ERP adapter) and your Maximo database at the same time. The upgrade program only supports Oracle E-Business Suite 12. After you complete the upgrade, the Oracle ERP adapter is upgraded from release 6.2 to release 7.1.

What is new

Before you upgrade the Oracle ERP adapter, ensure that you are aware of the features in release 7.1 and how the features might affect your implementation and customizations.

Oracle Project Accounting interfaces

The Oracle Project Accounting interfaces are now part of the Oracle ERP adapter.

If the interfaces are installed in your environment, the Maximo Asset Management upgrade program upgrades them from release 6.2 to release 7.1. Otherwise, the upgrade program installs the release 7.1 interfaces.

Inbound company interface

Oracle E-Business Suite uses the inbound company interface of the Oracle ERP adapter to send vendor information and vendor contacts to Maximo Asset Management. This interface has changed to support the vendor changes in Oracle E-Business Suite.

The following changes have been made to the inbound company interface:

Page 159: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Maximo Enterprise Adapter for Oracle Applications

Maximo Enterprise Adapter updates 155

Oracle E-Business Suite sends all vendor information and vendor contacts to Maximo Asset Management during the initial synchronization of companies.

Oracle E-Business Suite sends any contact updates and insertions, including first name, last name, telephone, e-mail, and fax, to Maximo Asset Management in real time regardless of whether vendors become updated.

Maximo Asset Management does not receive bank information. Oracle E-Business Suite handles all the banking transactions.

Supplier data mapping has changed to accommodate the vendor changes in Oracle E-Business Suite.

For more information about the supplier data mapping, see the IBM Maximo Enterprise Adapter Version 7.1 Integration Mappings Guide for Oracle Applications 12 Adapter.

Inbound purchase order interface

Oracle E-Business Suite provides two additional line types: fixed price and rate value base. These line types are sent to the Maximo Asset Management inbound purchase order interface as service line types.

Outbound purchasing interfaces

You can transfer new and updated purchase orders and contracts from Maximo Asset Management to Oracle E-Business Suite. The data transfer takes place using Oracle open interface tables and public APIs.

The purchasing interfaces have the following capabilities:

Uses standard concurrent processes and purchasing documents open interface for creating purchase orders and purchase contracts.

After a purchase order and a purchase contract are approved in Maximo Asset Management, the Oracle ERP adapter adds records to the following tables:

PO_HEADERS_INTERFACEPO_LINES_INTERFACEPO_DISTRIBUTIONS_INTERFACE

Sends updated information to Oracle E-Business Suite using Oracle standard APIs, when the Quantity, Price, Need By, and Promise Date fields are updated in Maximo Asset Management purchase orders.

Sends updated information to Oracle E-Business Suite using purchasing documents open interface when the Contract Price field is updated.

Sends updated information to Oracle E-Business Suite using Oracle standard APIs, when Maximo Asset Management purchase orders and contracts are canceled.

Sends purchase order releases that are in Maximo Asset Management as standard purchase orders to Oracle E-Business Suite.

For more information about the outbound purchasing interfaces, see “What is not upgraded” on page 158.

Page 160: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Maximo Enterprise Adapter for Oracle Applications

156 IBM Maximo: Upgrade Guide

Inbound contract interface

Oracle E-Business Suite sends the fixed price line type for blanket purchase orders and contracts as a service line type in the Maximo Asset Management inbound contract interface.

The Oracle ERP adapter uses the OAPCDEFORDERUNIT integration control as the order unit default when no unit of measure is specified on a purchase contract line in Oracle E-Business Suite.

Inbound invoice interface

The invoice line number for an inbound invoice is a concatenation of the number 1, a four-digit Oracle invoice line number, and a four-digit distribution line number. Commas are placed after three digits from right to left. For example: 100,010,001.

Outbound lot item

If the outbound lot item that is sent to Oracle E-Business Suite is a lot controlled item, you must set a lot prefix and a lot start number in Maximo Asset Management.

For more information about the outbound lot item, see the IBM Maximo Enterprise Adapter Version 7.1 System Administrator Guide for Oracle Applications 12 Adapter.

What is upgraded

The Maximo Asset Management upgrade utilities program uses the DBOA11I_MetaDoc.xml file to add, modify, or delete the Oracle ERP adapter integration components for Maximo Asset Management 7 and Oracle E-Business Suite 12.

The Maximo Asset Management upgrade program adds the following components to the Oracle ERP adapter:

New attributesEnterprise services and publish channelsThe external system (OA12)Integration controlsIntegration control registration with enterprise services and publish channels

The upgrade program also marks all of the obsolete components as user-defined and upgrades the external system that you used in the Oracle ERP adapter 6.2.

New attributes

The Oracle ERP adapter provides the following new attributes:

Attribute name Description Type COMPCONTACT.OA_DISABLED Remove disabled Oracle

company contactNon-persistent

COMPCONTACT.OA_EXTERNALREFID Vendor contact ID Persistent ITEM.OA_ITM_LOT_NUMBER Item lot number Non-persistent

Page 161: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Maximo Enterprise Adapter for Oracle Applications

Maximo Enterprise Adapter updates 157

Enterprise services and publish channels

The upgrade program replaces the release 6.2 inbound and outbound interfaces with the enterprise services and publish channels of the Oracle ERP adapter 7.1.

The following table shows the release 6.2 inbound interfaces and the release 7.1 enterprise services:

The following table shows the release 6.2 outbound interfaces and the release 7.1 publish channels:

ITEM.OA_ITM_LOT_PREFIX Item lot prefix Non-persistentPOLINE.OA_RATELINE Indicates if PO line is of rate

typePersistent

PURCHVIEW.OA_LINESTATUSIFACE_FLG Line status flag Non-persistent

Inbound interfaces Enterprise services

MX6_COA MXCOA_FROA12

MX6_CRAFT MXCRAFT_FROA12

MX6_GLCOMP MXGLCOMP_FROA12

MX6_INVBAL MXINVBAL_FROA12

MX6_INVENTORY MXINVENTORY_FROA12

MX6_INVISSUE MXINVISSUE_FROA12

MX6_INVOICE MXINVOICE_FROA12

MX6_ITEM MXITEM_FROA12

MX6_LABOR MXLABOR_FROA12

MX6_PC MXPC_FROA12

MX6_RCVROTITM MXRCVROTITM_FROA12

MX6_PROJ MXPROJ_FROA12

MX6_RECEIPT MXRECEIPT_FROA12

MX6_PO MXPO_FROA12

MX6_PR MXPR_FROA12

MX6_VENDOR MXVENDOR_FROA12

Outbound interfaces Publish channels

MX6_GLTXN MXGLTXN_TOOA12

MX6_INVENTORY MXINVENTORY_TOOA12

MX6_INVOICE MXINVOICE_TOOA12

MX6_INVRES MXINVRES_TOOA12

MX6_ITEM MXITEM_TOOA12

MX6_PC MXPC_TOOA12

MX6_PO MXPO_TOOA12

MX6_PROJTXN MXPROJTXN_TOOA12

Page 162: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Component name changes

158 IBM Maximo: Upgrade Guide

Integration controls

The following table lists the new integration controls:

For more information about release 7.1 features, see the IBM Maximo Enterprise Adapter Version 7.1 System Administrator Guide for Oracle Applications 12 Adapter.

What is not upgraded

Release 7.1 of the Oracle ERP adapter no longer supports the Cooperative Applications Initiative (CAI) outbound purchasing interfaces. The POAPI, which is the related integration control, is now obsolete and is marked as user-defined by the upgrade program.

Component name changes

Some Maximo Enterprise Adapter component names and functions have changed in version 7. The following table shows the version 6 component names and their corresponding version 7 component names.

Adapters

In version 7, the concept of an adapter has changed. The adapter is a mechanism to group inbound integration components (enterprise services) and outbound integration components (publish channels) that use a specific domain value.

MX6_PR MXPR_TOOA12

MX6_RECEIPT MXRECEIPT_TOOA12

Outbound interfaces Publish channels

Control name Description Value

OAITMLOTPREFIX Default lot prefix for lot controlled item Null (D)

OAITMLOTSTARTNUM Default lot start number for lot controlled item Null (D)

OAPCDEFORDERUNIT Order unit default on purchase contract line when no unit measure is specified on a purchase order line in Oracle

Null (D)

Version 6 component name Version 7 component name

Interface control Integration control

Integration object Object structure

Inbound interface Enterprise service

Outbound interface Publish channel

Page 163: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

External systems

Maximo Enterprise Adapter updates 159

The adapter grouping eliminates the need to define unique relationships between the adapter and enterprise services or publish channels. Inbound and outbound integration components are cross-functional.

You can create an adapter, or you can use the predefined MAXIMO adapter. You can use the Domains application to maintain adapters. If necessary, you can create multiple adapters.

Adapters have the following characteristics:

An adapter can group enterprise services and publish channels.

Any adapter can work with interface tables and Web services.

In version 7, there is no concept of an internal and an external adapter. Also, the inbound processing layer does not require any interpretation properties.

ATTENTION You can no longer use the MX5X adapter in version 7. The MX5X adapter, which supported the upgrade from version 5 to version 6, is removed during the version 7 upgrade process.

External systems

In version 7, the external system definition includes some new features:

Enterprise services and publish channels from multiple adapters can be associated with an external system.

The endpoint that is defined on an external system is the default endpoint value for all of the associated publish channels. Endpoint values that are associated with a publish channel can override the external system default endpoint value.

The external system does not have an associated adapter.

Queues

When you migrate to version 7, a new version of the application server is installed. The upgrade process also changes the default queue names. You must re-create your Java Message Service (JMS) queues that are used by the integration framework. You can use the provided error queue definition to support your implementation.

For more information about the creation and configuration of queues, see the JMS queue configuration information in the Integration Guide.

Endpoints and handlers

In version 7, the integration framework has extended the endpoint and handler capabilities. The End Points application replaces the End Point dialog box that

Page 164: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Endpoints and handlers

160 IBM Maximo: Upgrade Guide

was in the version 6 External Systems application. Endpoint properties can now be overwritten at run time. You can use custom code to change a property value instead of relying on the preconfigured endpoint property.

MXXMLFILE endpoint and XMLFILE handler

Before you upgrade, you must ensure that the provided MXXMLFILE endpoint and its XMLFILE handler exist in the Maximo 6 database. An error occurs when the upgrade validation utility does not detect the MXXMLFILE endpoint and the XMLFILE handler in the Maximo database. Create and configure this endpoint and handler to avoid an upgrade validation utility error.

Flat files or interface tables

If you use flat files or interface tables, you must select the Support Flat Structure check box on the Object Structure tab in the Object Structures application. To support a flat structure and an interface table column, the objects are checked for valid column names and duplications. If duplicate column names exist, you can use the Add/Modify Alias dialog box in the Object Structures application to change the alias name.

For more information about endpoint and handler changes, see the endpoints and handlers information in the Integration Guide.

Web service handler

The WEBSERVICE handler has some property changes to accommodate the changed Web service functions.

USERNAME handler property

The USERNAME handler property replaces the USERID handler property, but the property capability remains. If the specified Web service is secured, you must specify a user name.

MEP handler property

The MEP handler property replaces the ONEWAYWS handler property. The MEP handler property has capabilities that are different from the ONEWAYWS handler property.

This optional property specifies the message exchange pattern for the Web service. This property supports the following values. If you do not provide a value, the default value sendreceive is used.

Value Web service operation type

sendreceive Request and response

sendrobust Request with void or fault response

fireandforget Request only, no response, or fault

Page 165: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integration controls

Maximo Enterprise Adapter updates 161

Integration controls

The Maximo Asset Management integration controls replace the Maximo 6 interface controls. The integration control has capabilities that are different from the interface control.

Integration controls do not have an association with the adapter, instead they are defined at the system level. You must assign controls to any enterprise service and publish channel that is referencing a control in a Java processing class or processing rule.

The control values are configured at the external system level. Two external systems that process the same enterprise service or publish channel can share the same processing logic, class files, and processing rules, yet they process the data differently because they use different control values.

Integration objects and integration points

In version 7, integration objects are renamed to object structures. Additionally, the integration point has been consolidated into the object structure. The object structure identifies the Java processing classes for both inbound and outbound processing, which were previously defined on the integration point.

The object structure supports five inbound operations by default. You can use the object structure as a service to support inbound message processing. The object structure service can be invoked as a Web service by using an enterprise bean or HTTP.

User-defined integration objects may be unaltered when they are moved to object structures. System-provided integration objects are merged with the corresponding version 7 object structures. The resulting object structure includes any new content, such as a new object, that was added to the object structure as part of the version 7 enhancements. Also, included are system-provided object structures that were added as enhancements for version 7. If you added an object to a system-provided integration object in version 6, and the corresponding version 7 object structure was added in the same object, the hierarchical relationship for the version 7 object is provided.

In version 6, alternate keys for objects within an integration object were defined as part of the integration object definition. In version 7, the alternate key is maintained as part of the object configuration in the Database Configuration application. The upgrade utility moves the alternate keys from the integration object to the object definition.

Columns that are configured with an alias name in version 6 are retained in version 7. If the alias value for a column in version 6 differs from the value that is provided in version 7, the version 6 value is retained.

The setting restriction attribute that is configurable in the integration object in version 6 is now configured at the object attribute level. The configured value in version 6 is moved to the object attribute definition. As a result, an object column can have only one configured value for the setting restriction in version 7. In version 6, the setting restriction for a single column value can vary across integration objects.

Page 166: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integration objects and integration points

162 IBM Maximo: Upgrade Guide

The column configuration for persistent and nonpersistent columns in version 6 integration objects remain untouched. For system-provided object structures, additional columns might be included in version 7.

The version 6 concept of user-defined columns in an object structure is replaced by nonpersistent attributes, which can be defined at the object level in the Database Configuration application. User-defined columns are reimplemented as nonpersistent columns, which are marked as included in the object structure.

You can create object structure services that can be invoked from an external application. Object structure services support a synchronous invocation of object structures that do not require the configuration of an external system, JMS queues, or an enterprise service.

The concept of a merged integration object is no longer supported in version 7. However, you can duplicate the merged object capability by creating a nonpersistent business object and providing the necessary processing classes to map the nonpersistent object to the persistent objects. The upgrade process replaces the two version 6 system-provided merged integration objects with nonpersistent objects.

Integration object content changes

The objects listed in the following table have been either added to or removed from the object structure as part of the upgrade to version 7.

Object structures with a consumed by value of INTEGRATION can be used by other systems. Object structures with a consumed by value of MIGRATIONMGR are used exclusively by the Migration Manager application. If you want to use an object structure that is exclusively defined for the Migration Manager application, you can duplicate the object structure and change the Consumed by value to INTEGRATION.

ATTENTION The upgrade utility deletes the MXMAXROLE and the MXWF (DM) integration objects from the Maximo database.

The upgrade utility also deletes any instance of the MX5X adapter and its associated integration objects from the Maximo database.

New object structures

The following object structures are new to version 7:

MXCLASSIFICATIONMXENTSRV

Integration object Object Change

MXASSET ASSETSPEC Added to the object structure.

MXITEM ITEMSPEC Added to the object structure.

MXLOCATION LOCATIONSPEC Added to the object structure.

MXPERSON SMS Added to the object structure.

MXINTOBJECT MAXINTPOINT Removed from the object structure.

Page 167: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Inbound and outbound interfaces

Maximo Enterprise Adapter updates 163

MXIFACECONTROLMXIFACEINVOKEMXIFACEOUTMXIMMXINCIDENTMXLAUNCHMXLMOMXMRMXOMPMXPERUSERMXPROPMXQUEUEMXWOHIER

Business object order

The upgrade utility may alter the order of the objects that are in the integration object. When you complete the upgrade, check the appropriate object structure to determine whether the object order is altered. If the object order is altered, you must change the object order to meet your processing needs.

Inbound and outbound interfaces

In version 7, the term inbound interfaces is replaced by enterprise services. The integration framework provides object structure services and standard services to support external application access to application service methods.

Enterprise services can be invoked in an asynchronous model and messages process through the JMS queue. Enterprise services also can be invoked in a synchronous model. The service invoker receives a response when the service completes.

Enterprise services can support any of the operations that are supported by the object structure: Create, Update, Delete, Sync, and Query. Enterprise services can also be configured to reference an external schema. Version 6 query interface artifacts are converted to a single enterprise service component with a query operation.

In version 7, the term outbound interfaces is replaced by publish channels. In version 7, the integration framework provides an invocation channel that supports synchronous outbound message processing that can process a service response to Maximo.

Domains

In version 7, the integration framework does not add system domain values to inbound transactions. The integration framework provides the MXDOMAIN object structure to synchronize the domain values between the external application and Maximo.

Page 168: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Inbound and outbound interfaces

164 IBM Maximo: Upgrade Guide

Web services

In version 7, you can create and deploy Web services in the Web Services Library application. You can create and deploy three types of services: enterprise services, object structure services, and standard services. The Web Services Library application provides visibility to all Web services and it supports the generation of schema and Web Services Description Language (WSDL) files as part of the deployment process.

Message reprocessing

In version 7, you can manage and view publish channel and enterprise service messages that are flagged with an error in the Message Reprocessing application. You can view, correct, delete, and reprocess messages in error. You can view the error XML file without accessing the integration server error files.

Deleted interfaces

The upgrade utility deletes the version 6 interfaces that are listed in the following table. These Maximo Enterprise Adapter interfaces were used in the version 6 product installation procedures. In version 7, you can use the Object Structures and Migration Manager applications to configure the integration framework components.

Multiple integration points

The upgrade utility removes multiple integration points from an interface. The integration point with the highest processing sequence remains and is used as the primary object in the object structure.

Interface Description

MXACTIONInterface Action

MXCTEMPLATEInterface Communication template

MXMAXROLEInterface Role

MXWFInterface Workflow

MXINTTYPEInterface Interface type

MXINTERFACEInterface Interface

MXINTOBJECTInterface Integration object

MXENDPOINTInterface Endpoint

MXDOMAINInterface Domains

MXEXTSYSTEMInterface External system

MXMESSAGEInterface Messages

MXOBJECTCFGInterface Object and attribute configuration

Page 169: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Inbound and outbound interfaces

Maximo Enterprise Adapter updates 165

You can reconfigure the interfaces that use multiple integration points. You can reconfigure the interfaces in one of the following ways before you perform the upgrade:

Remove all but one of the multiple integration points from the interface.

Create multiple interface records and associate one integration point with each interface record.

Page 170: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

System properties

166 IBM Maximo: Upgrade Guide

System properties

The following table lists the properties that are migrated to version 7. You can update the property values in the System Properties application.

The upgrade program does not migrate the following properties, which are not used in version 7:

MAXINTWSPROPS.MXINTWSNAMEMAXINTWSPROPS.MXINTWSPASSWDMAXVARS.MXINTDOMAIN

URLs for inbound HTTP and HTTPS transactions

In version 6, a global URL was provided for each adapter to receive inbound transactions that use HTTP and HTTPS. Version 7 provides a URL for each combination of an external system and enterprise service to support the receipt of inbound transactions that use HTTP and HTTPS. You can continue to use a single URL when you upgrade from version 6 to 7.

XML transformation

After you upgrade to version 7, all transactions must comply with the version 7 XML format. The integration framework can transform version 6 XML transactions to version 7 XML formats. Additionally, adapters and some integration scenarios can either control or prevent the version 7 XML format transformations.

Version 6 file or table Version 6 property Version 7 property

MAXINTWSPROPS MXINTUDDIINQURL mxe.int.uddiinqurl

MXINTUDDINAME mxe.int.uddiname

MXINTIDDIPASSWD mxe.int.uddipassword

MXINTUDDIPUBURL mxe.int.uddipuburl

MXINTWSURL mxe.int.webappurl

MAXVARS MXINTDBUSER mxe.int.dfltuser

INTGLOBALDIR mxe.int.globaldir

INTEXPUPDSENDER mxe.int.expupdatesender

INTADMINTOEMAIL mxe.int.admintoemail

INTADMINFROMEMAIL mxe.int.fromadminemail

Page 171: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

XML transformation

Maximo Enterprise Adapter updates 167

Transformation enablements

The mxe.int.<adaptername>.convert6to7xml property indicates whether the integration framework transforms the transactions that are associated with an adapter.

The upgrade process sets the value of this property to 0 (false). If you change the property value to 1 (true) in the System Properties application, the integration framework converts the inbound transactions from a version 6 to a version 7 XML format. The format change occurs after the integration framework retrieves the transactions from the inbound queue. This transformation also occurs before any processing classes, inbound user exits, or inbound processing rules are applied.

If the value of the property equals 1, the integration framework transforms the outbound transactions from a version 7 to a version 6 XML format after it applies any outbound processing classes, user exits, and processing rules, and before the XML is written to the outbound queue.

Any custom outbound processing logic must conform to the version 7 XML schema.

Transformation limitations

The XML message structure (schema) is simplified in version 7. You can either migrate to the new XML format or continue using the version 6 XML format. The upgrade creates an mxe.int.<adaptername>.convert6to7xml system property for each adapter. The default value for this property is 0 (false).

If you want to continue to use a version 6 XML, you can set the mxe.int.<adaptername>.convert6to7xml property to 1 (true). When this property value equals 1, the integration framework converts the inbound XML messages from a version 6 format to a version 7 format when the message is retrieved from the queue.

For inbound interfaces, the version 6 XML format is based on the object structure that is associated with the enterprise service. The outbound messages are converted from a version 7 XML format to a version 6 XML format after the Java exits are applied and before the XSL is applied.

Support for this conversion continues until the next release. At that time you must migrate to the default XML format.

After you upgrade to version 7, you cannot generate version 6 XML schemas. The version 6 schema becomes an external schema definition.

Because the business object content of object structures is updated, the content of upgraded default interfaces might not comply with the version 6 schema of the interfaces.

Version 7 introduces a SELFREFERENCING attribute for object structures. The version 6 to 7 conversion does not support enterprise services or publish channels that use an object structure that has a SELFREFERENCING attribute value set to 1.

Page 172: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

XML transformation

168 IBM Maximo: Upgrade Guide

Transformation details

The following tables describe how the integration framework transforms the version 6 XML.

Page 173: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

XML transformation

Maximo Enterprise Adapter updates 169

Version 6 to 7 XML transformation considerations for nonquery and nonresponse interfaces

Version 6 element Inbound transformation to version 7 XML

Outbound transformation to version 6 XML

ROOT

Includes the name of the interface that is used to submit or receive the transaction.

Sets the version 7 root object structure element from the one that is registered to the enterprise service that is received in the version 6 transaction.

Does not map interface name information to the version 7 XML.

Sets the version 7 root operation element to Sync.

Sets the version 6 root element from the name of the publish channel from which the transaction was generated.

Sets the version 6 @lang attribute from the version 7 @ baseLanguage attribute.

HEADER

Includes a series of attributes and elements that specify the sender and recipient and uniquely identify the message.

Does not support the HEADER element in the version 7 XML.

Sets the version 7 attributes as follows:

Maps @baseLanguage from @language.

Maps @creationDatetime from /Header/CreationDateTime.

Maps @messageID from /Header/MessageID.

Maps @transLanguage from <topmbo><trans_langcode >.

Does not support the HEADER element in the version 7 XML.

Sets the version 6 elements as follows:

Maps /Header/CreationDateTime from /@creationDatetime.

Maps /Header/@event from /@event.

Maps /Header/MessageID from /@messageID.

Sets /Header/@operation to Notify.

Sets /Header/RecipientID to the name of the external system where the publish channel is registered.

Maps /Header/SenderID from the MXSYSID variable.

Page 174: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

XML transformation

170 IBM Maximo: Upgrade Guide

Version 6 to 7 XML transformation considerations for query and response interfaces

CONTENT

Includes one or more instances of the same integration object.

Does not support the CONTENT element in the version 7 XML.

Renames the Object Structure tag to <ObjectStructureSet>.

Assumes that integration object content and object structure content are the same.

Does not support the CONTENT element in the version 7 XML.

Renames the ObjectStructureSet tag to <ObjectStructure>.

Assumes that integration object content and object structure content are the same.

Adds a Content tag around the object structure data.

Version 6 element Inbound transformation to version 7 XML

Outbound transformation to version 6 XML

ROOT

Includes the name of the interface that is used to submit or receive the transaction.

Sets the version 7 root object structure element from the one registered to the enterprise service that is received in the version 6 transaction.

Does not map the interface name to the version 7 XML.

Sets the operation element to Query.

Sets the version 6 root element from the name of the publish channel from which the transaction was generated.

Sets the version 6 @lang attribute from the version 7 @ baseLanguage attribute.

Version 6 element Inbound transformation to version 7 XML

Outbound transformation to version 6 XML

Page 175: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

XML transformation

Maximo Enterprise Adapter updates 171

HEADER

Includes a series of attributes and elements that specify the sender and recipient and uniquely identify the message.

Does not support the HEADER element in the version 7 XML.

Sets the version 7 attributes as follows:

Maps /@maxItems from /Header/@maxItems.

Maps /@rsStart from /Header/@rsStart.

Maps /@uniqueResult from /Header/@uniqueResult.

Does not support the HEADER element in the version 7 XML.

Sets the version 6 header elements as follows:

Maps /Header/MessageID from /@messageID.

Maps /Header/@operation Response /Header/@rsStart from /@rsStart.

Sets /Header/RecipientID to the name of the external system where the publish channel is registered.

Maps /Header/@rsCount from /@rsCount.

Maps /Header/@rsTotal from/@rsTotal.

CONTENT

Includes one or more instances of the same integration object.

Does not support the CONTENT element in the version 7 XML.

Renames the Object Structure tag to <ObjectStructureSet>.

Assumes that the integration object content and object structure content are the same.

Does not support the CONTENT element in the version 7 XML.

Renames the ObjectStrucutreSet tag to <ObjectStructure>.

Assumes that the integration object content and object structure content are the same.

Adds a Content tag around the object structure data.

Version 6 element Inbound transformation to version 7 XML

Outbound transformation to version 6 XML

Page 176: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Deleted version 6 tables

172 IBM Maximo: Upgrade Guide

Deleted version 6 tables

The following table shows the version 6 tables that the upgrade utility deletes.

New version 7 tables

The following table shows the version 7 tables that the upgrade utility adds.

Table Change Description

MAXIFACE Function is merged with the MAXIFACEIN or MAXIFACEOUT tables, depending on the integration points that are supported by the migrated interfaces.

MAXIFACETYPE Data is implemented as a domain.

MAXINTMSGTYPE Function is moved to a domain.

MAXINTPOINT Function is merged with MAXINTOBJECT.

Table Change Description

MAXIFACEINCNTL Contains a record of the integration control and enterprise service associations.

MAXIFACEOUTCNTL Contains a record of the integration control and publish channel associations.

MAXIFACEINDETAIL Contains a record of the object structure and enterprise service associations.

Page 177: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

© Copyright IBM Corp. 2007, 2013 173

This appendix lists the error and warning messages, in numeric order, associated with the three upgrade utilities. The cause and an action to correct the problem are listed for each message.

Bracketed terms

Terms in <angle brackets> in the lists of error and warning messages indicate variables. The more frequently occurring variables are listed in the following table.

Checking the Support Web site

Be sure to check the Maximo Asset Management product page (www.ibm.com/software/sysmgmt/products/support/IBMMaximoAssetManagement.html) for the latest documentation updates and database issues.

Integrity checker error messages

Errors prevent the integrity checker utility from successfully passing. All errors must be corrected.

ERROR BMXAA0333E: Native index names longer than 18 characters exist. Before running ConfigDB, you must manually identify and rename these native indexes.

Cause: The Maximo database requires that index names have a maximum length of 18 characters. This restriction was bypassed through the database back end, and an index name was created containing more than 18 characters.

Troubleshooting the upgrade process B

<table> Table name, for example, WORKORDER.

<table.column> Table name and column name, for example, WORKORDER.WONUM.

<nnn> A numeric value, for example, 12.

<0>, <1> Variables whose values are explained in text that follows the error or warning message text.

Page 178: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integrity checker error messages

174 IBM Maximo Upgrade Guide

Action: Any index with a name longer than 18 characters must be dropped from the database back end. Use an SQL editor to drop the index. If the index is needed, you can use the Database Configuration application to re-create it. See the Technical Reference Guide for more details. If you need additional help, contact your Maximo database administrator or IBM Maximo Support.

ERROR BMXAA0451E: Tables exist that have not had their backup data restored. You must run RestoreFromBackup before you can run Upgrade.

Cause: When the database tables are configured using the Database Configuration application, Maximo makes backup copies of the tables, then applies your changes to the original tables. After this process is done, run the Database Configuration application again and restore the data from the backup tables. If this data restoration is not performed, the integrity checker stops the process with this error message because there might be serious implications to the overall upgrade of the Maximo database.

Action: To pass the integrity checker, you must run the Database Configuration application and select the option to restore from the backup tables. You are then given the choice of retaining the backup tables after restoration or dropping them. It is usually advisable to drop the backup tables because it saves disk space. Dropping the backup tables, however, is not mandatory. If you need additional help, contact IBM Maximo Support.

ERROR BMXAA04542E: These users should be removed from the security tables because they are not database users:

Cause: User groups are centrally stored in a Maximo database table called MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user entry is not present in these tables, it might cause problems while using Maximo. The database has been modified through the back end and data consistency between these tables and all other Maximo security tables has been compromised. The integrity checker finds this inconsistency and deletes the redundant entries.

Action: Run integrity checker in repair mode.

ERROR BMXAA0453E: The following groups should be removed from Maximo because they have no MAXIMO privileges:

Cause: User groups are centrally stored in a Maximo database table called MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user entry is not present in these tables, it might cause problems while using Maximo. The database has been modified through the back end and data consistency between these tables and all other Maximo security tables has been compromised.

Action: Run integrity checker in repair mode.

ERROR BMXAA0455E: The following users should be removed from Maximo because they have no MAXIMO privileges:

Cause: User groups are centrally stored in a Maximo database table called MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user entry is not present in these tables, it might cause problems while using Maximo. The database has been modified through the back end and data consistency between these tables and all other Maximo security tables has been compromised.

Action: Run integrity checker in repair mode.

Page 179: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integrity checker error messages

Troubleshooting the upgrade process 175

ERROR BMXAA0456E: The following users should be removed from the security tables: <table> because they are not Maximo users:

Cause: User groups are centrally stored in a Maximo database table called MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user entry is not present in these tables, it might cause problems while using Maximo. The database has been modified through the back end and data consistency between these tables and all other Maximo security tables has been compromised.

Action: Run integrity checker in repair mode.

ERROR BMXAA0457E: These users should be removed from the security tables because the user's group is not a database user:

Cause: User groups are centrally stored in a Maximo database table called MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user entry is not present in these tables, it might cause problems while using Maximo. The database has been modified through the back end and data consistency between these tables and all other Maximo security tables has been compromised.

Action: Run integrity checker in repair mode.

ERROR BMXAA0458E: The following Users Groups were not found in MAXGROUPS:

Cause: User groups are centrally stored in a Maximo database table called MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user entry is not present in these tables, it might cause problems while using Maximo. The database has been modified through the back end and data consistency between these tables and all other Maximo security tables has been compromised.

Action: Run integrity checker in repair mode.

ERROR BMXAA0459E: This group is defined as a user in the Maximo security tables: <table>

Cause: User groups are centrally stored in a Maximo database table called MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user entry is not present in these tables, it might cause problems while using Maximo. The database has been modified through the back end and data consistency between these tables and all other Maximo security tables has been compromised.

Action: Run integrity checker in repair mode.

ERROR BMXAA0462E: The database has a different UNIQUE property for the following original index definition(s):

Cause: Many indexes were originally defined in the Maximo database for better performance. The original indexes have been modified (probably through the back end).

Action: You can potentially improve Maximo performance by re-creating any unique indexes.

ERROR BMXAA0469E: No unique index found for primary key sequence on table(s): <table>

Cause: Every Maximo table must have a unique index that corresponds to the primary key sequence that is defined for that table. For these tables, that index is missing.

Page 180: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integrity checker error messages

176 IBM Maximo Upgrade Guide

Action: Create a unique index corresponding to the primary key sequence for the table. The primary key sequence for a table is defined by MAXATTRIBUTE.PrimaryKeyColSeq.

ERROR BMXAA0470E: Non-sequential primary key sequence on table(s): <table>

Cause: Every Maximo table must have a primary key sequence of columns, defined by MAXATTRIBUTE.PrimaryKeyColSeq. The values of PrimaryKeyColSeq must be consecutive and sequential. For these tables, the primary key sequence is not consecutive or not sequential.

Action: For the definitions of these tables, check and, if necessary, adjust the values of PrimaryKeyColSeq in MAXATTRIBUTE and MAXATTRIBUTECFG. The primary key sequence should have a corresponding unique index.

ERROR BMXAA0474E: These tables should be removed from Maximo because they do not exist in the database: <table>

Cause: One or more table names are defined as persistent tables in MAXTABLE but do not exist in the Maximo database. All Maximo database tables must be defined in the MAXTABLE table. They also might appear in other Maximo tables, including the following tables:

AUTOKEYMAXATTRIBUTEMAXATTRIBUTECFGMAXSYSINDEXES

Action: If you selected the report mode run-time option and you determine that the table is required, re-create the table. Use backup, if available, to restore the data in the table.

If the table is not required, remove the table name entry from all of the Maximo tables listed in the Cause section. For example, delete from MAXTABLE where tbname = ‘.....’.

In addition, if the table name is the main table in a custom application, remove any application entries from the following Maximo tables:

APPDOCTYPE APPFIELDDEFAULTSAPPLICATIONAUTHBOOKMARKDEFAULTQUERYEXCLUDEDACTIONS LOGINTRACKING MAXAPPS MAXLABELSMAXMENUMAXPRESENTATIONQUERYSIGOPTIONWFAPPTOOLBARWFASSIGNMENTWFTASKWORKVIEW

Page 181: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integrity checker error messages

Troubleshooting the upgrade process 177

For example, delete from MAXAPPS where app = ‘…..’. If necessary, contact IBM Maximo Support.

If you select the repair option, the table name entry and application entry (if the table name entry was for a custom application) are removed from the tables that are listed. In repair mode, you do not have an opportunity to maintain these relevant entries and restore the table from backup.

ERROR BMXAA0476E: The following tables own Maximo columns but are not defined as Maximo tables: <table>

Cause: A table name entry was found in MAXATTRIBUTE, but the table is not defined in MAXTABLE table. The names of all Maximo database tables must be entered in the MAXTABLE table. Each table name also appears in the MAXATTRIBUTE table, together with the names of all columns in that table. The table name might also be found in one or more of the following tables:

AUTOKEYMAXATTRIBUTECFGMAXSYSINDEXES

Action: If you selected the report mode option, and the table exists in the database, contact IBM Maximo Support.

If you selected the report mode option and the table does not exist in the database, remove the table name entries from all of the Maximo tables listed in the Cause section, including MAXATTRIBUTE. For example, delete * from MAXATTRIBUTE where tbname = ‘…..’.

In addition, if the table name is the main table in a custom application, remove any application entries from the following Maximo tables:

APPDOCTYPE APPFIELDDEFAULTSAPPLICATIONAUTHBOOKMARKDEFAULTQUERYEXCLUDEDACTIONS LOGINTRACKING MAXAPPS MAXLABELSMAXMENUMAXPRESENTATIONQUERYSIGOPTIONWFAPPTOOLBARWFASSIGNMENTWFTASKWORKVIEW

For example, delete from MAXAPPS where app = ‘…..’. If necessary, contact IBM Maximo Support.

If you selected the repair option and the table exists in the database, the problem cannot be repaired automatically. Contact IBM Maximo Support.

If you select the repair option and the table does not exist in the database, the table name entry is removed from all of the Maximo tables listed in the Cause

Page 182: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integrity checker error messages

178 IBM Maximo Upgrade Guide

section, including MAXATTRIBUTE. If the table name entry was for a custom application, any application entries are also removed from the following Maximo tables:

APPDOCTYPE APPFIELDDEFAULTSAPPLICATIONAUTHBOOKMARKDEFAULTQUERYEXCLUDEDACTIONS LOGINTRACKING MAXAPPS MAXLABELSMAXMENUMAXPRESENTATIONQUERYSIGOPTIONWFAPPTOOLBARWFASSIGNMENTWFTASKWORKVIEW

ERROR BMXAA0477E: The following are defined as Maximo tables but do not contain any Maximo columns: <table>

Cause: A table name is missing from MAXATTRIBUTE even though the name is present in the MAXTABLE table.

The names of all Maximo database tables must be entered in the MAXTABLE table. Each table name also appears in the MAXATTRIBUTE table, together with the names of all columns in that table. The table name might also be found in one or more of the following tables:

AUTOKEYMAXATTRIBUTECFGMAXSYSINDEXES

Action: If you selected the report mode option and the table exists in the database, contact IBM Maximo Support.

If you selected the report mode option and the table does not exist in the database, you must remove the table name from all of the Maximo tables listed in the Cause section, including the MAXTABLE table. For example: delete * from MAXTABLE where tbname = ‘…..’.

In addition, if the table name is the main table in a custom application, remove any application entries from the following Maximo tables:

APPDOCTYPE APPFIELDDEFAULTSAPPLICATIONAUTHBOOKMARKDEFAULTQUERYEXCLUDEDACTIONS LOGINTRACKING MAXAPPS MAXLABELSMAXMENU

Page 183: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integrity checker error messages

Troubleshooting the upgrade process 179

MAXPRESENTATIONQUERYSIGOPTIONWFAPPTOOLBARWFASSIGNMENTWFTASKWORKVIEW

For example, delete from MAXAPPS where app = ‘…..’. If necessary, contact IBM Maximo Support.

If you selected the repair option and the table exists in the database, the problem cannot be repaired automatically. Contact IBM Maximo Support.

If you select the repair option and the table does not exist in the database, the table name entry is removed from all of the Maximo tables listed in the Cause section, including MAXATTRIBUTE. If the table name entry was for a custom application, any application entries are also removed from the following Maximo tables:

APPDOCTYPE APPFIELDDEFAULTSAPPLICATIONAUTHBOOKMARKDEFAULTQUERYEXCLUDEDACTIONS LOGINTRACKING MAXAPPS MAXLABELSMAXMENUMAXPRESENTATIONQUERYSIGOPTIONWFAPPTOOLBARWFASSIGNMENTWFTASKWORKVIEW

ERROR BMXAA0478E: The ROWSTAMP trigger was not found for the following tables: <table>

Cause: The table is missing a rowstamp trigger. This might have been caused by installation of the integration gateway.

Action: Re-create the trigger, or run the integrity checker in repair mode to automatically provide the missing trigger.

ERROR BMXAA0479E: The ROWSTAMP trigger was found DISABLED on the following tables: <table>

Cause: The rowstamp trigger was inadvertently or intentionally disabled.

Action: You can enable the trigger manually, or run the integrity checker in repair mode to automatically enable the trigger.

ERROR BMXAA0480E: Null rowstamp(s) found in the following tables: <table>

Page 184: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integrity checker error messages

180 IBM Maximo Upgrade Guide

Cause: A rowstamp is a unique identifier for a row of data. It should never be null. The tables listed for this error contain null rowstamps. This might have been caused by a database being brought forward through multiple upgrades.

Action: Update any rowstamps that are null by assigning a unique rowstamp value.

ERROR BMXAA0490E: This column should be removed from Maximo because it does not exist in the database: <table.column>

Cause: An incompatibility exists between the column definition in the database system catalog and the Maximo catalog (the MAXATTRIBUTE table).

All Maximo columns must be defined as columns in the database’s system catalog. This column is not defined in the system catalog.

Action: If you selected the report mode option, you must either re-create the column in the system catalog, or delete all occurrences of the column in the MAXATTRIBUTE, and MAXATTRIBUTECFG tables. If necessary, contact IBM Maximo Support to correct this situation.

If you select the repair option, all entries for this column name are removed from the MAXATTRIBUTE and MAXATTRIBUTECFG tables. If the column is must-be, same-as (same as some root column), or root (other columns are the same as this column), this problem cannot be repaired automatically. Contact IBM Maximo Support.

ERROR BMXAA0493E: These Maximo-owned columns should be removed from the database because they do not exist in Maximo: <table.column>

Cause: A Maximo table column does not have a corresponding entry in MAXATTRIBUTE.

This message might indicate a database table problem that could not be fixed automatically. This error must be resolved before you can continue. Ignoring this error during an upgrade might result in a faulty upgrade, which might prevent the application from running smoothly.

Action: The listed table columns must be manually inserted or deleted from the MAXATTRIBUTE table. See the Technical Reference Guide and your SQL Language guide, or call IBM Maximo Support.

ERROR BMXAA0494E: The Maximo definition of this column does not match the actual column: <table.column>

Cause: An incompatibility exists between the column definition in the database system catalog and the Maximo catalog.

Action: Determine which column definition is correct, and redefine the incorrect column definition to match the correct one. If you are unsure which definition is correct, contact IBM Maximo Support. The integrity checker repair mode option modifies the Maximo column definition to match the database definition.

If the column is must-be, same-as (same as a root column), or root (other columns are the same as this column), the incompatibility is not repaired. In this case you must call IBM Maximo Support, or use the Database Configuration application to correct the incompatible column definitions.

ERROR BMXAA0495E: The Maximo ''nullable'' property of this column does not match the

Page 185: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integrity checker error messages

Troubleshooting the upgrade process 181

actual column definition: <table.column>Maximo definition is <required/nullable>Database column is <required/nullable>

Cause: The NULLS value of the Maximo column is different from the NULLS value of the system column.

It is permissible for some columns in a Maximo database to be null, meaning that the column contains no value at all. Whether a column can be null is defined by the NULLS value for that column.

Action: If you selected the report mode option, manually modify the NULLS value. If a null value is appropriate for this column, change NULLS to Y in the database and in MAXATTRIBUTE. If this column should never be null, change NULLS to N in the database and in MAXATTRIBUTE. You can make this change through the database back end. If you need additional help, contact IBM Maximo Support.

If you selected the repair option, the NULLS column in the Maximo table MAXATTRIBUTE is modified to match the NULLS column in the system table.

ERROR BMXAA0496E: This column is defined to be the “same as” a column that does not exist in Maximo: <table.column>

Cause: Certain columns in Maximo database tables must be the same as—be the same type and size—another column, called a root column, in the same or a different table. The root column and the same-as column are supposed to have the same data type, length, and scale. The indicated column is defined to be the same as a root column, but that root column does not exist.

Action: Redefine the same-as relationship so that it specifies a root column that exists in the Maximo database. The missing column might have to be added to the base Maximo database table. If necessary, contact IBM Maximo Support.

ERROR BMXAA0497E: The following columns are defined to be ''same-as'', but have different definitions: <table.column> <table.column>

Cause: Certain columns in Maximo database tables must be the same as—be the same type and size—another column, called a root column, in the same or a different table. The root column and the same-as column are supposed to have the same data type, length, and scale. This same-as relationship was broken by modifying the definition of one of the columns.

Action: If you selected the report mode option, contact IBM Maximo Support to repair the error.

If you selected repair mode and the data type does not match, repair mode changes the data type of the same-as column to match the data type of the root column. Run the Maximo Database Configuration application in order for changes to take effect. Then rerun the integrity checker utility. Note the following limitations:

If the same-as column is set up as must-be, it cannot be repaired by repair mode. Contact IBM Maximo Support.

If the same-as column has a value list associated with it, and the value list data type does not match the root column data type, and the value list type is 3 or 4 (Maximo defined value list), and the Maximo release version is 4.0 or above, this error cannot be repaired by repair mode. Contact IBM Maximo Support.

Page 186: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integrity checker error messages

182 IBM Maximo Upgrade Guide

If the listed conditions are all true, except that the value list type is 1 or 2 (a user-defined value list), the value list will be disassociated but repair by repair mode does take place.

If length does not match, repair mode compares all the columns that are the same as the root column. repair mode changes the column lengths to match that of the longest column. This result prevents user data loss and maintains the same-as relationship. Run the Maximo Database Configuration application for changes to take effect, then rerun the integrity checker.

ERROR BMXAA0499E: The Maximo definition of this column is invalid: <table.column>.

Cause: Maximo only recognizes certain data types. The data type of the reported column has been changed and Maximo no longer recognizes it.

Action: Use the Database Configuration application to change the data type of the column to the data type defined for this column. You might need to contact your Maximo database administrator or IBM Maximo Support to make this change.

ERROR BMXAA0502E: A column defined as YORN should not allow nulls: <table.column>

Cause: Some Maximo columns serve as switches. They can be true or false, on or off, yes or no. These columns are referred to as YORN columns (Yes or No). The specified column contains a NULL value.

Action: Update the errant rows to Yes or No.

ERROR BMXAA0513E: This column is both a root column and is same-as linked to another column: <table.column>

Cause: A column that is being referenced as a root column in a same-as relationship is itself referencing another column as the root column in a same-as relationship. There can only be one same-as reference between columns.

Action: Run the integrity checker in repair mode to resolve multiple same-as relationships between columns.

ERROR BMXAA0527E: The following groups have no privileges in the Maximo security tables. The group and its users should be removed from Maximo:

Cause: User groups are centrally stored in a Maximo database table called MAXGROUPS; users are stored in MAXUSERGROUPS. If a group or user entry is not present in these tables, it might cause problems while using Maximo. The database has been modified through the back end and data consistency between these tables and all other Maximo security tables has been compromised.

Action: Run integrity checker in repair mode.

ERROR BMXAA0528E: The following backup tables exist. If the data has been restored and the tables are not required, they should be deleted. <table>

Cause: Tables were restored from backup data using the Database Configuration application, but the backup tables were not dropped.

Action: Check that the tables have been restored, then use Database Configuration to drop the backup tables. Dropping the backup tables saves memory disk space. If you need additional help, contact IBM Maximo Support.

Page 187: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Integrity checker warning messages

Troubleshooting the upgrade process 183

ERROR BMXAA0529E: The following tables are mis-defined in MaxTable. A table alias (TBALIAS or CURTBALIAS) cannot be the same as the table name. <table>

Cause: A table alias is missing or is the same as the table name.

Action: Ensure that the aliases exist and are different from the table name. Running the integrity checker in repair mode corrects this problem.

Integrity checker warning messages

Warning messages do not prevent the integrity checker utility from successfully passing, but investigate and correct the causes of warning messages.

WARNING BMXAA0460E: Unimplemented database configuration changes found.

Cause: Changes were made to the database tables, possibly by the Database Configuration application or the integrity checker repair option, but the changes are still pending.

Action: Run the Database Configuration application. Either complete the changes and configure the database, or, if you do not want to make those changes, discard them. If you need additional help, contact IBM Maximo Support.

WARNING BMXAA0461E: The following original Maximo indexes are missing from Maximo:

Cause: Many indexes were originally defined in the Maximo database for better performance. The original indexes have been modified (probably through the back end).

Action: You can potentially improve Maximo performance by re-creating any missing indexes.

WARNING BMXAA0463E: The database has a different CLUSTERED property for the following original index definition(s):

Cause: Many indexes were originally defined in the Maximo database for better performance. The original indexes have been modified (probably through the back end).

Action: You can potentially improve Maximo performance by re-creating any clustered indexes.

WARNING BMXAA0475E: These Maximo-owned tables should be removed from the database because they do not exist in Maximo: <table>

Cause: Tables were found in the Maximo database that have no entry in the Maximo schema (MAXTABLE, MAXATTRIBUTE, and so on).

Action: Determine if the tables are necessary. Drop these tables from the database if they are no longer required. Dropping unneeded tables saves memory disk space. See your Maximo database administrator or call IBM Maximo Support if you need help removing the tables.

WARNING BMXAA0494E: The Maximo definition of this column does not match the actual column: <table.column>

Page 188: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade validation utility error messages

184 IBM Maximo Upgrade Guide

Cause: A column is defined one way in Maximo, and another way in the database.

Action: Determine which column definition is correct, and redefine the incorrect column definition to match the correct one. If you are unsure which definition is correct, contact IBM Maximo Support. The integrity checker repair mode option modifies the Maximo column definition to match the database definition.

WARNING BMXAA0526E: The following users do not have assigned labor codes. The database cannot be upgraded to a new version until all users have labor codes.

Cause: The users that are listed do not have assigned labor codes.

Action: No action is required unless you are upgrading the database to a newer version of Maximo. To upgrade, you must assign labor codes to all users.

WARNING BMXAA6244E: The following tables reference orphaned long descriptions; to remove them run Integrity Checker in repair mode. <table>

Cause: In the LONGDESCRIPTION table, rows exist that are “owned” by the specified tables, but the tables do not contain references to the long description. The long descriptions are “orphans” because they are disassociated from any table and are no longer accessible to Maximo. They continue to occupy space in the database, but serve no purpose.

Action: Remove the orphaned rows from the LONGDESCRIPTION table. Run integrity checker in repair mode to remove the orphans.

Upgrade validation utility error messages

Error messages prevent the validation utility from successfully running. Error messages must be corrected.

ERROR BMXAA0481E: Table cannot be added because it already exists in the database: <table>

Cause: A table that exists in the database has the same name as a table that is to be added by the database upgrade utility. The new Maximo table cannot be added to the database.

Action: Contact your database administrator to either rename the existing table or remove it from the database.

ERROR BMXAA0484E: Column cannot be added because it already exists in the database: <table.column>

Cause: A Maximo catalog record cannot be added to the listed tables because entries for the record already exist in those tables.

Action: The entries must be removed from the listed tables.

ERROR BMXAA0528E: The following backup tables exist. If the data has been restored and the tables are not required, they should be deleted.

Cause: Tables were restored from backup data using the Database Configuration application, but the backup tables were not dropped.

Page 189: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade validation utility error messages

Troubleshooting the upgrade process 185

Action: Check that the tables have been restored, then use Database Configuration to drop the backup tables. Dropping the backup tables saves memory disk space. If you need additional help, contact IBM Maximo Support.

ERROR BMXAA4169E: No record found in maxvars table for maxvar <adapter name>.

Cause: The MAXIFACETYPE database table shows that you have the IBM Maximo Enterprise <adapter name> installed, but the required varname and varvalue information does not exist in the MAXVARS table.

Action: If the Maximo Upgrade Resources page shows that the upgrade utilities support upgrading this product, ensure that you have installed the latest version 6 patch for the product. The latest patch inserts the necessary varname and varvalue information into the MAXVARS table.

ERROR BMXAA6244E: Orphan long descriptions exists against tables <table>. Run Repair mode to remove.

Cause: In the LONGDESCRIPTION table, rows exist that are “owned” by the specified tables, but the tables do not contain references to the long description. The long descriptions are “orphans” because they are disassociated from any table and are no longer accessible to Maximo. They continue to occupy space in the database, but serve no purpose.

Action: Remove the orphaned rows from the LONGDESCRIPTION table. Run integrity checker in repair mode to remove the orphans.

ERROR BMXAA6261E: Multiple alternate keys are not allowed for object:

Cause: In version 6, alternate keys are implemented and controlled through a MEA-specific table. In version 7, alternate keys are defined per Maximo business object. Each object supports only one alternate key.

Action: In the Integration Objects application, you must change the alternate key for each occurrence of any single Maximo business object. The Maximo business object must have the same alternate key across all integration objects.

ERROR BMXAA6262E: Multiple Interface Controls with the same name and different type or domain have been identified:

Cause: In version 6, the interface controls are registered at the adapter level. Duplicate names and different types or domain values are allowed as long as the name is unique within the adapter.

In version 7, controls are registered at the system level. When there are duplicate control names, the upgrade program upgrades one control and deletes the remaining duplicate controls.

Action: To resolve the interface control error:

1 Re-create the duplicate controls and assign different names to each control.

2 For processing rules and external systems that use any of the duplicate controls, replace the original control names with the new names.

ERROR BMXAA6264E: An end point based on XMLFILE handler does not exist. External System <0> upgrade cannot proceed.

Page 190: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade validation utility error messages

186 IBM Maximo Upgrade Guide

The actual error message substitutes <0> with the name of an external system.

Cause: The version 7 upgrade utility replaces any FLATFILE or IFACTABLE endpoint that is registered to an external system with an XMLFILE endpoint handler. An error condition occurs when no XMLFILE endpoint handler exists in the system.

Action: You must create and configure an endpoint that uses the XMLFILE handler.

ERROR BMXAA6265E: These interfaces do not include an inbound integration point that matches their corresponding interface integration object:

Cause The integration objects that are used by the interface integration points differ from the interface integration object. At least one integration point must implement an integration object that matches the interface integration object.

Action: Add an integration point that implements an integration object that matches the interface integration object.

ERROR BMXAA6267E: Interfaces with at least one inbound integration point associated with a merged integration object have been identified: IntPointName <0> IfaceName <1>

The actual error message substitutes <0> and <1> with the names of an integration point and interface, respectively.

Cause: The upgrade program has identified an inbound integration interface that maps to multiple integration points. At least one of the integration points corresponds to a merged integration object. Version 7 does not support merged integration objects.

Action: You must delete the integration points that implement a merged integration object on the interface. If those integration points are required for processing:

1 After completing the upgrade process, re-create the MERGED object by defining a nonpersistent Maximo business object in the Database Configuration application.

2 If the original integration object supports inbound integration points, you must create an enterprise service. If the original integration object supports outbound integration points, you must create a publish channel.

3 If any processing rules are based on the original integration object and integration points definition, re-create the rules in the new enterprise services or publish channels.

ERROR BMXAA6268E: Interface name must be unique. Name uniqueness conflict identified for <0> interface registered to <1> adapter

The actual error message substitutes <0> and <1> with the names of an interface and adapter, respectively.

Cause: In version 6, interfaces are registered at the adapter level. Duplicate names are allowed as long as the name is unique within the adapter.

In version 7, enterprise services and publish channels are registered at the system level. The interface name must be unique across adapters in order for the upgrade program to run successfully.

Page 191: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade validation utility error messages

Troubleshooting the upgrade process 187

Action: You must delete the duplicated interfaces and remove the association of the interface to all external systems. If these interfaces are required for integration processing:

1 Re-create the deleted interface with a new name.

2 Re-create any processing rules that apply to the deleted interface.

3 Add the new interface to the appropriate external systems.

ERROR BMXAA6269E: Multiple inbound integration points have been identified in <0> integration object.

The actual error message substitutes <0> with the name of an integration object.

Cause: Version 6 integration allows the definition of integration objects with multiple inbound integration points. In version 7, object structures do not support the concept of inbound integration points. An object structure supports one inbound integration point.

Action: You must delete the multiple inbound integration points from the integration object identified in the error message. You must remove the integration point from all interfaces that reference it. If those integration points are required for inbound integration processing:

1 Create an integration object for each integration point that you deleted.

2 Create an interface for each new integration object.

3 If any processing rules are based on the original integration object and integration points definition, re-create the rules to work with the new integration object definitions.

4 Add the new interfaces to the appropriate external systems.

ERROR BMXAA6270E: Multiple outbound integration points have been identified in <0> integration object.

The actual error message substitutes <0> with the name of an integration object.

Cause: Version 6 integration allows the definition of integration objects with multiple outbound integration points. In version 7, object structures do not support the concept of outbound integration points. An object structure supports one outbound integration point.

Action: You must delete the multiple outbound integration points from the integration object that is identified in the error message. You must remove the integration point from all interfaces that reference it. If those integration points are required for outbound integration processing:

1 Create an integration object for each integration point that you deleted.

2 Create an interface for each new integration object.

3 If any processing rules are based on the original integration object and integration points definition, re-create the rules in the new interfaces.

Page 192: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade validation utility error messages

188 IBM Maximo Upgrade Guide

4 Add the new interfaces to the appropriate external systems.

ERROR BMXAA6273E: All data must be removed from MXIN_INTER_TRANS table

Cause: The interface table inbound queue table (MXIN_INTER_TRANS) includes pending transactions.

Action: All pending interface table transactions must be processed by the interface table cron task, which includes any transactions in error. You can delete the rows in this table, which stops these rows from being processed.

ERROR BMXAA6275E: Interfaces with multiple outbound integration points have been identified:

Cause: Version 6 integration allows the definition of interfaces with multiple outbound integration points. In version 7, publish channels do not support the concept of outbound integration points. A publish channel supports one outbound integration point; a one-to-one relationship exists between object structures and publish channels.

Action: You must delete multiple outbound integration points from the interface definition. If those integration points are required for processing:

1 Create an integration object for each integration point that you deleted.

2 Create interfaces for the new integration objects.

3 If any processing rules are based on the original integration object and integration point definition, re-create the rules, in the new interfaces, to work with the new integration object definitions.

4 Add new interfaces to the appropriate external systems.

ERROR BMXAA6276E: Inbound setting restrictions should be same for this object (object: intobject1[ col1 col2 coln] intobject2[col1 col2 ])

Cause: In version 6, inbound setting restrictions are implemented and configured for an object attribute within an object structure. A single Maximo business object attribute can have a different setting restriction when a Maximo business object exists in multiple integration objects. In version 7, restrictions are defined per Maximo business object (MAXATTRIBUTE). A common set of restricted attributes, per Maximo business object, must exist in order for the upgrade to run successfully.

Action: In the Integration Objects application, you must set the inbound setting restriction for each occurrence of the Maximo business object. A Maximo business object attribute setting restriction must have the same value across all integration objects.

ERROR BMXAA6284E: Upgrade cannot add new apps because they already exist in MaxApps: <application>

Cause: You created a custom application or cloned an application and gave it a name that exists as an application name in version 7. Your version 6 application cannot be upgraded with its current name.

Page 193: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade validation utility error messages

Troubleshooting the upgrade process 189

Action: Rename the specified custom or cloned application that has the naming conflict with a version 7 application. If you rename the application, it will be upgraded and available in version 7 after you upgrade.

To rename a version 6 custom or cloned application, complete the following steps:

1 Log in to an SQL editor.

2 Enter the following commands in the database editor. Replace the value <OLD APPLICATION NAME> with the actual name of the application you want to rename. Replace <NEW APPLICATION NAME> with the new name for the application. Use all uppercase for the application names.

update maxapps set app='<NEW APPLICATION NAME>' where app = '<OLD APPLICATION NAME>';update maxpresentation set app='<NEW APPLICATION NAME>' where app = '<OLD APPLICATION NAME>';update sigoption set app='<NEW APPLICATION NAME>' where app = '<OLD APPLICATION NAME>';update applicationauth set app='<NEW APPLICATION NAME>' where app = '<OLD APPLICATION NAME>';update maxlabels set app='<NEW APPLICATION NAME>' where app = '<OLD APPLICATION NAME>';update maxmenu set moduleapp='<NEW APPLICATION NAME>' where moduleapp='<OLD APPLICATION NAME>' and menutype !='MODULE';update maxmenu set keyvalue='<NEW APPLICATION NAME>' where elementtype='APP' and keyvalue='<OLD APPLICATION NAME>';update appdoctype set app='<NEW APPLICATION NAME>' where app = '<OLD APPLICATION NAME>’;

Another option is to delete the custom or cloned application. Delete the application only if you do not need it in version 7.

To delete the custom or cloned application, complete the following steps:

1 Log in to an SQL editor.

2 Enter the following commands in the database editor. Replace APPLICATION NAME> with the name of the application you want to delete. Use all uppercase for the application name.

delete from maxapps where app='<APPLICATION NAME>';delete from maxpresentation where app='<APPLICATION NAME>';delete from sigoption where app='<APPLICATION NAME>';delete from applicationauth where app='<APPLICATION NAME>';delete from maxlabels where app='<APPLICATION NAME>';delete from maxmenu where moduleapp='<APPLICATION NAME>' and menutype !='MODULE';delete from maxmenu where elementtype='APP' and keyvalue='<APPLICATION NAME>';delete from appdoctype where app='<APPLICATION NAME>';

ERROR BMXAA6285E: The interface <0> uses an integration object <1> and is not using MX5X adapter. Either delete this interface or clone the integration object and update the interface to point to cloned integration object.

The actual error message substitutes <0> and <1> with the names of an interface and integration object, respectively.

Page 194: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade validation utility error messages

190 IBM Maximo Upgrade Guide

Cause: Version 7 integration does not support the MX5X adapter and its corresponding MX5X integration objects and interfaces. This message identifies an interface that is referencing an integration object that was delivered with the MX5X adapter. The integration object is deleted by the upgrade utility.

Action: You must delete the specified interface to remove the reference to the integration object. This requires removing the association to all external systems.

If the interface is required for integration processing, you must implement a new enterprise service, publish channel, or both, according to the version 7 integration framework architecture when you complete the upgrade process.

ERROR BMXAG1001E: DB cannot be upgraded because Maximo Oracle Adaptor patch minimum patch requirement is missing

Cause: The latest Oracle ERP adapter patch has not been applied.

Action: Apply the latest Oracle ERP 6.2 adapter patch.

ERROR BMXAG1002E: Column cannot be added because it already exists in the database

Cause: One or more column names of the Oracle ERP adapter cannot be added to the listed tables because of a name conflict.

Action: Rename or remove the following columns from the following tables:

ERROR BMXAG1003E: Enterprise Service cannot be added because it already exists in the database

Cause: One or more enterprise services of the Oracle ERP adapter cannot be added to the database because of a name conflict.

Action: Rename or remove the following enterprise services from the IFACENAME field of the MAXIFACEIN table:

MXCOA_FROA12MXCRAFT_FROA12MXGLCOMP_FROA12MXINVBAL_FROA12MXINVENTORY_FROA12MXINVISSUE_FROA12MXINVOICE_FROA12MXITEM_FROA12MXLABOR_FROA12MXPC_FROA12MXPO_FROA12MXPR_FROA12MXPROJ_FROA12MXRCVROTITM_FROA12

Table Columm name

COMPCONTACT OA_EXTERNALREFID

ITEM OA_ITM_LOT_NUMBER

ITEM OA_ITM_LOT_PREFIX

PURCHVIEW OA_LINESTATUSIFACE_FLG

Page 195: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade validation utility error messages

Troubleshooting the upgrade process 191

MXRECEIPT_FROA12MXVENDOR_FROA12

ERROR BMXAG1004E: Publish Channel cannot be added because it already exists in the database

Cause: One or more publish channels of the Oracle ERP adapter cannot be added to the database because of a name conflict.

Action: Rename or remove the following publish channels from the IFACENAME field of the MAXIFACEOUT table:

MXGLTXN_TOOA12MXINVENTORY_TOOA12MXINVOICE_TOOA12MXINVRES_TOOA12MXITEM_TOOA12MXPC_TOOA12MXPO_TOOA12MXPR_TOOA12MXPROJTXN_TOOA12MXRECEIPT_TOOA12

ERROR BMXAG1005E: Integration Control cannot be added because it already exists in the database

Cause: One or more integration controls of the Oracle ERP adapter cannot be added to the database because of a name conflict

Action: Rename or remove the following integration controls from the IFACECONTROL field of the MAXIFACECONTROL table:

ITMLOTPREFIXITMLOTSTARTNUMPCDEFORDERUNIT

ERROR BMXAG1006E: External System cannot be added because it already exists in the database

Cause: An Oracle ERP adapter external system cannot be added to the database because of a name conflict.

Action: Rename or remove the OA12 external system from the EXTSYSNAME field of the MAXEXTSYSTEM table.

ERROR BMXAH1001E: Ugrade cannot proceed. Must apply the latest Maximo 6.2 SAP Adapter patch

Cause: The SAP ERP adapter patch level is not on the latest level.

Action: Apply the latest SAP ERP 6.2 adapter patch.

ERROR BMXAH1002E: Object {0}** cannot be added because it already exists in the database

Cause: "SAP_ITEM_LDESC" object cannot be added because entries for the record already exist in the database.

Page 196: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade validation utility error messages

192 IBM Maximo Upgrade Guide

Action: The entries must be renamed or removed from the database.

ERROR BMXAH1003E: Relationship {0}** cannot be added because it already exists in the database

Cause: An SAP Adapter column name cannot be added to the listed tables because entries for the record already exist in those tables.

Action: The entries must be renamed or removed from the database.

ERROR BMXAH1004E: Column {0}** cannot be added into {0} because it already exists in the database.

Cause: A SAP Adapter column name cannot be added to the listed tables because entries for the record already exist in those tables.

Action: The entries must be renamed or removed from the tables.

ERROR BMXAH1005E: Column {0}** cannot be added into {0} because it already exists in the database.

Cause: A SAP Adapter End Point cannot be added to the database because entries for the record already exist in database

Action: The entries must be renamed or removed from the database.

ERROR BMXAH1006E: External System {0}** cannot be added because it already exists in the database.

Cause: A SAP Adapter External System cannot be added to the database because entries for the record already exist in database.

Action: The entries must be renamed or removed from the database.

ERROR BMXAH1007E: Enterprise Service {0}** cannot be added because it already exists in the database.

Cause: A SAP Adapter Enterprise Servicet cannot be added to the database because entries for the record already exist in database.

Action: The entries must be renamed or removed from the database.

Page 197: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade validation utility warning messages

Troubleshooting the upgrade process 193

ERROR BMXAH1008E: Publish Channel {0}** cannot be added because it already exists in the database.

Cause: A SAP Adapter Publish Channel cannot be added to the database because entries for the record already exist in database.

Action: The entries must be renamed or removed from the database.

** The actual error message substitutes {0} with the name of an Object, Relationship, Column, End Point, External System, Enterprise Service, or Publish Channel

Upgrade validation utility warning messages

Warning messages do not prevent the validation utility from successfully running. However, warning messages should be investigated and corrected.

WARNING BMXAA0460E: Unimplemented database configuration changes found.

Cause: Changes were made to the database tables, possibly by the Database Configuration application or integrity checker repair option, but the changes are still pending.

Action: Run the Database Configuration application. Either complete the changes and configure the database, or, if those changes are not wanted, discard them. If you need additional help, contact IBM Maximo Support.

WARNING BMXAA6263E: Multiple Interface Controls with the same name have been identified. Only one Interface control will be upgraded.

Cause: In version 6, interface controls are registered at the adapter level. Duplicate names are allowed as long as the name is unique within the adapter.

Version 7 integration controls are registered at the system level. Controls with duplicate names cannot be defined. The upgrade program upgrades only one control and deletes the remaining duplicate controls. For the controls that remain, preference is given to the control that is defined within the MAXIMO adapter.

Action: To maintain all of your 6.x interface controls before running the upgrade process:

1 Re-create the duplicate controls and assign different names to them.

2 In the processing rule and external system definitions, replace the original control names with the new names.

WARNING BMXAA6266E: No corresponding query type interface exists for response interface <0> with integration object <1>

The actual error message substitutes <0> and <1> with the names of an interface and integration object, respectively.

Cause: The upgrade program has identified an integration response interface without a corresponding query interface.

Page 198: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade validation utility warning messages

194 IBM Maximo Upgrade Guide

Action: None.

Response interfaces without a corresponding query interface cannot support any integration scenario. The upgrade process deletes them.

WARNING BMXAA6271E: MXINVBALQUERY and MXINVBALRESPONSE integration points will not be upgraded to 7.1. Only notify Integration Points (MXINVBALIN and MXINVBALOUT) will be used after upgrade for MXINVBAL

Cause: Version 6 integration allows multiple inbound integration points. Version 7 object structure does not support the concept of an inbound integration point. An object structure supports functionality equivalent to one inbound integration point.

The upgrade process migrates the MXINVBAL integration object that use integration points (inbound and outbound) with the NOTIFY operation. Version 7 does not use the MXINVBALQUERY and MXINVBALRESPONSE integration points during the upgrade process.

Action: None.

If you require an MXINVBAL query capability, you can use the version 7 enterprise service MXINVBALQUERYInterface. The object structure definition of this enterprise service is Inventory Balance (MXINVBAL).

WARNING BMXAA6272E: Rule <0> will be deleted from Interface <1>

The actual error message substitutes <0> and <1> with the names of a processing rule and interface, respectively.

Cause: In version 6, you can specify processing rules for any integration point that is registered to an interface. In version 7, you can specify rules only for the main object structure in an enterprise service. The upgrade program deletes any interface processing rules that are registered to additional integration objects.

Action: You must create a new interface for the object structure that is related to the integration point and apply the processing rules in a new interface.

WARNING BMXAA6274E: All merged integration objects and their related integration artifacts will not be upgraded to 7.1. Merged integration objects to be deleted are:

Cause: Version 7 integration does not support merged integration objects. Their capability is supported in nonpersistent Maximo business objects.

Action: After the upgrade, you must define a nonpersistent Maximo business object in the Database Configuration application, and use it to re-create the object structure.

WARNING BMXAA6282E: The end point <1> associated with the external system <0> implements a FLATFILE or an IFACETABLE handler. This end point will be replaced with one based on XMLFILE handler.

The actual error message substitutes <1> and <0> with the names of an endpoint and external system, respectively.

Cause: The Support Flat Structure flag for each version 7 integration object structure is disabled by default. You cannot use FLATFILE or IFACETABLE endpoints until that flag is enabled.

Page 199: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Upgrade utility error messages

Troubleshooting the upgrade process 195

Action: None.

If you require an external system to work with an endpoint that implements a FLATFILE or an IFACETABLE handler, you must first select the Support Flat Structure check box on object structures that are used by enterprise services or publish channels. You then must register the FLATFILE or IFACTABLE endpoint to that particular external system.

Upgrade utility error messages

Error messages prevent the upgrade utility from successfully running. Error messages must be corrected.

ERROR: Input file Maximo_root\tools\maximo\classes\psdi\upgrade\V600\EN\Metadoc_filename was not found.

Cause: You have the product referenced in Metadoc_filename installed in the database that is being upgraded. The upgrade utility does not support upgrading that product.

Action: Edit the Maximo_root\tools\maximo\classes\psdi\upgrade\V600\upgpoints.xml file and comment out the UPGPOINT tag for the referenced product. See Modifying the upgpoints.xml file (page 17) for more information about modifying the upgpoints.xml file.

(Oracle) ORA-01452: Cannot CREATE UNIQUE INDEX; duplicate keys found.

Cause: More than one record exists with the same unique key. The SQL statement immediately preceding this message is the statement that failed.

Action: Resolve the duplicate records and then create the missing index.

(SQL Server) QADB03: CREATE UNIQUE INDEX terminated because a duplicate key was found for index ID n.

Cause: More than one record exists with the same unique key. The SQL statement immediately preceding this message is the statement that failed.

Action: Resolve the duplicate records and then create the missing index.

Page 200: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Fixing and debugging SQL errors

196 IBM Maximo Upgrade Guide

Fixing and debugging SQL errors

The upgrade utilities for version 7 at times might encounter SQL errors while upgrading a database. The following information does not explain exactly what caused the SQL error, but it does help you repair the database so that the upgrade can continue.

1 Review the log file from the upgrade directory for the actual SQL error. The last entry in each file likely indicates the error that was detected.

2 Copy the SQL statement from the log. Paste and execute it within an SQL editor. The same error should be reported. The SQL statement can then be debugged and repaired for this error. It might be the result of many different problems.

Page 201: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

© Copyright IBM Corp. 2007, 2013 197

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 LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.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 LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any othercountry 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 websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.

Page 202: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

198 IBM Maximo: Upgrade Guide

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 Corporation2Z4A/10111400 Burnet RoadAustin, 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.

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.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs.

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.

Page 203: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

199

Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Microsoft, Windows, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Page 204: New 6 to 7 upgrade - IBM · 2020. 10. 19. · Starting the Maximo Upgrade Utilities program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

200 IBM Maximo: Upgrade Guide