> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.sfcodebot.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Employee Sync Config

The following article will help explain how you can add or update **Employee Sync Config** through SFCodeBot.

1. Navigate to **CodeBot** for SAP **SuccessFactors**, and enter your login details.
![](https://storage.crisp.chat/users/helpdesk/website/-/5/a/5/3/5a53c0e6e1563400/image_amm2lw.png)

2. On the Home screen, click on the **Time Track** module.

![](https://storage.crisp.chat/users/helpdesk/website/-/5/a/5/3/5a53c0e6e1563400/image_vexoc7.png)


3. Select your workspace from the next screen.

![](https://storage.crisp.chat/users/helpdesk/website/-/5/a/5/3/5a53c0e6e1563400/image_1svencc.png)


4. Navigate to the generated workbook by clicking the **Sheet** icon..

![](https://storage.crisp.chat/users/helpdesk/website/-/5/a/5/3/5a53c0e6e1563400/image_10smq54.png)

5. The workbook will appear in a new tab on your browser. Select the **Employee Sync Config** worksheet.

![](https://storage.crisp.chat/users/helpdesk/website/-/5/a/5/3/5a53c0e6e1563400/image_4p9z5e.png)

6. Employee Sync Configuration Sheet – Column Reference Guide
**Column B – Processing Status**
Set to Pending for new/unprocessed records
**Column C – External Code**
Unique ID tied to this record in the external system
**Column D – Date of Last Full Synchronization**
Date the last full sync was completed
**Column E – Last Synchronization Success**
Yes/No flag for whether the last sync completed successfully
**Column F – Number of Employees Synchronized**
Count of employee records synced in the last run
**Column G – Error Details**
Details of any error from the last sync; leave blank if none
**Column H – Synchronization Already In Progress**
Yes/No flag showing if a sync is currently running
**Column I – Trigger Full Synchronization**
Yes/No flag to manually kick off a full sync


![](https://storage.crisp.chat/users/helpdesk/website/-/5/a/5/3/5a53c0e6e1563400/image_1okqj4s.png)


7. Close the workbook, back in CodeBot click the hamburger menu and click on **Start Configuration**.

![](https://storage.crisp.chat/users/helpdesk/website/-/5/a/5/3/5a53c0e6e1563400/image_1p5p2q1.png)

8. On the **left-hand side**, enter your **SAP SuccessFactors** password or sign in using **SSO** (if it is configured for your instance). Next, enter the **Execution Notes**. On the **right-hand side**, under **Advanced Options**, select **Employee Sync Config** checkbox and choose the desired execution mode (**Standard** or **Optimized (Beta)**). Finally, click **Confirm and Start** to begin the execution.

![](https://storage.crisp.chat/users/helpdesk/website/-/5/a/5/3/5a53c0e6e1563400/image_ap8a5b.png)
9. As the status changes to processing you can monitor the execution. Below is the article attached for iteration monitoring.

[__https://help.sfcodebot.com/en/article/monitor-actions-in-codebot-for-sap-successfactors-1ous0mz/?bust=1748684800798__](https://help.sfcodebot.com/en/article/monitor-actions-in-codebot-for-sap-successfactors-1ous0mz/?bust=1748684800798)

10. Once the status shows complete, go back in the workbook, and observe that **Employee Sync Config** has been added successfully as the rows and their corresponding fields are now highlighted green. Meanwhile, the processing statuses have also turned to processed.

![](https://storage.crisp.chat/users/helpdesk/website/-/5/a/5/3/5a53c0e6e1563400/image_ddb476.png)
11. You can also confirm these changes by switching to **Manage Data** on SAP Success Factors and **Employee Sync Config.**
![](https://storage.crisp.chat/users/helpdesk/website/-/5/a/5/3/5a53c0e6e1563400/image_1a757r2.png)
**Thanks for using CodeBot!**