BSI TF 10.0.e1 - Message not showing 10.0.e1 cyclic

And yet another BSI post... I have just upgraded our production BSI from 10.0.d to 10.0.e1 and thought things looked good until I ran the PRTF screen and it is not showing the correct release (10.0.e1) in the BSI TF Client Messages screen. The System Tools screen shows the correct cyclic version (10.0.e1). Has anyone run into this and what did you do to fix it? I bounced Apache service and it didn't fix it.

Thanks in advance for your prompt input!
Deanna

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Comments

martin-doherty

We re-copied the BSI server file- bounced system and it fixed it. If this doesn't work, redownload it from BSI site.

martin-doherty

Yes, delete the contents of the server install, rerun the exe file. Client and cyclic data should be ok. Just stop/start Lawson. Re-run the cmptfxora9 (or whatever command you use to link the libraries) and then run cmprts to recompile lacobrts.

unknown

Just wanted to inform PA clients, just got off the phone with BSI Support...we experienced severe issues with reciprocity when going to BSI 10E1. Narrowed the issue down to regulatory bulletin 42 when everything broke.

BSI told us they just discovered this issue where they broke 800 PA school district taxes and are working on a fix and hope to have bulletin 44 out tomorrow with the fix.

unknown

INteresting - I have been sitting here for 45 minutes installing bulletin 42 - guess it is destroying things as I type

unknown

Bulletin 42 has 60,551 records, so it is a big one, but I installed it this morning and it took less than 10 minutes.

m-nilo

Be aware that there seems to be some other issues also not related to the bulletins. We've been testing 10.e2 and found that taxable wages don't show up for resident state in the following: 1. Live in NJ, work in DE, MD or PA: 2. Live in MD, work in DE, NC, or VA; 3. Live in WV, work in PA. In some instances, State W/H was taken for the resident state and NO taxable wage was shown in PR140. BSI support is looking into the issue.

unknown

Mike,
We had to go to the Hr00 and HR01 local reciprocal flag to 0 in Lawson to fix the missing taxable wage issue...
Did you try that?

BSI Support:
The problem that you are encountering with the PA local Reportable wage not being returned is because you are passing the Employee Type value "1". This option was discontinued back in 2012 with the implementation of the PA Act 32. I have been informed by Infor that you can change this value by going into the HR00/HR01 to set the Local Reciprocal (?) flag to 0.

Copyright © 2025 Infor. All rights reserved.