SAP Knowledge Base Article - Public

2338323 - Propagation of Global Info fields from RCM to EC

Symptom

Error: "Global Info fields are configured. But Country has not been passed from RCM. Please configure globalInfo.country or jobInfo.company, jobInfo.company.country, homeAddress.country.home for global info fields to be propogated to New Hire"

Environment

  • SAP SuccessFactors HCM Cloud
  • Employee Central
  • Recruiting Management

Resolution

Configurations Steps
  1. In RCM-EC transformation template, there are four ways to determine the country for the globalInfo mapping for a candidate. The precedence is:
    1. globalInfo.country
    2. jobInfo.company
    3. jobInfo.company.country
    4. homeAddress.country.home
    1. Note: If either of these is configured, the globalInfo fields related to the target country will be loaded and the data from RCM, will be mapped to the corresponding fields. 
    3. The field for mapping for the various countries is specified as follows
    5. <mapping-attribute>   
    6. <source refid="firstName" entity-type="application"/>   
    7. <target refid="globalInfo.[USA].genericNumber1 | globalInfo.[ARG].genericString1" />
    8. </mapping-attribute> 
    10. If none of the four targets are configured but we have a mapping for globalInfo, we get the below exception:
    11. "Global Info fields are configured. But Country has not been passed from RCM. Please configure globalInfo.country or jobInfo.company, jobInfo.company.country, homeAddress.country.home for global info fields to be propogated to New Hire"

 

  1. For a given RCM source, different globalInfo targets for different countries, can be configured as below. Based on the country selected from step 1, the corresponding target will be picked up and loaded with RCM data.
    2. <mapping-attribute>
      <source refid="no_of-children" entity-type="candidate"/>
      <target refid="globalInfo.[IND].custom-long1 | globalInfo.[USA].custom-long2 | globalInfo.[CHN].custom-long2" />
      </mapping-attribute
    5. Mapping Examples:
    7. <mapping-attribute>  
      <source refid="firstName" entity-type="application"/>
      <target refid="globalInfo.[USA].genericNumber1 | globalInfo.[ARG].genericString1" />
      </mapping-attribute>
    9. <mapping-attribute>    
      <source refid="middleName" entity-type="application"/> 
      <target refid="globalInfo.[USA].genericString1 | globalInfo.[ARG].genericString1" />
      </mapping-attribute>
    11. <mapping-attribute>
      <source refid="country" entity-type="jobrequisition"/>   
      <target refid="jobInfo.company.country" />
      </mapping-attribute>
    13. <mapping-attribute> 
      <source refid="country" entity-type="application"/>
      <target refid="globalInfo.country" />
      </mapping-attribute>
    15. <mapping-attribute>
      <source refid="country" entity-type="jobrequisition"/>
      <target refid="homeAddress.country.home" />
      </mapping-attribute>

See Also

Specific stipulations:

  1. By default, the Global info section will be loaded with CSF fields related to country we got from #1 only. It doesn't contain CSF fields related to legal entity's country.
  2. For the country we got from RCM as per the mapping, if CSF SDM doesnt have any global info fields configured, the CSF fields related to the legal entity's country will be loaded.
  3. For the country we got from RCM, if transformation template doesn't have any target fields configured, the CSF fields related to legal entity's country will be loaded.

Keywords

EC, RCM, propagation xml, field mapping, globalInfo , KBA , LOD-SF-EC-INT , Manage Pending Hires (Integration RCM/ ONB/ OBX + UI) , LOD-SF-RCM , Recruiting Management , LOD-SF-OBD , Onboarding , How To

Product

SAP SuccessFactors Employee Central all versions