Maximo Open Forum

 View Only

 IBM Maximo Budget Monitoring

  • Maximo Application Suite
Axel Alamilla's profile image
Axel Alamilla posted 02-16-2026 14:03

Hi everyone,

I have a question about how the Budget Monitoring application calculates the Estimated Total.

Case:

  • A budget line has an Estimated Total of 0.
  • A user creates a Work Order linked to that budget line.
  • Then they create a PR for 500.00 and a PO for 500.00.
  • The user cancels the PO first, and then cancels the PR.
  • After both cancellations, the budget line’s Estimated Total ends up at -500.00.

From what I can see, when the PO is cancelled, the system does not add the PR amount back into the Estimated Total, even though the BUDMON100 rule indicates it should.

linetype IN (SELECT value FROM synonymdomain WHERE domainid = 'LINETYPE' AND maxvalue IN ('SERVICE','STDSERVICE')) AND exists (select * from po where ponum = prline.ponum AND status IN(select value FROM synonymdomain WHERE domainid = 'POSTATUS' and maxvalue = 'CAN'))

According to this rule, the PONUM should remain on the PRLINE after the PO is cancelled, but Maximo doesn’t behave that way.

I verified whether Maximo 7.5 might be clearing it by mistake, but the same behavior occurs in a MAS 8 environment.

Has anyone encountered this before, or is this the expected behavior?

Steven Shull's profile image
Steven Shull

I would open a support ticket with IBM because that sounds like a bug. Budget Monitoring is a relatively new feature for Maximo that isn't as heavily utilized as some of the other features, so we've found a few issues with calculations from time to time. While budget monitoring is simple in concept, it is complicated to handle all the scenarios that can occur in Maximo because you're constantly adding/subtracting as records progress.

And as you've identified here, when a PO is cancelled it is removed from the PRLINE so that it can be copied to a new PO. That causes the increase to get missed and needs to be handled a different way. 

Bruno Portaluri's profile image
Bruno Portaluri

We tried hard to implement the OOTB Budget Monitoring feature but we found out that it is very buggy and capable of handling all the possible scenarios.

To solve the problem, we basically developed our own calculation engine that can work on top of the standard Budget application.

Feel free to get in touch with me on LinkedIn if you need additional details.