> ## 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).

# Time Event Type

The following article will help explain how you can add or update an **Time Event Type** 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. From the **Iteration**, navigate to the generated workbook by clicking the **sheet icon**.

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


5. The workbook will appear in a new tab on your browser. Select the **Time Event Type** worksheet.

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

6. Fill Out This Sheet – Column Guide
* **Column B:** Set the **Processing Status** to **Pending**.
* **Column C:** Enter the **Processing Object** — the reference value tied to this record.
* **Column E:** Enter the **Code** for the time event.
* **Column F:** Enter the **Title** of the time event.
* **Column G:** Enter a **Description** for the time event.
* **Column H:** Specify the **Event** — Start or Stop.
* **Column I:** Set the **Status** to TRUE or FALSE to indicate if the event is active.
* **Column J:** Read-only, auto-generated — **Last Modified By**.
* **Column K:** Read-only, auto-generated — **Last Modified On**.

![](https://storage.crisp.chat/users/helpdesk/website/-/5/a/5/3/5a53c0e6e1563400/image_7i02ib.png)
7. **Continue after the Divider:**
* **Column M:** Enable **pairing of Time Events** of the same Time Event Type (TRUE/FALSE).
* **Column N:** Enter the **Duration** — overdue time events threshold.
* **Column O:** Enable the **Workflow Process** for manual creation or deletion of Time Events (TRUE/FALSE).
* **Column P:** Enable the **Reason Field** for this Time Event (TRUE/FALSE).
* **Column Q:** Specify whether the **Reason field is mandatory** (TRUE/FALSE).
* **Column R:** Enable the **Comment Field** for this Time Event (TRUE/FALSE).
* **Column S:** Specify whether the **Comment field is mandatory** (TRUE/FALSE).

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

8. 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_c2mxie.png)

9. 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 **Time Event Type** 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_1dhwz0x.png)

10. 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)

11. Once the status shows complete, go back in the workbook, and observe that **Time Event Type** has been added successfully as the rows and their corresponding fields are now highlighted green. Meanwhile, the processing status have also turned to processed.

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

12. You can also confirm these changes by switching to **Configure Clock In Clock Out** on SAP Success Factors and **Time Event Type.**

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

Thanks for using **CodeBot.**