BN305 Changing Email Addresses? - LawsonGuru.com

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chris Martin	825

Woozy

Veteran Member

Posts: 709

New Poster

9/27/2010 9:00 PM

We've encountered a strange issue, and I'm hoping someone can point me in the right direction.

When we run BN305 'Highly Compensated Employees' in Update Mode, it is pulling the email addresses of some of the employees processed by the report, and overwritting email addresses for one or more other employees that aren't being processed by the report.

We didn't notice this until it had been run in PROD, but we've since duplicated it in two other prodlines on another box.

I have a CASE open with Lawson, but it's stalled. The engineer said that she couldn't find any issue reports on BN305 and that it would be tough to duplicate in their test environment, since they "don't have many email addresses loaded".

Has anybody experienced this issue? Any idea why it would be doing this and how to fix it?

Thanks!

Attached is a de-identified sample of what the data is doing.

Tags: BN305 email highly compensated comped

Deleted User

New Member

Posts: 0

9/28/2010 11:20 AM

I will need to run this in our test system to see if I can duplicate it. I must say this brought a smile to my face first thing in the morning. I am sure your GSC support engineer is going to load an em address in a few employees so they can see if they can duplicate the issue.

or that would seem to be a reasonable expectation.

Deleted User

New Member

Posts: 0

9/28/2010 11:44 AM

I just tested ours and I am not seeing the issue. To be sure we are talking apples to apples, are you referring to the e-mail address on the HR11 work tab? We are on 9.0.0 apps, however and do not have LTM.

Woozy

Veteran Member

Posts: 709

New Poster

9/28/2010 12:44 PM

Hi Margie - thanks for taking the time to try it. If I hadn't been able to duplicate the problem in three different prodlines, I don't think I would have believed it.

Correct - I am talking about the email address on the Work tab (EMP-EMAIL-ADDRESS). We are on 9.0.1.4 apps, which could make a difference. For what it's worth, here's the version info for our BN305: BN305PD 5 <3653260724>

LTM should have no impact on this whatsoever. Email address is one of the fields that interface over from LTM, but this is done using Personnel Actions for the updates, and the interface didn't run during my testing.

I'm afraid you're right about what our GSC Engineer will do to test it. I'd be surprised if they can "really" duplicate the issue. We have over 25,000 total employees (active and termed), of which 419 employees were processed by BN305, and only 49 of these caused problems with other employees. If they are using the "standard" test db, there can't be more than a few dozen employees total.

Hopefully someone will be able to confirm that I'm not crazy...

Thanks!

Deleted User

New Member

Posts: 0

9/29/2010 6:23 PM

Our version is ******* BN305PD 5 <3653260724> The same as yours.

John Henley

Posts: 3366

New Poster

Engaged Reader

Avid Reader

10/21/2010 8:41 PM

Yeah, that would be my expectation as well :)=

John Henley

Posts: 3366

New Poster

Engaged Reader

Avid Reader

10/21/2010 8:41 PM

Couple of other things to check:
1) are there any processflows or external interfaces in your production system that update the email address on EMPLOYEE table
2) do you have any database triggers on the EMPLOYEE table in your production system?

Woozy

Veteran Member

Posts: 709

New Poster

10/22/2010 1:45 PM

Sorry I never updated this ticket. We found it was more than just email address - it was also position that was being changed.

Global Support was able to duplicate our issues. They have opened a problem tracking ticket on this issue (JT-180515) "regarding BN305 changing email and position when run in Update". The JIRA is a priority 3.