IBM Support

IV74054: BMXAA0073E - CANNOT CHANGE THE STATUS OF ASSET XX SINCE IT IS PART OF A HIERARCHY WITH THE ASSET'S PARENT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • STEPS TO REPRODUCE:
    1. Create a locations record.
    a. Type: OPERATING
    b. Status: OPERATING
    c. Nothing else is significant.
    2. Create 2 asset records
    a. Location: <use the location created in step 1>
    b. Status: OPERATING
    c. Nothing else is significant
    3. Set the parent of one if the asset records created to the
    other asset record created.
    4. Set them both to DECOMMISSIONED status.
    5. Create an action.
    a. Action: DECOMLOC
    b. Object: LOCATIONS
    c. Type: Change Status
    d. Value: DECOMMISSIONED
    e. Accesible From: ALL
    6. Create an escalation.
    a. Escalation: <anything>
    b. Applies to: LOCATIONS
    c. Condition: location = '<use the location created in step 1>'
    d. Schedule: 1m,*,*,*,*,*,*,*,*,*
    e. Escalation Point 1
    i. Escalation Point Condition: 1=1
    ii. Repeat: checked
    f. Add DECOMLOC as an action .
    7. Activate the escalation:
    8. Wait until the escalation runs.
    9. Check the location created in step 1, it will NOT be
    decommissioned.
    10. Check the application logs, the error below will be found:
    
    [6/1/15 12:43:06:648 EDT] 000000a4 SystemOut     O 01 Jun 2015
    12:43:06:
    648 [ERROR] [MXServer] [CID-CRON-62916] Failed to execute
    action  on
    escalation:  XX reference point: {106}  for object {LOCATIONS}
    with id {461}
    psdi.util.MXApplicationException: BMXAA0073E - Cannot change
    the status
    of asset  XX since it is part of a hierarchy with the asset's
    parent XX in DECOMMISSIONED status.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of assets and location apps                            *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Maximo does not allow decommissioning a location that is in  *
    * a hierarchy of assets that are already in DECOMMISSIONED     *
    * status when trying to change status using an Escalation.     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * None                                                         *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package:
    	  Release 7.5.0.9 of Base Services
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV74054

  • Reported component name

    ASSETS

  • Reported component ID

    5724R46AS

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-06-09

  • Closed date

    2015-07-02

  • Last modified date

    2015-07-02

  • 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

    ASSETS

  • Fixed component ID

    5724R46AS

Applicable component levels

  • R750 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo 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:
09 April 2023