Skip to Content

Configuring SuccessFactors Employee Central Job Info into Employee Profile

Recently, a had some friends ask me if it was possible to enable a sync to auto populate Employee Central Job Information directly to Employee Profile’s Work Experience Within Company or Job History Portlet. The answer is “YES” and I’m pretty sure SuccessFactors have documented it somewhere. The big question or challenge most of us face is “Where can I find it?”

In this blog, I’ll go through the configuration steps required to enable this function.

Corporate Data Model

In Provisioning, download the Corporate Data Model and look for the <hris-element id=”eventReason”> section.


Make sure the visibility of the “include-in-work-experience” ID is set to “both”.  If the HRIS field is not available, just add it in before the closing of the </hris-element>.

Now update the Corporate Data Model back in Provisioning.

Foundation Object

Go to Admin Tools > Employee Files > Manage Organization, Pay and Job Structures.

Look for Event Reason “Transfer” (or any Event Reason driven Job Info record which you would want to include in Employee Profile)

Do Take Action > Make Correction and change the Include in Work Experience Flag to “Yes” and Save.


Repeat the steps for other event reasons.  This controls what type of history will default into the new job history portlet. I would recommend the following event reasons to include such as “New Hire”, “Rehire”, “Job Reclassification” and “Promotion”.

Configure Business Rules

Next we need a business rule which we will attach on the Employee Profile portlet.

Go to Admin Tools > Company Settings > Configure Business Rules and Create A New Rule

Make sure the Base Object is “Job Information” and the “if” statement Event Reason.Include In Work Experience = Yes


Enabling Employee Profile Portlet

Now go to Admin Tools > Employee Files > Configure Employee Files

Select the view you would like to add the new portlet to. In my example below, I would be adding it to the Profile.


Select “Insert Portlet” where you would like the portlet to show up and “Create and Add” the Internal Job History portlet.  You may also want to delete the existing “Work Experience Within Company” section since this is now a duplicate.


Proceed to configure the Internal Job History Portlet

In my example, I renamed the portlet to reflect Work Experience Within Company replacing the former.

Please also ensure to define the business rule created previously as the Rule name and include the fields you would like to display and save.

Do remember to Save Dashboard when you’re completed


Role Based Permission

The final step now is to give access to this newly created portlet. Do note that there is no need to give “edit” access since this is displaying information from Employee Central.


And now to test. Select any employee and go to their Profile record. Scroll to the newly created portlet and Job Information record would be populated here.


Thank you,

Leon Lee |

You must be Logged on to comment or reply to a post.
  • One more excellent blog ! Very informative ! This let's Employee Central information flow to Profile through simple "Event Reason Configuration". This also let's me define only certain event reason based info flow to profile rather than forcing me to send for every event reason.

    Keep writing more blogs !

  • Hi Leon

    I tried following you recipe, but cannot really get it to work. We are running the new "People Profile", and I wonder whether this has any impact on the setup required. I would like to move Job Information to the "insideWorkExperience" background element.

    1) Does the rule you propose need to include anything in the "Else" section of is the "If" part enough?

    2) Do I still need to configure the "job history portlet". I have done this but it does not appear anywhere and I have triple-checked permissions.



    • Hi Brian,

      Apologies for missing this. I don't think the configuration above works with people profile and its section/blocks.

      1. The rule does not need any value for the "Else" condition.

      2. What did you configure on the job history portlet? Could you attached a screen capture? 


  • Hi Leon,

    Thanks a lot for the article. Please, let me know if you have seen the next message in Job history portlet "Only one key can be requested at a time". The configuration was made step by step as is shown above.

    Thank you

    • Hi Ibzan,

      I'm not sure I understand what you mean by the next message in Job History Portlet.

      Care to elaborate further? Thanks!

      • Hi Leon,

        Yes, of course. I have the next message in the portlet:

        Briefly, the configuration was:
        - The corporate data model has the next code: “include-in-work-experience” ID is set to “both”

        - In event reason we have "Include in Work Experience" Flag to “Yes”

        - Our business rule is:

        - Job History portlet:

        - RBP for this portlet is enabled.

        It seems that our issue is within the configuration, but according with the manual there is not error. Is the first time we have the message, other configurations have been successful.

        Please, let us know if you have seen the same issue or you have more documentation about that.

        Thank you

        Kind regards,

        • Thanks for this blog post Leon. @Ibzan, I get the same error as you after following Leon's instructions. The error shows up in the new portlet we added " Internal Job History", and we get the error: "Portlet configuration Error: Only one key can be requested at a time".

          I logged an SF Ticket for this. No response yet on when a patch will be ready, but the Rep said it's a known regression issue specifically for this portlet and the Engineering team is working on a patch. TBD planned fix date.



          • Hi Anita, Ibzan,

            Yes, there seem to be an issue with this portlet after a recent update.

            It's strange because it works perfectly well for my existing clients but it fails for my newer clients.

            As per Anita, it's probably worth raising an SF ticket.



  • Hi Anita, Ibzan,

    The issue has since been rectified by SAP on the b1605 patch.

    Please check your instance and it's version and try again.


  • Hello Leon,

    Good blog. We have an issue, where we have implemented Employee Central for one country and other countries have only Employee Profile.

    Some employees in Employee Central have managers from Employee Profile. Hence we can change the Supervisor only through UDF upload. Since Employee Profile users are not searchable in Employee Central, the supervisor field of job information remains empty. Lately we observed that whenever there is any change in the Employee central job info, it syncs with Employee profile; hence deletes the Line Manager, uploaded from UDF. Does anyone else have similar issue, is there a solution for this?

    Thanks & Regards,


    • Hi Shilpa,

      It will only sync values for the employees in Employee Central. The sync only runs for employees when data is changed, except for the initial one-time sync job that is setup. If you are experiencing different behavior, please raise a ticket with SAP Support.

      Best regards,


  • has anyone configured this on people profile v3?? If so could you please guide me or send an email to

    Thanks in advance