3200837 - Values not appearing in Personal Data Collection or Manage Pending Hires page - Onboarding

In SAP SuccessFactors Onboarding, one or both of the following behaviors are observed:

• Field values do not appear on the Personal Data Collection (PDC) page when the new hire opens the step.
• Field values do not appear on the Manage Pending Hires (MPH) or Manage Pending Recruits (MPR) page for external users coming from Onboarding into Employee Central.

In some cases values appear below the field instead of inside it, indicating that the value sent by the source system does not match the available options on the target field.

SAP SuccessFactors Onboarding

1. Initiate an onboarding process for an external candidate from Recruiting or Onboarding.
2. Open the Personal Data Collection step as the candidate, or open the candidate from Manage Pending Hires in Admin Center.
3. Observe that one or more fields are blank, are not editable, or display values below the field rather than inside it.

The PDC and MPH pages render fields based on the data model configured in Manage Business Configuration:

• The PDC page follows the Onboardee person type data model (for example, JobInfo_Onboardee) when configured. If no Onboardee person type data model exists, the PDC page falls back to the Succession data model.
• The MPH/MPR page follows the Employee person type data model (for example, JobInfo_employee) when configured. If no Employee person type data model exists, the MPH/MPR page falls back to the Succession data model.

Values fail to appear when one or more of the following conditions are present:

1. Field permissions for the external user role are missing or restrictive (Employee Central Effective Dated Entities or Employee Data permissions).
2. Field visibility in Manage Business Configuration is not set to Editable.
3. A business rule is clearing or defaulting the field value during the onboarding context.
4. Locale is not maintained for the candidate, which suppresses picklist values for external users.
5. Field values sent from RCM do not match the picklist options available on the target field; Onboarding rejects the value and leaves the field blank.
6. Field IDs in the application template, job requisition template, or offer template do not match the IDs in the integration template (for example, application template field id "first-name-alt1" but integration template refid "first_name_alt1").
7. Source field IDs are not present in the integration template, so no data flows.
8. Data type mismatch exists between the RCM field and the Employee Central field in Manage Business Configuration.
9. The BPE service user configured in Update Process Flows for Onboarding and Offboarding does not have permissions to the affected fields.
10. Personal Information Screen Lookup is missing for Payment Information, or External User Visibility is not set to Yes for Custom Pay Type.

For Live Customer(s)

1. Confirm the data model in scope. In Admin Center > Manage Business Configuration, verify whether an Onboardee person type data model (PDC) or Employee person type data model (MPH) is configured. If neither exists, the page follows the Succession data model. See Help Portal, Personal Data Collection Configuration: Personal Data Collection Configuration | SAP Help Portal 
2. Verify that field visibility in Manage Business Configuration is set to Editable for the affected fields.
3. Verify role based permissions for the external user role under User, Employee Central Effective Dated Entities and User, Employee Data. See Help Portal, Role Based Permissions for New Hire and Internal Hire Data Review: Role-Based Permissions for New Hire and Internal Hire Data Review | SAP Help Portal 
4. Confirm the candidate locale is maintained. Missing locale suppresses picklist values for external users.
5. If a value appears below the field instead of inside it, compare the picklist options on the target Onboarding field against the value sent from RCM. Onboarding leaves the field blank when the value sent does not match an available option.
6. If Payment Information is missing on PDC, verify that a Personal Information Screen Lookup is created in Manage Data and includes Payment Information. If pay type shows No Data, set External User Visibility to Yes for the Custom Pay Type field.
7. If values appear below fields such as Legal Entity or Position, verify that a BPE service user is set in Update Process Flows for Onboarding and Offboarding and has permissions to those fields. See Help Portal, Setting Up a BPE Service User: Setting Up a BPE Service User | SAP Help Portal  and Help Portal, Editing the Process Flows for Default Onboarding and Offboarding Processes: Editing the Process Flows for Default Onboarding and Offboarding Processes | SAP Help Portal 
8. Identify rules clearing the field value. In Manage Data, create a Rule Trace object, reload the affected step for the candidate, and download the resulting CSV to identify which rule executed. Disable the rule, or scope it so that the Onboarding context evaluates to No.
9. Use the URL replay test for the NHDR to PDC flow. Copy the URL of the Provide Personal Data tile from the candidate login. After submitting the PDC step, open the copied URL in a new tab. If the data appears, saving is not the issue. If not, the candidate is missing field or object permissions.

For Implementation Partner(s) and Consultant(s)

When values are not flowing from Recruiting to Onboarding, verify the integration template (<>-mi-transformation-datamodel.XML) against the application, job requisition, and offer templates:

1. Field IDs must match exactly between the integration template (refid) and the source template (id), including underscores versus hyphens.
2. All source field IDs must be present in the integration template; otherwise no data flows for that field.
3. The data type of the RCM field must match the data type of the Employee Central field in Manage Business Configuration.

Template alignment is partner managed configuration. Engage your implementation partner for changes to integration templates and data model XMLs.

• 3023841 - Missing Field Values in Manage Pending Hires - Onboarding - SAP for Me
• 2956463 - Depended Entity for New Hire in PDC not foll
• 3073634 - Payment Information missing in Personal Data Collection - Onboarding - SAP for Me
• 2948472 - Pay type show as "No Data" for external users - Onboarding 2.0 - SAP for Me
• 3005131 - Account Owner field populated with 'null null' value - Onboarding 2.0. - SAP for Me
• Personal Data Collection Configuration | SAP Help Portal
• Role-Based Permissions for New Hire and Internal Hire Data Review | SAP Help Portal

SAP SuccessFactors Onboarding, OBX, RCM, Recruiting, Personal Data Collection, PDC, Manage Pending Hires, MPH, Manage Pending Recruits, MPR, values not appearing, blank fields, picklist no data, locale, BPE service user, External User Visibility, Custom Pay Type, Payment Information, Personal Information Screen Lookup, integration template, mi-transformation-datamodel, data model, Onboardee person type, Employee person type, Succession data model, business rule, Rule Trace, RCM to ONB, NHDR , KBA , LOD-SF-OBX-RCM , Initiate onboarding from RCM , Problem