2641994 - How to configure field association for FO Location as a child field - Recruiting Management

This article explains how to configure the association for the FO field Location. The case explained here works just if the field location is the child field. If you want to configure the location field as a parent, please follow the instructions on Implementing HR Master Data Sync for Foundation Object and Generic Object Fields in Recruiting Management.

If the configuration is not correct, the user may see the following error when uploading the job requisition template:

The field "location_obj" has field criteria defined with an invalid SourceFieldName "Division"

"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

When checking the guide Implementing HR Master Data Sync for Foundation Object and Generic Object Fields in Recruiting Management, we see there are no instructions on how to configure the Location field as a child field in an association.

In order to implement this solution, you have to follow the below steps:

1. We need first configure the association in the Corporate Data Model. Include the following line at the end of the Location field declaration.

The destination-entity is the parent object that will be used in the association of this field.

2. After configuring the association in the corporate data model, we have to add the field criteria for the location field in the Job Requisition XML template.

On the example we create for this article, we are making the Division field the parent of the Location field. Both fields have to be an object type.

3. After having the XML templates configured, it is time to make the associations on the foundation object using the UI. Go to admin center > Manage Organization, Pay and Job Structures and make the associations according to your business need.

Select the desired Location, click make correction and add the necessary associations. This action needs to be done to all locations.

When finishing the configuration, you will be able to make just valid selections for the location field based on the value provided in the parent field. On our example, you will be able to select the Amsterdam as a location just if you select one of the associated Divisions:

Here is an example where we did not provide any value to Division and the Location field did not show any information:

Once selecting one of the Divisions from the above configuration, we are able to select Amsterdam as Location:

FO Location; Association with Location RCM; The field "location_obj" has field criteria defined with an invalid SourceFieldName "Division" , KBA , LOD-SF-RCM , Recruiting Management , How To