IBM Support

IJ45613: MISSING LOCANCESTOR RECORDS WHEN CHANGING PARENT (VIEW/MODIFY PARENTS)

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 DESCRIPTION : There is an issue when changing a location
    within the hierarchy to another ancestor above that is a
    Facility causes missing records in the LOCANCESTOR table.
    
    STEPS TO REPRODUCE:
    STEP 1:
    
    1.1 Go to Locations Create a new record Location - L1001:HL1 ->
    Type- OPERATING Go to More Actions tab -> Associate Systems with
    Locations Add new row -> System- Primary Hierarchy Add Parent-
    NEEDHAM Click OK Save Record
    
    1.2 Create a new record L1002:HL2 Go to More Actions tab ->
    Associate Systems with Locations Add new row -> System- Primary
    Hierarchy Add Parent- L1001 Click OK Save Record
    
    1.3 Create a new record L1003:HL3 Go to More Actions tab ->
    Associate Systems with Locations Add new row -> System- Primary
    Hierarchy Add Parent- L1002 Click OK Save Record
    
    1.4 Create a new record L1004:TEST STATION Go to More Actions
    tab -> Associate Systems with Locations Add new row -> System-
    Primary Hierarchy Add Parent- L1003 Click OK Save Record
    
    1.5 Create a new record L123413:AWS FACILITY Go to More Actions
    tab -> Associate Systems with Locations Add new row -> System-
    Primary Hierarchy Add Parent- L1004 Click OK Save Record
    
    1.6 Create a new record L123414:RA FACILITY Go to More Actions
    tab -> Associate Systems with Locations Add new row -> System-
    Primary Hierarchy Add Parent- L123413 Click OK Save Record
    
    1.7 Create a new record L123415:RG-INSTRUMENT Go to More
    Actions tab -> Associate Systems with Locations Add new row ->
    System- Primary Hierarchy Add Parent- L123414 Click OK Save
    Record
    
    1.8 Create a new record L123416:LPU-SYS Go to More Actions tab
    -> Associate Systems with Locations Add new row -> System-
    Primary Hierarchy Add Parent- L123413 Click OK Save Record
    
    1.9 Create a new record L123417:PROU-ASSET Go to More Actions
    tab -> Associate Systems with Locations Add new row -> System-
    Primary Hierarchy Add Parent- L123416 Click OK Save Record
    
    1.10 Create a new record L123418:CWAN-SYS Go to More Actions
    tab -> Associate Systems with Locations Add new row -> System-
    Primary Hierarchy Add Parent- L123414 Click OK Save Record
    
    1.11 Create a new record L123419:CWANC-SYS Go to More Actions
    tab -> Associate Systems with Locations Add new row -> System-
    Primary Hierarchy Add Parent- L123418 Click OK Save Record
    
    1.12 Create a new record L123420:ANTA-ASSET Go to More Actions
    tab -> Associate Systems with Locations Add new row -> System-
    Primary Hierarchy Add Parent- L123419 Click OK Save Record
    
    1.13 Create a new record L123421:ROUTER-MC ASSET Go to More
    Actions tab -> Associate Systems with Locations Add new row ->
    System- Primary Hierarchy Add Parent- L123419 Click OK Save
    Record
    
    1.14 Create a new record L123422:SIM-ASSET Go to More Actions
    tab -> Associate Systems with Locations Add new row -> System-
    Primary Hierarchy Add Parent- L123419 Click OK Save Record
    
    STEP 2: Check backend view for LOCATION = L123422 in the
    LOCANCESTOR table Got to Advance Search -> WHERE Clause ->Run
    below query (location in(select ancestor from locancestor where
    location ='L123422')) and type in('COURIER','HOLDING','LABOR','
    OPERATING','DISPOSE','REPAIR','MOTHBALL','SALVAGE','VENDOR')
    
    Result - 10 records
    
    STEP 3: Go to Location L123418 More Actions -> View/Modify
    Parents -> New Parent-L123413 Click OK
    STEP 4: Verify Move in Hierarchy STEP 5: Check backend view for
    LOCATION = L123422 in the LOCANCESTOR table Got to Advance
    Search -> WHERE Clause ->Run below query (location in(select
    ancestor from locancestor where location ='L123422')) and type
    in('COURIER','HOLDING','LABOR','OPERATING','DISPOSE','REPAIR','
    MOTHBALL','SALVAGE','VENDOR'))Result - 6 records (L1001,L1002,L1
    
    
    
    CURRENT RESULT: Facility that was assigned does not show
    either as ancestor. 3 Missing L1003(HL3), L1004(TEST STATION),
    L123413(AWS FACILITY) 6 records were returned + 3 missing gives
    9 Which would be correct.
    
    
    EXPECTED RESULT: L123422, L123419, L123418, L123413, L1004,
    L1003, L1002, L1001, NEEDHAM Moving up 1 parent gives 9 total,
    moving back to original parent should give 10 ancestors.
    
    REPORTED IN VERSION - TPAE 7.6.1.2-IFIX20220426
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * MAXIMO                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * MISSING LOCANCESTOR RECORDS WHEN CHANGING PARENT             *
    * (VIEW/MODIFY PARENTS)                                        *
    ****************************************************************
    

Problem conclusion

  • The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release 8.x Product
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ45613

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-02-27

  • Closed date

    2023-09-05

  • Last modified date

    2023-09-05

  • 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 ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
05 September 2023