MAM 7.6.1.2:

I noticed that there are some OOB report object structures that have 1:M relationships.

For example, the REP_WOPLANACT ROS has the MULTIASSETLOCCI and WOSTATUS tables as child objects. Those objects can have multiple records for a given WORKORDER record.

(Cardinality: MULTIPLE)


Question:

How does Maximo handle 1:M relationships when generating list reports? (not detail reports)
#AssetandFacilitiesManagement
#Maximo

It looks like Maximo generates a line in the list report for every row on the Many side of the relationship. This is similar to how a SQL query would behave with a LEFT JOIN  where there was a 1:M relationship.

For example, if a WO has multi-assets, the the list report would produce duplicated rows for each of the multi-assets.

I'm guessing that could turn out to be dangerous for report designers. It would be easy enough to accidently double count or triple count the cost of a WO, since the WO records would be duplicated or triplicated in the report.




I imagine the 1:M object in the object structure is meant for detail reports, not list reports. But it still might be something to keep in mind. It would be easy for a non-expert to make a mistake.
#Maximo
#AssetandFacilitiesManagement

It's potentially worth noting since ROS can be used in start center result sets that it will NOT show 1:M on result sets. By default you won't even see these objects but if you enable the system property webclient.allowMultipleCardinality (disabled by default) it will show only the first record from the set.

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