Symptom
The Application ID (standard field) from Application is not flowing from RCM to EC , eventhough the respective configuration is in place
Environment
Successfactors Bixz Recruiting
Cause
Configuration issue.
The mapping template needs to configured specially so that the Application Id flows from RCM to EC
Resolution
The conventional configuration looks like this
mapping-attribute>
<source refid="id" entity-type="application"/>
<target refid="employmentInfo.custom-string79"/>
</mapping-attribute>
Where the "id" refers to the standard field in the Application and this looks correct, where the customer expect the application ID value should flow to the EC field mapped to custom-string79 from Application
However the system do not understand this and still the field in EC would be empty .
Correct configuration :
mapping-attribute>
<source refid="applicationId" entity-type="application"/>
<target refid="employmentInfo.custom-string79"/>
</mapping-attribute>
Please change the refid from id to applicationId only in the Trasformation template and not in the Application template(In application template the application id field should be still referred as "id" ).
So that the system understands and the value in the application ID will be flown from RCM to EC
Keywords
Application id , Transformation template, RCM to EC mapping , KBA , LOD-SF-RCM-INT , Integration Center & Intelligent Services , Problem