BN305 Changing Email Addresses?

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.

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.

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!

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

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

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?

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.