3304992 - Null candidate ID in application table causing issues in integration - Recruiting Managemen

The Candidate ID is null in application table and it's causing issues with any integration because the Candidate ID field on the Application object is marked as Not Nullable in OData Dictionary

SAP SuccessFactors Recruiting Management

1. The Candidate ID will become null in the application when a candidate profile is deleted when using DRM 1.0
2. This can also occur for external candidates with saved or draft applications who then are converted to internal. The previous application are unlinked from the Candidate ID, resulting in null Candidate ID

It would be best to omit the Candidate ID from application table element in any integration to avoid any issues with the integration itself

If it's mandatory to have the Candidate ID from the application table, then it's recommended to migrate to DPCS 2.0. With DPCS 2.0 the Candidate ID is retained in the application table after the candidate is deleted. Please note though that the activation of this feature should be carefully evaluated. Once it is turned on, if we have any application in the status like "Deleted on demand by Candidate", "Delete on demand by Admin" or any other withdraw status you will not be able to turn the feature off. For this reason, the feature needs to be turned on only if it is required by the business. 

2568067 - Deleting or Disabling the DPCS statement for career site - Recruiting Management 

DPCS, DRM, 2.0, null, nullable, true, false, nullable=false, conversion  , KBA , LOD-SF-RCM-INT , Integration Center & Intelligent Services , LOD-SF-RCM-APP , Applicants and Job Applications , How To