@Mark Fresa's got it: LONGDESCRIPTION.LDKEY = PLUSCASSETSTATUS.PLUSASSETSTATUSID AND LONGDESCRIPTION.OWNERTABLE ='PLUSCASSETSTATUSID" AND LONGDESCRIPTION.LDOWNERKEY ='MEMO'
I believe the ldownertable should be PLUSCASSETSTATUS, not ASSET. Try that. Some organizations have not enabled status tracking on assets, so it depends on your installation.
Maximo Asset>change Status>Memo>Long description Looking for Long Description table Found the long description table but is only includes asset description the ldownertable = "Description" is the only thing that shows via sql server query ran - select * from longdescription where ldownertable = ...
Hi Alex, The gap in your screenshot appears to be due to a gap in the Language table. Can you confirm the mapping to the PMMETER.UNITSTOGO-related language equivalent attribute. Best,
Hi Axel We are missing a bit of information, but first, you are using a floating PM; that is, when you generate the PM, it will wait until the work order has been completed. Until that time, there are no Units To Go. When the work order is complete, the work order completion date is used as the...
Hi Axel, I saw your post regarding the meter-based PMs and have a few troubleshooting steps that might help resolve the behavior you are seeing: Check the PM Baseline: I recommend reviewing the PM's Frequency tab and comparing the "Next Due Meter Reading" against the asset's current meter...
Hi everyone, I'm having an issue with the meter-based PMs configuration. According to the documentation I've found on the internet, the units to go should be calculated even if only the options "Generate Work Order Based on Meter Readings (Do Not Estimate)?" and "Generate Work Order When Meter...
3815 Harrison AvenueCincinnati, OH 45211contact@moremaximo.com
Join CommunityInvite ColleaguesLearn MoreAbout UsTerms of Use