Could it be that the MAXTYPE for the Maximo attribute ISTASK for Maximo View Object wotaskrollup_vw is YORN and default value is 0? You could change MAXTYPE to UPPER length 1 and apply decode to pass Y, N or NULL.
------------------------------
Nivin Jacob George Senior Consultant
Senior Consultant
Praxis Solutions
Kuwait
------------------------------
Original Message:
Sent: Tue November 02, 2021 09:48 AM
From: User1971
Subject: Ad-hoc report filling in gaps on right side of join incorrectly
MAM 7.6.1.2:
I have a view object in Maximo that only selects WOs, not tasks (ISTASK=0).
I effectively have a left join from the WORKORDER table to the view.
If I were to mock up what Maximo does, but in an SQL client, it would look like this:
select wo.wonum as wo_wonum, wo.istask as wo_istask, vw.istask as vw_istaskfrom maximo.workorder woleft join maximo.wotaskrollup_vw vw on wo.wonum = vw.wonum

The view doesn't have any matching tasks, so the tasks rows have nulls in the view columns, as expected.
However, if I do the same sort of thing in an ad-hoc report, the task rows have "N" values in the VW.ISTASK column, which is incorrect/unexpected.
For the task rows, the VW.ISTASK values should be null, just like other columns from the view (such as VW.ACTTOTALCOST_TASKS_INCL).
(Screenshot of the relationship: https://i.stack.imgur.com/DL77v.png)

Question:
Why is the ad-hoc report filling in gaps on right side of the join incorrectly? (for the VW.ISTASK column)
The highlighted values should be null, not "N".
Thanks.
#Maximo
#AssetandFacilitiesManagement