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

# EC - Event Reason

The following article will help explain how you can create an event reason 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_15myzdb.png)


2. On the Home screen, click on the **Employee Central** module.

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


3. Select your workspace from the next screen.

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


4. Open the workbook and navigate to the **Event Reason** worksheet.

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

5. Event Reason Setup

**Column B** – Processing Status: Set to Pending for the new record.
**Column C** – Event Reason ID: Unique code for the event reason.
**Column E** – End Date: Expiration date, typically 12/31/9999.
**Column F** – Event Reason Name: Display name for the event reason.
**Column G** – Start Date: Effective date of the record.
**Column H** – Description: Brief description of the event reason.
**Column I** – Status: Active or Inactive.
**Column J** – Event: Select the event type (e.g., Termination, Pay Rate Change).


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

**Column K** – Employee Status: Status this event reason triggers.
**Column L** – Follow-Up Activity in Position: Follow-up action in the position record, if any.
**Column M** – Display in Internal Job History Portlet: Yes or No.
**Column N** – Payroll Event: Payroll event tied to this record.|

**Fill out the remaining fields according to your requirements**.


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


6. Close the workbook and navigate back to SFCodeBot. Click the hamburger icon under the Actions tab for the same iteration number. Select **‘Start Configuration’**

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

7. 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 the **Event Reason** checkbox and finally, click **Confirm and Start** to begin the execution.


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


8. As the status changes to processing you can track the progress of the execution. To monitor the progress please refer to the article attached below:

[__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)


9. Once the status shows Complete, return to the workbook and confirm the **event reason** has been added successfully — the row and its fields are now highlighted green, and the Processing Status has changed to **Processed**.

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

**Screenshot 02**

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


10. You can confirm the changes by accessing Manage Organization, Pay and Job Structures in SAP SuccessFactors. Once there, select Event Reasons and search for the event reason you just created.
![](https://storage.crisp.chat/users/helpdesk/website/-/5/a/5/3/5a53c0e6e1563400/image_7h7fi9.png)


**Thanks for using CodeBot!**