CTE Login Name

[nsiatirlis]

Hello experts,

While reviewing the job result for the 305 file from SF to Concur, we are encountering the following warning:

"The Login ID provided for the employee with Employee ID 9697 in the 300 or 305 record is different than currently exists on the user's profile. It has not been updated by the 300 or 305 record. To update the employee's Login ID use a 320 record, manually update in User Administration, or use the NewLoginID field on the User Import. For more information about this or other errors, please search for the error message in our Knowledge Base."

Could you please advise on how we might resolve this warning?
(Manual correction is not feasible, as there are many similar cases).

Thank you in advance,
Nikos.

[KevinD]

@nsiatirlis seems like the message you received provides all possible ways you can resolve the issue. I'm not sure anyone reading this will provide a solution different from the message you received.

Why can't you manually update the user's Log in ID? 

[nsiatirlis]

Hi Kevin,

Thanks for your response.

The reason why manual update is not feasible is because this affects at least 100+ employees, and there is a possibility that these changes will reoccur in the future, as the Login ID is maintained in our client's master HR system (SAP SuccessFactors).

To give you a complete picture:

There is an existing integration in place using the 305 file, which handles user data from SF to Concur.

However, based on the error message, it appears that the 305 file does not update the Login ID.

Instead, the 320 file is required to change the Login ID in Concur.

So, my main question is:

Would it be necessary to build a second integration that generates and sends a 320 file to update employee usernames (Login IDs), every time there is a change in the master system (SF)?

Appreciate your guidance.

Best regards,
Nikos