PR39.2 AddIn not working after CTPs

It is a well-known/documented work around to upload one-time benefit deductions via PR39.2 instead of PR39.1. (PR39.1 produces a pop-up of PR35 that AddIns cannot accommodate.)

But we recently installed CTPs 121887 and 121985 for phase 2 of the W4 changes and now our PR39.2 AddIn does not work. We get no error messages but the entries are not in portal when we inquire. When we enter directly to PR39.2 now, PR35 pops up, so we're thinking that is the change/issue.

Is anyone else seeing this?

Attachment_4338.zip

Find more posts tagged with

Infor Lawson Human Resources Group - Discussion

Accepted answers

All comments

unknown

I'm not familiar with this specific issue, but we had issues in the past where the add-ins worked fine before patching/upgrade and then didn't, with no error message, and also only on a specific screen - it wasn't "broken" across the board. The resolution was to upgrade the add-ins installed on the desktop. See if you're up-to-date on the add-ins install. Sounds like a crazy resolution, but I've seen it happen.

unknown

Yes, we are seeing this too. Support says this is "working as designed' - in fact, they fixed a design flaw that previously allowed us to upload to PR39.2. There is a way to do it now, but you have to query the table to get the sequence number, then upload that as well. Plus we are also getting the false positive with the "add complete - continue" message even though it really didn't add anything. My users are not very happy with this...

unknown

Hi, just wanted to mention that, since installing the W4 patches, we are having an issue with the PR39.1 redirect to PR39.5 when users enter multiple one time deductions that require a date to be chosen on PR39.5. It used to be that, once you were redirected to PR39.5, when you selected the date and clicked OK, Lawson would take you to PR39.5 for the next deduction that needed a date sleected. Now, it takes you back to PR39.1. I opened a support case on the issue this morning. Hopefully if enough people report various problems, they'll take a look at PR39 and do some more testing and hopefully get these things fixed.

unknown

We are up to date with add-ins and I have an incident 14567173 opened with support at this time. I am requesting that they write up a JT for the false positive "add complete - continue". The Sequence number only works for employees that have a deduction without an end date . Prior to patch one time deductions did not require sequence number and would add deductions that had end date. Work around for onetime deduction was to add a new PR14 record with a deduction not tied to an end date for the employee.

unknown

I am not able to find your incident to review. Has there been any update from INFOR on this issue? Are they planning a fix?

unknown

In our case - I have been waiting for > 1 week for a reply on our PR39 case. We found that the W4 patches also caused problems with benefit deductions, our case on that has not had any activity from infor in > 2 weeks.

unknown

We have not formally issued an incident, but we will need to as well. We have been trying to get through testing the Phase II W4 patches, but keep finding bugs. We've had to implement 3 CTPs so far to fix issues with 2 for PR14 one for PR160 and now we have this issue with PR39.2 that is holding us up in moving the Phase II patches forward to PROD. It's been very frustrating with all the bugs.

unknown

Infor Lawson development is arguing the false positive that has been written up under JT-142269 on incident 14567173. The PR14 works but the deduction cannot be tied to a previous deduction with an end date to which the employee was previously enrolled. Prior to the patch you would receive an error similar to the following:

Add Comp:Warning; emp <number> ded <dedcode> not within eff dt rng

But now you get the false positive "add complete - continue".

unknown

Please provide your email address and I will send you an addins template and .uwf file to use to upload directly to PR39.2; I would attach here but do not see an option for attaching a file to my message.

unknown

faas.cathy@mayo.edu thank you Todd that would be helpful.

201009com_proactive.pdf

unknown

Would you mind sending me the files too. We have been having the same issues

Jennifer.Hinz@unitypoint.org

unknown

just sent

unknown

just sent to you as well

0811181026417683.xls

deanna-plant

We had issues with random PR14 benefit deductions not having the Cycle's marked therefore deductions were not taken. We installed CTP to fix this issue: CTP 111257

unknown

Because Infor development is disputing the JT-1422696 i also added Enhancement Request 57345 just in case infor Support is not able to get this bug fixed. You are welcome to endorse the Enhancement Request to see if we can get this issue pushed up to the product manager.

unknown

Hey Trevor, sounds like you are fighting the same battle I am. If we use an old or incorrect mapping for the new PR39.2, the upload wizard returns "Add Complete - Continue" even though the record was not added. Somehow support thinks this is ok, and is working as designed. You can create a mapping to the new version of the screen (use transfer and sequence number fields), but the false positive is a big issue.

unknown

Todd, can you please share your files with me as well. Alia.Qureshi@fmolhs.org

Appreciate it.

unknown

Thanks for doing that. I'll go out and endorse it immediately. We are also going to escalate this issue since we have a major process built around using Addins for our billing process.

unknown

I also endorsed your enhancment! I am so disappointed in how S3 HR/Payroll/Benefits is being neglected these days.

unknown

Sorry for the delay-been in meetings since this morning. Just sent you the excel template and the .uwf file for the addins upload.

unknown

Todd, can you share with me also. Having the same problem with addins.

0911060553270289.pdf

unknown

I know this thread is specific to PR39.2 but I wanted to share that the PR39.2 issue is only one of the issues we found after putting in the W4 patches. (We put in 121887 and 121931). We obviously found the issues with PR39.2 like everyone else, and how the logic was changed which subsequently caused the Upload Wizard to return false positives, but we have also had problems with PR160 (required another patch), problems with drilling on any field after an add on PR80 or PR39 (required an upgrade to a newer version of Smart Office), problems with certain deduction codes on PR14 (required yet another patch). So far that's all we have found (LOL). Anyone else find any other issues?

unknown

Our PR160 just came up with error "ERN2 record exceeded limit size of " after having installed the W4 patches

sheila-leipold

I believe it was patch 121931 that fixed our PR160 issue.

unknown

We have found all of those you indicate, but recently we also found that for in EMSS State W4 testing of those states that use the same format as FED W4 that the multiple job field is not working. If you select Yes for multiple jobs, No is what is sent to the PR13. Just found out from INFOR yesterday the fix is in the newest EMSS patch and we'll have to install that to get the state W4s to work correctly. So frustrated with this since, it seems we are all doing the testing of their code!!

karin-jensen

Hear, hear! We've had most of those issues as well. I, too, am tired of having to constantly test, watch for patches, and retest.

unknown

thank you Sheila

unknown

Is there a patch for the add ins issue?

unknown

No. Infor is saying it is working as designed. I know several folks are fighting that, because that cannot be correct. The workaround is to do a new mapping to include some transfer fields and the sequence number field. You can get the mapping to work, but you still have the risk if someone forgets and uses an old mapping, the results will say "Add Complete - Continue" even though the record was not added. That's a pretty big risk for us, so we are choosing to remove access to PR39.2 and force everyone to us PR539. As someone else said, PR539 works pretty good, but it is a new process to document/train on.

unknown

Did I see in this thread yesterday that someone in their testing found PR80 issues as well with phase 2 patches?

unknown

catf, fyi the patch we had to apply for PR160, 120726, also changed something in PR80, so it might contain a fix for PR80 issues as well. We do not use PR80 often so we didn't notice any problems with it before applying the PR160 patch.

unknown

Good morning group, FYI I just entered an enhancement request for an issue with the PR39 screen that is related to the change that is causing trouble with everyone's uploads. If you happen to be around there, please endorse it. ER 57767. thank you!

deanna-plant

Can someone also please share your files with us as well. Deanna.Plant@blessinghealth.org

Thank you so much!

sheila-leipold

Has anyone received an update on this issue? We are still having trouble with our one-time deductions that are either keyed on the PR39 or loaded with a PR539. When an employee has two payments being processed, it will duplicate the one-time deduction on both payments when running the PR140 in report. However, when we run the PR140 in update, it fixes itself. The one-time deduction is processed on the main payment and is removed from the 2nd payment (without any adjustments being made to anything). This is really starting to cause a balancing issue for Payroll. I'm just curious if anyone has a similar situation.

deanna-plant

Have these patches caused any issues to the Addins upload to PR14? And has it caused any issues to the PR514? Or are both of these still okay?

Copyright © 2025 Infor. All rights reserved.