Dear Support,

We have a customer running Enterprise Version 6.3 12-03-13 with the Educational Halcust dated 12-08-15.

We have two queries regarding the budget warnings in the Purchase Orders Module:


1. We set the following settings – Module > Purchase Orders > Settings > Purchase Commitment Settings :

i. Account – blank
ii. Object – blank
iii. start date – blank
iv. end date – blank
v. Budget Warning threshold – 90%
vi. Budget checking for Purchase Orders – selected
vii. Check Object budget Against all Accounts – selected
viii. Allow going Over Budget – not selected
ix. Budget Period – Whole Year.

There is only one record in this setting as setup above.
We then do a run a timed back and re-import the same data. The settings i–ix above reset themselves to their default values as if they have never been setup. We have replicated this on two different sets of data on two different installations. But it doesn’t happen to every set of data we import. Another set of data imported in the same installation with the same Halcust files does not reset itself. Why does certain data re-set itself like this? And how can we stop it doing this?



2. We have the above settings selected.
We have an object of ART that has a budget £4,730 against one Nominal Account. They have spent £4,270 leaving £460 remaining. The same object has received income of £900 but against a different nominal account which according to the commitment Report means the ART Object now have £1,360 left to spend.
However, the budget warnings received when posting a purchase order only allow them to spend up to £460 and ignore the account with the income posted against it. This is giving an inaccurate picture of the budget remaining for that object.

I can replicate this on the schools data on my installation. A similar setup (2 layers of object posted for each transaction) on a different school’s data takes the income into account in the budget warnings and reports correctly.

I have checked all the obvious settings and have tried doing a timed backup and re-importing this only to get the same result. I have also tried exporting out all the Nominal Transactions and re-importing them so they overwrite the existing ones (on a backup copy of the data) but I still get the same result when posting a purchase order – only allows me to post a purchase order up to the value of £460 and not beyond. I can also replicate this with different objects within the same data.

If I create a brand new object, setup a budget of £4,730 for this object, post income of £900, I can then post a purchase order up to the value of £5,630 with the budget warnings working correctly.

How can I get the system to take the income into account and give the correct budget warnings on the existing objects?

I can send a copy of the data if required.

Thanks


Kind regards

Dave