Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  Stop creating records into PERSONANCESTOR table

    Posted Tue June 10, 2025 02:23 AM

    Hi,

    Whenever a person record is created or its supervisor is updated, a record gets added into PERSONANCESTOR table. For some reason we want to stop injecting the records into this table. Is there any way (preferably configuration) to achieve this?



    ------------------------------
    Suhas Joshi
    ------------------------------


  • 2.  RE: Stop creating records into PERSONANCESTOR table

    Posted Wed June 11, 2025 02:35 AM

    I don't know legal way for this, there is no system attribute etc.

    If You really need this:

    1. Create some script, which cleans that after saving new person record
    2. Create DB trigger which cleans that table or rejects insert

    On that table is based some logic in Maximo, You can later run it to issues, that some functionality won't work, where that table is used.



    ------------------------------
    Juris Flugins
    Expert IT Consultant
    TROIA d.o.o
    Jurmala
    ------------------------------

    Original Message


  • 3.  RE: Stop creating records into PERSONANCESTOR table

    Posted Wed June 11, 2025 03:18 AM

    Hi Suhas

    Whilst you can use an automation script, the question is, why?  Although I have never encountered this table, it doesn't mean that it doesn't have an impact.

    The table holds the relationship between the supervisor and their subordinates, so this is something that may be used by Workflow and thus be rather important.

    If the ancestry has become out of sync, there are several articles on how to correct this.

    Just because we can, doesn't mean we should.



    ------------------------------
    Regards, Craig Kokay
    Princpal Consultant, COSOL
    https://cosol.global/

    Ph: +61-411-682-040
    email: craig.kokay@cosol.global
    #IBMChampion
    ------------------------------

    Original Message


  • 4.  RE: Stop creating records into PERSONANCESTOR table

    Posted Wed June 11, 2025 10:17 AM

    All the ANCESTOR tables are part of an Ancestor Pattern: Some table (e.g. WORKORDER, ASSET, PERSON, etc) is self-referencing to produce a hierarchy. While you could use a hierarchical or recursive query to go down from parent to child to child to child or up from child to parent to parent to parent, it is much easier to join in to the associated ANCESTOR table at one parent (e.g. `person.personid = personancestor.ancestor`) and join out at all of the children (e.g. `person.personid = personancestor.personid`). This way, you can instantly find all the way up or down the hierarchy. It's a super handy tool.

    So, I think you should avoid destroying a handy tool that will also reduce the supportability of your system. Instead, find another way to solve your problem.



    ------------------------------
    Blessings,
    Jason Uppenborn
    Sr. Technical Maximo Consultant
    Cohesive
    ------------------------------

    Original Message


  • 5.  RE: Stop creating records into PERSONANCESTOR table

    Posted Thu June 12, 2025 02:27 AM

    Adding a person creates a record automatically in PERSONANCESTOR table. This is core Maximo functionality and should not be disabled as it will impact other areas of Maximo. For example in View Requisition application, data is shown based on entries in the PERSONANCESTOR table.

    What is the actual business requirement in your case?

    ------------------------------
    Liliana Malaescu

    Senior Maximo Consultant
    ZNAPZ (part of Naviam)
    ------------------------------



    ------------------------------
    Liliana Malaescu
    ------------------------------

    Original Message


  • 6.  RE: Stop creating records into PERSONANCESTOR table

    Posted Thu June 12, 2025 08:53 AM

    As Liliana says this is core Maximo functionality.

    Deliberately deleting / preventing the record being written would have the effect of deliberately corrupting the database.

    Corrupting the database could put the system in a position where IBM Support would not investigate Person related problems because the system is not behaving as designed. 

    What are you actually trying to achieve?

    What is the underlying problem that has led to the conclusion that you need to disable this record creation?



    ------------------------------
    Mark Robbins
    Support Lead/Technical Design Authority / IBM Champion 2017 - 2023
    Cohesive (previously Vetasi Limited)
    https://www.linkedin.com/pulse/maximo-support-advice-from-non-ibm-engineer-article-mark-robbins/
    ------------------------------

    Original Message


Related Content