Skip to main content

Changed package in Mosaic sent different purchasee order to Abacus

In this article, we look at how changing a package in Mosaic caused it to send a different Purchase Order number to Abacus.

Y
Written by Yusef Abulaynain
Updated over 4 months ago

Please check whether you made the changes for a different cost centre, a different supplier, or if someone from another purchasing team made them. Mosaic treats these kinds of changes as major, so itโ€™ll automatically generate a new Purchase Order number and send it to Abacus through the interface.
โ€‹

If your team reviews a service user's care package, make sure the same team that made the original purchase handles it. Mosaic assumes a change in purchasing team means a change in cost centre, which it sees as a major change, this triggers a new Purchase Order ID.


If none of the above applies, please raise a new case and include the following:

  • Person ID.

  • What the purchase order was and what itโ€™s changed to.

  • Whether the care package has changed, what those changes are, and when they happened.


โ€‹

Did this answer your question?