IBM Support

IV99219: WHEN CHANGING ACTIVITY STATUS IN PLUSCA APPLICATION, THE STATUS ON OTHER ACTIVITY RECORD WILL BE CHANGED

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

  • PROBLEM: When changing ACTIVITY status on "Condition
    Report(Nuc)" application, the status on other
    ACTIVITY record will be changed.
    
    PERFORMANCE ISSUE: N
    
    STEPS TO REPRODUCE:
    - Multiple users operate.
    
    "#1" >>> A user
    "#2" >>> B user
    
    1. #1 Open condition report(Nuc).
    2. #1 Create a new CR, and created 2 ACTs.
    >>> At this time, the both status of ACK are "WAPPR (Waiting on
    Approval)".
    3. #2 Open condition report(Nuc).
    4. #2 Open the Screening tab CR, which was created step2
    5. #1 Change the both ACT status from "WAPPR (Waiting on
    Approval)" to
       "In Progress".
    6. #2 Change one of the ACT status from "WAPPR (Waiting on
    Approval)" to
       "APPR (Approved)".
    7. #2 An error is displayed. (There is no status change)
    8. #2 Change another ACT status to "COMP (Completed)".
    
    >>>> Then, both status will be "COMP (Completed)".
    
    CURRENT ERRONEOUS RESULT:  status for both activities changed
    to "COMP" (Completed) status
    
    EXPECTED RESULT: status for one activity should be changed to
    "COMP" (Completed) status
    
    ADDITIONAL INFO: The fix for APAR IV94523 did not address this
    issue in the "Condition Report(Nuc)" application
    replicated with TPAE 7.6.0.8-IFIX20170710-0952 Build
    20170512-0100 DB Build V7608-63 HFDB Build HF7608-01
    
    
    ENVIRONMENT (SYSTEM INFO):
    Tivoli's process automation engine 7.6.0.2-IFIX20170110-1411
    Build
    20150903-2113 DB Build V7602-31 HFDB Build HF7602-10
    IBM Maximo for Nuclear Power 7.5.1.0-20150904-1742 Build
    20121004-0300
    DB Build V7510-17 HFDB Build HF7510-48
    IBM TPAE Integration Framework 7.6.0.2 Build 20150901-2100 DB
    Build
    V7602-05
    IBM Maximo Calibration 7.6.0.0 Build 20150611-1558 DB Build
    V7600-01
    IBM Maximo Asset Management 7.6.0.2 Build 20150903-2113 DB
    Build V7601-
    01
    OS Linux 2.6.32-358.el6.x86_64
    DB Oracle 11.2 (Oracle Database 11g Enterprise Edition
    Release 11.2.0.3.0 - 64bit Production With the Partitioning,
    OLAP, Data
    Mining and Real Application Testing options)
    
    LOCAL FIX: N/A
    
    SECURITY IMPACT (Y/N): N
    

Local fix

  • change application xml for condition report:
    Export the application xml, search for dialog
    "activitychangestatus" and change the beanclass to
    "psdi.webclient.beans.workorder.WOChildChangeStatusBean"
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users that use Maximo for Nuclear Power.                 *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * WHEN CHANGING ACTIVITY STATUS IN PLUSCA APPLICATION, THE     *
    * STATUSON OTHER ACTIVITY RECORD WILL BE CHANGED               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • UI changed to solve the problem.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV99219

  • Reported component name

    MAXIMO FOR NUCL

  • Reported component ID

    5724R5300

  • Reported release

    751

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-08-22

  • Closed date

    2017-09-12

  • Last modified date

    2017-09-12

  • 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

    MAXIMO FOR NUCL

  • Fixed component ID

    5724R5300

Applicable component levels

  • R760 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCHPRP","label":"Nuclear Power"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"751","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
12 September 2017