IBM Support

IJ05222: LOCATIONS TO WORKORDER RELATIONSHIP SHOULD STILL BE EDITABLE VIA DATABASE CONFIGURATION

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Prior to version 7.507, the LOCATIONS to WORKORDER relationship
    for checking if a
    location can be DECOMMISSIONED was in the MAXRELATIONSHIP table
    and
    could be changed by the client in the Database Configuration
    application. The SQL for this check was moved into the code
    starting
    with 7507. This SQL should still be editable via Database
    Configuration
    as some clients may choose to modify this relationship.
    
    Current erroneous result:
    Client is not able to modify relationship via Database
    Configuration.
    
    Expected result:
    Client should be able to modify relastionship via Database
    Configuration.
    
    Environment:
    App Server IBM WebSphere Application Server 7.0.0.15
    
    Version IBM Maximo Asset Management 7.5.0.11 Build 201610201952
    DB
    Build V75011-00
    Tivoli's process automation engine 7.5.0.11 Build 20161020-1751
    DB
    Build V75011-17
    IBM Maximo Enterprise Adapter for SAP Applications 7.5.0.1 Build
    201203011027 DB Build V7500-06
    IBM TPAE Integration Framework 7.5.1.6 Build 20161012-1035 DB
    Build
    V7516-03
    
    Server OS Linux 2.6.32-696.6.3.el6.x86_64
    
    Server DB Oracle 11.2 (Oracle Database 11g Enterprise Edition
    Release
    11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data
    Mining
    and Real Application Testing options)
    

Local fix

  • na
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO users                                                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Relationship that checks if location can be decommissioned   *
    * moved to class file.                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Prior to version 7.507, the LOCATIONS to WORKORDER relationship
    OPENWOFORLOC, used to check if a location can be DECOMMISSIONED,
    was in the MAXRELATIONSHIP table and could be changed by the
    client in the Database Configuration application. The SQL for
    this check was moved into the code starting with 7507 making it
    impossible to customize. This was not necessary. The SQL,
    modified to address a prior APAR, is not built conditionally or
    dynamically and should have remained in the MAXRELATIONSHIP
    table where it can be modified via Database Configuration.
    
    Current erroneous result:
    Inability to customize relationship via Database Configuration.
    
    Expected result:
    Ability to modify relastionship via Database Configuration.
    

Problem conclusion

  • The relationship OPNWRKFORLOC (from the LOCATIONS object to the
    MULTIASSETLOCCI object) replaces the relationship OPENWOFORLOC
    (from the LOCATIONS object to the WORKORDER object) that existed
    prior to Maximo 7.5.0.7. OPENWOFORLOC still exists in the
    MAXRELATIONSHIP table but is not used when trying to
    decommission a location. If prior to 7.5.0.7 you had modified
    OPENWOFORLOC to customize behavior for decommissioning a
    location, you will need to incorporate these changes into
    OPNWRKFORLOC if you want this customization in Maximo 7.6.1.0 or
    later.
    
    The fix for this APAR is contained in the following maintenance
    package:
    	| release\fix pack\interim fix for Release 7.6.1.0
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ05222

  • Reported component name

    SYSTEM CONFIG

  • Reported component ID

    5724R46S1

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-03-26

  • Closed date

    2018-05-16

  • Last modified date

    2018-05-16

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

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

Fix information

  • Fixed component name

    SYSTEM CONFIG

  • Fixed component ID

    5724R46S1

Applicable component levels

  • R760 PSY

       UP



Document information

More support for: Maximo Asset Management

Software version: 750

Reference #: IJ05222

Modified date: 16 May 2018