I have an Object Structure that has LOCATION as its main object and SERVICEADDRESS as its child, when i try to send a message, the location and service address is saved but the service address is not populated to the location, upon checking it looks like it has something to do with SERVICEADDRESS.OBJECTNAME although im not sure if that is really the reason, is there a better way to do this without using script? I don't want to save a record using script because it will have problems with validation. 

I have an Object Structure that has LOCATION as its main object and SERVICEADDRESS as its child, when i try to send a message, the location and service address is saved but the service address is not populated to the location, upon checking it looks like it has something to do with SERVICEADDRESS.OBJECTNAME although im not sure if that is really the reason, is there a better way to do this without using script? I don't want to save a record using script because it will have problems with validation. 

Gaby,

Understanding object precedence is a study unto itself.  Since the dawn of Maximo it has been a non-normalized database with ALL referential integrity begin governed by Maximo Business Objects.  This goes all the way back to original code in Maximo 1.x in the 1980s since PSDI supported MANY databases.  Cannot code foreign keys in many languages without managing many code sets.  So.. by abstracting the business logic to the MBOs, Voila! a miracle occurred.

So now how to load data with this understanding?  MBO precedence.  As Juris said you need to ensure you have populated the LOCATIONS.SADDRESSCODE AFTER you have inserted valid SERVICEADDRESS objects into the DB. Your object structure then really should be two passes, and not a single one. 

While there is no one single load order (unless you decide to load EVERY object in the DB, which most folks do not!) there is a precedence. Generally system level objects need to be there before Sets, and Sets level objects before Orgs, and Org level objects before Sites, etc.

Example: Job Plans.  Since you may have Job plans with Org or Site you "should" load Job Plans after sites.  If your Job plan references a classification, then you must have classifications loaded prior to loading Job Plans.  So precedence... does your object reference any other object?  If so, then load that one first, and work your way backwards. 

Pro Tip:  Look at Migration Manger OOTB packages.  There are lots of clues as to precedence there.

------------------------------
Bradley K. Downing , MBA
Senior Solution Architect
IBM
Bakersfield
------------------------------

Original Message:
Sent: Fri January 17, 2025 02:18 AM
From: Gaby D
Subject: Creating LOCATIONS and SERVICEADDRESS at the same time using MIF Integration

I have an Object Structure that has LOCATION as its main object and SERVICEADDRESS as its child, when i try to send a message, the location and service address is saved but the service address is not populated to the location, upon checking it looks like it has something to do with SERVICEADDRESS.OBJECTNAME although im not sure if that is really the reason, is there a better way to do this without using script? I don't want to save a record using script because it will have problems with validation. 

------------------------------
Gaby D
------------------------------

Gaby,

Understanding object precedence is a study unto itself.  Since the dawn of Maximo it has been a non-normalized database with ALL referential integrity begin governed by Maximo Business Objects.  This goes all the way back to original code in Maximo 1.x in the 1980s since PSDI supported MANY databases.  Cannot code foreign keys in many languages without managing many code sets.  So.. by abstracting the business logic to the MBOs, Voila! a miracle occurred.

So now how to load data with this understanding?  MBO precedence.  As Juris said you need to ensure you have populated the LOCATIONS.SADDRESSCODE AFTER you have inserted valid SERVICEADDRESS objects into the DB. Your object structure then really should be two passes, and not a single one. 

While there is no one single load order (unless you decide to load EVERY object in the DB, which most folks do not!) there is a precedence. Generally system level objects need to be there before Sets, and Sets level objects before Orgs, and Org level objects before Sites, etc.

Example: Job Plans.  Since you may have Job plans with Org or Site you "should" load Job Plans after sites.  If your Job plan references a classification, then you must have classifications loaded prior to loading Job Plans.  So precedence... does your object reference any other object?  If so, then load that one first, and work your way backwards. 

Pro Tip:  Look at Migration Manger OOTB packages.  There are lots of clues as to precedence there.

I have an Object Structure that has LOCATION as its main object and SERVICEADDRESS as its child, when i try to send a message, the location and service address is saved but the service address is not populated to the location, upon checking it looks like it has something to do with SERVICEADDRESS.OBJECTNAME although im not sure if that is really the reason, is there a better way to do this without using script? I don't want to save a record using script because it will have problems with validation. 

Hi Everyone,

Thanks for the reply, in the end we created 2 OS one for SA and one for Location, I just thought there was a way to do it because LOCATION/LOCATIONSPEC works (if you use the MXOPERLOC setup of course) where you send them at the same time and LOCATIONSPEC was not having the "record not found" issue. 

Thanks again!

Gaby,

Understanding object precedence is a study unto itself.  Since the dawn of Maximo it has been a non-normalized database with ALL referential integrity begin governed by Maximo Business Objects.  This goes all the way back to original code in Maximo 1.x in the 1980s since PSDI supported MANY databases.  Cannot code foreign keys in many languages without managing many code sets.  So.. by abstracting the business logic to the MBOs, Voila! a miracle occurred.

So now how to load data with this understanding?  MBO precedence.  As Juris said you need to ensure you have populated the LOCATIONS.SADDRESSCODE AFTER you have inserted valid SERVICEADDRESS objects into the DB. Your object structure then really should be two passes, and not a single one. 

While there is no one single load order (unless you decide to load EVERY object in the DB, which most folks do not!) there is a precedence. Generally system level objects need to be there before Sets, and Sets level objects before Orgs, and Org level objects before Sites, etc.

Example: Job Plans.  Since you may have Job plans with Org or Site you "should" load Job Plans after sites.  If your Job plan references a classification, then you must have classifications loaded prior to loading Job Plans.  So precedence... does your object reference any other object?  If so, then load that one first, and work your way backwards. 

Pro Tip:  Look at Migration Manger OOTB packages.  There are lots of clues as to precedence there.

I have an Object Structure that has LOCATION as its main object and SERVICEADDRESS as its child, when i try to send a message, the location and service address is saved but the service address is not populated to the location, upon checking it looks like it has something to do with SERVICEADDRESS.OBJECTNAME although im not sure if that is really the reason, is there a better way to do this without using script? I don't want to save a record using script because it will have problems with validation. 

Hi Everyone,

Thanks for the reply, in the end we created 2 OS one for SA and one for Location, I just thought there was a way to do it because LOCATION/LOCATIONSPEC works (if you use the MXOPERLOC setup of course) where you send them at the same time and LOCATIONSPEC was not having the "record not found" issue. 

Thanks again!

Gaby,

Understanding object precedence is a study unto itself.  Since the dawn of Maximo it has been a non-normalized database with ALL referential integrity begin governed by Maximo Business Objects.  This goes all the way back to original code in Maximo 1.x in the 1980s since PSDI supported MANY databases.  Cannot code foreign keys in many languages without managing many code sets.  So.. by abstracting the business logic to the MBOs, Voila! a miracle occurred.

So now how to load data with this understanding?  MBO precedence.  As Juris said you need to ensure you have populated the LOCATIONS.SADDRESSCODE AFTER you have inserted valid SERVICEADDRESS objects into the DB. Your object structure then really should be two passes, and not a single one. 

While there is no one single load order (unless you decide to load EVERY object in the DB, which most folks do not!) there is a precedence. Generally system level objects need to be there before Sets, and Sets level objects before Orgs, and Org level objects before Sites, etc.

Example: Job Plans.  Since you may have Job plans with Org or Site you "should" load Job Plans after sites.  If your Job plan references a classification, then you must have classifications loaded prior to loading Job Plans.  So precedence... does your object reference any other object?  If so, then load that one first, and work your way backwards. 

Pro Tip:  Look at Migration Manger OOTB packages.  There are lots of clues as to precedence there.

I have an Object Structure that has LOCATION as its main object and SERVICEADDRESS as its child, when i try to send a message, the location and service address is saved but the service address is not populated to the location, upon checking it looks like it has something to do with SERVICEADDRESS.OBJECTNAME although im not sure if that is really the reason, is there a better way to do this without using script? I don't want to save a record using script because it will have problems with validation.