Internal Error when viewing an activity in E-Rec after a username change

Question

Hello,
Hereu2019s a brief explanation of the scenario that we are in:
u2022 We created a new User ID for an employee because of his/her name
change.
u2022 We then attached this new User Id to her HR master records using Info
Type 105 (IT0105) subtype 1 (ST01).
u2022 This employee already had her previous User ID attached to his HR
master records using the same IT0105 ST01. So now, this employee has 2
IT0105 ST01 records.
u2022 We transferred these records (old and new ids) to E-Recruiting via
ALE process.
To do this ALE process, we executed RBDMIDOC program on the system
where our HR Master Data reside.
u2022 Then in our e-recruiting system, we executed RBDAPP01 to process
these idocs.
u2022 This processing delimited the old User ID and created a new User ID
for the same person in the e-recruiting system. We can view this
relationship in HRP1001.
u2022 Now, prior to her name change, this person had performed some
activities on a candidateu2019s records in E-Recruiting. Obviously, these
activities were performed with his old user ID. So those activities
have the old user ID associated with them.
u2022 After sending the new User Id in e-recruiting, when we go to view
those candidate activities in candidate overview, the system throws the
internal error message.
The format that we use for creating usernames is last name first letter of first name, i.e. Bob Jones would look like JONESB.
At present the only way to remedy the situation is to have the recruiter who's name (and username) changed manually change it for each activity.
After opening up a message with SAP they responded with:
Dear Customer,
That's right. The reason why this recruiter doesn't see his/her
activities is because they were created under a different user.
E-Recruiting is designed with a stable CP-US relationship. If you
do a delimination this can cause problems for the recruiter (as
mentioned above) as in IT5131 the user is stored as team member.
If the user assigned to a CP changes, the responsible candidate class
cannot be instanced anymore. So we strictly recommend not to delimit theCP-US relation.
Has anyone else experienced the problem?  How did you address it?  It has been my experience to use the name of the employee when creating a username.  This has never been a problem in our core system, just in E-Recruiting.
Thank you for your help!
Regards,
Ryan

Answer 1

DonSu,
You have to look at the line above it to gather what's happening.  As I mentioned it making a call to get the contents of the Data Source using GetDataSourceContents.  What you might try is making the same call using Microsoft APIs and PowerShell.
http://technet.microsoft.com/en-us/library/reportservice2010.reportingservice2010.getdatasourcecontents.aspx
[string]$folderDestination = "/<Path to Data source>"
[string]$webServiceUrl = "https://EnterURLhere/ReportServer/ReportService2010.asmx"
$ssrsProxy = New-WebServiceProxy -Uri $webServiceUrl -UseDefaultCredential
$DatasourceContent = $ssrsProxy.GetDataSourceContents($folderDestination)
$DataSourceOutput = $DatasourceContent | Select-Object ConnectString, Extension, Enabled, UserName, WindowsCredentials, CredentialRetrieval
Write-Output $DataSourceOutput