- Import data with Maximo Integration Framework (MIF)
- Screencast: Import users and passwords with Maximo Integration Framework
- Screencast: Import data with XML flat files
- Import assets and asset specifications with MIF
- Export data to XML files with MIF
- How to import failure codes with the Maximo Integration Framework (MIF)
- Import locations with Maximo Integration Framework
- Create a Person Group object structure and web services with MIF
- Import PM’s and PM sequences with Maximo Integration Framework (MIF)
- Import asset classification hierarchies and classification attributes with MIF
- Exporting data to XML with MIF event listener for any changes on an object automatically
- Import Inventory Records using Maximo Integration Framework (MIF)
- Import users security groups with MIF
- Import labor codes with Maximo Integration Framework
- Import/Export data with MxLoader by Bruno Portaluri
In this tutorial, I will show you how to setup object structures and enterprise services to import PM’s that use PM sequencing. PM sequencing or job plan sequencing is when you want to use a different job plan on one PM when the it is generated into a workorder. The topic of job plan sequencing is complicated and won’t be covered in this post but you can view this YouTube video of an explanation of job plan sequencing.
So lets get started. This post also comes with a sample excel document to download.
So the first thing we want to do is to create a new object structure. There is no existing object structure for PM’s so we will create a new one. Click Go To -> Integration -> Object Structure. Create a new one called MXPM. Set the “Consumed By” to INTEGRATION and check the “Support Flat Structure?” option if you are going to use interface tables. In our case, we will use interface tables so go ahead and check it.
Next, click new row and add the PM object. This is the object that we will use to import just the PM data such as PMNUM, DESCRIPTION, ASSETNUM, etc. Click new row again and add the PMSEQUENCE object. This is the object we will use to import the job plan sequence numbers. Make sure you also set the relationship to PMSEQUENCE as well. Once you have these two objects, save the record. The “Alias Conflict?” check box should now be checked. This means that we have to change the alias names of some columns so, click Select Action -> Add/Modify Alias. Click on the PMSEQUENCE row and you should see 4 rows and 2 of them are duplicates. Change the JPNUM field alias to be “PMS_JPNUM” and the ORGID field alias to be “PMS_ORGID”. Click OK and save.
Next, we need to create a new Enterprise Service. Go To -> Integration -> Enterprise Services and create a new one and name it “MXPMInterface”. Set the operation to “Sync” and Object Structure to the one you created above, “MXPM”. Set the interface table field to “IFACEPM”. You can enable message tracking on this if you want as well.
Next, we have to add this to an external system. I have a system called EXTIMPORT so I just add the enterprise service to this and enabled it. Then you go to Select Action -> Create Interface Tables to create the IFACEPM table we set above.
Now that we have our setup complete, we need to have the data to import. There are two phases to this import. The first phase is to import data into the PM object only and then the second phase is to associate the job plan sequencing to the PM. We could probably do all this in one pass, but it gets more complicated than it needs to be and much easier to do it in phases. So to import PM data is pretty straight forward. All you need is to supply the necessary data for the PM. These are the columns I used to import data:
PMNUM, Description, Assetnum, ChangeBy, ChangeDate, DownTime, Frequency, FreqUnit, GLAccount, HasChildren, Interruptible, JPNUM, JPSEQINUSE, Location, ORGID, SITEID, Parent, PMCounter, Priority, Status, UseFrequency, UseTargetDate, WorkType, WOStatus, and of course the TRANSID and TRANSSEQ columns.
The most important field in this set is the JPSEQINUSE field. If your PM is gonna use the job plan sequencing, which we will import in the second phase, then you need to make sure this field is set to 1 in order for use to import the job plan sequences or else the import will fail.
Once you have your data in the interface table for the PM’s, you can go ahead and import them. If you don’t know how to import from interface tables, you can look at this post. Once you have completed the import for PM’s, you can now go into the second phase of the import process.
To import the job plan sequences, it’s also as simple as the PM’s, but these are the fields that you will need to populate in the interface table in order for the import to work.
PMNUM, ORGID, SITEID, Interval, PMS_JPNUM, PMS_ORGID, and TRANSID and TRANSEQ
These are the only fields you need to import the job plan sequences on the PM record. I have supplied an example excel document with two tabs, one for PM’s and one fore PM sequencing for the job plans.