Maximo Open Forum

 View Only

 Problem Loading Location Hierarchy with Application Import

  • Assets
Tori Foley's profile image
Tori Foley posted 04-18-2025 12:22

I'm attempting to use application import to load a location hierarchy, trying a single record right now. Object Structure includes locations, locancestor, lochierarchy, and locoper tables. I'm receiving the error listed below with nothing in the logs. The location already exists with no parent and is in the same system as the new parent.

BMXAA5598E - Processing of an inbound transaction failed. The processing exception is identified in document 1 which starts at line 2 and ends at line 2.
    locations#addlocation

Steven Shull's profile image
Steven Shull

Which object structure are you using? You should be using something like MXOPERLOC. That error at a glance is thrown when the LOCOPER record is being added and the owner MBO is not LOCATIONS. I'm not sure how that would happen because you normally wouldn't interact with this object directly. 

Just a heads up, due to how application import works with a single commit, loading hierarchies would be complicated. You'd need to load the top level, then second level, then third level, etc. That's not the cause of your issue but it would probably be worth doing this as an Enterprise service import on the External System after you get past the issue. 

Tori Foley's profile image
Tori Foley

I'm using a custom OS based on MXOPERLOC. The locations I was trying to set up a hierarchy for were previously loaded so I need to remove them and re-add with the hierarchy. 

Danny King's profile image
Danny King

I am not sure how you are formatting the data to send to Maximo. Just be sure to set lochierarchy.newparent with the parent location to update the location hierarchy for the record.