Confirm

We have had an issue on a job where a payment request was created with the "Job Complete" flag ticked, which in turn ticked the "Complete" flag of the individual SoR's. Then, the user unticked the "job Complete" flag and clicked no on the pop up, effectively leaving the SoR's still ticked as "Complete".
In the mean time, another user created a variation on these SoR's to increase the quantities, and the variation was committed before the batch routine was run and committed.

So now, we have a job that has a total value of £7,566.91 and Paid at £4,998.42: the remainder cannot be requested as we can't add archived SoR's to a new request; and we can't reverse the variation as you can't vary Archived SoR's.

We tried allowing duplicate SoR's to be added to a request (something we definitely do not want as a regular occurrence due to rounding issues in the past) and ticking the "job Complete" flag Confirm automatically varies items to the requested amounts.... instead, it varied with the new items but left the old the same, so in DEV the job is now worth £10,135.40 instead of the £7.5k it should be.

Anyone have any ideas if this can be fixed?

Thank you in advance.

------------------------------
Ana Resende
Gloucestershire County Council
GLOUCESTER
------------------------------

Hi Ana,

I may have missed something but the Payment Commit should have varied the Items back down to the Requested amounts.  Has this not happened?

It would probably be best to raise a Support Call for this.

Regards
Liz

------------------------------
Elizabeth McKenzie
Pitney Bowes
Principal Software Engineer
------------------------------

Original Message:
Sent: 09-21-2020 07:52
From: Ana Resende
Subject: Archived SoR's with outstanding quantities

We have had an issue on a job where a payment request was created with the "Job Complete" flag ticked, which in turn ticked the "Complete" flag of the individual SoR's. Then, the user unticked the "job Complete" flag and clicked no on the pop up, effectively leaving the SoR's still ticked as "Complete".
In the mean time, another user created a variation on these SoR's to increase the quantities, and the variation was committed before the batch routine was run and committed.

So now, we have a job that has a total value of £7,566.91 and Paid at £4,998.42: the remainder cannot be requested as we can't add archived SoR's to a new request; and we can't reverse the variation as you can't vary Archived SoR's.

We tried allowing duplicate SoR's to be added to a request (something we definitely do not want as a regular occurrence due to rounding issues in the past) and ticking the "job Complete" flag Confirm automatically varies items to the requested amounts.... instead, it varied with the new items but left the old the same, so in DEV the job is now worth £10,135.40 instead of the £7.5k it should be.

Anyone have any ideas if this can be fixed?

Thank you in advance.

------------------------------
Ana Resende
Gloucestershire County Council
GLOUCESTER
------------------------------

Hi Liz,

That's right. I think the issue might be that the request was created before the variation, but the variation was committed before the batch, thereby causing a difference on the ordered field between a new request and an existing request? I shall raise a ticket with Support.

Kind Regards,

Ana​

------------------------------
Ana Resende
Gloucestershire County Council
GLOUCESTER
------------------------------

Original Message:
Sent: 09-22-2020 08:48
From: Elizabeth McKenzie
Subject: Archived SoR's with outstanding quantities

Hi Ana,

I may have missed something but the Payment Commit should have varied the Items back down to the Requested amounts.  Has this not happened?

It would probably be best to raise a Support Call for this.

Regards
Liz

------------------------------
Elizabeth McKenzie
Pitney Bowes
Principal Software Engineer

Original Message:
Sent: 09-21-2020 07:52
From: Ana Resende
Subject: Archived SoR's with outstanding quantities

We have had an issue on a job where a payment request was created with the "Job Complete" flag ticked, which in turn ticked the "Complete" flag of the individual SoR's. Then, the user unticked the "job Complete" flag and clicked no on the pop up, effectively leaving the SoR's still ticked as "Complete".
In the mean time, another user created a variation on these SoR's to increase the quantities, and the variation was committed before the batch routine was run and committed.

So now, we have a job that has a total value of £7,566.91 and Paid at £4,998.42: the remainder cannot be requested as we can't add archived SoR's to a new request; and we can't reverse the variation as you can't vary Archived SoR's.

We tried allowing duplicate SoR's to be added to a request (something we definitely do not want as a regular occurrence due to rounding issues in the past) and ticking the "job Complete" flag Confirm automatically varies items to the requested amounts.... instead, it varied with the new items but left the old the same, so in DEV the job is now worth £10,135.40 instead of the £7.5k it should be.

Anyone have any ideas if this can be fixed?

Thank you in advance.

------------------------------
Ana Resende
Gloucestershire County Council
GLOUCESTER
------------------------------