on 04-21-2022 10:43 AM
Hi, we are a global business and have separate company codes for each physical office. It is not uncommon for us to have a user who works for another company for a period of time, sometimes people even move permanently from the US office to the UK office for example. We do not have any HR modules, so our users are created using the import employees app.
You cannot re-import a user with a different company code, so how do you change a company code?
I tried deleting the user and re-creating, but it knows the deleted user exists still.
We need to retain the same user ID (firstname.surname) for the purposes of authentication (SSO to Azure AD), so we cannot use a different user ID.
Can anyone advise the procedure/method for doing this? We would have a similar issue with a name change too for example if somebody got married I expect.
We need to be able to do this, it's essential. Many thanks.
Hi
I understood that you need to change an existing employee company code. This is not possible via import employee app (reason is that these are HR operations - termination and rehire - and not foreseen via this app). the possible solution for this is to use external workforce API. See here the use cases (rehire) with sample payloads.
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just a potentially helpful response to add - the 2302 upgrade is a game changer, the 'Manage workforce' tile now allows this and more as far as I can see. Finally my life is a little easier! 🙂
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Alan
This note https://launchpad.support.sap.com/#/notes/2555311 and then the related ones explain what are the options in case of company code changes.
start from: "Note: company code change is not supported by the simpler approach of Import Employee App (error Employee: XXXX - CompanyCode cannot be changed). In case a company code change is required in this scenario one alternative would be to delete the employee and recreate it again in correct company code (for more details see KBA 2702011), another alternative could be moving to use the Public API or SF replication which both cover this possibility."
Thank you, hope gives initial direction.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
6 | |
5 | |
5 | |
5 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.