Release V4 | EAM Software

  • Home / EAM Tools / Data Management / Release V4

    New functions in EAM Data Manager V4

    The EAM Data Manager for IBM Maximo and IBM Control Desk is being steadily developed.
    The version 4 was released in January 2017. From now on it is availiable for all our customers.
    Below you find the explanation of the most important tool fuctions.

    • Delete records with the EAM Importer: Until now you could ealily import new data or modify existing data by uploading Excel files. New in version 4 is the possibility to delete records. See chapter Delete records with Excel Import files - $Delete on page 63 for more information on this feature.

    • End of support for Maximo 7.1, new Apache POI library: The EAM Datamanagement tools internally use the Apache POI library for reading and writing Excel Files ( Due to security reasons a very recent version of this library should be used. But there is a catch: Recent version require Java 1.6 or higher which is in turn not usable with Maximo 7.1. To resolve this issue we dropped support for Maximo 7.1 and now the EAM Datamanagement Tools use version 3.15 of the Apache POI library.

    • Support for virtual child objects in extended import (nonpersistent child objects): There are a few situations where the nonpersistent child objects are used. One example is the action menue entry “Change item number” in the asset application. Version 4 now calls the execute() method of these nonpersistent Mbo’s.

    • Status change in child objects during extended import: Up until version 4 a status change was possible only for main objects. Starting with version 4 status changes are possible for child objects during an extended import. This allows e.g. to change the status of LABORQUAL records if they are a child object of a Qualification import.

    • Update key values in the excel import file: Since the early versions of the EAM Importer Key attributes which use the Maximo AUTOKEY feature are written back in the excel file. New in version 4 is that all key attributes of an object are compared to the values from the excel import file and differences can be written back to the import file. This very useful if your Maximo Object uses some business logic (or some other external systems) to generate key values (the corresponding key value is not specified in the import file and the key attribute is not AUTOKEY). See chapter Handling of Key Valuesgenerated by Business Logic (not AUTOKEY) on page 38 for further information.

    • Cronjob for processing import files: Excel import files can be imported into the Maximo user interface (the usual method). Since version 3 you can also import files from the command line (see chapter Data import with the commandline on page 114). New in V4: you can create a Maximo cronjob and configure a contask instance. A crontask instance then looks for excel import files in a specific directory and processes them. See chapter Import Excel files with a Crontask on page 116.

    • Check if Admin Mode is active when importing objects with ancestor information: You can import Excel files whether Admin Mode in on or off. If Admin Mode is on certain Maximo services are disabled, internal events are not fired and listeners might not get notified. One negative implication is, that required changes in ancestor tables are not executed when admin mode is on. At least the following object habe ancestor tables: Asset, Person, PM and WO. To avoid inconsistent data in Maximo you can only import data in those Objects (and all Objects which extend ANCMbo) if the admin mode is off.
    Error message if admin mode is on during import of Asset, PM, WO or Person.

    Markdorf, January 2017
    Your EAM Team