IBM Support

IV33925: OPEN MAP FROM SERVICE ADDRESS FIELD OPENS THE MAP OF A DIFFERENTSERVICE ADDRESS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Steps to replicate the issue in Maximo 7.5.0.2 Spatial 7.5.0.0:
    
    - Go to Service Requests application
    
    - Bring up any Service Request record with Service Address
    
    - From Service Address field, click on Detail Menu and select
    Open Map
    
    The problem is: system opens the map of a different Service
    Address.
    

Local fix

  • No workaround has been found.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Maximo Spatial Asset Management 7.5.0, using Service     *
    * Address "Open Map" functionality.                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * In any Spatial enabled application with a Service Address    *
    * field, "Open  Map" functionality could bring a different     *
    * service address than the selected one.                       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please install the most recent interim fix.                  *
    ****************************************************************
    

Problem conclusion

  • For service addresses, the "Open Map" was incorrectly using the
    field longitude and latitude to load the service address record
    from database, and depending on their values, the SQL query
    did't returned any records, causing a NullPointerException
    error, noticeable in the server logs, and incorrectly bringing
    to the map the first service address in table. The query was
    changed to use just te organization, site and address code to
    load the records and problem was solved.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV33925

  • Reported component name

    MAXIMO SPATIAL

  • Reported component ID

    5724T3900

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2012-12-20

  • Closed date

    2013-01-19

  • Last modified date

    2013-01-19

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • MAXIMO
    

Fix information

  • Fixed component name

    MAXIMO SPATIAL

  • Fixed component ID

    5724T3900

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSG2D3","label":"Maximo Spatial Asset Management"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"750","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
19 January 2013