Maximo Open Forum

 View Only

  • 1.  BMXAA4590E & BMXAA4129E

    Posted 02-01-2023 09:01
    Edited by Christopher Winston 02-01-2023 09:29
    This error shows status 'comp' in work order but shows 'closed' in work order history.  If you try to close it, you get the error messages.
    Help!!  ERROR: BMXAA4590E & BMXAA4129E
    #WorkManagement

    ------------------------------
    Duncan 
    City of Fortworth
    ------------------------------


  • 2.  RE: BMXAA4590E & BMXAA4129E

    Posted 02-02-2023 10:30
    So if I am understanding correctly, work order status is COMP but history has entry for COMP and after it for CLOSE correct?

    If this is the case you should look how that has happened and how has done change status transaction which has made CLOSE entry from work order history.

    To solve this you can do either #1 or #2 given below.

    1. Go to database and run this query to delete the CLOSE status-

    delete from wostatus where status='CLOSE' and wonum=<PUT UR WONUM Here>

    Now from Maximo change status of record to CLOSE.

    OR

    #2. Fire this query to update status of Work Order in WORKORDER table and you already have entry for CLOSE in WOSTATUS-

    update workorder set status='CLOSE' , HISTORY=1 where wonum=<PUT UR WONUM Here> and status='COMP'​​​

    ------------------------------
    Prashant Sharma
    Sedin Technologies
    Connect with me @ https://www.linkedin.com/in/psharmamaximo/

    #IBM Champion 2022
    #IBM Champion 2023
    ------------------------------

    Original Message


  • 3.  RE: BMXAA4590E & BMXAA4129E

    Posted 02-03-2023 09:42

    This is something I've seen but was never able to figure out how to replicate. When a WO goes to CLOSED you have ASSETHISTORY & ASSETHIERARCHY records get created. If for some reason the status change didn't get made to the WORKORDER and you try to change it again they try to get inserted again. That's why you're getting the BMXAA4129E error. 

    Your options are to either backend update the workorder to set the status, historyflag, etc. as Prashant mentioned or delete the ASSETHISTORY & ASSETHIERARCHY records and change it again from the front end. Either way you need to run database updates to get past it. 



    ------------------------------
    Steven Shull
    IBM
    ------------------------------

    Original Message


  • 4.  RE: BMXAA4590E & BMXAA4129E

    Posted 02-06-2023 09:23
    We ran into this issue when users closed work orders by accident and requested they be reopened through the back end. The errors occurred when someone reopened the work order without deleting the entries from the ASSETHISTORY & ASSETHIERARCHY tables. 
     

    ------------------------------
    Kevin Egolf
    TechOps
    ------------------------------

    Original Message


Related Content