3721886 - MDF fields are not visible in onboarding - Onboarding

• MDF records created via external ATS integration are not visible to onboardees.
• MDF records manually created in the same MDFs are visible to onboardees.
• e.g. when a record is created manually using "Personal Phone" type, only this record is visible to onboardees, while the record created via integration using "Other Phone" type remains invisible.

SAP SuccessFactors Onboarding

1. Navigate to Manage Data -> Personal Phone Information.
2. Search for the user ID "user's id".
3. Observe the record created via integration using the Phone Type "Other Phone".
4. Create another record manually using the Phone Type "Personal Phone".
5. Access the system as the onboardee and verify visibility.

Records created via API do not always receive the required external-user context used by onboarding processes.

1. Run the MDF Object Definition to DB Sync Job from provisioning.
2. Navigate to the instance and access External User Visibility.
3. Check the box for Custom Objects.
4. Provide the object code: cust_PersonalPhoneInfo.
5. Click "Run".
6. Test the visibility with a new user to confirm the resolution.

3477152 - [Onboarding] How to set the external user visibility for MDF objects via Business Rule

obx, MDF record visibility, onboarding process, external ATS integration, external user visibility, MDF Object Definition, DB Sync Job, API record creation, external user context, onboarding MDF objects , KBA , LOD-SF-OBX-DC , Personal Data Collection , Problem