Symptom. When doing a basic import for inactive users to be made active, an error is encountered: User: [1] Duplicate person_ id _external [1] Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
2772512-User: [***]This UserId [***] is duplicated with existing person_ id _external Symptom You are trying to import the basic import but when doing so you are receiving an error message saying that the user ID is duplicated in another person_ id _external.
Symptom. When creating a new Employee via import, after importing the Basic User Data you encounter an error message [There is already another person in the system with the same Person ID External] when validating/importing Biographical Information for a user. Image/data in this KBA is from SAP internal systems, sample data, or demo systems.
While that might be the case, often the duplicate error is caused by an existing record already in your system conflicting with one new record you are trying to import that is also referring to the same username/userid. To effectively troubleshoot the duplicate error you will need both your import file and a fresh employee export file.
The below error appears while updating/upserting username for an employee in Successfactors . DUPLICATE _USERNAME : Failed to add/update user [XXXX] XXX YYYYY (N/AN/AN/A): Duplicate Username – XXXX. This error can appear either when an API is used to upsert or a csv import is used to upsert in Successfactors .
4/7/2018 · Person ID External already exists error Scenario When creating a new Employee via import, after importing the Basic User Data you encounter an error message (Person ID External already exists error)There is already another person in the system with the same Person ID External] when validating/importing Biographical Information for a user,, 6/6/2016 · Set Company System Setting – Next Person Id Assigned and make personInfo.person- id -external visibility to View. Disadvantages: Variant 1 – nothing preset, so it can be hard to use the same convention for all employees Variant 2 – can be hard to find some data relevant to the employee (you see only generated ID)
