Maximo

Maximo

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

 View Only
  • 1.  Object Structure - Why is "Support Flat Structure" read-only until save?

    Posted Sun December 19, 2021 06:03 PM
    MAM 7.6.1.2:

    When creating a new object structure, the "Support Flat Structure" field is read-only until the object structure is initially saved:



    So when writing instructions for creating object structures, I need to include the following steps:
    ...
    10. Save the object structure.
    11. Change "Support Flat Structure" to Yes  (since this field is read-only until save)
    12. Save the object structure again.

    Question:
    Why is the "Support Flat Structure" field read-only until the object structure is initially saved? Can that step be avoided?

    #AssetandFacilitiesManagement
    #Maximo


  • 2.  RE: Object Structure - Why is "Support Flat Structure" read-only until save?

    Posted Mon December 20, 2021 10:00 AM
    The reporting option supporting flat structure seems abnormal to me and I'm not sure it's intended, though all of the out of the box object structures seem to have it selected as well so I'm a bit confused. The intent for flat structure was for an import of a CSV file where you may have two identically named attributes on different objects that you needed Maximo to distinguish between. For example, you could have WONUM on WORKORDER (header) & WOACTIVITY (tasks) and those both can't be named WONUM in the CSV file. 

    I'm pretty confident the fact that you can set it after save is probably the bug here. If you're seeing a reason why it's needed let me know and I can try and track it down further.

    ------------------------------
    Steven Shull
    ------------------------------



  • 3.  RE: Object Structure - Why is "Support Flat Structure" read-only until save?

    Posted Mon December 20, 2021 12:33 PM
    Edited by System Admin Wed March 22, 2023 11:45 AM
    My thoughts were:

    In the future, I might want to use the ROS for Application Export too. Having a multi-purpose object structure like that (for reports and for exporting to Excel/CSV) would avoid the need for creating a duplicate object structure...just for the Application Export option.

    I wanted to enable the flat-file setting now, when creating the ROS, so that I can avoid modifying the ROS later. Otherwise, if I were to enable the flat-file option later, then that would mean I couldn't edit any ad hoc reports that are based on the ROS, since the ROS was modified after the a hoc report was created.
    So I was just trying to be proactive and not break my reports.

    But I haven't had a chance to test whether object structures can be multi-purpose like that.

    Related: Use ROS for flat file Application Export too?