Symptom
- E-Verify is determined by state/locations.
- E-Verify is set-up to trigger if the company code and location has a flag.
- If a company code is listed and a location isn't flagged, E-Verify will not run.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
SAP SuccessFactors Onboarding 1.0
Cause
1. Misconfiguration on settings in SuperAdmin for the Company Structure (Location and any other Corporate Structure Level Properties)
If the key StartEverifyProcess is set in Level Property the EVerify process will be triggered even if candidate is not in a location for Everify
2. Step Action overwriting the Corporate Structure data
Resolution
1.
- Login to SuperAdmin
- Go To Corporate Structure and open all the levels one by one to see if the key StartEverifyProcess is present in Level Properties
- If key is present:
-
- Delete the key and save the settings
- Test with new candidate
- Issue is resolved.
- Delete Key
2.
- Login to SuperAdmin
- Go to Processes and open the Onboarding process for which the affected candidate went through
- Go to all the steps available (1, 2, 3) and check in Assign Actions whether there is any step action added for each step to confirm the value from the key used to trigger E-Verify is not being overwritten with a different value
Keywords
EverifyStartProcess, Key, Non-Everify Candidate, E-Verify by Location, non-US, global. , KBA , LOD-SF-OBD-EVF , e-Verify , Problem
SAP Knowledge Base Article - Public