*This post is locked for comments
*This post is locked for comments
Greetings Donnette - I am running in to the issue as well, would you mind sharing the solution you found?
Thanks
John.
Yes I did find a solution. Thank you.
Hello Donnette and John,
Are you still experiencing this issue? If so, here's the logic in the taSopHdrIvcInsert stored procedure that's being checked to determine if that error should be given:
1) First, it determines the value of @DEPOSITS and @PAYMENTS using the following queries:
select @DEPOSITS = isnull(sum(p.AMNTPAID),0)
from SOP10103 p (nolock) left outer join SY03100 b (nolock) on p.CARDNAME = b.CARDNAME
where p.SOPTYPE = @I_vSOPTYPE
and p.SOPNUMBE = @I_vSOPNUMBE
and (p.PYMTTYPE in (1,2,3))
select @PAYMENTS = isnull(sum(p.AMNTPAID),0)
from SOP10103 p (nolock) left outer join SY03100 b (nolock) on p.CARDNAME = b.CARDNAME
where p.SOPTYPE = @I_vSOPTYPE
and p.SOPNUMBE = @I_vSOPNUMBE
and (p.PYMTTYPE in (4,5,6))
You will need to substitute the values in your XML for @I_vSOPTYPE and @I_vSOPNUMBE
2) Then, this is the ultimate comparison for Error Code 60. Just sum up @DEPOSITS and @PAYMENTS and compare it to the <PYMTRCVD> value you've passed.
if ((@DEPOSITS + @PAYMENTS) <> @I_vPYMTRCVD)
If the two sides of this equation don't match up you have a problem and will receive this error.
Let me know if you have any questions.
Donnette, did you get an answer to your problem. I am running into the same problem with 2 taCreateSopPaymentInsertRecord s
André Arnaud de Cal...
292,494
Super User 2025 Season 1
Martin Dráb
231,307
Most Valuable Professional
nmaenpaa
101,156