3655379 - E-Verify Task Error - Onboarding

Onboarding 2.0 E-Verify Task Error, "Request Type cannot be null in requestPayload". 

"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 2.0

1. Login to SuccessFactors and go to ONB 2.0
2. Take candidate's activity
3. select "Accept & Confirm New Hire's response"
4. Receiving an error that reads "Request Type cannot be null in requestPayload". 

Customer has outdated BPE process.

Recommended to update Process Flows for Onboarding and Offboarding to prevent the issue for any new candidates and provided workaround for impacted candidate.  

1. Firstly, customer must run Update Process Flows for Onboarding and Offboarding from an admin centre this is to prevent, so no new issues to come with new candidates.
2.  Work around for impacted candidates: we need to add a link on fanDocumentId to their E-Verify data;

Here are steps to add a link on fanDocumentId to their E-Verify data.

1. Find a signed document in manage documents for affected candidate, example screenshot below
   
   
   
2. Get Attachment ID there.
3. Go to manage data -> E-Verify data -> search for E-Verify data of impacted candidate> click on correction.
4. Under FAN attachment ID > put the Attachment ID which got from manage documents.
   
   
   
   
5. Now go to "Complete E-Verify: Tentative Nonconfirmation:” step and refresh the page -> it should have FAN signed document now at the manager's view. Like below image.
   
   
6. After page refresh, it should work fine and unblock E-Verify flow and customer can proceed further.

• 3614879 - Unable to submit TNC task - Onboarding
• 2163516 - E-Verify Further Action Notices (FAN) for Tentative Nonconfirmation (TNC)

Request Type, cannot be null in requestPayload, E-Verify Task Error, TNC , KBA , LOD-SF-OBX-EVF , Everify , Problem