3729385 - Application error when submitting personal data collection step - Onboarding

• Error message example:
  • “An application error occurred. Please try again later, or notify support (with the error information of errorId=[IDNUMBER], timestamp=[TIMESTAMP], and the version information from the current screen) if the issue keeps occurring.”
    
    
  • “An application error occurred. Please try again later, or notify support (with the error information of errorId=123456789123456789132, timestamp=2026-01-01T01:12:43.193+0000, and the version information from the current screen) if the issue keeps occurring.”
    

    The application error usually occurs when initiating onboarding for any hire type through the API with dependent information, the visibility of dependent information to external has no value (the PerPerson entity record's visibility is not set to 'y'). This leads to an issue during the personal data collection (PDC) step, where the existing dependent data fails to load.

SAP SuccessFactors Onboarding

1. Launch the Onboarding process and navigate to the PDC step as the candidate.
2. Submit the PDC form.
3. Observe that the submission fails with the application error and errorId/timestamp.

Scenario A: Field Type Mismatch Between Object and UI

• Cause:
  • A mismatch exists between the object field type and the UI configuration:
    • The object field is defined as a picklist.
    • The UI field is configured as a string.

Scenario B: Dependent Information Visibility Not Set via API (Known Issue)

• Cause:
  • Known product issue where dependent data lacks external visibility, preventing dependent records from loading during PDC.

Scenario A: Field Type Mismatch Between Object and UI

• Resolution:
  • Compare the impacted field in both:
    • Object Definition (confirm picklist vs. string).
    • UI Configuration (confirm field type and picklist binding).
  • If a mismatch is found:
    • Delete the problematic UI field.
    • Recreate the UI field with the correct type and picklist association to match the object definition.
  • For internal SAP support engineers: Review internal memo for pertinent logs to validate the failure context and confirm the mismatch.

Scenario B: Dependent Information Visibility Not Set via API (Known Issue)

• Resolution:
  • The tentative fix for this issue is scheduled to be released in 2H 2026 Release.
  • Please follow this KBA for updates. Click on star to bookmark this article to receive updates about this issue. For more information about updates from subscribed KBAs, you can refer to the KBA 2171560 - How to be notified of new or updated SAP Notes or KBAs.

KBA 2171560 - How to be notified of new or updated SAP Notes or KBAs.

application error, personal data collection, onboarding, dependent, information, visibility issue, PerPerson, entity, errorId=, timestamp, PDC, data load failure, custom MDF object, hire template, API issue, obx, onb, errorId, UI field mismatch, hire template configuration, intermittent error, Unable to set the value, OBX-41179  , KBA , LOD-SF-OBX-PDC , Personal Data Collection , Problem