3535631 - Error in Personal Data Collection Step After Onboarding Restart - Onboarding

• An error occurs when submitting the personal data collection step after the onboarding process is restarted.
• The error message displayed is "java.lang.IllegalStateException: java.lang.IllegalStateException: com.successfactors.genericobject.app.exception.MDFSQLException: com.sap.db.jdbc.exceptions.BatchUpdateExceptionSapDB: [301]: unique constraint violated: Table(GENERIC_OBJECT_T), Index(UK_GENERIC_OBJECT_T_EXT_CODE)(input position -1)".

• Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental

SAP SuccessFactors Onboarding

1. Using Hire Template
2. Restart the onboarding process.
3. Attempt to submit the personal data collection step.
4. The error message is displayed.
   

The error is caused by the absence of an external user visibility rule set for the Payment Information object or Person Type.

1. Follow the steps from KBA 3477152 - [Onboarding] How to set the external user visibility for MDF objects via Business Rule.
   1. If externalUserVisibility field is not available in rule for selection please change the visibility of the field in the object itself first
   2. Navigate to Configure Object Definition > Payment Information
   3. Click Take Action > Make Correction 
   4. Look for field externalUserVisibility
   5. Click Details
   6. Change value for Visibility to Read Only or Editable
   7. Save
   8. Try again to create the rule following steps in KBA 3477152 - [Onboarding] How to set the external user visibility for MDF objects via Business Rule
2. Once the rule has been configured, add the rule in Configure Object Definition > Payment Information > Save Rules.
3. Create a second rule for PersonType external user visibility, same as payment info but object is PersonType.
4. Once both rules are created; one for Payment Information external user visibility, one for PersonType external user visibility and added to the objects, perform an odata refresh.
5. Restart Onboarding again for the affected candidate
6. Complete NHDR (if you do not have a NHDR step, please access new hire data from dashboard and submit)
7. Now in PDC error should not appear.
8. Support see internal memo

Refer to KBA 3477152 - [Onboarding] How to set the external user visibility for MDF objects via Business Rule for more details.

SAP SuccessFactors, Onboarding, Personal Data Collection, Error, MDFSQLException, BatchUpdateExceptionSapDB, External User Visibility, Payment Information, Person Type, [301]: unique constraint violated: Table(GENERIC_OBJECT_T), Index(UK_GENERIC_OBJECT_T_EXT_CODE)(input position -1) , restart, 301, custom template, template, hire template, OBX-31322, service layer, centralized services. , KBA , LOD-SF-OBX-PDC , Personal Data Collection , Known Error