SAP Knowledge Base Article - Public

2849733 - Standard veteran Keys are created during the import from RCM - Onboarding 1.0


Standard panels related to Veteran information are not being used in Onboarding, however some keys are generated for candidates with a predefined value, such as VeteranAnother  = Yes.

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 1.0

Reproducing the Issue

Initiate Onboarding from RCM or import a candidate from a 3rd party product, during the import a few additional keys were created. In audit trail you'll find these values in the event NEWHIRE_IMP_UPD Please find the below key list:

  • VeteranSelfId;
  • VeteranVietnam;
  • VeteranRecentlySeparated;
  • VeteranDisabled;
  • VeteranAnother;
  • Campaign.


  • The application is working as designed. This is a functionality defined in Onboarding Super Admin in the file HRXML.ImportNewHire.xlst
  • In this import file there is a section that compares the VeteranStatus and create a few other keys based on the incoming value from RCM. Please find below sample of ImportNewHire.xlst:



There are two possible solutions to avoid this behavior:

  1. Do not use the key VeteranStatus in the integration between Onboarding and RCM;
  2. Remove the calculation logic from ImportNewHire.xlst. For this particular solution, you'll need to engage your implementation partner for review and apply this solution in your environment, since that needs to be done in Onboarding SuperAdmin.


ImportNewHire.xlst, VeteranStatus, Setup Onboarding Integration , KBA , LOD-SF-OBD , Onboarding , LOD-SF-OBD-INT , Integrations with Onboarding , Problem


SAP SuccessFactors Onboarding