Maximo Open Forum

 View Only

Obsolescence of unnecessary nomenclature.

  • 1.  Obsolescence of unnecessary nomenclature.

    Posted an hour ago

    Dear experts, good afternoon!
    I'm asking for advice. I've been researching a seemingly simple issue for several days now: aging items that are no longer needed.
    However, the contractor who implemented Maximo for us used some strange solutions. It seemed like, "What's so special about aging items?" He selected the "Pending Obsolescence" status (by the way, is this status just an interim status or is it really needed for something?). Then he selected the "Obsolete" status, and that's it.

    The system is throwing us several conditions.
    1) The balance for this item must be 0, which is clear.
    2) This item must not be in open Work Orders, which is also clear.
    3) This item must not be in open Purchase Orders.
    4) This item must not be in open Purchase Orders, and the Java class checks for this.
    It seems like there's nothing complicated about the standard version out of the box.
    The order checks that all its lines are copied to the supplier's order, and then it can be transferred to the APPR status and then to the CAN status, and historyflag =1 can be set, and the record will be archived.
    But our procurement process is very poorly organized, apparently due to our mentality.
    Our Purchase Order is generated in Maximo and, after approval by the initiator, is sent to the accounting system. There, the purchasing department generates a Purchase Order for the supplier, which is then sent to Maximo. However, it may arrive with a different set of lines and different product range than the order, for various reasons. Therefore, there's no verification that the order lines have been copied to the order. Approvals occur in the financial system, and the purchasing department processes the orders.
    When the purchase is completed, the financial system returns the status "COMPLETED," but for some reason, the contractor set this status to WAPPR instead of APPR, and the system doesn't allow it to be converted to CAN status, among other conditions.
    That's why ALL my orders in the system have a COMPLETED status. Incidentally, the same applies to supplier orders. They have an APPROVED status.
    Because of this, I can't age the items.
    That's why I have a question.
    Of course, I could rewrite the standard Java class, but for now I'm hoping to get by with the least amount of effort.
    How can I change the purchasing orders from COMPLETED to CLOSE? I'd like to point out in advance that I've tried an automation script, but it doesn't work. I've also tried escalation, but it doesn't work either. Well, with escalation, it's clear the system won't let me execute the changestatus. I went to the PRSTATUS domain, deleted the WAPPR COMPLETED status from there, and changed it to APPR COMPLETED. Unfortunately, it doesn't help, and the system won't let me change it to the final CLOSE status. Is there a way to do this automatically? Of course, there's always the option to UPDATE directly in the database, but I try to avoid that. Thank you to everyone who participates in my threads, your answers are very valuable and helpful!


    #Customizations
    #EverythingMaximo
    #Inventory

    ------------------------------
    Sergey Melnikov
    RusNet
    ------------------------------