Maximo Open Forum

Hi Team, 

I am trying to load FAILURELIST data(PROBLEM/Cause/Remedy) data using MXLOADER but getting error.

Error:- 

Returning object ID [CLASS ID] is only supported for OS services

Did anyone faced this type issue and help me to fix this ?

Object:- FAILURELIST

OS :- MXL_FAILURELIST

Hello - I've seen a similar error in the past.  The issue was the object structure.  Are you using a custom object structure?  Verify that the object structure is correct and that all fields are set correctly.  If you want to share your MXLoader file with a few lines of data I will test it in a Out of the Box Maximo 7.6.1.3.

What could be miss on OBJECT STRUCUTUE related to this error ?

Make sure that you have the Object Structure and Object in the right columns (below) and make sure that your security settings for the object are correct, allowing write access.    

On the load sheet, did you include the LANGCODE and ORGID as columns.  I have seen that happen as well. 

Hi @JustIn goodLuck

in the Object structure we have to enable the Parent Code Attribute from Non -persistency tab and we need to pass like this.

while loading in the Problem:

FAILURECODE           FAILURELIST           ORGID           PARENTCODE        TYPE

FPROB1                                                        Org1               FCAUSE1                 PROBLEM                                       

While loading in the CAUSE

FAILURECODE           FAILURELIST           ORGID           PARENTCODE        TYPE

FCAUS1                                                        Org1               FPROB1                  CAUSE                                      

While loading in the REMEDY

FAILURECODE           FAILURELIST           ORGID           PARENTCODE        TYPE

FREMED1                                                      Org1              FCAUS1                  REMEDY                                      

Try to load like this. will be resolved your issue.

In my last role we had an object structure which better suited how a human might structure the data.  The problem is, I can't remember if it was an existing structure available to anyone, or something we built internally.  What I do remember is our structure allowed you to load data like this:

   FAILURECODE, PROBLEM, PROBLEM_DESCRIPTION, CAUSE, CAUSE_DESCRIPTION, REMEDY, REMEDY_DESCRIPTION

   FAIL_001,PR_001, Broken, CA_001, WearTear, RE_001, Replace

   FAIL_001,PR_001, Broken, CA_001, WearTear, RE_002, StickyTape

and the processing class would take each row and process the problem, cause and remedy in a sensible way, adding codes that didn't exist yet, and creating the hierarchy.

What I also remember is how painfully slow the existing structure was, so I built my own Object Structure and processing class to massively increase performance.  It involved building non-persistent objects for the intended data loading structure, and processing classes which cached data as it went in order to reduce reads from the database.

This might not be terribly helpful as I quit that company some time back, but it might be worth checking if any of those more clever data structures exist naturally, as performance might not be an issue at all for small datasets anyway. (we were often dealing with 10000s-100000s).

------------------------------
Levi Hinz
Levi Hinz Consulting
------------------------------