Skip to content
✦ Made with Docsie · generated from video

How to Create an Event Reason in SuccessFactors

This guide shows you how to create an event reason in SuccessFactors, from the Admin Center form through to permissions. You enter the required fields, check the related picklist values, and configure optional fields such as Follow-Up Activity in Position and Payroll Event. You then grant permissions for the new event reason. The guide also covers event reason derivation with business rules and the related provisioning settings.

SuccessFactors 36 steps 26 screenshots 2240 words Source video 13:33 Generated cost $4.90

Video: How To Create Event Reasons - SAP SuccessFactors Employee Central by Web World Design (2021). All credit for the demonstration goes to the creator; watch the original on YouTube. The written guide below was generated from this video by Docsie. Creator? Request a change or removal.

This guide shows you how to create an event reason in SuccessFactors, from the Admin Center form through to permissions. You enter the required fields, check the related picklist values, and configure optional fields such as Follow-Up Activity in Position and Payroll Event. You then grant permissions for the new event reason. The guide also covers event reason derivation with business rules and the related provisioning settings.

Prerequisites

Before you start, make sure you have the following:

  • Access to the SAP SuccessFactors system and its Admin Center.
  • Events defined in the Picklist Center. Events determine where an event reason can be used, for example Hire or Termination.
  • A positionActionType picklist with the values RCLS and TRAN, if you plan to use Follow-Up Activity in Position.
  • Payroll integration enabled in provisioning, if you plan to use the Payroll Event field.

Create the event reason

1

Log in and open the Admin Center

Log in to the SAP SuccessFactors system, then navigate to the Admin Center.

2

Search for Manage Organization, Pay and Job Structures

  1. Click the Search for actions or people field at the top right to activate it. You can use this search bar to search for action keywords or employee names.
  2. Type Manage Organization, Pay and Job Structures.
  3. Select Manage Organization, Pay and Job Structures from the search results.
The SuccessFactors Employee Profile page with the search bar highlighted and a tooltip about searching for actions or people
The SuccessFactors Employee Profile page with the search bar highlighted and a tooltip about searching for actions or people
3

Open the event reason form

  1. In Manage Organization, Pay and Job Structures, locate the Create New dropdown.
  2. Select Event Reason to open the event reason creation form.
4

Review the form fields and set the effective date

The Event Reason form contains the following fields:

  • Effective as of: The date from which the event reason is effective, for example 03/01/2021 (March 1, 2021). The event reason is available for selection only on or after this date.
  • Event Reason ID: A unique identifier for the event reason.
  • Event Reason Name: A descriptive name for the event reason.
  • Description: An optional description.
  • Status: Set to Active to enable the event reason.
  • Event: The relevant event, selected from the dropdown.
  • Employee Status: The appropriate employee status.
  • Follow-Up Activity in Position: A follow-up activity, if required.
  • Payroll Event: The payroll event, if applicable.
  • Display in Internal Job History Portlet: Yes or No, as needed.

Start by entering the Effective as of date. Review all entered information for accuracy before you save.

The Event Reason form with the Effective as of date picker open and March 1, 2021 selected
The Event Reason form with the Effective as of date picker open and March 1, 2021 selected
The Event Reason form with Effective as of set to 03/01/2021 and the remaining fields ready for input
The Event Reason form with Effective as of set to 03/01/2021 and the remaining fields ready for input
5

Enter the event reason ID

Type DBHIRE in the Event Reason ID field. This value uniquely identifies the event reason in the system.

The Event Reason form with DBHIRE entered as the Event Reason ID
The Event Reason form with DBHIRE entered as the Event Reason ID
6

Enter the event reason name

Type A New Hire in the Event Reason Name field. This descriptive name is displayed for the event reason.

The Event Reason form with A New Hire entered as the Event Reason Name
The Event Reason form with A New Hire entered as the Event Reason Name
7

Enter the description

Type A New Hire in the Description field. The description can match the event reason name or provide additional context.

The Event Reason form with A New Hire entered as the Description
The Event Reason form with A New Hire entered as the Description
8

Set the status

Select Active from the Status dropdown. Only event reasons marked as Active are available for selection in the system. If you set the status to Inactive, the event reason is not selectable or usable.

The Event Reason form with Status set to Active
The Event Reason form with Status set to Active
9

Select the event

  1. Click the Event dropdown.
  2. Choose Hire from the list of available events.

Events are defined in the Picklist Center and determine where the event reason can be used, for example Hire or Termination. Associating this event reason with the Hire event means it appears only in relevant Hire UIs.

The Event Reason form with the Event dropdown open and the available events listed
The Event Reason form with the Event dropdown open and the available events listed
10

Set the employee status

  1. Click the Employee Status dropdown.
  2. For a hiring event, select Active.

This ensures that when you use this event reason, the employee's status is set to active in the Job Information portlet.

The Event Reason form with the Employee Status dropdown open and ready for selection
The Event Reason form with the Employee Status dropdown open and ready for selection

Configure Follow-Up Activity in Position

11

Make the Follow-Up Activity in Position field visible

Locate the Follow-Up Activity in Position field. You set this field on individual event reasons, and it may not always be visible.

If the field is not visible, update the visibility of the field implicit-position-action in the corporate data model. This field is present in the HRIS element ID eventReason and uses the picklist positionActionType. Configure the picklist with two values:

  • RCLS (Position Reclassification)
  • TRAN (Position Transfer)
The Event Reason form with the Follow-Up Activity in Position dropdown open, showing No Selection, Position Reclassification, and Position Transfer
The Event Reason form with the Follow-Up Activity in Position dropdown open, showing No Selection, Position Reclassification, and Position Transfer
12

Open the positionActionType picklist in the Picklist Center

  1. From the Admin Center, navigate to the Picklist Center.
  2. Use the search bar to search for the picklist positionActionType.
The Picklist Center with the search bar being used to search for "position"
The Picklist Center with the search bar being used to search for "position"
13

Verify the picklist values

In the Picklist Center, check the details for positionActionType. Confirm that the picklist contains exactly two values:

  • RCLS with the label Position Reclassification and status Active.
  • TRAN with the label Position Transfer and status Active.

Both values must be Active to be selectable in configuration. The top of the screen shows the following reference details:

  • Code: positionActionType
  • Status: Active
  • Effective Start Date: Jan 1, 1900

Use this screen to confirm that your configuration matches the setup required for event reasons that involve position actions.

The Picklist Center showing the positionActionType picklist with RCLS (Position Reclassification) and TRAN (Position Transfer), both Active
The Picklist Center showing the positionActionType picklist with RCLS (Position Reclassification) and TRAN (Position Transfer), both Active
14

Set the follow-up activity on the event reason

Click the Follow-Up Activity in Position dropdown and select Position Reclassification or Position Transfer, as needed.

When a manager makes any change in the Update Employee Record screen using this event reason, the selected follow-up activity is triggered. This applies to event reasons derived from business rules and to those defined manually.

The Event Reason screen with the Follow-Up Activity in Position dropdown showing Position Reclassification and Position Transfer
The Event Reason screen with the Follow-Up Activity in Position dropdown showing Position Reclassification and Position Transfer
The Event Reason screen with the Follow-Up Activity in Position dropdown, illustrating how the setting is used
The Event Reason screen with the Follow-Up Activity in Position dropdown, illustrating how the setting is used

Configure the internal job history and payroll event fields

15

Set Display in Internal Job History Portlet

Locate the Display in Internal Job History Portlet field for each event reason. Set it to Yes for every event reason that should be visible in the internal job history.

If you set this field to No, EC (Employee Central) historical data is not visible in the internal job history portlet.

16

Enable and configure the Payroll Event field

The Payroll Event field is available on the event reason when payroll integration is enabled in provisioning. If the field is not visible, enable it from provisioning.

After you modify the corporate data model, verify that the event reason UI contains the Payroll Event field. Then apply these rules:

  • Configure the field as a string data type only. Do not use bit lists or other data types.
  • Make sure the value is exactly four characters long. Do not enter longer values.
17

Enter the payroll event value

In the Event Reason configuration screen, locate the Payroll Event field and enter a value that is exactly four characters long, for example 1234.

If you enter more than four characters, the system displays the error "reached the maximum length allowed of 4 characters." The field does not accept longer values. This restriction prevents integration issues.

The Event Reason screen with the Payroll Event field showing an error for exceeding four characters
The Event Reason screen with the Payroll Event field showing an error for exceeding four characters

Grant permissions for the event reason

18

Open the permission role list

  1. In the Admin Center, select Manage Permission Roles.
  2. On the Permission Role List screen, review the available roles with their user types, descriptions, statuses, and actions.
  3. Locate the role you want to configure, for example SF Admin.
The Permission Role List screen showing several roles, including SF Admin
The Permission Role List screen showing several roles, including SF Admin
19

Open the role details

  1. Click the role name, for example SF Admin, to open the Permission Role Detail screen.
  2. Under Permission Settings, click the Permission button to view and edit the permissions for the role.
  3. Review and adjust permissions as needed, such as access to position management, the metadata framework, and other modules.
The Permission Role Detail screen with the Permission button highlighted and permissions listed
The Permission Role Detail screen with the Permission button highlighted and permissions listed
20

Configure event reason permissions for employee data

  1. In the Permission settings dialog, make sure the Employee Data section is selected.
  2. Locate the Event Reasons column.
  3. Search for the event reason you want to configure, for example A New Hire (DBHIRE). You can enter DBHIRE in the search bar at the top right of the dialog.
  4. Select the appropriate boxes under View and/or Edit to grant the permissions you want.
  5. Click Done to confirm your selections.
The Permission settings dialog showing Employee Data and the event reason A New Hire (DBHIRE) with permission checkboxes
The Permission settings dialog showing Employee Data and the event reason A New Hire (DBHIRE) with permission checkboxes
21

Save the permission settings

  1. After you change event reasons and picklist external codes, review your permission settings. In the Permission settings dialog, make sure the correct event reasons are selected and the permissions are set as needed.
  2. Click Done to confirm your selections.
  3. On the main Permission Role Detail screen, click Save Changes to apply your updates.
The Permission settings dialog in the Admin Center with the Employee Data section, the event reasons list, and the Done button highlighted
The Permission settings dialog in the Admin Center with the Employee Data section, the event reasons list, and the Done button highlighted
22

Troubleshoot permission changes that don't take effect

If users don't see the permission changes you made, try the following in order:

  • Log out of SuccessFactors and log back in to refresh your session and apply the new permissions.
  • If the issue persists, clear your browser cache to remove stored data that might cause display issues.
  • Try accessing SuccessFactors in a completely different browser to rule out browser-specific caching problems.
The Permission settings dialog with event reason permissions and a browser search bar visible, illustrating the troubleshooting steps
The Permission settings dialog with event reason permissions and a browser search bar visible, illustrating the troubleshooting steps

Derive event reasons with business rules

23

Understand the derivation approaches

SuccessFactors supports both XML-based and rules-based approaches for deriving event reasons in job information and compensation information. The XML-based approach derives event reasons for changes to job and compensation data.

A new rules scenario supports "unsafe" rules in the job information and compensation modules. This allows more flexible event reason assignment.

24

Open Business Rules Admin

Click Business Rules Admin in the Admin Center menu. You see a list of existing business rules with these columns:

  • Rule Name
  • Rule ID
  • Scenario
  • Rule Type
  • Base Object
  • Last Modified By
  • Assigned

Use the search and filter options to locate specific rules.

25

Start a new rule

Click Create New Rule to begin configuring a new business rule. The button is typically at the top right of the Business Rules Admin screen.

The Business Rules Admin screen with the list of rules and the Create New Rule button highlighted
The Business Rules Admin screen with the list of rules and the Create New Rule button highlighted
26

Select the Event Reason Derivation scenario

  1. On the Configure Business Rules screen, review the rule scenario categories, for example Advances Management, Benefits Management, Calibration, and Employee Central Core.
  2. Expand Employee Central Core to view the related scenarios.
  3. Click the radio button next to Event Reason Derivation.

This scenario derives the event reason automatically for Job and Compensation Information entities. A description appears and explains how it automates event reason assignment during job or compensation changes.

27

Enter the rule details

In the Event Reason Derivation panel, enter the following:

  • Rule Name: A unique name for your rule.
  • Rule ID: A unique identifier for the rule.
  • Start Date: The effective start date for the rule. The default is 01/01/1900.
  • Description: An optional description.
28

Choose the base object type

Click the Base Object Type dropdown and select the type that fits your rule. The available options are:

  • Job Information Model
  • Compensation Information Model
The Event Reason Derivation panel with the Base Object Type dropdown showing Job Information Model and Compensation Information Model
The Event Reason Derivation panel with the Base Object Type dropdown showing Job Information Model and Compensation Information Model
29

Confirm your selection

Make sure all required fields are filled, then click Continue to proceed with rule creation.

Each business rule is created for a specific object, either Job Information or Compensation Information, and is automatically migrated as needed. For more detail on configuring event reason derivation rules, refer to the SAP documentation.

30

Recognize migrated rules

All migrated rules in SAP SuccessFactors start with the postfix migrated_rule. This naming makes it easier to identify, view, and edit migrated rules. A rule with this postfix was migrated as part of the system update.

The Configure Business Rules screen with Event Reason Derivation selected and a note that all migrated rules start with the postfix migrated_rule
The Configure Business Rules screen with Event Reason Derivation selected and a note that all migrated rules start with the postfix migrated_rule
31

Understand automatic assignment of new rules

New business rules are automatically assigned to the respective HRIS objects in the system. The correct rules are therefore applied to Job Information or Compensation Information entities without manual intervention.

The Configure Business Rules screen showing the Event Reason Derivation panel, the note about migrated rules, and the Base Object Type dropdown
The Configure Business Rules screen showing the Event Reason Derivation panel, the note about migrated rules, and the Base Object Type dropdown

Review provisioning settings for business rules

32

Note the removed legacy switch

The legacy switch Enable youCalc Rules Engine for HRIS has been removed from the provisioning settings. This streamlines the configuration and removes the dependency on the old rules engine.

The Configure Business Rules screen with a note about the removal of the legacy Enable youCalc rules engine for HRIS switch
The Configure Business Rules screen with a note about the removal of the legacy Enable youCalc rules engine for HRIS switch
33

Note the decoupled switches

The Enable Business Rules for Event Reason Derivation switch and the other related workflow switches are now decoupled. Enabling or disabling one does not affect the other. This gives you more granular control over rule and workflow derivation.

34

Understand workflow derivation logic

The Enable Business Rules for Workflow Derivation switch controls how workflows are derived:

  • If you enable it, workflows are derived using business rules.
  • If you disable it, workflows are derived from the XML model.
35

Understand event reason derivation logic

The Enable Business Rules for Event Reason Derivation switch controls how event reasons are derived:

  • If you enable it, event reasons are derived using business rules.
  • If you disable it, event reason derivation is disabled.
The Configure Business Rules screen with a note explaining event reason derivation when Enable Business Rules for Event Reason Derivation is on or off
The Configure Business Rules screen with a note explaining event reason derivation when Enable Business Rules for Event Reason Derivation is on or off
36

Spot test after changes

After you change business rules or provisioning settings, perform spot testing in all instances. This confirms that event reason and workflow derivation work as expected in your SAP SuccessFactors environment.

Summary

You now know how to create an event reason in SuccessFactors. You entered the event reason details, checked the positionActionType picklist, and configured the follow-up activity, internal job history display, and Payroll Event field. You then granted permissions for the new event reason. You also reviewed how event reason derivation works with business rules and how the provisioning switches affect it.

What's next

  • Create a business rule with the Event Reason Derivation scenario to automate event reason assignment for job or compensation changes.
  • Look for rules with the migrated_rule postfix to review migrated rules.
  • Perform spot testing in all instances after you change business rules or provisioning settings.
  • Refer to the SAP documentation for more detail on configuring event reason derivation rules.
Generation details: cost, quality tiers

Docsie billed 7,000 credits ($4.90) to analyze this 14-minute video at standard quality. The rewrite, template fill and Word/PDF exports were included. The same video at each quality tier:

QualityFrames sampledCreditsApprox. cost
Draftevery 16-30 s3,500$2.45
Standard (this guide)every 8-15 s7,000$4.90
Detailedevery 4-7 s14,000$9.80
Ultraevery 1-3 s28,000$19.60

Credits priced at $0.70 per 1,000; plans include a monthly allowance. Enterprise customers on on-premise or bring-your-own-model deployments run this on their own inference and pay no per-video credits.

Generated by Docsie Video-to-Docs on 2026-11-01 from a 13-minute video. Screenshots are frames from the source video and belong to their creator, Web World Design, whose original is embedded above. If you own this video and want the guide removed or credited differently, contact us and we will act within one business day.

Turn your own training videos into guidesJoin teams that save hours, reduce documentation work and scale training with Docsie.
See Docsie in action. No commitment.

Ready to Transform Your Documentation?

Start creating professional documentation that your users will love