Maximo Open Forum

I posted this on IBM site but thought I might catch some alternate eyes here that are not over there:

I am having a heck of a time trying to get a medium sized Failure Hierarchy to load into a MAS 9 environment using MxLoader.

I first hit the issue that the NextGen MxLoader does not support the MXL_FAILURELIST. So I move back to 6.2 and then find that I cannot connect to MAS in 6.2.

Once I finally got REST connections working (in 8.4) after looking on various threads and trying to do a custom OS with FAILURELIST and FAILURECODE I could not get it to work to save my life.

My biggest issue is that I cannot find a way to OVERRIDE the FAILURELIST value as it goes into MBO and as such it generates its own new sequence values when I load. I need the values to stay what I want to be able to load a hierarchy I have already created. Anybody have the solution to this issue? The override cannot be selected in the OS definition. I have the data in a 7.6.1.3 env to pull out and want to move it with the same values to the new environment.

So, what I have got somewhat working is to use single MBO OS's one for FAILURECODE (MXL_FAILURECODE). And then my own OS with just FAILURELIST to do the FAILURECLASS load and then I use the OOTB - MXAPIFAILURELIST to load the PROBLEM,CAUSE and REMEDY.  But the hassle is I must find the newly generated PARENT values for the PROBLEM, CAUSE and REMEDY and that is a MAJOR hassle since they are multiple levels deep and very complex to get the PARENT value on each of those codes going in.

I cannot believe there is not an easier way to load a full hierarchy. I see why Bruno stopped supporting it in the NextGen API as it looks really complicate to achieve.

Anybody have any advice to provide or how they were able to do it?

One note that I am dealing with a SaaS environment so I have not database access which is causing much of the problems here. Cannot even query the DB for id values.

Thanks,

I posted this on IBM site but thought I might catch some alternate eyes here that are not over there:

I am having a heck of a time trying to get a medium sized Failure Hierarchy to load into a MAS 9 environment using MxLoader.

I first hit the issue that the NextGen MxLoader does not support the MXL_FAILURELIST. So I move back to 6.2 and then find that I cannot connect to MAS in 6.2.

Once I finally got REST connections working (in 8.4) after looking on various threads and trying to do a custom OS with FAILURELIST and FAILURECODE I could not get it to work to save my life.

My biggest issue is that I cannot find a way to OVERRIDE the FAILURELIST value as it goes into MBO and as such it generates its own new sequence values when I load. I need the values to stay what I want to be able to load a hierarchy I have already created. Anybody have the solution to this issue? The override cannot be selected in the OS definition. I have the data in a 7.6.1.3 env to pull out and want to move it with the same values to the new environment.

So, what I have got somewhat working is to use single MBO OS's one for FAILURECODE (MXL_FAILURECODE). And then my own OS with just FAILURELIST to do the FAILURECLASS load and then I use the OOTB - MXAPIFAILURELIST to load the PROBLEM,CAUSE and REMEDY.  But the hassle is I must find the newly generated PARENT values for the PROBLEM, CAUSE and REMEDY and that is a MAJOR hassle since they are multiple levels deep and very complex to get the PARENT value on each of those codes going in.

I cannot believe there is not an easier way to load a full hierarchy. I see why Bruno stopped supporting it in the NextGen API as it looks really complicate to achieve.

Anybody have any advice to provide or how they were able to do it?

One note that I am dealing with a SaaS environment so I have not database access which is causing much of the problems here. Cannot even query the DB for id values.

Thanks,