Skip to main content

Error NullPointerException appears when a purchase order is being authorised

In this article, we explain why a NullPointerException may occur when authorising a PO due to missing role match logic.

Y
Written by Yusef Abulaynain

Error:
​‘Caused by: java.lang.NullPointerException
at uk.co.corelogic.framework.authorisations.logic.AuthorisationsManagerBO.workerRoleRuleRoleMatch(AuthorisationsManagerBO.java:746)’

The code indicates it can’t find a worker, who is assigned on the appropriate date, with a role to authorise the purchases, so you’ll likely need to check the Authorisation Rules and see which workers’ roles fall under those rules.
​
Could you please ask your team to think about these questions:

  • What’s their proposed purchase?

  • How have they set up the authorisation rules in the Admin Tool at the Budget level? Care Package level. Service level?

  • What’s the cost of their proposed purchase?

  • Do they have a worker with the right role who can make the purchase at that price, according to the rules for authorisation?

In a similar past situation, the worker who raised the case realised they should've sent the authorisation request to someone with a higher level of authority. So, they withdrew the authorisation request and re-sent it to a different worker with the right authority.

📌​Note: If Mosaic can’t find anyone when you click the authorisation button, it’ll just crash because it needs at least one person to bring up the screen.

📌Note: To access the link, you'll be redirected to the Access Portal,

You’ll find more details on Authorisations in Section 9 of the Finance configuration guide.

Did this answer your question?