Skip to main content

Purchase Orders and Elements

Troubleshooting purchasing steps, elements, and package setup.

Error [object Object] when saving a purchasing stepIn this article, we look at the "[object Object]" error that appears in Mosaic when saving a purchasing step even without making changes.
Error: 'ORA-00001: unique constraint (FW.IDXPK_ELEM_DETS_PO_REVS) violated'In this article, we explain the ORA-00001 error in framework logs caused by a unique constraint violation on purchase order revisions.
Pop Script Log has a warning for service users with services with end dates 01/01/2300In this article, we explain why the Pop Script Log contains a warning for service users whose services have end dates of 01/01/2300.
Error: 'Could not find element with the ID'In this article, we explain why you may see errors in Framework logs or Mosaic error screens (21.2+).
Unable to save care package using the green tickIn this article, we explain why the finance team may see 'kir-prod-app' errors when finalising workflow steps using the green tick.
Purchase step save error 'No budget element change found with the ID Description'In this article, we explain the 'UncheckedFrameworkException: No budget element change found with the ID' error when saving a purchase step.
Error NullPointerException appears when a purchase order is being authorisedIn this article, we explain why a NullPointerException may occur when authorising a PO due to missing role match logic.
Error: 'Element is a changed element that should have appeared on a purchase order in the past'In this article, we explain errors when finishing a purchase workstep due to missing PO data for changed elements.
Error screen or blank or white screen on a Purchase workstepIn this article, we explain why purchase worksteps may show blank screens, often triggered by actions on the Package tab.
Purchase order displays an incorrect amountIn this article, we explain why post-uplift purchase orders may not match care package screens.
Purchase Order not clickableIn this article, we explain why manual rate uplifts may not generate updated purchase orders.
Element type added to payment cycle by mistakeIn this article, we examine an issue where a no-cycle element was incorrectly assigned a payment cycle, affecting service user data.
Unable to start a purchase workstepIn this article, we explain an error when starting a purchase workstep: another worker has already begun altering the care package.