on 08-17-2020 12:04 PM
Hi Experts,
US - UK
New personnel number created during Inter company transfer from US05 to UK01 in Q - System without delimiting the Old Company code mentioned in the attached API. Please provide a fix to this Issue at the earliest
Issue 1: Reason for not delimiting the old record mentioned in the attached API
Issue 2: What is the reason for creation of new Personnel Number
Issue 3: Process and Impact analysis for deletion of old personnel Number.
US-US - Successful
Note : For within USA i.e from company code US02 to US05 it was working fine as required.
Also is it correct to delete the old personnel number to fix the issue ?
Links Referred: Global Employment
https://help.sap.com/viewer/b7b190087c1d4f9fad2bad3ca0d22d50/2008.500/en-US/fb4d2b4090e84d9599720af3...
Error Handling in workforce API
https://help.sap.com/viewer/b7b190087c1d4f9fad2bad3ca0d22d50/2008.500/en-US/3f80914ee4274a138e818860...
Regards,
V
Hello vangala07
A new Personnel Number must be created for each company code assignment (for different countries).
I saw you already raised a ticket. I'll check it and reply you there.
The Personnel Number can be deleted if this employee is not linked to any project / timesheet. But it's not wrong to have an obsolete Personnel Number.
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Javier - History of records are gone with the old Pernr as that is linked to project, however new ID does not have project associated and i am not sure if this is captured in Info type change documents, however, i am ok as the username is unique to both the numbers, but at least it should delimit the date to -1 logic or at least what is mentioned in the API load to avoid discrepancies
Also will it be the Same business partner or it will also be updated as i see BP sync message twice in the API.
But wanted a detailed Impact Analysis please. Thanks
Regards,
V
User | Count |
---|---|
85 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.