KHOSI
Active Member
Hello,
I've been having this strange bug in Payroll since we moved from SP15 to SP20 with Oneoff R1. Hoping someone had experienced something like this before in other apps.
Provincial Taxe does not calculate in Payroll interim whenever the server JDE.INI debug OUPUT=NONE. BUT whenever I put OUTPUT=BOTH, provincial taxe started to calculate as should be. Someone mentioned to me that he had a similar problem in Postings but as soon as they turned on the debugger, numbers got well calculated but when they turn debugger off results were blank. He told me that because the job ended before it finished the calculations therefore when the debugger was turned on, it has time to go in each step and complete calculations. Unfortunately, he forgot what he had changed in his JDE.INI.
THis is a good one but I am sure that you experts will give me a hand on this. JDE does not have a clue and as usual they said that they were not able to replicate the problem at their site so....it's on us.
Right now, we are backing to SP15 but still have a test environment for SP20 on different enterprise server.
NOTE: we are still on B7332
I've been having this strange bug in Payroll since we moved from SP15 to SP20 with Oneoff R1. Hoping someone had experienced something like this before in other apps.
Provincial Taxe does not calculate in Payroll interim whenever the server JDE.INI debug OUPUT=NONE. BUT whenever I put OUTPUT=BOTH, provincial taxe started to calculate as should be. Someone mentioned to me that he had a similar problem in Postings but as soon as they turned on the debugger, numbers got well calculated but when they turn debugger off results were blank. He told me that because the job ended before it finished the calculations therefore when the debugger was turned on, it has time to go in each step and complete calculations. Unfortunately, he forgot what he had changed in his JDE.INI.
THis is a good one but I am sure that you experts will give me a hand on this. JDE does not have a clue and as usual they said that they were not able to replicate the problem at their site so....it's on us.
Right now, we are backing to SP15 but still have a test environment for SP20 on different enterprise server.
NOTE: we are still on B7332