Maximo

Maximo

Come for answers, stay for best practices. All we're missing is you.

 View Only

  • 1.  Import WOs from Excel (application import/export; mandatory keys missing)

    Posted Fri June 25, 2021 11:47 AM
    MAM 7.6.1.2:

    I have an existing Object structure that has been used successfully for loading WOs via MxLoader.



    Now, in addition to using that object structure for MxLoader, I've set it up so that users can also import from Excel using application import/export.


    Test:

    I've exported a single WO to CSV from WOTRACK using application export.
    As a simple test, I want to import that WO back into Maximo using application import. I haven't made any changes to the CSV. I just want to see if the import will work.

    Unfortunately, the import has failed:

    BMXAA5804E - Import of data in file CGWORKORDER 3.csv was unsuccessful.
    BMXAA6534E - Processing for an inbound transaction failed. The processing exception is identified in line 2.
    BMXAA5861E - Mandatory keys are missing - unable to create xml from flat structure.


    Question:

    I don't understand how mandatory keys can be "missing", if the data came from the object structure in Maximo in the first place.
    Does anyone have any idea what I'm doing wrong? What fields are missing?

    Thanks!
    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: Import WOs from Excel (application import/export; mandatory keys missing)

    Posted Mon June 28, 2021 01:20 AM
    This is a tough one to answer without the spreadsheet.  Usually, though to import, it needs to fields that form the primary key in the spreadsheet, which in the case of a work order is usually the WONUM and SITEID, but it's possible to nominate other keys.  Have a look also at the Exclude/Include as a key field, may not be able to be exported as it's been excluded.

    BTW: The object structure I see in the screen shot is a custom one, so we don't know how its been set-up.

    ------------------------------
    ===============================
    Craig Kokay,
    Lead Senior Maximo/IoT Consultant
    ISW
    Sydney, NSW, Australia
    Ph: 0411-682-040
    =================================
    #IBMChampion2021
    ------------------------------

    Original Message


  • 3.  RE: Import WOs from Excel (application import/export; mandatory keys missing)

    Posted Mon August 02, 2021 01:04 PM
    Edited by System Admin Wed March 22, 2023 11:50 AM

    Like you mentioned, "the primary key in the spreadsheet" was the issue.

    Despite the fact that Maximo generates its own WONUM values, I still needed to provide fake WONUMS in the spreadsheet (for both the WO and Service Address) so that Maximo could link the SA to the WO.
    I just used dummy WONUMS like 1,2,3,4,5 -- since Maximo didn't actually use them to populate WONUM in the WORKORDER table.

    Note: The fake IDs are only necessary if some of the columns are for related records. If I were only importing data from columns for a single table, like WORKORDER, then I wouldn't need the fake IDs. 

    (Hopefully I'm remembering that correctly. It was a few weeks ago...)


    #AssetandFacilitiesManagement
    #Maximo


Related Content