How to import failure codes with the Maximo Integration Framework (MIF)

There is already a guide to import failure codes with Maximo 6 and MEA but it seems as though this guide isn’t really useful for Maximo 7 and the Integration Framework.  Initially, I thought it the guide provided by IBM for Maximo 6 would of been enough, but when I tried to create an import for Maximo 7, I realized that guide was all wrong.  I guess that was my mistake for not looking into the guide completely.  So here is my method of importing failure codes into Maximo 7

The first thing to do is to create a new Object Structure.  Let’s call it “MXFAILURELIST’ and set the ‘Consumed By’ to ‘INTEGRATION’.  We also want to check the ‘Support Flat Structure’ because I will be importing this through a CSV or DAT file.  Next we will want to add some objects to this structure.  Now this is where the IBM guide for Maximo 6 differs.  The first object we want to add is ‘FAILURELIST’.  The second object we will add is ‘FAILURECODE’.  Set the parent to ‘FAILURELIST’ and the relationship to ‘FAILURECODE’.  If you save, you will now notice that the ‘Alias Conflict’ is now checked.  So we have to fix that before we proceed.  Go to Select Action -> Add/Modify Alias.  You will see that the FAILURECODE for the FAILURELIST object is a duplicate, so let’s rename this alias name to ‘FL_FAILURECODE’.  We prefixed it with ‘FL’ to know that it belongs to the FAILURELIST object.  Click OK and save.

Next, we want to create a Publish Channel for this object.  Create a new one and call it ‘MXFAILURELISTInterface’.  Set the object structure to the one above and save.  This publish channel will be used to export data to a DAT file so we have a format to work with.  Now let’s create an Enterprise Service.  Create a new one and call it ‘MXFAILURELISTInterface’.  Set the object structure to the one above and save.  Now since this is the import interface, we want to turn on message tracking so go to Select Action -> Message Tracking and check the appropriate box.

Now, I will already assume that you have your external system setup and properly running so I won’t go into details on setting that up.  I do want to mention that you will have to setup your MIF global directory in order to export data.  You can look at this tutorial if you haven’t done that already.  So open your external system and click on the Publish Channel tab.  Add the ‘MXFAILURELISTInterface’ we created earlier and enable it.  Set the end point to ‘MXFLATFILE’.  Now click the export data button and go check your MIF global directory for the DAT file it created.

This file it created will be used as our template to import data.  So here you can add as many failure codes as needed.  Here is a sample of what my import file looks like with one record:

EXTIMPORT,MXFAILURELISTInterface,AddChange,EN
FL_FAILURECODE,FAILURELIST,ORGID,PARENT,TYPE,DESCRIPTION,FAILURECODE,FAILURECODEID
TESTCODE,,BEDFORD,,,DESCRIPTION OF CODE,TESTCODE,

One important thing to note here is that I added the ‘AddChange’ property to the first line.  Now go into your external system, and add the ‘MXFAILURELISTInterface’ and enable it.  Now click the data import and select the DAT file with all your failure codes.

Series Navigation< Export data to XML files with MIFImport locations with Maximo Integration Framework >

Did You Know...

As Maximo Experts, we have developed Maximo adds on products to make Maximo work assignment simple, reporting easy, and facilitating service requests seamless. Check out our additional products EZPlanner, EZInsight, and EZRequest.

Find Out More

7 thoughts on “How to import failure codes with the Maximo Integration Framework (MIF)

  1. What I should have said is it does not build the hierarchy for the problem, cause and remedy.

    What is happening is that the failurelist columnn values in the failurelist table are being overwriten by the sequence numbers that are in the load file.

    My sample file
    DATALOAD,MXFAILURELISTInterface,,EN
    FL_FAILURECODE,FAILURELIST,ORGID,PARENT,TYPE,DESCRIPTION,FAILURECODE,FAILURECODEID
    PUMPS,3334,EAGLENA,,,Pump Failures,PUMPS,
    LEAK,3336,EAGLENA,3334,PROBLEM,Leaking,LEAK,
    FITTING,3338,EAGLENA,3336,CAUSE,Fitting Leaking,FITTING,
    HOUSING,3340,EAGLENA,3336,CAUSE,Housing Leaking,HOUSING,
    REPLSHFT,3342,EAGLENA,3338,REMEDY,Replace Shaft,REPLSHFT,
    REPLGASK,3344,EAGLENA,3340,REMEDY,Replace Gasket,REPLGASK,

  2. When I attempt t generate the schema/view XML, I get the following message:
    BMXAA1266E – The XML instance cannot be generated from the schema.
    No Schemas to process.
    Nothing gets added to the globaldir that I set up. This does not occur when I attempt this on other object structures.
    Any ideas?

    Thanks,

    Derek

  3. Hello,

    I have followed these instructions however I get the error FAILURECODE is blank for some reason when the XML is generated from the CSV/DAT file it’s blanking out FAILURECODE

    There are no restrictions or anything on my Enterprise Service?

    PUMPS
    3334
    MTFM

    Pump Failures

Leave a Reply

Your email address will not be published. Required fields are marked *