3686312 - LinkedIn Recruiter System Connect (RSC) - Data Transfer to new Standard Fields for RSC Implemetation using Integration Center

As explained in KBA 3679842, some field mappings have options that are hardcoded to specific fields in SuccessFactors Recruiting. For example, industries and employmentStatus from LinkedIn map to industry and classificationType in Recruiting, and this mapping cannot be changed.

This can create implementation challenges, as some fields linked to these hardcoded mappings are not used by customers, and they may have other standard or custom fields where the same information is stored.

This KBA explains how to move the existing data into the fields required for the mapping.

For example, if a customer does not use the employmentStatus standard field but has another field with the same information, they must still map and fill employmentStatus to implement LinkedIn Recruiter System Connect (RSC). This KBA guides how to create an Integration Center job to transfer the data.

"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 Recruiting Management

You can also refer to the SAP Community Blog Post - LinkedIn Recruiter System Connect (RSC) Implementation - Data Transfer to new Standard Fields

NOTES:

• This integration needs experience with Integration Center and Recruiting configuration, and it is meant to be handled by Implementation Partners or Admin Users who have an implementation background;
• The integration described below may behave in different ways on different systems. Please make sure to test all steps in a lower environment before moving anything to Production;
  • For better results, we suggest testing first with a small number of records before updating all of them.
• Integration Center may not support updating all records in one single run if the number is higher than the tool's limit. We strongly recommend reviewing Integration Center limits before creating the integration: 2742107 - Integration Center: Frequently asked questions
• As a best practice, avoid creating one integration for more than one field mapping, as this may cause performance timeouts;

STEPS:

1. Go to Admin Center > Integration Center > My Integrations;
2. "+ Create" button > More Integration Types;
3. Select the following setup:
   • Trigger: Scheduled
   • Destination: SuccessFactors
   • Source: SuccessFactors
   • Format: OData v2
     
4. Select the entity;
   • • For Candidate Profile entity, you can use the entity CandidateLight to bypass required field validation
     • For Job Application, you can refer to the KBA Required attribute on Application fields via OData API - Recruiting Management
     • For Job Requisition, you can add the property "isDraft" to the mapping, making sure to pass TRUE. With this value, you can make your update without providing all mandatory values on the Job Requisition.
   • If the following criteria is not meet, the update may fail.
5. On "Options" tab, fill all necessary fields
6. On "Configure Fields" tab:
   1. Change the view to "Field Mapping View"
      
   2. Link the source field with the new standard field; - For example, you are mapping your existing standard OR custom fields that holds up the Employment Category to employmentStatus field, you need to link the existing field from the left column to the employmentStatus field in the right column. Here's an example from the columns (The entity here is Candidate):
      
      You need to drag and drop the field.
      
      
      
   3. Repeat the same steps to the ID field by linking the field from the left column to the right column
      • IDs per entity:
        • Candidate ID - candidateId
        • Job Application ID - applicationId
        • Job Requisition ID - jobReqId
   4. Once the mapping is done go to "Filter and Sort" and exclude any anonymized record, otherwise the system will considered anonymized records, which don't support updates:
      1. Click on "Browse" button
      2. Entity Tree View > Select the "Anonymized Flag"
      3. Add and filter by 0 (0 is the value for "Non-Anonymized)
   5. You can skip the "Scheduling" tab as the integration is meant to be executed one time only;
   6. "Review and Run" tab:
      • Click on "Run Now"
      • Wait the integration to complete
      • Verify any possible errors and fix

• 3669079 - Linkedin Recruiter System Connect - Recruiting Management
• 3679842 - LinkedIn Recruiter System Connect (RSC) - Not Possible to Change Field Mapping for Specific Fields

mapping, RSC, field, linkedIn, data, field , KBA , LOD-SF-RCM-INT , Integration Center & Intelligent Services , Problem