Payroll, BSFN's and logging

cdawes8

Well Known Member
Payroll, BSFN\'s and logging

I've got a really weird situation.

I'm running B733.2 with SP 17.1_B1 and Vertex 2.3.2 on an Intel/NT 4.0
Enterprise server with Oracle 8.1.7.1. Clients are Intel/Win2K FAT's and
Citrix.

When I run Payroll Locally on a workstation it works.

When I run Payroll on the server it doesn't work.

When I run Payroll on the server with logging turn on for the CALLOBJECT
KERNAL's Payroll works.

The specific problem if that the Employee portion of the Canada Pension Plan
deduction does not calculate properly. What the system does when running on
the server with no logging on is take the employee to the max for the year
instead of calculating just for the current pay period.

JDE is still scratching their heads. Why would the problem not occur when
logging is turned on? Does anyone have any ideas on what to do? I would
normally just get a log and send it to Denver but with logging on it works
so that's not much use.

Thanks

Colin

Colin Dawes
City of Guelph
B733.2 SP17.1_B1, Intel/NT/Oracle 8.1.7.1 FAT & TSE
 
Re: Payroll, BSFN\'s and logging

As you probably know... Payroll is uniquely BSFN laden... (as opposed to UBE / and Event Rule... like other applications).

But what about putting in poor man's debugging (add certain things in the code to attempt to capture certain conditions in and around the Vertex bit..)

Sounds like some sort of timing issue (debugging is slowing it down so it can connect or something).

On the AS/400... looking at the job log of the JDENET_K Call Object has revealed Vertex issues before to me. Not sure if you have that sort of "operating system" logging that can help on the Intel platform.

AS400 V5R1, XE+XU1+45ESUs, SP16.1, NT-SQL7 for CO
 
Re: Payroll, BSFN\'s and logging

Hi Colin,

I agree with Jack. It is almost sure that this is a timing problem.
We also faced similar problems that an error doesn't occur when debugging is on. Running locally also slow down the running (data access happens on the network between client and server), so also can eliminate the timing problem.

First check your table spaces. When auto increment have started then it can cause this type of problem. If this happened then increase the table spaces.

I know, there are some timing related settings in jde.ini too, try to increase these values. Excuse me, I can not tell you what are these settings and I can not ask any CNC guy currently. I hope, you will find them.

Merry Christmas and Happy New Year!
"Kellemes Karácsonyi Ünnepeket és Boldog Újévet!"

Zoltán

B7332 SP11, ESU 4116422, Intel NT4, SQL 7 SP1
(working with B7321, B7331, XE too)
 
Back
Top